KR20230116959A - Displaying a scrollable list of affordances associated with physical activities - Google Patents

Abstract

This disclosure relates generally to managing user interfaces. In one method, a scrollable list of affordances associated with physical activities is displayed. A first athletic metric change affordance corresponding to the first affordance in the scrollable list of affordances is displayed. User input is received. Upon a determination that user input is detected at a first affordance in the scrollable list of affordances, a physical activity tracking function associated with the selected first affordance is initiated. Upon a determination that phase user input is detected at the first exercise metric change affordance, a user interface configured to change the exercise metric is displayed.

Description

DISPLAYING A SCROLLABLE LIST OF AFFORDANCES ASSOCIATED WITH PHYSICAL ACTIVITIES

claim of priority

This application is filed on May 15, 2017 and is entitled "DISPLAYING A SCROLLABLE LIST OF AFFORDANCES ASSOCIATED WITH PHYSICAL ACTIVITIES", US Provisional Patent Application Serial No. 62/506,304; and US Provisional Patent Application Serial No. 15/705,849, filed on September 15, 2017, entitled "DISPLAYING A SCROLLABLE LIST OF AFFORDANCES ASSOCIATED WITH PHYSICAL ACTIVITIES"; Their contents are hereby incorporated by reference in their entirety.

technology field

The present invention relates generally to computer user interfaces, and more specifically to techniques for displaying affordances associated with bodily activity.

Many modern electronic devices provide the ability to control exercise tracking functions. Some techniques for controlling the motion tracking function require multiple user inputs. These techniques can be cumbersome and inefficient.

However, some techniques for displaying interfaces associated with physical activities using electronic devices are generally cumbersome and inefficient. For example, some existing techniques use complex and time consuming user interfaces, which may involve multiple key presses and keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.

Accordingly, the present technique provides faster and more efficient methods and interfaces to electronic devices for displaying affordances associated with bodily activity. Such methods and interfaces optionally complement or replace other methods for displaying affordances associated with bodily activity. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.

In some embodiments, a method, in an electronic device having a display, a touch-sensitive surface, and a body activity tracking sensor, includes: displaying a scrollable list of affordances associated with physical activities; displaying a first athletic metric change affordance corresponding to a first affordance in the scrollable list of affordances; receiving user input; upon a determination that a user input is detected at a first affordance in the scrollable list of affordances, initiating a physical activity tracking function associated with the selected first affordance; and in response to a determination that a user input is detected at the first athletic metric change affordance, displaying a user interface configured to change the athletic metric.

In some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, a touch-sensitive surface, and a body activity tracking sensor, comprising: one or more programs They: display a scrollable list of affordances associated with physical activities; displaying a first athletic metric change affordance corresponding to a first affordance in the scrollable list of affordances; to receive user input; upon a determination that a user input is detected at a first affordance in the scrollable list of affordances, initiating a physical activity tracking function associated with the selected first affordance; and a non-transitory computer-readable storage medium comprising instructions for displaying a user interface configured to change an athletic metric in response to a determination that a user input is detected at the first athletic metric change affordance.

In some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, a touch-sensitive surface, and a body activity tracking sensor, wherein the one or more programs : to display a scrollable list of affordances associated with physical activities; displaying a first athletic metric change affordance corresponding to a first affordance in the scrollable list of affordances; to receive user input; upon a determination that a user input is detected at a first affordance in the scrollable list of affordances, initiating a physical activity tracking function associated with the selected first affordance; and in response to a determination that a user input is detected at the first athletic metric change affordance, a transitory computer-readable storage medium comprising instructions for displaying a user interface configured to change an athletic metric.

In some embodiments, an electronic device includes a display; a touch-sensitive surface; body activity tracking sensors; 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 configured to: display a scrollable list of affordances associated with physical activities; displaying a first athletic metric change affordance corresponding to a first affordance in the scrollable list of affordances; to receive user input; upon a determination that a user input is detected at a first affordance in the scrollable list of affordances, initiating a physical activity tracking function associated with the selected first affordance; and in accordance with a determination that a user input is detected at a first athletic metric change affordance, an electronic device comprising instructions for displaying a user interface configured to change an athletic metric is disclosed.

In some embodiments, an electronic device includes a display; a touch-sensitive surface; body activity tracking sensors; means for displaying a scrollable list of affordances associated with physical activities; means for displaying a first athletic metric change affordance corresponding to a first affordance in the scrollable list of affordances; means for receiving user input; means for initiating a physical activity tracking function associated with the selected first affordance upon a determination that user input is detected at a first affordance in the scrollable list of affordances; and means for displaying a user interface configured to change an athletic metric in response to a determination that a user input is detected at the first athletic metric change affordance.

In some embodiments, a method, in an electronic device having a display and a touch-sensitive surface, comprising: displaying a scrollable list of affordances associated with bodily activities while an audio application is playing audio content; while the audio application is playing the audio content, receiving user input at an affordance of the scrollable list of affordances; and in response to receiving user input at the affordance: initiating a physical activity tracking function associated with the selected affordance, and determining whether the workout audio playlist setting is enabled; In accordance with a determination that setting the athletic audio playlist is enabled: stopping playing the audio content on the device, and initiating playing the athletic audio playlist on the device; and upon a determination that the workout audio playlist setting is disabled, continuing to play the audio content on the device.

In some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured for execution by one or more processors of an electronic device having a display and a touch-sensitive surface, wherein the one or more programs: an audio application is an audio while playing content, to display a scrollable list of affordances associated with physical activities; to receive user input at an affordance in the scrollable list of affordances while the audio application is playing audio content; and in response to receiving user input at the affordance: to initiate a physical activity tracking function associated with the selected affordance, and to determine whether the workout audio playlist setting is enabled; Upon a determination that the workout audio playlist setting is enabled: to stop playing the audio content on the device, and to start playing the workout audio playlist on the device; and a non-transitory computer-readable storage medium comprising instructions for continuing to play audio content on the device upon a determination that the athletic audio playlist setting is disabled.

In some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display and a touch-sensitive surface, wherein one or more programs: an audio application is an audio content to display a scrollable list of affordances associated with physical activities while playing; to receive user input at an affordance in the scrollable list of affordances while the audio application is playing audio content; and in response to receiving user input at the affordance: to initiate a physical activity tracking function associated with the selected affordance, and to determine whether the workout audio playlist setting is enabled; Upon a determination that the workout audio playlist setting is enabled: to stop playing the audio content on the device, and to start playing the workout audio playlist on the device; and a transitory computer-readable storage medium comprising instructions for continuing to play the audio content on the device upon a determination that the workout audio playlist setting is disabled.

In some embodiments, an electronic device includes a display; a touch-sensitive surface; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, wherein the one or more programs are configured to: display a scrollable list of affordances associated with bodily activities while the audio application is playing audio content. for; to receive user input at an affordance in the scrollable list of affordances while the audio application is playing audio content; and in response to receiving user input at the affordance: to initiate a physical activity tracking function associated with the selected affordance, and to determine whether the workout audio playlist setting is enabled; Upon a determination that the workout audio playlist setting is enabled: to stop playing the audio content on the device, and to start playing the workout audio playlist on the device; and upon a determination that the workout audio playlist setting is disabled, an electronic device comprising instructions for continuing to play audio content on the device is disclosed.

In some embodiments, an electronic device includes a display; a touch-sensitive surface; means for displaying a scrollable list of affordances associated with physical activities while the audio application is playing audio content; means for receiving user input at an affordance of the scrollable list of affordances while the audio application is playing audio content; and in response to receiving user input at the affordance: means for initiating a physical activity tracking function associated with the selected affordance, and means for determining whether the workout audio playlist setting is enabled; In accordance with a determination that setting the athletic audio playlist is enabled: means for stopping playing the audio content on the device, and means for initiating playing the athletic audio playlist on the device; and means for continuing to play audio content on the device upon a determination that the athletic audio playlist setting is disabled.

In some embodiments, in an electronic device having a display and a touch-sensitive surface, a method comprising: receiving, from an external device, a message; and in accordance with a determination that the message includes athletic information: displaying one or more predefined responses to the received message; receiving user input corresponding to selecting a predefined response from one or more predefined responses; and subsequent to receiving the user input, composing a reply message, the reply message comprising: a selected predefined response; and including athletic information.

In some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display and a touch-sensitive surface, the one or more programs: from an external device, for receiving messages; and in accordance with a determination that the message includes athletic information: to display one or more predefined responses to the received message; for receiving user input corresponding to selecting a predefined response from one or more predefined responses; and subsequent to receiving the user input, to compose a reply message, the reply message comprising: a selected predefined reply; and athletic information - a non-transitory computer-readable storage medium containing instructions is disclosed.

In some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display and a touch-sensitive surface, wherein one or more programs: from an external device, a message for receiving; and in accordance with a determination that the message includes athletic information: to display one or more predefined responses to the received message; for receiving user input corresponding to selecting a predefined response from one or more predefined responses; and subsequent to receiving the user input, to compose a reply message, the reply message comprising: a selected predefined reply; and athletic information - a transitory computer readable storage medium containing instructions is disclosed.

In some embodiments, an electronic device includes a display; a touch-sensitive surface; one or more processors; and a memory storing one or more programs configured to be executed by one or more processors, the one or more programs configured to: receive, from an external device, a message; and in accordance with a determination that the message contains athletic information: to display one or more predefined responses to the received message; for receiving user input corresponding to selecting a predefined response from one or more predefined responses; and subsequent to receiving the user input, to compose a reply message, the reply message comprising: a selected predefined reply; and athletic information - an electronic device comprising instructions is disclosed.

In some embodiments, an electronic device includes a display; a touch-sensitive surface; means for receiving, from an external device, a message; and in accordance with a determination that the message includes athletic information: means for displaying one or more predefined responses to the received message; means for receiving user input corresponding to selecting a predefined response from one or more predefined responses; and, subsequent to receiving the user input, means for composing a reply message, wherein the reply message comprises a selected predefined reply; and including athletic information.

In some embodiments, a method, in an electronic device having a display, a touch-sensitive surface, and a body activity tracking sensor: displaying a scrollable list of affordances associated with heart rate information, wherein the scrollable list of affordances: first as an affordance, the first affordance identifying a first physical activity and first heart rate information associated with the first physical activity and measured by the physical activity tracking sensor; and a second affordance that identifies a second physical activity and second heart rate information associated with the second physical activity, different from the first heart rate information, and measured by the physical activity tracking sensor. Ham -; receiving user input; displaying additional first heart rate information according to a determination that the user input corresponds to the first affordance; and according to a determination that the user input corresponds to the second affordance, displaying additional second heart rate information different from the additional first heart rate information.

In some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, a touch-sensitive surface, and a body activity tracking sensor, comprising: one or more programs are: to display a scrollable list of affordances associated with heart rate information, wherein the scrollable list of affordances is: a first affordance, a first physical activity, and associated with the first physical activity, measured by the body activity tracking sensor. a first affordance, identifying first heart rate information; and a second affordance that identifies a second physical activity and second heart rate information associated with the second physical activity, different from the first heart rate information, and measured by the physical activity tracking sensor. Ham -; to receive user input; displaying additional first heart rate information according to a determination that the user input corresponds to the first affordance; And according to a determination that the user input corresponds to the second affordance, a non-transitory computer-readable storage medium including instructions for displaying additional second heart rate information different from the additional first heart rate information is disclosed.

In some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, a touch-sensitive surface, and a body activity tracking sensor, wherein the one or more programs : to display a scrollable list of affordances associated with heart rate information, wherein the scrollable list of affordances is: a first affordance, a first physical activity, and a first physical activity associated with the first physical activity and measured by the body activity tracking sensor. 1 first affordance, identifying heart rate information; and a second affordance that identifies a second physical activity and second heart rate information associated with the second physical activity, different from the first heart rate information, and measured by the physical activity tracking sensor. Ham -; to receive user input; displaying additional first heart rate information according to a determination that the user input corresponds to the first affordance; And according to a determination that the user input corresponds to the second affordance, a transitory computer-readable storage medium including instructions for displaying additional second heart rate information different from the additional first heart rate information is disclosed.

In some embodiments, an electronic device may include a display; a touch-sensitive surface; body activity tracking sensors; 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: for displaying a scrollable list of affordances associated with heart rate information, the scrollable list of affordances comprising: a first affordance that identifies a first physical activity and first heart rate information associated with the first physical activity and measured by the physical activity tracking sensor; and a second affordance that identifies a second physical activity and second heart rate information associated with the second physical activity, different from the first heart rate information, and measured by the physical activity tracking sensor. Ham -; to receive user input; displaying additional first heart rate information according to a determination that the user input corresponds to the first affordance; And according to a determination that the user input corresponds to the second affordance, an electronic device comprising instructions for displaying additional second heart rate information different from the additional first heart rate information is disclosed.

In some embodiments, an electronic device may include a display; a touch-sensitive surface; body activity tracking sensors; Means for displaying a scrollable list of affordances associated with heart rate information, the scrollable list of affordances comprising: a first affordance, a first physical activity, and a first physical activity associated with the first physical activity and measured by the body activity tracking sensor. 1 A first affordance, identifying heart rate information; and a second affordance that identifies a second physical activity and second heart rate information associated with the second physical activity, different from the first heart rate information, and measured by the physical activity tracking sensor. Ham -; means for receiving user input; means for displaying additional first heart rate information upon a determination that the user input corresponds to the first affordance; and means for displaying additional second heart rate information different from the additional first heart rate information in accordance with a determination that the user input corresponds to the second affordance.

In some embodiments, a method is provided in an electronic device having a display, a touch-sensitive surface, and a body activity tracking sensor: while tracking heart rate data corresponding to data received from the body activity tracking sensor: the heart rate data is a heart rate alert. determining whether a criterion is satisfied; According to determining that the heart rate data satisfies the heart rate warning criterion: displaying a heart rate warning affordance; receiving a user input corresponding to a heart rate warning affordance; and subsequent to receiving a user input corresponding to the heart rate warning affordance, causing display of a graph comprising heart rate data that meets the heart rate warning criterion over a period of time; and upon determining that the heart rate data does not satisfy the heart rate warning criteria, withholding from causing display of the heart rate warning affordance.

In some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, a touch-sensitive surface, a body activity tracking sensor, and the one or more programs. , one or more programs: while tracking heart rate data corresponding to data received from the body activity tracking sensor: to determine whether the heart rate data satisfies a heart rate warning criterion; Upon determining that the heart rate data satisfies the heart rate warning criterion: to display a heart rate warning affordance; to receive user input corresponding to a heart rate warning affordance; and subsequent to receiving the user input corresponding to the heart rate warning affordance, to cause display of a graph comprising heart rate data that meets the heart rate warning criterion over a period of time; and a non-transitory computer-readable storage medium comprising instructions for suspending causing display of a heart rate warning affordance upon a determination that the heart rate data does not satisfy a heart rate warning criterion.

In some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, a touch-sensitive surface, a body activity tracking sensor, and the one or more programs, comprising: One or more programs may: while tracking heart rate data corresponding to data received from the body activity tracking sensor: to determine whether the heart rate data satisfies heart rate warning criteria; Upon determining that the heart rate data satisfies the heart rate warning criterion: to display a heart rate warning affordance; to receive user input corresponding to a heart rate warning affordance; and subsequent to receiving the user input corresponding to the heart rate warning affordance, to cause display of a graph comprising heart rate data that meets the heart rate warning criterion over a period of time; and withholding instructions from causing display of the heart rate warning affordance upon a determination that the heart rate data does not satisfy the heart rate warning criteria.

In some embodiments, an electronic device includes a display; a touch-sensitive surface; body activity tracking sensors; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, wherein the one or more programs: while tracking heart rate data corresponding to data received from the physical activity tracking sensor: the heart rate data is for determining whether a heart rate warning criterion is satisfied; Upon determining that the heart rate data satisfies the heart rate warning criterion: to display a heart rate warning affordance; to receive user input corresponding to a heart rate warning affordance; and subsequent to receiving the user input corresponding to the heart rate warning affordance, to cause display of a graph comprising heart rate data that meets the heart rate warning criterion over a period of time; and upon determining that the heart rate data does not satisfy a heart rate warning criterion, an electronic device comprising instructions for withholding from causing display of a heart rate warning affordance is disclosed.

In some embodiments, an electronic device may include a display; a touch-sensitive surface; body activity tracking sensors; while tracking heart rate data corresponding to data received from the body activity tracking sensor: means for determining whether the heart rate data satisfies a heart rate warning criterion; upon determining that the heart rate data satisfies the heart rate warning criterion: means for displaying a heart rate warning affordance; means for receiving user input corresponding to a heart rate warning affordance; and, subsequent to receiving a user input corresponding to the heart rate warning affordance, means for causing display of a graph comprising heart rate data that meets the heart rate warning criterion over a period of time; and means for suspending causing display of a heart rate warning affordance upon a determination that the heart rate data does not satisfy a heart rate warning criterion.

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

Accordingly, devices are provided with faster and more efficient methods and interfaces for displaying interfaces associated with bodily activity, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may complement or replace other methods for displaying affordances associated with physical activity.

For a better understanding of the various described embodiments, reference should be made to the specific details for carrying out the invention in connection with the following drawings, where like reference numerals indicate corresponding parts throughout the drawings.
1A is a block diagram illustrating a portable multifunction device having a touch-sensitive display, in accordance with some embodiments.
1B is a block diagram illustrating example components for event handling, in accordance with some embodiments.
2 shows a portable multifunction device with a touch screen, in accordance with some embodiments.
3 is a block diagram of an example multifunction device having a display and a touch-sensitive surface, in accordance with some embodiments.
4A shows an example user interface for a menu of applications on a portable multifunction device, in accordance with some embodiments.
4B depicts an example user interface for a multifunction device having a touch-sensitive surface separate from a display, in accordance with some embodiments.
5A illustrates a personal electronic device in accordance with some embodiments.
5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.
5C and 5D show example components of a personal electronic device with a touch-sensitive display and intensity sensors, in accordance with some embodiments.
5E-5H depict example components and user interfaces of a personal electronic device, in accordance with some embodiments.
6A-6B depict example user interfaces in accordance with some embodiments.
7 is a flow diagram illustrating a method for operating an electronic device, in accordance with some embodiments.
8A-8T show example user interfaces in accordance with some embodiments.
9 is a flow diagram illustrating a method for operating an electronic device, in accordance with some embodiments.
10A-10N depict example user interfaces in accordance with some embodiments.
11 is a flow diagram illustrating a method for operating an electronic device, in accordance with some embodiments.
12A-12M show example user interfaces in accordance with some embodiments.
13 is a flow diagram illustrating a method for operating an electronic device, in accordance with some embodiments.
14A-14O show example user interfaces in accordance with some embodiments.
15 is a flow diagram illustrating a method for operating an electronic device, in accordance with some embodiments.

The following description sets forth exemplary methods, parameters, and the like. However, it should be recognized that this description is not intended as a limitation on the scope of the present disclosure but instead is provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methods and interfaces for displaying affordances associated with bodily activity. Such techniques can reduce the cognitive burden on a user accessing affordances associated with physical activity, thereby improving productivity. Additionally, such techniques may reduce processor and battery power that would otherwise be wasted on excessive user inputs.

