PATENT DOCUMENT

Publication Number: US-11660503-B2
Application Number: US-202117516537-A
Country: US
Kind Code: B2

Title: Activity and workout updates

Abstract:
The present disclosure generally relates to navigating, viewing, and sharing activity and workout data and interacting with workout and/or activity applications. In some examples, scrolling of activity data is based on the content being displayed. In some examples, friends&#39; activity data may be viewed. In some examples, a notification and workout data for a friend&#39;s completed workout is received and displayed. In some example, the activity data received from friends is viewed and managed. In some examples, workout data for a multi-segment workout is displayed in a three-dimensional stack on a map. In some examples, a workout application operates in a limited mode until a touch input is received with a characteristic intensity that is greater than a threshold intensity.

Claims:
What is claimed is: 
     
       1. A portable electronic device comprising:
 one or more processors; 
 a display; 
 a touch sensitive screen; and 
 memory storing one or more programs for execution by the one or more processors, the one or more programs including instructions for:
 receiving first workout data for a first segment of a multi-segment workout route, wherein the first workout data includes a first plurality of geographic locations for the multi-segment workout route and a first plurality of workout metrics associated with the first plurality of geographic locations; 
 receiving second workout data for a second segment of the multi-segment workout route, wherein the second workout data includes a second plurality of geographic locations for the multi-segment workout route and a second plurality of workout metrics associated with the second plurality of geographic locations; and 
 displaying a three-dimensional stack, wherein the three-dimensional stack comprises a first graphical representation of the first workout data and a second graphical representation of the second workout data over a map, 
 wherein the first graphical representation at least partially superimposes the second graphical representation, 
 wherein the appearance of the first graphical representation is based on the first plurality of workout metrics of the first workout data and the second graphical representation is based on the second plurality of workout metrics of the second workout data, and 
 wherein displaying the three-dimensional stack includes superimposing a first representation of a first route over the map based on the first plurality of geographic locations and superimposing a second representation of a second route over the map based on the second plurality of geographic locations. 
 
 
     
     
       2. The electronic device of  claim 1 , the one or more programs further including instructions for:
 displaying a two-dimensional graph of the first workout data and the second workout data with the display of the first graphical representation and the second graphical representation. 
 
     
     
       3. The electronic device of  claim 2 , the one or more programs further including instructions for:
 displaying a first indicator on the two-dimensional graph for a portion of the first workout data or a portion of the second workout data; and 
 displaying a second indicator on the display of the first workout data or the second workout data, wherein the first indicator and second indicator correspond to the same portion of the first workout data or the second workout data. 
 
     
     
       4. The electronic device of  claim 2 , wherein the two-dimensional graph includes an indication of an elevation for the first workout data and the second workout data. 
     
     
       5. The electronic device of  claim 2 , wherein the first graphical representation has a position-dependent color based on a position-dependent workout metric from the first workout data and the second graphical representation has a position-dependent color based on the position-dependent workout metric from the second workout data. 
     
     
       6. The electronic device of  claim 5 , wherein the position-dependent workout metric is a workout pace or a swim stroke. 
     
     
       7. The electronic device of  claim 1 , the one or more programs further including instructions for:
 displaying concurrently with the first graphical representation and the second graphical representation on the map an affordance for sharing an image of the display of the first graphical representation and the second graphical representation on the map. 
 
     
     
       8. 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, the one or more programs including instructions for:
 receiving first workout data for a first segment of a multi-segment workout route, wherein the first workout data includes a first plurality of geographic locations for the multi-segment workout route and a first plurality of workout metrics associated with the first plurality of geographic locations; 
 receiving second workout data for a second segment of the multi-segment workout route, wherein the second workout data includes a second plurality of geographic locations for the multi-segment workout route and a second plurality of workout metrics associated with the second plurality of geographic locations; and 
 displaying a three-dimensional stack, wherein the three-dimensional stack comprises a first graphical representation of the first workout data and a second graphical representation of the second workout data over a map, 
 wherein the first graphical representation at least partially superimposes the second graphical representation, 
 wherein the appearance of the first graphical representation is based on the first plurality of workout metrics of the first workout data and the second graphical representation is based on the on the second plurality of workout metrics of the second workout data, and 
 wherein displaying the three-dimensional stack includes superimposing a first representation of a first route over the map based on the first plurality of geographic locations and superimposing a second representation of a second route over the map based on the second plurality of geographic locations. 
 
     
     
       9. The non-transitory computer-readable storage medium of  claim 8 , the one or more programs further including instructions for:
 displaying a two-dimensional graph of the first workout data and the second workout data with the display of the first graphical representation and the second graphical representation. 
 
     
     
       10. The non-transitory computer-readable storage medium of  claim 9 , the one or more programs further including instructions for:
 displaying a first indicator on the two-dimensional graph for a portion of the first workout data or a portion of the second workout data; and 
 displaying a second indicator on the display of the first workout data or the second workout data, wherein the first indicator and second indicator correspond to the same portion of the first workout data or the second workout data. 
 
     
     
       11. The non-transitory computer-readable storage medium of  claim 9 , wherein the two-dimensional graph includes an indication of an elevation for the first workout data and the second workout data. 
     
     
       12. The non-transitory computer-readable storage medium of  claim 9 , wherein the first graphical representation has a position-dependent color based on a position-dependent workout metric from the first workout data and the second graphical representation has a position-dependent color based on the position-dependent workout metric from the second workout data. 
     
     
       13. The non-transitory computer-readable storage medium of  claim 12 , wherein the position-dependent workout metric is a workout pace or a swim stroke. 
     
     
       14. The non-transitory computer-readable storage medium of  claim 8 , the one or more programs further including instructions for:
 displaying concurrently with the first graphical representation and the second graphical representation on the map an affordance for sharing an image of the display of the first graphical representation and the second graphical representation on the map. 
 
     
     
       15. A method comprising:
 on an electronic device with a display:
 receiving first workout data for a first segment of a multi-segment workout route, wherein the first workout data includes a first plurality of geographic locations for the multi-segment workout route and a first plurality of workout metrics associated with the first plurality of geographic locations; 
 receiving second workout data for a second segment of the multi-segment workout route, wherein the second workout data includes a second plurality of geographic locations for the multi-segment workout route and a second plurality of workout metrics associated with the second plurality of geographic locations; and 
 displaying a three-dimensional stack, wherein the three-dimensional stack comprises a first graphical representation of the first workout data and a second graphical representation of the second workout data over a map, 
 wherein the first graphical representation at least partially superimposes the second graphical representation, 
 wherein the appearance of the first graphical representation is based on the first plurality of workout metrics of the first workout data and the second graphical representation is based on the second plurality of workout metrics of the second workout data, and 
 wherein displaying the three-dimensional stack includes superimposing a first representation of a first route over the map based on the first plurality of geographic locations and superimposing a second representation of a second route over the map based on the second plurality of geographic locations. 
 
 
     
     
       16. The method of  claim 15 , further comprising:
 displaying a two-dimensional graph of the first workout data and the second workout data with the display of the first graphical representation and the second graphical representation. 
 
     
     
       17. The method of  claim 16 , further comprising:
 displaying a first indicator on the two-dimensional graph for a portion of the first workout data or a portion of the second workout data; and 
 displaying a second indicator on the display of the first workout data or the second workout data, wherein the first indicator and second indicator correspond to the same portion of the first workout data or the second workout data. 
 
     
     
       18. The method of  claim 16 , wherein the two-dimensional graph includes an indication of an elevation for the first workout data and the second workout data. 
     
     
       19. The method of  claim 16 , wherein the first graphical representation has a position-dependent color based on a position-dependent workout metric from the first workout data and the second graphical representation has a position-dependent color based on the position-dependent workout metric from the second workout data. 
     
     
       20. The method of  claim 19 , wherein the position-dependent workout metric is a workout pace or a swim stroke. 
     
     
       21. The method of  claim 15 , further comprising:
 displaying concurrently with the first graphical representation and the second graphical representation on the map an affordance for sharing an image of the display of the first graphical representation and the second graphical representation on the map.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of U.S. patent application Ser. No. 16/378,136, entitled “ACTIVITY AND WORKOUT UPDATES”, filed on Apr. 8, 2019, which is a continuation of U.S. patent application Ser. No. 15/616,480, entitled “ACTIVITY AND WORKOUT UPDATES”, filed on Jun. 7, 2017, which claims priority to U.S. provisional patent application 62/348,908, entitled “ACTIVITY AND WORKOUT UPDATES”, filed on Jun. 11, 2016, the contents 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 interacting with workout or activity applications. 
     BACKGROUND 
     Approximately 133 million Americans currently suffer from at least one chronic health condition. This number is expected to rise to approximately 165 million by the year 2020. This deterioration in health can be attributed largely to a sedentary lifestyle with little to no physical activity. For example, lack of sufficient physical activity can increase the risk of developing diabetes, hypertension, colon cancer, depression and anxiety, obesity, and weak muscles and bones. In addition, recent studies have found that extended periods of inactivity (e.g., sitting at a desk), can lead to serious health risks, such as an increased risk of a heart attack. 
     BRIEF SUMMARY 
     Some techniques for viewing and sharing activity data 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 viewing and sharing activity data. Such methods and interfaces optionally complement or replace other methods for viewing and sharing activity data. 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 an embodiment, at a portable electronic device having a display, a graphical representation of activity data is generated for output on the display. The graphical representation includes a goal portion and a workout portion. The goal portion and the workout portion each extend beyond a displayable area of the display. The goal portion includes a first goal graphical element for a first goal metric. The workout portion includes a first workout graphical element for a first workout metric. A first portion of the graphical representation is displayed on the display. The displayed first portion includes a first graphical element. In response to receiving a first scroll input and while the displayed first portion is of the goal portion, the display of the first graphical element is replaced with a display of the first goal graphical element. In response to receiving a first scroll input and while the displayed first portion is not of the goal portion, the first graphical element is translated by an amount based on a magnitude of the first scroll input and displaying at least portion of the first workout graphical element. 
     In an embodiment, at a portable electronic device having a display, contact information for a plurality of contacts, including a first contact, is displayed. Activity summary data for the first contact is received from one or more external electronic devices. The activity summary data for the first contact includes a first goal metric. First user input selecting the first contact is received. In response to receiving the first user input selecting the first contact, a portion of a graphical representation of the activity summary is displayed on the display. The graphical representation includes a first goal graphical element for the first goal metric. 
     In an embodiment, at a portable electronic device having a display, a notification and workout summary data are receiving from an external electronic device. The workout summary data is for a completed workout of a remote user associated with the external electronic device. A first graphical element representing the notification is displayed on the display. A first user input is received selecting the first graphical element while displaying the first graphical element. In response to the first user input, a portion of a graphical representation of the workout summary data is displayed 
     In an embodiment, at a portable electronic device having a display and a touch-sensitive scree, contact information is displayed, including first contact information for a first plurality of contacts, including a first contact. The first contact information corresponds to the first contact. First user input is received indicating a selection of the first contact. In response to receiving the first user input, a determination is made whether the portable electronic device has access to activity data associated with the first contact. In accordance with a determination that the portable electronic device has access to activity data associated with the first contact, a portion of a graphical representation of the activity data is displayed. In accordance with a determination that the electronic device does not have access to activity data associated with the first contact, a graphical element is displayed indicating that activity data is not available for the first contact. 
     In an embodiment, at a portable electronic device having a display, first workout data for a first segment of a multi-segment workout route is received. The first workout data includes a plurality of locations for the multi-segment workout route and a plurality of workout metrics associated with the plurality of locations. Second workout data for a second segment of the multi-segment workout route is received. The second workout data includes a plurality of locations for the multi-segment workout route and a plurality of workout metrics associated with the plurality of locations. A first graphical representation of the first workout data and a second graphical representation of the second workout data are displayed over a map. The first and second graphical representations are displayed in a three-dimensional stack. The appearance of the first graphical representation is based on the plurality of workout metrics of the first workout data and the second graphical representation is based on the plurality of workout metrics of the second workout data. 
     In an embodiment, on a portable electronic device with a display and a pressure sensitive touch screen, an indication to start a workout is received. In response to receiving the indication start a workout, a plurality of workout metrics for the workout are recorded with a workout application of the electronic device. A first user input is received on the pressure sensitive touch screen while recording the plurality of workout metrics. The first user input has a characteristic intensity. In response to receiving the first user input, a determination is made whether the workout application is in a locked state and whether the characteristic intensity exceeds a threshold intensity. In accordance with a determination that the workout application is in a locked state and the first user input does not exceed the threshold intensity, the workout application of the electronic device continues to record the plurality of workout metrics for the workout. In accordance with a determination that the workout application is in a locked state and the first user input exceeds the threshold intensity, recording with the workout application is stopped. In accordance with a determination that the workout application is in an unlocked state, the first user input according is processed according to the workout application. 
     An embodiment of a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display. The one or more programs includes instructions for: generating, for output on the display, a graphical representation of activity data, wherein the graphical representation includes a goal portion and a workout portion, wherein the goal portion and the workout portion each extend beyond a displayable area of the display, wherein the goal portion includes a first goal graphical element for a first goal metric, and wherein the workout portion includes a first workout graphical element for a first workout metric; displaying a first portion of the graphical representation on the display, wherein the displayed first portion includes a first graphical element; in response to receiving a first scroll input: while the displayed first portion is of the goal portion, replacing the display of the first graphical element with a display of the first goal graphical element; and while the displayed first portion is not of the goal portion, translating the first graphical element by an amount based on a magnitude of the first scroll input and displaying at least portion of the first workout graphical element. 
     An embodiment of a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display. The one or more programs includes instructions for: displaying contact information for a plurality of contacts, including a first contact; receiving, from one or more external electronic devices, activity summary data for the first contact, wherein the activity summary data for the first contact includes a first goal metric; receiving first user input selecting the first contact; in response to receiving the first user input selecting the first contact, displaying a portion of a graphical representation of the activity summary on the display, wherein the graphical representation includes a first goal graphical element for the first goal metric. 
     An embodiment of a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display. The one or more programs includes instructions for: receiving, from an external electronic device, a notification and workout summary data for a completed workout of a remote user associated with the external electronic device; displaying, on the display, a first graphical element representing the notification; receiving a first user input selecting the first graphical element while displaying the first graphical element; in response to the first user input, displaying a portion of a graphical representation of the workout summary data. 
     An embodiment of a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display. The one or more programs includes instructions for: displaying contact information, including first contact information, for a first plurality of contacts, including a first contact, wherein the first contact information corresponds to the first contact; receiving first user input indicating a selection of the first contact; in response to receiving the first user input, determining whether the portable electronic device has access to activity data associated with the first contact; in accordance with a determination that the portable electronic device has access to activity data associated with the first contact, displaying a portion of a graphical representation of the activity data; and in accordance with a determination that the electronic device does not have access to activity data associated with the first contact, displaying a graphical element indicating that activity data is not available for the first contact. 
     An embodiment of a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display. The one or more programs includes instructions for: receiving first workout data for a first segment of a multi-segment workout route, wherein the first workout data includes a plurality of locations for the multi-segment workout route and a plurality of workout metrics associated with the plurality of locations; receiving second workout data for a second segment of the multi-segment workout route, wherein the second workout data includes a plurality of locations for the multi-segment workout route and a plurality of workout metrics associated with the plurality of locations; and displaying a first graphical representation of the first workout data and a second graphical representation of the second workout data over a map, wherein the first and second graphical representations are displayed in a three-dimensional stack, wherein the appearance of the first graphical representation is based on the plurality of workout metrics of the first workout data and the second graphical representation is based on the plurality of workout metrics of the second workout data. 
     An embodiment of a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display. The one or more programs includes instructions for: receiving an indication to start a workout; in response to receiving the indication start a workout, recording with a workout application of the electronic device a plurality of workout metrics for the workout; receiving a first user input on the pressure sensitive touch screen while recording the plurality of workout metrics, wherein the first user input has a characteristic intensity; in response to receiving the first user input, determining: whether the workout application is in a locked state, and whether the characteristic intensity exceeds a threshold intensity; in accordance with a determination that the workout application is in a locked state and the first user input does not exceed the threshold intensity, continuing to record with the workout application of the electronic device the plurality of workout metrics for the workout; in accordance with a determination that the workout application is in a locked state and the first user input exceeds the threshold intensity, stopping the recording with the workout application; in accordance with a determination that the workout application is in an unlocked state, processing the first user input according to the workout application. 
     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 viewing and sharing activity data, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for viewing and sharing activity data. 
    
    
     
       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 a touch-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. 
         FIGS.  5 C- 5 D  illustrate exemplary components of a personal electronic device having a touch-sensitive display and intensity sensors in accordance with some embodiments. 
         FIGS.  5 E- 5 H  illustrate exemplary components and user interfaces of a personal electronic device in accordance with some embodiments. 
         FIGS.  6 A- 6 E  illustrate user interfaces of a portable electronic device executing a workout or activity application in accordance with some embodiments. 
         FIGS.  7 A- 7 K  illustrate user interfaces of a portable electronic device navigating and viewing activity data in accordance with some embodiments. 
         FIG.  8    is a flow diagram illustrating a method for navigating and viewing activity data using a portable electronic device in accordance with some embodiments. 
         FIG.  9    shows an exemplary functional block diagram of an electronic device in accordance with the principles of the various described embodiments. 
         FIGS.  10 A- 10 G  illustrate user interfaces of a portable electronic device navigating and viewing contact&#39;s activity data in accordance with some embodiments. 
         FIG.  11    is a flow diagram illustrating a method for navigating and viewing contact&#39;s activity data using a portable electronic device in accordance with some embodiments. 
         FIG.  12    shows an exemplary functional block diagram of an electronic device in accordance with the principles of the various described embodiments. 
         FIGS.  13 A- 13 F  illustrate exemplary user interfaces for activity and workout monitoring and sharing, in accordance with some embodiments. 
         FIG.  14    is a flow diagram illustrating a method for activity and workout monitoring and sharing using a portable electronic device in accordance with some embodiments. 
         FIG.  15    shows an exemplary functional block diagram of an electronic device in accordance with the principles of the various described embodiments. 
         FIGS.  16 A- 16 J  illustrate exemplary user interfaces navigating and sharing activity data in accordance with some embodiments. 
         FIG.  17    is a flow diagram illustrating a method for navigating and sharing activity data using a portable electronic device in accordance with some embodiments. 
         FIG.  18    shows an exemplary functional block diagram of an electronic device in accordance with the principles of the various described embodiments. 
         FIGS.  19 A- 19 D  illustrate exemplary user interfaces for viewing and navigating workout data in accordance with some embodiments. 
         FIG.  20    is a flow diagram illustrating a method  2000  for viewing and navigating workout data using a portable electronic device in accordance with some embodiments. 
         FIG.  21    shows an exemplary functional block diagram of an electronic device in accordance with the principles of the various described embodiments. 
         FIGS.  22 A- 22 F  illustrate exemplary user interfaces for pausing a workout and preventing inadvertent activation of other functions on the portable electronic device in accordance with some embodiments. 
         FIG.  23    is a flow diagram illustrating a method  2300  for pausing a workout and preventing inadvertent activation of the other functions on a portable electronic device during a workout in accordance with some embodiments. 
         FIG.  24    shows an exemplary functional block diagram of an electronic device in accordance with the principles of the various described embodiments. 
     
    
    
     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 viewing, navigating, and sharing activity or workout data and interacting with workout applications. For example, there is a need for display of workout and other activity data in a manner that allows for efficient navigation, even during a workout, easy viewing, and convenient sharing with friends. As another example, there is also a need for interfaces with workout applications that allow for easy interaction with the workout application during the work while at the same time preventing inadvertent functions form being activated during the workout. Such techniques can reduce the cognitive burden on a user who use activity and workout applications, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs. 
     Below,  FIGS.  1 A- 1 B,  2 ,  3 ,  4 A- 4 B, and  5 A- 5 H  provide a description of exemplary devices for performing the techniques for managing event notifications.  FIGS.  6 A- 6 E  illustrate exemplary user interfaces for a workout or activity application. 
       FIGS.  7 A- 7 K  illustrate user interfaces of a portable electronic device navigating and viewing activity data in accordance with some embodiments.  FIG.  8    is a flow diagram illustrating a method for navigating and viewing activity data using a portable electronic device in accordance with some embodiments. The user interfaces in  FIGS.  7 A- 7 K  are used to illustrate the processes described below, including the processes in  FIG.  8   . 
       FIGS.  10 A- 10 G  illustrate user interfaces of a portable electronic device navigating and viewing contact&#39;s activity data in accordance with some embodiments.  FIG.  11    is a flow diagram illustrating a method for navigating and viewing contact&#39;s activity data using a portable electronic device in accordance with some embodiments. The user interfaces in  FIGS.  10 A- 10 G  are used to illustrate the processes described below, including the processes in  FIG.  11   . 
       FIGS.  13 A- 13 F  illustrate exemplary user interfaces for activity and workout monitoring and sharing, in accordance with some embodiments.  FIG.  14    is a flow diagram illustrating a method for activity and workout monitoring and sharing using a portable electronic device in accordance with some embodiments. The user interfaces in  FIGS.  13 A- 13 F  are used to illustrate the processes described below, including the processes in  FIG.  14   . 
       FIGS.  16 A- 16 J  illustrate exemplary user interfaces navigating and sharing activity data in accordance with some embodiments.  FIG.  17    is a flow diagram illustrating a method for navigating and sharing activity data using a portable electronic device in accordance with some embodiments. The user interfaces in  FIGS.  16 A- 16 J  are used to illustrate the processes described below, including the processes in  FIG.  17   . 
       FIGS.  19 A- 19 D  illustrate exemplary user interfaces for viewing and navigating workout data in accordance with some embodiments.  FIG.  20    is a flow diagram illustrating a method  2000  for viewing and navigating workout data using a portable electronic device in accordance with some embodiments. The user interfaces in  FIGS.  19 A- 19 D  are used to illustrate the processes described below, including the processes in  FIG.  20   . 
       FIGS.  22 A- 22 F  illustrate exemplary user interfaces for pausing a workout and preventing inadvertent activation of other functions on the portable electronic device in accordance with some embodiments.  FIG.  23    is a flow diagram illustrating a method  2300  for pausing a workout and preventing inadvertent activation of the other functions on a portable electronic device during a workout in accordance with some embodiments. The user interfaces in  FIGS.  22 A- 22 F  are used to illustrate the processes described below, including the processes in  FIG.  23   . 
     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, Calif. 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 (I/O) subsystem  106 , other input control devices  116 , and external port  124 . Device  100  optionally includes one or more optical sensors  164 . Device  100  optionally includes one or more contact intensity sensors  165  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 RF signals, also called electromagnetic signals. RF circuitry  108  converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry  108  optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry  108  optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry  108  optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document. 
     Audio circuitry  110 , speaker  111 , and microphone  113  provide an audio interface between a user and device  100 . Audio circuitry  110  receives audio data from peripherals interface  118 , converts the audio data to an electrical signal, and transmits the electrical signal to speaker  111 . Speaker  111  converts the electrical signal to human-audible sound waves. Audio circuitry  110  also receives electrical signals converted by microphone  113  from sound waves. Audio circuitry  110  converts the electrical signal to audio data and transmits the audio data to peripherals interface  118  for processing. Audio data is, optionally, retrieved from and/or transmitted to memory  102  and/or RF circuitry  108  by peripherals interface  118 . In some embodiments, audio circuitry  110  also includes a headset jack (e.g.,  212 ,  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 , 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 is, 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, Calif. 
     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 (not shown) 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 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 .  FIG.  1 A  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 (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) 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/motion module  130  optionally detects contact with touch screen  112  (in conjunction with display controller  156 ) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module  130  includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module  130  receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module  130  and display controller  156  detect contact on a touchpad. 
     In some embodiments, contact/motion module  130  uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device  100 ). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter). 
     Contact/motion module  130  optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event. 
     Graphics module  132  includes various known software components for rendering and displaying graphics on touch screen  112  or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like. 
     In some embodiments, graphics module  132  stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module  132  receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller  156 . 
     Haptic feedback module  133  includes various software components for generating instructions used by tactile output generator(s)  167  to produce tactile outputs at one or more locations on device  100  in response to user interactions with device  100 . 
     Text input module  134 , which is, optionally, a component of graphics module  132 , provides soft keyboards for entering text in various applications (e.g., contacts  137 , e-mail  140 , IM  141 , browser  147 , and any other application that needs text input). 
     GPS module  135  determines the location of the device and provides this information for use in various applications (e.g., to telephone  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(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 view(s) displayed on touch-sensitive display  112  when the application is active or executing. In some embodiments, device/global internal state  157  is used by event sorter  170  to determine which application(s) is (are) currently active, and application internal state  192  is used by event sorter  170  to determine application views  191  to which to deliver event information. 
     In some embodiments, application internal state  192  includes additional information, such as one or more of: resume information to be used when application  136 - 1  resumes execution, user interface state information that indicates information being displayed or that is ready for display by application  136 - 1 , a state queue for enabling the user to go back to a prior state or view of application  136 - 1 , and a redo/undo queue of previous actions taken by the user. 
     Event monitor  171  receives event information from peripherals interface  118 . Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display  112 , as part of a multi-touch gesture). Peripherals interface  118  transmits information it receives from I/O subsystem  106  or a sensor, such as proximity sensor  166 , accelerometer(s)  168 , and/or microphone  113  (through audio circuitry  110 ). Information that peripherals interface  118  receives from I/O subsystem  106  includes information from touch-sensitive display  112  or a touch-sensitive surface. 
     In some embodiments, event monitor  171  sends requests to the peripherals interface  118  at predetermined intervals. In response, peripherals interface  118  transmits event information. In other embodiments, peripherals interface  118  transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration). 
     In some embodiments, event sorter  170  also includes a hit view determination module  172  and/or an active event recognizer determination module  173 . 
     Hit view determination module  172  provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display  112  displays more than one view. Views are made up of controls and other elements that a user can see on the display. 
     Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture. 
     Hit view determination module  172  receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module  172  identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module  172 , the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view. 
     Active event recognizer determination module  173  determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module  173  determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module  173  determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views. 
     Event dispatcher module  174  dispatches the event information to an event recognizer (e.g., event recognizer  180 ). In embodiments including active event recognizer determination module  173 , event dispatcher module  174  delivers the event information to an event recognizer determined by active event recognizer determination module  173 . In some embodiments, event dispatcher module  174  stores in an event queue the event information, which is retrieved by a respective event receiver  182 . 
     In some embodiments, operating system  126  includes event sorter  170 . Alternatively, application  136 - 1  includes event sorter  170 . In yet other embodiments, event sorter  170  is a stand-alone module, or a part of another module stored in memory  102 , such as contact/motion module  130 . 
     In some embodiments, application  136 - 1  includes a plurality of event handlers  190  and one or more application views  191 , each of which includes instructions for handling touch events that occur within a respective view of the application&#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 (not shown) 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)  208 , subscriber identity module (SIM) card slot  210 , headset jack  212 , and docking/charging external port  124 . Push button  206  is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device  100  also accepts verbal input for activation or deactivation of some functions through microphone  113 . Device  100  also, optionally, includes one or more contact intensity sensors  165  for detecting intensity of contacts on touch screen  112  and/or one or more tactile output generators  167  for generating tactile outputs for a user of device  100 . 
       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 I/O section  514 . 
     Memory  518  of personal electronic device  500  can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors  516 , for example, can cause the computer processors to perform the techniques described below, including method  800  ( FIG.  8   ), method  11  ( FIG.  11   ), method  1400  ( FIG.  14   ), method  1700  ( FIG.  17   ), method  2000  ( FIG.  20   ), and method  2300  ( FIG.  23   ). 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 ,  3 , and  5   ). 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. 
       FIG.  5 C  illustrates detecting a plurality of contacts  552 A- 552 E on touch-sensitive display screen  504  with a plurality of intensity sensors  524 A- 524 D.  FIG.  5 C  additionally includes intensity diagrams that show the current intensity measurements of the intensity sensors  524 A- 524 D relative to units of intensity. In this example, the intensity measurements of intensity sensors  524 A and  524 D are each 9 units of intensity, and the intensity measurements of intensity sensors  524 B and  524 C are each 7 units of intensity. In some implementations, an aggregate intensity is the sum of the intensity measurements of the plurality of intensity sensors  524 A- 524 D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a respective intensity that is a portion of the aggregate intensity.  FIG.  5 D  illustrates assigning the aggregate intensity to contacts  552 A- 552 E based on their distance from the center of force  554 . In this example, each of contacts  552 A,  552 B, and  552 E are assigned an intensity of contact of 8 intensity units of the aggregate intensity, and each of contacts  552 C and  552 D are assigned an intensity of contact of 4 intensity units of the aggregate intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij that is a portion of the aggregate intensity, A, in accordance with a predefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is the distance of the respective contact j to the center of force, and ΣDi is the sum of the distances of all the respective contacts (e.g., i=1 to last) to the center of force. The operations described with reference to  FIGS.  5 C- 5 D  can be performed using an electronic device similar or identical to device  100 ,  300 , or  500 . In some embodiments, a characteristic intensity of a contact is based on one or more intensities of the contact. In some embodiments, the intensity sensors are used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity diagrams are not part of a displayed user interface, but are included in  FIGS.  5 C- 5 D  to aid the reader. 
     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). 
       FIGS.  5 E- 5 H  illustrate detection of a gesture that includes a press input that corresponds to an increase in intensity of a contact  562  from an intensity below a light press intensity threshold (e.g., “IT L ”) in  FIG.  5 E , to an intensity above a deep press intensity threshold (e.g., “IT D ”) in  FIG.  5 H . The gesture performed with contact  562  is detected on touch-sensitive surface  560  while cursor  576  is displayed over application icon  572 B corresponding to App 2, on a displayed user interface  570  that includes application icons  572 A- 572 D displayed in predefined region  574 . In some embodiments, the gesture is detected on touch-sensitive display  504 . The intensity sensors detect the intensity of contacts on touch-sensitive surface  560 . The device determines that the intensity of contact  562  peaked above the deep press intensity threshold (e.g., “IT D ”). Contact  562  is maintained on touch-sensitive surface  560 . In response to the detection of the gesture, and in accordance with contact  562  having an intensity that goes above the deep press intensity threshold (e.g., “IT D ”) during the gesture, reduced-scale representations  578 A- 578 C (e.g., thumbnails) of recently opened documents for App 2 are displayed, as shown in  FIGS.  5 F- 5 H . In some embodiments, the intensity, which is compared to the one or more intensity thresholds, is the characteristic intensity of a contact. It should be noted that the intensity diagram for contact  562  is not part of a displayed user interface, but is included in  FIGS.  5 E- 5 H  to aid the reader. 
     In some embodiments, the display of representations  578 A- 578 C includes an animation. For example, representation  578 A is initially displayed in proximity of application icon  572 B, as shown in  FIG.  5 F . As the animation proceeds, representation  578 A moves upward and representation  578 B is displayed in proximity of application icon  572 B, as shown in  FIG.  5 G . Then, representations  578 A moves upward,  578 B moves upward toward representation  578 A, and representation  578 C is displayed in proximity of application icon  572 B, as shown in  FIG.  5 H . Representations  578 A- 578 C form an array above icon  572 B. In some embodiments, the animation progresses in accordance with an intensity of contact  562 , as shown in  FIGS.  5 F- 5 G , where the representations  578 A- 578 C appear and move upwards as the intensity of contact  562  increases toward the deep press intensity threshold (e.g., “IT D ”). In some embodiments, the intensity, on which the progress of the animation is based, is the characteristic intensity of the contact. The operations described with reference to  FIGS.  5 E- 5 H  can be performed using an electronic device similar or identical to device  100 ,  300 , or  500 . 
     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. 
     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 E and  7 A- 7 K  illustrate exemplary user interfaces for activity and workout monitoring, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIG.  8   . 
       FIG.  6 A  illustrates portable electronic device  600 . In some embodiments, device  600  includes some or all of the features of device  100 , device  300 , or device  500 , described above with respect to  FIGS.  1 A- 1 B,  2 - 3 ,  4 A- 4 B, and  5 A- 5 H . Portable electronic device  600  is displaying user interface  602  for a workout or activity application, which may help track data relating to the physical activity, health, and/or biological state of a user of portable electronic device  600 . Portable electronic device  600  may be carried with or worn on the user. For example, portable electronic device  600  may be a watch worn on a wrist of the user. Portable electronic device may also be other types of devices. 
     User interface  602  includes goal summary graphical element  604  representing the progress towards a set of goals. The progress towards each of the goals in the set of goals is represented by goal graphical elements  606 ,  608 , and  610 . For example, goal graphical element  606  may represent the progress towards a goal for the total calories burned in the day, goal graphical element  608  may represent a goal for the total time the user has spent being active that day, and goal graphical element  610  may be related to a goal for the number of hours today that user has stood up at least once. Goal summary graphical element  604  may be updated as sensors on portable electronic device  600  measure additional activity data. 
     User interface  602  also includes page indicator  612  that indicates other pages are available for viewing. For example, indicator  612  shows there is another page accessible from the current page. The solid dot in indicator  612  indicates that user interface  602 , which is currently being viewed, is the first of two pages. The non-filled indicator on the right side of the solid-filled indicator shows that there is one other page that is not being displayed but can be accessed from user interface  602 . This page may be accessed, for example, by a swipe gesture on the touch screen of portable electronic device  600 . When the page is changed, indicator  612  is updated to reflect the page that is being displayed. 
     For example, a swipe gesture to the left may display the last page and an updated indicator will be displayed showing the first dot open and the last dot filled. The result of this example is depicted in  FIG.  6 B , which includes user interface  660  showing contact information  662 ,  664 ,  666 , and  668  (although contact information  668  is only partially displayed) for a plurality of contacts (Adam, Jeff, Mary, and Nancy). Contact information  662 ,  664 ,  666 , and  668  include the first names of the contacts. The contact information could include other fields in addition to or instead of first names, such as, last names, initials, pictures, group names, or usernames. Displayed with contact information  662 ,  664 ,  666 , and  668  is a goal metric for each contact. In  FIG.  6 B , the goal metric is the progress towards each contact&#39;s goal for total calories burned for the day. The progress is indicated as a percentage of the goal. 
     Referring back to  FIG.  6 A , in addition to viewing additional pages from user interface  602 , other user input, such as a vertical scroll gesture, can be used to access additional information of user interface  602 . For example, a scroll gesture may scroll user interface  602  so that a new portion of user interface  602  is displayed. This result is depicted in  FIG.  6 C , which shows that goal summary graphical element  604  has been replaced with goal graphical element  614 , which includes similar data for a goal metric as goal graphical element  606  of  FIG.  6 A . Goal graphical element  614  also includes text specifying the current progress towards the goal. Indicator  612  is not included in  FIG.  6 C  for ease of presentation. Indicator  612 , however, could be present in any of  FIGS.  6 C- 6 E  or may not be present in  FIGS.  6 A- 6 B . 
     If one or more additional scroll gestures are received while portable electronic device  600  is in the state depicted in  FIG.  6 D , additional portions of user interface  602  may be displayed, such as the portion depicted in  FIG.  6 D . This portion includes workout graphical elements  616 ,  618 ,  620 , and  622  for respective workout metrics. In this case, the graphical elements are text. In other cases, the graphical elements can include other elements, for example text, images, video, and animations. 
     Scrolling may be possible for user interface  660  of  FIG.  6 B . For example, if a scroll input (e.g., a swipe gesture on the touch screen or rotation of a rotatable input) is received for user interface  660  as depicted in  FIG.  6 B , then user interface  660  may be scrolled to display contact information for additional contacts as depicted in  FIG.  6 E  (e.g., contact information  670  for the contact named Tom). 
       FIG.  7 A  depicts graphical representation  700  of activity data. The activity data is, for example, for a user of portable electronic device  600  ( FIGS.  6 A- 6 E ). Portions of graphical representation  702  may be displayed on portable electronic device  600  as part of a user interface (e.g., user interface  602 ). Graphical representation  702  includes goal graphical elements  604 ,  614 ,  702 ,  704 , and  706 . Goal graphical elements  604  and  614  are described with respect to  FIGS.  6 A and  6 D , respectively. Goal graphical elements  702  and  704  may be similar to goal graphical element  614  except they present different goal metrics (e.g., activity time and number hours where a user has stood). 
     Goal summary graphical element  706  displays a chronological representation of the goal metrics associated with goal graphical elements  614 ,  702 , and  704 . Specifically, graph  708  corresponds to the goal metric associated with goal graphical element  614  and depicts the magnitude of calories burned as a function of the time of day with the morning being on the left side of the graph and night being on the right side of the graph. Graph  710  similarly corresponds to the goal metric associated with goal graphical element  702 . Graph  712  similarly corresponds to the goal metric associated with goal graphical element  704 , except graph  712  depicts binary data (e.g., whether for each hour in the day the user stood up). Graphs  708 ,  710 , and  712  may be color-coded to their respective goal graphical elements. 
     Workout graphical elements  616 ,  618 ,  620 , and  622  correspond to different workout metrics for a workout of the user. For example, these graphical elements may correspond to the time of a workout, the distance of a workout, the pace of a workout, and an average or a maximum heart rate for a workout. These graphical elements may represent the most recent workout a user completed. In other cases, these or additional graphical elements may represent multiple workouts or today&#39;s workout(s). 
     Graphical representation  700  may also include additional graphical elements, such as graphical element  714 . Graphical element  714  could represent other data and information that may be interesting or useful to the user. 
     The goal related graphical elements (e.g., goal summary graphical elements  604 , goal graphical elements  614 ,  702 , and  704 , and goal graphical element  706 ) are included in goal portion  716  of graphical representation  700 . The elements in this portion are more suited for being displayed one at a time when displayed on a smaller screen. For example, it may not be desirable to display half of goal graphical element  614  and half of graphical element  702 . Instead, it may be more desirable to only display one of these elements at a time and to make it easy for a user to switch between the elements. In some embodiments, doing so may assist the user with consumption of related information, thereby reducing cognitive burden while interacting with the electronic device and improving the human-device interface. 
     The workout related graphical elements (e.g., workout graphical elements  616 ,  618 ,  620 , and  622 ) are included in workout portion  718 . In contrast to the elements of the goal portion, the elements of the workout portion may be suitable for viewing even when multiple elements are being displayed at once. Accordingly, it may be desirable for a user to have more control on what workout graphical elements are currently displayed. Embodiments described below allow for the same user input to be treated differently depending on what is being displayed. This is enable a user to user a single type of user input to scroll through the data in a manner that maintains the most useful scroll style for each portion of the graphical presentation. 
       FIG.  7 B  depicts graphical representation  701  of activity data. Graphical representation  701  is similar to graphical representation  700  with a few exceptions. First, instead of goal graphical indicators  702  and  704  of graphical representation  700 , goal graphical elements  720  and  722 , which correspond to the goal metrics for goal graphical indicators  702  and  704 , are included and sized the same as goal graphical element  614 . Second, there are no elements in graphical representation  701  for chronological goal data, as depicted in goal graphical elements  706 . Third, graphical representation  701  includes graphical elements  724  and  730  that are not included in either goal portion  726  or workout portion  728 . Graphical elements  724  and  730  may be other types of graphical elements, such as a summary of activity data for friends or a description of other data. Fourth, workout portion  728  excludes workout graphical elements  616  and  714 . 
     Graphical representations  700  and  701  extend beyond the displayable area when displayed on of the display of portable electronic device  600 . In some cases, graphical representation  700  and  701  may have widths that correspond with the width of the displayable area of the display of portable electronic device  600  and have heights that are multiples of the height of the displayable area of the display of portable electronic device  600 . The reverse could also be true (i.e., height corresponds but width is many multiples). Additionally, as explained above, the different portions of the graphical representations may have suitable scrolling styles that are different. Specifically, as explained in more detail in the following paragraphs with respect to  FIGS.  7 C- 7 K , the goal portion of a graphical representation of activity data may be more suited to scrolling an entire graphical element at a time while the workout portion may be suited to a more continuous scrolling style. 
       FIG.  7 C , which is the same as  FIG.  6 A , depicts user interface  602  that is displaying a portion of graphical representation  700 . The displayed portion of graphical representation  700  includes goal summary graphical element  604 , which is part of the goal portion of graphical representation  700 . Because the graphical elements of the goal portion are more suited to being displayed one at a time, in response to a scroll input from the bottom of the display to the top of the display, the display of goal summary graphical element  604  is replaced with goal graphical element  614 , as depicted in  FIG.  7 D . 
     In the goal portion, the display transition from summary graphical element  604  to goal graphical element  614  or, more generically, from one graphical element to an adjacent graphical element, may take place through various mechanisms. For example the transition from goal graphical element  614  ( FIG.  7 D ) to goal graphical element  702  ( FIG.  7 F ) may, in response to a scroll input, be in the form of a translation of the graphical elements, in the form of a shrinking/growing animation, or in other forms. 
       FIG.  7 E  depicts an instant of a display transition in the form of a translation of the graphical elements. As the scroll input is received, goal graphical element  614  translates up and off of the display while goal graphical element  702  translates up and on to the display. If the scroll input ceases before goal graphical element  702  has fully replaced goal graphical element  614 , one of the graphical elements snaps to the display while the other is not displayed. For example, as depicted in  FIG.  7 E , more than half of goal graphical element  614  has translated off of the display and more than half of goal graphical element  702  has translated on to the display. In this case, because more than half of goal graphical element  702  is now displayed, in response to the scroll input ceasing and without further user input, all of goal graphical element  702  may be displayed without displaying any of goal graphical element  702 , as depicted in  FIG.  7 F . Other thresholds beside a half could also be used (e.g., a third or a quarter). If the threshold is not exceeded, the display will return to displaying only goal graphical element  614 , as depicted in  FIG.  7 D . 
       FIG.  7 G  depicts an instant of another display transition from  FIG.  7 D  to  FIG.  7 F  in the form of a shrinking/growing transition. As the scroll input is received, goal graphical element  614  shrinks and goal graphical element  702  grows. For example, transition graphical element  732  in  FIG.  7 G  depicts shrinking portion  734  that corresponds to goal graphical indicator  614  and depicts growing portion  736  that corresponds to goal graphical indicator  702 . As with the translation transition described in the previous paragraph, if the scroll input ends and the display transition exceeds a threshold level, then the display will snap to goal graphical element  702 , as depicted in  FIG.  7 F , without any additional user input. If the threshold is not exceeded, the display will automatically return to goal graphical element  614 , as depicted in  FIG.  7 D , in response to the scroll input ceasing. 
     The transition to the rest of the graphical elements (e.g., goal graphical element  706  of  FIG.  7 H ) of the goal portion of graphical representation  700  ( FIG.  7 A ) are performed in a similar manner. In addition to the translation and shrinking/growing animation transitions described above, other transitions could also be used, such as replacing display of the graphical elements in response to a certain level of scroll input or fading the graphical elements in and out in response to the scroll input. 
       FIG.  7 I  depicts the transition from displaying graphical elements of the goal portion to graphical elements of the workout portion of graphical representation  700  of activity data. This transition may occur similar to the transitions described above so that when a threshold part of the workout portion or a workout graphical element is displayed in response to a scroll input (e.g., as depicted in  FIG.  7 I ), the display may snap to the first workout graphical element (e.g., workout graphical element  616  in  FIG.  7 J ) automatically without further user input in response to the scroll input ceasing. Alternatively, once a portion of the workout portion is displayed, a scroll input may be more continuous and the display may be maintained in its current state in response to the scroll input ceasing. For example, if the scroll input ceased while the display included part of goal graphical element  706  and graphical element  612 , as depicted in  FIG.  7 I , the display may be maintained. 
     Once workout graphical elements (e.g., workout graphical elements  616 ,  618 ,  620 ,  622 , or  714 ) are being displayed (e.g., as depicted in  FIG.  7 J ), a scroll input may result in a more continuous scroll as opposed to the scroll behavior that snapped to graphical elements discussed above with respect to the goal portion. The displayed workout graphical elements of the work portion may be translated an amount proportional to the scroll input and not automatically translated further in response to the scroll input ceasing. For example, with respect to  FIG.  7 K , in response to a scroll input ceasing while only parts of workout graphical elements  612  and  618  are displayed, the display may be maintained absent further user input. Alternatively, the display may automatically translate the workout graphical elements so that the closest workout graphical element is aligned with the top of the display. 
       FIG.  8    is a flow diagram illustrating a method for navigating and viewing activity data using a portable electronic device in accordance with some embodiments. Method  800  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 ) with a display and, in some cases, a touch sensitive screen. Some operations in method  800  are, optionally, combined, the order of some operations is, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  800  provides an intuitive way for navigating and viewing activity data. The method reduces the cognitive burden on a user for navigating menus and view different types of activity metrics, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to navigate and comprehend data faster and more efficiently conserves power and increases the time between battery charges. 
     In block  802 , a graphical representation of activity data is generated for output on to a display of the portable electronic device. For example, one or more processors of the portable electronic device may generate the graphical representation. The graphical representation may be, for example, graphical representations  700  or  701  of  FIGS.  7 A and  7 B , respectively. The activity data may be generated on the portable electronic device, for example, by taking measurements with one or more sensors of the portable electronic device. The activity data may also be received from external sources, such as a companion device. Other methods for obtaining the activity data may also be used. 
     The graphical representation generated in block  802  includes a goal portion and a workout portion. The goal portion includes a goal graphical element for a goal metric. The workout portion includes a workout graphical element for a workout metric. The graphical representation is larger than the displayable area of the display of the portable electronic device. Some embodiments of method  800 , allow for easy navigation of the graphical representation and thus make it easy to recognize and comprehend the data represented in the graphical representation. More description and examples of graphical representations for activity may be found in  FIGS.  7 A and  7 B  and associated descriptions. 
     In block  804 , a portion of the graphical representation is displayed on the display of the portable electronic device. The displayed first portion includes a first graphical element, which may be a goal graphical element (e.g., goal graphical element  614  of graphical representation  700  of  FIG.  7 A ) of the goal portion, a workout graphical element (e.g., workout graphical element  614  of graphical representation  700  of  FIG.  7 A ) of the workout portion, or another graphical element. 
     In block  806 , a scroll in input is received at the portable electronic device. For example, a scroll input may be any input that is interpreted as a scroll, such as a swipe gesture or drag gesture on the touch screen or a rotation of a rotatable input. Other types of scroll inputs could also be used. 
     In block  808 , while the displayed portion is of the goal portion, the display of the first graphical element is replaced with display of the first goal graphical element. For example, if the first graphical element of block  804  is another goal graphical element (e.g., goal graphical element  604  of  FIG.  7 A ) the displayed portion is of the goal portion. In this example, in response to receiving the scroll input of block  806 , goal graphic element  604  is replaced with the first goal graphical element (e.g., goal graphical element  614  of  FIG.  7 A ). This result is depicted in the transition from  FIG.  7 C  to  FIG.  7 D . This block may be performed by one or processors, including graphics processors, of the portable electronic device. 
     In some variations of method  800 , the transition from display of the first graphical element to the display of the first goal graphical element includes an animation. For example, the shrinking/growing animation described with respect to  FIG.  7 G  could be used. This animation may be generated via one or processors, including graphics processors, of the portable electronic device. 
     Optionally in block  810  as part of block  808 , in response to detecting that the scroll input has stopped, an amount that the first goal graphical element is being displayed is determined, for example, by one or more processors of the portable electronic device. If the displayed amount is greater than a threshold amount, display of the first goal graphical element may automatically and completely replace the display of the first graphical element. If the displayed amount is less than the threshold amount, the display of the first graphical element may be automatically restored and the first goal graphical element will be not displayed at all. This block is also described with respect to the transitions from  FIG.  7 D  to  FIG.  7 F  via  FIG.  7 E or  7 G . 
     There are many possible values for the threshold. For example, the threshold may be 50%. Determining the displayed amount of the first goal graphical element may be carried out with various methods, include directly determining the amount of the first goal graphical element that is displayed, determining the amount of the first graphical element that is displayed, or determining the magnitude of the scroll input that was received. 
     In some variations of method  800 , after displaying the first goal graphical element (e.g., goal graphical element  614  of  FIG.  7 A ) as described in block  808 , another scroll input is received (e.g., in a similar manner as the scroll input of block  806  was received. In response to the scroll input, a part of a second goal graphical element (e.g., goal graphical element  702  of  FIG.  7 E ) is displayed with a part of first goal graphical element (e.g., goal graphical element  614  of  FIG.  7 E ). In accordance with the displayed part of the second goal graphical element exceeding a threshold, the second goal graphical element is displayed without displaying the first goal graphical element. For example, as described above with respect to the description of the transition from  FIG.  7 D  to  FIG.  7 F  via  FIG.  7 E , either first goal graphical element  614  or second goal graphical element  702  will be displayed (but not both) in response to detecting the scroll input has ceased. If the scroll amount (e.g., the displayed part of the second goal graphical) has exceeded a threshold, the second goal graphical element will be displayed without the first goal graphical element. Otherwise, the display of the first goal graphical element is restored without display of the second goal graphical element. 
     In block  812 , while the displayed portion is not of the goal portion, the display of the first graphical element is translated an amount based on a magnitude of the scroll input. Additionally, at least part of the first workout graphical element is also displayed. For example, if the first graphical element of block  804  is another workout graphical element (e.g., workout graphical element  616  of  FIG.  7 J ) the displayed portion is of the workout portion (i.e., not of the goal portion). In this example, in response to receiving the scroll input of block  806 , workout graphic element  616  is translated up the display so that only part of the element is displayed. At the same time, part of a first workout graphical element (e.g., workout graphical element  622  of  FIG.  7 A ) is also displayed. This result is depicted in the transition from  FIG.  7 J  to  FIG.  7 K . This block may be performed by one or processors, including graphics processors, of the portable electronic device. In response to detecting that the scroll input has ceased, the partial displays of workout graphical elements  616  and  622  is maintained, as depicted in  FIG.  7 K . 
     In some variations of process  800 , after displaying the first workout graphical element (e.g., workout graphical element  616  of  FIG.  7 A ) as described in block  808 , another scroll input is received (e.g., in a similar manner as the scroll input of block  806  was received). In response to the scroll input, a part of a second workout graphical element (e.g., workout graphical element  622  of  FIG.  7 K ) is displayed with a part of first workout graphical element (e.g., workout graphical element  616  of  FIG.  7 K ). This display is maintained even when the scroll input ceases. For example, as described above with respect to the description of the transition from  FIG.  7 J  to  FIG.  7 K , both first workout graphical element  616  or second workout graphical element  622  will be displayed in response to detecting the scroll input has ceased. 
     Note that details of the processes described above with respect to method  800  (e.g.,  FIG.  8   ) are also applicable in an analogous manner to the methods described below. For example, method  1100  ( FIG.  11   ), method  1400  ( FIG.  14   ), method  1700  ( FIG.  17   ), method  2000  ( FIG.  20   ) and method  2300  ( FIG.  23   ) optionally includes one or more of the characteristics of the various methods described above with reference to method  800 . For example, method  800 &#39;s scrolling style may be applicable to view data in these other methods. For brevity, these details are not repeated below. 
     In accordance with some embodiments,  FIG.  9    shows an exemplary functional block diagram of an electronic device  900  configured in accordance with the principles of the various described embodiments. In accordance with some embodiments, the functional blocks of electronic device  900  are configured to perform the techniques described above. The functional blocks of the device  900  are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG.  9    are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG.  9   , an electronic device  900  includes a display unit  902  configured to display a graphic user interface, a touch-sensitive surface unit  904  configured to receive contacts (i.e., touches), optionally a pressure-sensitive surface unit  918 , and a processing unit  906  coupled to the display unit  902  and the touch-sensitive surface unit  904 . In some embodiments, the processing unit  906  includes a display enabling unit  908 , receiving unit  910 , a determining unit  912 , a generating unit  914 , and, optionally, a detecting unit  916 . 
     The processing unit  906  is configured to: generate (e.g., with generating unit  914 ), for output on the display, a graphical representation of activity data, wherein the graphical representation includes a goal portion and a workout portion, where: the goal portion and the workout portion each extend beyond the displayable area of the display, the goal portion includes a first goal graphical element for a first goal metric, and the workout portion includes a first workout graphical element for a first workout metric. The processing unit  906  is further configured to enable display (e.g., with display enabling unit  908 ) of a first portion of the graphical representation on the display unit  902 , where the displayed first portion includes a first graphical element. The processing unit  906  is further configured to in response to receiving a first scroll input (e.g., with touch-sensitive surface unit  904 ): while the displayed first portion is of the goal portion, enable replacing (e.g., with displaying enabling unit  908 ) of the display of the first graphical element with a display of the first goal graphical element; and while the displayed first portion is not of the goal portion, enable translating (e.g., with displaying enabling unit  908 ) the first graphical element by an amount based on a magnitude of the first scroll input and displaying at least portion of the first workout graphical element. 
     In some embodiments replacing the display of the first graphical element with a display of the first goal graphical element includes transitioning the first graphical element to the first goal graphical element via an animation. 
     In some embodiments, the processing unit  906  is further configured to, in response to receiving (e.g., with receiving unit  910 ) the first scroll input, enabling display (e.g., with display enabling unit  908 ) of a part of the first graphical element while displaying a part of the first goal graphical element. The processing unit  906  is further configured to, while the displayed first portion is of the goal portion and in response to detecting (e.g., with detecting unit  916 ) that the first scroll input has stopped, determining (e.g., with determining unit  912 ) whether the displayed part of the first goal graphical element is greater than a threshold, wherein replacing the display of the first graphical element with the display of the first goal graphical element is in accordance with a determination that the displayed part of the first goal graphical element exceeds the threshold. 
     In some embodiments, the goal portion includes a second goal graphical element for a second goal metric and the processing unit  902  is further configured to, while displaying the first goal graphical element, receiving (e.g., with receiving unit  910 ) a second scroll input. The processing unit  902  is further configured to, in response to receiving the second scroll input, enable display (e.g., with display enabling unit  909 ) display of a part of the first goal graphical element while displaying a part of the second goal graphical element. The processing unit  902  is further configured to, in response to detecting that the first scroll input has stopped, determining (e.g., with determining unit  912 ) whether the displayed part of the second goal graphical element is greater than a threshold. The processing unit  906  is further configured to, in accordance with a determination that the displayed part of the second goal graphical element is greater than the threshold intensity, enabling replacement (e.g., with the display enabling unit  908 ) of the display of the first goal graphical element with display of the second goal graphical element. 
     In some embodiments, the graphical representation includes a goal summary portion having a summary graphical element representing chronological data for the first goal metric. 
     In some embodiments, a color of the summary graphical element corresponds to a color of the first goal metric. 
     In some embodiments, the workout portion includes a second workout graphical element for a second workout metric and the processing unit  906  is further configured to, while displaying the first workout graphical element, receiving (e.g., with the receiving unit  910 ) a third scroll input. The processing unit  906  is further configured to, in response to receiving the third scroll input, enabling translation (e.g., with display enabling unit  908 ) of the display of the first workout graphical element an amount based on the third scroll input while displaying a part of the second workout graphical element. The processing unit  906  is further configured to, after the second scroll input has ceased, enabling the maintaining (e.g. with displaying enabling unit  908 ) of display of a part of the first workout graphical element and display of the part of the second workout graphical element. 
     In some embodiments, the portable electronic device includes a pressure sensitive touch screen unit  918  and the processing unit  906  is further configured to receive (e.g., with receiving unit  910 ) user input on the pressure sensitive touch screen unit ( 918 ) while displaying part of the goal portion of the graphical representation of activity data, where the user input has a characteristic intensity. The processing unit  906  is further configured to determine whether the characteristic intensity exceeds an intensity threshold in accordance with a determination that the user input exceeds the intensity threshold: enable display (e.g., with display enabling unit  908 ) of an affordance for entering a goal setting interface and in response to receiving user input selecting the affordance, enabling display (e.g., with display enabling unit  908 ) of the goal setting interface. The processing unit  906  is further configured to receive (e.g., with the receiving unit  912 ) via the goal setting interface user input indicating a new value for the first goal via a displayed user interface element. 
       FIGS.  10 A- 10 G  illustrate user interfaces of a portable electronic device navigating and viewing activity data in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIG.  11   . 
       FIG.  10 A  (which is the same as  FIG.  6 B ) depicts user interface  660  on portable electronic device  600 . User interface  660  includes contact information graphical element  662 ,  664 , and  668  (only partially visible) for the contacts corresponding to names Adam, Jeff, and Nancy (name not visible). User interface  600  also includes information graphical element  666  (labeled “Me”) for the user of portable electronic device  600 . Each contact information graphical element includes contact information, which in this case is the name of each contact represented by the contact information graphical element. Each contact information graphical element and the other information graphical element also includes a goal graphical element for a goal metric (in this case, the progress towards the calories goal for the day). Other graphical elements for other goal metrics, workout metrics, and other contact information could also be included. 
     The contact information accessible through user interface  660  provides access to contacts that share activity data, including goal or workout data, with the user of portable electronic device  600 . User interface  660  provides an easy interface for the user of portable electronic device  600  to rank herself or himself against friends, co-workers, and/or other acquaintances represented by the contact information. In  FIG.  10 A , the contact information is sorted alphabetically according to the name of each corresponding contact. A sort interface, such as sort interface  1000  of  FIG.  10 B , may be provided to allow the user to select how to sort the contact information displayed in user interface  660 . 
     For example, sort interface  1000  of  FIG.  10 B  may be displayed in response to receiving corresponding user input on user interface  660  as displayed in  FIG.  10 A . If portable electronic device  600  has a pressure sensitive touch screen, then sort interface  1000  may be displayed in response to a touch on the pressure sensitive touch screen that has a characteristic intensity that is greater than a threshold intensity. Sort interface  1000  includes affordances  1002 ,  1004 , and  1006  that allow a user to select a parameter that will be used to sort the contact information. Affordance  1002  selects the contact names for sorting, which is displayed in FIG.  10 A. Affordance  1004  selects the progress towards the calories goal for sorting the contact information, the result of which is depicted in  FIG.  10 C . Affordance  1006  selects the number of completed workouts that day as the parameter for sorting the contact information. Other parameters are also possible, such as other goal metrics, types of workouts completed, and other workout metrics. 
     Referring to  FIG.  10 C , in response to receiving user input selecting contact information graphical element  664 , graphical representation  1008  ( FIG.  10 D ) of activity data for Jeff may be generate for display on the display of portable electronic device  600 , as depicted in  FIGS.  10 E- 10 G . Alternatively, graphical representation  1008  could be generated prior to selecting of a contact information graphical element or could be generated on the fly as portions of graphical representation  1008  are displayed. The activity data may be received from an external electronic device, such as an electronic device that is associated with Jeff. The activity data could be received from the electronic device associated with Jeff via a server that stores and distributes such data. The activity data may be, for example, received on a periodic basis, when user interface  660  is first displayed, when a contact information graphical element is selected, or at other times. 
     Referring to  FIG.  10 D , graphical representation  1008  of activity data for Jeff may be similar to the graphical representations of activity data described with respect to  FIGS.  7 A and  7 B . Graphical representation  1008  of activity data for Jeff may include goal graphical elements  1010 ,  1012 ,  1014 ,  1016 ,  1018 , and  1022 . These graphical elements may provide information about the progress that Jeff has made towards various activity goals. Graphical representation  1008  of activity data for Jeff may also include workout graphical elements  1024 ,  1026 , and  1028  that may provide data for a workout that Jeff has completed today or someone other time period. Multiple sets of workout elements could also be included for additional workouts that Jeff has completed. While one example graphical representation of activity data has been provided in  FIG.  10 D , may other representations that contain other combinations and/or types of data could also be displayed. 
     Referring to  FIGS.  10 E and  10 F , portions of graphical representation  1008  ( FIG.  10 D ) of activity data for Jeff are displayed. Graphical representation  1008  can be navigated using a scroll input (e.g., a swipe or drag on the touch sensitive screen or rotation of a rotatable input mechanism). In addition to graphical representation  1008  of activity data for Jeff, affordances  1030  and  1032  may also be displayed after the end of graphical presentation  1008 , as depicted in  FIG.  10 G , so that communication may be initiated with the contact (Jeff in the case of  FIG.  10 G ). Selection of affordance  1030  or  1032  may open a communication application (e.g., email, messaging, or social networking) with Jeff&#39;s contact information for the communication application. A message may then be entered or a pre-defined message may be selected for sending to Jeff. Pre-defined message can include any type of messages, such as messages of encouragement, competition, or praise. 
       FIG.  11    is a flow diagram illustrating a method for navigating and viewing contact&#39;s activity data using a portable electronic device in accordance with some embodiments. Method  1100  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 ) with a display and, in some cases, a touch sensitive screen or a touch sensitive screen that is also pressure sensitive. Some operations in method  1100  are, optionally, combined, the order of some operations are, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  1100  provides an intuitive way for navigating and viewing contact&#39;s activity data. The method reduces the cognitive burden on a user for navigating menus and view different types of activity metrics, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to navigate and comprehend data faster and more efficiently conserves power and increases the time between battery charges. 
     In block  1102 , contact information for a plurality of contacts is displayed on a display of a device. The contact information includes information for a first contact.  FIGS.  10 A and  10 C  depict examples displays resulting from the performance of block  1102 . The contact information for a first contact is, for example, contact information graphical element  664  of  FIGS.  10 A and  10 C . In some variations of method  1100 , the contact information graphical elements may include workout data or goal data as well, as depicted in contact graphical elements  662 ,  664 , and  668  of  FIGS.  10 A and  10 C . 
     In some variations of method  1100 , an information graphical element is also displayed for the user of the device. For example, as depicted in  FIG.  10 A , user interface  660  includes information graphical element  666  that includes goal data for the owner (labeled as “Me”) of portable electronic device  600 . 
     In some variation of method  1100 , a parameter for sorting the contact information is received via a sort interface. The sort interface may be accessed from or through a user interface displaying the contact information by, for example, touching a touch sensitive screen of the device that is also pressure sensitive. If the touch has a characteristic intensity that exceeds an intensity threshold, then the sort interface is entered. The sort interface (e.g., sort interface  1000  of  FIG.  10 B ) allows a user to select a parameter for sorting the contact information. The parameter may be selected via touches on displayed affordances associated with the various parameters. After the parameter is selected (e.g., selecting affordance  1004  of  FIG.  10 B  for the calories progress parameter), the contact information is updated based on the sorting parameters (e.g., the display of  FIG.  10 A  is updated with the display of  FIG.  10 C ). 
     In block  1104 , activity summary data is received from one or more external devices. Block  1104  may occur before or after block  1102  and before, after, or in response to block  1106 . The activity summary data may include at least a first goal metric, such as the progress towards a calories burned goal, an activity measurement goal (e.g., standing up every hour), an exercise time goal, or other types of goals. In variations of method  1100 , activity summary data may also include data for one or workout metrics, such as performance data for a recent workout or other workout related data (e.g., a pace, a distance, a time, a calorie value, and a heart rate). The activity summary data may be received from one or more external devices, such as an electronic device associated with the contact (e.g., with respect the example of Jeff as the first contact, a smartphone and/or an activity monitor belonging to Jeff). The activity summary data may also be received via one or more servers. 
     In block  1106 , first user input selecting the first contact is received. For example, with respect to  FIGS.  10 A and  10 C , contact information graphical elements  662 ,  664 , and  668  may be affordances that are selectable via a touch sensitive screen. Alternatively, a first contact may be selected via hardware inputs, such as buttons, keyboards, rotatable inputs, or other types of interface devices inputs. 
     In block  1108 , in response to receiving the first user input selecting the first contact in block  1106 , a portion of a graphical representation of the activity summary data is displayed on the display, such as the portions depicted in and described with respect to  FIGS.  10 E- 10 G . The graphical representation includes at least a first goal graphical element, such as a graphical indicator or text, for the first goal metric. The graphical representation may be, for example, graphical representation  1008  of  FIG.  10 D . The graphical representation may include any number of different activity graphical elements, including goal graphical elements and workout graphical elements. 
     In addition to displaying a portion of the graphical representation, affordances for communicating with the selected contact may be displayed. For example, with respect to  FIG.  10 G , affordances  1030  and  1032  may allow a user of the device to send a message Jeff, as described above. Alternatively, the affordances may be a part of the graphical representation. 
     In accordance with some embodiments,  FIG.  12    shows an exemplary functional block diagram of an electronic device  1200  configured in accordance with the principles of the various described embodiments. In accordance with some embodiments, the functional blocks of electronic device  1200  are configured to perform the techniques described above. The functional blocks of the device  1200  are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG.  12    are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG.  12   , an electronic device  1200  includes a display unit  1202  configured to display a graphic user interface, a touch-sensitive surface unit  1204  configured to receive contacts (i.e., touches), optionally a pressure-sensitive surface unit  1216 , and a processing unit  1206  coupled to the display unit  1202  and the touch-sensitive surface unit  1204 . In some embodiments, the processing unit  1206  includes a display enabling unit  1208  and receiving unit  1210  and optionally a determining unit  1212 , a sorting unit  1214 . 
     The processing unit  1206  is configured to enable display of (e.g., with display enabling unit  1208 ) of contact information for a plurality of contacts, including a first contact. The processing unit  1206  is further configured to receive (e.g., with receiving unit  1210 ), from one or more external electronic devices, activity summary data for the first contact, where the activity summary data for the first contact includes a first goal metric and to receive (e.g., with receiving unit  1210 ) first user input selecting the first contact. The processing unit  1206  is further configured to, in response to receiving the first user input selecting the first contact, enable display of (e.g., with display enabling unit  1208 ) a portion of a graphical representation of the activity summary on the display, where the graphical representation includes a first goal graphical element for the first goal metric. 
     In some embodiments, the displayed contact information includes workout data or goal data for each of the plurality of contacts. 
     In some embodiments, the portable electronic device includes a pressure sensitive touch screen and the processing unit  1206  is further configured to, while displaying the contact information, receive (e.g., with receiving unit  1210 ) second user input on the pressure sensitive touch screen, where the second user input has a characteristic intensity. The processing unit  1206  is further configured to, in response to receiving the second user input, determine (e.g., with determining unit  1212 ) whether the characteristic intensity exceeds a threshold intensity. The processing unit  1206  is further configured to, in accordance with a determination that the second user input exceeds the threshold intensity, enable display of (e.g., with display enabling unit  1208 ) a sort interface for selecting a parameter by which to sort the first plurality of contacts. The processing unit  1206  is further configured to, while displaying the sort interface, receive (e.g., with receiving unit  1210 ) a third user input identifying a parameter for sorting the plurality of contacts. The processing unit  1206  is further configured to, in response to receiving the second user input, sort (e.g., with sort interface  1214 ) the first plurality of contacts to generate a sorted first plurality of contacts based on the parameter. The processing unit  1206  is further configured to enable update of the display of (e.g., with display enabling unit  1208 ) the contact information based on the sorted first plurality of contacts. 
     In some embodiments, the graphical representation of the activity summary includes an affordance for contacting the first contact and the processing unit  1206  is further configured to receive (e.g., with receiving unit  1210 ) third user input indicating selection of the affordance. The processing unit  1206  is further configured to, in response to receiving the third user input, enable display of (e.g., with display enabling unit  1208 ) a messaging user interface configured to receive message input for the first contact on the portable electronic device. 
     In some embodiments, the first goal metric is at least one of a number of calories burned or a measurement of an activity. 
     In some embodiments, the activity summary includes a first workout metric and the graphical representation includes a first workout graphical element for the first workout metric. 
     In some embodiments, the first workout metric is selected from the group consisting of a pace, a distance, a time, a calorie value, and a heart rate. 
     In some embodiments, the processing unit  1206  is further configured to, while displaying the contact information, enable display of (e.g., with display enabling unit  1208 ) a graphical element corresponding to a user of the portable electronic device, where the graphical element includes an activity graphical element for the user. 
       FIGS.  13 A- 13 F  illustrate exemplary user interfaces for activity and workout monitoring and sharing, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIG.  14   . 
       FIG.  13 A  depicts user interface  1300  on portable electronic device  600 . User interface  1300  includes a graphical element in the form of notification indicator  1302  and graphical element  1304 , which is displaying the current date and time. In addition to notification indicator  1302  indicating that a notification has been received, portable electronic device  600  may also alert a user in other ways that a notification has been received, such as haptic feedback, an audio indicator, other visual indications, or other ways of notifying the user. Indicator  1302  may indicate that any number of notifications have been received, including a notification of a completed workout of a remote user. 
     The notification may be received from one or more external devices. For example, the notification may be received from a device associated with the remote user of an electronic device. The notification may be received via one or more servers. The notification may also be received via an electronic device that is associated with the user. For example, the portable electronic device may be a watch and the notification may be received at the watch via communication with a paired smartphone, which may receive the notification via one or more servers that received the notification from the external electronic device associated with the remote user. 
     In addition to receiving the notification, workout summary data may also be received in a similar manner. The workout summary data can be received via the same or different paths described previously. Additionally, the workout summary data and notification could be received at the same time or at different times. The workout summary data and notification also could be the same data (i.e., the notification is the workout summary data). 
     Referring to  FIG.  13 B , user input may be received that initiates access to a notification center that includes information for the received notification. For example, a user may touch indicator  1302  on the touch sensitive screen and drag down the touch to pull down the notification center from the top of the display.  FIG.  13 B  depicts notification center  1306  about half-way through being pulled down. Notification alert graphical element  1310  is displayed with notification information  1314  and indication  1316 , which indicates an application that is associated with the notification. Notification alert graphical element  1308  along with notification information  1312  are partially visible. 
     Referring to  FIG.  13 C  the interface for notification center  1306  is fully visible. Two notification alert graphical elements ( 1308  and  1310 ) are present. If additional notifications were available, the associated notification alert graphical elements could be displayed via a scrolling input (e.g., via a swipe or drag gesture). Notification alert graphical alert  1308  includes indication  1318 , which indicates an application that is associated with the notification. 
     Notification alert graphical elements  1308  and  1310  may be affordances for selecting the associated notification or associated application. For example, a user may select one of the affordances via a touch sensitive screen. Other input methods could also be used to select a notification alert. 
     In response to a selection of a notification alert graphical element for the Workout application (graphical element  1310 ), a graphical representation of the received workout summary data that corresponds to the notification is at least partially displayed in the Workout application, as depicted in  FIGS.  13 D- 13 F . If the graphical representation extends beyond the size of the displayable area of the display, the other portions may be accessed by scrolling the display via a user input (e.g., touch sensitive screen or other hardware user inputs), as depicted in  FIGS.  13 D- 13 F  ( FIG.  13 E  depicts the result of a first scroll input and  FIG.  13 F  depicts the result of a second scroll input). In this example, the graphical representation includes workout graphical elements  1320 ,  1322 ,  1324 ,  1326 , and  1330  that all relate to different aspects of the workout. For example, workout graphical element  1330  in  FIG.  13 D  includes a graphical element indicating the type of workout completed; workout graphical elements  1326  includes a graphical element indicating the weather associated with the completed workout; and workout graphical elements  1320 ,  1322 , and  1324  include graphical elements for workout metric data (e.g., pace, distance, time, calories burned, or a heart rate) for the completed workout. The graphical representation could also include graphical elements for other types of data, such as goal metrics (e.g., for calories burned, number of steps, a count of hours when time was spent standing, or other measurements of an activity). 
     As part of or in addition to the graphical representation, one or more affordances may be displayed, such as affordance  1328  of  FIG.  13 F . The one or more affordances may provide various actions that the user may perform by selecting an affordance. For example with respect to affordance  1328  of  FIG.  13 F , selecting affordance  1328  will open a messaging user interface that a user can use to enter a message for the contact associated with the graphical representation. In the case of  FIGS.  13 D- 13 F , selecting affordance  1328  would result in a messaging interface for sending Adam a message. The messaging interface can also include the ability to select and send pre-defined messages. Pre-defined message can include any type of messages, such as messages of encouragement, competition, or praise. 
       FIG.  14    is a flow diagram illustrating a method for activity and workout monitoring and sharing using a portable electronic device in accordance with some embodiments. Method  1400  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 ) with a display. Some operations in method  1400  are, optionally, combined, the order of some operations is, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  1400  provides an intuitive way for navigating and viewing completed activity notifications and associated workout data. The method reduces the cognitive burden on a user for navigating menus and view different types of activity metrics, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to navigate and comprehend data faster and more efficiently conserves power and increases the time between battery charges. 
     In block  1402 , a notification and workout summary data are received from an external electronic device. The workout summary data may be for a completed workout of a remote user associated with the external electronic device. The notification may be, for example, a Push Notification or other type of notification that is generated in response to an indication from the external electronic device that the remote user completed a workout. The workout summary data may include data for one or more workout metrics, such as those described above with respect to  FIGS.  13 D- 13 F . 
     In block  1404 , a first graphical element representing the notification is displayed on the display, such as described above with respect to  FIG.  13 C . The display of the first graphical element may occur after receipt of the workout summary data or, if the notification and workout summary data are different data, the display of the first graphical element could occur before the receipt of the workout summary data. 
     In block  1406 , while displaying the first graphical element, a first user input selecting the first graphical element is received. The first user input may be, for example, a touch on the touch sensitive screen while displaying the first graphical element. In other words, the first graphical element may be an affordance, as described above with respect to  FIG.  13 C . 
     In block  1408 , in response to the first user input, a portion of a graphical representation of the workout summary data is displayed. For example, the graphical representation may be similar to the graphical representations described previously with respect to  FIGS.  7 A,  7 B, and  10 D  except the graphical representation in block  1408  is for the workout summary data. Portions of an example graphical representation of workout summary data are depicted in  FIGS.  13 D- 13 F . 
     In accordance with some embodiments,  FIG.  15    shows an exemplary functional block diagram of an electronic device  1500  configured in accordance with the principles of the various described embodiments. In accordance with some embodiments, the functional blocks of electronic device  1500  are configured to perform the techniques described above. The functional blocks of the device  1500  are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG.  15    are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG.  15   , an electronic device  1500  includes a display unit  1502  configured to display a graphic user interface, a touch-sensitive surface unit  1504  configured to receive contacts (i.e., touches), and a processing unit  1506  coupled to the display unit  1502  and the touch-sensitive surface unit  1504 . In some embodiments, the processing unit  1506  includes a display enabling unit  1508  and receiving unit  1510 . 
     The processing unit  1506  is configured to: receive (e.g., with receiving unit  1510 ), from an external electronic device, a notification and workout summary data for a completed workout of a remote user associated with the external electronic device; enable display (e.g., with display enabling unit  1508 ) of, on the display (e.g., display unit  1502 ), a first graphical element representing the notification; receive (e.g., with receiving unit  1510 ) a first user input selecting the first graphical element while displaying the first graphical element; and in response to the first user input, enable display (e.g., with display enabling unit  1508 ) of a portion of a graphical representation of the workout summary data. 
     In some embodiments, the graphical representation includes a graphical element indicating a type of the workout. 
     In some embodiments, the graphical representation includes a graphical element indicating weather data associated with the workout. 
     In some embodiments, the graphical representation includes a graphical element of a first goal metric and wherein the first goal metric is a number of calories burned or a measurement of activity. 
     In some embodiments, the graphical representation includes a graphical element for a first workout metric for the completed workout and the first workout metric is selected from the group consisting of a pace, a distance, a time, a number of calories burned, and a heart rate. 
     In some embodiments, the graphical representation includes a graphical element of a second workout metric for the workout different than the first workout metric and the second workout metric is selected from the group consisting of a pace, a distance, a time, a calorie value, and a heart rate. 
     In some embodiments, receiving the workout summary occurs after receiving the first user input selecting the notification. 
     In some embodiments, the graphical representation of the activity summary includes an affordance for contacting the first contact and the processing unit  1506  is further configured to receive (e.g., with receiving unit  1510 ) a second user input indicating selection of the affordance. The processing unit  1506  is further configured to, in response to receiving the second user input, enabling display (e.g., with display enabling unit  1508 ) of a messaging user interface configured to receive message input for the first contact on the portable electronic device. 
     In some embodiments, the messaging user interface includes a plurality of pre-defined messages, and wherein at least one of the pre-defined messages is based on type of the current workout. 
     In some embodiments, the messaging user interface includes a plurality of pre-defined messages and at least one of the pre-defined messages is based on the workout summary data. 
       FIGS.  16 A- 16 J  illustrate exemplary user interfaces navigating and sharing activity data, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIG.  17   . 
       FIG.  16 A  illustrates portable electronic device  1600 , such as the multifunction electronic device described above with respect to  FIGS.  1 A- 1 B,  2 - 3 ,  4 A- 4 B, and  5 A- 5 H . Portable electronic device includes user interface  1602  for a workout or activity application, which may help track data relating to the physical activity, health, and/or biological state of a user of portable electronic device  1600 . Portable electronic device  1600  may be carried with or worn on a user. For example, portable electronic device  600  may be a smartphone. Portable electronic device  1600  may also be other types of devices and connect to other devices, such as portable electronic device  600  of  FIG.  6 A , to measure and collect workout and activity data. 
     User interface  1602  includes goal summary graphical element  1604  that represents the progress towards various activity goals for the day. Goal summary graphical element  1604  may be the same or similar as goal summary graphical element  604  described above with respect to  FIG.  6 A . Goal summary graphical elements  1606  may be smaller versions of goal graphical element  1604  with each one being associated with a day of the week. Goal graphical element  1606  associated with Saturday (labeled “S”) is the same as and updated with goal graphical element  1604  as the day&#39;s activities are measured and recorded. 
     User interface  1602  can include other graphical elements. For example, goal summary graphical element  1608  is a chronological representation of one of the goal metrics associated with goal summary graphical element  1604 . Additional information and graphical elements may be accessible by scrolling user interface  1602 . 
     User interface  1602  also includes affordances  1610 ,  1612 ,  1614 , and  1616  for selecting various modes of user interface  1602  or the application. Affordance  1610  corresponds to a goral history interface for accessing data about past activity goals, including past daily goal metrics. Affordance  1612  corresponds to a workout history interface for accessing data about past workouts, including workout metrics. Affordance  1614  corresponds to a sharing interface where activity and workout data can be shared with friends. 
       FIG.  16 B  depicts user interface  1617 , which is displayed in response to receiving user input selecting affordance  1616  of  FIG.  16 A  (e.g., via a touch on the touch sensitive screen). In  FIG.  16 B , user interface  1602  includes affordance  1618  for initializing the sharing of data and graphical element  1619 . In response to user input selecting affordance  1618 , graphical element  1619  transforms into S-shaped graphical element  1620  of  FIG.  16 C  via an animation to indicate that workout and activity sharing is initializing. 
     After the animation of graphical element  1619  of  FIG.  16 B  transforming into graphical element  1620  of  FIG.  16 C , a list of potential friends is loaded. For example, the list of friends depicted in  FIG.  16 D  may be the list of contacts  1622 ,  1624 ,  1626 ,  1628 ,  1630 ,  1632 ,  1634 , and  1636  from other applications, such as an email application, a contacts application, or a phone application. The list of contacts could also be loaded from a remote server or other device. 
     After retrieving the list of contacts, a determination is made of which contacts support the sharing of activity data, such as goal metrics or workout metrics. For example, a determination can be made as to whether each contact is associated with an electronic device that measures and/or records activity data. This association may be stored on a central server. With respect to  FIG.  16 D , the presence of selection indicators  1638 ,  1640 ,  1642 ,  1644 ,  1646 , and  1648  indicate that the associated contact supports the sharing of activity data. The absence of a selection indicator for contacts  1630  and  1634  indicate that those contacts do not support the sharing of activity data. 
       FIG.  16 E  depicts the selection of several of the selection indicators via, for example, touches on the screen where the selection indicators are displayed. In this example, the selection indicators are affordances for indicating that the user wants to share activity data with the associated contact. The selection is depicted as a check mark over the selection indicators. The entire contact regions could alternatively be the affordances for selecting the various contacts. Once the selection of contacts is completed, affordance  1650  can be selected via user input to complete the initialization procedure. In response to the selection of affordance  1650 , invitation messages may be sent to the selected contacts indicating that the user would like to be an activity friend with the contact. If the contact accepts the invitation, the user and the contact can share activity data as described below. 
       FIG.  16 F  depicts user interface  1602  in the sharing mode after initialization. After initialization has been completed once, this sharing mode may be entered in response to selection of affordance  1616  instead of entering the initialization mode. The sharing mode includes affordance  1662  for entering a sort interface for selecting a parameter for ordering the activity friends. Affordance  1660  allows a user to enter a messaging interface to message the activity friends. Affordance  1650  corresponds to the user and provides for the user to view the user&#39;s own activity data as will be seen by the activity friends. Affordances  1652 ,  1654 ,  1658 , and  1660  correspond to activity friends (i.e., contacts that either accepted the user&#39;s invitation to share activity data or contacts that sent an invitation that the user accepted) and provide for the user to view an activity friend&#39;s activity data. 
     For example, in response to user input selecting affordance  1652  of  FIG.  16 F , a determination is made as to whether activity data for Adam is available (e.g., locally or on a server). The presence of the actual activity data may be checked or other configuration or variables may be checked. If activity data is available, which indicates that Adam is not hiding activity data, a portion of a graphical representation of Adam&#39;s activity data is displayed, as depicted in  FIG.  16 G . Selection of affordance  1664  in  FIG.  16 G  returns to the activity friend listing in  FIG.  16 F . The graphical representation includes goal summary graphical elements  1666  and  1668  of  FIG.  16 G  and achievement graphical elements  1670  of  FIG.  16 H .  FIG.  16 H  also depicts affordances  1672 ,  1674 , and  1676  that allow the user to control activity sharing with the contact. For example, affordance  1672  may prevent further notifications regarding Adam&#39;s activities (e.g., notifications described with respect to  FIGS.  13 A- 13 F and  14   ) from being provided to the user. Affordance  1674  may prevent the user&#39;s activity data from being provided to Adam. This may be important, for example, if the relationship between the user and Adam is one that it is not appropriate for the user to share activity data with Adam but the user should be able to see Adam&#39;s activity data. One such example case is if the user is a trainer or healthcare provider that is monitoring Adam&#39;s activities but the user does not want to share their activities and make Adam feel as though he must compete with the user&#39;s activities. Affordance  1676  allows for the user to remove Adam as an activity friend. 
     Graphical element  1678  may be another affordance for performing other actions with respect to Adam, may be a graphical element depicting additional activity information, may be a graphical element providing information regarding the history or status of Adam as an activity friend (e.g., when the friendship began, how long data has been hidden), or may be another type of graphical element. 
     Similar graphical representations of activity data may be displayed in response to selecting other affordances for activity friends depicted in  FIG.  16 F  (and for affordance  1650  for the daily summary of the user&#39;s activity data) when activity data is available for the contact associated with the corresponding affordance. If, however, activity data is not available, either because activity data has not been received or because an activity friend has decided to hide their data from the user, an indication that activity data is not available in response to selection of the affordance. 
     For example, if affordance  1660  of  FIG.  16 F  is selected but activity data for Wendy is not available, then graphical element  1680  may be displayed indicating that the activity data is not available, as depicted in  FIG.  16 I . Alternative, the graphical element could also state that Wendy is hiding her activity data. 
     An activity friend interface, such as that of  FIG.  16 J , may be used to view and manage activity friends. For example, with reference to  FIG.  16 J , each potential activity friend and current activity friend may be listed. Graphical element  1682  is associated with a potential activity friend that has sent the user an invitation to share activity data. Affordances  1684  and  1686  can be used to accept or decline the invitation, respectively. Graphical elements  1688  and  1690  indicate activity friends with mutual sharing of activity data. Graphical element  1692  indicates an activity friend that the user is hiding activity data from. Graphical element  1694  indicates an activity friend that is hiding activity data from the user. Graphical elements  1682 ,  1688 ,  1690 ,  1692 , and  1694  may also be affordances that, when selected, provide additional information about activity friend (e.g., summary of activity data or other contact information). 
       FIG.  17    is a flow diagram illustrating a method for navigating and sharing activity data using a portable electronic device in accordance with some embodiments. Method  1700  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 ,  1600 ) with a display and, in some cases, a touch sensitive screen. Some operations in method  1700  are, optionally, combined, the order of some operations is, optionally, changed, and some operations are, optionally, omitted. 
     In block  1702 , contact information is displayed, including first contact information, for a first plurality of contacts, including a first contact, where the first contact information corresponds to the first contact. The contact information may be, for example, the name or a contact. The contract information could also include activity data, such as a goal metric. Graphical element  1652  of  FIG.  16 F  is an example of displaying contact information (e.g., the contact&#39;s name) for a first contact (the contact named “Adam”). 
     Variations of method  1700  may include, prior to the display of the contact information in block  1702 , generating the first plurality of contacts. This process may start by displaying an affordance for generating the first plurality of contact, such as affordance  1618  of  FIG.  16 B . In response to receiving user input selecting the affordance, a second plurality of contacts are retrieved. For example, the second plurality of contacts may be contacts from an email application, a phone application, a contact application, a database, or other source. The second plurality of contacts can be retrieved from a source locally or remotely. The second plurality of contacts includes the first contact and a second contact. 
     Next a determination is made whether an electronic device associated with the second contact supports sharing of activity data. This determination may be made in several manners. For example, a determination can be made as to whether an electronic device associated with the second contact can measure and/or record activity data. Local or remote databases may be queried to make this determination. In accordance with a determination that the second contact is not associated with an electronic device that supports sharing of activity data, the second contact is excluded from the first plurality of contacts. For example, the second contact may be excluded by preventing the second contact from being selected to be included in the first plurality of contacts. This is illustrated with respect to  FIG.  16 D  and described above. For example, if “Tina” is the second contact in  FIG.  16 D , Tina cannot be added to the first plurality of contacts displayed in  FIG.  16 F  because it has been determined that Tina is not associated with a device that can share activity data and a selection indicator has not been provided for Tina. In contrast, if the first contact is “Adam,” it has been determined that Adam is associated with an electronic device that supports sharing of activity data. Accordingly, selection indicator  1638  ( FIG.  16 D ) is provided for Adam so that a user may add Adam to the first plurality of contacts. 
     Variations of method  1700  may include sorting the first plurality of contacts for display. An affordance for a sort interface may be displayed and selected via a user input (e.g., affordance  1662  of  FIG.  16 F ). The sort interface may provide for receipt of user input that indicates a parameter for sorting the first plurality of contacts. For example, contact information (e.g., name) or activity data (e.g., goal metrics or workout metrics) may also be selected as the sort parameter. In response to a selection of a parameter, the first plurality of contacts are sorted based on the selected parameter to generate a sorted first plurality of contacts and the display of the contact information is based on the sort first plurality of contacts. 
     In block  1704 , first user input indicating a selection of the first contact is received. For example, the first user input may be received via a touch sensitive screen or other form of input. With reference to  FIG.  16 F , graphical element  1652  may also be an affordance that is selectable via the touch sensitive screen of portable electronic device  1600 . In this example, the first contact is selected via a user touch on the touch screen where graphical element  1652  is displayed. 
     In block  1706 , in response to receiving the first user input, a determination is made whether the portable electronic device has access to activity data associated with the first contact. This determination may be carried out in various manners. For example, one or more processors of the portable electronic device may check local memory for activity data associated with the first contact. A database of contact information that includes a flag or other configuration data may also indicate whether activity data is available for the first contact. As another example, a remote server or an electronic device associated with the contact can be checked. The determination may also check for whether there is an indication available that the first contact is hiding their activity data. 
     In block  1708 , in accordance with a determination that the portable electronic device has access to activity data associated with the first contact, displaying a portion of a graphical representation of the activity data. The graphical representation of the activity data may be similar to the graphical representations of activity, goal, and workout data previously described. For example, an example graphical representation for the first contact “Adam” of  FIG.  16 F  is depicted in  FIGS.  16 G and  16 H . 
     In addition to displaying the graphical representation for activity data of the first contact, other data and/or affordances may be displayed. For example, an affordance for hiding activity data from the first contact may be included (e.g., affordance  1674  of  FIG.  16 H ). In response to receiving user input selecting this affordance, an indication may be stored that prevents sending of the user&#39;s activity data to the contact. 
     As another example, an affordance for muting future notifications regarding activities from the first contact may be displayed (e.g., affordance  1672  of  FIG.  16 H ). In response to receiving user input selecting this affordance, future notifications regarding the first contact&#39;s activities or activity data will not be presented to the user. 
     As another example, an affordance for removing the first contact from the first plurality of contacts may be displayed (e.g., affordance  1676  of  FIG.  16 H ). In response to receiving user input selecting this affordance, the first contact is removed from the first plurality of contacts. Removing the first contact from the first plurality of contacts does not necessarily affect the first contact&#39;s presence in the second plurality of contacts. 
     In block  1710 , in accordance with a determination that the electronic device does not have access to activity data associated with the first contact, displaying a graphical element indicating that activity data is not available for the first contact. An example of this display is depicted in  FIG.  16 I . As another example, the graphical element indicating that activity data is not available may also indicate that the first contact is hiding activity data. 
     In some variations of method  1700 , in response to receiving user input selecting an affordance for a friend control interface, display of the contact information is replaced with display of a graphical representation of summary status data, such as depicted  FIG.  16 J . The graphical representation of the summary data includes a hiding portion, an invitation portion, and a sharing portion. The hiding portion includes contact information for a set of contacts that are hiding activity data. The invitation portion includes contact information for a set of contacts from which a notification has been received indicating an offer to share activity data. The sharing portion includes contact information for a set of contacts that are sharing activity data. 
     In accordance with some embodiments,  FIG.  18    shows an exemplary functional block diagram of an electronic device  1800  configured in accordance with the principles of the various described embodiments. In accordance with some embodiments, the functional blocks of electronic device  1800  are configured to perform the techniques described above. The functional blocks of the device  1800  are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG.  18    are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG.  18   , an electronic device  1800  includes a display unit  1802  configured to display a graphic user interface, a touch-sensitive surface unit  1804  configured to receive contacts (i.e., touches) and a processing unit  1806  coupled to the display unit  1802  and the touch-sensitive surface unit  1804 . In some embodiments, the processing unit  1806  includes a display enabling unit  1808 , receiving unit  1810 , and a determining unit  1812  and, optionally, a retrieving unit  1814 , a sorting unit  1816 , a storing unit  1818 , a removing unit  1820 , an excluding unit  1822 , and a sending unit  1824 . 
     The processing unit  1806  is configured to enable display (e.g., with display enabling unit  1808 ) of contact information, including first contact information, for a first plurality of contacts, including a first contact, where the first contact information corresponds to the first contact. The processing unit  1806  is further configured to receive (e.g., with receiving unit  1812 ) first user input indicating a selection of the first contact. The processing unit  1806  is further configured to, in response to receiving the first user input, determine (e.g., with determining unit  1812 ) whether the portable electronic device has access to activity data associated with the first contact. 
     The processing unit  1806  is configured to, in accordance with a determination that the portable electronic device has access to activity data associated with the first contact, enable display (e.g., with display enabling unit  1808 ) of a portion of a graphical representation of the activity data. 
     The processing unit  1806  is configured to, in accordance with a determination that the electronic device does not have access to activity data associated with the first contact, enable display (e.g., with display enabling unit  1808 ) of a graphical element indicating that activity data is not available for the first contact. 
     In some embodiments, before displaying the contact information, the processing unit  1806  is configured to enable display (e.g., with display enabling unit  1808 ) of a first affordance for generating the first plurality of contacts and receive (e.g., with receiving unit  1812 ) second user input indicating selection of the first affordance. The processing unit  1806  is further configured to, in response to receiving the second user input, retrieve (e.g., with retrieving unit  1814 ) a second plurality of contacts, where the second plurality of contacts includes the first contact and a second contact. The processing unit  1806  is further configured to determine (e.g., with determining unit  1812 ) whether an electronic device associated with the second contact of a second plurality of contacts supports sharing of activity data. The processing unit  1806  is further configured to, in accordance with a determination that the second contact is not associated with an electronic device that supports sharing of activity data, excluding the second contact from the first plurality of contacts. The processing unit  1806  is further configured to determine (e.g., with determining unit  1812 ) whether an electronic device associated with the first contact supports sharing of activity data. The processing unit  1806  is further configured to, in accordance with a determination that the electronic device associated with the first contact supports sharing of activity data, add (e.g., with adding unit  1818 ) the first contact to the first plurality of contacts. 
     In some embodiments, the processing unit  1806  is further configured to determine (e.g., with determining unit  1812 ) whether the electronic device associated with the first contact supports sharing of activity data includes determining whether the electronic device is capable of measuring activity data. 
     In some embodiments, the processing unit  1806  is configured to receive (e.g., with receiving unit  1812 ) user input selecting an affordance for a sort interface and, in response to receiving the user input selecting the affordance for the sort interface, enable display (e.g., with display enabling unit  1808 ) of the sort interface. The processing unit  1806  is configured to, while displaying the sort user interface, receive (e.g., with receiving unit  1812 ) a third user input corresponding to a parameter by which to sort the first plurality of contacts and, in response to receiving the third user input, sort (e.g., with sorting unit  1818 ) the first plurality of contacts to generate a sorted first plurality of contacts based on the parameter, where display of the contact information is based on the sorted first plurality of contacts. 
     In some embodiments, the graphical representation includes a second affordance indicating that activity data should not be shared with the first contact and the processing unit  1806  is further configured to, while displaying the second affordance, receive (e.g., with receiving unit  1812 ) a fourth user input indicating selection of the first affordance. The processing unit  1806  is further configured to, in response to receiving the fourth user input, store (e.g., with storing unit  1818 ) data indicating that activity data should not be sent to the first contact. 
     In some embodiments, the graphical representation includes a third affordance indicating completed workouts of the first contact should not generate a message on the portable electronic device and the processing unit  1806  is further configured to, while displaying the third affordance, receive (e.g., with receiving unit  1812 ) a fifth user input indicating selection of the third affordance and, in response to receiving the fifth user input, store (e.g. with storing unit  1818 ) data indicating that a notification processed in response to the first contact completing a workout. 
     In some embodiments, the processing unit  1806  is configured to, in accordance with a determination that the portable electronic device does not have access to activity data associated with the first contact, enable display (e.g., with display enabling unit  1808 ) an indication that the first contact is hiding activity data. 
     In some embodiments, the graphical representation includes a fourth affordance indicating the first contact should be removed from the first plurality of contacts and the processing unit  1806  is further configured to, while displaying the fourth affordance, receive (e.g., with receiving unit  1812 ) a sixth user input indicating selection of the fourth affordance. The processing unit  1806  is further configured to, in response to receiving the sixth user input, remove (e.g., with removing unit  1820 ) the first contact from the first plurality of contacts while maintaining the first contact in the second plurality of contacts. 
     In some embodiments, the processing unit  1806  is further configured to enable display (e.g., with display enabling unit  1808 ) of a fifth affordance for displaying summary status data for the first plurality of contacts and to receive (e.g., with receiving unit  1812 ) a seventh user input selecting the fifth affordance. The processing unit  1806  is further configured to, in response to receiving the seventh user input, enable the replacing of display (e.g., with display enabling unit  1808 ) of the contact information with display of a graphical representation of the summary status data, where the graphical representation of the summary data includes a hiding portion, an invitation portion, and a sharing portion, where the hiding portion includes contact information for a set of contacts that are hiding activity data, where the invitation portion includes contact information for a set of contacts from which a notification has been received indicating an offer to share activity data, and where the sharing portion includes contact information for a set of contact that are sharing activity data. 
     In some embodiments, the processing unit  1806  is further configured to receive (e.g., with receiving unit  1812 ) from an external electronic device paired with the portable electronic device, an indication that a user workout is completed and receive (e.g., with receiving unit  1812 ), from the external electronic device, data for the user workout; and send (e.g., with sending unit  1824 ) the data to at least one of the first plurality of contacts. 
       FIGS.  19 A- 19 D  illustrate exemplary user interfaces for viewing and navigating workout data in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIG.  20   . 
       FIG.  19 A  depicts street map  1900  on portable electronic device  1600 . While map  1900  is depicted as a two-dimensional map, three-dimensional maps could also be used. 
     The portable electronic device receives workout data that includes position-dependent workout metrics for a workout. The locations of the workout data coincide with the locations in map  1900 . The workout data may include data for multiple segments of the workout, such as multiple laps of a run or bike loop or multiple swimming laps. The workout data may be received from an external electronic device, such as a workout monitor, or may be measured from sensors included within the portable electronic device. 
       FIG.  19 B  depicts workout segments  1902 ,  1904 , and  1906  stacked in a three-dimensional stack on map  1900 . Workout segments  1902 ,  1904 , and  1906  are pattern-coded based on the position-dependent data in the workout data. For example, the pattern coding may correspond to a corresponding workout pace at the location on the map. Other coding, such as color, may be used instead of pattern coding. 
     Affordance  1901  allows a user to share displayed workout information with a contact. In response to user input selecting affordance  1901 , a messaging interface may be displayed that allows the user to include additional text and to select a recipient. The data and information necessary to generate the display then may be transmitted to the recipient. Alternatively, an image capture of the display may be transmitted. 
       FIG.  19 C  depicts graph  1908  representing data associated with workout segments  1902 ,  1904 , and  1906 . Graph  1908  includes curve  1910  that represents data associated with the workout segments. For example, the x-axis may be distance and the y-axis is elevation. Other values could also be used for the axes, such as time, pace, stroke (in the case of a swim workout), heart rate, and other parameters. Additionally, curve  1910  may be color-coded or have other coding to indicate additional information, such as pace. The coloring or other coding may coordinate with or be different than the coloring or other coding of the workout segments. 
       FIG.  19 D  depicts selection indicator  1912  that selects a point or portion of curve  1910 . In response to receiving the user input specifying the position for selection indicator  1912 , selection marker  1914  and graphical element  1916  are displayed on map  1900  based on the location in one of the workout segments that correspond to selection market  1914 . Graphical element  1916  may include workout metrics associated with the workout for the selected location. 
       FIG.  20    is a flow diagram illustrating a method  2000  for viewing and navigating workout data using a portable electronic device in accordance with some embodiments. Method  2000  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 ,  1600 ) with a display. Some operations in method  2000  are, optionally, combined, the order of some operations is, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  2000  provides an intuitive way for reviewing workout data. The method reduces the cognitive burden on a user for reviewing workout data, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to review workout data faster and more efficiently conserves power and increases the time between battery charges. 
     In block  2002 , first workout data for a first segment of a multi-segment workout route is received. The workout data may be received from sensors of the device, from sensors on an external device, such as an exercise monitor, or from a remote source. 
     The multi-segment workout route can be any number of different types of workouts. For example, in the case of a running or cycling workout, each segment of the multi-segment workout may be one loop of a route (e.g., each of workout segments  1902 ,  1904 , and  1906  of  FIG.  19 B ). As another example, in a swimming workout, each segment may be one lap of a pool or a lap of a route in a body of water. 
     The first workout data includes a plurality of locations for the multi-segment workout route and a plurality of workout metrics associated with the plurality of locations. For example, each segment of the multi-segment workout route may have one or more workout metrics, such as speed, pace, or heart rate, associated with each of a plurality of locations along the route (e.g., every 1 m, 3 m, 10 m, etc. or the locations could be recorded based on a time period, such as recording a location every 1 s, 5 s, 10 s, etc.). In other words, the workout data includes position-dependent workout metric data for the segment. 
     In block  2004 , second workout data for a second segment of the multi-segment workout route is received. The second workout data is similar to the first workout data received in block  2002 , except it is for a different segment. 
     In block  2006 , a first graphical representation of the first workout data and a second graphical representation of the second workout data are displayed on a map. The map may be a two-dimensional or three-dimensional map. The first and second graphical representations are displayed in a three-dimensional stack, wherein the appearance of the first graphical representation is based on the plurality of workout metric of the first workout data and the second graphical representation is based on the plurality of workout metrics of the second workout data. For example, the appearance of the first graphical representation and the second graphical representation may be color-coded or otherwise coded based on the workout metrics at each point along the segment. An example of this is depicted in  FIG.  19 B . The appearance of the segments may be coded according to any of the workout metrics, such as pace or heart rate. 
     In variations of method  2000 , a two-dimensional graph of the first workout data and the second workout data is displayed with the first and second graphical representations. This is depicted in  FIG.  19 C  that includes graph  1908  with curve  1910  showing the elevation of the workout segments. In some variations, the two-dimensional graph includes an indicator of a location on one of the workout segments. The corresponding location of the corresponding segment may be marked in the three-dimensional stack of the graphical representations of the workout segments and additional workout metrics may be displayed for the location. This is illustrated in  FIG.  19 D  where indicator  1912  on graph  1908  corresponds to the location on segment  1904  indicated by indicator  1914 . Graphical element  1916  provides additional workout metrics for the work at the location indicated by indicators  1912  and  1914 . 
     In variations of method  2000 , an affordance to sharing the displayed workout data is provided. In response to user input selecting the affordance, a messaging interface may be displayed that allows the user to select a recipient and add additional text. Then, the data and information necessary to generate the display or an image capture of the display is transmitted to the recipient along with any text that the user entered. 
     In accordance with some embodiments,  FIG.  21    shows an exemplary functional block diagram of an electronic device  2100  configured in accordance with the principles of the various described embodiments. In accordance with some embodiments, the functional blocks of electronic device  2100  are configured to perform the techniques described above. The functional blocks of the device  2100  are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG.  21    are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG.  21   , an electronic device  2100  includes a display unit  2102  configured to display a graphic user interface, a touch-sensitive surface unit  2104  configured to receive contacts (i.e., touches), optionally a pressure-sensitive surface unit  2118 , and a processing unit  2106  coupled to the display unit  2102  and the touch-sensitive surface unit  2104 . In some embodiments, the processing unit  2106  includes a display enabling unit  2108  and receiving unit  2110 . 
     The processing unit  2106  is configured to: receive (e.g., with receiving unit  2108 ) first workout data for a first segment of a multi-segment workout route, where the first workout data includes a plurality of locations for the multi-segment workout route and a plurality of workout metrics associated with the plurality of locations; receive (e.g., with receiving unit  2108 ) second workout data for a second segment of the multi-segment workout route, where the second workout data includes a plurality of locations for the multi-segment workout route and a plurality of workout metrics associated with the plurality of locations; and enable display (e.g., with display enabling unit  2108 ) of a first graphical representation of the first workout data and a second graphical representation of the second workout data over a map, where the first and second graphical representations are displayed in a three-dimensional stack, where the appearance of the first graphical representation is based on the plurality of workout metrics of the first workout data and the second graphical representation is based on the plurality of workout metrics of the second workout data. 
     In some embodiments, the processing unit  2106  is further configured to enable display (e.g., with display enabling unit  2108 ) of a two-dimensional graph of the first workout data and the second workout data with the display of the first graphical representation and the second graphical representation. 
     In some embodiments, the processing unit  2106  is further configured to enable display (e.g., with display enabling unit  2108 ) of a first indicator on the two-dimensional graph for a portion of the first workout data or a portion of the second workout data enable display (e.g., with display enabling unit  2108 ) of a second indicator on the display of the first workout data or the second workout data, where the first indicator and second indicator correspond to the same portion of the first workout data or the second workout data. 
     In some embodiments, the two-dimensional graph includes an indication of an elevation for the first workout data and the second workout data. 
     In some embodiments, the first graphical representation has a position-dependent color based on a position-dependent workout metric from the first workout data and the second graphical representation has a position-dependent color based on the position-dependent workout metric from the second workout data. 
     In some embodiments, the position-dependent workout metric is a workout pace or a swim stroke. 
     In some embodiments, the processing unit  2106  is further configured to enable display (e.g., with display enabling unit  2108 ) of concurrently with the first graphical representation and the second graphical representation on the map an affordance for sharing an image of the display of the first graphical representation and the second graphical representation on the map. 
       FIGS.  22 A- 22 F  illustrate exemplary user interfaces for pausing a workout and preventing inadvertent activation of other functions on the portable electronic device in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIG.  23   . 
     A workout may be started on the portable electronic device by a user selecting from a plurality of workout types and providing any additional information need to a specific workout type. For example, if a swimming workout type is selected, the user may also need to specify whether the swim workout is in a pool or open water. Alternatively, these may be separated out as different types of workouts. In the case of a pool swim workout, the user may need to specify the length of the pool. Other example workout types include running, cycling, wheelchair, rowing, and elliptical. 
     Once a workout is selected and running, the portable electronic device may turn off its display to conserve battery power. However, the device may still process touch inputs on the touch screen even with the display turned off. Specifically, the touch screen may not only detect touch inputs, but it may also detect characteristic intensity of the touches, as described above. The device is then configured to respond differently depending whether the received touch has a characteristic intensity that exceeds a threshold. This may be useful, for example, when the touch interface has the potential to receive inadvertent inputs that could be interpreted as a touch. In the case of a swimming workout, water running over the touch screen may be interpreted at a touch on the touch screen. This can cause inadvertent actions to occur on the portable electronic device, including ending the workout, sending messages, or dismissing notifications. By requiring a touch to have a characteristic intensity that exceeds a threshold intensity before further interaction may occur, the possibility of inadvertent actions taking place based on inadvertent touches is greatly reduced. 
       FIG.  22 A  depicts user interface  2200  that includes lock indication  2002  indicating that the current workout is in the locked state. User interface  2200  also includes: workout metric graphical element  2004 , which is displaying the time elapsed for the workout; goal metric graphical elements  2006  and  2008 , where goal metric graphical element  2008  indicates progress towards a goal represented by goal metric graphical element  2008 ; and workout metric graphical element  2010 , which represents the total calories burned so far for the workout.  FIG.  22 A  may occur in response to a touch on the touch sensitive screen that has a characteristic intensity that does not exceed a threshold while the ongoing workout is in a locked state. 
     A workout is in a locked state if it will not respond normally to touches on the touch screen that do not have characteristic intensities that exceed an intensity threshold. For example, user interface  2200  of  FIG.  22 A  would normally allow a user to further interface with the display through other gestures on the touch screen. When the workout is in a locked state, however, further touches on user interface  2200  may have limited effect, as described below. 
       FIG.  22 B  depicts use interface  2200  that includes indication  2212  indicating that the workout is in a locked state and a force touch (e.g., a touch with a characteristic intensity greater than a threshold) should be used to pause the workout.  FIG.  22 B  may appear after another touch is detected on user interface  2200  of  FIG.  22 A  that has a characteristic intensity that does not exceed an intensity threshold. In some cases, when a workout is in a locked state, the displays in  FIGS.  22 A and  22 B  are the only displays that are accessible to a user without first performing a touch with a characteristic intensity greater than a threshold intensity. 
       FIG.  22 C  depicts user interface  2200  in response to portable electronic device  600  receiving a touch input with a characteristic intensity that exceeds a threshold intensity. In  FIG.  22 C , user interface  2200  includes a pause indicator  2216 , workout summary graphical element  2214 , and indicator  2218  indicating how to resume the workout. Workout summary graphical element  2214  may be further interacted with to reveal additional workout data. In response to user interface  2200  receiving a touch with a characteristic intensity that exceed a threshold intensity, the workout may resume in the locked state and the user interface  2200  may return to a state of limited response to low intensity touches, as described with respect to  FIGS.  22 A and  22 B . 
     In response to portable electronic device  600  in  FIG.  22 C  receiving user input, such as a scroll or swipe input,  FIG.  22 D  depicts user interface  2200  with graphical elements  2220 ,  2222 ,  2224  providing, respectively, the workout state, a graphical representation of a potential action, and instructions for executing the potential action. In response to user interface  2200  receiving a touch with a characteristic intensity that exceed a threshold intensity, the workout may end. 
     In response to portable electronic device  600  in  FIG.  22 D  receiving further user input, such as a scroll or swipe input,  FIG.  22 E  depicts user interface  2200  with graphical elements  2226 ,  2228 ,  2230  providing, respectively, the workout state, a graphical representation of a potential action, and instructions for executing the potential action. In response to user interface  2200  receiving a touch with a characteristic intensity that exceed a threshold intensity, the workout may be resumed in the unlocked state.  FIG.  22 F  depicts user interface  2200  as described in  FIG.  22 A , except that the workout is ongoing in the unlocked state, such as would be the result from user input with a sufficient characteristic intensity being received in  FIG.  22 E . A touch input with a characteristic intensity that exceeds a threshold on user interface  2200  may display an interface that allows the workout to be locked again. 
       FIG.  23    is a flow diagram illustrating a method  2300  for pausing a workout and preventing inadvertent activation of the other functions on a portable electronic device during a workout in accordance with some embodiments. Method  2300  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 ,  1600 ) with a display and a touch sensitive screen that is also pressure sensitive. Some operations in method  2300  are, optionally, combined, the order of some operations are, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  2300  provides an intuitive way for pausing a workout application and preventing inadvertent activations or deactivations of functions on the portable electronic device during a workout. The method reduces the cognitive burden on a user for pausing a workout application and preventing inadvertent activations or deactivations of functions on the portable electronic device during a workout, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to pause a workout application and prevent inadvertent activations or deactivations of functions on the portable electronic device during a workout faster and more efficiently conserves power and increases the time between battery charges. 
     In block  2302 , an indication to start a workout is received. A workout may be started on the portable electronic device by a user selecting from a plurality of workout types and providing any additional information need to a specific workout type. For example, if a swimming workout type is selected, the user may also need to specify whether the swim workout is in a pool or open water. Alternatively, these may be separated out as different types of workouts. In the case of a pool swim workout, the user may need to specify the length of the pool. Other example workout types include running, cycling, wheelchair, rowing, and elliptical. 
     In block  2304 , in response to receiving the indication start a workout, a workout application of the portable electronic device starts recording a plurality of workout metrics for the workout. For example, workout metrics may include speed, pace, swim stroke, heart rate, distance, and time. 
     In block  2306 , a first user input is received on the pressure sensitive touch screen while recording the plurality of workout metrics. The first user input has a characteristic intensity. Blocks  2308 - 2314  are in response to receiving the first user input. The first user input may be received while the display is powered off or while a user interface (e.g., user interface  2200  of  FIG.  22 A ) is displayed on the display. 
     In block  2308 , a determination is made as to (1) whether the workout application is in a locked state and (2) whether the characteristic intensity exceeds a threshold intensity. The determination of whether the workout application is in the locked stated may be made based on status bits associated with the workout application or by some other means. 
     In block  2310 , in accordance with a determination that the workout application is in a locked state and the first user input does not exceed the threshold intensity, the workout application continues to record the plurality of workout metrics for the workout. In other words, the touch first input does not affect the workout application&#39;s operation. Subsequent touches of this type while the workout application is in the same state would produce the same result. In some variations, in accordance with these determinations, the workout application may display a limited user interface, as depicted in  FIGS.  22 A and  22 B . 
     In block  2312 , in accordance with a determination that the workout application is in a locked state and the first user input exceeds the threshold intensity, the recording with the workout application is stopped (e.g., paused). In addition to pausing the recording of the plurality of workout metrics, a pause screen may also be displayed, as depicted in  FIG.  22 C . User input received while displaying the pause screen may present additional workout metrics or information for the workout. 
     In some variations of method  2300 , after stopping the recording with the workout application, a third user input is received on the pressure sensitive. In response to receiving the third user input, a determination is made as to whether the third user input has a characteristic intensity exceeds a threshold intensity. In accordance with a determination that the third user input does not exceed the threshold intensity and in response to the second user input, a workout metric for the workout is displayed. In accordance with a determination that the third user input exceeds the threshold intensity, recording the workout metrics with the workout application is resumed. 
     In some variations of method  2300 , after stopping the recording with the workout application and while displaying a resume user interface, a fourth user input to resume the recording with the workout application and changing the workout application to an unlocked state is received, as described with respect to  FIG.  22 E  above. In response to receiving the fourth user input, the recording with the workout application is resumed. Data is also stored indicating the workout application is in an unlocked state. 
     In block  2314 , in accordance with a determination that the workout application is in an unlocked state, processing the first user input according to the workout application. This is normal operation of the workout application. 
     In some variations of method  2300 , after completion of the workout, data is stored associating a type of the completed workout with an indication of a locked or unlocked state based on whether the state of the workout application when the workout ended. 
     In some variations of method  2300 , a fifth user input is received and processed via a hardware input of the portable electronic device while recording the plurality of workout metrics and while the workout application is in the locked state. In other words, hardware inputs are still processed normally even when the workout is in the locked state. 
       FIGS.  22 A- 22 F and  23    and the associated description, describe an embodiment of an input-intensity-to-unlock system. With this type of system having an input-intensity-sensitive and touch-sensitive screen, a device can have two states and moving from one state to the other state may occur in response to a touch on the screen having a characteristic intensity that is greater than an intensity threshold. For example, a first state of the device may be a limited or a locked state while the second state may allow for full functionality. While the device is in the first state, in response to receiving a touch having a characteristic intensity that does not exceed the intensity threshold, no action is taken or an action of a limited set of available actions is taken (e.g., an action that does not require that the characteristic intensity meet an intensity threshold). The limited set of available actions is less than the full functionality of the device available in the second state and may include, for example, displaying instruction for switching the device into the other state, displaying an indication of the state the device is in, displaying summary information, or other limited functions. While the device is in the first state, in response to receiving a touch that exceeds the threshold intensity, the device is switched to the second state that provides full or near full functionality (e.g., when the device is a locked device, the device is switched to an unlocked state). In some embodiments, changing state (e.g., unlocking) requires, in addition to requiring an input intensity greater than the intensity threshold, that one or more additional criterion be met (e.g., that the input includes a required component of motion or that the input includes two or more contacts). Stated another way, the device may receive an input having a characteristic intensity; determine whether the input meets state change criteria, where the state change criteria includes a criterion that is met when the characteristic intensity of the input exceeds an intensity threshold; in response to a determination that the state change criteria are met, changing an access state of the device; and in response to a determination that the state change criteria are not met, processing the input as a non-state changing function (e.g., as a touch input that does not result in state change) or forgoing any further action in response to the input. 
     In accordance with some embodiments,  FIG.  24    shows an exemplary functional block diagram of an electronic device  2400  configured in accordance with the principles of the various described embodiments. In accordance with some embodiments, the functional blocks of electronic device  2400  are configured to perform the techniques described above. The functional blocks of the device  2400  are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG.  24    are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG.  24   , an electronic device  2400  includes a display unit  2402  configured to display a graphic user interface, a touch-sensitive surface unit  2404  configured to receive contacts (i.e., touches), a pressure-sensitive surface unit  2418 , and a processing unit  2406  coupled to the display unit  2402  and the touch-sensitive surface unit  2404 . In some embodiments, the processing unit  2406  includes a display enabling unit  2408 , receiving unit  2410 , a determining unit  2412 , a recording unit  2414 , and, optionally, a storing unit  2416 . 
     The processing unit  2406  is configured to: receive (e.g., with receiving unit  2410 ) an indication to start a workout; in response to receiving the indication start a workout, record (e.g., with recording unit  2414 ) a plurality of workout metrics for the workout; receive (e.g., with receiving unit  2410 ) a first user input on the pressure sensitive touch screen while recording the plurality of workout metrics, wherein the first user input has a characteristic intensity; and in response to receiving the first user input, determine (e.g., with determining unit  2412 ) whether the workout application is in a locked state and whether the characteristic intensity exceeds a threshold intensity. 
     The processing unit  2406  is configured to, in accordance with a determination that the workout application is in a locked state and the first user input does not exceed the threshold intensity, continue to record (e.g., with recording unit  2414 ) the plurality of workout metrics for the workout; in accordance with a determination that the workout application is in a locked state and the first user input exceeds the threshold intensity, stop the recording (e.g., with recording unit  2414 ); and in accordance with a determination that the workout application is in an unlocked state, process (e.g., with input processing unit  2422 ) the first user input according to the workout application. 
     In some embodiments, processing unit  2402  is further configured to, in accordance with a determination that the workout application is in a locked state and the first user input exceeds the threshold intensity, enable display (e.g., with display enabling unit  2408 ) of a pause screen for the workout. 
     In some embodiments, processing unit  2402  is further configured to, in response to receiving a second user input while the recording is stopped, enabling the scrolling (e.g., with display enabling unit  2408 ) of a display of a workout metric for the workout. 
     In some embodiments, processing unit  2402  is further configured to, after stopping the recording with the workout application, receive (e.g., with receiving unit  2410 ) a third user input on the pressure sensitive touch screen, wherein the third user input has a characteristic intensity. The processing unit  2406  is further configured to, in response to receiving the third user input: determine (e.g., with determining unit  2412 ) whether the characteristic intensity exceeds a threshold intensity and in accordance with a determination that the third user input does not exceed the threshold intensity and in response to the second user input, enabling display (e.g., with display of display enabling unit  2408 ) of a workout metric for the workout. The processing unit  2406  is further configured to, in accordance with a determination that the third user input exceeds the threshold intensity, resume (e.g., with recording unit  2414 ) the recording. 
     In some embodiments, processing unit  2402  is further configured to, after stopping the recording with the workout application and while displaying a resume user interface, receive (e.g., with receiving unit  2410 ) a fourth user input to resume the recording with the workout application and changing the workout application to an unlocked state and, in response to receiving the fourth user input, resume (e.g., with recording unit  2414 ) recording and store (e.g., with storing unit  2416 ) data indicating the workout application is in an unlocked state. 
     In some embodiments the workout is a swim workout. 
     In some embodiments, processing unit  2402  is further configured to, after completion of the workout, store (e.g., with storing unit  2416 ) data associating a type of the workout with an indication of a locked or unlocked state. 
     In some embodiments, determining whether the first user input exceeds a threshold pressure occurs while the display is off. 
     In some embodiments, processing unit  2402  is further configured to receive (e.g., with receiving unit  2410 ) a fifth user input via a hardware input of the portable electronic device while recording the plurality of workout metrics and while the workout application is in the locked state and process (e.g., with input processing unit  2422 ) the fourth user input. 
     The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated. 
     Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims. 
     As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the delivery to users of invitational content or any other content that may be of interest to them. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information. 
     The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. 
     The present disclosure further 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. For example, 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 should occur only after receiving the informed consent of the users. Additionally, such entities would take 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. 
     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 advertisement delivery 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. In another example, users can select not to provide location information for targeted content delivery services. In yet another example, users can select to not provide precise location information, but permit the transfer of location zone information. 
     Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content delivery services, or publically available information.

