PATENT DOCUMENT

Publication Number: US-11791031-B2
Application Number: US-202217852020-A
Country: US
Kind Code: B2

Title: Activity trends and workouts

Abstract:
The present disclosure generally relates to computer user interfaces, and more specifically to techniques for presenting activity trends and managing workouts.

Claims:
What is claimed is: 
     
       1. An electronic device, comprising:
 a touch-sensitive display; 
 one or more processors; 
 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:
 receiving:
 activity data corresponding to a first activity metric for a first time period; and 
 activity data corresponding to the first activity metric for a second time period, different than the first time period; 
 
 receiving a request to display a first user interface; and 
 in response to receiving the request, displaying, via the touch-sensitive display, the first user interface, the first user interface including a representation of the first activity metric, wherein the representation of the first activity metric includes:
 in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type, a first coaching indication including a prediction corresponding to when the relationship will transition from being of the first type to being of a second type, different from the first type, while maintaining a future level of activity for the first activity metric; and 
 in accordance with a determination that the relationship is a third type different from the first type, a second coaching indication that does not include a prediction corresponding to when the relationship will transition from being of the third type to being of the second type. 
 
 
 
     
     
       2. The electronic device of  claim 1 , wherein the first type requires that the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is negative. 
     
     
       3. The electronic device of  claim 1 , wherein the representation of the first activity metric includes:
 while the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is the first type:
 in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the second time period and the activity data corresponding to the first activity metric for a subset of the first time period is a fourth type, displaying a third coaching indication; and 
 in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the second time period and the activity data corresponding to the first activity metric for the subset of the first time period is a fifth type, displaying, a fourth coaching indication that is different from the third coaching indication. 
 
 
     
     
       4. The electronic device of  claim 1 , wherein the representation of the first activity metric includes:
 while the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is the first type:
 in accordance with a determination that the prediction exceeds a first time threshold and is less than a second time threshold, displaying a fifth coaching indication; and 
 in accordance with a determination that the prediction exceeds the second time threshold, displaying a sixth coaching indication that is different from the fifth coaching indication. 
 
 
     
     
       5. The electronic device of  claim 1 , wherein the one or more programs further include instructions for:
 while the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is the first type:
 in accordance with a determination that the prediction is a first classification, displaying a fifth coaching indication without a prediction corresponding to when the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period will be of the second type while maintaining the future level of activity for the first activity metric. 
 
 
     
     
       6. The electronic device of  claim 1 , wherein the prediction is determined by:
 removing old data from the activity data corresponding to the first activity metric for the first time period, 
 removing old data from the activity data corresponding to the first activity metric for the second time period, and 
 until the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is the second type,
 adding predicted data to the activity data corresponding to the first activity metric for the first time period, and 
 adding the predicted data the activity data corresponding to the first activity metric for the first time period to the activity data corresponding to the first activity metric for the second time period. 
 
 
     
     
       7. 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 with a touch-sensitive display, the one or more programs including instructions for:
 receiving:
 activity data corresponding to a first activity metric for a first time period; and 
 activity data corresponding to the first activity metric for a second time period, different than the first time period; 
 
 receiving a request to display a first user interface; and 
 in response to receiving the request, displaying, via the touch-sensitive display, the first user interface, the first user interface including a representation of the first activity metric, wherein the representation of the first activity metric includes:
 in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type, a first coaching indication including a prediction corresponding to when the relationship will transition from being of the first type to being of a second type, different from the first type, while maintaining a future level of activity for the first activity metric; and 
 in accordance with a determination that the relationship is a third type different from the first type, a second coaching indication that does not include a prediction corresponding to when the relationship will transition from being of the third type to being of the second type. 
 
 
     
     
       8. A method, comprising:
 at an electronic device including a touch-sensitive display:
 receiving:
 activity data corresponding to a first activity metric for a first time period; and 
 activity data corresponding to the first activity metric for a second time period, different than the first time period; 
 
 receiving a request to display a first user interface; and 
 in response to receiving the request, displaying, via the touch-sensitive display, the first user interface, the first user interface including a representation of the first activity metric, wherein the representation of the first activity metric includes:
 in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type, a first coaching indication including a prediction corresponding to when the relationship will transition from being of the first type to being of a second type, different from the first type, while maintaining a future level of activity for the first activity metric; and 
 in accordance with a determination that the relationship is a third type different from the first type, a second coaching indication that does not include a prediction corresponding to when the relationship will transition from being of the third type to being of the second type.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a Continuation of U.S. non-Provisional application Ser. No. 16/994,352, entitled “ACTIVITY TRENDS AND WORKOUTS,” filed on Aug. 14, 2020, which is a Continuation of U.S. non-Provisional application Ser. No. 16/588,950, entitled “ACTIVITY TRENDS AND WORKOUTS,” filed on Sep. 30, 2019, which claims priority to U.S. Provisional Patent Application Ser. No. 62/844,063, entitled “ACTIVITY TRENDS AND WORKOUTS,” filed on May 6, 2019, the contents of each of which are hereby incorporated by reference in their entirety. 
    
    
     FIELD 
     The present disclosure relates generally to computer user interfaces, and more specifically, to techniques for presenting activity trends and managing workouts. 
     BACKGROUND 
     Users rely on portable multifunction devices for a variety of operations, including tracking activity. Such users may want to easily track the activity and view details related to the activity. 
     BRIEF SUMMARY 
     Some techniques for presenting activity trends and managing workouts using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices. 
     Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for presenting activity trends and managing workouts. Such methods and interfaces optionally complement or replace other methods for presenting activity trends and managing workouts. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges. 
     In some examples, a method is provided for execution at an electronic device including a display device. The method comprises receiving: activity data corresponding to a first activity metric for a first time period, and activity data corresponding to the first activity metric for a second time period different from the first period of time. The method further comprises receiving a request to display a first user interface. The method further comprises, in response to receiving the request, displaying, via the display device, the first user interface including: in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type, displaying a representation of the first activity metric in a first portion of the first user interface; and in accordance with a determination that the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a second type, displaying the representation of the first activity metric in a second portion of the first user interface different from the first portion. 
     In some examples, 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 with a display device is provided. In some examples, the one or more programs include instructions for performing the method discussed above. 
     In some examples, an electronic device comprising: a display device; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors is provided. In some examples, the one or more programs include instructions for performing the method discussed above. 
     In some examples, an electronic device comprising: a display device and means for performing the method discussed above. 
     In some examples, 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 with a display device is provided. In some examples, the one or more programs include instructions for: receiving: activity data corresponding to a first activity metric for a first time period; and activity data corresponding to the first activity metric for a second time period different from the first period of time; receiving a request to display a first user interface; and in response to receiving the request, displaying, via the display device, the first user interface including: in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type, displaying a representation of the first activity metric in a first portion of the first user interface; and in accordance with a determination that the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a second type, displaying the representation of the first activity metric in a second portion of the first user interface different from the first portion. 
     In some examples, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display device is provided. In some examples, the one or more programs include instructions for: receiving: activity data corresponding to a first activity metric for a first time period; and activity data corresponding to the first activity metric for a second time period different from the first period of time; receiving a request to display a first user interface; and in response to receiving the request, displaying, via the display device, the first user interface including: in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type, displaying a representation of the first activity metric in a first portion of the first user interface; and in accordance with a determination that the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a second type, displaying the representation of the first activity metric in a second portion of the first user interface different from the first portion. 
     In some examples, an electronic device, comprising: a display; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors is provided. In some examples, the one or more programs include instructions for: receiving: activity data corresponding to a first activity metric for a first time period; and activity data corresponding to the first activity metric for a second time period different from the first period of time; receiving a request to display a first user interface; and in response to receiving the request, displaying, via the display device, the first user interface including: in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type, displaying a representation of the first activity metric in a first portion of the first user interface; and in accordance with a determination that the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a second type, displaying the representation of the first activity metric in a second portion of the first user interface different from the first portion. 
     In some examples, an electronic device, comprising: a display is provided. In some examples, the electronic device includes: means for receiving: activity data corresponding to a first activity metric for a first time period; and activity data corresponding to the first activity metric for a second time period different from the first period of time; means for receiving a request to display a first user interface; and in response to receiving the request, means for displaying, via the display device, the first user interface including: in accordance with a determination that a relationship between the activity data corresponding to the first activity, metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type, means for displaying a representation of the first activity metric in a first portion of the first user interface; and in accordance with a determination that the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a second type, means for displaying the representation of the first activity metric in a second portion of the first user interface different from the first portion. 
     In some examples, a method performed method at an electronic device including a display device is provided. In some examples, the method comprises: receiving: activity data corresponding to a first activity metric for a first time period; and activity data corresponding to the first activity metric for a second time period, wherein the first time period is a subset of the second time period; receiving a request to display a first user interface; and in response to receiving the request, displaying, via the display device, the first user interface including: representation of the activity data corresponding to the first activity metric for the first time period; a representation of the activity data corresponding to the first activity metric for the second time period; and representation of a comparison of the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period. 
     In some examples, 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 with a display device is provided. In some examples, the one or more programs include instructions for performing the method described above. 
     In some examples, an electronic device comprising: a display device; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors is provided. In some examples, the one or more programs include instructions for performing the method discussed above. 
     In some examples, an electronic device comprising: a display device and means for performing the method discussed above. 
     In some examples, 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 with a display device is provided. In some examples, the one or more programs include instructions for: receiving: activity data corresponding to a first activity metric for a first time period; and activity data corresponding to the first activity metric for a second time period, wherein the first time period is a subset of the second time period; receiving a request to display a first user interface; and in response to receiving the request, displaying, via the display device, the first user interface including: a representation of the activity data corresponding to the first activity metric for the first time period; a representation of the activity data corresponding to the first activity metric for the second time period; and a representation of a comparison of the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period. 
     In some examples, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display device is provided. In some examples, the one or more programs include instructions for: receiving: activity data corresponding to a first activity metric for a first time period; and activity data corresponding to the first activity metric for a second time period, wherein the first time period is a subset of the second time period; receiving a request to display a first user interface; and in response to receiving the request, displaying, via the display device, the first user interface including: a representation of the activity data corresponding to the first activity metric for the first time period; a representation of the activity data corresponding to the first activity metric for the second time period; and a representation of a comparison of the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period. 
     In some examples, an electronic device, comprising: a display device; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors is provided. In some examples, the one or more programs include instructions for: receiving: activity data corresponding to a first activity metric for a first time period; and activity data corresponding to the first activity metric for a second time period, wherein the first time period is a subset of the second time period; receiving a request to display a first user interface; and in response to receiving the request, displaying, via the display device, the first user interface including: a representation of the activity data corresponding to the first activity metric for the first time period; a representation of the activity data corresponding to the first activity metric for the second time period; and a representation of a comparison of the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period. 
     In some examples, an electronic device, comprising: a display device is provided. In some examples, the electronic device includes: means for receiving: activity data corresponding to a first activity metric for a first time period; and activity data corresponding to the first activity metric for a second time period, wherein the first time period is a subset of the second time period; means for receiving a request to display a first user interface; and in response to receiving the request, means for displaying; via the display device, the first user interface including: a representation of the activity data corresponding to the first activity metric for the first time period; a representation of the activity data corresponding to the first activity metric for the second time period; and a representation of a comparison of the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period. 
     In some examples, a method to be performed at an electronic device including a display device is provided. In some examples, the method comprises: receiving: activity data corresponding to a first activity metric for a first time period; and activity data corresponding to the first activity metric for a second time period, different than the first period of time; receiving a request to display a first user interface; and in response to receiving the request, displaying, via the display device, the first user interface; the first user interface including a representation of the first activity metric, wherein the representation of the first activity metric includes: in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type, a first coaching indication including a prediction corresponding to when the relationship will transition from being of the first type to being of a second type, different from the first type, while maintaining a future level of activity for the first activity metric; and in accordance with a determination that the relationship is a third type different from the first type, a second coaching indication that does not include a prediction corresponding to when the relationship will transition from being of the third type to being of the second type. 
     In some examples, 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 with a display device is provided. In some examples, the one or more programs include instructions for performing the method described above. 
     In some examples, an electronic device comprising: a display device; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors is provided. In some examples, the one or more programs include instructions for performing the method discussed above. 
     In some examples, an electronic device comprising: a display device and means for performing the method discussed above. 
     In some examples, 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 with a display device is provided. In some examples, the one or more programs include instructions for: receiving: activity data corresponding to a first activity metric for a first time period; and activity data corresponding to the first activity metric for a second time period, different than the first period of time; receiving a request to display a first user interface; and in response to receiving the request, displaying, via the display device, the first user interface, the first user interface including a representation of the first activity metric, wherein the representation of the first activity metric includes: in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type, a first coaching indication including a prediction corresponding to when the relationship will transition from being of the first type to being of a second type, different from the first type, while maintaining a future level of activity for the first activity metric; and in accordance with a determination that the relationship is a third type different from the first type, a second coaching indication that does not include a prediction corresponding to when the relationship will transition from being of the third type to being of the second type. 
     In some examples, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display device is provided. In some examples, the one or more programs include instructions for: receiving: activity data corresponding to a first activity metric for a first time period; and activity data corresponding to the first activity metric for a second time period, different than the first period of time; receiving a request to display a first user interface; and in response to receiving the request, displaying, via the display device, the first user interface, the first user interface including a representation of the first activity metric, wherein the representation of the first activity metric includes: in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type, a first coaching indication including a prediction corresponding to when the relationship will transition from being of the first type to being of a second type, different from the first type, while maintaining a future level of activity for the first activity metric; and in accordance with a determination that the relationship is a third type different from the first type, a second coaching indication that does not include a prediction corresponding to when the relationship will transition from being of the third type to being of the second type. 
     In some examples, an electronic device, comprising: a display device; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors is provided. In some examples, the one or more programs include instructions for: receiving: activity data corresponding to a first activity metric for a first time period; and activity data corresponding to the first activity metric for a second time period, different than the first period of time; receiving a request to display a first user interface; and in response to receiving the request, displaying, via the display device, the first user interface; the first user interface including a representation of the first activity metric, wherein the representation of the first activity metric includes: in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type, a first coaching indication including a prediction corresponding to when the relationship will transition from being of the first type to being of a second type, different from the first type, while maintaining a future level of activity for the first activity metric; and in accordance with a determination that the relationship is a third type different from the first type, a second coaching indication that does not include a prediction corresponding to when the relationship will transition from being of the third type to being of the second type. 
     In some examples, an electronic device, comprising a display device is provided. In some examples, the electronic device includes: means for receiving: activity data corresponding to a first activity metric for a first time period; and activity data corresponding to the first activity metric for a second time period, different than the first period of time; means for receiving a request to display a first user interface; and in response to receiving the request, means for displaying, via the display device, the first user interface, the first user interface including a representation of the first activity metric, wherein the representation of the first activity metric includes: in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type, a first coaching indication including a prediction corresponding to when the relationship will transition from being of the first type to being of a second type, different from the first type, while maintaining a future level of activity for the first activity metric; and in accordance with a determination that the relationship is a third type different from the first type, a second coaching indication that does not include a prediction corresponding to when the relationship will transition from being of the third type to being of the second type. 
     In some examples, a method performed at an electronic device including a display device is provided. The method comprises: displaying, via the display device, a first instance of a first user interface including a first set of affordances associated with physical activity tracking functions, wherein the first set of affordances includes a first affordance associated with a first physical activity tracking function; while displaying the first instance of the first user interface, receiving a user input; and in response to receiving the user input: in accordance with a determination that the user input is detected at the first affordance in the first set of affordances, launching the first physical activity tracking function; and in accordance with a determination that the user input is detected at a second affordance in the first set of affordances, displaying a second user interface that includes a third affordance associated with a second physical activity tracking function; receiving a set of one or more inputs, the set of one or more inputs including an input corresponding to selection of the third accordance; and in response to receiving the set of one or more inputs, displaying a second instance of first user interface, wherein: the second instance of the first user interface includes the first affordance and a fourth affordance associated with the second physical activity tracking function, and the first instance of the first user interface does not include an affordance associated with the second physical activity tracking function. 
     In some examples, 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 with a display device is provided. In some examples, the one or more programs include instructions for performing the method described above. 
     In some examples, an electronic device comprising: a display device; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors is provided. In some examples, the one or more programs include instructions for performing the method discussed above. 
     In some examples, an electronic device comprising: a display device and means for performing the method discussed above. 
     In some examples, 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 with a display device is provided. The one or more programs include instructions for: displaying, via the display device, a first instance of a first user interface including a first set of affordances associated with physical activity tracking functions, wherein the first set of affordances includes a first affordance associated with a first physical activity tracking function; while displaying the first instance of the first user interface, receiving a user input; and in response to receiving the user input: in accordance with a determination that the user input is detected at the first affordance in the first set of affordances, launching the first physical activity tracking function; and in accordance with a determination that the user input is detected at a second affordance in the first set of affordances, displaying a second user interface that includes a third affordance associated with a second physical activity tracking function; receiving a set of one or more inputs, the set of one or more inputs including an input corresponding to selection of the third affordance; and in response to receiving the set of one or more inputs, displaying a second instance of first user interface, wherein: the second instance of the first user interface includes the first affordance and a fourth affordance associated with the second physical activity tracking function, and the first instance of the first user interface does not include an affordance associated with the second physical activity tracking function. 
     In some examples, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display device is provided. The one or more programs include instructions for: displaying, via the display device, a first instance of a first user interface including a first set of affordances associated with physical activity tracking functions, wherein the first set of affordances includes a first affordance associated with a first physical activity tracking function; while displaying the first instance of the first user interface, receiving a user input; and in response to receiving the user input: in accordance with a determination that the user input is detected at the first affordance in the first set of affordances, launching the first physical activity tracking function; and in accordance with a determination that the user input is detected at a second affordance in the first set of affordances, displaying a second user interface that includes a third affordance associated with a second physical activity tracking function; receiving a set of one or more inputs, the set of one or more inputs including an input corresponding to selection of the third affordance; and in response to receiving the set of one or more inputs, displaying a second instance of first user interface, wherein: the second instance of the first user interface includes the first affordance and a fourth affordance associated with the second physical activity tracking function, and the first instance of the first user interface does not include an affordance associated with the second physical activity tracking function. 
     In some examples, an electronic device, comprising: a display device; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors is provided. The one or more programs include instructions for: displaying, via the display device, a first instance of a first user interface including a first set of affordances associated with physical activity tracking functions, wherein the first set of affordances includes a first affordance associated with a first physical activity tracking function; while displaying the first instance of the first user interface, receiving a user input; and in response to receiving the user input: in accordance with a determination that the user input is detected at the first affordance in the first set of affordances, launching the first physical activity tracking function; and in accordance with a determination that the user input is detected at a second affordance in the first set of affordances, displaying a second user interface that includes a third affordance associated with a second physical activity tracking function; receiving a set of one or more inputs, the set of one or more inputs including an input corresponding to selection of the third affordance; and in response to receiving the set of one or more inputs, displaying a second instance of first user interface, wherein: the second instance of the first user interface includes the first affordance and a fourth affordance associated with the second physical activity tracking function, and the first instance of the first user interface does not include an affordance associated with the second physical activity tracking function. 
     In some examples, an electronic device, comprising a display device is provided. The electronic device further comprises: means displaying, via the display device, a first instance of a first user interface including a first set of affordances associated with physical activity tracking functions, wherein the first set of affordances includes a first affordance associated with a first physical activity tracking function; while displaying the first instance of the first user interface, means for receiving a user input; and in response to receiving the user input: in accordance with a determination that the user input is detected at the first affordance in the first set of affordances, means for launching the first physical activity tracking function; and in accordance with a determination that the user input is detected at a second affordance in the first set of affordances, means for displaying a second user interface that includes a third affordance associated with a second physical activity tracking function; means for receiving a set of one or more inputs, the set of one or more inputs including an input corresponding to selection of the third affordance; and in response to receiving the set of one or more inputs, means for displaying a second instance of first user interface, wherein: the second instance of the first user interface includes the first affordance and a fourth affordance associated with the second physical activity tracking function, and the first instance of the first user interface does not include an of associated with the second physical activity tracking function. 
     Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally; included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. 
     Thus, devices are provided with faster, more efficient methods and interfaces for presenting activity trends and managing workouts, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces can complement or replace other methods for presenting activity trends and managing workouts. 
    
    
     
       DESCRIPTION OF THE FIGURES 
       For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures. 
         FIG.  1 A  is a block diagram illustrating a portable multifunction device with ouch-sensitive display in accordance with some embodiments. 
         FIG.  1 B  is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. 
         FIG.  2    illustrates a portable multifunction device having a touch screen in accordance with some embodiments. 
         FIG.  3    is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. 
         FIG.  4 A  illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments. 
         FIG.  4 B  illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments. 
         FIG.  5 A  illustrates a personal electronic device in accordance with some embodiments. 
         FIG.  5 B  is a block diagram illustrating a personal electronic device in accordance with some embodiments. 
         FIG.  6 A  depicts an electronic device displaying a home user interface via a display device. 
         FIG.  6 B  depicts an electronic device displaying an information user interface for an activity application. 
         FIG.  6 C  depicts an electronic device displaying an instance of a 90-day trends user interface via a display device when an insufficient amount of data to identify a trend has been received for multiple activity metrics. 
         FIG.  6 D  depicts an electronic device displaying an instance of a 90-day trends user interface via a display device when all activity metrics have a negative trend within the last 90 days as compared to the last 365 days. 
         FIG.  6 E  depicts an electronic device displaying an instance of a 90-day trends user interface via a display device when some activity metrics have a positive trend and other activity metrics have a negative trend within the last 90 days as compared to the last 365 days. 
         FIG.  6 F  depicts an electronic device displaying an instance of a 90-day trends user interface via a display device when all activity metrics have a positive trend within the last 90 days as compared to the last 365 days. 
         FIG.  6 G  depicts an electronic device displaying a detailed exercise user interface. 
         FIG.  6 H  depicts an electronic device displaying a ready-to-user user interface via a display device when activity trends are ready to be viewed on a second device. 
         FIG.  6 I  depicts an electronic device displaying a mid-month-update user interface via a display device when activity trends are available to be viewed on a second device. 
         FIGS.  7 A- 7 B  are a flow diagram illustrating a method for presenting activity trends using an electronic device in accordance with some embodiments. 
         FIGS.  8 A- 8 B  are a flow diagram illustrating a method for presenting activity trends using an electronic device in accordance with some embodiments. 
         FIG.  9    is a flow diagram illustrating a method for presenting activity trends using an electronic device in accordance with some embodiments. 
         FIG.  10 A  depicts an electronic device displaying a watch face user interface via a display device. 
         FIG.  10 B  depicts an electronic device displaying a workout platter user interface via a display device. 
         FIG.  10 C  depicts an electronic device displaying a walk user interface via a display device. 
         FIG.  10 D  depicts an electronic device displaying a control user interface via a display device. 
         FIG.  10 E  depicts an electronic device displaying a workout platter user interface via a display device  1002  and performing a scrolling operation. 
         FIG.  10 F  depicts an electronic device receiving user input corresponding to selection of a more workouts affordance. 
         FIG.  10 G  depicts an electronic device displaying a workout list user interface via a display device. 
         FIG.  10 H  depicts an electronic device receiving user input corresponding to selection of an AUS football affordance. 
         FIG.  10 I  depicts an electronic device displaying a workout platter user interface via a display device. 
         FIG.  10 J  depicts an electronic device displaying an AUS football interface via a display device  1007 . 
         FIG.  10 K  depicts an electronic device displaying a control user interface via a display device. 
         FIG.  10 L  depicts an electronic device displaying a workout platter user interface via a display device. 
         FIG.  10 M  depicts an electronic device displaying a workout platter user interface via a display device with an AUS football affordance moved to the left and a delete affordance displayed in a location that was at least partially covered up by the AUS football affordance prior to being moved to the left. 
         FIG.  10 N  depicts an electronic device displaying a workout platter user interface via a display device without an AUS football affordance. 
         FIGS.  11 A- 11 B  are a flow diagram illustrating methods of organizing workouts in accordance with some embodiments. 
         FIG.  12 A  depicts an electronic device displaying an activity application user interface via a display device  1002 , 
         FIG.  12 B  depicts an electronic device displaying an activity user interface via a display device. 
         FIG.  12 C  depicts an electronic device displaying a friends user interface via a display device. 
         FIG.  12 D  depicts an electronic device displaying an awards user interface via a display device. 
         FIG.  12 E  depicts an electronic device displaying a non-awarded detailed user interface via a display device. 
         FIG.  12 F  depicts an electronic device displaying an awarded detailed user interface via a display device. 
     
    
    
     DESCRIPTION OF EMBODIMENTS 
     The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments. 
     There is a need for electronic devices that provide efficient methods and interfaces for presenting activity trends and managing workouts. Below,  FIGS.  1 A- 1 B,  2 ,  3 ,  4 A- 4 B, and  5 A- 5 B  provide a description of exemplary devices for performing the techniques for managing event notifications.  FIGS.  6 A- 6 I  illustrate exemplary user interfaces for presenting activity trends. The user interfaces in  FIGS.  6 A- 6 I  are used to illustrate the processes described below, including the processes in  FIGS.  7 A- 7 B,  8 A- 8 B, and  9   .  FIGS.  7 A- 7 B  are a flow diagram illustrating methods of presenting activity trends in accordance with some embodiments.  FIGS.  8 A- 8 B  are a flow diagram illustrating methods of presenting activity trends in accordance with some embodiments.  FIG.  9    is a flow diagram illustrating methods of presenting activity trends in accordance with some embodiments.  FIGS.  10 A- 10 N  illustrate exemplary user interfaces for managing workouts. The user interfaces in  FIGS.  10 A- 1    ON are used to illustrate the processes described below, including the processes in  FIGS.  11 A- 11 B ,  FIGS.  11 A- 11 B  are a flow diagram illustrating methods of organizing workouts in accordance with some embodiments.  FIGS.  12 A- 12 F  illustrate exemplary user interfaces for displaying awards. 
     Although the following description uses terms “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 described embodiments. The first touch and the second touch are both touches, but they are not the same touch. 
     The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. 
     The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context. 
     Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad). 
     In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick. 
     The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application. 
     The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user. 
     Attention is now directed toward embodiments of portable devices with touch-sensitive displays.  FIG.  1 A  is a block diagram illustrating portable multifunction device  100  with touch-sensitive display system  112  in accordance with some embodiments. Touch-sensitive display  112  is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.” Device  100  includes memory  102  (which optionally includes one or more computer-readable storage mediums), memory controller  122 , one or more processing units (CPUs)  120 , peripherals interface  118 , RF circuitry  108 , audio circuitry  110 , speaker  111 , microphone  113 , input/output ( 110 ) subsystem  106 , other input control devices  116 , and external port  124 . Device  100  optionally includes one or more optical sensors  164 . Device  100  optionally includes one or more contact intensity sensors  165  for detecting intensity of contacts on device  100  (e.g., a touch-sensitive surface such as touch-sensitive display system  112  of device  100 ). Device  100  optionally includes one or more tactile output generators  167  for generating tactile outputs on device  100  (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system  112  of device  100  or touchpad  355  of device  300 ). These components optionally communicate over one or more communication buses or signal lines  103 . 
     As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button). 
     As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user&#39;s sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user&#39;s hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user&#39;s movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user. 
     It should be appreciated that device  100  is only one example of a portable multifunction device, and that device  100  optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in  FIG.  1 A  are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application-specific integrated circuits. 
     Memory  102  optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller  122  optionally controls access to memory  102  by other components of device  100 . 
     Peripherals interface  118  can be used to couple input and output peripherals of the device to CPU  120  and memory  102 . The one or more processors  120  run or execute various software programs and/or sets of instructions stored in memory  102  to perform various functions for device  100  and to process data. In some embodiments, peripherals interface  118 , CPU  120 , and memory controller  122  are, optionally, implemented on a single chip, such as chip  104 . In some other embodiments, they are, optionally, implemented on separate chips. 
     RF (radio frequency) circuitry  108  receives and sends RE signals, also called electromagnetic signals. RE circuitry  108  converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RE circuitry  108  optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry  108  optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry  108  optionally includes well-known circuitry for detecting near field communication (NEC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA, Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document. 
     Audio circuitry  110 , speaker  111 , and microphone  113  provide an audio interface between a user and device  100 . Audio circuitry  110  receives audio data from peripherals interface  118 , converts the audio data to an electrical signal, and transmits the electrical signal to speaker  111 . Speaker  111  converts the electrical signal to human-audible sound waves. Audio circuitry  110  also receives electrical signals converted by microphone  113  from sound waves. Audio circuitry  110  converts the electrical signal to audio data and transmits the audio data to peripherals interface  118  for processing. Audio data is, optionally, retrieved from and/or transmitted to memory  102  and/or RF circuitry  108  by peripherals interface  118 . In some embodiments, audio circuitry  110  also includes a headset jack (e.g.,  212 ,  FIG.  2   ). The headset jack provides an interface between audio circuitry  110  and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone). 
     I/O subsystem  106  couples input/output peripherals on device  100 , such as touch screen  112  and other input control devices  116 , to peripherals interface  118 . I/O subsystem  106  optionally includes display controller  156 , optical sensor controller  158 , depth camera controller  169 , intensity sensor controller  159 , haptic feedback controller  161 , and one or more input controllers  160  for other input or control devices. The one or more input controllers  160  receive/send electrical signals from/to other input control devices  116 . The other input control devices  116  optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s)  160  are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g.,  208 ,  FIG.  2   ) optionally include an up/down button for volume control of speaker  111  and/or microphone  113 . The one or more buttons optionally include a push button (e.g.,  206 ,  FIG.  2   ). 
     A quick press of the push button optionally disengages a lock of touch screen  112  or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g.,  206 ) optionally turns power to device  100  on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen  112  is used to implement virtual or soft buttons and one or more soft keyboards. 
     Touch-sensitive display  112  provides an input interface and an output interface between the device and a user. Display controller  156  receives and/or sends electrical signals from/to touch screen  112 . Touch screen  112  displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects. 
     Touch screen  112  has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen  112  and display controller  156  (along with any associated modules and/or sets of instructions in memory  102 ) detect contact (and any movement or breaking of the contact) on touch screen  112  and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen  112 , In an exemplary embodiment, a point of contact between touch screen  112  and the user corresponds to a finger of the user. 
     Touch screen  112  optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen  112  and display controller  156  optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen  112 . In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California. 
     A touch-sensitive display in some embodiments of touch screen  112  is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen  112  displays visual output from device  100 , whereas touch-sensitive touchpads do not provide visual output. 
     A touch-sensitive display in some embodiments of touch screen  112  is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety. 
     Touch screen  112  optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen  112  using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user. 
     In some embodiments, in addition to the touch screen, device  100  optionally includes a touchpad for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display, visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen  112  or an extension of the touch-sensitive surface formed by the touch screen. 
     Device  100  also includes power system  162  for powering the various components. Power system  162  optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices. 
     Device  100  optionally also includes one or more optical sensors  164 .  FIG.  1 A  shows an optical sensor coupled to optical sensor controller  158  in I/O subsystem  106 , Optical sensor  164  optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor  164  receives light from the environment, projected through one or more lenses, and converts the light to data representing an image. In conjunction with imaging module  143  (also called a camera module), optical 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 is enabled for use as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user&#39;s image is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of optical sensor  164  can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor  164  is used along with the touch screen display for both video conferencing and still and/or video image acquisition. 
     Device  100  optionally also includes one or more depth camera sensors  175 .  FIG.  1 A  shows a depth camera sensor coupled to depth camera controller  169  in I/O subsystem  106 . Depth camera sensor  175  receives data from the environment to create a three dimensional model of an object (e.g., a face) within a scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with imaging module  143  (also called a camera module), depth camera sensor  175  is optionally used to determine a depth map of different portions of an image captured by the imaging module  143 . In some embodiments, a depth camera sensor is located on the front of device  100  so that the user&#39;s image with depth information is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display and to capture selfies with depth map data. In some embodiments, the depth camera sensor  175  is located on the back of device, or on the back and the front of the device  100 . In some embodiments, the position of depth camera sensor  175  can be changed by the user e.g., by rotating the lens and the sensor in the device housing) so that a depth camera sensor  175  is used along with the touch screen display for both video conferencing and still and/or video image acquisition. 
     Device  100  optionally also includes one or more contact intensity sensors  165 .  FIG.  1 A  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, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor  165  receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system  112 ). In some embodiments, at least one contact intensity sensor is located on the back of device  100 , opposite touch screen display  112 , which is located on the front of device  100 . 
     Device  100  optionally also includes one or more proximity sensors  166 , IA shows proximity sensor  166  coupled to peripherals interface  118 . Alternately, proximity sensor  166  is, optionally, coupled to input controller  160  in I/O subsystem  106 . Proximity sensor  166  optionally performs as described in U.S. patent application Ser. No. 11/241,839, “Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “Proximity Detector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and Ser. No. 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” 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 placed near the user&#39;s ear (e.g., when the user is making a phone call). 
     Device  100  optionally also includes one or more tactile output generators  167 .  FIG.  1 A  shows a tactile output generator coupled to haptic feedback controller  161  in I/O subsystem  106 . Tactile output generator  167  optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device). Contact intensity sensor  165  receives tactile feedback generation instructions from haptic feedback module  133  and generates tactile outputs on device  100  that are capable of being sensed by a user of device  100 . In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system  112 ) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device  100 ) or laterally (e.g., back and forth in the same plane as a surface of device  100 ). In some embodiments, at least one tactile output generator sensor is located on the back of device  100 , opposite touch screen display  112 , which is located on the front of device  100 . 
     Device  100  optionally also includes one or more accelerometers  168 .  FIG.  1 A  shows accelerometer  168  coupled to peripherals interface  118 . Alternately, accelerometer  168  is, optionally, coupled to an input controller  160  in I/O subsystem  106 . Accelerometer  168  optionally performs as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device  100  optionally includes, in addition to accelerometer(s)  168 , a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device  100 . 
     In some embodiments, the software components stored in memory  102  include operating system  126 , communication module (or set of instructions)  128 , contact/motion module (or set of instructions)  130 , graphics module (or set of instructions)  132 , text input module (or set of instructions)  134 , Global Positioning System (GPS) module (or set of instructions)  135 , and applications (or sets of instructions)  136 . Furthermore, in some embodiments, memory  102  ( FIG.  1 A ) or  370  ( FIG.  3   ) stores device/global internal state  157 , as shown in  FIGS.  1 A and  3   . Device/global internal state  157  includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display  112 ; sensor state, including information obtained from the device&#39;s various sensors and input control devices  116 ; and location information concerning the device&#39;s location and/or attitude. 
     Operating system  126  (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory, management, storage device control, power management, etc.) and facilitates communication between various hardware and software components. 
     Communication module  128  facilitates communication with other devices over one or more external ports  124  and also includes various software components for handling data received by RF circuitry  108  and/or external port  124 . External port  124  (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices. 
     Contact/notion module  130  optionally detects contact with touch screen  112  (in conjunction with display controller  156 ) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module  130  includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module  130  receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module  130  and display controller  156  detect contact on a touchpad. 
     In some embodiments, contact/motion module  130  uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device  100 ). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter). 
     Contact/motion module  130  optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event. 
     Graphics module  132  includes various known software components for rendering and displaying graphics on touch screen  112  or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like. 
     In some embodiments, graphics module  132  stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module  132  receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller  156 . 
     Haptic feedback module  133  includes various software components for generating instructions used by tactile output generator(s)  167  to produce tactile outputs at one or more locations on device  100  in response to user interactions with device  100 . 
     Text input module  134 , which is, optionally, a component of graphics module  132 , provides soft keyboards for entering text in various applications (e.g., contacts  137 , e-mail  140 , LM  141 , browser  147 , and any other application that needs text input). 
     GPS module  135  determines the location of the device and provides this information for use in various applications (e.g., to telephone  138  for use in location-based dialing; to camera  143  as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets). 
     Applications  136  optionally include the following modules (or sets of instructions), or a subset or superset thereof:
         Contacts module  137  (sometimes called an address book or contact list);   Telephone module  138 ;   Video conference module  139 ;   E-mail client module  140 ;   Instant messaging (IM) module  141 ;   Workout 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 ;   Widget modules  149 , which optionally include one or more of: weather widget  149 - 1 , stocks widget  149 - 2 , calculator widget  149 - 3 , alarm clock widget  149 - 4 , dictionary widget  149 - 5 , and other widgets obtained by the user, as well as user-created widgets  149 - 6 ;   Widget creator module  150  for making user-created widgets  149 - 6 ;   Search module  151 ;   Video and music player module  152 , which merges video player module and music player module;   Notes module  153 ;   Map module  154 ; and/or   Online video module  155 .       

     Examples of other applications  136  that are, optionally, stored in memory  102  include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication. 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , contacts module  137  are, optionally, used to manage an address book or contact list (e.g., stored in application internal state  192  of contacts module  137  in memory  102  or memory  370 ), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone  138 , video conference module  139 , e-mail  140 , or IM  141 ; and so forth. 
     In conjunction with RF circuitry  108 , audio circuitry  110 , speaker  111 , microphone  113 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , telephone module  138  are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module  137 , modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies. 
     In conjunction with RF circuitry  108 , audio circuitry  110 , speaker  111 , microphone  113 , touch screen  112 , display controller  156 , optical sensor  164 , optical sensor controller  158 , contact/motion module  130 , graphics module  132 , text input module  134 , contacts module  137 , and telephone module  138 , video conference module  139  includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , e-mail client module  140  includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module  144 , e-mail client module  140  makes it very easy to create and send e-mails with still or video images taken with camera module  143 . 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , the instant messaging module  141  includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS). 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , GPS module  135 , map module  154 , and music player module, workout support module  142  includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data. 
     In conjunction with touch screen  112  display controller  156 , optical sensor&#39;s)  164 , optical sensor controller  158 , contact/motion module  130 , graphics module  132 , and image management module  144 , camera module  143  includes executable instructions to capture still images or video (including a video stream) and store them into memory  102 , modify characteristics of a still image or video, or delete a still image or video from memory  102 . 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , and camera module  143 , image management module  144  includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , browser module  147  includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , e-mail client module  140 , and browser module  147 , calendar module  148  includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , and browser module  147 , widget modules  149  are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget  149 - 1 , stocks widget  149 - 2 , calculator widget  149 - 3 , alarm clock widget  149 - 4 , and dictionary widget  149 - 5 ) or created by the user (e.g., user-created widget  149 - 6 ). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets). 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , and browser module  147 , the widget creator module  150  are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget). 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , search module  151  includes executable instructions to search for text, music, sound, image, video, and/or other files in memory  102  that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions. 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , audio circuitry  110 , speaker  111 , RF circuitry  108 , and browser module  147 , video and music player module  152  includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen  112  or on an external, connected display via external port  124 ). In some embodiments, device  100  optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.). 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , and text input module  134 , notes module  153  includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions. 
     In conjunction with RF circuitry  108 , touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , text input module  134 , GPS module  135 , and browser module  147 , map module  154  are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions. 
     In conjunction with touch screen  112 , display controller  156 , contact/motion module  130 , graphics module  132 , audio circuitry  110 , speaker  111 , RF circuitry  108 , text input module  134 , e-mail client module  140 , and browser module  147 , online video module  155  includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port  124 ), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module  141 , rather than e-mail client module  140 , is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety. 
     Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module  152 ,  FIG.  1 A ). In some embodiments, memory  102  optionally stores a subset of the modules and data structures identified above. Furthermore, memory  102  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 through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device  100 , the number of physical input control devices (such as push buttons, dials, and the like) on device  100  is, optionally, reduced. 
     The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device  100  to a main, home, or root menu from any user interface that is displayed on device  100 . In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad. 
       FIG.  1 B  is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory  102  ( FIG.  1 A ) or  370  ( FIG.  3   ) includes event sorter  170  (e.g., in operating system  126 ) and a respective application  136 - 1  (e.g., any of the aforementioned applications  137 - 151 ,  155 ,  380 - 390 ). 
     Event sorter  170  receives event information and determines the application  136 - 1  and application view  191  of application  136 - 1  to which to deliver the event information. Event sorter  170  includes event monitor  171  and event dispatcher module  174 . In some embodiments, application  136 - 1  includes application internal state  192 , which indicates the current application views) displayed on touch-sensitive display  112  when the application is active or executing. In some embodiments, device/global internal state  157  is used by event sorter  170  to determine which application(s) is (are) currently active, and application internal state  192  is used by event sorter  170  to determine application views  191  to which to deliver event information. 
     In some embodiments, application internal state  192  includes additional information, such as one or more of: resume information to be used when application  136 - 1  resumes execution, user interface state information that indicates information being displayed or that is ready for display by application  136 - 1 , a state queue for enabling the user to go back to a prior state or view of application  136 - 1 , and a redo/undo queue of previous actions taken by the user. 
     Event monitor  171  receives event information from peripherals interface  118 . Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display  112 , as part of a multi-touch gesture). Peripherals interface  118  transmits information it receives from I/O subsystem  106  or a sensor, such as proximity sensor  166 , accelerometer(s)  168 , and/or microphone  113  (through audio circuitry  110 ). Information that peripherals interface  118  receives from I/O subsystem  106  includes information from touch-sensitive display  112  or a touch-sensitive surface. 
     In some embodiments, event monitor  171  sends requests to the peripherals interface  118  at predetermined intervals. In response, peripherals interface  118  transmits event information. In other embodiments, peripherals interface  118  transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration). 
     In some embodiments, event sorter  170  also includes a hit view determination module  172  and/or an active event recognizer determination module  173 . 
     Hit view determination module  172  provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display  112  displays more than one view. Views are made up of controls and other elements that a user can see on the display. 
     Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture. 
     Hit view determination module  172  receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module  172  identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module  172 , the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view. 
     Active event recognizer determination module  173  determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module  173  determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module  173  determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views. 
     Event dispatcher module  174  dispatches the event information to an event recognizer (e.g., event recognizer  180 ). In embodiments including active event recognizer determination module  173 , event dispatcher module  174  delivers the event information to an event recognizer determined by active event recognizer determination module  173 . In some embodiments, event dispatcher module  174  stores in an event queue the event information, which is retrieved by a respective event receiver  182 . 
     In some embodiments, operating system  126  includes event sorter  170 . Alternatively, application  136 - 1  includes event sorter  170 . In yet other embodiments, event sorter  170  is a stand-alone module, or a part of another module stored in memory  102 , such as contact/motion module  130 . 
     In some embodiments, application  136 - 1  includes a plurality of event handlers  190  and one or more application views  191 , each of which includes instructions for handling touch events that occur within a respective view of the application&#39;s user interface. Each application view  191  of the application  136 - 1  includes one or more event recognizers  180 . Typically, a respective application view  191  includes a plurality of event recognizers  180 . In other embodiments, one or more of event recognizers  180  are part of a separate module, such as a user interface kit or a higher level object from which application  136 - 1  inherits methods and other properties. In some embodiments, a respective event handler  190  includes one or more of: data updater  176 , object updater  177 , GUI updater  178 , and/or event data  179  received from event sorter  170 , Event handler  190  optionally utilizes or calls data updater  176 , object updater  177 , or GUI updater  178  to update the application internal state  192 . Alternatively, one or more of the application views  191  include one or more respective event handlers  190 . Also, in some embodiments, one or more of data updater  176 , object updater  177 , and GUI updater  178  are included in a respective application view  191 . 
     A respective event recognizer  180  receives event information (e.g., event data  179 ) from event sorter  170  and identifies an event from the event information. Event recognizer  180  includes event receiver  182  and event comparator  184 . In some embodiments, event recognizer  180  also includes at least a subset of: metadata  183 , and event delivery instructions  188  (which optionally include sub-event delivery instructions). 
     Event receiver  182  receives event information from event sorter  170 . The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device. 
     Event comparator  184  compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator  184  includes event definitions  186 . Event definitions  186  contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 ( 187 - 1 ), event 2 ( 187 - 2 ), and others. In some embodiments, sub-events in an event ( 187 ) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 ( 187 - 1 ) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 ( 187 - 2 ) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display  112 , and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers  190 . 
     In some embodiments, event 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 sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display  112 , when a touch is detected on touch-sensitive display  112 , event comparator  184  performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler  190 , the event comparator uses the result of the hit test to determine which event handler  190  should be activated. For example, event comparator  184  selects an event handler associated with the sub-event and the object triggering the hit test. 
     In some embodiments, the definition for a respective event ( 187 ) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer&#39;s event type. 
     When a respective event recognizer  180  determines that the series of sub-events do not match any of the events in event definitions  186 , the respective event recognizer  180  enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture. 
     In some embodiments, a respective event recognizer  180  includes metadata  183  with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata  183  includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata  183  includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy. 
     In some embodiments, a respective event recognizer  180  activates event handler  190  associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer  180  delivers event information associated with the event to event handler  190 . Activating an event handler  190  is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer  180  throws a flag associated with the recognized event, and event handler  190  associated with the flag catches the flag and performs a predefined process. 
     In some embodiments, event delivery instructions  188  include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process. 
     In some embodiments, data updater  176  creates and updates data used in application  136 - 1 . For example, data updater  176  updates the telephone number used in contacts module  137 , or stores a video file used in video player module. In some embodiments, object updater  177  creates and updates objects used in application  136 - 1 . For example, object updater  177  creates a new user-interface object or updates the position of a user-interface object. GUI updater  178  updates the GUI. For example, GUI updater  178  prepares display information and sends it to graphics module  132  for display on a touch-sensitive display. 
     In some embodiments, event handler(s)  190  includes or has access to data updater  176 , object updater  177 , and GUI updater  178 . In some embodiments, data updater  176 , object updater  177 , and GUI updater  178  are included in a single module of a respective application  136 - 1  or application view  191 . In other embodiments, they are included in two or more software modules. 
     It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices  100  with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized. 
       FIG.  2    illustrates a portable multifunction device  100  having a touch screen  112  in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI)  200 , In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers  202  (not drawn to scale in the figure) or one or more styluses  203  (not drawn to scale in the figure). 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 optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device  100 . In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap. 
     Device  100  optionally also include one or more physical buttons, such as “home” or menu button  204 . As described previously, menu button  204  is, optionally, used to navigate to any application  136  in a set of applications that are, optionally, executed on device  100 . Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen  112 . 
     In some embodiments, device  100  includes touch screen  112 , menu button  204 , push button  206  for powering the device on/off and locking the device, volume adjustment button(s)  20 S, subscriber identity module (SIM) card slot  210 , headset jack  212 , and docking/charging external port  124 . Push button  206  is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device  100  also accepts verbal input for activation or deactivation of some functions through microphone  113 . Device  100  also, optionally, includes one or more contact intensity sensors  165  for detecting intensity of contacts on touch screen  112  and/or one or more tactile output generators  167  for generating tactile outputs for a user of device  100 . 
       FIG.  3    is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device  300  need not be portable. In some embodiments, device  300  is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child&#39;s learning toy), a gaming system, or a control device (e.g., a home or industrial controller), Device  300  typically includes one or more processing units (CPUs)  310 , one or more network or other communications interfaces  360 , memory  370 , and one or more communication buses  320  for interconnecting these components. Communication buses  320  optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device  300  includes input/output (I/O) interface  330  comprising display  340 , which is typically a touch screen display. I/O interface  330  also optionally includes a keyboard, and/or mouse (or other pointing device)  350  and touchpad  355 , tactile output generator  357  for generating tactile outputs on device  300  (e.g., similar to tactile output generator(s)  167  described above with reference to  FIG.  1 A ), sensors  359  (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s)  165  described above with reference to  FIG.  1 A ). Memory  370  includes high-speed random access memory, such as DRAM, SRAM, DDR. RAM, or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory  370  optionally includes one or more storage devices remotely located from CPU(s)  310 , In some embodiments, memory  370  stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory  102  of portable multifunction device  100  ( FIG.  1 A ), or a subset thereof. Furthermore, memory  370  optionally, stores additional programs, modules, and data structures not present in memory  102  of portable multifunction device  100 . For example, memory  370  of device  300  optionally stores drawing module  380 , presentation module  382 , word processing module  384 , website creation module  386 , disk authoring module  388 , and/or spreadsheet module  390 , while memory  102  of portable multifunction device  100  ( FIG.  1 A ) optionally does not store these modules. 
     Each of the above-identified elements in  FIG.  3    is, optionally, stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The above-identified modules or programs (e.g., 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 rearranged in various embodiments. In some embodiments, memory  370  optionally stores a subset of the modules and data structures identified above. Furthermore, memory  370  optionally stores additional modules and data structures not described above. 
     Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device  100 . 
       FIG.  4 A  illustrates an exemplary user interface for a menu of applications on portable multifunction device  100  in accordance with some embodiments. Similar user interfaces are, optionally, implemented on device  300 . 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 ;   Tray  408  with icons for frequently used applications, such as:
           Icon  416  for telephone module  138 , labeled “Phone,” which optionally includes an indicator  414  of the number of missed calls or voicemail messages;   Icon  418  for e-mail client module  140 , labeled “Mail,” which optionally includes an indicator  410  of the number of unread e-mails;   Icon  420  for browser module  147 , labeled “Browser;” and   Icon  422  for video and music player module  152 , also referred to as iPod (trademark of Apple Inc.) module  152 , labeled “iPod;” and   
           Icons for other applications, such as:
           Icon  424  for IM module  141 , labeled “Messages;”   Icon  426  for calendar module  148 , labeled “Calendar;”   Icon  428  for image management module  144 , labeled “Photos;”   Icon  430  for camera module  143 , labeled “Camera;”   Icon  432  for online video module  155 , labeled “Online Video,”   Icon  434  for stocks widget  149 - 2 , labeled “Stocks;”   Icon  436  for map module  154 , labeled “Maps,”   Icon  438  for weather widget  149 - 1 , labeled “Weather;”   Icon  440  for alarm clock widget  149 - 4 , labeled “Clock;”   Icon  442  for workout support module  142 , labeled “Workout Support;”   Icon  444  for notes module  153 , labeled “Notes;” and   Icon  446  for a settings application or module, labeled “Settings,” which provides access to settings for device  100  and its various applications  136 .   
               

     It should be noted that the icon labels illustrated in  FIG.  4 A  are merely exemplary. For example, icon  422  for video and music player module  152  is labeled “Music” or “Music Player,” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon. 
       FIG.  4 B  illustrates an exemplary user interface on a device (e.g., device  300 ,  FIG.  3   ) with a touch-sensitive surface  451  (e.g., a tablet or touchpad  355 ,  FIG.  3   ) that is separate from the display  450  (e.g., touch screen display  112 ). Device  300  also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors  359 ) for detecting intensity of contacts on touch-sensitive surface  451  and/or one or more tactile output generators  357  for generating tactile outputs for a user of device  300 . 
     Although some of the examples that follow will be given with reference to inputs on touch screen display  112  (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in  FIG.  4 B . In some embodiments, the touch-sensitive surface (e.g.,  451  in  FIG.  4 B ) has a primary axis (e.g.,  452  in  FIG.  4 B ) that corresponds to a primary axis (e.g.,  453  in  FIG.  4 B ) on the display (e.g.,  450 ). In accordance with these embodiments, the device detects contacts (e.g.,  460  and  462  in  FIG.  4 B ) with the touch-sensitive surface  451  at locations that correspond to respective locations on the display (e.g., in  FIG.  4 B,  460    corresponds to  468  and  462  corresponds to  470 ). In this way, user inputs (e.g., contacts  460  and  462 , and movements thereof) detected by the device on the touch-sensitive surface (e.g.,  451  in  FIG.  4 B ) are used by the device to manipulate the user interface on the display (e.g.,  450  in  FIG.  4 B ) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein. 
     Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by, ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously. 
       FIG.  5 A  illustrates exemplary personal electronic device  500 . Device  500  includes body  502 . In some embodiments, device  500  can include some or all of the features described with respect to devices  100  and  300  (e.g.,  FIGS.  1 A- 4 B ). In some embodiments, device  500  has touch-sensitive display screen  504 , hereafter touch screen  504 . Alternatively, or in addition to touch screen  504 , device  500  has a display and a touch-sensitive surface. As with devices  100  and  300 , in some embodiments, touch screen  504  (or the touch-sensitive surface) optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touch screen  504  (or the touch-sensitive surface) can provide output data that represents the intensity of touches. The user interface of device  500  can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device  500 . 
     Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety. 
     In some embodiments, device  500  has one or more input mechanisms  506  and  508 . Input mechanisms  506  and  508 , if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device  500  has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device  500  with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device  500  to be worn by a user. 
       FIG.  5 B  depicts exemplary personal electronic device  500 . In some embodiments, device  500  can include some or all of the components described with respect to  FIGS.  1 A,  1 B , and  3 . Device  500  has bus  512  that operatively couples I/O section  514  with one or more computer processors  516  and memory  518 . I/O section  514  can be connected to display  504 , which can have touch-sensitive component  522  and, optionally, intensity sensor  524  (e.g., contact intensity sensor). In addition, I/O section  514  can be connected with communication unit  530  for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. Device  500  can include input mechanisms  506  and/or  508 . Input mechanism  506  is, optionally, a rotatable input device or a depressible and rotatable input device, for example. Input mechanism  508  is, optionally, a button, in some examples. 
     Input mechanism  508  is, optionally, a microphone, in some examples. Personal electronic device  500  optionally includes various sensors, such as GPS sensor  532 , accelerometer  534 , directional sensor  540  (e.g., compass), gyroscope  536 , motion sensor  538 , and/or a combination thereof, all of which can be operatively connected to  110  section  514 . 
     Memory  518  of personal electronic device  500  can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors  516 , for example, can cause the computer processors to perform the techniques described below, including processes  700 ,  800 ,  900 , and  1100  ( FIGS.  7 A,  7 B,  8 A,  8 B,  9 ,  11 A, and  11 B ). A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. 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. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device  500  is not limited to the components and configuration of  FIG.  5 B , but can include other or additional components in multiple configurations. 
     As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices  100 ,  300 , and/or  500  ( FIGS.  1 A,  3 , and  5 A- 5 B ). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) each optionally constitute an affordance. 
     As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad  355  in  FIG.  3    or touch-sensitive surface  451  in  FIG.  4 B ) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system  112  in  FIG.  1 A  or touch screen  112  in  FIG.  4 A ) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user&#39;s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device). 
     As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation. 
     In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity. 
     The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to 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 operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures. 
     An increase of characteristic intensity of the 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 of characteristic intensity of the 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 of characteristic intensity of the 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 the contact on the touch-surface. A decrease of characteristic intensity of the 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 are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where 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 operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input). 
     In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances). 
     For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally; in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold; the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. 
     As used herein, the terms “open application” or “executing application” refer to a software application with retained state information (e.g., as part of device/global internal state  157  and/or application internal state  192 ). An open or executing application is, optionally, any one of the following types of applications:
         an active application, which is currently displayed on a display screen of the device that the application is being used on;   a background application (or background processes), which 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, which is not running, but has state information that is stored in memory (volatile and non-volatile, respectively) and that can be used to resume execution of the application.       

     As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application. 
     Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device  100 , device  300 , or device  500 . 
       FIGS.  6 A- 6 I  illustrate exemplary user interfaces for presenting activity trends, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIGS.  7 A,  7 B,  8 A,  8 B, and  9   . 
       FIG.  6 A  depicts electronic device  600  displaying home user interface  604  via display device  602 . In some examples, electronic device  600  includes one or more features of devices  100 ,  300 , or  500 . Home user interface  604  includes multiple affordances, each affordance for initiating a different application. For example, the multiple affordances include activity affordance  606  for initiating an activity application (e.g., an application corresponding to physical activity performed by a user associated with electronic device  600 ). 
     As depicted in  FIG.  6 A , electronic device  600  receives user input  607  corresponding to selection of activity affordance  606 . User input  607  can include a touch gesture, such as a tap gesture on activity affordance  606 , causing the activity application to be initiated (e.g., display of a user interface of the activity application, such as information user interface  608  (depicted in  FIG.  6 B ) or 90-day trends user interface  612  (depicted in  FIGS.  6 C- 6 F ), 
       FIG.  6 B  depicts electronic device  600  displaying information user interface  608  for an activity application (e.g., the activity application discussed above for  FIG.  6 A ). Information user interface  608  is an example of a first user interface displayed when initiating the activity application. In some examples, information user interface  608  is displayed at an initial time that a user navigates to the activity application after content to implement activity trends (e.g., techniques described in methods  700 ,  800 , or  900 ) has been received by electronic device  600  (e.g., after an update or after an installation of the activity application at a time after the content has been added to the activity application). 
     In some examples, information user interface  608  is displayed in response to receiving user input (e.g., user input  607 ) corresponding to selection of an activity affordance (e.g., activity affordance  606 ). It should be recognized that other user interfaces (e.g., 90-day, trends user interface  612 , as depicted in  FIG.  6 C ) can be displayed when initiating the activity, application, such as when information user interface  608  has been previously dismissed. In some examples, one or more user inputs must be received before displaying information user interface  608  and/or 90-day trends user interface  612 . 
     Information user interface  608  provides information related to how activity trends in the activity application work. For example,  FIG.  6 B  depicts information user interface  608  including text that states “Closing your rings everyday will create trends with your activity data. See your comparison of the past 90 days with the past year,” 
     Information user interface  608  includes continue affordance  610 . Selection of continue affordance  610  dismisses information user interface  608  and causes a different user interface to be displayed (e.g., 90-day trends user interface  612 , as depicted in  FIG.  6 C ). As depicted in  FIG.  6 B , electronic device  600  receives user input  611  corresponding to selection of continue affordance  610 . User input  611  can include a touch gesture, such as a tap gesture on continue affordance  610 . 
       FIG.  6 C  depicts electronic device  600  displaying an instance of 90-day trends user interface  612  via display device  602  when an insufficient amount of data to identify a trend has been received for multiple activity metrics. As used herein, a trend corresponds to a comparison of data within a first time period (e.g., 90 days) and data within a second time period (e.g., 365 days), where the first time period is included within the second time period. In some examples, a trend can be identified with less than a full time period. For example, instead of requiring 365 days of activity data for an activity metric, a trend for the activity metric can be identified when there is at least 180 days of activity data for the activity data, where (1) the remaining days without activity data are ignored when identifying the trend and (2) the shorter of the two time periods is potentially shortened to maintain a similar percentage between the two percentages (e.g., when 180 days is received, the shorter of the two time periods can be 45). As shown,  FIG.  6 C  is a user interface shown after four days of activity is received for a user associated with electronic device  600 . For clarity of the examples discussed herein, a table is provided below to provide examples of different trend classifications for different scenarios. 
     
       
         
           
               
               
               
               
             
               
                   
               
               
                   
                   
                 Difference between 
                   
               
               
                 90 day 
                 365 day 
                 90 day average and 
               
               
                 average 
                 average 
                 365 average 
                 Trend Assessment 
               
               
                   
               
             
            
               
                   
               
            
           
           
               
               
               
               
            
               
                 90 
                 100 
                 −10 
                 Negative 
               
               
                 100 
                 100 
                 0 
                 Neutral (in some examples 
               
               
                   
                   
                   
                 herein, classified as positive) 
               
               
                 110 
                 100 
                 10 
                 Positive 
               
               
                   
               
            
           
         
       
     
     The instance of 90-day trends user interface  612  as depicted in  FIG.  6 C  includes insufficient data portion  614  with header portion  616  and representations for multiple activity metrics, such as move representation  618 . Header portion  616  includes a predicted amount of time before a sufficient amount of data will have been received. For example, header portion  616  includes text stating: “Ready in: 26 days.” Such text indicates that it is estimated that the activity application will have enough data to present activity trends via 90-day trends user interface  612  in 26 days. The estimate can be calculated based on forecasting that sufficient information will be received each day for the next 26 days, satisfying an amount of activity data to provide activity trends after the 26 days. Header portion  616  includes information regarding why it will take 26 days to be ready (e.g., “It takes 30 days of activity to start your trends.”). 
     As indicated above, insufficient data portion  614  includes move representation  618 . Move representation  618  corresponds to activity data related to a move activity metric (e.g., an amount of movement that is determined for a user). Move representation  618  includes identification information  618   a  indicating that move representation  618  relates to the move activity metric (the “move” text), icon  618   b  indicating that there is insufficient activity data received for the move activity metric to determine an activity trend for the move activity metric (the “−” with a circle around it), placeholder information  618   c  indicating an average value for move representation  618  is unavailable (the “−/− cal avg” text), and description  618   d  (the “this trend measures the active calories you burn” text). Other examples of representations for activity metrics depicted in  FIG.  6 C  include exercise, stand, and move minutes. Each of the other examples of representations include similar content as move representation  618 . 
       FIG.  6 D  depicts electronic device  600  displaying an instance of 90-day trends user interface  612  via display device  602  when all activity metrics have a negative trend within the last 90 days as compared to the last 365 days. It should be recognized that trends might be over different times from 90 days and 365 days (such as more or less than 90 days and/or more or less than 365 days). In some examples, the trends are based on rolling time periods. In some examples, a rolling time period means that, as a new day is added to a time period, an oldest day in the time period is removed. For example; a rolling time period of 90 days means that at day 90) the rolling time period equals day 1 to day 90 and at day 91 the rolling time period equals day 2 to day 91. 
       FIG.  6 D  depicts 90-day trends user interface  612  at least 30 days after at least 30 days of activity data is received. For example, the instance of 90-day trends user interface  612  depicted in  FIG.  6 D  can be displayed 26 days after the instance of 90-day trends user interface  612  depicted in  FIG.  6 C  is displayed. In some examples, activity trends (e.g., move representation  624 ) in 90-day trends user interface  612  are refreshed daily such that activity trends are updated each day. The instance of 90-day trends user interface  612  depicted in  FIG.  6 D  includes negative trend portion  620  with overall coaching portion  622  and representations for multiple activity metrics, including move representation  624 . 
     Overall coaching portion  622  includes text providing a summary of the included activity metrics. For example, overall coaching portion  622  includes text stating: “Your trends need some attention. You&#39;ve got this, John!” 
     The representations for multiple activity metrics included in negative trend portion  620  each are associated with a different activity metric that has been determined to have a negative trend (e.g., an average of an activity metric for the past 90 days is less than an average of the activity metric for the past 365 days). For example, negative trend portion  620  includes move representation  624 . Move representation  624  corresponds to activity data related to a move activity metric (e.g., an amount of movement that is determined for a user). Move representation  624  includes identification information  624   a  indicating that it relates to the move activity metric (the “move” text), icon  624   b  indicating that the move activity metric is trending down (the “V” with a circle around it), average value  624   c  indicating an average value for the move activity metric over the last 90 days (the “400 cal avg” text), comparison value  624   d  indicating the difference between the average value for the move activity metric over the last 90 days and an average value for the move activity metric over the last 365 days (“−60”), and coaching indication  624   e  (the “Try to move around for 10 extra minutes” text). Other examples of representations depicted in  FIG.  6 D  include exercise, stand, and move minutes. Each of the other examples of presentations include similar content as move representation  618 , including their own coaching indication (e.g.,  626   e ,  628   e , and  630   e ). 
     In some examples, coaching indications are only provided to representations corresponding to activity metrics with a negative trend over the last 90 days as compared to the last 365 days. In such examples, coaching indications include a prediction for when a negative trend will transition to a neutral or positive trend. 
     In some examples, coaching indications are modified based on an amount of time it would take for an average of the corresponding activity metric to transition to a neutral or positive trend when forecasting an estimated increase (e.g., 10% per day). In some examples, the estimated increase can be capped based on a threshold for the corresponding activity metric (e.g., an estimated increase for standing cannot cause a stand goal of greater than 14 hours). In some examples, the amount of time affects how the coaching indications are modified. For example: when the amount of time is less than a week, a coaching indication includes a prediction with the amount of time; when the amount of time is more than a week and less than two weeks, a coaching indication includes a prediction with the amount of time rounded to a single week; when the amount of time is more than two weeks, a coaching indication does not include a prediction of time. In some examples, different activity metrics use a different estimated increase. 
     In some examples, forecasting includes simulating the estimated increase by: (1) forming a histogram associated with activity data for each of a shorter time period (e.g., the last 90 days) and a longer time period (e.g., the last 365 days) (e.g., each bin in the histogram corresponding to an average of activity data for a particular activity metric for a different day); (2) removing an oldest bin from the histogram; (3) adding a new bin to the histogram for the next day with a value corresponding to a value of activity data for a particular activity metric for a current day and the estimated increase (e.g., if the value for the current day is 10 and the estimated increase is 1 (e.g., 10% of the value for the current day), the value for the new bin would be 11 instead of 10); and (4) repeating 2 and 3 until the corresponding activity metric transitions to a neutral or positive trend. In some examples, when repeating 3, the estimated increase can be the same for each additional day (e.g., based on example above, if the estimated increase is 1 and a value for a previous day is 11, the value for a current day would be 12), become zero after the first day (e.g., based on example above, if the estimated increase becomes 9 after the first day and a value for a previous day is 11, the value for a current day would be 11 instead of continuing to increase to 12), or change each day based on some function (e.g., f(x)=1/x). 
     In some examples, coaching indications are modified based on a recent trend within the last 90 days, such as the last 15 days. In one example, the recent trend is determined using the Mann-Kendall (MK) test to look at pairs of data in a given data set to identify whether a monotonic trend is present. 
     For clarity of the examples discussed above, a table is provided below to provide examples of different coaching indications for different scenarios with a description of why the coaching indication is what it is. 
     
       
         
           
               
               
               
             
               
                   
               
               
                   
                   
                 Explanation of coaching 
               
               
                 Trend classification 
                 Example coaching indication 
                 indication 
               
               
                   
               
             
            
               
                 Positive trend for 90/365 and 
                 “Getting better every day, keep 
                 Based on having a positive 
               
               
                 recently positive within 90 
                 it up!” 
                 trend and recently positive, 
               
               
                   
                   
                 a coaching indication 
               
               
                   
                   
                 should encourage similar 
               
               
                   
                   
                 behavior in the future. 
               
               
                 Positive trend for 90/365 and 
                 “While you are above average 
                 Based on having a positive 
               
               
                 recently negative within 90 
                 for the last 90 days, you are 
                 trend but recently negative, 
               
               
                   
                 starting to lose some ground.” 
                 a coaching indication 
               
               
                   
                   
                 should recognize the 
               
               
                   
                   
                 positive trend but be more 
               
               
                   
                   
                 cautionary due to the 
               
               
                   
                   
                 recent negative trend. 
               
               
                 Negative trend for 90/365 but 
                 “Keep doing what you are 
                 Based on having a 
               
               
                 recently positive within 90 
                 doing and you will be back to 
                 negative trend but recently 
               
               
                   
                 your yearly average in no 
                 positive, a coaching 
               
               
                   
                 time.” 
                 indication should 
               
               
                   
                   
                 recognize that the user is 
               
               
                   
                   
                 improving. 
               
               
                 Negative trend for 90/365 and 
                 “Don&#39;t forget to stand for one 
                 Based on having a 
               
               
                 recently negative within 90 
                 minute per hour throughout the 
                 negative trend and recently 
               
               
                   
                 day, you are getting farther 
                 negative, a coaching 
               
               
                   
                 from your average lately.” 
                 indication should identify 
               
               
                   
                   
                 that a user is falling farther 
               
               
                   
                   
                 behind. 
               
               
                 Negative trend for 90/365 that 
                 “Try to move around for 10 
                 Based on being able to 
               
               
                 can transition to a positive 
                 extra minutes for the next 3 
                 transition within a week, a 
               
               
                 trend within a week if to 
                 days and you will be right back 
                 coaching indication should 
               
               
                 maintain a 10% increase in 
                 to your yearly average.” 
                 identify a number of days 
               
               
                 average value as compared to 
                   
                 it takes to transition to a 
               
               
                 the last 90 days 
                   
                 positive trend with an 
               
               
                   
                   
                 estimated increase. 
               
               
                 Negative trend for 90/365 that 
                 “Walk an extra 10 minutes 
                 Based on being able to 
               
               
                 can transition to a positive 
                 each day and you&#39;ll be back on 
                 transition longer than a 
               
               
                 trend longer than a week but 
                 track in 1 week.” 
                 week but within a few 
               
               
                 within a few weeks if maintain 
                   
                 weeks, a coaching 
               
               
                 a 10% increase in average 
                   
                 indication should identify a 
               
               
                 value as compared to the last 
                   
                 way for a user to reach the 
               
               
                 90 days 
                   
                 yearly average but round 
               
               
                   
                   
                 to the nearest week. 
               
               
                 Negative trend for 90/365 that 
                 “Let&#39;s get back to the swing of 
                 Based on being able to 
               
               
                 can transition to a positive 
                 things and walk a couple of 
                 transition longer than a 
               
               
                 trend over a few weeks if 
                 minutes each day.” 
                 few weeks, a coaching 
               
               
                 maintain a 10% increase in 
                   
                 indication should not 
               
               
                 average value as compared to 
                   
                 include any particular way 
               
               
                 the last 90 days 
                   
                 to improve, such as a 
               
               
                   
                   
                 number of days or even an 
               
               
                   
                   
                 amount of activity per day. 
               
               
                   
               
            
           
         
       
     
       FIG.  6 E  depicts electronic device  600  displaying an instance of 90-day trends user interface  612  via display device  602  when some activity metrics have a positive trend and other activity metrics have a negative trend within the last 90 days as compared to the last 365 days.  FIG.  6 E  depicts 90-day trends user interface  612  at least 30 days after at least 30 days of activity data is received. The instance of 90-day trends user interface  612  depicted in  FIG.  6 E  includes positive trend portion  632  and negative trend portion  638 , each with an overall coaching indication for the respective portion (e.g., overall coaching indication  634  and overall coaching indication  640 ). In one example, overall coaching indication  634  for positive trend portion  632  includes the text “Keep it going” and overall coaching indication  640  for negative trend portion  638  includes the text “Make it happen”). In some examples, the instance of 90-day trends user interface  612  depicted in  FIG.  6 E  (or any instances of 90-day trends user interface  612 ) includes an insufficient data portion (not illustrated, but similar to insufficient data portion  614  in the instance of 90-day trends user interface  612  depicted in  FIG.  6 C ) for one or more activity metrics with an insufficient amount of corresponding data. In one example, the insufficient data portion is below negative trend portion  638 . 
     As mentioned above, the instance of 90-day trends user interface  612  as depicted in  FIG.  6 E  includes positive trend portion  632  with representations for multiple activity metrics that have each been determined to be trending up or neutral (e.g., an average of an activity metric for the past 90 days is equal to or greater than an average of the activity metric for the past 365 days). For example, positive trend portion  632  includes move representation  636 . Move representation  636  corresponds to activity data related to a move activity metric (e.g., an amount of movement that is determined for a user). Move representation  636  includes identification information  636   a  indicating that it relates to the move activity metric (the “move” text), icon  636   b  indicating that the move activity metric has a positive trend over the last 90 days as compared to the last 365 days (the “{circumflex over ( )}” with a circle around it), and average value  636   c  indicating that the move activity metric has averaged 460 calories over the last 90 days (the “460 cal avg” text). 
     It should be recognized that the move representation, when in positive trend portion  632  does not include a comparison value indicating the difference between the average value for the move activity metric over the last 90 days and an average value for the move activity metric over the last 365 days and/or a coaching indication while both such content is provided for activity metrics in negative trend portion  638 . In some examples, only providing the difference and/or the coaching indication in negative trend portion  638  allows a system to not push users into thinking they need to keep increasing their trend. Similarly, classifying equal as positive, allows a system to not push users into thinking they need to keep increasing their trend. 
     Other examples of representations of activity metrics in positive trend portion  632  depicted in  FIG.  6 E  include exercise, move minutes, walking speed, workout intensity, and flights climbed. While each of the other examples of representations of activity metrics in positive trend portion  632  include similar content as move representation  636 , it should be recognized that different representations sometimes have different units of measure. For example, an exercise activity representation, as depicted in  FIG.  6 E , includes text indicating exercise activity metric averaged 36 minutes per day for the last 90 days. 
     As mentioned above, the instance of 90-day trends user interface  612  as depicted in FIG. OF includes negative trend portion  638  with representations for multiple activity metrics that are each associated with a different activity metric that has been determined to have a negative trend (e.g., an average of an activity metric for the past 90 days is less than an average of the activity metric for the past 365 days). For example, negative trend portion  638  includes stand representation  642 . Stand representation  642  corresponds to activity data related to a stand activity metric (e.g., a number of hours per day where a user has determined to have stood for at least one hour). Stand representation  642  includes identification information  642   a  indicating that it relates to the stand activity metric (the “stand” text), icon  642   b  indicating that the stand activity metric has a negative trend over the last 90 days as compared to the last 365 days (the “V” with a circle around it), average value  642   c  indicating that the stand activity metric has averaged 10 hours per day over the last 90 days (the “10 hr avg” text), comparison value  642   d  indicating the difference between the average value for the stand activity metric over the last 90 days and an average value for the stand activity metric over the last 365 days (“−2”), and coaching indication  642   e  (the “Don&#39;t forget to stand for one minute per hour throughout the day” text). The other example of a representation in negative trend portion  638  depicted in FIG. OF is walking distance representation  644 . Walking distance representation  644  includes similar content as stand representation  642 , including its own coaching indication ( 644   e ). 
     It should be recognized that the order within each portion (e.g., positive trend portion  632  and negative trend portion  638 ) maintains the order of representations as provided in instances discussed above. A representation not included in one of the portions continues the order in another portion. For example, the order in FIG. OD is move, exercise, stand, and move minutes and the order in positive trend portion  632  is move, exercise, and move minutes, with stand missing from positive trend portion  632  because move minutes did not have a positive trend. In  FIG.  6 D , it can be seen that stand is the first representation in negative trend portion  638 . 
     In some examples, one or more icons in positive trend portion  632  (e.g.,  636   b ) (e.g., in some examples, all of the icons in positive trend portion  632 , either sequentially or at the same time) are animated (e.g., bounce in an upward direction) in response to displaying the instance of 90-day trends user interface  612  depicted in  FIG.  6 E . After a time threshold (e.g., zero or more; in some examples, non-zero) after animating the one or more icons in positive trend portion  632  has passed, one or more icons in negative trend portion  638  (e.g.,  642   b ) (e.g., in some examples, all of the icons in negative trend portion  638 , either sequentially or at the same time) are animated (e.g., bounce in a downward direction). By animating icons associated with negative trend portion  638  after animating icons associated with positive trend portion  632 , the instance of 90-day trends user interface  612  as depicted in  FIG.  6 E  can draw emphasis to representations in negative trend portion  638 . 
       FIG.  6 F  depicts electronic device  600  displaying an instance of 90-day trends user interface  612  via display device  602  when all activity metrics have a positive trend within the last 90 days as compared to the last 365 days.  FIG.  6 F  depicts 90-day trends user interface  612  at least 30 days after at least 30 days of activity data is received. The instance of 90-day trends user interface  612  depicted in  FIG.  6 F  includes positive trend portion  646  and an overall coaching indication stating “You&#39;re doing great!” 
     Positive trend portion  646  includes representations for multiple activity metrics that have each been determined to be neutral or positive (e.g., an average of an activity metric for the past 90 days is equal to or greater than an average of the activity metric for the past 365 days). For example, positive trend portion  646  includes exercise representation  648  and fitness levels representation  650 . Exercise representation  648  corresponds to activity data related to an exercise activity metric (e.g., an amount of time for which a user has been detected exercising). Fitness levels representation  650  corresponds to activity data related to a different exercise metric (e.g., a determined workout intensity for a user). It should be recognized that fitness levels representation  650  has not been displayed in other instances of 90-day trends user interface  612  described above. This is illustrating that some representations might only be displayed when there is at least some activity data received for a respective activity metric or there is enough activity data received for the respective activity metric to identify a trend (e.g., 37 VO 2  max avg). This allows for metrics that are often used to always show some representation (e.g., sometimes a null value) and other metrics that are not often used (or that require special equipment) to only show when either some activity data has been received or enough activity data has been received to provide a trend. 
     As depicted in  FIG.  6 F , electronic device  600  receives user input  649  corresponding to selection of exercise representation  648 . User input  649  can include a touch gesture, such as a tap gesture on exercise representation  648 , causing a detailed activity metric user interface corresponding to exercise representation  648  to be displayed (e.g., detailed exercise user interface  652 , as depicted in  FIG.  6 G ). 
       FIG.  6 G  depicts electronic device  600  displaying detailed exercise user interface  652 . In some examples, detailed exercise user interface  652  is displayed in response to receiving user input (e.g., user input  649 ) corresponding to selection of exercise representation  648 . In some examples, one or more user inputs must be received before displaying detailed exercise user interface  652 . It should be recognized that other detailed activity metric user interfaces can be displayed when other activity metric representations are selected, the other detailed activity metric user interfaces corresponding to whichever activity metric representation is selected. 
     Detailed exercise user interface  652  includes identification information  654 , indicating the activity metric that detailed exercise user interface  652  corresponds. For example, identification information  654  states that detailed exercise user interface  652  corresponds to an exercise activity metric. 
     Detailed exercise user interface  652  includes summary portion  656 . Summary portion  656  includes textual representation  656   a  indicating whether the exercise activity metric is trending down (e.g., an average of the last 90 days is less than an average of the last 365 days) (where textual representation would be “trending down,” as illustrated), trending up (e.g., an average of the last 90 days is more than an average of the last 365 days) (where textual representation would be “trending up”), or trending neutral (e.g., an average of the last 90 days is equal to an average of the last 365 days) (where textual representation would be “staying consistent”). It should be recognized that trending neutral and trending up can be grouped together such that a system does not distinguish between the two, and instead uses the trending up for when the trend is up or neutral. Summary portion  656  includes icon  656   b  indicating that the exercise activity metric has a positive trend over the last 90 days as compared to the last 365 days (the “{circumflex over ( )}” with a circle around it). Summary portion  656  includes average value  656   c  indicating that the exercise activity metric has averaged 36 minutes per day over the last 90 days (the “36 min avg” text). Summary portion  656  includes difference indicator  656   d  indicating a difference between an average of the last 90 days and an average of the last 365 days (“+3”). Summary portion  656  includes summary information  656   e  with a textual equivalent of icon  656   b . Summary portion  656  includes coaching indication  656   f  indicating a suggestion for the exercise activity metric going forward. As depicted in  FIG.  6 G , coaching indication  656   f  states “Keep it going, John!,” reflecting that the exercise activity metric is trending upward. It should be recognized that summary portion  656  can include a subset of what was described above (e.g., summary portion  656  might not include textual representation  656   a ). 
     Detailed exercise user interface  652  includes weekly representation  658  to visually represent activity data for the exercise activity metric over the last 365 days. In some examples, such as depicted in  FIG.  6 G , weekly representation  658  is a bar graph with x-axis corresponding to time (e.g., weeks over the last 365 days) and y-axis corresponding to an average value for the exercise activity metric over either the last 90 days or the last 365 days. In such examples, weekly representation  658  is divided into weeks using a bar for each week (e.g., 52 bars). In some examples, the x-axis of weekly representation  658  is labeled by month and the range of the y-axis is from 0 to a maximum average value over the last 365 days (e.g., 40, as depicted in  FIG.  6 G ). 
     As depicted in  FIG.  6 G  in weekly representation  658 , bars associated with time periods within the last 90 days are visually distinguished (e.g., different patterns or different colors) from bars associated with time periods within the last 365 days. In one example, the bars associated with the last 90 days are green while the bars associated with the last 365 days are gray. When a week does not have any corresponding activity data, a bar is not displayed for the week (e.g., 51 bars will be displayed instead of 52). In some examples, weekly representation  658  includes an additional indication to separate representations corresponding to the last 90 days and representations corresponding to the last 365 days but not the last 90 days. For example, in  FIG.  6 G , vertical line  658   c  is inserted separating the two groups of bars. 
     Weekly representation  658  includes 90-day average representation  658   a  and 365-day average representation  658   b , where 90-day average indication  658   a  indicates an average for the last 90 days and 365-day average representation  658   b  indicates an average for the last 365 days (including the last 90 days). As depicted in  FIG.  6 G , each of 90-day average representation  658   a  and 365-day average representation  658   b  is a visually distinct line at a vertical location corresponding to a value of the corresponding average (e.g., because the average for the last 90 days is greater than the average for the last 365 days, 90-day average representation  658   a  is arranged at a vertical location higher than 365-day average representation  658   b ). In some examples, 90-day average representation  658   a  includes an indication regarding whether the average for the last 90 days is equal to or greater than the average for the last 365 days. For example, as depicted in  FIG.  6 G , 90-day average representation  658   a  includes “{circumflex over ( )},” indicating that the average for the last 90 days is equal to or greater than the average for the last 365 days. Similarly, if the average for the last 90 days is lower than the average for the last 365 days, 90-day average representation  658   a  can include “V.” 
     Detailed exercise user interface  652  includes daily averages representation  660  to compare activity data for the exercise activity metric for particular days of a week over the last 90 days and the last 365 days. In some examples, such as depicted in  FIG.  6 G , daily averages representation  660  includes a visual representation for comparing the activity data (e.g., a bar graph with x-axis corresponding to different days of the week and y-axis corresponding to an average value for the exercise activity metric over the last 90 days and the last 365 days). In such examples, the range of the y-axis is from 0 to a maximum average value over the last 365 days (e.g., 40, as depicted in  FIG.  6 G ). 
     As depicted in  FIG.  6 G  in daily averages representation  660 , bars associated with time periods corresponding to the last 90 days are visually distinguished (e.g., different patterns or different colors) from bars associated with time periods corresponding to the last 365 days. In one example, the bars corresponding to the last 90 days are green while the bars corresponding to the last 365 days are gray. As depicted in  FIG.  5 G  in weekly representation  658 , bars associated with time periods (e.g., days within a week or hours within a day) within the last 90 days are paired (e.g., adjacent with no intervening representations) with bars associated with corresponding time periods within the last 365 days (e.g., a bar associated with Mondays within the last 90 days is paired with a bar associated with Mondays within the last 365 days. 
     Daily averages representation  660  includes textual representations (e.g.,  660   a  and  660   b ) to correspond to the visual representation. For example, as depicted in  FIG.  6 A , daily averages representation  660  includes a table under the visual representation, with numbers corresponding to the bar graph, such as 32 and 38 being located such as to appear to corresponding to the Monday section of the bar graph. In some examples, numbers corresponding to the last 90 days are on a first line of the table and numbers corresponding to the last 365 days are on a second line, under the first line. In some examples, numbers corresponding to the last 90 days are visually distinct (e.g., different patterns or different colors) from numbers corresponding to the last 365 days. In one example, the numbers for the last 90 days are green while the numbers for the last 365 days are gray. 
     It should be recognized that some detailed activity metric user interfaces might not include a daily averages representation, such as detailed activity metric user interfaces corresponding to an action not often performed every day (e.g., running speed). For example, an action related to exercising can, instead of a daily averages representation, include a representation to compare activity data for an activity metric for a particular time period (other than days of a week) over the last 90 days and the last 365 days, such as hour, week, or month. 
     Detailed exercise user interface  652  includes exercise rings closed representation  662  to compare an activity metric associated with but different from the exercise activity metric. For example, exercise rings closed representation  662  relates to exercise rings closed, which is an activity metric corresponding to a predefined or user-defined threshold of an amount of exercise per day. In one example, exercise rings closed is associated with the exercise activity metric because an exercise ring closes based on the exercise activity metric exceeding a threshold in a given day. 
     Exercise rings closed representation  662  includes 90 days representation  662   a  and 365 days representation  662   b.  90 days representation  662   a  includes a textual representation of a number of days out of the last 90 days that a user closed their exercise rings (e.g., “79/90 Days”) and a percentage for the number of days out of the last 90 days (e.g., “88%). 365 days representation  662   b  includes a textual representation of a number of days out of the last 365 days that a user closed their exercise rings (e.g., “284/365 Days”) and a percentage for the number of days out of the last 365 days (e.g., “77%). In some examples, 90 days representation  662   a  is visually distinguished from 365 days representation  662   b  (e.g., 90 days representation  662   a  is green and 365 days representation  662   b  is gray). 
       FIG.  6 H  depicts electronic device  664  displaying ready-to-user user interface  670  via display device  668  when activity trends (e.g., such as depicted in  FIG.  6 D ) are ready to be viewed on a second device (e.g., electronic device  600 ). In some examples, electronic device  664  includes one or more features of devices  100 ,  300 ,  500 , or  600 . In some examples, ready-to-user user interface  670  includes positive trend portion  674 , with display of multiple representations for different activity metrics (e.g., move representation or exercise representation). As depicted in  FIG.  6 H , each representation includes an identification of an activity metric corresponding to the representation (e.g., “Move”), an icon corresponding to a comparison of the activity metric for the last 90 days as compared to the activity metric for the last 365 days (e.g., icon with “{circumflex over ( )}”), and a value corresponding to a summary of the activity metric for the last 90 days (e.g., “460 cal avg”). In ready-to-user user interface  670  as depicted in  FIG.  6 H , all activity metrics have a positive trend within the last 90 days as compared to the last 365 days. It should be recognized that this is just an example and other combinations of all negative trends or a mix of some positive trends and some negative trends are possible. 
       FIG.  6 I  depicts electronic device  664  displaying mid-month-update user interface  678  via display device  668  when activity trends (e.g., such as depicted in  FIG.  6 D ) are available to be viewed on a second device (e.g., electronic device  600 ). In some examples, mid-month-update user interface  678  is pushed to be displayed via display device  668  (e.g., from electronic device  600 ) once per a particular time period (e.g., a month). However, it should be recognized that mid-month-update user interface  678  can be caused to be displayed at a different rate. 
     In some examples, mid-month-update user interface  678  includes positive trend portion  682  and negative trend portion  684 , each with display of multiple representations for different activity metrics (e.g., move representation or exercise representation). As depicted in  FIG.  6 I , each representation in positive trend portion  682  includes an identification of an activity metric corresponding to the representation (e.g., “Move”), an icon corresponding to a comparison of the activity metric for the last 90 days as compared to the activity metric for the last 365 days (e.g., icon with “{circumflex over ( )}”), and a value corresponding to the comparison (e.g., “460 cal avg”). As depicted in  FIG.  6 I , each representation in negative trend portion  684  includes an identification of an activity metric corresponding to the representation (e.g., “Move minutes”), an icon corresponding to a comparison of the activity metric for the last 90 days as compared to the activity metric for the last 365 days (e.g., icon with “V”), a value corresponding to a summary of the activity metric for the last 90 days (e.g., “30 min avg”), and a difference between the summary of the activity metric for the last 90 days and a summary of the activity metric for the last 365 days (e.g., (“−4”). 
     In mid-month-update user interface  678  as depicted in  FIG.  6 I , some activity metrics have a positive trend and other activity metrics have a negative trend within the last 90 days as compared to the last 365 days. It should be recognized that this is just an example and other combinations of all positive trends or all negative trends are possible. 
       FIGS.  7 A- 7 B  are a flow diagram illustrating method  700  for presenting activity trends (e.g., organizing activity metrics by trends (e.g., upwards/downwards) over time) using an electronic device in accordance with some embodiments. Method  700  relates to displaying a user interface (e.g., 90-day trend home page) with trend representation(s), each representation corresponding to a different activity metric, where placement of a trend representation is based on whether the trend representation is determined to currently be a first classification (e.g., no change or positive) or a second classification (e.g., negative). Method  700  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 ,  664 ) with a display device. Some operations in method  700  are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  700  provides an intuitive way for presenting activity trends. The method reduces the cognitive burden on a user for presenting activity trends, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to identify activity trends faster and more efficiently conserves power and increases the time between battery charges. 
     At  702 , the device (e.g.,  600 ,  664 ) receives activity data corresponding to a first activity metric (e.g., data corresponding to a measured level of activity for a user of the electronic device (e.g., data for activity performed by the user while wearing the electronic device)) for a first time period (e.g., 3 months). 
     At  704 , the device receives activity data corresponding to the first activity metric for a second time period (e.g., 1 year) different from the first period of time. 
     At  706 , the devices receives a request (e.g.,  607  or  611 ) to display a first user interface (e.g.,  612 ) (e.g., user interface that includes comparisons of activity data for a plurality of activity metrics). 
     At  708 , the device, in response to receiving the request, displays, via the display device, the first user interface. 
     At  710 , the first user interface includes, in accordance with a determination that a relationship (e.g., a mathematical relationship; a mathematical comparison) between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type (e.g., the activity data (e.g., an average value of the activity data) for the first time period reflects no change or a positive change relative to the activity data (e.g., an average value of the activity data) for the second time period), displaying a representation (e.g.,  636 ) (e.g., a graphical or textual indication of the first activity metric) of the first activity metric in a first portion (e.g.,  626 ) of the first user interface. 
     At  712 , the first user interface includes, in accordance with a determination that the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a second type (e.g., the activity data for the first time period reflects a negative change relative to the activity data for the second time period) (e.g., negative), displaying the representation (e.g.,  642 ) (e.g., up arrow or down arrow) of the first activity metric in a second portion (e.g.,  636 ) of the first user interface different from the first portion (in some examples, representations determined to be of the first type are visually grouped within the user interface to be separate from representations determined to be of the second type). Dynamically placing a representation of an activity metric (e.g., in a first portion or a second portion of a user interface) based on a relationship between activity data associated with the activity metric over different time periods provides a user with visual feedback about a current state of the activity metric and data stored on a device. For example, such placement allows a user to quickly identify activity metrics for which the user has a negative trend recently. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to identify what type of data the user needs to provide a device to change the user interface and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is the first type when an activity value (e.g., average, slope of a linear fit) determined (e.g., calculated) for the activity data corresponding to the first activity metric for the first time period is equal to or greater than an activity value (e.g., the same activity value determined for the first time period) determined for the activity data corresponding to the first activity metric for the second time period. In some examples, the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is the second type when the activity value determined for the activity data corresponding to the first activity metric for the first time period is less than the activity value determined for the activity data corresponding to the first activity metric for the second time period. 
     In some examples, the representation of the first activity metric includes a visual indication (e.g., a graphical indication (up or down arrow); a textual indication)) (e.g.,  636   b ) of whether the relationship is the first type or the second type. 
     In some examples, displaying the first user interface includes, in accordance with a determination that the representation of the first activity metric is displayed in the first portion of the first user interface, animating the visual indication at a first time point (e.g., immediately on display, 0.5 seconds after display) after initially displaying the first user interface (e.g., automatically upon display of the first user interface). In some examples, displaying the first user interface includes, in accordance with a determination that the representation of the first activity metric is displayed in the second portion of the first user interface, animating the visual indication at a second time point (e.g., 1 second, a time point selected to be after the completion of the animation based on the first time point) after initially displaying the first user interface that is after the first time point. Animating visual indications (associated with activity metrics) such that visual indications associated with a first portion of a user interface are animated after visual indications associated with a second portion of the user interface (thereby highlighting such visual indications associated with the first behavior) provides a user with visual feedback about a current state of the activity metrics. For example, animating in such a way allows a user to quickly identify activity metrics for which the user has a negative trend recently. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient, by helping the user to identify what type of data the user needs to provide a device to change the user interface and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, displaying the first user interface includes, in accordance with a determination that the activity data corresponding to the first activity metric meets a first set of data insufficiency criteria (e.g., data is not available for the first time period and/or the second time period) that includes a criterion that is met when the first activity metric is a first metric type (e.g., a metric that is infrequently provided for a percentage of users; a metric that is not directly measured by one or more sensors of the electronic device) and a criterion that is met when the first the activity data corresponding to the first activity metric is below a data sufficiency threshold (e.g., data for the first and/or second time period does not exist or exists, but does not meet a threshold amount requirement), forgoing display of the representation of the first activity metric in the first user interface (e.g., in the first portion and the second portion) (e.g., irrespective of a relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type). 
     In some examples, displaying the first user interface includes, in accordance with a determination that the activity data corresponding to the first activity metric meets a second set of data insufficiency criteria (e.g., data is not available for the first time period and/or the second time period) that includes a criterion that is met when the first activity metric is a second metric type (e.g., a metric that is frequently provided for a percentage of users; a metric that is directly measured by one or more sensors of the electronic device) and a criterion that is met when the activity data corresponding to the first activity metric is below the data sufficiency threshold (e.g., data for the first and/or second time period does not exist or exists, but does not meet a threshold amount requirement), displaying the representation of the first activity metric in a third portion (e.g.,  618  or in a position in  612  as depicted in  FIG.  6 E  other than positive trend portion  632  and negative trend portion  638 )) of the user interface that is different from the first portion and the second portion with an indication (e.g., a graphical indication, a textual indication) that the activity data corresponding to the first activity metric is insufficient (e.g., irrespective of a relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type). Providing indications of whether a sufficient amount of data has been received for a particular activity metric provides a user with visual feedback about a current state of activity data stored on a device. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to identify what type of data the user needs to provide a device to change the user interface and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, displaying the representation of the first activity metric in a third portion of the user interface includes displaying an indication of a predicted length of time remaining for the first activity data corresponding to the first activity metric to meet the data sufficiency threshold (e.g.,  616 ) (in some examples, the predicted length of time is based on an assumption that a sufficient amount of activity data for the second activity metric will be received for the length of time). Indicating a predicted length of time needed to display a particular activity metric provides a user with visual feedback about a current state of activity data stored on a device and an indication regarding how the user needs to use the device in the future to be provided particular metrics. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to identify what type of data the user needs to provide a device to change the user interface and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, the first time period is a first predetermined period of time (e.g., the previous 90 days) prior to the current time (e.g., selected based on the current time (e.g., current day/date)). In some examples, the second time period is a second predetermined period of time (e.g., the previous 365 days) prior to the current time that is different from the first predetermined time period. 
     In some examples, displaying the representation of the first activity metric in a second portion (e.g.,  642 ) of the first user interface includes displaying a first coaching indication (e.g.,  642   e ) (e.g., “Let&#39;s get to walking 1 more mile per day”) including a prediction corresponding to when (e.g., a period of time (e.g., 1 day, 5 days, 2 weeks) the relationship will transition from being of the second type (e.g., negative) to being of the first type (e.g., even or positive trend) while maintaining a future level (e.g., a predicted future level) of activity (e.g., 10% more walking per day) for the first activity metric. In some examples, displaying the representation of the first activity metric in a first portion of the first user interface includes forgoing display of the first coaching indication (in some examples, the representation displayed in the first portion includes a second coaching indication (e.g., “keep it up!”), different than the first coaching indication). Selectively providing a prediction regarding a user&#39;s activity level assists the user in performing a technical task of providing additional activity data, thereby providing the user with visual feedback about a current state of activity data stored on a device. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to identify what type of data the user needs to provide a device to change the user interface and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, the electronic device includes a sensor device (e.g., an accelerometer, a GPS, a heart rate monitor). In such examples, the activity data corresponding to the first activity metric includes activity data received (e.g., detected) via the sensor device. 
     In some examples, the activity data corresponding to the first activity metric includes activity data received from a second electronic device (e.g., an external electronic device). 
     At  714 , the device receives activity data corresponding to a third activity metric (e.g., data corresponding to a measured level of activity for a user of the electronic device (e.g., data for activity performed by the user while wearing the electronic device)) for the first time period (e.g., 3 months). 
     At  716 , the device receives activity data corresponding to the third activity metric for the second time period (e.g., 1 year). 
     At  718 , displaying the first user interface includes, in accordance with a determination that a relationship (e.g., a mathematical relationship; a mathematical comparison) between the activity data corresponding to the third activity metric for the first time period and the activity data corresponding to the third activity metric for the second time period is the first type (e.g., no change or positive), displaying a representation (e.g., a graphical or textual indication of the first activity metric) of the third activity metric in the first portion of the first user interface. 
     At  720 , displaying the first user interface includes, in accordance with a determination that the relationship between the activity data corresponding to the third activity metric for the first time period and the activity data corresponding to the third activity metric for the second time period is the second type (e.g., negative), displaying a representation (e.g., up arrow or down arrow) of the third activity metric in the second portion of the first user interface. 
     In some examples, the representation of the first activity metric includes an indication in a first unit of measurement (e.g., calories, steps). In such examples, the representation of the third activity metric includes an indication in a second unit of measurement (e.g., minutes, miles) that is different than the first unit of measurement. 
     In some examples, the first time period (e.g., preceding 90 days) is a subset of the second time period (e.g., preceding 365 days). 
     In some examples, the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period includes a comparison of an average of the activity data corresponding to the first activity metric for the first time period with an average of the activity data corresponding to the first activity metric for the second time period. 
     In some examples, the activity data corresponding to the first activity metric for the first time period is selected from a group consisting of one or more of: a number of calories burned, an amount of time for which a user has been detected exercising, a number of hours for which a user has been detected to be standing for at least one minute, an amount of time for which a user has moved, an amount of time for which a user has stood, a walking speed, an identified fitness level for a given time for a user, a number of flights of stairs climbed, a distanced walked, and a determined workout intensity for a user. 
     In some examples, the device displays a user interface with all positive e.g.,  FIG.  6 G ) or all negative trends (e.g.,  FIG.  6 D ), where a user interface with all positive trends is different from a user interface with all negative trends and a user interface with a mix of positive and negative trends (e.g.,  FIG.  6 E ), and where a user interface with all negative trends is different from a user interface with a mix of positive and negative trends. In some examples, the order of trend representations is consistent between different views (e.g., all positive, all negative, or different combinations of mixes of positives and negatives). For example, in  FIG.  6 D , it can be seen that the order is move, exercise, stand, move minutes, and walk speed. Then, in  FIG.  5 E , while some of the representations for activity metrics have transitioned from negative to positive, the order within positive and the order within negative is maintained such that it keeps the order of move, exercise, stand, move minutes, and walk speed for each activity metric represented in each portion (e.g., in positive, the order is move, exercise, and move minutes, with stand missing because it is in the second portion). In some examples, the device displays a user interface with  10  different trends: move, exercise, stand, move minutes, stand minutes, walk speed, fitness levels, flights climbed, walking distance, and workout intensity. In some examples, negative trends include coaching information while positive trends do not include coaching information (e.g.,  636  and  642 ). 
     Note that details of the processes described above with respect to method  700  (e.g.,  FIGS.  7 A- 7 B ) are also applicable in an analogous manner to the methods described below. For example, methods  800  and  900  optionally includes one or more of the characteristics of the various methods described above with reference to method  700 . For example, selection of an activity representation in the first user interface described in method  700  can cause display of the first user interface described in method  800 . For another example, one or more coaching indications described in method  900  can be included in the first user interface described in method  700 . For brevity, these details are not repeated below. 
       FIGS.  8 A- 8 B  are a flow diagram illustrating method  800  for presenting activity trends (e.g., comparing an activity metric over two different lengths of time) using an electronic device in accordance with some embodiments. Method  800  relates to displaying a user interface (e.g., detailed page) with activity metric representations for a particular activity metric, comparing a first amount of time (e.g., 90 days) with a second amount of time (e.g., 365 days). Method  800  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 ,  664 ) with a display device. Some operations in method  800  are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  800  provides an intuitive way for presenting activity trends. The method reduces the cognitive burden on a user for presenting activity trends, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to identify activity trends faster and more efficiently conserves power and increases the time between battery charges. 
     At  802 , the device (e.g.,  600 ) receives activity data corresponding to a first activity metric (e.g., data corresponding to a measured level of activity for a user of the electronic device (e.g., data for activity performed by the user while wearing the electronic device)) for a first time period (e.g., 3 months). 
     At  804 , the device receives activity data corresponding to the first activity metric for a second time period (e.g., 1 year), wherein the first time period is a subset of the second time period (e.g., the second time period includes the first time period). In some examples, at least some of the activity data is detected by a sensor of the electronic device. For example; the device includes a sensor device (e.g., an accelerometer, a GPS, a heart rate monitor) and the activity data corresponding to the first activity metric includes activity data received (e.g., detected) via the sensor device. In some examples, the activity data is received from a second electronic device. For example, the activity data corresponding to the first activity metric includes activity data received from a second electronic device (e.g., an external electronic device). 
     At  806 , the device receives a request to display a first user interface (e.g., user interface with details for a specific activity metric) (e.g.,  649 ). 
     At  808 , the device, in response to receiving the request, displays, via the display device, the first user interface (e.g.,  652 ). 
     At  810 , the first user interface includes a representation (e.g., bars in  658  that are right of  658   c ) (e.g., a graphical or textual representation of a numerical value) (in some examples, the representation is a bar graph showing user activity data for the particular activity metric on each day within the first time period) of the activity data corresponding to the first activity metric for the first time period. 
     At  812 , the first user interface includes a representation (e.g., bars in  658  that are left of  658   c ) (e.g., a graphical or textual representation of a numerical value) (in some examples, the representation is a bar graph showing user activity data for the particular activity metric on each day within the second time period) of the activity data corresponding to the first activity metric for the second time period. 
     In some examples, the representation of the activity data corresponding to the first activity metric for the first time period is visually distinct (e.g., includes a visual characteristic (e.g., a color, a border, a shape) that is not present in the representation for the second time period or lacks a visual characteristic that is present in the representation for the second time period) from the representation of the activity data corresponding to the first activity metric for the second time period. 
     At  814 , the first user interface includes a representation (e.g.,  656   a ,  656   b ,  656   d ,  656   e ,  658   a ) (e.g., a graphical or textual representation of a numerical value) of a comparison (e.g., a mathematical comparison) of the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period. Displaying representations regarding different activity metrics with a comparison of activity data over different time periods provides a user with visual feedback about a current state of activity data stored on a device. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to identify what type of data the user needs to provide a device to change the user interface and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, at  816 , displaying the first user interface includes displaying an indication (e.g.,  658   a ) (e.g., a textual or graphical indication) for an average of the activity data corresponding to the first activity metric for the first time period. In such an example, at  818 , displaying the first user interface includes displaying an indication (e.g.,  658   b ) (e.g., a textual or graphical indication) for an average of the activity data corresponding to the first activity metric for the second time period. 
     In some examples, the representation of the activity data corresponding to the first activity metric for the first time period is divided into a first number of representations (e.g., a number of representations corresponding to a unit (e.g., days) of the time period). In such an example, the representation of the activity data corresponding to the first activity metric for the second time period is divided into a second number of representations different from the first number of representations. 
     In some examples, the representation of the comparison indicates a difference between the activity data (e.g., a difference between an activity value (e.g., average, slope of a linear fit) determined (e.g., calculated) for the first and second time periods for the activity data) corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period (in some examples, the representation of the comparison indicates a difference only when the activity data for the first time period is less than the activity data for the second time period). 
     In some examples, at  820 , displaying the first user interface includes displaying a plurality of first-time-period representations for the first time period (e.g., empty bars in  660 ) (e.g., bars in a graph for each day of the week corresponding to 90 day period), wherein: a first first-time-period representation (e.g., Monday bar for 90 day period) corresponds to a length of time (e.g., a day), a second first-time-period representation (e.g., Tuesday bar for 90 day period) corresponds to the length of time, the first first-time-period representation corresponds to a third time period (e.g., each Monday within the 90 day period) within the first time period, and the second first-time-period representation corresponds to a fourth time period (e.g., each Tuesday within the 90 day period) within the first time period. In such an example, at  822 , displaying the first user interface includes displaying a plurality of second-time-period representations for the second time period (e.g., bars with diagonal lines in  660 ) (e.g., bars in a graph for each day of the week corresponding to 365 day period), wherein: a first second-time-period representation (e.g., Monday bar for 365 day period) corresponds to the length of time, a second second-time-period representation (e.g., Tuesday bar for 365 day period) corresponds to the length of time, the first second-time-period representation corresponds to a fifth time period (e.g., each Monday within the 365 day period) within the second time period, the second second-time-period representation corresponds to a sixth time period (e.g., each Tuesday within the 365 day period) within the second time period, the third time period corresponds to the fifth time period (e.g., both are Mondays within their respective time periods), the fourth time period corresponds to the sixth time period (e.g., both are Tuesdays within their respective time periods), the first first-time-period representation is visually paired with (e.g., displayed adjacent to (e.g., without any other intervening representations)) the first second-time-period representation, and the second first-time-period representation is visually paired with the second second-time-period representation. Visually depicting a user&#39;s activity over time using a comparison of two different time periods provides a user with visual feedback about a current state of activity data stored on a device and information regarding how the user uses the device over time. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to identify what type of data the user needs to provide a device to change the user interface and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, at  824 , displaying the first user interface includes displaying a representation (e.g.,  662   a ) of a percentage of time periods of a particular length (e.g., a day) of the activity data corresponding to the first activity metric (e.g., calories burned) for the first time period for which (e.g., during which) the first activity metric met a threshold activity level (e.g., 500 calories/day) (in some examples, the user interface includes a percentage of days during a 90 day period in which the value of a activity metric (e.g., calories burned) met a threshold value (e.g., 85% of the days logged a calories burned metric of greater than 500 calories), Linking an activity metric with a particular threshold and tracking a user&#39;s past ability to meet the threshold provides a user with visual feedback about how the user uses the device. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to identify what type of data the user needs to provide a device to change the user interface and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, at  824 , displaying the first user interface includes displaying an icon (e.g.,  656   b ) indicating whether a relationship (e.g., a mathematical relationship; a mathematical comparison) between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type (e.g., the activity data (e.g., an average value of the activity data) for the first time period reflects no change or a positive change relative to the activity data (e.g., an average value of the activity data) for the second time period) or a second type (e.g., the activity, data for the first time period reflects a negative change relative to the activity data for the second time period). 
     Note that details of the processes described above with respect to method  800  (e.g.,  FIGS.  8 A- 8 B ) are also applicable in an analogous manner to the methods described below. For example, methods  700  and  900  optionally includes one or more of the characteristics of the various methods described above and below with reference to method  800 . For example, selection of a back affordance in the first user interface described in method  900  can cause display of the first user interface described in method  700 . For another example, one or more coaching indications described in method  900  can be included in the first user interface described in method  800 . For brevity, these details are not repeated below. 
       FIG.  9    is a flow diagram illustrating method  900  for presenting activity trends (e.g., providing different coaching depending on relationship between data of time periods; coaching includes a prediction of when relationship will change, if certain activity level is maintained) using an electronic device in accordance with some embodiments. Method  900  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 ,  664 ) with a display device. Some operations in method  900  are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  900  provides an intuitive way for presenting activity trends. The method reduces the cognitive burden on a user for presenting activity trends, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to identify activity trends faster and more efficiently conserves power and increases the time between battery charges. 
     At  902 , the device (e.g.,  600 ) receives activity data corresponding to a first activity metric (e.g., data corresponding to a measured level of activity for a user of the electronic device (e.g., data for activity performed by the user while wearing the electronic device)) for a first time period (e.g., 3 months). 
     At  904 , the device receives activity data corresponding to the first activity metric for a second time period (e.g., 1 year), different than the first period of time. 
     At  906 , the device receives a request (e.g.,  607 ,  611 ,  649 ) to display a first user interface (e.g.,  612 ,  652 ) (e.g., user interface that includes comparisons of activity data for a plurality of activity metrics or user interface with details for a specific activity metric). 
     At  908 , the device, in response to receiving the request, displays, via the display device, the first user interface, the first user interface including a representation (e.g.,  642 , or  656 ) (e.g., a graphical or textual indication of the first activity metric) of the first activity metric. 
     At  910 , the representation of the first activity metric includes, in accordance with a determination that a relationship (e.g., a mathematical relationship; a mathematical comparison) between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is a first type (e.g., negative trend for which can be remedied within 1 day), displaying a first coaching indication (e.g.,  628   e ) (e.g., “Don&#39;t forget to stand for one minute per hour throughout the day”) including a prediction (e.g., “the day” the  628 ) corresponding to when (e.g., a period of time (e.g., 1 day, 5 days, 2 weeks) the relationship will transition from being of the first type to being of a second type (e.g., even or positive trend), different from the first type, while maintaining a future level of activity (e.g., 10% more walking per day) for the first activity metric. 
     At  912 , the representation of the first activity metric includes, in accordance with a determination that the relationship is a third type (e.g., negative trend for which can be remedied more than a week but within 1 month) different from the first type, a second coaching indication (e.g.,  624   e ) (e.g., “Try to move around for 10 extra minutes”) that does not include a prediction corresponding to when (e.g., a period of time (e.g., 1 day, 5 days, 2 weeks) the relationship will transition from being of the third type to being of the second type. Dynamically modifying activity-related information provided to a user based on classifying the user&#39;s activity provides a user with visual feedback about a current state of activity data stored on a device. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to identify what type of data the user needs to provide a device to change the user interface and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, the first type requires that the relationship between the activity data (e.g., relationship between an activity value (e.g., average, slope of a linear fit) determined (e.g., calculated) for the activity data corresponding to the first activity metric for the first time period and the second time period)) corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is negative (e.g., the average value for the first time period is 50 calories burned/day and the average value for the second time period is 75 calories burned/day with a difference in the values being −25 calories burned/day)). 
     In some examples, the representation of the first activity metric includes: while the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is the first type (this in accordance means that the trend is negative): in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the second time period and the activity data corresponding to the first activity metric for a subset of the first time period (e.g., the last 7 days in a 90 day period) is a fourth type (e.g., recently positive), displaying a third coaching indication (e.g., “You have been improving lately, but let&#39;s get to walking 1 more mile per day to reach your yearly average”; a coaching indication in addition to the first coaching indication); and in accordance with a determination that a relationship between the activity data corresponding to the first activity metric for the second time period and the activity data corresponding to the first activity metric for the subset of the first time period (e.g., the last 7 days in a 90 day period) is a fifth type (e.g., recently negative), displaying a fourth coaching indication that is different from the third coaching indication (e.g., “let&#39;s get to walking 1 more mile per day to reach your yearly average”). Dynamically modifying activity-related information provided to a user based on a user&#39;s recent behavior as compared to less recent behavior provides a user with visual feedback about a recent state of activity data stored on a device. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to identify what type of data the user needs to provide a device to change the user interface and reducing user mistakes when operating/interacting; with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, the representation of the first activity metric includes: while the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is the first type: in accordance with a determination that the prediction exceeds a first time threshold (e.g., &gt;1 day) and is less than a second time threshold (e.g., &lt;7 days), displaying a fifth coaching indication (e.g., a coaching indication in addition to the first coaching indication); and in accordance with a determination that the prediction exceeds the second time threshold (e.g., &gt;7 days), displaying a sixth coaching indication (e.g., a coaching indication in addition to the first coaching indication) that is different from the fifth coaching indication. Dynamically modifying activity-related information provided to a user based on a link of time predicted for the activity data to be similar to the past provides a user with visual feedback about a current state of activity data stored on a device. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to identify what type of data the user needs to provide a device to change the user interface and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, at  914 , the device, while the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is the first type (this in accordance means that the trend is negative): in accordance with a determination that the prediction is a first classification (e.g., requiring a level of activity that exceeds threshold (e.g., an unreasonably high requirement)), displaying a fifth coaching indication (e.g., “Do better”) without a prediction corresponding to when the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period will be of the second type (e.g., even or positive trend) while maintaining the future level of activity (e.g., 10% more walking per day) for the first activity metric. 
     In some examples, the prediction is determined by: removing old data from the activity data corresponding to the first activity metric for the first time period, removing old data from the activity data corresponding to the first activity metric for the second time period, and until the relationship between the activity data corresponding to the first activity metric for the first time period and the activity data corresponding to the first activity metric for the second time period is the second type, adding predicted data to the activity data corresponding to the first activity metric for the first time period, and adding the old data from the activity data corresponding to the first activity metric for the first time period to the activity data corresponding to the first activity metric for the second time period (in some examples, trend reverses in 1 day, which only requires taking the last actual 89/364 days of data and adding one predicted day). 
     Note that details of the processes described above with respect to method  900  (e.g.,  FIG.  9   ) are also applicable in an analogous manner to the methods described below. For example, methods  700  and  800  optionally includes one or more of the characteristics of the various methods described above with reference to method  900 . 
       FIGS.  10 A- 10 N  illustrate exemplary user interfaces for managing workouts, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIGS.  11 A- 11 B . 
       FIG.  10 A  depicts electronic device  1000  displaying watch face user interface  1004  via display device  1002 . Electronic device  1000  includes various input mechanisms that receive user input, such as rotatable input mechanism  1001 , which is able to receive a rotatable input (and, in some examples, can also receive a push input). In some examples, electronic device  1000  includes one or more features of devices  100 ,  300 , or  500 . Watch face user interface  604  includes workout affordance  1006  for initiating a workout application (e.g., an application to track workouts performed by a user associated with electronic device  1000 ). 
     Referring to  FIG.  10 A , electronic device  1000  receives user input  1007  corresponding to selection of workout affordance  1006 . User input  1007  can include a touch gesture, such as a tap gesture on workout affordance  1006 , causing the workout application to be initiated (e.g., display of a user interface of the workout application, such as workout platter user interface  1008  as depicted in  FIG.  10 B ). 
       FIG.  10 B  depicts electronic device  1000  displaying workout platter user interface  1008  via display device  1002 . Workout platter user interface  1008  includes scrollable list of affordances  1010 , which are each associated with a respective physical activity tracking function for a physical activity. For example, scrollable list of affordances  1010  includes walk affordance  1012   a , which corresponds to a physical activity tracking function for an outdoor walk. 
     It is noted that scrollable list of affordances  1010  includes additional affordances corresponding to other physical activity tracking functions that are not currently displayed but can be displayed in response to a scrolling input (e.g., rotation of rotational mechanism  1001 ). In some embodiments, scrollable list of affordances  1010  includes more workouts affordance, which will be described in further detail below (see at least  FIG.  10 F ). 
     Referring to  FIG.  10 B , electronic device  1000  receives user input  1013  corresponding to selection of walk affordance  1012   a . User input  1013  can include a touch gesture, such as a tap gesture on walk affordance  1012   a , causing a physical activity tracking function associated with walk affordance  1012   a  to be launched (e.g., display of one or more user interfaces of the workout application, with a final user interface corresponding to the physical activity tracking function associated with walk affordance  1012   a  (e.g., walk user interface  1014  as depicted in  FIG.  10 C ). 
       FIG.  10 C  depicts electronic device  1000  displaying walk user interface  1014  via display device  1002 . Walk user interface  1014  displays a set of tracked metrics (e.g., “00:01.40,” “0 active cal,” “70 BPM,” “15′11″ average mile,” and “0 ft”) (which are tracked by the physical activity tracking function associated with walk affordance  1012   a.    
     In some examples, tracking of the set of tracked metrics is performed by one or more tracking sensors of electronic device  1000 . For example, electronic device  1000  tracks physical activity via tracking sensors (or workout sensors) that communicate with workout support module  142  (as depicted in  FIG.  3   ). 
     Referring to  FIG.  10 C , electronic device  1000  receives user input  1015  corresponding to a swipe gesture. User input  1015  can include a touch gesture, causing a control user interface of the workout application to be displayed (e.g., control user interface  1016  as depicted in  FIG.  10 D ). 
       FIG.  10 D  depicts electronic device  1000  displaying control user interface  1016  via display device  1002 . In some examples, device  1000  displays control user interface  1016  in response to a user input (e.g., user input  1015 ) while displaying walk user interface  1014 . Control user interface  1016  includes affordances to control various functionalities of the workout application. For example, control user interface  1016  includes end workout affordance  1018  (configured to, when selected, end a currently running workout). 
     Referring to  FIG.  10 D , electronic device  1000  receives user input  1019  corresponding to selection of end workout affordance  1018 , User input  1019  can include a touch gesture, such as a tap gesture on end workout affordance  1018 , causing the currently running workout (associated with outdoor walk) to end and workout platter user interface  1008  to be displayed, as depicted in  FIG.  10 E . 
       FIG.  10 E  depicts electronic device  1000  displaying, once again, workout platter user interface  1008  via display device  1002  and performing a scrolling operation. For example, rotational input  1021  is received at rotatable input mechanism  1001 . In response to rotational input  1021 , as depicted in  FIG.  10 F , scrollable list of affordances  1010  is scrolled in an upward direction such that more workouts affordance  1022  are displayed. 
     Referring to  FIG.  10 F , electronic device  1000  receives user input  1023  corresponding to selection of more workouts affordance  1022 . User input  1023  can include a touch gesture, such as a tap gesture on more workouts affordance  1022 , causing a user interface with a list of available workouts to be displayed (e.g., workout list user interface  1024  as depicted in  10 G). 
       FIG.  10 G  depicts electronic device  1000  displaying workout list user interface  1024  via display device  1002 . In some examples, workout list user interface  1024  includes a scrollable list of affordances with popular portion  1026  (as depicted in  FIG.  10 G ) and alphabetical portion  1027  (as depicted in  FIG.  10 H ). 
     Referring to  FIG.  10 G , popular portion  1026  includes multiple workout affordances, each workout affordance determined to be most relevant (e.g., popular among users, most frequently used by a user associated with electronic device  1000 , etc.). For example, the multiple workout affordances in popular portion  1026  includes dance affordance  1028 . Selection of a particular workout affordance of the multiple workout affordances causes (1) a workout affordance corresponding to the particular workout affordance to be added to workout platter user interface  1008  such that the workout affordance can be selected in the future when a user navigates to workout platter user interface  1008  and/or (2) a physical activity tracking function corresponding to the workout affordance to be launched. 
     Referring to  FIG.  10 H , alphabetical portion  1027  includes a list of workout affordances in alphabetical order, including AUS football affordance  1030  (e.g., an affordance corresponding to function for tracking activity associated with Australian rules football). It should be recognized that the list of workout affordances can be ordered in a different manner. Similar to popular portion  1026 , selection of a particular workout affordance in the list of workout affordances causes (1) a workout affordance corresponding to the particular workout affordance to be added to workout platter user interface  1008  such that the workout affordance can be selected in the future when a user navigates to workout platter user interface  1008  and/or (2) a physical activity tracking function corresponding to the workout affordance to be launched. 
     Similar to as described above for  FIG.  11 . 0 E ,  FIG.  10 F  depicts electronic device  1000  receiving rotational input  1029  at rotatable input mechanism  1001 . In response to rotational input  1029 , the scrollable list of affordances of workout list user interface  1024  is scrolled in an upward direction such that more workout affordances are displayed (e.g., other workout affordances in popular portion  1026  (not depicted) or workout affordances in alphabetical portion  1021  (as depicted in  FIG.  10 H )). 
       FIG.  10 H  depicts electronic device  1000  receiving user input  1031  corresponding to selection of AUS football affordance  1030 . User input  1031  can include a touch gesture, such as a tap gesture on AUS football affordance  1030 , causing a workout affordance corresponding to AUS football affordance  1030  to be added to workout platter user interface  1008  (e.g., AUS football affordance  1034  as depicted in  FIG.  10 I ). 
     Similar as described above for  FIGS.  10 B- 10 D ,  FIGS.  10 I- 10 K  depict user interfaces involved in beginning and ending a workout. For example,  FIG.  10 I  depicts electronic device  1000  displaying workout platter user interface  1008  via display device  1002 . Workout platter user interface  1008  depicted in  FIG.  10 I  includes AUS football affordance  1034 , showing that workout platter user interface  1008  depicted in  FIG.  10 I  is in a state after AUS football affordance  1034  has been added to workout platter user interface  1008  (e.g., after  FIG.  10 H ) (see  FIG.  10 F , which does not include AUS football affordance  1034 ). AUS football affordance  1034  corresponds to a physical activity tracking function for Australian football. 
     Referring to  FIG.  10 I , electronic device  1000  receives user input  1035  corresponding to selection of AUS football affordance  1034 . User input  1035  can include a touch gesture, such as a tap gesture on AUS football affordance  1034 , causing a physical activity tracking function associated with AUS football affordance  1034  to be launched (e.g., display of one or more user interfaces of the workout application, with a final user interface corresponding to the physical activity tracking function associated with AUS football affordance  1034  (e.g., AUS football user interface  1036  as depicted in  FIG.  10 J ). 
       FIG.  10 J  depicts electronic device  1000  displaying AUS football interface  1036  via display device  1002 . AUS football interface  1036  displays a set of tracked metrics (e.g., “00:01.29,” “0 active cal,” “0 total cal,” and “—BPM”) (which are tracked by the physical activity tracking function associated with AUS football affordance  1034 ). 
     In some examples, tracking of the set of tracked metrics is performed by one or more tracking sensors of electronic device  1000 . For example, electronic device  1000  tracks physical activity via tracking sensors (or workout sensors) that communicate with workout support module  142  (as depicted in  FIG.  3   ). 
     Referring to  FIG.  10 J , electronic device  1000  receives user input  1037  corresponding to a swipe gesture. User input  1037  can include a touch gesture, causing a control user interface of the workout application to be displayed (e.g., control user interface  1038  as depicted in  FIG.  10 K ). 
       FIG.  10 K  depicts electronic device  1000  displaying control user interface  1038  via display device  1002 . Control user interface  1038  includes affordances to control various functionalities of the workout application. For example, control user interface  1038  includes end workout affordance  1040  (configured to, when selected, end a currently running workout). 
     Referring to  FIG.  10 K , electronic device  1000  receives user input  1041  corresponding to selection of end workout affordance  1040 . User input  1041  can include a touch gesture, such as a tap gesture on end workout affordance  1040 , causing the currently running workout (associated with Australian football) to end and workout platter user interface  1008  to be displayed, as depicted in  FIG.  10 L . 
       FIG.  10 L  depicts electronic device  1000  displaying workout platter user interface  1008  via display device  1002 . Workout platter user interface  1008  depicted in  FIG.  10 L  includes AUS football affordance  1034 , showing that workout platter user interface  1008  depicted in  FIG.  10 L  is in a state after AUS football affordance  1034  has been added to workout platter user interface  1008  (e.g., after  FIG.  10 H ) (see  FIG.  10 F , which does not include AUS football affordance  1034 ). 
     Referring to  FIG.  10 L , electronic device  1000  receives user input  1043  corresponding to a swipe gesture associated with (e.g., at least partially on top of) AUS football affordance  1034 . User input  1043  can include a touch gesture, causing (1) AUS football affordance  1034  to move to the left and (2) delete affordance  1044  to be displayed in a position that was at least partially previously occupied by AUS football affordance  1034  prior to moving (as depicted in  FIG.  10 M ), 
       FIG.  10 M  depicts electronic device  1000  displaying workout platter user interface  1008  via display device  1002  with AUS football affordance  1034  moved to the left and delete affordance  1044  displayed in a location that was at least partially covered up by AUS football affordance  1034  prior to being moved to the left. Referring to  FIG.  10 L , electronic device  1000  receives user input  1045  corresponding to selection of delete affordance  1040 , User input  1041  can include a touch gesture, such as a tap gesture on end workout affordance  1044 , causing AUS football affordance  1034  to be removed from workout platter user interface  1008  (as depicted in  FIG.  10 N ) until AUS football affordance  1034  is added again using the process described in  FIGS.  10 F- 10 H .  FIG.  10 N  depicts electronic device  1000  displaying workout platter user interface  1008  via display device  1002  without AUS football affordance  1034 . 
       FIGS.  11 A- 11 B  are a flow diagram illustrating method  1100  for managing workouts (e.g., more-workouts option for workout platters, allowing user to view a list of workouts to add to workout platters) using an electronic device in accordance with some embodiments. Method  1100  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 ,  664 ,  1000 ) with a display device. Some operations in method  1100  are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  1100  provides an intuitive way for managing workouts. The method reduces the cognitive burden on a user for managing workouts, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to add and delete workout affordances associated with physical activity tracking functions faster and more efficiently conserves power and increases the time between battery charges. 
     At  1102 , the device (e.g.,  1000 ) displays, via the display device, a first instance of a first user interface (e.g.,  1008  as depicted in  FIGS.  10 B,  10 E, and  10 F ) including a first set of affordances (e.g.,  1012   a ,  1012   b ) (e.g., workout platters) associated with physical activity tracking functions (in some examples, different affordances in a plurality of the scrollable list of affordances correspond to different physical activities), wherein the first set of affordances includes a first affordance (e.g.,  1012   a ) associated with a first physical activity tracking function. 
     At  1104 , while displaying the first instance of the first user interface, the device receives a user input (e.g.,  1013 ) (e.g., a tap in the user interface). 
     At  1106 , in response to receiving the user input, in accordance with a determination that the user input is detected at the first affordance (e.g., run option) in the first set of affordances, the device launches (e.g., activating, starting) the first physical activity tracking function (e.g.,  1014 ) (e.g., running). 
     At  1108 , in further response to receiving the user input, in accordance with a determination that the user input is detected at a second affordance (e.g.,  1022 ) (e.g., more-workouts option) in the first set of affordances, the device displays a second user interface (e.g.,  1024 ) (e.g., more-workouts interface) that includes a third affordance (e.g.,  1030 ) associated with a second physical activity tracking function (e.g., walking option). 
     At  1110 , the device receives a set of one or more inputs (e.g.,  1031 ), the set of one or more inputs including an input corresponding to selection of the third affordance. 
     At  1112 , in response to receiving the set of one or more inputs, the device displays a second instance (e.g.,  1008  as depicted in  FIG.  10 I ) of first user interface, wherein: the second instance of the first user interface includes the first affordance and a fourth affordance (e.g.,  1034  associated with the second physical activity tracking function (e.g., an affordance that, when selected, launches the second physical activity tracking function), and the first instance of the first user interface does not include an affordance (e.g., any affordance) associated with the second physical activity tracking function. Updating a list of physical activity tracking functions shown to a user on an initial user interface provides the user with more control of the device by helping the user avoid unintentionally executing physical activity tracking functions and simultaneously reducing the number of steps that a user must take to reach desired physical activity tracking functions. Providing additional control of the device without cluttering the UI with additional displayed controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, the first set of affordances includes a fifth affordance  1012   b ) associated with a third physical activity tracking function (e.g., golfing option) different from the first physical activity tracking function and the second physical activity tracking function. 
     In some examples, the input corresponding to selection of the third affordance causes the second instance of the first user interface to be displayed (in some examples, the input corresponding to selection of the third affordance is the terminal input (e.g., the only input) in the set of one or more inputs). 
     In some examples, the second instance of the first user interface includes the second affordance. 
     In some examples, at  1114 , the device receives an input (e.g.,  1031 ) corresponding to selection of the second affordance within the second instance of the first user interface. 
     In some examples, at  1116 , in response to receiving the input corresponding to selection of the second affordance within the second instance of the first user interface, the device displays a second instance of the second user interface (e.g.,  1024 ) (e.g., more-workouts interface) that does not include an affordance associated with the second physical activity tracking function. 
     In some examples, at  1118 , while displaying the second instance of the first user interface, the device receives a second set of one or more inputs, the second set of one or more inputs including an input (e.g.,  1043 ) corresponding to the fourth affordance associated with the second physical activity tracking function (e.g., an affordance corresponding to an activity tracking function that was previously added to the user interface) (e.g., a set of inputs corresponding to a request to remove the fourth affordance from the first user interface). 
     In some examples, in response to receiving the second set of one or more inputs, the device displays a third instance of the first user interface (e.g.,  1008  as depicted in  FIG.  10 N ) wherein the third instance of the first user interface does not include an affordance associated with the second physical activity tracking function. Allowing a user to quickly and efficiently remove physical activity tracking functions from a list of physical activity tracking functions provides the user with more control of the device by helping the user avoid unintentionally executing physical activity tracking functions and simultaneously reducing the number of steps that a user must take to reach desired physical activity tracking functions. Providing additional control of the device without cluttering the UI with additional displayed controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, receiving the second set of one or more inputs includes: receiving a swipe gesture e.g.,  1043 ) corresponding to the fourth affordance and a tap gesture (e.g.,  1045 ) corresponding to a delete affordance (e.g.,  1044 ) associated with the fourth affordance a delete affordance that is displayed in response to receiving the swipe gesture). 
     Note that details of the processes described above with respect to method  1100  (e.g.,  FIGS.  7 A- 7 B ) are also applicable in an analogous manner to the methods described above. For example, methods  700 ,  800 , and  900  optionally includes one or more of the characteristics of the various methods described above with reference to method  1100 . For example, deletion of a representation as described in methods  700 ,  800 , and  900  can be performed as described in method  1100 . 
       FIGS.  12 A- 12 F  illustrate exemplary user interfaces for displaying awards, in accordance with some embodiments.  FIG.  12 A  depicts electronic device  1000  displaying activity application user interface  1204  via display device  1002 . Activity application user interface  1204  includes activity affordance  1206 , friends affordance  1208 , and awards affordance  1210 . 
     Each of these affordances are configured, when selected, to cause electronic device  1000  to display a user interface corresponding to the respective affordance. For example, activity affordance  1206  corresponds to a user interface for displaying information related to activity of a user associated with electronic device  1000  (as depicted in  FIG.  12 B ). Friends affordance  1208  corresponds to a user interface for managing friends (e.g., users for which are sending data to and/or receiving data from the user associated with electronic device (e.g., sharing)) of the user associated with electronic device  1000  (as depicted in  FIG.  12 C ). Awards affordance  1210  corresponds to a user interface for displaying awards of the user associated with electronic device  1000  (as depicted in  FIG.  12 D ). 
     Referring to  FIG.  12 A , electronic device  1000  receives user input  1207  corresponding to selection of activity affordance  1206 . User input  1207  can include a touch gesture, such as a tap gesture on activity affordance  1206 , causing a user interface associated with activity affordance  1206  to be displayed (e.g., activity user interface  1212 ). 
       FIG.  12 B  depicts electronic device  1000  displaying activity user interface  1212  via display device  1002 . Activity user interface  1212  includes information related to activity of a user associated with electronic device  1000  (e.g., three rings, which each ring representing an amount of a different activity metric that the user has completed during a current day). 
     Referring to  FIG.  12 B , electronic device  1000  receives user input  1213  corresponding to a swipe gesture. User input  1213  can include a touch gesture, causing a user interface for managing friends to be displayed (e.g., friends user interface  1216  as depicted in  FIG.  12 C ). 
       FIG.  12 C  depicts electronic device  1000  displaying friends user interface  1216  via display device  1002 . Friends user interface  1212  includes multiple affordances, each affordance corresponding to a user for which the user associated with electronic device  1000  is sharing with. 
     Referring to  FIG.  12 C , electronic device  1000  receives user input  1217  corresponding to a swipe gesture. User input  1217  can include a touch gesture, causing a user interface for displaying awards to be displayed (e.g., awards user interface  1218  as depicted in  FIG.  12 D ). In some examples, the swipe gesture depicted in  FIG.  12 C  is determined to be the same direction as the swipe gesture depicted in  FIG.  12 B . In such examples, if a swipe gesture on friends user interface  1216  is determined to be the opposite direction as the swipe gesture depicted in  FIG.  12 B , the swipe gesture causes activity user interface  1212  to be displayed. 
       FIG.  12 D  depicts electronic device  1000  displaying awards user interface  1218  via display device  1002 . Awards user interface  1212  includes multiple sections (e.g.,  1220   a - 1220   d ), each section including one or more representations of awards corresponding to the respective section. For example, recent section  1220   a  includes one or more representations of awards that were recently received by the user of electronic device  1000  (e.g., representation  1222   a ). For another example, March challenge section  1220   b  includes one or more representations of awards that are associated with a March challenge (e.g., representation  1222   b ). 
     A representation of an award can include one or more visual attributes indicating that the award have been awarded to the user of electronic device  1000 . For example, representation  1222   a  can be a first set of one or more colors while representation  1222   b  can be a second set of one or more colors, the first set of one or more colors indicating that an award corresponding to representation  1222   a  has been awarded to the user and the second set of one or more colors indicating that an award corresponding to representation  1222   b  has not been awarded to the user. 
     Referring to  FIG.  12 D , electronic device  1000  receives user input  1223  corresponding to selection of representation  1222   b . User input  1223  can include a touch gesture, such as a tap gesture on representation  1222   b , causing a user interface associated with representation  1222   b  to be displayed (e.g.,  1224  or  1228 ). 
       FIG.  12 E  depicts electronic device  1000  displaying non-awarded detailed user interface  1224  via display device  1002 . Non-awarded detailed user interface  1224  corresponds to representation  1222   b  based on user input  1223  corresponding to selection of representation  1222   b . Non-awarded detailed user interface  1224  includes a representation of representation  1222   b  (e.g., representation  1226 ). In some examples, representation  1226  is larger than representation  1222   b  (not illustrated). Non-awarded detailed user interface  1224  includes text indicating how the user can earn an award corresponding to representation  1226  (“Earn this award by exercising 1000 minutes this month”). 
       FIG.  12 F  depicts electronic device  1000  displaying awarded detailed user interface  1228  via display device  1002 . Once an award has been given to the user, a representation corresponding to the award can change. For example,  FIG.  12 F  depicts representation  1230 , which corresponds to representation  1226  except that the appearance of representation  1230  is different from representation  1226 . In some examples, the different appearance corresponds to representation  1226  being a first set of one or more colors and representation  1230  being a second set of one or more colors different from the first set of one or more colors, the difference indicating that an award corresponding to representation  1230  has been awarded and an award corresponding to representation  1226  has not been awarded. 
     The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Man modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated. 
     Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims. 
     As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve tracking of activity and viewing of details related to the activity. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records relating to a user&#39;s health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information. 
     The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to track activity and view details related to the activity. Accordingly, use of such personal information data enables improved tracking of activity and improved viewing of details related to the activity. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user&#39;s general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals. 
     The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply, with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country. 
     Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of activity services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In another example, users can select not to provide activity data for targeted activity services. In yet another example, users can select to limit the length of time activity data is maintained or entirely prohibit the development of trend data. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app. 
     Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user&#39;s privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods. 
     Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, activity can be tracked and details related to the activity viewed by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the activity services, or publicly available information.

Metadata:
Filing Date: 20220628
Publication Date: 20231017
Grant Date: 20231017
Priority Date: 20190506
Inventors: GILRAVI, Eamon F.
ARNEY, Julie A.
Assignee: APPLE INC
CPC Classifications: [{"code": "G16H20/30", "inventive": true, "first": true, "tree": "[]"}, {"code": "A61B5/1118", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/1123", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/4866", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/743", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/7435", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/7475", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B24/0062", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B71/0622", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B24/00", "inventive": true, "first": true, "tree": "[]"}, {"code": "G16H20/30", "inventive": true, "first": true, "tree": "[]"}, {"code": "G16H20/30", "inventive": true, "first": true, "tree": "[]"}, {"code": "A61B5/103", "inventive": true, "first": false, "tree": "[]"}, {"code": "G16H40/63", "inventive": true, "first": false, "tree": "[]"}, {"code": "G16H50/30", "inventive": true, "first": false, "tree": "[]"}, {"code": "G16H15/00", "inventive": true, "first": false, "tree": "[]"}, {"code": "G16H50/70", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/1118", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/1122", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/681", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/7275", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/744", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/4866", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/486", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B2562/0219", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B2503/10", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B2505/09", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B5/1123", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/1118", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B24/0062", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/7435", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B71/0622", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/4866", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/1123", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/743", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/7475", "inventive": true, "first": false, "tree": "[]"}]
Family ID: 72425579