Hereinafter, FIGS. 1A and 1B, 2, 3, 4A and 4B, and 5A-5H provide a description of example devices for performing techniques for managing event notifications. 6A-6BH depict example user interfaces for displaying affordances associated with physical activity. 7 is a flow diagram illustrating methods of displaying affordances associated with physical activity, in accordance with some embodiments. The user interfaces of FIGS. 6A-6BH are used to illustrate the processes described below, including those of FIG. 7 .

8A-8T depict example user interfaces for continuing or not playing a currently playing song in response to selecting an exercise. 9 is a flow diagram illustrating a method of continuing or not continuing to play a currently playing song in response to selecting an exercise, in accordance with some embodiments. The user interfaces of FIGS. 8A-8T are used to illustrate the processes described below, including those of FIG. 9 .

10A-10N depict example user interfaces for composing a reply message containing predefined responses and workout information. 11 is a flow diagram illustrating methods of composing a reply message including a predefined response and workout information, in accordance with some embodiments. The user interfaces of FIGS. 10A-10N are used to illustrate the processes described below, including those of FIG. 11 .

12A-12M show example user interfaces for displaying affordances associated with heart rate information. 13 is a flow diagram illustrating methods of displaying affordances associated with heart rate information, in accordance with some embodiments. The user interfaces of FIGS. 12A-12M are used to illustrate the processes described below, including those of FIG. 13 .

14A-14O depict example user interfaces for displaying a heart rate warning. 15 is a flow diagram illustrating methods of displaying a heart rate alert, in accordance with some embodiments. The user interfaces of FIGS. 14A-14O are used to illustrate the processes described below, including those of FIG. 15 .

Although the following description uses terms such as "first", "second", etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various embodiments described. Both the first touch and the second touch are touches, but they are not the same touch.

Terminology used in the description of various described embodiments herein is for the purpose of describing specific embodiments only and is not intended to be limiting. As used in the description of the various described embodiments 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 is intended It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. The terms "include", "including", "comprise", and/or "comprising", when used herein, refer to the stated features, integers specifies the presence of s, steps, operations, elements, and/or components, but the presence of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will further be understood that does not preclude additions.

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

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 without limitation iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, CA. Other portable electronic devices such as laptop or tablet computers having touch-sensitive surfaces (eg, touch screen displays and/or touchpads) are optionally used. It should also be appreciated that in some embodiments, the device is not a portable communication device but a desktop computer with a touch-sensitive surface (eg, a touch screen display and/or touchpad).

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

Devices typically support a variety of applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, website authoring applications, disk authoring applications, spreadsheet applications, gaming applications, telephony applications, video conferencing applications, email application, instant messaging application, workout assistance application, photo management application, digital camera application, digital video camera application, web browsing application, digital music player application, and/or digital video player application.

Various applications running on the device optionally use at least one universal physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface, as well as corresponding information displayed on the device, are optionally adjusted and/or changed from one application to the next and/or within individual applications. In this way, the device's universal physical architecture (such as a touch-sensitive surface) supports a variety of applications, optionally with user interfaces that are intuitive and transparent to the user.

Attention is now directed to embodiments of portable devices having touch-sensitive displays. 1A is a block diagram illustrating a portable multifunction device 100 having a touch-sensitive display system 112, in accordance with some embodiments. Touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and is sometimes 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 includes Device 100 optionally includes one or more optical sensors 164 . Device 100 optionally includes one or more contact intensity sensors to detect the intensity of contacts on device 100 (eg, a touch-sensitive surface such as touch-sensitive display system 112 of device 100). (165). Device 100 is optionally configured to generate tactile outputs on device 100 (e.g., with touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). one or more tactile output generators 167 (for generating tactile outputs on the same touch-sensitive surface). These components optionally communicate via one or more communication buses or signal lines 103 .

As used in the specification and claims, the term “strength” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (eg, finger contact) on a touch-sensitive surface, or touch Refers to a substitute (proxy) for the force or pressure of contact on a sensitive surface. The intensity of the contact has a range of values that includes at least four distinct values and more typically includes hundreds (eg, at least 256) distinct values. The strength of the contact is selectively determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors under or near the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (eg, a weighted average) to determine an estimated force of contact. Similarly, the pressure-sensitive tip of the stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and/or changes thereto of a contact area detected on the touch-sensitive surface, the capacitance of the touch-sensitive surface in the vicinity of the contact and/or changes thereto, and/or the touch-sensitive surface in the vicinity of the contact. The resistance of and/or changes thereto are optionally used as a substitute for the force or pressure of contact on the touch-sensitive surface. In some implementations, alternate measurements of contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (eg, the intensity threshold is described in units corresponding to the alternate measurements). In some implementations, alternate measurements of contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., an intensity threshold is the pressure threshold measured in units of pressure). Using the intensity of a touch as an attribute of user input may otherwise display affordances (e.g., on a touch-sensitive display) and/or (e.g., a touch-sensitive display, a touch-sensitive surface, or Enables user access to additional device functions that may not be accessible by the user on reduced-size devices with limited real-area to receive user input (via physical/mechanical controls such as knobs or buttons) let it

As used in the specification and claims, the term “tactile output” refers to the physical displacement of a device relative to its previous location, a component of the device relative to another component of the device (eg, a housing) (eg, a touch-sensitive output). surface), or the displacement of a component relative to the center of mass of the device to be detected by the user using the user's sense of touch. For example, in situations where a device or a component of a device is in contact with a user's touch-sensitive surface (eg, a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement is generated by the user's device or It will be interpreted as a tactile sensation corresponding to a perceived change in the physical properties of a component of a device. For example, movement of a touch-sensitive surface (eg, a touch-sensitive display or trackpad) is optionally interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation, such as a “down click” or “up click,” even in the absence of movement of a physical actuator button associated with a touch-sensitive surface that is physically depressed (e.g., displaced) by the user's movement. . As another example, movement of the touch-sensitive surface is optionally interpreted or perceived by the user as "roughness" of the touch-sensitive surface, even if there is no change in flatness of the touch-sensitive surface. Although these interpretations of touch by a user will be subject to the user's individualized sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "up click", "down click", "roughness"), unless stated otherwise, the tactile output generated is typical (or average) corresponds to a physical displacement of the device or component thereof that will produce the described sensory perception for the user.

Device 100 is only one example of a portable multifunction device, and device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally a component It should be understood that they have different configurations or arrangements of The various components shown in FIG. 1A are 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 (ASICs).

Memory 102 optionally includes high-speed random access memory, and optionally also includes one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. It contains the same non-volatile memory. Memory controller 122 optionally controls access to memory 102 by other components of device 100 .

Peripherals interface 118 may be used to couple the device's input and output peripherals to CPU 120 and memory 102 . One or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions on device 100 and to process data. In some embodiments, peripherals interface 118 , CPU 120 and memory controller 122 are optionally implemented on a single chip, such as chip 104 . In some other embodiments, these are, optionally, implemented on separate chips.

Radio frequency (RF) circuitry 108 receives and transmits RF signals, also referred to as electromagnetic signals. The RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communication networks and other communication devices via the electromagnetic signals. The RF circuitry 108 optionally includes, but is not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and the like. However, it includes well-known circuitry for performing these functions. RF circuitry 108 optionally connects networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet, and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN), and/or a MAN. (metropolitan area network), and communicates with other devices by wireless communication. RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. Optionally, the wireless communication includes Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution (EV-DO), data-only), HSPA, HSPA+, dual-cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA) ), time division multiple access (TDMA), Bluetooth (Bluetooth), Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g. IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging (XMPP) and presence protocol), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS), and/or Short Message Service (SMS), or communications not yet developed at the filing date of this document. protocols, including, but not limited to, any other suitable communication protocol.

The audio circuitry 110 , the speaker 111 , and the microphone 113 provide an audio interface between a user and the device 100 . The audio circuitry 110 receives audio data from the peripheral interface 118, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts electrical signals into sound waves that can be heard by humans. The audio circuit section 110 also receives electrical signals converted from sound waves by the microphone 113 . Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is optionally fetched from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118 . In some embodiments, audio circuitry 110 also includes a headset jack (eg, 212 in FIG. 2 ). The headset jack is the interface between audio circuitry 110 and detachable audio input/output peripherals such as output-only headphones, or headsets that have both an output (eg, one or both ear headphones) and an input (eg, microphone). provide an interface.

I/O subsystem 106 couples input/output peripherals on device 100 , such as touch screen 112 and other input control devices 116 , to peripherals interface 118 . I/O subsystem 106 optionally includes one or more input controllers for display controller 156, light sensor controller 158, intensity sensor controller 159, haptic feedback controller 161 and other input or control devices ( 160). One or more input controllers 160 receive/transmit electrical signals from/to other input control devices 116 . Other input control devices 116 optionally include physical buttons (eg, push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and the like. In some alternative embodiments, input controller(s) 160 is optionally coupled to (or not coupled to) any of a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. not). The one or more buttons (eg, 208 in FIG. 2 ) optionally include an up/down button for controlling the volume of the speaker 111 and/or the microphone 113 . The one or more buttons optionally include a push button (eg, 206 of FIG. 2 ).

A quick press of the push button selectively unlocks the touch screen 112, or initiates processes that selectively use gestures on the touch screen to unlock the device, as of December 23, 2005 As described in U.S. Patent Application Serial No. 11/322,549, filed dated, "Unlocking a Device by Performing Gestures on an Unlock Image" (U.S. Patent No. 7,657,849), which is hereby incorporated herein by reference in its entirety. do. A longer press of the push button (eg, 206) selectively powers device 100 on or off. The functionality of one or more buttons is optionally customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

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

Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (together with any associated modules and/or sets of instructions in memory 102) control (and any movement or interruption of a contact) on touch screen 112. ) and converts the detected contact into interaction with user interface objects (eg, one or more soft keys, icons, web pages or images) displayed on the touch screen 112 . In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to a finger of the user.

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

Optionally, a touch-sensitive display in some embodiments of touch screen 112 is disclosed in U.S. Pat. Nos. 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and/or 6,677,932 (Westerman et al.); and/or multi-touch sensitive touchpads described in US Patent Publication No. 2002/0015024A1, each of which is incorporated herein by reference in its entirety. However, while touch screen 112 displays visual output from device 100, touch-sensitive touchpads do not provide visual output.

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

Touch screen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. A user, optionally, makes contact with the touch screen 112 using any suitable object or appendage, such as a stylus, finger, or the like. In some embodiments, the user interface is designed to operate primarily using finger-based contacts and gestures, which may be less precise than stylus-based input due to the larger contact area of a finger on a touch screen. In some embodiments, the device converts coarse finger-based input into precise pointer/cursor positions or commands for performing actions desired by the user.

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

Device 100 also includes a power system 162 for powering various components. The power system 162 optionally includes a power management system, one or more power sources (eg, a battery, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator ( eg, light emitting diodes (LEDs)), and any other components associated with generating, managing, and distributing power within portable devices.

Device 100 also optionally includes one or more optical sensors 164 . 1A shows a light sensor coupled to light sensor controller 158 in I/O subsystem 106 . Optical sensor 164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor 164 receives light from the environment, projected through one or more lenses, and converts the light into data representing an image. In conjunction with the imaging module 143 (also referred to as a camera module), the light sensor 164 optionally captures still images or video. In some embodiments, an optical sensor is located on the back of device 100, opposite touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for still and/or video image acquisition. let it be In some embodiments, the light sensor is located on the front of the device so that, optionally, an image of the user is obtained for the video conference while the user views other video conference participants on the touch screen display. In some embodiments, the position of the light sensor 164 can be changed by the user (eg, by rotating a lens and sensor within the device housing) so that a single light sensor 164 can videoconferencing and stop and/or or to be used with a touch screen display for both video image acquisition.

Device 100 also optionally includes one or more contact intensity sensors 165 . 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). The contact intensity sensor 165 receives contact intensity information (eg, pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with or proximate to a touch-sensitive surface (eg, touch-sensitive display system 112 ). In some embodiments, at least one contact intensity sensor is located on the back side of device 100 opposite touch screen display 112 located on the front side of device 100 .

Device 100 also optionally includes one or more proximity sensors 166 . 1A shows proximity sensor 166 coupled to peripherals interface 118 . Alternatively, proximity sensor 166 is, optionally, coupled to input controller 160 within I/O subsystem 106. Proximity sensor 166 is optionally described in U.S. patent applications Ser. No. 11/241,839, “Proximity Detector In Handheld Device”; 11/240,788, "Proximity Detector In Handheld Device"; 11/620,702, "Using Ambient Light Sensor To Augment Proximity Sensor Output"; 11/586,862, "Automated Response To And Sensing Of User Activity In Portable Devices"; and 11/638,251, "Methods And Systems For Automatic Configuration Of Peripherals," which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables touch screen 112 when the multifunction device is positioned near the user's ear (eg, when the user is making a phone call).

Device 100 optionally also includes one or more tactile output generators 167 . 1A shows a tactile output generator coupled to a haptic feedback controller 161 in I/O subsystem 106. Tactile output generator 167 is optionally one or more electroacoustic devices such as speakers or other audio components and/or motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating includes electromechanical devices that convert energy into linear motion, such as a component (eg, a component that converts electrical signals into tactile outputs on the device). Contact intensity sensor 165 receives tactile feedback generating instructions from haptic feedback module 133 and produces tactile outputs on device 100 that can be sensed by a user of device 100 . In some embodiments, the at least one tactile output generator is co-located with or proximate to a touch-sensitive surface (eg, touch-sensitive display system 112), optionally perpendicular to (eg, touch-sensitive display system 112) the touch-sensitive surface. , into/out the surface of the device 100) or laterally (eg, back and forth in the same plane as the surface of the device 100) to produce a tactile output. In some embodiments, at least one tactile output generator sensor is located on the back side of device 100 opposite touch screen display 112 located on the front side of device 100 .

Device 100 also optionally includes one or more accelerometers 168 . 1A shows accelerometer 168 coupled to peripherals interface 118 . Alternatively, accelerometer 168 is optionally coupled to input controller 160 within I/O subsystem 106. Accelerometer 168, optionally, is provided in US Patent Publication No. 20050190059, "Acceleration-based Theft Detection System for Portable Electronic Devices" and US 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 entirety. In some embodiments, information is displayed in a portrait view or landscape view on a touch screen display based on analysis of data received from one or more accelerometers. Device 100 optionally includes, in addition to accelerometer(s) 168, a magnetometer (not shown), and a GPS (eg, portrait or landscape) to obtain information regarding the position and orientation (eg, portrait or landscape) of device 100. or a GLONASS or other global navigation system) receiver (not shown).

In some embodiments, software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module ( or set of instructions) 132, text input module (or set of instructions) 134, GPS module (or set of instructions) 135, and applications (or sets of instructions) 136. . Additionally, in some embodiments, memory ( 102 in FIG. 1A or 370 in FIG. 3 ) stores device/global internal state 157 as shown in FIGS. 1A and 3 . The device/global internal state 157 includes an active application state, if any, indicating which applications are currently active; display state, which indicates which applications, views, or other information occupy various areas of the touch screen display 112; sensor status, including information obtained from the device's various sensors and input control devices 116; and location information regarding the position and/or attitude of the device.

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

The communication module 128 enables communication with other devices through one or more external ports 124 and also various other functions for processing data received by the RE circuitry 108 and/or external ports 124. contains software components. External port 124 (eg, USB, FIREWIRE, etc.) is configured to couple to other devices either directly or indirectly over a network (eg, Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (eg, 30-pin) connector that is the same as, similar to, and/or compatible with the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (eg, a touchpad or physical click wheel). . The contact/motion module 130 determines whether a contact has occurred (eg, detecting a finger-down event), the intensity of the contact (eg, the force or pressure of the contact, or a substitute for force or pressure of the contact), determining whether there is movement of the contact to track movement across the touch-sensitive surface (e.g., one or more finger-dragging events). ), and determining whether contact has ceased (e.g., detecting a finger-up event or contact cessation). It includes various software components to perform. Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact represented by the series of contact data optionally determines speed (magnitude), speed (magnitude and direction), and/or acceleration (change in magnitude and/or direction) of the contact point. includes doing These actions are optionally applied to single contacts (eg, one finger contacts) or to multiple simultaneous contacts (eg, “multi-touch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on the touchpad.

In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an action was performed by the user (e.g., whether the user “clicked” on an icon). judged). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., intensity thresholds are not determined by activation thresholds of specific physical actuators, and changing the physical hardware of device 100 may can be adjusted without). For example, the mouse “click” threshold of a trackpad or touch screen display can be set to any of a wide range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device may (eg, by adjusting individual intensity thresholds and/or adjusting multiple intensity thresholds all at once with a system-level click "intensity" parameter) one of a set of intensity thresholds. You are provided with software settings to adjust for the anomaly.

The contact/motion module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (eg, different motions, timings, and/or intensities of detected contacts). Thus, the gesture is optionally detected by detecting a specific contact pattern. For example, detecting a finger tap gesture involves detecting a finger-down event followed by a finger-down event at the same location (or substantially the same location) as the finger-down event (e.g., at the location of an icon). and detecting an up (liftoff) event. As another example, detecting a finger swipe gesture on a touch-sensitive surface detects a finger-down event followed by one or more finger-dragging events, followed by a finger-up (liftoff). ) to detect events.

Graphics module 132 renders and renders graphics on touch screen 112 or other display, including components for changing the visual effect (eg, brightness, transparency, saturation, contrast, or other visual properties) of displayed graphics. It includes various known software components for display. As used herein, the term “graphics” includes without limitation text, web pages, icons (eg, user interface objects including soft keys), digital images, videos, animations, and the like. , includes any object that can be displayed to the user.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. Graphics module 132 receives one or more codes from applications or the like that specify graphics to be displayed, along with coordinate data and other graphic property data, if necessary, and then generates screen image data to display controller 156. print out

Haptic feedback module 133 is used by tactile output generator(s) 167 to generate tactile outputs at one or more locations on device 100 in response to user interactions with device 100. It includes various software components for generating instructions.

Text input module 134, which is optionally a component of graphics module 132, is used for various applications (e.g., Contacts 137, Email 140, IM 141, Browser 147, and other applications requiring text input). Provides soft keyboards for entering text in any other application).

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). to; and to applications providing location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:

연락처 모듈(137)(때때로 주소록 또는 연락처 목록으로 지칭됨);

Contacts module 137 (sometimes referred to as an address book or contact list);

telephony module 138;

video conferencing module 139;

email client module 140;

instant messaging (IM) module 141;

exercise support module 142;

camera module 143 for still and/or video images;

image management module 144;

video player module;

music player module;

browser module 147;

calendar module 148;

Optionally, weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other information obtained by the user. widget modules 149 including widgets as well as one or more of user-created widgets 149-6;

widget creator module 150 for creating user-created widgets 149-6;

search module 151;

a video and music player module 152 incorporating a video player module and a music player module;

memo module 153;

map module 154; and/or

Online video module (155).

Examples of other applications 136 optionally stored within memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, cryptography, digital rights, etc. It includes management, voice recognition and voice replication.