Metadata:
Filing Date: 20211101
Publication Date: 20230530
Grant Date: 20230530
Priority Date: 20160611
Inventors: WILLIAMS, ALED HYWEL
GRAHAM, DAVID CHANCE
WILSON, CHRISTOPHER
Assignee: APPLE INC
CPC Classifications: [{"code": "A63B2220/805", "inventive": false, "first": false, "tree": "[]"}, {"code": "A63B2230/06", "inventive": false, "first": false, "tree": "[]"}, {"code": "G16H50/30", "inventive": false, "first": false, "tree": "[]"}, {"code": "A63B2024/0068", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B5/11", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0485", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/0022", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B5/0022", "inventive": false, "first": false, "tree": "[]"}, {"code": "G16H40/67", "inventive": true, "first": false, "tree": "[]"}, {"code": "G16H20/30", "inventive": true, "first": false, "tree": "[]"}, {"code": "G16H40/67", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/1118", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06T11/60", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04808", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B5/6898", "inventive": true, "first": false, "tree": "[]"}, {"code": "G16H50/30", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B24/0084", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2220/807", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/0481", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06V40/23", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0481", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B71/0622", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0481", "inventive": true, "first": false, "tree": "[]"}, {"code": "G16H20/30", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0485", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2071/0691", "inventive": false, "first": false, "tree": "[]"}, {"code": "A63B24/0062", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/04845", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2230/75", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06T11/60", "inventive": true, "first": false, "tree": "[]"}, {"code": "G16H20/30", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2071/0655", "inventive": false, "first": false, "tree": "[]"}, {"code": "A63B2220/62", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B5/1118", "inventive": true, "first": true, "tree": "[]"}, {"code": "G16H50/30", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04845", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0485", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2220/12", "inventive": false, "first": false, "tree": "[]"}, {"code": "A63B2225/50", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B5/00", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/1118", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/0022", "inventive": true, "first": false, "tree": "[]"}, {"code": "G16H40/67", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2220/806", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/04817", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06T11/60", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2220/20", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B5/6898", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/6898", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2220/40", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06T11/60", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2225/50", "inventive": false, "first": false, "tree": "[]"}, {"code": "A63B2220/62", "inventive": false, "first": false, "tree": "[]"}, {"code": "A63B2220/20", "inventive": false, "first": false, "tree": "[]"}, {"code": "A63B2220/805", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B5/00", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2220/40", "inventive": false, "first": false, "tree": "[]"}, {"code": "G16H50/30", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06V40/23", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B24/0084", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2024/0068", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/0481", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0485", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B24/0062", "inventive": true, "first": true, "tree": "[]"}, {"code": "A63B2071/0691", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B5/11", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/6898", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2071/0655", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B5/0022", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2220/806", "inventive": false, "first": false, "tree": "[]"}, {"code": "A63B2220/12", "inventive": false, "first": false, "tree": "[]"}, {"code": "A63B2230/06", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/04845", "inventive": true, "first": false, "tree": "[]"}, {"code": "G16H20/30", "inventive": true, "first": false, "tree": "[]"}, {"code": "G16H40/67", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B71/0622", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2220/807", "inventive": false, "first": false, "tree": "[]"}, {"code": "A63B2230/75", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B5/1118", "inventive": true, "first": false, "tree": "[]"}]
Family ID: 59249040