Along with touch screen 112, display controller 156, contact/motion module 130, graphics module 132 and text input module 134, contacts module 137 optionally includes an address book or contact list ( eg stored in memory 102 or in application internal state 192 of contacts module 137 in memory 370): this includes: adding name(s) to address book thing; deleting name(s) from the address book; associating phone number(s), email address(es), physical address(es) or other information with a name; associating an image with a name; sorting and sorting names; providing phone numbers or email addresses to initiate and/or facilitate communication by phone 138, video conferencing module 139, email 140 or IM 141; and the like.

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 In conjunction with input module 134, phone module 138 optionally inputs a sequence of characters corresponding to the phone number, accesses one or more phone numbers in contacts module 137, and modifies the phone number entered. It is used to dial individual phone numbers, have conversations, and disconnect or hang up when conversations are complete. As noted above, wireless communication optionally uses any of a plurality of communication standards, protocols, and technologies.

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 Together with the module 130, the graphics module 132, the text input module 134, the contacts module 137 and the phone module 138, the video conferencing module 139 interacts with the user and one or more other people according to user instructions. It includes executable instructions to initiate, initiate, and end a video conference between participants.

Along with the RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132 and text input module 134, the email client module 140 provides user instructions. It includes executable instructions that allow you to compose, send, receive, and manage emails in response to emails. In conjunction with the image management module 144, the email client module 140 makes it very easy to create and send emails with still or video images taken with the camera module 143.

Along with the RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132 and text input module 134, the instant messaging module 141, Enter a sequence of characters corresponding to a message, modify previously entered characters, (e.g. Short Message Service (SMS) or Multimedia Message Service for telephone-based instant messages) . . In some embodiments, instant messages sent and/or received optionally include graphics, pictures, audio files, video files, and/or other attachments as supported by MMS and/or Enhanced Messaging Service (EMS). do. As used herein, “instant messaging” refers to phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS). ) refers to both.

RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154 , and the music player module, the workout support module 142 devises workouts (eg, with time, distance, and/or calorie expenditure goals); communicate with motion sensors (sports devices); receive motion sensor data; calibrate sensors used to monitor exercise; select and play music for exercise; It contains executable instructions that cause the display, storage and transmission of athletic data.

along 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 , the camera module 143 captures still images or video (including a video stream) and stores them in the memory 102, modifies the characteristics of the still image or video, or stores a still image or video from the memory 102; Contains executable instructions that cause the video to be deleted.

Together with the touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134 and camera module 143, the image management module 144 is stationary and /or include executable instructions that cause video images to be arranged, modified (eg edited) or otherwise manipulated, labeled, deleted, presented (eg in a digital slideshow or album), and stored .

Together with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132 and text input module 134, browser module 147, web page Executable instructions for browsing the Internet according to user instructions, including retrieving, linking to, receiving, and displaying attachments and other files linked to web pages, as well as attachments and other files linked to web pages or portions thereof. include them

RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, email client module 140, and browser module ( 147), the calendar module 148 is executable to create, display, modify, and store calendars and data associated with calendars (eg, calendar entries, to-do lists, etc.) according to user instructions. contains commands.

Widget modules, along with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134 and browser module 147 149 is selectively downloaded and used by the user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary) widget 149-5), or user-created (eg, user-created widget 149-6) mini-applications. 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 (eg, Yahoo! widgets).

Widget generator module, together with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134 and browser module 147 150 is optionally used to create widgets by the user (eg, change a user-specified portion of a web page into a widget).

Together with the touch screen 112, display controller 156, contact/motion module 130, graphics module 132 and text input module 134, the search module 151 is configured according to user instructions to one or more search criteria. (e.g., one or more user-specific search terms) to search for text, music, sound, image, video, and/or other files in memory 102 that match search terms.

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

Together with the touch screen 112, display controller 156, contact/motion module 130, graphics module 132 and text input module 134, the memo module 153 takes notes, writes and writes notes according to user instructions. Includes executable instructions that allow creating and managing to-do lists and the like.

RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147 ), along with maps module 154, optionally according to user instructions, maps and data associated with the maps (eg, driving directions; data relating to stores and other points of interest in or near a particular location; and other location-based data), display, modify, and store.

Touch screen 112, display controller 156, contact/motion module 130, graphic module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, Together with email client module 140 and browser module 147, online video module 155 allows a user to access online videos in one or more file formats, such as H.264, browse them, (e.g., stream and Receive (by download), play (e.g., on a touch screen or on an external connected display via external port 124), email with a link to a particular online video, and otherwise manage contains commands that In some embodiments, instant messaging module 141 rather than email client module 140 is used to send a link to a particular online video. Additional descriptions of online video applications can be found in U.S. Provisional Patent Application Serial No. 60/936,562, filed Jun. 20, 2007, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos" and Dec. 31, 2007. See U.S. Patent Application Serial No. 11/968,067, filed dated, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," the contents of which are hereby incorporated by reference in their entirety. .

Each of the above-identified modules and applications are executable instructions for performing one or more of the functions described above and methods described herein (eg, computer implemented methods and other information processing methods described herein). corresponds to a set of These modules (eg, sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise reproduced in various embodiments. are arranged For example, the video player module is optionally combined with the music player module into a single module (eg, video and music player module 152 of FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Memory 102 also optionally stores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively via a touch screen and/or touchpad. By using a touch screen and/or touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, etc.) on device 100 is optionally reduced.

A predefined set of functions performed entirely via the touch screen and/or touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 to a main, home or root menu. In these embodiments, the "menu button" is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.

1B is a block diagram illustrating example components for event handling, in accordance with some embodiments. In some embodiments, memory ( 102 in FIG. 1A or 370 in FIG. 3 ) is used to store event sorter 170 (eg, in operating system 126 ) and individual applications 136 - 1 (eg, the applications described above). (any of 137-151, 155, 380-390).

The event sorter 170 receives the event information and determines the application 136-1 to which the event information is to be passed, and the application view 191 of the application 136-1. Event sorter 170 includes event monitor 171 and event dispatcher module 174 . In some embodiments, application 136-1 includes application internal state 192 indicating the current application view(s) 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) are currently active, and application internal state 192 is used by event sorter 170 It is used to determine the application views 191 to deliver event information by.

In some embodiments, application internal state 192 indicates user resume information to be used when application 136-1 resumes execution, information being displayed by application 136-1 or ready to be displayed. interface state information, a state queue to allow the user to return to a previous state or view of application 136-1, and redo/undo previous actions taken by the user Contains additional information such as one or more of the queues.

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

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 (eg, receiving an input that exceeds a predetermined noise threshold and/or for more than a predetermined duration). .

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

Hit view determination module 172 provides software procedures for determining where a sub-event occurred within one or more views when touch-sensitive display 112 displays more than one view. Views consist of controls and other elements that a user can see on a display.

Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, where information is displayed and touch-based gestures occur. The application views (of an individual application) on which a touch is detected optionally correspond to program levels within the program or view hierarchy of the application. For example, the lowest level view in which a touch is detected is optionally referred to as a hit view, and the set of events recognized as pertinent inputs are optionally determined based at least in part on the hit view of the initial touch initiating the touch-based gesture. do.

Hit view determination module 172 receives information related to sub-events of a touch-based gesture. If an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy for which the sub-event should be processed. In most situations, a hit view is the lowest level view in which an initiating subevent (eg, a first subevent in a sequence of subevents forming an event or potential event) occurs. Once a hit view is identified by the hit view determination module 172, the hit view typically receives all subevents related to the same touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively involved views, and therefore all actively involved views are specific to the sub-event. Determines that the sequence should be received. In other embodiments, even if touch sub-events are restricted entirely to the region associated with one particular view, higher views in the hierarchy will still remain as actively participating views.

Event dispatcher module 174 dispatches event information to an event recognizer (eg, event recognizer 180). In embodiments that include active event recognizer determination module 173 , event dispatcher module 174 passes event information to the event recognizer determined by active event recognizer determination module 173 . In some embodiments, event dispatcher module 174 stores event information in an event queue, which event information is retrieved by individual event receivers 182.

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

In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which touch events occur within a respective view of the user interface of the application. contains instructions for processing them. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, an individual application view 191 includes a plurality of event recognizers 180 . In other embodiments, one or more of event recognizers 180 is part of a separate module, such as a user interface kit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. am. In some embodiments, an individual event handler 190 is one of data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. contains more than Event handler 190 optionally uses or calls data updater 176 , object updater 177 , or GUI updater 178 to update application internal state 192 . Alternatively, one or more of the application views 191 include one or more respective event handlers 190 . Also, in some embodiments, one or more of data updater 176 , object updater 177 , and GUI updater 178 are included within a respective application view 191 .

Individual event recognizer 180 receives event information (eg, event data 179 ) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184 . In some embodiments, event recognizer 180 also includes at least metadata 183 and a subset of event delivery instructions 188 (optionally including subevent delivery instructions).

Event receiver 182 receives event information from event classifier 170 . The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information such as the location of the sub-event. If the sub-event is related to the motion of the touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (eg, from portrait to landscape orientation, or vice versa), the event information being the device's current orientation (also referred to as device posture). It contains corresponding information about

Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines the event or sub-event, or determines or updates the status of the event or sub-event. In some embodiments, event comparator 184 includes event definitions 186 . Event definitions 186 include definitions of events (eg, predefined sequences of sub-events), eg, event 1 187-1, event 2 187-2, and the like. In some embodiments, sub-events within event 187 include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. A double tap may be, for example, a first touch on a displayed object during a pre-determined phase (touch start), a first lift-off during a pre-determined phase (touch end), a displayed object during a pre-determined phase a second touch on (touch start), and a second liftoff (touch end) during a predetermined phase. In another example, the definition for event 2 (187-2) is dragging on a displayed object. Dragging includes, for example, a touch (or contact) on a displayed object during a predetermined phase, movement of the touch across the touch-sensitive display 112 , and lift-off (touch end) of the touch. In some embodiments, an event also includes information about one or more associated event handlers 190 .

In some embodiments, event definition 187 includes a definition of an event for a respective user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a subevent. For example, in an application view in which three user interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 determines three user interface objects. A hit test is performed to determine which of them is associated with a touch (subevent). If each displayed object is associated with an individual event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the object and subevent that triggers the hit test.

In some embodiments, the definition for each event 187 also includes a delayed delivery delay that delays delivery of the event information until after it has been determined whether the sequence of sub-events corresponds to or does not correspond to the event type of the event recognizer. contains actions.

If individual event recognizer 180 determines that the series of sub-events does not match any of the events in event definitions 186, then individual event recognizer 180 determines whether event disabled, event failed, or The event end state is entered, after which the respective event recognizer ignores subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

In some embodiments, individual event recognizers 180 may include configurable properties, flags, and/or lists that indicate how the event delivery system should perform subevent delivery for actively participating event recognizers. It includes metadata 183 with In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact with, or come to interact with, each other. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether subevents are passed to various levels in a view or program hierarchy.

In some embodiments, an individual event recognizer 180 activates an event handler 190 associated with an event when one or more specific sub-events of the event are recognized. In some embodiments, individual event recognizer 180 passes event information associated with the event to event handler 190 . Activating the event handler 190 is separate from sending (and deferred sending) subevents to individual hit views. In some embodiments, event recognizer 180 sends a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include subevent delivery instructions that deliver event information about a subevent without activating an event handler. Instead, subevent delivery instructions deliver event information to event handlers or actively participating views associated with a series of subevents. Event handlers associated with a series of sub-events or actively participating views receive event information and perform a predetermined process.

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

In some embodiments, event handler(s) 190 includes or accesses 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 within 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.

The foregoing discussion regarding event handling of user touches on a touch-sensitive display also applies to other forms of user inputs for operating multifunction devices 100 having input devices, but all of which are initiated on touch screens. You have to understand that it is not For example, single or multiple keyboard presses or holds and optionally coordinated mouse movements and mouse button presses; contact movements on a touchpad, such as tap, drag, scroll, etc.; pen stylus inputs; movement of the device; verbal commands; detected eye movements; biometric inputs; and/or any combination thereof is optionally used as inputs corresponding to sub-events defining the event to be recognized.

2 shows a portable multifunction device 100 having a touch screen 112, in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI) 200 . In this embodiment, as well as other embodiments described below, the user may use, for example, one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). It is possible to select one or more of the graphics by making a gesture on the graphics using (not shown). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture is, optionally, one or more taps of a finger in contact with device 100, one or more (left to right, right to left, up and/or down) swipes, and/or rolling (right to left, left to right, up and/or down). In some implementations or situations, a graphic is not selected if it is inadvertently touched. For example, when the gesture corresponding to selection is a tap, a swipe gesture to sweep over an application icon optionally does not select the corresponding application.

Device 100 also optionally includes one or more physical buttons, such as a “home” or menu button 204 . As discussed above, menu button 204 is used to navigate to any application 136 in the set of applications that are optionally running on device 100 . Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering on/off and locking the device, volume control button(s) 208 , a subscriber identity module (SIM) card slot 210 , a headset jack 212 , and a docking/charging external port 124 . The push button 206 optionally powers on/off the device by depressing the button and holding the button depressed for a predefined time interval; lock the device by pressing and releasing the button before a predefined time interval has elapsed; Used to unlock the device or initiate the unlocking process. In an alternative embodiment, device 100 also accepts verbal input for activating or deactivating some functions via microphone 113 . Device 100 also optionally includes one or more contact intensity sensors 165 to detect intensity of contacts on touch screen 112 and/or to generate tactile outputs for a user of device 100. one or more tactile output generators 167 for

3 is a block diagram of an example multifunction device having a display and a touch-sensitive surface, in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home or industrial controller). )am. 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 for interconnecting these components. s 320. Communication buses 320 optionally include circuitry (sometimes referred to as a chipset) that interconnects system components and controls communications between them. Device 300 includes an input/output (I/O) interface 330 that includes a display 340, which is typically a touch screen display. I/O interface 330 also optionally includes keyboard and/or mouse (or other pointing device) 350 and touchpad 355, tactile output for generating tactile outputs on device 300. generator 357 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A), and sensors 359 (e.g., light sensor, acceleration sensor, proximity sensor, touch-sensitive sensor, and/or a contact intensity sensor 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; 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 includes programs, modules, and data structures similar to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). , or a subset thereof. Memory 370 also optionally stores additional programs, modules and data structures that are not present in memory 102 of portable multifunction device 100. For example, the memory 370 of the device 300 optionally includes a drawing module 380, a presentation module 382, a word processing module 384, a website authoring module 386, and a disk authoring module 388. ), and/or spreadsheet module 390, whereas memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store such modules.

Each of the previously identified elements in FIG. 3 is, optionally, stored in one or more of the aforementioned memory devices. Each of the previously identified modules corresponds to a set of instructions for performing the function described above. The above-identified modules or programs (eg, 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 else rearranged. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Memory 370 also optionally stores additional modules and data structures not described above.

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

4A shows an example user interface for a menu of applications on portable multifunction device 100, in accordance with some embodiments. Similar user interfaces are optionally implemented on device 300 . 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;

battery status indicator 406;

A tray 408 with icons for frequently used applications, such as:

o icon 416 for telephony module 138 labeled “Phone” which optionally includes an indicator 414 of the number of missed calls or voicemail messages;

o Optionally, an icon 418 for the email client module 140 labeled “Mail” that includes an indicator 410 of the number of unread emails;

o Icon 420 for browser module 147 labeled “Browser”; and

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

Icons for other applications, such as:

o icon 424 for IM module 141 labeled “Messages”;

o icon 426 for calendar module 148 labeled “Calendar”;

o icon 428 for image management module 144 labeled “Photos”;

o Icon 430 for camera module 143 labeled “Camera”;

o icon 432 for the online video module 155 labeled “online video”;

o icon 434 for stocks widget 149-2 labeled “Stocks”;

o icon 436 for map module 154 labeled “Map”;

o icon 438 for weather widget 149-1 labeled “Weather”;

o icon 440 for alarm clock widget 149-4 labeled “Clock”;

o icon 442 for athletic support module 142 labeled “exercise support”;

o icon 444 for notes module 153 labeled “Notes”; and

o Icon 446 for a Settings application or module, labeled “Settings”, providing access to settings for device 100 and its various applications 136.

It should be noted that the icon labels shown in FIG. 4A are exemplary only. For example, the icon 422 for the video and music player module 152 is labeled “Music” or “Music Player”. Other labels are optionally used for various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label for a particular application icon is separate from the name of the application corresponding to the particular application icon.

FIG. 4B shows a device (eg, in FIG. 3 ) having a touch-sensitive surface 451 (eg, tablet or touchpad 355 in FIG. 3 ) that is separate from display 450 (eg, touch screen display 112 ). An exemplary user interface on device 300 is shown. Device 300 also optionally includes one or more contact intensity sensors (eg, one or more of sensors 359 ) and/or device 300 to detect intensity of contacts on touch-sensitive surface 451 . ) includes one or more tactile output generators 357 for generating tactile outputs for the user.

Although some of the examples that follow will be provided with reference to inputs on a touch screen display 112 (where the touch-sensitive surface and display are combined), in some embodiments, the device may operate separately from the display, as shown in FIG. 4B . Detect inputs on the personal touch-sensitive surface. In some embodiments, a touch-sensitive surface (eg, 451 in FIG. 4B ) has a major axis (eg, 452 in FIG. 4B ) that corresponds to a major axis (eg, 453 in FIG. 4B ) on a display (eg, 450 ). According to these embodiments, the device may interact with the touch-sensitive surface 451 at locations corresponding to the respective locations on the display (eg, 460 corresponds to 468 and 462 corresponds to 470 in FIG. 4B ). Detect contacts (eg, 460 and 462 in FIG. 4B). In this way, user inputs (eg, contacts 460 and 462 and their movements) detected by the device on the touch-sensitive surface (eg, 451 in FIG. Used by the device when 1 to manipulate the user interface on the multifunction device's display (eg, 450 in FIG. 4B ). It should be understood that similar methods are, optionally, used for other user interfaces described herein.

Additionally, while the examples below are given primarily with reference to finger inputs (eg, finger contacts, finger tap gestures, finger swipe gestures), in some embodiments, one or more of the finger inputs may be used with other inputs. It should be understood that input from the device is replaced (eg, mouse-based input or stylus input). For example, a swipe gesture is optionally replaced with a mouse click (eg, instead of a contact) and movement of the cursor along the path of the subsequent swipe (eg, instead of movement of the contact). As another example, the tap gesture is optionally replaced with a mouse click while the cursor is positioned over the location of the tap gesture (eg, instead of detecting the contact and then ceasing to detect the contact). Similarly, it should be understood that when multiple user inputs are detected simultaneously, multiple computer mice are selectively used simultaneously, or mouse and finger contacts are selectively used simultaneously.

5A depicts an exemplary personal electronic device 500 . Device 500 includes a body 502 . In some embodiments, device 500 may include some or all of the features described with respect to devices 100 and 300 (eg, FIGS. 1A-4B ). In some embodiments, device 500 has a touch-sensitive display screen 504 (hereinafter, touch screen 504 ). Alternatively or in addition to touch screen 504 , device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) is, optionally, one for detecting the intensity of contacts (eg, touches) being applied. It includes more than one intensity sensor. One or more intensity sensors of touch screen 504 (or touch-sensitive surface) may provide output data representing the intensity of touches. The user interface of device 500 may respond to touches based on the intensity of the touches, meaning that touches of different intensities may invoke different user interface actions on device 500 .

Exemplary techniques for detecting and processing touch intensity are described, for example, in Related Applications: Filed on May 8, 2013 and entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to International Patent Application No. PCT/US2013/040061 (published as WIPO Publication No. WO/2013/169849), "an Application", and filed on November 11, 2013 and entitled "Device, Method, and Graphical User Interface" for Transitioning Between Touch Input to Display Output Relationships", International Patent Application No. PCT/US2013/069483 (published as WIPO Publication No. WO/2014/105276), each of which is incorporated herein by reference in its entirety.

In some embodiments, device 500 has one or more input mechanisms 506, 508. Input mechanisms 506 and 508 (if included) may be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. These attachment mechanisms (if included) allow device 500 to attach to, for example, a hat, glasses, earrings, necklace, shirt, jacket, bracelet, watch strap, chain, pants, belt, shoe, wallet. , so that it can be attached to a backpack, etc. These attachment mechanisms allow device 500 to be worn by a user.

5B depicts an exemplary personal electronic device 500 . In some embodiments, device 500 may include some or all of the components described with respect to FIGS. 1A, 1B, and 3 . Device 500 has a bus 512 operably coupling an I/O section 514 with one or more computer processors 516 and memory 518 . The I/O section 514 can be connected to the display 504 , which can have a touch-sensitive component 522 and, optionally, an intensity sensor 524 (eg, a contact intensity sensor). I/O section 514 also includes communication unit 530 to receive application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. can be connected with Device 500 may include input mechanisms 506 and/or 508 . Input mechanism 506 is, optionally, a rotatable input device or, for example, a depressable and rotatable input device. In some examples, input mechanism 508 is, optionally, a button.

In some examples, input mechanism 508 is, optionally, a microphone. Personal electronic device 500 optionally includes GPS sensor 532, accelerometer 534, orientation sensor 540 (eg, compass), gyroscope 536, motion sensor 538, and/or any of these various sensors, such as combinations, all of which can be operatively connected to the I/O section 514.

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, which may be executed by one or more computer processors 516. When executed, it causes, for example, computer processors to perform the techniques described below, including processes 700, 900, 1100, 1300, and 1500 (FIGS. 7, 9, 11, 13, and 15). can make them perform. A computer readable storage medium can be any medium that can tangibly contain or store computer executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic, optical, and/or semiconductor storage. Examples of such storage include magnetic disks, CD, DVD, or optical disks based on Blu-ray technologies, as well as persistent solid state memory such as flash, solid state drives, and the like. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B and may include other or additional components in many configurations.

As used herein, the term "affordance" refers to a user interaction that is selectively displayed on the display screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A and 5B). Refers to a user-interactive graphical user interface object. For example, each of an image (eg icon), button, and text (eg hyperlink) selectively constitutes an affordance.

As used herein, the term "focus selector" refers to an input element that indicates the current portion of the user interface with which the user is interacting. In some implementations that include a cursor or other location marker, a touch-sensitive surface (eg, FIG. 3 ) while the cursor is over a particular user interface element (eg, a button, window, slider, or other user interface element). When an input (e.g., a press input) is detected on touchpad 355 of FIG. 4 or touch-sensitive surface 451 of FIG. function as Some implementations that include a touch screen display that enable direct interaction with user interface elements on the touch screen display (eg, touch-sensitive display system 112 of FIG. 1A or touch screen 112 of FIG. 4A ) , when an input (eg, a press input by contact) is detected on a touch screen display at the location of a specific user interface element (eg, a button, window, slider, or other user interface element), the specific user interface element is detected The detected contact on the touch screen functions as a “focus selector” to be adjusted according to the received input. In some implementations, focus is shifted to one of the user interfaces without corresponding movement of a cursor or movement of a contact on the touch screen display (eg, by using a tab key or an arrow key to move focus from one button to another). is moved from one area to another area of the user interface; In these implementations, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the particular form the focus selector has, it is generally intended to convey the user's intended interaction with the user interface (e.g., by presenting the device with an element of the user interface that the user wishes to interact with). A user interface element controlled by (or a touch on a touch screen display). For example, the position of a focus selector (eg, cursor, touch, or selection box) over an individual button while a press input is detected on a touch-sensitive surface (eg, a touchpad or touch screen) (on a display of a device) Unlike other user interface elements being shown, it will indicate that the user is about to activate an individual button.

As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, a predefined number of intensity samples, or (e.g., after detecting a contact, before detecting a liftoff of a contact, before or after detecting the start of movement of a contact, A predetermined period of time (e.g., before or after detecting an increase in the intensity of a contact, and/or before or after detecting a decrease in the intensity of a contact) for a predefined event before detecting the end of the contact. 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds). The characteristic intensity of the contact optionally includes a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, and a top 10 percentile value of the intensities of the contact. ), a value of half the maximum value of the intensities of the contact, a value of 90 percent of the maximum value of the intensities of the contact, and the like. In some embodiments, the duration of the contact (eg, when the characteristic intensity is an average of the intensity of the contact over time) is used to determine the characteristic intensity. In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action was performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, as a result of a contact having a characteristic intensity that does not exceed a first threshold, a first action is performed, and as a result of a contact having a characteristic intensity that exceeds the first intensity threshold but does not exceed a second intensity threshold, a second action is performed. An action is performed, and as a result of a contact having a characteristic strength above the second threshold, a third action is performed. In some embodiments, a comparison between a characteristic strength and one or more thresholds is used to determine whether to perform one or more actions (e.g., individual actions), rather than being used to determine whether to perform a first action or a second action. or whether to suspend performing individual operations).

5C illustrates detection of a plurality of contacts 552A through 552E on a touch-sensitive display screen 504 using a plurality of intensity sensors 524A through 524D. 5C further includes intensity diagrams showing current intensity measurements of intensity sensors 524A-524D in terms of intensity units. In this example, the intensity measurements of intensity sensors 524A and 524D are each 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are each 7 intensity units. In some implementations, the total intensity is the sum of the intensity measurements of the plurality of intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned an individual intensity that is a fraction of the total intensity. 5D shows the assignment of total strength to contacts 552A-552E based on their respective distances from center of force 554 . In this example, contacts 552A, 552B, and 552E are each assigned a contact intensity of 8 intensity units of the total intensity, and contacts 552C and 552D are each assigned a contact intensity of 4 intensity units of the total intensity. is assigned More generally, in some implementations, each contact j is assigned an individual intensity Ij that is a fraction of the total intensity A according to a predefined mathematical function Ij = A·(Dj/ΣDi) , where Dj is the distance of each individual contact j to the center of force, and ΣDi is the sum of the distances of all individual contacts to the center of force (e.g. i=1 to last). Operations described with reference to FIGS. 5C and 5D may be performed using an electronic device similar to or identical to device 100 , 300 , or 500 . In some embodiments, a characteristic intensity of a contact is based on one or more intensities of the contact. In some embodiments, intensity sensors are used to determine a single characteristic intensity (eg, a single characteristic intensity of a single contact). It should be noted that the intensity diagrams are not part of the displayed user interface and are included in FIGS. 5C and 5D to assist the reader.

In some embodiments, a portion of a gesture is identified to determine feature strength. For example, the touch-sensitive surface optionally receives successive swipe contacts that transition from a starting location to an ending location, at which point the intensity of the contact increases. In this example, the characteristic strength of the contact at the end location is optionally based on only a portion of successive swipe contacts (eg, only a portion of the swipe contact at the end location) rather than the entire swipe contact. In some embodiments, a smoothing algorithm is optionally applied to the intensities of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally comprises one of an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. contains one or more In some situations, these smoothing algorithms remove narrow spikes or dips in the strengths of the swipe contact to determine the characteristic strength.

The intensity of a contact on the touch-sensitive surface is optionally characterized for 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 will perform actions typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform actions different from those typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, when a contact is detected with a characteristic intensity below a light-press intensity threshold (eg, and above a nominal contact detection intensity threshold below which the contact is no longer detected), the device determines the light-press intensity. Movement of the contact on the touch-sensitive surface will move the focus selector without performing an action associated with the threshold or the deep press intensity threshold. In general, unless otherwise noted, these intensity thresholds are consistent between different sets of user interface drawings.

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 is sometimes referred to as a "light press" input. 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 is sometimes referred to as a "deep press" input. 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 is sometimes 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 is sometimes referred to as detecting liftoff 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.

In some embodiments described herein, one or more operations may detect an individual press input performed with an individual contact (or multiple contacts) or in response to detecting a gesture comprising the individual press input. and wherein the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press input intensity threshold. In some embodiments, the respective action is performed in response to detecting an increase in intensity of the respective contact above a press input intensity threshold (eg, a “down stroke” of the respective press input). In some embodiments, the press input comprises an increase in the intensity of the respective contact above a press input intensity threshold and a subsequent decrease in intensity of the contact below the press input intensity threshold, wherein the respective action is the individual action below the press input intensity threshold. in response to detecting a subsequent decrease in the intensity of the contact (eg, an “up stroke” of an individual press input).

5E-5H show contact 562 from an intensity below the light press intensity threshold (eg, “IT _L ”) of FIG. 5E to an intensity above the deep press intensity threshold (eg, “IT _D ”) of FIG. 5H . It shows detection of a gesture including a press input corresponding to an increase in intensity. On the displayed user interface 570 including the application icons 572A to 572D displayed in the predefined area 574, while the cursor 576 is displayed over the application icon 572B corresponding to App 2, A gesture performed using contact 562 is detected on touch-sensitive surface 560 . In some embodiments, the gesture is detected on touch-sensitive display 504 . Intensity sensors detect the intensity of contacts on touch-sensitive surface 560 . The device determines that the intensity of contact 562 has peaked by exceeding a deep press intensity threshold (eg, “IT _D ”). Contact 562 remains on touch-sensitive surface 560 . In response to detection of the gesture, and following a contact 562 with an intensity exceeding a deep press intensity threshold (e.g., “IT _D ”) during the gesture, reduced scale representations of recently opened documents for App 2 ( 578A-578C) (eg, thumbnails) are displayed, as shown in FIGS. 5F-5H. In some embodiments, the intensity compared to one or more intensity thresholds is a characteristic intensity of the contact. It should be noted that the intensity diagram for contact 562 is not part of the displayed user interface and is included in FIGS. 5E-5H as an aid to the reader.

In some embodiments, the display of representations 578A-578C includes animation. For example, as shown in FIG. 5F, representation 578A is initially displayed adjacent to application icon 572B. As the animation progresses, representation 578A moves up and representation 578B is displayed proximate application icon 572B, as shown in FIG. 5G. Then, as shown in FIG. 5H, representation 578A moves up, representation 578B moves up toward representation 578A, and representation 578C is displayed proximate application icon 572B. Representations 578A-578C form an array over icon 572B. In some embodiments, as shown in FIGS. 5F and 5G , the animation progresses according to the intensity of contact 562, where the intensity of contact 562 exceeds a deep press intensity threshold (eg, "IT _D "). Representations 578A through 578C appear and move up as they increase toward. In some embodiments, the strength on which the progress of the animation is based is the characteristic strength of the contact. Operations described with reference to FIGS. 5E to 5H may be performed using an electronic device similar to or identical to device 100 , 300 , or 500 .

In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as "jitter", where the device has a hysteresis intensity threshold ( For example, the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or any suitable percentage of the press input intensity threshold. Thus, in some embodiments, a press input includes an increase in intensity of an individual contact above a press input intensity threshold, and a subsequent decrease in intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold; The respective action is performed in response to detecting a subsequent decrease in the intensity of the respective contact below the hysteresis intensity threshold (eg, the “up stroke” of the respective press input). Similarly, in some embodiments, the press input causes the device to increase the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, and optionally, to an intensity below the hysteresis intensity. It is detected only when detecting a subsequent decrease in the intensity of the contact, and the respective action is performed in response to detecting a press input (eg, an increase in the intensity of the contact or a decrease in the intensity of the contact depending on the environment).

For convenience of description, the description of operations performed in response to a press input associated with the press input intensity threshold or in response to a gesture including the press input, optionally, an increase in the intensity of a contact exceeding the press input intensity threshold, a hysteresis intensity threshold An increase in the intensity of a contact from an intensity below the press input intensity threshold to an intensity above the press input intensity threshold, a decrease in the intensity of the contact below the press input intensity threshold, and/or an intensity of the contact below the hysteresis intensity threshold corresponding to the press input intensity threshold. Triggered in response to detecting any of the declines. Further, in examples where an action is described as being performed in response to detecting a decrease in the intensity of the contact below a press input intensity threshold, the action is, optionally, less than a hysteresis intensity threshold that corresponds to and is lower than the press input intensity threshold. is performed in response to detecting a decrease in the intensity of the contact of

As used herein, an “installed application” is a software application that has been downloaded onto an electronic device (eg, devices 100, 300, and/or 500) and is ready to be launched (eg, opened) on the device. refers to In some embodiments, the downloaded application becomes an application installed through an installation program that extracts program portions from the downloaded package and integrates the extracted portions with the computer system's operating system.

As used herein, the terms “open application” or “running application” refer to a state held (e.g., as part of device/global internal state 157 and/or application internal state 192). Refers to a software application that holds information. The open or running application is optionally any of the following application types:

an active application currently displayed on the display screen of the device on which the application is being used;

a background application (or background process) that is not currently displayed, but one or more processes for the application are being processed by one or more processors; and

A suspended or hibernated application that is not running, but has state information that is stored in memory (volatile and non-volatile, respectively) and can be used to resume execution of the application.

As used herein, the term "closed application" refers to software applications that do not have state information retained (eg, state information for closed applications is not stored in the device's memory). Thus, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the device's memory. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application stops being displayed, the first application becomes a background application.

Attention is now directed to embodiments of user interfaces (“UIs”) and associated processes implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

6A-6B depict example user interfaces associated with a physical activity application, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 7 .

6A shows a device 600 having a touch-sensitive display 602 . A user interface 610A of the workout application is displayed on the touch-sensitive display 602 . Device 600 has various input mechanisms that can receive user input, such as rotatable input mechanism 603 that can receive rotatable input (and can also receive push input) and push user input. An input mechanism 604 is included. In some embodiments, device 600 includes some or all of the features of device 100 , device 300 , or device 500 .

User interface 610A includes a scrollable list 620 of affordances associated with individual physical activity tracking functions for the physical activity. For example, the scrollable list of affordances includes affordance 621 corresponding to a physical activity tracking function for outdoor running, and affordance 622 corresponding to a physical activity tracking function for a pool swim. include Note that the scrollable list of affordances 620 includes additional affordances corresponding to other body activity tracking functions that are not currently displayed but may be displayed in response to a scrolling input (eg, rotation of the rotation mechanism 603). do.

In some embodiments, one or more of the affordances in the scrollable list of affordances 620 includes a respective athletic metric change affordance, which will be described in more detail below (see at least FIG. 6J ). For example, affordance 621 includes workout metric change affordance 631 and affordance 622 includes workout metric change affordance 632 .

In some embodiments, one or more affordances in the scrollable list of affordances 620 include a physical activity icon corresponding to the physical activity associated with the affordance. For example, affordance 621 includes a physical activity icon 621 - 1 (eg, a runner's icon). Similarly, affordance 622 includes a physical activity icon 622-1 (eg, an icon of a child). In various embodiments, the physical activity icons (eg, physical activity icon 621 - 1 ) are displayed in a first state (eg, a static state).

In some embodiments, one or more affordances in the scrollable list of affordances include an athletic identifier. For example, affordance 621 includes workout identifier 621-2 indicating that affordance 621 is associated with an outdoor running workout. Similarly, affordance 622 includes exercise identifier 622-2 indicating that affordance 622 is associated with a swimming pool exercise.

In some embodiments, one or more affordances in the scrollable list of affordances include athletic goal information. For example, affordance 622 includes exercise goal information 622-3 indicating that a predetermined goal for a swimming pool exercise associated with affordance 622 is 3 miles. That is, if affordance 622 is selected, the associated physical activity tracking function will automatically track the distance of a swimming pool workout with a pre-set goal of 3 miles. Affordance 621 includes an athletic goal affordance 621-3 indicating that the outdoor run associated with affordance 621 is an “open goal.” The open goal indication indicates to the user that the associated workout does not currently have any pre-set goal. Accordingly, when affordance 621 is selected, various metrics will be tracked by the associated body activity tracking function, where the metrics do not include any pre-set target values.

Referring to FIG. 6B , a touch input (eg, tap input) 615A is received, where the touch input 615A corresponds to selection of affordance 621 . Upon a determination that user input 615A is detected at first affordance 621 in the scrollable list of affordances, the physical activity tracking function associated with affordance 621 is initiated. That is, execution of the physical activity tracking function starts according to the selection of the affordance 621 . Also, in some embodiments, selection of another affordance (eg, affordance 622) in the scrollable list of affordances 620 will initiate another associated physical activity tracking function, which will be described in more detail below.

Referring to FIGS. 6C-6F , in response to selection of affordance 621 , user interface 610B displays a countdown prior to tracking metrics by the physical activity tracking function. For example, user interface 610B displays "Ready" (FIG. 6C), then "3" (FIG. 6D), then "2" (FIG. 6E), and then "1" (FIG. 6F). to display a numerical countdown.

In response to completion of the countdown, user interface 610C is displayed (FIGS. 6G-6I). User interface 610 displays tracked metrics 630 (which are tracked by the physical activity tracking function) associated with an exercise (eg, outdoor running) corresponding to selected affordance 621 . For example, user interface 610C allows tracking of various metrics (e.g., miles 630-1, active calories 630-2, average miles 630-3, and time 630-4). include As shown in FIGS. 6G-6I , user interface 610C at a time of 0.01 seconds for outdoor running ( FIG. 6G ), at a time of 0.59 seconds for outdoor running ( FIG. 6H ), and for outdoor running. Displays tracked metrics 630 of an outdoor running workout at a time of 1.23 seconds ( FIG. 6H ). In some embodiments, in response to selection of affordance 621 , user interface 610C is displayed without displaying (or bypassing) user interface 610C.

Displaying a scrollable list of exercise affordances and initiating a physical activity tracking function to track metrics associated with the selected exercise affordance allows the user to quickly select an exercise and initiate the tracking function to track metrics associated with the selected exercise. let it track Reducing the number of inputs needed to perform tracking of athletic metrics improves the operability of the device (eg, by helping the user provide appropriate inputs when operating/interacting with the device and reducing user errors). and make the user-device interface more efficient, which further reduces the power usage of the device and improves its battery life by enabling the user to use the device more quickly and efficiently.

In some embodiments, while the body activity tracking function associated with the affordance is running, the body activity icon is displayed in an animated state. For example, referring to FIGS. 6G-6I , body activity icon 621-1 is animated (e.g., body activity icon 621-1) while tracking metrics 630. The runner in moves in a running motion). It should be appreciated that the body activity icon 621 - 1 stops being animated when the body activity tracking function associated with the affordance stops running (eg, stops tracking metrics 630 ).

In some embodiments, tracking of the metrics is performed by one or more tracking sensors of the device. For example, device 600 tracks physical activity via tracking sensors (or athletic sensors) in communication with athletic support module 142 (as shown in FIG. 3 ).

Referring to FIG. 6J , user interface 610A displays a scrollable list 620 of affordances (similar to FIG. 6A ). A user input 615B (eg, a tap gesture) is received at the workout metric change affordance 631 .

Referring to FIG. 6K , according to a determination that a user input 615B is detected at the exercise metric change affordance 631, a user interface 610D is displayed, where the user interface 610D corresponds to the body affordance 621. and change athletic metrics associated with an activity (eg, outdoor running). Specifically, user interface 610D provides metric affordances 640 (e.g., open goal affordance 640-1, distance affordance 640-2), calorie affordance associated with an outdoor running workout and corresponding workout metrics. (640-3), and time affordance (640-4). User interface 610D also includes an affordance 641 configured to display the previous UI 610A (FIG. 6J) when selected. In some embodiments, upon determining that user input 615B is detected on exercise metric change affordance 631 , user interface 610D is displayed initiating the physical activity tracking function associated with affordance 621 .

Displaying the workout metric change affordance with a scrollable list of workouts allows the user to quickly change the metric's target values and initiate a tracking function to track metrics associated with the workout. Reducing the number of inputs needed to change target values and perform tracking of athletic metrics (e.g., by helping a user provide appropriate inputs when operating/interacting with a device and reducing user errors) Improves the operability of the device and makes the user-device interface more efficient, which further reduces the power usage of the device and improves its battery life by enabling the user to use the device more quickly and efficiently .

Referring to FIG. 6L, a user input 615C (eg, a tap gesture) is received at a distance affordance 640-2.

Referring to FIGS. 6M to 6R , in response to receiving a user input 615C at the distance affordance 640 - 2 , a target value user interface 610E is displayed. Goal value user interface 610E includes a target value 642 (eg, 7.5 miles) corresponding to the selected distance affordance 640-2 of the outdoor running workout. The initial goal of 7.50 miles is the current value associated with the distance metric for outdoor running. That is, if an outdoor running workout is initiated (with a distance goal of 7.50 miles), the tracking of the distance metric will be set to 7.50 miles.

In some embodiments, target value 642 (eg, 7.50 miles) is a target change affordance 643 (eg, a “-” affordance) and/or a target change affordance 644 (eg, a “+” affordance). can be adjusted through For example, user input 615D is received at target change affordance 644 (FIG. 6N). In response to receiving user input 615D on target change affordance 644, the target value of 7.50 miles is changed to 7.60 miles (FIG. 6O). Similarly, user input 615E is received at target change affordance 643 (FIG. 6P). In response to receiving user input 615E on target change affordance 643, the target value of 7.60 miles is changed to 7.50 miles (FIG. 6Q).

As shown in FIG. 6Q , target value user interface 610E includes target information 646 . For example, the goal information 646 is information identifying the previous longest distance (related to an outdoor running exercise) tracked by the physical activity tracking function. Accordingly, a user may adjust target value 642 based at least in part on target information 646 (by increasing or decreasing target value, as described above). Target value user interface 610E also includes an affordance 645 configured to display previous UI 610D (FIG. 6L) when selected.

Referring to FIG. 6R , the target value user interface 610E includes a start affordance 647 configured to initiate a physical activity tracking function associated with affordance 621 . For example, user input 615H is received at start affordance 647 . In response to user input 615H selecting affordance 647, a physical activity tracking function associated with affordance 621 (eg, outdoor running) is initiated. Specifically, the physical activity tracking function tracks distance traveled for outdoor running based on a goal of 7.50 miles. In some embodiments, initiation of the physical activity tracking function associated with affordance 621 via start affordance 647 is similar to initiation of the physical activity tracking function by user input 615A at affordance 621 ( 6c to 6i).

6s-6u illustrate various embodiments of a target value user interface 610E. FIG. 6S shows user interface 610E displayed in response to user input at open goal affordance 640-1 (FIG. 6K). The open goal feature does not include any goal values associated with physical activity (eg, outdoor running). Accordingly, target value user interface 610E does not display any target values (when displayed in response to selection of open target affordance 640-1). In response to receiving user input 615I at start affordance 647, a physical activity tracking function associated with affordance 621 (eg, outdoor running) is initiated. The disclosed body tracking function tracks various metrics (eg, distance, calories, time), but does not track metrics for goals. In some embodiments, initiation of the physical activity tracking function associated with affordance 621 via start affordance 647 is similar to initiation of the physical activity tracking function by user input 615A at affordance 621 ( 6c to 6i).

FIG. 6T shows target value user interface 610E displayed in response to user input at time goal affordance 640-4 (FIG. 6K). Goal user interface 610E (when displayed in response to selection of time goal affordance 640-4) includes goal value 642 (e.g., elapsed time of one hour), goal change affordances 643, 644, goal information 646 (eg, information identifying the longest previous duration the physical activity tracking function tracked for an outdoor run), and start affordance 647 . Target value 642 may be adjusted through selection of target change affordance 643 and/or target change affordance 644 as described above (FIGS. 6M to 6Q). Additionally, in response to user input (eg, a tap gesture) selecting affordance 647 , physical activity tracking functionality associated with affordance 621 (eg, outdoor running) is initiated. Specifically, the physical activity tracking function tracks the duration of outdoor running based on a target value of 1 hour. In some embodiments, initiation of the physical activity tracking function associated with affordance 621 via start affordance 647 is similar to initiation of the physical activity tracking function by user input 615A at affordance 621 ( 6c to 6i).

FIG. 6U shows user interface 610E displayed in response to user input at calorie affordance 640-3 (FIG. 6K). Goal user interface 610E (when displayed in response to selection of calorie affordance 640-3) includes goal value 642 (e.g., active calories burned), goal change affordances 643, 644, and goal information. 646 (eg, information identifying the most calories burned that the physical activity tracking feature tracked from a previous outdoor running workout), and start affordance 647 . Target value 642 may be adjusted through selection of target change affordance 643 and/or target change affordance 644 as described above (FIGS. 6M to 6Q). Additionally, in response to user input (eg, a tap gesture) selecting affordance 647 , physical activity tracking functionality associated with affordance 621 (eg, outdoor running) is initiated. Specifically, the physical activity tracking function tracks calories burned during outdoor running based on a goal of 700 calories. In some embodiments, initiation of the physical activity tracking function associated with affordance 621 via start affordance 647 is similar to initiation of the physical activity tracking function by user input 615A at affordance 621 ( 6c to 6i).

6V-6AB depict one embodiment of a user interface 610A displaying scrolling of a scrollable list of affordances 620 and selection of an affordance. For example, rotational input 605 is received at rotatable input mechanism 603 (FIGS. 6V and 6W). In response to rotation input 605, list of affordances 620 is displayed with affordance 622 fully displayed, affordance 621 partially displayed, and affordance 623 (associated with stair stepper movement) partially displayed. is scrolled upwards to be displayed as (FIG. 6x).

User input 615J is received at affordance 622 (FIG. 6y). In response to user input 615J at affordance 622 (associated with a swimming pool exercise), user interface 610F is displayed (FIG. 6Z). User interface 610F includes pool length value 648 , value change affordance 643 and/or value change affordance 644 . The pool length value 648 may be changed (eg, from 50 yards to 100 yards, from 50 yards to 25 yards, etc.) via one or more of the value change affordances. In particular, user interface 610F is configured to receive a pool length value (eg, 50 yards) for a swim in pool workout, such that the body activity tracking function determines the number of pool lengths the user swims during a swim in pool workout. make it possible to track

User input 615K is received at start affordance 647 (FIG. 6AA). In response to user input 615K, a physical activity tracking function associated with affordance 622 (eg, swimming in a pool) is initiated. For example, in response to selection of affordance 647, user interface 610C is displayed (FIG. 6ab). User interface 610C provides various metrics 633 (e.g., lap count metric 633-1, active calories 633-2, total calories 633-3, and elapsed time 633-4). contains traces of A comparison between FIG. 6G (showing metrics tracked 630 associated with outdoor running) and FIG. 6AB (showing metrics tracked 633 associated with swimming in a pool) shows that different physical activities track different metrics. It should be understood that it can be tracked using For example, for running activities, it is often desirable to track the total length of runs (in miles), and for swimming pools, it is often desirable to track the number of laps completed.

6ac and 6ad illustrate one embodiment of a user interface 610A. User interface 610A displays affordances 624 and 625 in a scrollable list of affordances 620 . In one embodiment, affordance 625 is not associated with a specific physical activity and is labeled “OTHER, Open Goal”. Additionally, in one embodiment, affordance 625 is the last (or bottom) affordance in the scrollable list of affordances 620 . As described in more detail below, affordances 625 facilitate updating the scrollable list of affordances 220 with additional specific activity affordances, where a user may select a specific physical activity associated with the additional specific activity affordance (e.g., , yoga) can be selected.

User input 615L is received at affordance 625 (FIG. 6AD). In response to user input 615L, user interface 610G is displayed (FIG. 6ae). User interface 610G displays information 638 indicating that the user can select an exercise associated with metrics to be tracked by the physical activity tracking function. User interface 610G includes affordance 647 configured to initiate a physical activity tracking function.

User input 615M is received at affordance 647 (FIG. 6af). In response to user input 615M, user interface 61B is displayed (FIG. 6ag). User interface 610B displays a countdown prior to tracking metrics by the physical activity tracking function, as described above (eg, FIGS. 6C-6F ).

Upon completion of the countdown, user interface 610C is displayed (FIGS. 6ah-6ai). User interface 610C provides a plurality of metrics 634 (eg, duration 634-1, active calories 634-2, total calories) tracked by the physical activity tracking function during physical activity (eg, yoga). 634-3, and heart rate 634-4). In some embodiments, user interface 610C is displayed in response to user input 615M without display of intervening user interface 610B. User interface 610C as shown in FIGS. 6ah and 6ai does not include a physical activity icon (e.g., physical activity icon 621-1) because affordance 625 is not associated with physical activity. Note

User input 615N (eg, a swipe gesture) is received on touch-sensitive display 602 ( FIGS. 6AI-6AK). In response to user input 615N, user interface 610H is displayed (FIG. 6A). User interface 610H includes affordances for controlling various functions of the athletic application. For example, user interface 610H includes screen lock affordance 650 (configured to lock screen and not receive user input), workout switching affordance 651 (described in more detail below), workout end affordance 652 (configured to end the current running workout), and workout pause affordance 653 (configured to pause the current running workout).

The user interface 610C includes a paging dot 639-1 and a paging dot 639-2. Paging dots correspond to successive pages (or user interfaces) in an athletic application. For example, paging dot 639-1 corresponds to user interface 610C, and paging dot 639-2 corresponds to user interface 610H. In response to a user input such as a swipe gesture (e.g., 610H), the currently displayed page (e.g., user interface 610C in FIG. )) is replaced by the display of Note that when user interface 610C is displayed, paging dot 639-1 is highlighted (FIG. 6ah). Similarly, when user interface 610H is displayed, paging dot 639-2 is highlighted (FIG. 6A).

User input 6150 is received at workout end affordance 652 (FIG. 6am). For example, upon completion of a user's yoga workout, the user selects end workout affordance 652 to stop tracking metrics 634 . In response to user input 6150 at exercise end affordance 652, user interface 610I is displayed (FIG. 6an).

User interface 610I includes a list of tracked metrics 634 associated with affordance 625 . For example, user interface 610I includes body activity information 635 associated with metrics 634 . Because tracked metrics 634 were tracked through selection of affordance 625 (eg, Other, Open Goal affordance), physical activity currently assigned to or associated with tracked metrics 634 of a completed workout (eg, yoga ) is not User interface 610I also includes duration 634-1, active calories 634-2, total calories 634-3, average heart rate 634-4, and range of heart rates 634-5. includes Additionally, user interface 610I includes an activity add affordance 636 and a complete affordance 637 . In some embodiments, user interface 610I includes date and weather information associated with the physical activity.

Note that for ease of discussion, the entirety of user interface 610I (including off-screen portions) is shown in FIG. 6A. However, it should be understood that the entirety of user interface 610I may not be displayed on touch-sensitive display 602 of limited display size. As a result, the user can scroll through the user interface via user input (eg, rotatable input) received at rotatable input mechanism 603 .

User input 615P (eg, a tap gesture) is received at affordance 636 (FIG. 6ao). Referring to FIG. 6AP , a user interface 610J is displayed in response to user input 615P on affordance 636 . User interface 610J displays a predefined list 660 of selectable physical activities. The predefined list 660 of selectable physical activities is selected and subsequently configured to be associated with tracked metrics 634 corresponding to an affordance 625 (eg, Other, Open Goal affordance). The predefined list 660 of selectable physical activities includes soccer (660-1), yoga (660-2), strength training (660-3), archery (660-4), basketball (660-5), and Curling 660-6. Note that the predefined list of selectable physical activities 660 may include additional physical activities that are not currently displayed but may be displayed in response to a scrolling input (eg, rotation of the rotation mechanism 603).

In some embodiments, the predefined list 660 of selectable physical activities includes a first set of physical activities (eg, soccer 660-1, yoga 660-2, and strength training 660-3). )). The first set of physical activities, in some embodiments, is a predefined list of popular activities and is displayed at the top of the predefined list 660 of selectable physical activities. Additionally, the predefined list 660 of selectable physical activities includes a second set of physical activities listed in alphabetical order (eg, archery 660-4, basketball 660-5, and curling 660-4). 6)).

Referring to FIGS. 6aq and 6ar , a user input 615Q is received in a yoga activity 660-2. In response to user input 615Q in yoga activity 660-2, metrics 634 of the completed workout are associated with the yoga workout. Accordingly, body activity information 635 (in user interface 660I) indicates that metrics 634 are associated with a yoga exercise through selection of affordance 625 . Additionally, in response to user input 615Q on yoga activity 660-2, user interface 660I includes an icon 670 corresponding to a yoga exercise.

6at shows a companion device 690 being paired to device 600 . In some embodiments, counterpart device 690 can be device 100 , device 300 , device 500 , or a device that includes features of one or more of these devices. The counterpart device 690 includes a touch-sensitive display 691 . A user interface 692 is displayed on the touch-sensitive display 691 . Far-end device 690, as described herein, in some embodiments, when paired to device 600, may display application views and perform at least some of the same processes as device 600. can do. In response to the user input 615R in the affordance 637 (FIG. 6as), list information of yoga exercises is displayed on the user interface 692 of the partner's device 690. For example, user interface 692 includes icon 670 and metrics 634 associated with a completed yoga workout.

6au and 6av show one embodiment of a user interface 610A. In response to user input 615R on affordance 637 (FIG. 6as), affordance 626 is added to the scrollable list of affordances 620. For example, affordance 626 is a new affordance associated with yoga exercise. Affordance 626 is an open goal affordance associated with yoga exercise. An open target affordance is not associated with any predefined target values. As such, in some embodiments, the body activity tracking function tracks various metrics associated with an open goal affordance, and tracks the metrics without considering any predefined goal values. Affordance 626 is listed at the top or beginning of the scrollable list of affordances 620 . In one embodiment, affordance 626 is listed at the bottom or end of a scrollable list of affordances 620 . In various embodiments, affordance 625 remains listed in a scrollable list of affordances upon adding a new affordance (e.g., affordance 626), as described herein, where a new affordance is added. Affordances are created based in part on the selection of affordances 625 .

User input 615S is received at affordance 626 (FIG. 6av). In response to user input 615S, as described above, user interface 610B displays a countdown prior to tracking metrics by the physical activity tracking function (eg, FIGS. 6C-6F ). Upon completion of the countdown displayed on user interface 610B, the physical activity tracking function returns metrics 634 (e.g., duration 634-1) associated with the yoga exercise tracked by the physical activity tracking function during the physical activity. , active calories 634-2, total calories 634-3, and heart rate 634-4) (FIG. 6ax).

Referring to FIGS. 6ay-6bb , user input 615T (eg, a swipe gesture) is received on touch-sensitive display 602 . In response to user input 615T, user interface 610H is displayed (FIG. 6bb). User interface 610H includes affordances for controlling various functions of the athletic application. For example, the user interface 610H includes a screen lock affordance 650, an exercise switching affordance 651, an exercise end affordance 652, and an exercise pause affordance 653.

User input 615U is received at motion switching affordance 651 (FIG. 6BC). For example, while the physical activity tracking feature is tracking metrics 634 during a user's yoga workout, the user selects workout switching affordance 651 to switch to a different workout. In response to user input 615U on athletic switching affordance 651, user interface 610A is displayed ( FIG. 6BD ), a scrollable list of affordances (e.g., affordance 621 and affordance 622) ( 620) is displayed. Additionally, in response to user input 615U at athletic switching affordance 651 , the physical activity tracking function that tracks metrics 634 is paused.

6BD depicts user interface 610A including a paused body activity affordance 655 . In one embodiment, user input at affordance 655 is configured to continue a paused workout (eg, a paused yoga workout). For example, in response to user input at affordance 655, a paused physical activity tracking function associated with a yoga workout resumes tracking metrics 634 (eg, FIG. 6ay).

Referring to FIGS. 6be to 6bg, a user input 615V is received at affordance 621 (FIG. 6be). In response to user input 615V at affordance 621, metrics 630 (eg, miles 630-1, active calories 630-2, average) of the corresponding physical activity (eg, outdoor running) A physical activity tracking function is initiated to track miles 630-3, and time 630-4. Additionally, in response to user input 615V on affordance 621 ( FIG. 6B ), a paused workout (eg, a paused yoga workout) is canceled. Specifically, the physical activity tracking functionality associated with tracking metrics 634 is canceled.

Referring to FIG. 6BH, a user interface 610H is displayed. For example, user interface 610H is displayed in response to a swipe gesture on touch-sensitive display 602 in FIG. 6BG.

User input 615W is received at exercise end affordance 652 (FIG. 6BH). In response to user input 615W at workout end affordance 652, tracking of metrics 630 ends, and user interface 610J is displayed (FIG. 6B). User interface 610J is configured to display a list of aggregated metrics of at least two previously completed workouts. For example, user interface 610J may display aggregated metrics 680 (e.g., total time 680- 1), active calories (680-2), total calories (680-3), average heart rate (680-4), and heart rate range (680-5)). In one embodiment, the user switched from a yoga workout to an outdoor running workout via selection of switching affordance 651 (FIG. 6BC).

The user interface 610J includes an exercise affordance 681 associated with a yoga exercise and an affordance 682 associated with an outdoor running exercise. User input 615W is received at affordance 682 corresponding to an outdoor running workout. In response to user input 615W on affordance 682, user interface 610K is displayed (FIG. 6BK). User interface 610K includes metrics 630 associated with outdoor running (eg, total time, average pace, active calories, total calories, average heart rate, and heart rate range). Similarly, in some embodiments, in response to user input at affordance 681, metrics 634 associated with the yoga exercise will be displayed (e.g., similar to displayed metrics 634 in FIG. 6A). box).

Referring to FIGS. 6BL and 6BM , device 600 is proximate to a pairable exercise device 695 (eg, external heart rate monitor, treadmill, stair stepper). Device 600 and device 695 are communicatively pairable. For example, device 600 and device 695 are pairable via wireless communication (eg, near-field communication (NFC), Bluetooth). It should be appreciated that device 690 may also be pairable to exercise device 695 .

Device 600 detects pairable exercise device 695 when device 600 is in close proximity to pairable exercise device 695 . In response to detecting pairable athletic device 695 and upon determining that the automatic athletic device pairing criteria are satisfied, device 600 automatically pairs with pairable athletic device 695 (eg, without further user input). (FIG. 6bm). For example, device 695 is automatically paired with device 695 (eg, an external heart rate monitor). Accordingly, device 600 displays information 696 indicating that device 600 and device 695 have been automatically paired with each other.

In one embodiment, the automatic workout device pairing criterion is satisfied when a workout (eg, outdoor running workout) on device 600 is completed. In another embodiment, the automatic athletic device pairing criterion is satisfied when device 600 has been paired with a pairable exercise device 695 within a predetermined amount of time (eg, within the last 90 days). In a further embodiment, the automatic athletic device pairing criterion is satisfied when the user positively enables the setting for automatic pairing with pairable athletic devices.

In some embodiments, in response to detecting pairable athletic device 695 and upon determining that the automatic athletic device pairing criterion is not satisfied, device 600 does not automatically pair with a pairable athletic device. In one embodiment, the automatic exercise device pairing criterion is not satisfied when an exercise (eg, outdoor running exercise) on device 600 has not been previously completed. In another embodiment, the automatic athletic device pairing criterion is not satisfied when device 600 has not been paired with a pairable exercise device 695 within a predetermined amount of time (eg, within the last 90 days). In a further embodiment, the automatic athletic device pairing criterion is not satisfied when the user does not positively enable the setting for automatic pairing with pairable athletic devices. In another embodiment, the automatic athletic device pairing criteria provides user input that allows the user to select an athletic affordance (eg, affordance 621) and connects the user with a pairable exercise device 695 (eg, heart monitor). They are not satisfied when prompted to do so. For example, referring to FIG. 6B , a pairing accept affordance 696-1 (eg, Yes) and a pairing reject affordance 696-2 (eg, not now) are displayed. The devices 600 and 695 will be paired according to the user's selection of the pairing accept affordance 696-1. Alternatively, devices 600 and 695 will not pair upon user selection of pairing refusal affordance 696-2.

7 is a flow diagram illustrating a method for displaying a scrollable list of affordances associated with physical activities using an electronic device, in accordance with some embodiments. Method 700 is performed in a device (eg, 100, 300, 500, 600) having one or more processors, memory and a body activity tracking sensor. Some actions of method 700 are optionally combined, some actions are optionally reordered, and some actions are optionally omitted.

As described below, method 700 provides, among other things, an intuitive way to initiate a physical activity tracking function upon a determination that a user input is detected at a first affordance in a scrollable list of affordances. This method reduces the cognitive burden on the user by selecting an exercise from a list of exercises and initiating a physical activity tracking function, thereby creating a more efficient human-machine interface. For battery-powered computing devices, allowing a user to select an exercise from a list of exercises and initiate a physical activity tracking function is faster and more efficient to conserve power and reduce the time between battery charges. increase

At block 710 , the device (eg 600 ) displays a scrollable list (eg 620 ) of affordances associated with physical activities.

At block 720, the device displays a first athletic metric change affordance (eg, 631) that corresponds to the first affordance (eg, 621) of the scrollable list of affordances (eg, 620).

At block 730, the device (eg, 600) receives user input (eg, 615A).

At block 740, in accordance with a determination that user input (eg, 615A) is detected at a first affordance (eg, 221) within the scrollable list of affordances (eg, 220), the physical activity tracking function associated with the selected first affordance. is disclosed (eg, the body activity tracking function tracks metrics 630).

At block 750, in response to a determination that a user input (eg, 615B) is detected at a first exercise metric change affordance (eg, 631), a user interface configured to change an exercise metric (eg, 610D) is displayed.

In some embodiments, user input (eg, 615L) is received at a second affordance (eg, 625) in the scrollable list of affordances. In response to the user input at the second affordance, the device (eg, 600) initiates a physical activity tracking function associated with the selected second affordance. Following completion of the tracking function, the device displays a predefined list (eg, 660) of selectable physical activities. User input (eg, 615Q) is received at a selectable physical activity (eg, 660-2) of a predefined list of selectable physical activities. Following selection of a physical activity in the predefined list of selectable physical activities, the device updates the scrollable list of affordances (eg, 220) with additional affordances (eg, 626) associated with the selected physical activity.

According to some embodiments, upon determining that user input (eg, 615B) is detected at the first athletic metric change affordance (eg, 631 ), the device determines the level of the physical activity tracking function associated with the first affordance (eg, 621 ). postpone the start

In some embodiments, user input (eg, 615C) corresponding to selecting a metric affordance (eg, 640-2) of a plurality of metric affordances (eg, 640) is received. In response to selecting the metric affordance and receiving the corresponding user input, the device (eg, 600) displays a first target value (eg, 642) corresponding to the selected metric affordance.

In some embodiments, in response to receiving user input corresponding to selecting a metric affordance (eg, 615C), the device (eg, 600) displays at least one target change affordance (eg, 643 or 644). do. User input (eg, 615D) corresponding to selecting at least one target change affordance is received. In response to receiving a user input corresponding to at least one goal change affordance, the first goal value (eg, a goal value of 7.50 miles) is replaced with a second goal value (eg, a goal value of 7.60 miles).

In some embodiments, in addition to receiving a user input (eg, 615C) corresponding to selecting a metric affordance (eg, 640-2), the device (eg, 600) initiates an association associated with the selected first affordance. A physical activity tracking start affordance (eg, 647) corresponding to initiating the physical activity tracking function is displayed. A user input (eg, 615H) corresponding to selecting the physical activity tracking function start affordance is received. In response to selecting a physical activity tracking function start affordance and receiving the corresponding user input, a physical activity tracking function associated with the selected first affordance is initiated (e.g., device 600 monitors metrics associated with an outdoor running workout). 630)).

In some embodiments, initiating the physical activity tracking function associated with the selected first affordance (eg, 621) determines a first set of metrics (eg, 630) associated with the first type of physical activity (eg, outdoor running). includes tracking A second set of metrics associated with a second type of physical activity (eg, swimming in a pool) in accordance with a determination that a user input is detected at a second affordance (eg, 622) within a scrollable list of affordances (eg, 620). A physical activity tracking function associated with the selected second affordance is initiated, including tracking (eg, 633). The second set of metrics (eg, 633) is different from the first set of metrics (eg, 630).

In some embodiments, an affordance (eg, 621) in the scrollable list of affordances includes a physical activity icon (eg, 621-1) corresponding to the physical activity (eg, running outdoors) associated with the affordance. In some embodiments, while the physical activity tracking function associated with the affordance is running, the physical activity icon (eg, 621-1) is displayed in an animated state.

In some embodiments, user input (eg, 615T) corresponding to a request to display a user interface (eg, 610H) configured to switch exercises while a physical activity tracking function associated with affordance (eg, 626) is running. is received In response to receiving user input corresponding to a request to display a user interface configured to switch workouts, the physical activity tracking function is paused and a workout switching affordance (eg, 651 ) is displayed. A user input (eg, 615U) corresponding to selecting an athletic switching affordance is received. In response to receiving user input corresponding to selecting an athletic switching affordance, a scrollable list of affordances (e.g., 620) is displayed, and a paused physical activity affordance associated with the paused body activity function (e.g., 655 ) is displayed.

In some embodiments, subsequent to pausing the physical activity tracking function, user input (eg, 615V) corresponding to selection of an affordance (eg, 621) in a scrollable list of affordances (eg, 620) is received. . In response to receiving user input corresponding to selection of an affordance in the scrollable list of affordances, the paused body activity tracking function is canceled (eg, stops tracking metrics 634 for a yoga workout). , a different physical activity tracking function associated with the selected affordance is initiated (eg, begins tracking metrics 630 for outdoor running).

In some embodiments, user input corresponding to selection of a paused body activity affordance (eg, 655 ) is received. In response to receiving user input corresponding to selection of the paused physical activity affordance, the paused physical activity tracking function is resumed (eg, tracking of metrics 634 resumes).

In some embodiments, subsequent to completion of the first motion tracking function and the second motion tracking function, a scrollable movement of a first physical activity associated with the first motion tracking function and a second physical activity associated with the second motion tracking function. A list (eg, a list of aggregated metrics 680 ) is displayed. The scrollable workout list includes a set of aggregated metrics (e.g., 680) of a first workout tracking function and a second workout tracking function, a first affordance (e.g., 681) associated with a first physical activity, and a second physical activity. and an associated second affordance (eg, 682). User input (eg, 615W) is received. Upon a determination that the user input (eg, 615W) corresponds to a selection of a first affordance associated with a first physical activity (eg, 681), a set of metrics (eg, 630 in FIG. 6BK ) associated with the first physical activity is displayed Upon a determination that the user input (eg, 615W) corresponds to a selection of a second affordance associated with a second physical activity (eg, 682), a set of metrics (eg, 634) associated with the second physical activity is displayed.

In some embodiments, a pairable exercise device (eg, 695) is detected. In response to detecting a pairable exercise device, and an automatic exercise device pairing criterion is satisfied (e.g., an exercise has been completed on device 600, or device 600 has paired with pairable exercise device 695 within a predetermined amount of time). or the user positively enables the setting for automatic pairing with pairable athletic devices), upon determination, the device (eg, 600) is automatically paired with the pairable athletic device. In response to detecting a pairable exercise device (e.g., 695) and an automatic exercise device pairing criterion is not met (e.g., an exercise has not been previously completed on device 600 or device 600 has not been previously completed at a predetermined time). has not been paired with a pairable exercise device 695 within the device, the user has not positively enabled the setting for automatic pairing, or the user has been prompted to provide user input that allows it to connect with a pairable exercise device). Upon determination, it suspends automatic pairing of the device with a pairable exercise device (FIG. 6B).

In some embodiments, a user interface configured to change an athletic metric (eg, 610D) includes a plurality of metric affordances (eg, 640-1, 640-2) corresponding to a physical activity associated with a first affordance (eg, 621). , 640-3, 64-4). In some embodiments, the body activity tracking function tracks metrics (eg, 630) corresponding to data received from body activity tracking sensors (eg, sensors in exercise support module 142). In some embodiments, the first affordance (eg, 621) in the scrollable list of affordances (eg, 620) is the most recently selected affordance.

Note that details of the processes described above with respect to method 700 (eg, FIG. 7 ) are also applicable in a similar manner to the methods described below. For example, method 900 optionally includes one or more of the features of the various methods described above with reference to method 700. For example, method 900 may include, in some embodiments, initiating a physical activity tracking function or displaying a user interface configured to change an athletic metric. For brevity, these details are not repeated below.

8A-8T depict example user interfaces associated with a physical activity application and an audio application, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 9 .

8A shows a device 800 having a touch-sensitive display 802 . Device 800 has various input mechanisms that receive user input, such as rotatable input mechanism 803 that can receive rotatable input (and can also receive push input) and push user input. An input mechanism 804 is included. In some embodiments, device 800 includes some or all of the features of device 100 , device 300 , device 500 , or device 600 .

Referring to FIG. 8A , a user interface 810A displayed on the touch-sensitive display 802 is an audio application control user interface configured to control audio content being played on the audio application. The user interface 810A includes audio content information 811 and audio content control units 812 . For example, the audio content information 811 includes, but is not limited to, the title of the currently playing audio content (eg, “Across the Land”) and the name of the group performing the song (eg, “Awe Singers”). It doesn't work. Audio content controls 812 include, but are not limited to, jump forward to next song, pause/play, jump backward to previous song, and volume control. Not limited.

User input 815A (eg, push input via finger 816) is received at rotatable input mechanism 803 (FIG. 8B). In response to user input 815A and while audio content is playing on the audio application, user interface 810B is displayed (FIG. 8C). User interface 810B includes a plurality of application affordances 805 associated with applications. For example, affordance 805-1 is associated with an athletic application and affordance 805-2 is associated with an audio application currently playing audio content.

User input 815B (eg, a tap gesture) is received at affordance 805-1 (FIG. 8D). In response to user input 815B at affordance 805-1 and while audio content is playing on the audio application, user interface 810C is displayed (FIG. 8E). User interface 810C includes a scrollable list 820 of affordances associated with individual physical activity tracking functions for the physical activity. For example, the scrollable list of affordances includes affordance 821 corresponding to a physical activity tracking function for running outdoors, and affordance 822 corresponding to a physical activity tracking function for swimming in a pool. Note that the list of affordances 820 includes additional affordances corresponding to other body activity tracking functions that are not currently displayed but may be displayed in response to a scrolling input (eg, rotation of the rotation mechanism 803). .

In some embodiments, one or more of the affordances in the scrollable list of affordances 820 includes a respective athletic metric change affordance. For example, affordance 821 includes workout metric change affordance 831 and affordance 822 includes workout metric change affordance 832 . In one embodiment, user interface 810C is identical to user interface 610A (FIG. 6A). Accordingly, user interface 810C includes the same features and functionality as user interface 610A, as described above.

In some embodiments, while audio content is currently playing on device 800, device 800 receives an enabled setting of the workout audio playlist setting from an external device (eg, counterpart device 890) and , which will be described in more detail below (Figs. 8n to 8t). When the workout audio playlist setting is enabled, the workout playlist will automatically play in response to selection of the workout affordance. In one embodiment, a workout audio playlist is a list of audio content (eg, a list of songs) selected by the user to be played during a workout.

User input 815C is received at affordance 821 (FIG. 8F). In response to user input 815C, user interface 810D is displayed (FIG. 8G). User interface 810D (similar to user interface 610B) displays a countdown prior to tracking metrics by the physical activity tracking function associated with affordance 821 . In one embodiment, user interface 810D is identical to user interface 610B (FIGS. 6C-6F). Accordingly, user interface 810D includes the same features and functionality as user interface 610B, as described above.

In response to completion of the countdown, user interface 810E is displayed (FIG. 8H). User interface 810E provides a plurality of metrics 830 (eg, miles 830-1, active calories 830-2), average miles tracked by the physical activity tracking function during physical activity (eg, outdoor running). (830-3), and time (830-4). In one embodiment, user interface 810E is identical to user interface 610C (FIGS. 6G-6I). Accordingly, user interface 810E includes the same features and functionality as user interface 610C, as described above. In one embodiment, user interface 810E is displayed in response to user input 815C without display of intervening user interface 610D.

Additionally, in response to user input 815C (FIG. 8F), the audio application stops playing the currently playing song (eg, "Across the Land") and begins playing the workout audio playlist. For example, the currently playing song (eg, “Across the Land”) is not a song listed in the workout playlist. Accordingly, the currently playing song is canceled and replaced with playing the song in the workout playlist.

8I-8L , on the touch-sensitive display 802 while a physical activity tracking function is running (eg, tracking metrics associated with an outdoor running workout) and an audio application is playing audio content. User input 815D (eg, swipe gesture) is received. In response to user input 815D, user interface 810A is displayed. User interface 810A displays the audio content from the workout audio playlist because (as described above) playback of the workout audio playlist was initiated in response to user input 815C. In particular, user interface 810A includes audio content information 811 corresponding to the song "Feel the Burn" performed by "Drill Sergeant" from a workout audio playlist. Note that the user interface 810A includes a volume control 813 configured to control the volume of the currently playing song.

In some embodiments, when the setting is not enabled, the song currently playing continues to play, as can be seen in FIG. 8M.

Referring to FIGS. 8I to 8K , the user interface 810E includes paging dots 839-1, 839-2, and 839-3. Paging dots correspond to successive pages (or user interfaces). For example, paging dot 839-1 corresponds to motion control user interface (eg, similar to user interface 610H), paging dot 839-2 corresponds to user interface 810E, and paging dot 839-2 corresponds to user interface 810E. Dot 839-3 corresponds to user interface 810A. In response to user input, such as swipe gesture 815D, the currently displayed user interface 610E (FIG. 8I) is replaced with the display of a corresponding continuous user interface 810A (FIG. 8K). Note that when user interface 810E is displayed, paging dot 839-2 is highlighted (FIG. 8I). Similarly, when user interface 810A is displayed, paging dot 839-3 is highlighted (FIG. 8L).

8N-8T illustrate embodiments of counterpart device 890 being paired to device 800 . In some embodiments, counterpart device 890 can be device 100 , device 300 , device 500 , or a device that includes features of one or more of these devices. The counterpart device 890 includes a touch-sensitive display 891 . A user interface 892A is displayed on the touch-sensitive display 891 . Far-end device 890, as described herein, in some embodiments, when paired to device 800, can display application views and perform at least some of the same processes as device 800. can do. In some embodiments, the setting (eg, enabled or disabled) of the workout audio playlist setting is received from the counterpart device 890 (as described above).

Referring to FIG. 8N , user interface 892A provides a plurality of affordances associated with individual applications (eg, watch application, camera application, weather application, clock application, phone application, messaging application, mail application, and browser application). s 893. In one embodiment, affordance 893 - 1 is associated with a wristwatch application (eg, a wristwatch application for controlling various features and functions of device 800 ).

User input 815F is received at affordance 893-1 (FIG. 8O). In response to user input 815F on affordance 893-1, user interface 892B is displayed (FIG. 8P). User interface 892B enables device information 860 (eg, information related to device 800 paired with device 892), watch screens 861 (eg, device 800 to be displayed) various wrist watch screens), and a list 862 of application affordances corresponding to applications installed on the device 800 . List of application affordances 862, in some embodiments, corresponds at least in part to plurality of application affordances 805 displayed on user interface 810B on device 800 (FIG. 8C). List of application affordances 862 includes affordance 862 - 1 corresponding to an athletic application installed on device 800 .

User input 815G (eg, a tap gesture) is received at affordance 862-1 (FIG. 8Q). In response to user input 815G at affordance 862-1, user interface 892C is displayed (FIG. 8R). User interface 892C includes various workout application settings associated with the workout application installed on device 800 . In one embodiment, user interface 892C includes a workout audio playlist setup 870 (eg, “Workout Playlist Auto Play”). As shown in FIG. 8R , the setting of workout audio playlist settings 870 is enabled. Thus, when the workout audio playlist setting 870 is enabled (on the device 890), the workout audio playlist, as described above, includes an affordance within the scrollable list of affordances 820 (e.g., affordance 821). )) is automatically played by the audio application (on the device 800). In one embodiment, the setting of the workout audio playlist setting 870 (eg, the enabled setting) corresponds to the default setting on the device 890 . In another embodiment, the setting of workout audio playlist settings 870 (eg, the enabled setting) corresponds to user-selected settings on device 890 .

User interface 892C includes run autopause settings 871 . For example, if run autopause setting 871 is determined to be enabled, tracking of metrics associated with a running workout will determine that the user has stopped running for a predetermined amount of time (eg, 3 seconds). automatically paused when Alternatively, if the run autopause setting 871 is determined to be disabled, tracking of metrics associated with the running workout will be performed when it is determined that the user has stopped running for a predetermined amount of time (eg, 3 seconds). It continues (without automatically pausing).

Automatically stopping the song playing on the device when the workout playlist setting is enabled and initiating playback of the workout audio playlist on the device in response to selection of the workout causes the user to, at the same time, stop the currently playing song. and automatically initiate playback of the workout playlist, giving the user more control of the device. Automatically stopping the song playing on the device when the workout playlist setting is enabled and initiating playback of the workout audio playlist on the device in response to the selection of the workout, without requiring additional user input, can (e.g., improve the operability of the device and make the user-device interface more efficient (by helping the user provide appropriate inputs when operating/interacting with the device and reducing user errors), which further It reduces the power usage of the device and improves its battery life by enabling faster and more efficient use of the device.

Referring to FIG. 8S , user input 815H is received at workout audio playlist setup 870 . User input 815H is to switch the workout audio playlist setting from enabled to disabled (or from disabled to enabled). Referring to FIG. 8T , in response to user input 815H, workout audio playlist setting 870 is set to disabled. Thus, when the workout audio playlist setting 870 is disabled (on the device 890), the workout audio playlist, as described above, includes an affordance within the scrollable list of affordances 820 (e.g., affordance 821). )) is not automatically played by the audio application (on the device 800). For example, when workout audio playlist setting 870 is disabled (on device 890), selection of an affordance (e.g., affordance 821) in scrollable list of affordances 820, as described above, In response, the song currently playing by the audio application (on device 800) (e.g., "Across the Land") remains playing without interruption In one embodiment, set workout audio playlist 870 ) (eg, a disabled setting) corresponds to a default setting in device 890 .

9 is a flow diagram illustrating a method for automatically playing a workout playlist based on workout playlist settings in response to selecting an workout affordance. Method 900 is performed in a device (eg, 100, 300, 500, 600, 800) having one or more processors and memory. Some actions of method 900 are optionally combined, some actions are optionally reordered, and some actions are optionally omitted.

As described below, method 900 provides, among other things, an intuitive way to automatically play a workout playlist based on workout playlist settings in response to selecting an workout affordance. This method reduces the cognitive burden on the user by automatically playing the workout playlist based on the workout playlist settings, thereby creating a more efficient human-machine interface. For battery-powered computing devices, allowing a user to select an exercise from a list of exercises and initiate a physical activity tracking function is faster and more efficient to conserve power and reduce the time between battery charges. increase

At block 910 , while the audio application is playing audio content (eg, “Across the Land”), device 800 displays a scrollable list of affordances associated with physical activities (eg, 820 ).

At block 920, while the audio application is playing audio content, user input (eg, 815C) is received at an affordance (eg, 821) of the scrollable list of affordances.

At block 930, in response to receiving user input at the affordance, the physical activity tracking function associated with the selected affordance is initiated, and it is determined whether the workout audio playlist setting is enabled (e.g., device 890 ) from which an enabled setting is received).

At block 940, upon determining that the exercise audio playlist setting is enabled, audio content currently playing on the device (eg, “Across the Land”) is stopped, and playing the exercise audio playlist (eg, “Across the Land”). Playback of “Feel the Burn”) is initiated on the device (eg, device 800). At block 950, upon a determination that the workout audio playlist setting is disabled (eg, a disabled setting received from device 890), the audio content currently playing on the device (eg, “Across the Land” ) continues.

In some embodiments, while the body activity tracking function is running (eg, tracking metrics 830) and the audio application is playing audio content (eg, "Across the Land" is playing). , an audio application of an audio application that receives a user input (eg, 815D) corresponding to a request to display an audio application control user interface (eg, 8910A), and plays audio content in response to the user input (eg, 815D). A control user interface (eg, 810A) is displayed.

In some embodiments, prior to receiving user input (eg, 815C) at affordance (eg, 821 ), setting (eg, enabled or disabled) of the workout audio playlist setting from an external device (eg, 890 ) ) is received.

Note that details of the processes described above with respect to method 900 (eg, FIG. 9 ) are also applicable in a similar manner to the methods described below. For example, method 900 optionally includes one or more of the features of the various methods described above with reference to method 1300. For example, tracking metrics by the physical activity tracking function in method 900 may also track heart rate information, as described in method 1300 . For brevity, these details are not repeated below.

10A-10N depict example user interfaces associated with a messaging application, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 11 .

10A shows a device 1000 having a touch-sensitive display 1002 . Device 1000 has various input mechanisms that receive user input, such as rotatable input mechanism 1003 that can receive rotatable input (and can also receive push input) and push user input. An input mechanism 1004 is included. In some embodiments, device 1000 includes some or all of the features of device 100 , device 300 , device 500 , device 600 , or device 800 .

10A includes a user interface 1010A. User interface 1010A includes a message 1020 (eg, text message or email) received from an external device. Message 1020 includes workout information. For example, workout information may include person 1020-1 (eg, "John completed a workout!"), type of workout 1020-2 (eg, "Outdoor Run"), and workout metrics 1020-3. ) (eg, 3.00 miles, 326 active calories, and 351 total calories).

In some embodiments, external device 1020 (which sent message 1020 ) may send some or all of the features of device 1000 (or device 100 , device 300 , or device 500 ). includes In one embodiment, an external device is a device that is a counterpart device to another external device (eg, counterpart device 690 described above). In one embodiment, message 1020 is written by an athletic application (or athletic tracking application) on an external device, where the athletic application generates the athletic information included in message 1020 . Further, in one embodiment, the athletic application on the external device includes some or all of the features as an athletic application described herein (eg, an athletic application as shown at least in FIG. 6A ).

User interface 1010A also includes reply affordance 1022-1 (eg, configured to allow a user to create a reply message), mute affordance 1022-1 (eg, to view subsequent messages from an external device). configured to mute), and close affordance 1022-3 (eg, configured to close message 1020 without sending a reply message).

User input 1015A is received at reply affordance 1022-1 (FIG. 10B). Referring to FIGS. 10C and 10D , in response to user input 1015A at reply affordance 1022-1 and in response to a determination that message 1020 includes athletic information, user interface 1010B is displayed. . User interface 1010B is configured to allow a user to compose a reply message to message 1020 . User interface 1010B includes a list of predefined responses 1030 corresponding to message 1020 containing workout information. Predefined responses 1030 may, in some embodiments, include predefined response 1030-1 (eg, “how'd you get so good”), predefined response 1030-2 (eg, “how'd you get so good”). , "# goals"), predefined response 1030-3 (e.g., "Hands down, you're the best"), predefined response 1030-4 (e.g., "what's your secret?") , predefined response 1030-5 (eg, "Hello!"), predefined response 1030-6 (eg, "what's up?"), predefined response 1030-7 (eg, "on my way"), and a predefined response 1030-8 (eg, "ok").

In addition, user interface 1010B includes an affordance 1031 configured to allow a user to record an audio reply to message 1020, a user to send emojis to a reply message to message 1020. An affordance 1032 configured to allow a user to select, an affordance 1033 configured to allow a user to send a handwritten reply message (or sticker) to the message 1020, and a reply message (handwritten input) to the user to the message 1020. and an affordance 1034 configured to enable transmission of text including text generated from.

In one embodiment, upon a determination that message 1020 does not contain athletic information (eg, text containing “Hi Jane”), the message is displayed on device 1000 . However, predefined responses 1030 are not displayed on device 1000 .

As shown in FIG. 10D, user input 1015B is received in predefined response 1030-2. In response to user input 1015B in predefined response 1030-2, a reply message to message 1020 (eg, reply message 1050 in FIG. 10E) is composed. In one embodiment, subsequent to receiving user input 1015B in predefined response 1030-2, an intermediary user interface prompting the user to compose a reply message is displayed. In response to a user input to compose a reply message, a reply message is created.

10E and 10F show a user interface 1010C (eg, a text message user interface) displayed on the counterpart device 1065 (eg, the counterpart device for the device 1000) and the external device 1090. Referring to FIG. 10E , a reply message 1050 is displayed on the counterpart device 1065 . In one embodiment, a reply message 1050 is displayed on device 1000 . The reply message 1050 is a selected predefined message 1030-2 (eg, "#goals" selected on device 1000 in FIG. 10C) and athletic information, such as a person 1020-1 (eg, "John" ), the type of workout 1020-2 (eg, “Outdoor Run”), and workout metrics 1020-3 (eg, 3.00 miles). At the counterpart device 1065, the reply message 1050 is displayed inline with other messages (from the external device 1090). Referring to FIG. 10F , a reply message 1050 is received by an external device 1090 and displayed on the external device 1090 . On the external device 1090, the reply message 1050 is displayed inline with the other messages (from the far device 1065).

Generating a reply message containing athletic information and a selected predefined response from a received message allows a user to quickly compose a reply message that automatically includes athletic information (from a received message); allows to generate reply messages with minimal user input. Reducing the number of inputs required to perform an action improves the operability of the device (eg, by helping the user provide appropriate inputs when operating/interacting with the device and reducing user mistakes) and -makes the device interface more efficient, which further reduces the device's power usage and improves battery life by enabling the user to use the device more quickly and efficiently.

10G shows a user interface 1010C displayed on device 1000 . User interface 1010C displays a person 1020-1 (e.g., "John completed a workout!"), a selected predefined message 1030-2 (e.g., "#goals"), and a reply message delivery indication 1051. ) (eg, "Delivered"). The reply message delivery indication 1051 indicates that the reply message 1050 (to the message 1020) has been sent to the external device 1090.

10H includes a user interface 1010A. User interface 1010A includes a message 1040 (eg, text message or email) received from an external device. Message 1040 includes workout information. For example, exercise information may include the person 1040-1 (eg, "John earned an achievement"), the type of exercise 1040-2 (eg, "Outdoor Run"), and the user of the external device (eg, John ) includes information identifying the achievement sticker 104-3 indicating that exercise achievement has been completed. In one embodiment, message 1040 is composed by an athletic application on an external device, where the athletic application generates athletic information included in message 1040 . Further, in one embodiment, the athletic application on the external device includes some or all of the features as an athletic application described herein (eg, an athletic application as shown at least in FIG. 6A ).

User interface 1010A also includes reply affordance 1042-1 (eg, configured to allow a user to create a reply message), mute affordance 1042-1 (eg, to view subsequent messages from an external device). configured to mute), and close affordance 1042-3 (eg, configured to close message 1020 without sending a reply message).

User input 1015C is received at reply affordance 1042-1 (FIG. 10I). Referring to FIGS. 10J and 10K , in response to user input 1015C at reply affordance 1042-1 and in response to a determination that message 1040 includes athletic information, user interface 1010B is displayed. . User interface 1010B is configured to allow a user to compose a reply message to message 1040 . User interface 1010B includes a list of predefined responses 1043 corresponding to message 1040 containing workout information. Predefined responses 1043 may, in some embodiments, include predefined response 1043-1 (eg, “you're on fire!”), predefined response 1043-2 (eg, “you're on fire!”) "INCREDIBLE"), predefined response 1043-3 (e.g. "keep it up!"), predefined response 1043-4 (e.g. "you inspire me"), predefined response 1043 -5) (eg "Hello!"), predefined response 1043-6 (eg "what's up?"), predefined response 1043-7 (eg "on my way"), and a predefined response 1043-8 (eg, “ok”).

In addition, user interface 1010B includes an affordance 1031 configured to allow a user to record an audio reply to message 1040, a user to select emojis for a reply message to message 1040. an affordance 1032 configured to allow a user to send a handwritten reply message (or sticker) to message 1040, and an affordance 1033 configured to allow a user to send a reply message to message 1040 (generated from handwriting input). and an affordance 1034 configured to enable transmission of text).

In one embodiment, upon a determination that message 1040 does not contain athletic information (eg, text containing “Hi Jane”), the message is displayed on device 1000 . However, predefined responses 1043 are not displayed on device 1000 .

User input 1015D is received in predefined response 1043-4. In response to user input 1015D in predefined response 1043-4, a reply message to message 1040 is created (eg, reply message 1060 in FIG. 10L). In one embodiment, subsequent to receiving user input 1015D in predefined response 1043-4, an intermediary user interface prompting the user to compose a reply message is displayed. In response to user input to compose a reply message, a reply message to message 1040 is created.

10L and 10M show a user interface 1010C (eg, a text message user interface) displayed on the counterpart device 1065 (eg, the counterpart device for device 1000) and the external device 1090. Referring to FIG. 10L , a reply message 1060 is displayed on the counterpart device 1065 . In one embodiment, reply message 1060 is displayed on device 1000 . The reply message 1060 is a selected predefined message 1043-4 (eg, "You inspire me" selected in device 1000 of FIG. 10K) and exercise information, such as a person 1040-1 (eg, "John earned an achievement"), and information identifying the achievement sticker (1040-3). At the counterpart device 1065, the reply message 1060 is displayed inline with other messages (from the external device 1090). Referring to FIG. 10M , a reply message 1060 is received by an external device 1090 and displayed on the external device 1090 . On the external device 1090, the reply message 1060 is displayed inline with the other messages (from the far device 1065).

10N shows a user interface 1010C displayed on device 1000 . User interface 1010C displays a person 1040-1 (eg, "John earned an achievement"), a selected predefined message 1043-4 (eg, "you inspire me"), and an indication of delivery of a reply message 1051 ) (eg, "Delivered"). Reply message delivery indication 1051 indicates that reply message 1060 (to message 1020) has been sent to external device 1090.

11 is a flow diagram illustrating a method for composing a reply message containing selected predefined responses and workout information. Method 1100 is performed on a device (eg, 100, 300, 500, 600, 800, or 1000) having one or more processors and memory. Some actions of method 1100 are optionally combined, some actions are optionally reordered, and some actions are optionally omitted.

As described below, method 1100 provides, among other things, an intuitive way for a user to quickly compose a reply message that automatically includes workout information (from a received message), and allows the user to Enables the creation of reply messages with minimal user input. This method reduces the cognitive load on the user by automatically including in the reply message the exercise information from the received message. For battery-powered computing devices, allowing a user to select an exercise from a list of exercises and initiate a physical activity tracking function is faster and more efficient to conserve power and reduce the time between battery charges. increase

At block 1110 , a message (eg 1020 ) is received at the device (eg 1000 ) from an external device (eg 1090 ).

At block 1120, one or more predefined responses to the received message in response to a determination that the message (eg, 1020) includes athletic information (eg, 1020-1, 1020-2, or 1020-3). (eg 1030) is displayed.

At block 1130, user input (eg, 1015B) corresponding to selecting a predefined response (eg, 1030-2) of one or more predefined responses is received.

At block 1140, subsequent to receiving the user input (eg, 1015B), a reply message (eg, 1050) is composed, where the reply message includes the selected predefined response (eg, 1030-2) and workout information. (eg, 1020-1, 1020-2, or 1020-3).

In some embodiments, a message (eg, 1020) is displayed on the device (eg, 1000). In some embodiments, the composed message (eg, 1050) is sent to an external device (eg, 1090) in response to user input (eg, 1015B) to select a predefined response (eg, 1030-2). In some embodiments, upon a determination that the message (eg, 1020) does not include athletic information, the message is displayed (eg, device without subsequently displaying one or more predefined responses (eg, 1030)). (displayed at 1000).

In some embodiments, athletic information is a person (eg, 1020-1), athletic metrics (eg, 1020-3), type of exercise (eg, 1020-2), or achievement sticker (eg, 1040-3). contains information identifying the

It is noted that details of the processes described above with respect to method 1100 (eg, FIG. 11 ) are also applicable in a similar manner to the methods described above. For example, method 1100 optionally includes one or more of the features of the various methods described above with reference to method 700. For example, method 1100 includes workout metrics similar to those described with respect to method 700 . For brevity, these details are not repeated below.

12A-12M show example user interfaces associated with a heart rate tracking application, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 13 .

12A shows a device 1200 having a touch-sensitive display 1202 . Device 1200 has various input mechanisms that can receive user input, such as rotatable input mechanism 1203 that can receive rotatable input (and can also receive push input) and push user input. An input mechanism 1204 is included. In some embodiments, device 1200 includes some or all of the features of device 100, device 300, device 500, device 600, device 800, or device 1000. do.

Referring to FIGS. 12A and 12B , a user interface 1210A of a heart rate application is displayed on the touch-sensitive display 1202 . User interface 1210A includes list 1220 of affordances. List of affordances 1220 includes affordances 1221 associated with current heart rate (of a user of device 1200), affordances 1222 associated with heart rate during a physical activity (eg, outdoor running), and during a breathing session of a breathing application. It includes an affordance 1223 associated with the heart rate of .

One or more affordances in list of affordances 1220 identify a physical activity associated with the affordance. For example, affordance 1221 identifies activity 1221-1 (eg, the user's activity associated with the current heart rate), affordance 1222 identifies activity 1222-1 (eg, outdoor running), and , affordance 1223 identifies activity 1223-1 (eg, a breathing session).

One or more affordances in list of affordances 1220 identify heart rate information associated with the physical activity. For example, affordance 1221 identifies heart rate information 1221-2 (eg, 75 BPM, 69 resting). Affordance 1222 identifies heart rate information 1222-2 (eg, an average heart rate of 138 BPM), and affordance 1223 identifies heart rate information 1223-2 (eg, 60 BPM). In one embodiment, heart rate information is measured by a body activity tracking sensor of device 1200 .

Displaying a list of affordances that identify physical activity and associated heart rate information enables a user to quickly view physical activity and associated heart rate information and select affordances to observe additional heart rate information associated with physical activity. . Reducing the number of inputs for observing additional heart rate information improves the operability of the device (eg, by helping the user provide appropriate inputs when operating/interacting with the device and reducing user mistakes) It makes the user-device interface more efficient, which further reduces the power usage of the device and improves its battery life by enabling the user to use the device more quickly and efficiently.

User input 1215A is received at affordance 1220-1 (FIG. 12B). In response to user input 1215A at affordance 1220-1, user interface 1210B is displayed (FIG. 12C). User interface 1210B includes graph 1230 . Graph 1230 is a graph of the user's current heart rate (eg, today's heart rate) over a period of time. User interface 1210B also includes activity 1221-1 (eg, the user's activity associated with the current heart rate) and heart rate information 1221-2 (eg, 75 BPM, 69 plateau).

Graph 1230 includes physical activity points corresponding to heart rates of various physical activities. For example, graph 1230 shows physical activity points 1230-1 corresponding to current heart rate, physical activity points 1230-2 corresponding to outdoor running, and physical activity points 1230-3 corresponding to breathing sessions. ). As shown in FIG. 12C , the physical activity point 1230 - 1 corresponding to the current heart rate is highlighted because the current heart rate information corresponds to the selected affordance 1221 .

User input 1215B (eg, rotational input) is received at rotatable input mechanism 1203 (FIG. 12D). In response to user input 1215B on rotatable input mechanism 1203, activity 1222-1 (eg, outdoor running) and corresponding metrics (eg, 142 high BPM, 138 BPM average) are displayed ( Figure 12e). Additionally, physical activity points 1230-2 corresponding to outdoor running are highlighted.

In response to additional user input 1215B on rotatable input mechanism 1203, activity 1222-3 (eg, breathing session) and corresponding metrics (eg, 60 BPM) are displayed (FIG. 12F). Additionally, the body activity point 1230-3 corresponding to the breathing session is highlighted.

Referring to FIGS. 12G and 12H , a user input 1215C is received at an affordance 1231 . In response to user input 1215C on affordance 1231, previous user interface 1210A is displayed (FIG. 12H).

User input 1215D is received at affordance 1222 (FIG. 12H). In response to user input 1215D on affordance 1222, user interface 1210B is displayed (FIG. 12I). User interface 1210B includes graph 1240 . Graph 1240 is a graph of the user's heart rate during an outdoor run over the duration of the outdoor run. User interface 1210B also includes activity 1221-2 (eg, outdoor running) and corresponding metrics (eg, 142 high BPM and 116 BPM average). Graph 1240 also includes average heart rate 1240 - 1 (eg, 116 BPM) over the duration of the outdoor run.

In some embodiments, user input (eg, a tap gesture) is received on touch-sensitive display 1202 ( FIG. 12I ). In response to user input on touch-sensitive display 1202 , user interface 1210B displays graph 1245 . Graph 1245 is a graph of the user's heart rate during a recovery period (or cool down period) after completion of physical activity (eg, outdoor running). For example, graph 1245 shows heart rate information 1245-1 at a first duration after outdoor running (e.g., 98 BPM one minute after outdoor running), heart rate information at a second duration after outdoor running ( 1245-2) (eg, 74 BPM after 2 minutes after outdoor running), and heart rate information 1245-3 at a third duration after outdoor running (eg, 68 BPM after 3 minutes after outdoor running). Additionally, graph 1245 shows a first heart rate point 1246-1 corresponding to heart rate information 1245-1 (eg, 98 BPM), and a corresponding first heart rate point 1246-1 corresponding to heart rate information 1245-2 (eg, 74 BPM). A second heart rate point 1246-2 and a third heart rate point 1246-3 corresponding to the heart rate information 1245-3 (eg, 68 BPM).

Referring to FIGS. 12K and 12L , a user input 1215E is received at an affordance 1231 . In response to user input 1215E on affordance 1231, previous user interface 1210A is displayed (FIG. 12L).

User input 1215F is received at affordance 1223 (FIG. 12L). In response to user input 1215F at affordance 1223, user interface 1210B is displayed (FIG. 12M). User interface 1210B includes graph 1250 . Graph 1250 is a graph of the user's heart rate during a breathing session over the duration of the breathing session. User interface 1210B also includes activity 1223-1 (eg, breathing session) and heart rate information 1223-2 (eg, 60 BPM) associated with the breathing session. Graph 1250 includes average heart rate 1250-1 over the duration of the breathing session.

13 is a flow diagram illustrating a method for displaying a scrollable list of affordances associated with heart rate information. Method 1300 is performed on a device (eg, 100, 300, 500, 600, 800, 1000, or 1200) having one or more processors and memory. Some actions of method 1300 are optionally combined, some actions are optionally reordered, and some actions are optionally omitted.

As described below, method 1300 provides, among other things, an intuitive way to select an affordance that allows for additional heart rate information to be observed. This method reduces the cognitive burden on the user by enabling the user to quickly observe multiple physical activities and associated heart rate information. For battery-operated computing devices, enabling a user to view multiple physical activities and associated heart rate information saves power faster and more efficiently and increases the time between battery charges.

At block 1310, a scrollable list of affordances associated with heart rate information (eg, 1220) is displayed. The scrollable list of affordances includes at least a first affordance (eg 1221 ) and a second affordance (eg 1222 ). A first affordance (eg, 1221) identifies a first physical activity (eg, 1221-1) and first heart rate information (eg, 1221-2), where the first heart rate information is measured by a physical activity tracking sensor. do. A second affordance (eg, 1222) identifies a second physical activity (eg, 1222-1) and second heart rate information (eg, 1222-2), where the second heart rate information is measured by a physical activity tracking sensor. do. The second heart rate information (eg, 1222-2) is different from the first heart rate information (eg, 1221-2).

At block 1320, user input (eg, 1215A) is received.

At block 1330, based on a determination that the user input corresponds to a first affordance (eg, 1221), additional first heart rate information (eg, 1230) is displayed.

At block 1340, in response to a determination that the user input corresponds to the second affordance, additional second heart rate information (eg, 1240) that is different from the first additional heart rate information (eg, 1230) is displayed.

In some embodiments, the additional first heart rate information or the additional second heart rate information is a graph of heart rate over time (eg, 1240), a graph of average heart rate over time (eg, 1240-1), over time A graph of breathing heart rate over a predetermined period of time (eg, 1250), a graph of current heart rate over a predetermined period of time (eg, 1230), a graph of exercise heart rate over time (eg, 1240), or at completion of an exercise over a predetermined period of time. Include a graph of the heart rate that follows (eg, 1245). In one embodiment, the additional first heart rate information is displayed concurrently with the first heart rate information (eg, 1210B).

Note that details of the processes described above with respect to method 1300 (eg, FIG. 13 ) are also applicable in a similar manner to the methods described below. For example, method 1300 optionally includes one or more of the features of various methods described below with reference to method 1500. For example, method 1300 includes, in some embodiments, displaying a heart rate affordance in accordance with a determination that the heart rate data satisfies a heart rate warning criterion. For brevity, these details are not repeated below.

14A-14O show example user interfaces associated with a heart rate tracking application, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 15 .

14A shows a device 1400 having a touch-sensitive display 1402 . Device 1400 has various input mechanisms that receive user input, such as rotatable input mechanism 1403 that can receive rotatable input (and can also receive push input) and push user input. An input mechanism 1404 is included. In some embodiments, device 1400 is one of the features of device 100, device 300, device 500, device 600, device 800, device 1000, or device 1200. include some or all

Referring to FIG. 14A , a user interface 1410A is displayed on the touch-sensitive display 1402 . User interface 1410A includes heart rate information 1420 (eg, 75 BPM, 2 minutes ago). Heart rate information 1420 is the current heart rate of the user of device 1400 . User interface 1410A includes one or more affordances associated with individual applications (eg, affordance 1421 associated with an athletic application, and affordance 1422 associated with an activity tracking application). Also, the user interface 1410A includes time, date, temperature, and the like.

User input 1415A corresponding to heart rate information 1420 is received at touch-sensitive display 1402 (FIG. 14B). In response to user input 1415A on touch-sensitive display 1402, user interface 1415B is displayed (FIG. 14C). User interface 1410B, in some embodiments, is similar to user interface 1210A (FIG. 12A) described above. User interface 1410B includes affordance 1421 associated with the current heart rate of the user of device 1400 . Affordance 1421 includes physical activity 1421-1 (eg, the user's current activity associated with the current heart rate), and heart rate information 1421-2 (eg, 75 BPM measured 2 minutes ago (from the current time)). identify

While tracking heart rate data corresponding to data received from the body activity tracking sensor of device 1400 (e.g., the user's current heart rate), the heart rate data satisfies a heart rate warning criterion (e.g., the tracked heart rate data is arrhythmia). i) is determined. In response to a determination that the heart rate data satisfies the heart rate warning criteria (eg, the tracked heart rate data was determined to be arrhythmic), user interface 1410C is displayed (FIG. 14D). User interface 1410C includes a heart rate warning affordance 1430 (eg, “Heart Health, Possible Arrhythmia Detected”) to warn the user that the user's tracked heart rate data meets heart rate warning criteria.

In one embodiment, the heart rate warning criteria include criteria based on a heart rate exceeding a heart rate threshold. For example, an instantaneous heart rate exceeds a predetermined heart rate threshold (eg, a heart rate greater than 100 BPM, or a heart rate less than 60 BPM), where exceeding the predetermined heart rate threshold indicates an arrhythmia. Instantaneous heart rate can be determined by measuring the inter-beat-interval between two consecutive heart rates. Instantaneous heart rate is based on a single interval (between successive heart beats). An instantaneous heart rate can be converted to beats per minute, and therefore such instantaneous heart rates can differ between successive beats (intervals).

In one embodiment, the heart rate warning criteria include criteria that are satisfied when the heart rate pattern matches the heart rate warning pattern. For example, a pattern of instantaneous heart rate (eg, irregular instantaneous heart rate between successive beats) is matched with a heart rate warning pattern indicative of an arrhythmia.

Displaying a heart rate warning icon when the user's tracked heart information is determined to indicate that the user may have an arrhythmia immediately alerts the user that he may have a heart condition that must be diagnosed by a medical professional. Performing an action when a set of conditions are met without requiring additional user input (e.g., by helping the user provide appropriate inputs and reducing user errors when operating/interacting with the device) improves the operability of the device and makes the user-device interface more efficient, which further reduces the power usage of the device and improves its battery life by enabling the user to use the device more quickly and efficiently.

User input 1415B is received at heart rate warning affordance 1430 (FIG. 14D). In response to receiving user input 1415B on heart rate warning affordance 1430, user interface 1410D is displayed (FIG. 14E). User interface 1410D provides information directing the user that additional details related to heart rate data may be accessed from the other party's device to device 1400 .

14F-14O show counterpart device 1490 being paired to device 1400 . The counterpart device 1490 includes a touch-sensitive display 1491 . Far-end device 1490, as described herein, in some embodiments, when paired to device 1400, can display application views and perform at least some of the same processes as device 1400. can do.

Referring to FIG. 14F , user interface 1492A includes a list of affordances 1493 associated with individual applications (eg, watch application, camera application, weather application, clock application, and health application). Affordance 1493-1 is associated with a health application. The health application displays heart rate data, which will be described in more detail below. Additionally, in some embodiments, a health application on counterpart device 1490 is configured to control various features and functions of a corresponding health application on device 1400 .

User input 1415C is received at affordance 1493-1 associated with the health application (FIG. 14G). In response to user input 1415C, user interface 1492B is displayed (FIG. 14H). User interface 1492B includes various affordances 1494 associated with health data. For example, user interface 1492B may include an affordance 1494-1 associated with activity data, an affordance 1494-2 associated with heart health data, an affordance 1494-3 associated with mindfulness data, and an affordance 1494-3 associated with nutrition data. and an affordance 1494-4 associated with and an affordance 1494-5 associated with sleep data.

User input 1415D is received at affordance 1494-2. User input 1415D is received at affordance 1494-2 (FIG. 14I). In response to user input 1415D, user interface 1492C is displayed (FIG. 14J). User interface 1492C includes graph 1495 . Graph 1495 includes heart rate data that meets heart rate warning criteria over a period of time. For example, graph 1495 is a tachogram of heart rate data (satisfying heart rate warning criteria) over a predetermined period of time (eg, 21 seconds). Graph 1495 includes normal heart rate 1495-1 over the same time period. A graph 1495 is displayed following receipt of user input 1415B at heart alert affordance 1430 (FIG. 14D).

User interface 1492C includes graph type 1496-1 (eg, tachogram), heart rate data tracking period 1496-2 (eg, 21 seconds), additional graph information 1496-3, user commands 1496 -4), and cardiac alert settings 1496-5 (eg, enabled or disabled). In one embodiment, the settings of heart rate alert settings 1496-5 correspond to user-selected settings on device 1490. In another embodiment, the settings of heart rate alert settings 1496-5 correspond to default settings in device 1490.

User interface 1492C includes scrollable cardiac data affordances 1497-1, 1497-2, and 1497-3. The scrollable heart data affordances are associated with established heart rate data corresponding to data received from the body activity tracking sensor. Scrollable heart data affordances identify the date and time heart rate data was received from the body activity tracking sensor. For example, cardiac data affordance 1497-1 is the date 1498-1 (eg, today November 16, 2016) and the time 1498-2 (eg, today) that the associated data was received from the body activity tracking sensor. 5:21pm).

Graph 1495 corresponds to heart rate data associated with affordance 1497-1 (FIG. 14J). Accordingly, affordance 1497-1 is highlighted relative to affordances 1497-2 and 1497-3.

Referring to FIGS. 14K-14M , user input 1415E (eg, a swipe gesture) is received near scrollable cardiac data affordances 1497-1, 1497-2, and 1497-3. In response to user input 1415E, cardiac data affordances 1497-1, 1497-2, and 1497-3 are scrolled to a new position. For example, affordances are translated to the left such that at least affordance 1497-3 is fully displayed.

Referring to FIGS. 14N and 14O , a user input 1415F is received at an affordance 1497-3. In response to user input 1415F received at affordance 1497-3, graph 1495 is replaced by graph 1499 (FIG. 14O). Graph 1499 corresponds to heart rate data associated with affordance 1497-3. Accordingly, affordance 1497-3 is highlighted relative to affordances 1497-1 and 1497-2. It should be understood that heart rate data associated with at least one affordance (eg, affordances 1497-1, 1497-2, or 1497-3) is heart rate data that satisfies the heart rate warning criteria. In some embodiments, the heart rate data associated with at least one affordance (eg, affordance 1497-1, 1497-2, or 1497-3) is heart rate data that does not satisfy a heart rate warning criterion.

It should be understood that heart rate data (eg, heart rate data that satisfies heart rate warning criteria) may be transmitted to an external device. For example, the heart rate data can be sent (eg, email or text) to the healthcare professional's device so that the healthcare professional can access/view the heart rate data.

15 is a flow diagram illustrating a method for displaying a heart rate warning affordance. Method 1500 is performed on a device (eg, 100, 300, 500, 600, 800, 1000, 1200, or 1400) having one or more processors and memory. Some actions of method 1500 are optionally combined, some actions are optionally reordered, and some actions are optionally omitted.

As described below, method 1500 provides, among other things, an intuitive way to immediately alert a user to possible heartbeat irregularities. This method reduces the cognitive burden on the user by enabling the user to quickly observe heart rate warnings and subsequently observe heart rate data that meets the heart rate warning criteria. For battery-operated computing devices, enabling a user to observe heart rate data that meets heart rate warning criteria saves power faster and more efficiently and increases the time between battery charges.

At block 1510, while tracking heart rate data corresponding to the data received from the body activity tracking sensor (e.g., tracking current heart rate data), whether the heart rate data satisfies a heart rate warning criterion (e.g., the heart rate data matching with an irregular heartbeat pattern) is determined.

At block 1520, upon determining that the heart rate data satisfies the heart rate warning criteria, a heart rate warning affordance (eg, 1430) is displayed.

At block 1530, user input corresponding to the heart rate warning affordance (eg, 1415B) is received.

At block 1540, following receiving user input corresponding to the heart rate warning affordance, a graph (eg, 1495) is displayed containing heart rate data that meets the heart rate warning criteria over a period of time. At block 1550, upon determining that the heart rate data (eg, the user's current heart rate data) does not satisfy the heart rate warning criteria, withholds display of the heart rate warning affordance (eg, 1430 is not displayed).

In some embodiments, graph 1495 includes an expected or normal heart rate over a period of time 1495-1. In some embodiments, the heart rate warning criteria includes criteria based on a heart rate exceeding a heart rate threshold. In some embodiments, the heart rate warning criteria include criteria that are satisfied when the heart rate pattern matches the heart rate warning pattern. In some embodiments, heart rate data is instantaneous heart rate acceleration. In some embodiments, graph 1495 of heart rate data is a tachogram.

In some embodiments, heart rate data is transmitted to an external device. For example, heart rate data is sent to the medical professional's device (eg, email, text).

Note that details of the processes described above with respect to method 1500 (eg, FIG. 15 ) are also applicable in a similar manner to the methods described below. For example, method 1500 optionally includes one or more of the features of the various methods described above with reference to method 700. For example, method 1500 includes, in some embodiments, initiating a body activity tracking function in response to selection of an affordance in a scrollable list of affordances. For brevity, these details are not repeated below.

The foregoing description, for explanatory purposes, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teachings. The embodiments were selected and described to best explain the principles of the techniques and their practical applications. Thus, those skilled in the art will be able to best utilize the techniques and various embodiments using various modifications as suited to the particular use contemplated.

Although the invention 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. Such changes and modifications are to be understood to be included within the scope of the disclosure and examples as defined by the claims.

As noted above, one aspect of the present technology is the collection and use of data available from various sources to improve the display to users of body activity information. The present invention contemplates that, in some cases, this collected data may include personal information data that can be used to uniquely identify, or to contact or locate a particular individual. Such personal data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records relating to a user's health or fitness level (e.g., vital signs). measurements, medication information, athletic information), date of birth, or any other identifying or personal information.

The present invention recognizes that the use of such personal information data in the present technology can be used to the benefit of users. For example, personal information data may be used to provide a user with a history of his/her physical activity. Accordingly, the use of such personal information data enables feedback to the user regarding the user's physical activity. Additionally, other uses for personal information data that benefit the user are also contemplated by the present invention. For example, health and fitness data can be used to provide insight into a user's general wellness, or can be used as positive feedback to individuals using technology to pursue wellness goals.

The present invention contemplates that entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will adhere to well-established privacy policies and/or privacy practices. In particular, such entities must implement and consistently use privacy policies and practices that are generally recognized to meet or exceed industrial or administrative requirements for keeping personal information data private and secure. Such policies should be easily accessible by users and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and appropriate uses of the entity, and should not be shared or sold outside of these legitimate uses. Further, such collection/sharing must occur after receiving the notified consent of the users. Additionally, such entities are committed to taking any necessary steps to protect and secure access to such personal information data and to ensure that others having access to such personal information data adhere to their privacy policies and procedures. should be considered Moreover, such entities may themselves be evaluated by third parties to demonstrate their adherence to widely accepted privacy policies and practices. Additionally, policies and practices must be tailored to the specific types of personal information data collected and/or accessed and adapted to applicable laws and standards, including jurisdiction specific considerations. For example, in the United States, the collection of certain health data or access thereto may be governed by federal and/or state laws, such as the US Health Insurance Portability and Accountability Act (HIPAA); Health data from other countries may be subject to different regulations and policies and should be treated accordingly. Accordingly, different privacy practices must be maintained for different personal data types in each country.

Notwithstanding the foregoing, the present invention also contemplates embodiments in which a user selectively blocks use of, or access to, personal information data. That is, the present invention contemplates that hardware and/or software components may be provided to prevent or block access to such personal information data. For example, in the case of physical activity services, the technology allows users to "opt in" or "opt out" of participation in the collection of personal information data during registration for the service. It can be configured to allow In another example, users may choose not to provide location information for targeted content delivery services or at any time thereafter. In another example, users may choose not to provide precise physical activity information but allow delivery of general physical activity information. In addition to providing "I agree" and "I do not agree" options, the present invention contemplates providing notifications regarding access or use of personal information. For example, a user may be notified upon downloading an app that their personal data will be accessed, and then reminded immediately before the personal data is accessed by the app.

It is also the intention of the present invention that personal information data be managed and processed in a manner that minimizes the risk of unintended or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data when it is no longer needed. In addition, and when applicable, including as applicable to certain health-related applications, data de-identification may be used to protect user privacy. Control how data is stored, where appropriate, by removing certain identifiers (eg, date of birth, etc.); by controlling the amount or specificity of stored data (eg, collecting location data at the city level rather than at the address level); De-identification may be facilitated by (eg, by aggregating data across users), and/or by other methods.

Thus, while the present invention broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present invention also contemplates that various embodiments may also be implemented without the need to access such personal information data. consider that That is, various embodiments of the present technology are not rendered inoperable due to a lack of all or some of such personal information data. For example, information may be presented using non-personal information data or body activity based on the most basic minimal amount of personal information.

Claims (10)

As a method,
In an electronic device having a display,
Receiving a message from an external device;
Upon determining that the message contains athletic information:
displaying, via the display, one or more predefined responses to the message;
receiving user input corresponding to selecting a predefined response from among the one or more predefined responses; and
Subsequent to receiving the user input, composing a response message, the response message comprising:
the selected predefined response, and
including the exercise information; and
and upon a determination that the message does not contain athletic information, presenting the message via the display without presentation of the one or more predefined responses. The method of claim 1 , wherein the athletic information includes information identifying a person. The method of claim 1 , wherein the athletic information includes athletic metrics. The method of claim 1 , wherein the exercise information includes a type of exercise. The method of claim 1 , wherein the athletic information includes achievement stickers. According to claim 1,
In response to receiving the user input, further comprising transmitting the response message to the external device. According to claim 1,
The method further comprising displaying the message through the display. The method of claim 1 , wherein composing the response message occurs automatically in response to receiving the user input. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, the one or more programs for performing the method of any one of claims 1 to 8. A non-transitory computer-readable storage medium containing instructions. As a computer system,
display;
one or more processors; and
a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any one of claims 1-8.

Images