PATENT DOCUMENT

Publication Number: US-10674942-B2
Application Number: US-201816144849-A
Country: US
Kind Code: B2

Title: Displaying user interfaces associated with physical activities

Abstract:
The present disclosure generally relates to user interfaces and more specifically to techniques for displaying user interfaces associated with physical activities. Exemplary user interfaces related to activity competitions are described. Exemplary user interfaces related to a friends list for activity sharing are described. Exemplary user interfaces associated with alerts presented to a user in response to automatically determining a boundary of a workout are described. Exemplary user interfaces associated with configuring a pace alert for a workout application are described.

Claims:
What is claimed is: 
     
       1. An electronic device, comprising:
 a display; 
 one or more processors; 
 one or more sensors; and 
 a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for:
 detecting, via the one or more sensors, activity data, wherein the activity data includes at least one or more of user standing data, user moving data, and user exercise data; and 
 in response to detecting the activity data:
 in accordance with a determination that the activity data satisfies first activity boundary alert criteria, wherein the first activity boundary alert criteria corresponds to a first predicted type of physical activity:
 displaying a first activity boundary alert including a first affordance; 
 receiving a first user input corresponding to selection of the first affordance; and 
 in response to receiving the first user input, initiating a first physical activity tracking function corresponding to the first predicted type of physical activity; and 
 
 in accordance with a determination that the activity data satisfies second activity boundary alert criteria, wherein the second activity boundary alert criteria corresponds to a second predicted type of physical activity, different from the first predicted type of physical activity:
 displaying a second activity boundary alert including a second affordance; 
 receiving a second user input corresponding to selection of the second affordance; and 
 in response to receiving the second user input, initiating a second physical activity tracking function corresponding to the second predicted type of physical activity, wherein the second physical activity tracking function is different from the first physical activity tracking function. 
 
 
 
 
     
     
       2. The electronic device of  claim 1 , wherein the one or more sensors includes one or more of an accelerometer, a global positioning system (GPS) sensor, a heart rate monitor, a clock, and a gyroscope. 
     
     
       3. The electronic device of  claim 1 , wherein the one or more programs further include instructions for:
 further in response to detecting the activity data:
 in accordance with a determination that the activity data does not satisfy the second activity boundary alert criteria, forgoing display of the second activity boundary alert. 
 
 
     
     
       4. The electronic device of  claim 1 , wherein the activity data is detected before a physical activity tracking function is active. 
     
     
       5. The electronic device of  claim 1 , wherein the first physical activity tracking function corresponding to the first activity boundary alert tracks activity data detected prior to displaying the first activity boundary alert. 
     
     
       6. The electronic device of  claim 1 , wherein the activity data was detected via a first sensor of the one or more sensors, the one or more programs further including instructions for:
 initiating the first physical activity tracking function corresponding to the first predicted type of physical activity corresponding to the first activity boundary alert by detecting second activity data via a second sensor, different from the first sensor, of the one or more sensors. 
 
     
     
       7. The electronic device of  claim 1 , wherein the first activity boundary alert corresponds to a third physical activity tracking function, and wherein the first activity boundary alert includes a third affordance, the one or more programs further including instructions for:
 receiving a third user input corresponding to a selection of the third affordance in the first activity boundary alert; 
 in response to receiving the third user input, displaying a first user interface including:
 a fourth affordance corresponding to a fourth physical activity tracking function different from the third physical activity tracking function; and 
 a fifth affordance corresponding to a fifth physical activity tracking function different from the third physical activity tracking function; and 
 while displaying the first user interface, receiving a fourth user input: 
 in accordance with the fourth user input corresponding to a selection of the fourth affordance in the first user interface, configuring the electronic device to track activity data detected after the selection of the fourth affordance using the fourth physical activity tracking function; and 
 in accordance with the fourth user input corresponding to a selection of the fifth affordance in the second user interface, configuring the electronic device to track activity data detected after the selection of the fifth affordance using the fifth physical activity tracking function. 
 
 
     
     
       8. The electronic device of  claim 1 , wherein the activity data is detected while an existing physical activity tracking function is active, and wherein the first activity boundary alert includes a sixth affordance, the one or more programs further including instructions for:
 receiving a fourth user input corresponding to a selection of the sixth affordance; and 
 in response to receiving the fourth user input:
 ending a current physical activity tracking function; and 
 storing activity data detected prior to receiving the fourth user input as a previous workout. 
 
 
     
     
       9. The electronic device of  claim 8 , wherein the first activity boundary alert includes a seventh affordance, the one or more programs further including instructions for:
 receiving a fifth user input corresponding to a selection of the seventh affordance; and 
 in response to receiving the fifth user input, pausing execution of the current physical activity tracking function. 
 
     
     
       10. The electronic device of  claim 9 , wherein the first activity boundary alert corresponds to a sixth physical activity tracking function, and wherein displaying the first activity boundary alert includes displaying an eighth affordance, the one or more programs further including instructions for:
 receiving a sixth user input corresponding to a selection of the eighth affordance; and 
 in response to receiving the sixth user input:
 initiating a process for ceasing execution of the sixth physical activity tracking function; and 
 displaying a second user interface including:
 a ninth affordance corresponding to a seventh physical activity tracking function different from the sixth physical activity tracking function, and 
 a tenth affordance corresponding to an eighth physical activity tracking function different from the sixth physical activity tracking function and the seventh physical activity tracking function; 
 
 
 receiving a seventh user input; 
 in accordance with the seventh user input corresponding to a selection of the ninth affordance in the second user interface, initiating the seventh physical activity tracking function; and 
 in accordance with the seventh user input corresponding to a selection of the tenth affordance in the second user interface, initiating the eighth physical activity tracking function. 
 
     
     
       11. The electronic device of  claim 10 , wherein the first activity boundary alert includes an eleventh affordance, and wherein the first physical activity tracking function corresponding to the first activity boundary alert is a ninth physical activity tracking function, the one or more programs further including instructions for:
 receiving an eighth user input corresponding to a selection of the eleventh affordance; and 
 in response to receiving the eighth user input, initiating ninth physical activity tracking function corresponding to the first activity boundary alert, wherein the ninth physical activity tracking function is different from the eighth physical activity tracking function. 
 
     
     
       12. The electronic device of  claim 11 , wherein the first affordance is highlighted as compared to the eleventh affordance. 
     
     
       13. The electronic device of  claim 1 , wherein the one or more programs further include instructions for:
 after displaying the first activity boundary alert and before a physical activity tracking function is active:
 displaying a third user interface including a scrollable list of affordances associated with physical activities; 
 receiving a ninth user input; 
 in accordance with a determination that the ninth user input is detected at a twelfth affordance in the scrollable list of affordances, launching the first physical activity tracking function corresponding to the first activity boundary alert; and 
 in accordance with a determination that the ninth user input is detected at a thirteenth affordance in the scrollable list of affordances, launching a physical activity tracking function (1) not corresponding to the first activity boundary alert and (2) different from the first physical activity tracking function corresponding to the first activity boundary alert. 
 
 
     
     
       14. The electronic device of  claim 13 , wherein the first physical activity tracking function corresponding to the first activity boundary alert is a tenth physical activity tracking function, the one or more programs further including instructions for:
 in accordance with a determination that the ninth user input is detected at a fourteenth affordance in the scrollable list of affordances, launching an eleventh physical activity tracking function corresponding to the first activity boundary alert, wherein the eleventh physical activity tracking function is different from the tenth physical activity tracking function, and wherein the eleventh physical activity tracking function corresponding to the first activity boundary alert tracks activity data detected after receiving the ninth user input. 
 
     
     
       15. The electronic device of  claim 1 , wherein the first activity boundary alert includes a first animated affordance representing the first predicted type of physical activity corresponding with the first activity boundary alert, and wherein the second activity boundary alert includes a second animated affordance representing the second predicted type of physical activity corresponding with the second activity boundary alert. 
     
     
       16. The electronic device of  claim 1 , wherein the activity data is detected while an existing physical activity tracking function is active. 
     
     
       17. The electronic device of  claim 1 , wherein the one or more programs further including instructions for:
 after a predetermined time has lapsed without initiating a physical activity tracking function corresponding to the first activity boundary alert, displaying a third activity boundary alert, wherein a physical activity tracking function corresponding to the third activity boundary alert tracks activity data detected prior to displaying the first activity boundary alert. 
 
     
     
       18. The electronic device of  claim 1 , wherein the first activity boundary alert includes first content, the one or more programs further including instructions for:
 after displaying the first activity boundary alert, displaying a fourth activity boundary alert including second content, wherein the second content is different from the first content. 
 
     
     
       19. A method, comprising:
 at an electronic device including a display and one or more sensors:
 detecting, via the one or more sensors, first activity data that satisfies first activity boundary alert criteria, wherein the first activity boundary alert criteria corresponds to a first predicted type of physical activity and the first activity data includes at least one or more of user standing data, user moving data, and user exercise data; 
 in response to detecting the first activity data:
 displaying a first activity boundary alert including a first affordance; 
 receiving a first user input corresponding to selection of the first affordance; and 
 in response to receiving the first user input, initiating a first physical activity tracking function corresponding to the first predicted type of physical activity; 
 
 detecting, via the one or more sensors, second activity data that satisfies second activity boundary alert criteria, wherein the second activity boundary alert criteria corresponds to a second predicted type of physical activity, different from the first predicted type of physical activity and the second activity data includes at least one or more of user standing data, user moving data, and user exercise data; and
 in response to detecting the second activity data:
 displaying a second activity boundary alert including a second affordance; 
 receiving a second user input corresponding to selection of the second affordance; and 
 in response to receiving the second user input, initiating a second physical activity tracking function corresponding to the second predicted type of physical activity, wherein the second physical activity tracking function is different from the first physical activity tracking function. 
 
 
 
 
     
     
       20. The method of  claim 19 , wherein the one or more sensors includes one or more of an accelerometer, a global positioning system (GPS) sensor, a heart rate monitor, a clock, and a gyroscope. 
     
     
       21. The method of  claim 19 , further comprising:
 in response to detecting the activity data: 
 in accordance with a determination that the activity data does not satisfy the second activity boundary alert criteria, forgoing display of the second activity boundary alert. 
 
     
     
       22. The method of  claim 19 , wherein the activity data is detected before a physical activity tracking function is active. 
     
     
       23. The method of  claim 19 , wherein the first physical activity tracking function corresponding to the first activity boundary alert tracks activity data detected prior to displaying the first activity boundary alert. 
     
     
       24. The method of  claim 19 , wherein the activity data was detected via a first sensor of the one or more sensors, the method further comprising:
 initiating the first physical activity tracking function corresponding to the first predicted type of physical activity corresponding to the first activity boundary alert by detecting second activity data via a second sensor, different from the first sensor, of the one or more sensors. 
 
     
     
       25. The method of  claim 19 , wherein the first activity boundary alert corresponds to a third physical activity tracking function, and wherein the first activity boundary alert includes a third affordance, the method further comprising:
 receiving a third user input corresponding to a selection of the third affordance in the first activity boundary alert; 
 in response to receiving the third user input, displaying a first user interface including:
 a fourth affordance corresponding to a fourth physical activity tracking function different from the third physical activity tracking function; and 
 a fifth affordance corresponding to a fifth physical activity tracking function different from the third physical activity tracking function; and 
 while displaying the first user interface, receiving a fourth user input: 
 in accordance with the fourth user input corresponding to a selection of the fourth affordance in the first user interface, configuring the electronic device to track activity data detected after the selection of the fourth affordance using the fourth physical activity tracking function; and 
 in accordance with the fourth user input corresponding to a selection of the fifth affordance in the second user interface, configuring the electronic device to track activity data detected after the selection of the fifth affordance using the fifth physical activity tracking function. 
 
 
     
     
       26. The method of  claim 19 , wherein the activity data is detected while an existing physical activity tracking function is active, and wherein the first activity boundary alert includes a sixth affordance, the method further comprising:
 receiving a fourth user input corresponding to a selection of the sixth affordance; and 
 in response to receiving the fourth user input:
 ending a current physical activity tracking function; and 
 storing activity data detected prior to receiving the fourth user input as a previous workout. 
 
 
     
     
       27. The method of  claim 26 , wherein the first activity boundary alert includes a seventh affordance, the method further comprising:
 receiving a fifth user input corresponding to a selection of the seventh affordance; and 
 in response to receiving the fifth user input, pausing execution of the current physical activity tracking function. 
 
     
     
       28. The method of  claim 27 , wherein the first activity boundary alert corresponds to a sixth physical activity tracking function, and wherein displaying the first activity boundary alert includes displaying an eighth affordance, the method further comprising:
 receiving a sixth user input corresponding to a selection of the eighth affordance; and 
 in response to receiving the sixth user input:
 initiating a process for ceasing execution of the sixth physical activity tracking function; and 
 displaying a second user interface including:
 a ninth affordance corresponding to a seventh physical activity tracking function different from the sixth physical activity tracking function, and 
 a tenth affordance corresponding to an eighth physical activity tracking function different from the sixth physical activity tracking function and the seventh physical activity tracking function; 
 
 
 receiving a seventh user input; 
 in accordance with the seventh user input corresponding to a selection of the ninth affordance in the second user interface, initiating the seventh physical activity tracking function; and 
 in accordance with the seventh user input corresponding to a selection of the tenth affordance in the second user interface, initiating the eighth physical activity tracking function. 
 
     
     
       29. The method of  claim 28 , wherein the first activity boundary alert includes an eleventh affordance, and wherein the first physical activity tracking function corresponding to the first activity boundary alert is a ninth physical activity tracking function, the method further comprising:
 receiving an eighth user input corresponding to a selection of the eleventh affordance; and 
 in response to receiving the eighth user input, initiating ninth physical activity tracking function corresponding to the first activity boundary alert, wherein the ninth physical activity tracking function is different from the eighth physical activity tracking function. 
 
     
     
       30. The method of  claim 29 , wherein the first affordance is highlighted as compared to the eleventh affordance. 
     
     
       31. The method of  claim 19 , further comprising:
 after displaying the first activity boundary alert and before a physical activity tracking function is active:
 displaying a third user interface including a scrollable list of affordances associated with physical activities; 
 receiving a ninth user input; 
 in accordance with a determination that the ninth user input is detected at a twelfth affordance in the scrollable list of affordances, launching the first physical activity tracking function corresponding to the first activity boundary alert; and 
 in accordance with a determination that the ninth user input is detected at a thirteenth affordance in the scrollable list of affordances, launching a physical activity tracking function (1) not corresponding to the first activity boundary alert and (2) different from the first physical activity tracking function corresponding to the first activity boundary alert. 
 
 
     
     
       32. The method of  claim 31 , wherein the first physical activity tracking function corresponding to the first activity boundary alert is an tenth physical activity tracking function, the method further comprising:
 in accordance with a determination that the ninth user input is detected at a fourteenth affordance in the scrollable list of affordances, launching an eleventh physical activity tracking function corresponding to the first activity boundary alert, wherein the eleventh physical activity tracking function is different from the tenth physical activity tracking function, and wherein the eleventh physical activity tracking function corresponding to the first activity boundary alert tracks activity data detected after receiving the ninth user input. 
 
     
     
       33. The method of  claim 19 , wherein the first activity boundary alert includes a first animated affordance representing the first predicted type of physical activity corresponding with the first activity boundary alert, and wherein the second activity boundary alert includes a second animated affordance representing the second predicted type of physical activity corresponding with the second activity boundary alert. 
     
     
       34. The method of  claim 19 , wherein the activity data is detected while an existing physical activity tracking function is active. 
     
     
       35. The method of  claim 19 , further comprising:
 after a predetermined time has lapsed without initiating a physical activity tracking function corresponding to the first activity boundary alert, displaying a third activity boundary alert, wherein a physical activity tracking function corresponding to the third activity boundary alert tracks activity data detected prior to displaying the first activity boundary alert. 
 
     
     
       36. The method of  claim 19 , wherein the first activity boundary alert includes first content, the method further comprising:
 after displaying the first activity boundary alert, displaying a fourth activity boundary alert including second content, wherein the second content is different from the first content. 
 
     
     
       37. 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:
 detecting, via the one or more sensors, activity data, wherein the activity data includes at least one or more of user standing data, user moving data, and user exercise data; and 
 in response to detecting the activity data:
 in accordance with a determination that the activity data satisfies first activity boundary alert criteria, wherein the first activity boundary alert criteria corresponds to a first predicted type of physical activity:
 displaying a first activity boundary alert including a first affordance; 
 receiving a first user input corresponding to selection of the first affordance; and 
 in response to receiving the first user input, initiating a first physical activity tracking function corresponding to the first predicted type of physical activity; and 
 
 in accordance with a determination that the activity data satisfies second activity boundary alert criteria, wherein the second activity boundary alert criteria corresponds to a second predicted type of physical activity, different from the first predicted type of physical activity:
 displaying a second activity boundary alert including a second affordance; 
 receiving a second user input corresponding to selection of the second affordance; and 
 in response to receiving the second user input, initiating a second physical activity tracking function corresponding to the second predicted type of physical activity, wherein the second physical activity tracking function is different from the first physical activity tracking function. 
 
 
 
     
     
       38. The non-transitory computer readable storage medium of  claim 37 , wherein the one or more sensors includes one or more of an accelerometer, a global positioning system (GPS) sensor, a heart rate monitor, a clock, and a gyroscope. 
     
     
       39. The non-transitory computer readable storage medium of  claim 37 , wherein the one or more programs further include instructions for:
 further in response to detecting the activity data:
 in accordance with a determination that the activity data does not satisfy the second activity boundary alert criteria, forgoing display of the second activity boundary alert. 
 
 
     
     
       40. The non-transitory computer readable storage medium of  claim 37 , wherein the activity data is detected before a physical activity tracking function is active. 
     
     
       41. The non-transitory computer readable storage medium of  claim 37 , wherein the first physical activity tracking function corresponding to the first activity boundary alert tracks activity data detected prior to displaying the first activity boundary alert. 
     
     
       42. The non-transitory computer readable storage medium of  claim 37 , wherein the activity data was detected via a first sensor of the one or more sensors, the one or more programs further including instructions for:
 initiating the first physical activity tracking function corresponding to the first predicted type of physical activity corresponding to the first activity boundary alert by detecting second activity data via a second sensor, different from the first sensor, of the one or more sensors. 
 
     
     
       43. The non-transitory computer readable storage medium of  claim 37 , wherein the first activity boundary alert corresponds to a third physical activity tracking function, and wherein the first activity boundary alert includes a third affordance, the one or more programs further including instructions for:
 receiving a third user input corresponding to a selection of the third affordance in the first activity boundary alert; 
 in response to receiving the third user input, displaying a first user interface including:
 a fourth affordance corresponding to a fourth physical activity tracking function different from the third physical activity tracking function; and 
 a fifth affordance corresponding to a fifth physical activity tracking function different from the third physical activity tracking function; and 
 while displaying the first user interface, receiving a fourth user input: 
 in accordance with the fourth user input corresponding to a selection of the fourth affordance in the first user interface, configuring the electronic device to track activity data detected after the selection of the fourth affordance using the fourth physical activity tracking function; and 
 in accordance with the fourth user input corresponding to a selection of the fifth affordance in the second user interface, configuring the electronic device to track activity data detected after the selection of the fifth affordance using the fifth physical activity tracking function. 
 
 
     
     
       44. The non-transitory computer readable storage medium of  claim 37 , wherein the activity data is detected while an existing physical activity tracking function is active, and wherein the first activity boundary alert includes a sixth affordance, the one or more programs further including instructions for:
 receiving a fourth user input corresponding to a selection of the sixth affordance; and 
 in response to receiving the fourth user input:
 ending a current physical activity tracking function; and 
 storing activity data detected prior to receiving the fourth user input as a previous workout. 
 
 
     
     
       45. The non-transitory computer readable storage medium of  claim 44 , wherein the first activity boundary alert includes a seventh affordance, the one or more programs further including instructions for:
 receiving a fifth user input corresponding to a selection of the seventh affordance; and 
 in response to receiving the fifth user input, pausing execution of the current physical activity tracking function. 
 
     
     
       46. The non-transitory computer readable storage medium of  claim 45 , wherein the first activity boundary alert corresponds to a sixth physical activity tracking function, and wherein displaying the first activity boundary alert includes displaying an eighth affordance, the one or more programs further including instructions for:
 receiving a sixth user input corresponding to a selection of the an eighth affordance; and 
 in response to receiving the sixth user input:
 initiating a process for ceasing execution of the sixth physical activity tracking function; and 
 displaying a second user interface including:
 a ninth affordance corresponding to a seventh physical activity tracking function different from the sixth physical activity tracking function, and 
 a tenth affordance corresponding to an eighth physical activity tracking function different from the sixth physical activity tracking function and the seventh physical activity tracking function; 
 
 
 receiving a seventh user input; 
 in accordance with the seventh user input corresponding to a selection of the ninth affordance in the second user interface, initiating the seventh physical activity tracking function; and 
 in accordance with the seventh user input corresponding to a selection of the tenth affordance in the second user interface, initiating the eighth physical activity tracking function. 
 
     
     
       47. The non-transitory computer readable storage medium of  claim 46 , wherein the first activity boundary alert includes an eleventh affordance, and wherein the first physical activity tracking function corresponding to the first activity boundary alert is a ninth physical activity tracking function, the one or more programs further including instructions for:
 receiving an eighth user input corresponding to a selection of the eleventh affordance; and 
 in response to receiving the eighth user input, initiating ninth physical activity tracking function corresponding to the first activity boundary alert, wherein the ninth physical activity tracking function is different from the eight physical activity tracking function. 
 
     
     
       48. The non-transitory computer readable storage medium of  claim 47 , wherein the first affordance is highlighted as compared to the eleventh affordance. 
     
     
       49. The non-transitory computer readable storage medium of  claim 37 , wherein the one or more programs further include instructions for:
 after displaying the first activity boundary alert and before a physical activity tracking function is active:
 displaying a third user interface including a scrollable list of affordances associated with physical activities; 
 receiving a ninth user input; 
 in accordance with a determination that the ninth user input is detected at a twelfth affordance in the scrollable list of affordances, launching the first physical activity tracking function corresponding to the first activity boundary alert; and 
 in accordance with a determination that the ninth user input is detected at a thirteenth affordance in the scrollable list of affordances, launching a physical activity tracking function (1) not corresponding to the first activity boundary alert and (2) different from the first physical activity tracking function corresponding to the first activity boundary alert. 
 
 
     
     
       50. The non-transitory computer readable storage medium of  claim 49 , wherein the first physical activity tracking function corresponding to the first activity boundary alert is an tenth physical activity tracking function, the one or more programs further including instructions for:
 in accordance with a determination that the ninth user input is detected at a fourteenth affordance in the scrollable list of affordances, launching an eleventh physical activity tracking function corresponding to the first activity boundary alert, wherein the eleventh physical activity tracking function is different from the tenth physical activity tracking function, and wherein the eleventh physical activity tracking function corresponding to the first activity boundary alert tracks activity data detected after receiving the ninth user input. 
 
     
     
       51. The non-transitory computer readable storage medium of  claim 37 , wherein the first activity boundary alert includes a first animated affordance representing the first predicted type of physical activity corresponding with the first activity boundary alert, and wherein the second activity boundary alert includes a second animated affordance representing the second predicted type of physical activity corresponding with the second activity boundary alert. 
     
     
       52. The non-transitory computer readable storage medium of  claim 37 , wherein the activity data is detected while an existing physical activity tracking function is active. 
     
     
       53. The non-transitory computer readable storage medium of  claim 37 , wherein the one or more programs further including instructions for:
 after a predetermined time has lapsed without initiating a physical activity tracking function corresponding to the first activity boundary alert, displaying a third activity boundary alert, wherein a physical activity tracking function corresponding to the third activity boundary alert tracks activity data detected prior to displaying the first activity boundary alert. 
 
     
     
       54. The non-transitory computer readable storage medium of  claim 37 , wherein the first activity boundary alert includes first content, the one or more programs further including instructions for:
 after displaying the first activity boundary alert, displaying a fourth activity boundary alert including second content, wherein the second content is different from the first content.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application claims priority to U.S. provisional patent application 62/668,159, entitled “DISPLAYING USER INTERFACES ASSOCIATED WITH PHYSICAL ACTIVITIES”, filed on May 7, 2018, and U.S. provisional patent application 62/679,906, entitled “DISPLAYING USER INTERFACES ASSOCIATED WITH PHYSICAL ACTIVITIES”, filed on Jun. 3, 2018, the entire contents of which are hereby incorporated by reference. 
    
    
     FIELD 
     The present disclosure relates generally to user interfaces and more specifically to techniques for displaying user interfaces associated with physical activities. 
     BACKGROUND 
     Many modern electronic devices provide the capability of tracking physical activities by a user. Such electronic devices often display information associated with the physical activities to the user. Some techniques provide the ability to compare the physical activities of the user with physical activities of other users. Other techniques provide the ability to begin and end tracking of a physical activity. Other techniques provide the ability to set pace alerts for a physical activity. However, such techniques can be cumbersome and inefficient. 
     SUMMARY 
     Some techniques for displaying user interfaces associated with physical activities using electronic devices 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 displaying user interfaces associated with physical activities. Such methods and interfaces optionally complement or replace other methods for displaying user interfaces associated with physical activities. 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. 
     A system of one or more computers can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions. One or more computer programs can be configured to perform particular operations or actions by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions. 
     One general aspect includes a method performed at an electronic device including a display. The method includes receiving first user activity data for a time period, the first user activity data including at least first user activity data for a first time subset and first user activity data for a second time subset. The method further includes receiving second user activity data for the time period, the second user activity data including at least second user activity data for the first time subset and second user activity data for the second time subset. The method further includes displaying, on the display, a user interface including: (1) a representation of the first user activity data for the first time subset; (2) a representation of the first user activity data for the second time subset; (3) a cumulative representation of the first user activity data for the time period, where the cumulative representation of the first user activity data for the time period is based on at least the first user activity data for a first time subset and the first user activity data for a second time subset; (4) a representation of the second user activity data for the first time subset; (5) a representation of the second user activity data for the second time subset; and (6) a cumulative representation of the second user activity data for the time period, where the cumulative representation of the second user activity data for the time period is based on at least the second user activity data for a first time subset and the second user activity data for a second time subset. Other examples of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods. 
     One general aspect includes a method performed at an electronic device including a display. The method includes receiving first user activity data for a first user, where the first user activity data corresponds to a first time period and a second time period. The method further includes receiving second user activity data for a second user, where the second user activity data corresponds to the first time period, and where the first time period includes a first elapsed sub-period and a first unelapsed sub-period for an activity competition between the first user and the second user. The method further includes receiving third user activity data for the third user, where the third user activity data corresponds to the second time period, and where the second time period includes a second elapsed sub-period and a second unelapsed sub-period for an activity competition between the first user and the third user. The method further includes displaying, on the display, a user interface including: (1) a representation of the first user activity data and the second user activity data during the first elapsed sub-period for the activity competition between the first user and the second user; (2) an indication of an amount of time in the first unelapsed sub-period for the activity competition between the first user and the second user; (3) a representation of the first activity data and the third activity data during the second elapsed sub-period for the activity competition between the first user and the third user; and (4) an indication of an amount of time in the second unelapsed sub-period for the activity competition between the first user and the third user. Other examples of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods. 
     One general aspect includes a method performed at an electronic device including a display and one or more sensors. The method includes detecting, via the one or more sensors, activity data. The method further includes, in response to detecting the activity data and in accordance with a determination that the activity data satisfies activity boundary alert criteria, displaying an activity boundary alert. The method further includes, in further response to detecting the activity data and in accordance with a determination that the activity data does not satisfy the activity boundary alert criteria, forgoing display of the activity boundary alert. Other examples of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods. 
     One general aspect includes a method performed at an electronic device. The method includes displaying a physical activity rate user interface including a first setting affordance and a second setting affordance. The method further includes. while displaying the physical activity rate user interface, receiving a first user input. The method further includes, in response to receiving the first user input and in accordance with the first user input corresponding to selection of the first setting affordance, configuring a physical activity rate calculation to use a first portion of a dataset. The method further includes, in response to receiving the first user input and in accordance with the first user input corresponding to selection of the second setting affordance, configuring a physical activity rate calculation to use a second portion of the dataset different from the first portion. Other examples of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods. 
     One general aspect includes 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 any of the methods described above. 
     One general aspect includes a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for any of the methods described above. 
     One general aspect includes an electronic device, including a display. The electronic device also includes one or more processors. The electronic device also includes memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing any of the methods described above. 
     One general aspect includes an electronic device, including a display. The electronic device also includes means for receiving first user activity data for a time period, the first user activity data including at least first user activity data for a first time subset and first user activity data for a second time subset. The electronic device also includes means for receiving second user activity data for the time period, the second user activity data including at least second user activity data for the first time subset and second user activity data for the second time subset. The electronic device also includes means for displaying, on the display, a user interface including: (1) a representation of the first user activity data for the first time subset; (2) a representation of the first user activity data for the second time subset; (3) a cumulative representation of the first user activity data for the time period, where the cumulative representation of the first user activity data for the time period is based on at least the first user activity data for a first time subset and the first user activity data for a second time subset; (4) a representation of the second user activity data for the first time subset; (5) a representation of the second user activity data for the second time subset; (6) and a cumulative representation of the second user activity data for the time period, where the cumulative representation of the second user activity data for the time period is based on at least the second user activity data for a first time subset and the second user activity data for a second time subset. 
     One general aspect includes an electronic device, including a display. The electronic device also includes means for receiving first user activity data for a first user, where the first user activity data corresponds to a first time period and a second time period. The electronic device also includes means for receiving second user activity data for a second user, where the second user activity data corresponds to the first time period, and where the first time period includes a first elapsed sub-period and a first unelapsed sub-period for an activity competition between the first user and the second user. The electronic device also includes means for receiving third user activity data for the third user, where the third user activity data corresponds to the second time period, and where the second time period includes a second elapsed sub-period and a second unelapsed sub-period for an activity competition between the first user and the third user. The electronic device also includes means for displaying, on the display, a user interface including: (1) a representation of the first user activity data and the second user activity data during the first elapsed sub-period for the activity competition between the first user and the second user; (2) an indication of an amount of time in the first unelapsed sub-period for the activity competition between the first user and the second user; (3) a representation of the first activity data and the third activity data during the second elapsed sub-period for the activity competition between the first user and the third user; and (4) an indication of an amount of time in the second unelapsed sub-period for the activity competition between the first user and the third user. 
     One general aspect includes an electronic device, including a display. The electronic device also includes means for detecting, via the one or more sensors, activity data. The electronic device also includes a means for, in response to detecting the activity data and in accordance with a determination that the activity data satisfies activity boundary alert criteria, displaying an activity boundary alert. The electronic device also includes a means for, in response to detecting the activity data and in accordance with a determination that the activity data does not satisfy the activity boundary alert criteria, forgoing display of the activity boundary alert. 
     One general aspect includes an electronic device, including a display. The electronic device also includes means for displaying a physical activity rate user interface including a first setting affordance and a second setting affordance. The electronic device also includes means for, while displaying the physical activity rate user interface, receiving a first user input. The electronic device also includes means for, in response to receiving the first user input and in accordance with the first user input corresponding to selection of the first setting affordance, configuring a physical activity rate calculation to use a first portion of a dataset. The electronic device also includes means for, in response to receiving the first user input and in accordance with the first user input corresponding to selection of the second setting affordance, configuring a physical activity rate calculation to use a second portion of the dataset different from the first portion. 
     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 displaying user interfaces associated with physical activities, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for displaying user interfaces associated with physical activities. 
    
    
     
       DESCRIPTION OF THE FIGURES 
       For a better understanding of the various described examples, reference should be made to the Description of Examples below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures. 
         FIG. 1A  is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some examples. 
         FIG. 1B  is a block diagram illustrating exemplary components for event handling in accordance with some examples. 
         FIG. 2  illustrates a portable multifunction device having a touch screen in accordance with some examples. 
         FIG. 3  is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some examples. 
         FIG. 4A  illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some examples. 
         FIG. 4B  illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some examples. 
         FIG. 5A  illustrates a personal electronic device in accordance with some examples. 
         FIG. 5B  is a block diagram illustrating a personal electronic device in accordance with some examples. 
         FIGS. 5C-5D  illustrate exemplary components of a personal electronic device having a touch-sensitive display and intensity sensors in accordance with some examples. 
         FIGS. 5E-5H  illustrate exemplary components and user interfaces of a personal electronic device in accordance with some examples. 
         FIGS. 6A-6T  illustrate exemplary user interfaces related to activity competitions in accordance with some examples. 
         FIGS. 7A-7B  is a flow diagram illustrating a method for displaying an activity competition representation using an electronic device in accordance with some examples. 
         FIGS. 8A-8Y  illustrate exemplary user interfaces related to a friends list for activity sharing in accordance with some examples. 
         FIGS. 9A-9B  is a flow diagram illustrating a method for displaying a friends list representation using an electronic device in accordance with some examples. 
         FIGS. 10A-10Q  illustrate exemplary user interfaces associated with alerts presented to a user in response to automatically determining a boundary of a workout in accordance with some examples. 
         FIG. 11  is a flow diagram illustrating a method for displaying an alert in response to automatically determining a boundary of physical activity using an electronic device in accordance with some examples. 
         FIGS. 12A-12AK  illustrate exemplary user interfaces associated with configuring a pace alert for a workout application in accordance with some examples. 
         FIG. 13  is a flow diagram illustrating a method for displaying a user interface to configure a dataset that is used to calculate a pace using an electronic device in accordance with some examples. 
     
    
    
     DESCRIPTION OF EXAMPLES 
     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 examples. 
     There is a need for electronic devices that provide efficient methods and interfaces for displaying user interfaces associated with physical activities. Such techniques can reduce the cognitive burden on a user who accesses user interfaces associated with physical activities, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs. 
     Below,  FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H  provide a description of exemplary devices for performing the techniques for managing event notifications.  FIGS. 6A-6T  illustrate exemplary user interfaces related to activity competitions in accordance with some examples.  FIGS. 7A-7B  is a flow diagram illustrating a method for displaying an activity competition representation using an electronic device in accordance with some examples. The user interfaces in  FIGS. 6A-6T  are used to illustrate the processes described below, including the process in  FIGS. 7A-7B .  FIGS. 8A-8Y  illustrate exemplary user interfaces related to a friends list for activity sharing in accordance with some examples.  FIGS. 9A-9B  is a flow diagram illustrating a method for displaying a friends list representation using an electronic device in accordance with some examples. The user interfaces in  FIGS. 8A-8Y  are used to illustrate the processes described below, including the process in  FIGS. 9A-9B .  FIGS. 10A-10Q  illustrate exemplary user interfaces associated with alerts presented to a user in response to automatically determining a boundary of a workout in accordance with some examples.  FIG. 11  is a flow diagram illustrating a method for displaying an alert in response to automatically determining a boundary of physical activity using an electronic device in accordance with some examples. The user interfaces in  FIGS. 10A-10Q  are used to illustrate the processes described below, including the process in  FIG. 11 .  FIGS. 12A-12AK  illustrate exemplary user interfaces associated with configuring a pace alert for a workout application in accordance with some examples.  FIG. 13  is a flow diagram illustrating a method for displaying a user interface to configure a dataset that is used to calculate a pace using an electronic device in accordance with some examples. The user interfaces in  FIGS. 12A-12AK  are used to illustrate the processes described below, including the process in  FIG. 13 . 
     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 examples. 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 examples herein is for the purpose of describing particular examples only and is not intended to be limiting. As used in the description of the various described examples 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. 
     Examples of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some examples, 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 examples 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 examples, 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 examples of portable devices with touch-sensitive displays.  FIG. 1A  is a block diagram illustrating portable multifunction device  100  with touch-sensitive display system  112  in accordance with some examples. 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. 1A  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 examples, peripherals interface  118 , CPU  120 , and memory controller  122  are, optionally, implemented on a single chip, such as chip  104 . In some other examples, 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 examples, 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 examples, input controller(s)  160  are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g.,  208 ,  FIG. 2 ) optionally include an up/down button for volume control of speaker  111  and/or microphone  113 . The one or more buttons optionally include a push button (e.g.,  206 ,  FIG. 2 ). 
     A quick press of the push button optionally disengages a lock of touch screen  112  or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g.,  206 ) optionally turns power to device  100  on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen  112  is used to implement virtual or soft buttons and one or more soft keyboards. 
     Touch-sensitive display  112  provides an input interface and an output interface between the device and a user. Display controller  156  receives and/or sends electrical signals from/to touch screen  112 . Touch screen  112  displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some examples, 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 example, 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 examples. 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 example, 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 examples 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 examples 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 examples, 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 examples, 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 examples, 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 examples, in addition to the touch screen, device  100  optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some examples, 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. 1A  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 examples, 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 examples, 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 examples, 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. 1A  shows a contact intensity sensor coupled to intensity sensor controller  159  in I/O subsystem  106 . Contact intensity sensor  165  optionally includes one or more piezoresistive strain gauges, capacitive force sensors, 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 examples, 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 examples, 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. 1A  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 examples, 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. 1A  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 examples, 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 examples, 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. 1A  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 examples, 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 examples, 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 examples, memory  102  (FIG.  1 A) or  370  ( FIG. 3 ) stores device/global internal state  157 , as shown in  FIGS. 1A and 3 . Device/global internal state  157  includes one or more of: 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 examples, 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 examples, contact/motion module  130  and display controller  156  detect contact on a touchpad. 
     In some examples, 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 examples, 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 examples, 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 examples, 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 examples, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some examples, 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 examples, 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 examples, 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 examples. 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. 1A ). In some examples, 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 examples, 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 examples, 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 examples, a “menu button” is implemented using a touchpad. In some other examples, the menu button is a physical push button or other physical input control device instead of a touchpad. 
       FIG. 1B  is a block diagram illustrating exemplary components for event handling in accordance with some examples. In some examples, memory  102  ( FIG. 1A ) 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 examples, 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 examples, 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 examples, 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 examples, event monitor  171  sends requests to the peripherals interface  118  at predetermined intervals. In response, peripherals interface  118  transmits event information. In other examples, 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 examples, 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 examples, active event recognizer determination module  173  determines that only the hit view should receive a particular sequence of sub-events. In other examples, 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 examples, 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 examples 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 examples, event dispatcher module  174  stores in an event queue the event information, which is retrieved by a respective event receiver  182 . 
     In some examples, operating system  126  includes event sorter  170 . Alternatively, application  136 - 1  includes event sorter  170 . In yet other examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, the event also includes information for one or more associated event handlers  190 . 
     In some examples, event definition  187  includes a definition of an event for a respective user-interface object. In some examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, event handler(s)  190  includes or has access to data updater  176 , object updater  177 , and GUI updater  178 . In some examples, 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 examples, 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 examples. The touch screen optionally displays one or more graphics within user interface (UI)  200 . In this example, 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 examples, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some examples, 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 examples, the menu button is implemented as a soft key in a GUI displayed on touch screen  112 . 
     In some examples, 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 example, 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 examples. Device  300  need not be portable. In some examples, 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. 1A ), 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. 1A ). Memory  370  includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory  370  optionally includes one or more storage devices remotely located from CPU(s)  310 . In some examples, 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. 1A ), 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. 1A ) 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 examples. In some examples, 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 examples of user interfaces that are, optionally, implemented on, for example, portable multifunction device  100 . 
       FIG. 4A  illustrates an exemplary user interface for a menu of applications on portable multifunction device  100  in accordance with some examples. Similar user interfaces are, optionally, implemented on device  300 . In some examples, 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. 4A  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 examples, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some examples, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon. 
       FIG. 4B  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 examples, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in  FIG. 4B . In some examples, the touch-sensitive surface (e.g.,  451  in FIG.  4 B) has a primary axis (e.g.,  452  in  FIG. 4B ) that corresponds to a primary axis (e.g.,  453  in  FIG. 4B ) on the display (e.g.,  450 ). In accordance with these examples, the device detects contacts (e.g.,  460  and  462  in  FIG. 4B ) with the touch-sensitive surface  451  at locations that correspond to respective locations on the display (e.g., in  FIG. 4B, 460  corresponds to  468  and  462  corresponds to  470 ). In this 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. 4B ) are used by the device to manipulate the user interface on the display (e.g.,  450  in  FIG. 4B ) of the multifunction device when the touch-sensitive surface is separate from the display. It 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 examples, 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. 5A  illustrates exemplary personal electronic device  500 . Device  500  includes body  502 . In some examples, device  500  can include some or all of the features described with respect to devices  100  and  300  (e.g.,  FIGS. 1A-4B ). In some examples, 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 examples, 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 examples, 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 examples, 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. 5B  depicts exemplary personal electronic device  500 . In some examples, device  500  can include some or all of the components described with respect to  FIGS. 1A, 1B, 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 processes  700  ( FIGS. 7A-7B ),  900  ( FIGS. 9A-9B ),  1100  ( FIG. 11 ), and  1300  ( FIG. 13 ). A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device  500  is not limited to the components and configuration of  FIG. 5B , 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. 1A, 3, and 5A-5B ). 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. 4B ) 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. 1A  or touch screen  112  in  FIG. 4A ) 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 examples, 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 examples, 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 examples, 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 examples, 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. 5C  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. 5C  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 examples, each contact is assigned a respective intensity that is a portion of the aggregate intensity.  FIG. 5D  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. 5C-5D  can be performed using an electronic device similar or identical to device  100 ,  300 , or  500 . In some examples, a characteristic intensity of a contact is based on one or more intensities of the contact. In some examples, 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. 5C-5D  to aid the reader. 
     In some examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, the contact-detection intensity threshold is zero. In some examples, the contact-detection intensity threshold is greater than zero. 
     In some examples 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 examples, 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 examples, 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. 5E-5H  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. 5E , to an intensity above a deep press intensity threshold (e.g., “IT D ”) in  FIG. 5H . 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 examples, 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. 5F-5H . In some examples, 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. 5E-5H  to aid the reader. 
     In some examples, 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. 5F . 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. 5G . 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. 5H . Representations  578 A- 578 C form an array above icon  572 B. In some examples, the animation progresses in accordance with an intensity of contact  562 , as shown in  FIGS. 5F-5G , 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 examples, 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. 5E-5H  can be performed using an electronic device similar or identical to device  100 ,  300 , or  500 . 
     In some examples, 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 examples, 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 examples, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances). 
     For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. 
     As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices  100 ,  300 , and/or  500 ) and is ready to be launched (e.g., become opened) on the device. In some examples, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system. 
     As used herein, the terms “open application” or “executing application” refer to a software application with retained state information (e.g., as part of device/global internal state  157  and/or application internal state  192 ). An open or executing application is, optionally, any one of the following types of applications:
         an active application, which is currently displayed on a display screen of the device that the application is being used on;   a background application (or background processes), which is not currently displayed, but one or more processes for the application are being processed by one or more processors; and   a suspended or hibernated application, which is not running, but has state information that is stored in memory (volatile and non-volatile, respectively) and that can be used to resume execution of the application.       

     As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application. 
     Attention is now directed towards examples of user interfaces (“UP”) and associated processes that are implemented on an electronic device, such as portable multifunction device  100 , device  300 , or device  500 . 
       FIGS. 6A-6T  illustrate exemplary user interfaces related to activity competitions in accordance with some examples. Such activity competitions allow participants of the activity competitions to compete for a set time period using physical activity detected by their respective devices. For example, an activity competitions can be configured to last for a week. During the week, devices of participants can detect physical activity performed by the participants. By the end of the week, the participant with the most detected physical activity can win the activity competition. In some examples, an activity competition can be between two participants. In other examples, an activity competition can be between more than two participants. 
       FIG. 6A  depicts two electronic devices (i.e., device  600 A and device  600 B). For explanatory purposes, device  600 A will belong to Molly and device  600 B will belong to Aled; the two devices are in electronic communication (e.g., wireless communication). Each of the two electronic devices can include a touch-sensitive display (e.g., touch-sensitive display  602 A and touch-sensitive display  602 B) for displaying user interfaces that can be interacted with by touching the touch-sensitive display. It should be recognized that other input mechanisms (other than touch) can be used to interact with the user interfaces displayed by the two electronic devices. For example, each electronic device includes a rotatable input mechanism (e.g., rotatable input mechanism  604 A and rotatable input mechanism  604 B that can each rotate with respect to the housings of the respective devices) and a push button (e.g., push button  606 A and push button  606 B). In some examples, devices  600 A and  600 B may include one or more features of devices  100 ,  300 , or  500 , as described above. When multiple electronic devices are illustrated in a single figure, it should be recognized that the user interfaces depicted in the figure can be synced in time (e.g., while device  600 A displays a first user interface in a figure, device  600 B displays a second user interface in the figure). 
     Referring to device  600 A in  FIG. 6A , user interface  608  is displayed on touch-sensitive display  602 A. User interface  608  is a notification that is displayed in response to a determination that a participant of the activity competition (e.g., Molly) associated with device  600 A has completed three different physical activity goals (referred to as rings). A representation of the three different physical activity goals completed is illustrated at representation  610 B. 
     Referring to device  600 B in  FIG. 6A , user interface  612  is displayed in response to receiving data, transmitted from device  600 A, indicating that Molly completed her three different physical activity goals. For example, user interface  612  can be informing Aled that Molly completed her three different physical activity goals (as illustrated at representation  610 A). It should be recognized that user interface  612  can be displayed in response to other physical activity performed by Molly, such as Molly completing a workout. 
     User interface  612  can include a scrollable list of affordances  614 , where each affordance is associated with a different operation. For example, the scrollable list of affordances  614  includes first affordance  614 A, second affordance  614 B, and third affordance  614 C. Selection of first affordance  614 A can initiate a sequence to begin an activity competition between Aled and Molly. Selection of second affordance  614 B can cause a messaging interface to be displayed (as depicted in  FIG. 6J  and discussed below) to allow Aled to send a message to Molly in response to her completing her three physical activity goals. Selection of third affordance  614  can cause device  600 B to cease to display user interface  612 . In  FIG. 6A , the full content of user interface  612  is shown, including portions that would not initially fit on the display (e.g., portions accessed via scrolling), for ease of explanation. Throughout the disclosure, additional user interfaces are shown in this manner for ease of explanation. 
       FIG. 6B  again illustrates the user interfaces depicted in  FIG. 6A . While device  600 A is continuing to display user interface  608  in  FIG. 6B , it should be recognized that device  600 A can display a different user interface. As described above, user interface  612  on device  600 B includes first affordance  614 A. Referring to  FIG. 6B , user input (e.g., tap input)  601  is received, where user input  601  corresponds to selection of first affordance  614 A. In accordance with a determination that user input  601  is detected at first affordance  614 A, a user interface related to initiating an activity competition is displayed (e.g., user interface  616  depicted in  FIG. 6C ). 
     Referring to  FIG. 6C , user interface  616  is displayed on touch-sensitive display  602 B in response to selection of first affordance  614 A. User interface  616  describes rules for an activity competition. It should be recognized that, in some examples, user interface  616  might not be displayed in response to selection of first affordance  614 A (as depicted in  FIG. 6B ). For example, Aled might have already initiated a particular number of activity competitions such that a user interface describing rules for an activity competition is not necessary. In some examples, user interface  616  can be displayed in response to selection of first affordance  614 A for a particular number of times per participant. For example, user interface  616  can be displayed to Aled 2 times before it is no longer displayed to Aled. 
     User interface  616  includes icon  618 . Icon  618  can represent activity competitions between Molly and Aled, such that all activity competitions (e.g., past activity competitions) between Molly and Aled are associated with icon  618 . In some examples, activity competitions between different participants (such as Molly and Steve) can be represented by different icons with different visual themes than icon  618 . It should be recognized that, in some examples, icons can be assigned to activity competitions prior to display of user interface  616 . User interface  616  further includes affordance  620  for indicating an acceptance of the terms in user interface  616  and causing an invitation to begin an activity competition to be sent to Molly (e.g., to device  600 A). 
       FIG. 6D  again illustrates the user interfaces depicted in  FIG. 6C . While device  600 A is continuing to display user interface  608  in  FIG. 6D , it should be recognized that device  600 A can display a different user interface. As described above, user interface  616  includes an affordance  620 A. Referring to  FIG. 6D , user input (e.g., tap input)  603  is received, where user input  603  corresponds to selection of affordance  620 . In accordance with a determination that user input  603  is detected at affordance  620 , an invitation for an activity competition between Aled and Molly can be sent to device  600 A (as depicted in  FIG. 6E ). 
     Referring to  FIG. 6E , in response to Molly selecting affordance  620  in user interface  616  (as depicted in  FIG. 6D ), user interface  628  can be displayed on device  600 B and user interface  622  can be displayed on device  600 A. User interface  628  indicates that Aled must wait for Molly to accept the invitation sent by Aled, before the activity competition will start. User interface  628  includes icon  630  (which can have the same theme as icon  618 , as depicted in  FIG. 6C ) and affordance  632 , to cease to display user interface  628 . 
     User interface  622  of device  600 A describes rules for an activity competition, similar to user interface  616 . User interface  622  includes icon  624  (which can have the same theme as icon  618 , as depicted in  FIG. 6C ). User interface  622  further includes a scrollable list of affordances  626 , where each affordance is associated with a different operation. For example, the scrollable list of affordances  626  includes first affordance  626 A and second affordance  626 B. 
     Selection of first affordance  626 A can accept the invitation for the activity competition sent by Aled. Acceptance of the invitation can cause the activity competition to begin at a predefined time after the selection (e.g., midnight of the current day), as further described below. Selection of second affordance  626 B can cause device  600 B to reject the invitation (e.g., cause the activity competition to not begin) and cease to display user interface  612 . 
       FIG. 6F  again illustrates the user interfaces depicted in  FIG. 6E . While device  600 B is continuing to display user interface  628  in  FIG. 6F , it should be recognized that device  600 B can display a different user interface. As described above, user interface  622  on device  600 A includes first affordance  626 A. Referring to  FIG. 6F , user input (e.g., tap input)  605  is received, where user input  605  corresponds to selection of first affordance  626 A. In accordance with a determination that user input  605  is detected at first affordance  626 A, an activity competition between Molly and Aled can be set to initiate at a predefined time in the future. 
     Referring to  FIG. 6G , in response to receiving the selection (e.g., by Molly) of affordance  605  in user interface  622  (as depicted in  FIG. 6F ), user interface  634  can be displayed on device  600 A and user interface  640  can be displayed on device  600 B. User interface  634  indicates that the activity competition with Aled will start tomorrow. User interface  634  includes icon  636  (which can have the same theme as icon  618 , as depicted in  FIG. 6C ) and affordance  638 , to cease to display user interface  638 . 
     User interface  640  indicates that the invitation that Aled sent was accepted and that the activity competition with Molly will start tomorrow. User interface  640  includes icon  642  (which can have the same theme as icon  618 , as depicted in  FIG. 6C ). User interface  622  further includes a scrollable list of affordances  644 , where each affordance is associated with a different operation. For example, the scrollable list of affordances  626  includes first affordance  626 A for displaying a messaging user interface (as depicted in  FIG. 6I ) and second affordance  626 B for ceasing to display user interface  640 . 
       FIG. 6H  again illustrates the user interfaces depicted in  FIG. 6G . While device  600 A is continuing to display user interface  634  in  FIG. 6H , it should be recognized that device  600 A can display a different user interface. As described above, user interface  640  on device  600 B includes first affordance  644 A. Referring to  FIG. 6H , user input (e.g., tap input)  607  is received, where user input  607  corresponds to selection of first affordance  644 A. In accordance with a determination that user input  607  is detected at first affordance  644 A, a messaging user interface is displayed (as depicted in  FIG. 6I ). 
     Referring to  FIG. 6I , device  600 B displays user interface  646  in response to selection of first affordance  644 A in user interface  640  (as depicted in  FIG. 6H ). User interface  646  includes a scrollable list of affordances  648 , where each affordance is associated with a different predefined message. Selection of an affordance in the scrollable list of affordance  648  can cause a communication (sometimes referred to as a message) to be generated with the corresponding predefined message and sent to Molly. For example, selection of second affordance  648 B can cause a communication with the text “YOU CAN&#39;T BEAT ME!” to be sent to Molly. 
       FIG. 6J  again illustrates the user interfaces depicted in  FIG. 6I . While device  600 A is continuing to display user interface  634  in  FIG. 6J , it should be recognized that device  600 A can display a different user interface. As described above, user interface  646  on device  600 B includes second affordance  648 B. Referring to  FIG. 6J , user input (e.g., tap input)  609  is received, where user input  609  corresponds to selection of second affordance  648 B. In accordance with a determination that user input  609  is detected at second affordance  648 B, a communication can be generated with text corresponding to second affordance  648 B and sent to Molly. 
     Referring to  FIG. 6K , device  600 B displays user interface  656  in response to selection of second affordance  648 B in user interface  646  (as depicted in  FIG. 6J ). User interface  656  indicates that a message has been sent and includes affordance  658  for causing user interface  656  to cease to display. 
     Also in response to selection of second affordance  648 B in user interface  646  (as depicted in  FIG. 6J ), device  600 A displays user interface  650  in touch-sensitive display  602 A, as depicted in  FIG. 6K . User interface  650  includes a representation of the predefined message sent by Aled, as discussed above. User interface  650  also includes a scrollable list of affordances  652 , where each affordance is associated with a different operation. For example, the scrollable list of affordances  626  includes first affordance  626 A for displaying a messaging user interface (as depicted in  FIG. 6I ) and second affordance  626 B for ceasing to display user interface  650 . 
     While an activity competition is active, participants in the activity competition can receive notifications including a status of the activity competition. For example, in response to the activity competition beginning, a notification can be displayed to each of the participants in the activity competition, as depicted in  FIG. 6L . 
     Referring to  FIG. 6L , user interface  660  is displayed on touch-sensitive display  602 B of device  600 B. While not illustrated, a similar user interface can be displayed on touch-sensitive display  602 A of device  600 A. 
     User interface  660  indicates that the activity competition with Molly has begun. User interface  600  includes a scrollable list of affordances  662 , where each affordance is associated with a different operation. For example, the scrollable list of affordances  626  includes (1) first affordance  662 A for displaying information related to the activity competition, (2) second affordance  662 B for displaying a messaging user interface (as depicted in  FIG. 6I ), and (3) third affordance  662 C for ceasing to display user interface  660 . 
     As depicted in  FIG. 6L , first affordance  662 A includes first portion  663 A with information related to Aled for the activity competition and second portion  663 B with information related to Molly for the activity competition. The information related to Aled includes icon  663 C with a number indicating a number of times that Aled has won an activity competition against Molly. The information related to Aled further includes score  663 D for Aled for the activity competition so far. It should be recognized that the information included within first affordance  662 A can be different than illustrated, such as the information can include graph  670 , as depicted in  FIG. 6M  and discussed below). 
     Selection of first affordance  662 A can cause a user interface with additional information regarding the activity competition to be displayed. For example, the additional information can include graph  670 , as depicted in  FIG. 6M  and discussed below. 
     In addition to a notification being displayed when the activity competition begins, notifications can be displayed at predefined times during the activity competition. For example, a predefined time can be an absolute time during the activity competition (e.g., each day at 10 AM) or as a result of an event occurring on a device where the notification is displayed (e.g., a participant completing a goal, performing a workout, or accessing a particular application on the device). Such notifications can include information related to one or more active activity competitions. 
     Referring to  FIG. 6M , user interface  664  is displayed on touch-sensitive display  602 B in response to a trigger being activated at a predefined time. For example, the predefined time can be at 10 PM on Friday, causing user interface  644  to be displayed. 
     User interface  644  includes a scrollable list of affordances  666 , where each affordance is associated with a different operation. For example, the scrollable list of affordances  666  includes first affordance  666 A for a first activity competition, second affordance  666 B for a second activity competition, and third affordance  666 C for ceasing to display user interface  660 . In some examples, the order of affordances for activity competitions can be based upon when the activity competitions are finishing. For example, activity competitions finishing sooner can be included in the scrollable list before activity competitions finishing later. 
     First affordance  666 A includes information related to the first activity competition. As depicted in  FIG. 6M , first affordance  666 A includes information similar to first affordance  662 A (as depicted in  FIG. 6L ). For example, first affordance  666 A (as depicted in  FIG. 6M ) includes icon  668 A with a number indicating a number of times that Molly has won an activity competition against Aled. First affordance  666 A further includes an identification of Molly (e.g., element  668 B) and a score for Molly for the first activity competition so far (e.g., element  668 C) (sometimes referred to as a cumulative score). 
     As depicted in  FIG. 6M , first affordance  666 A further includes graph  670  for the first activity competition, where graph  670  includes information regarding the first activity competition for multiple subsets (e.g., days). Graph  670  can include more granular information than included in element  668 . The x-axis of graph  670  includes identifications of multiple subsets of the first activity competition. As depicted in  FIG. 6M , each subset is a day of the week (e.g., reference  670 A points to “M” for Monday). It should be noted that “M” is located first to indicate that the first activity competition began on Monday. In addition, it should be noted that “F” (e.g., reference  670 D) is visually highlighted (e.g., circled) in  FIG. 6M  to indicate that Friday is the current day. 
     The y-axis of graph  670  includes representations of physical activity detected for each participant in the first activity competition for each subset. For example, representation  670 B indicates an amount of physical activity detected for Molly (e.g., detected by device  600 A and transmitted to device  600 B) on Monday and representation  670 C indicates an amount of physical activity detected for Aled on Monday. By having representation  670 B adjacent to representation  670 C, physical activity for each participant for Monday can easily be compared. It should be noted that representations for Molly are provided to the left of representations for Aled in graph  670 . The configuration is such because  600 B corresponds to Aled&#39;s device. When a subset has not occurred yet (e.g., Saturday as depicted in  FIG. 6M ), representations corresponding to the subset (e.g., reference  670 E) can be displayed as zero. 
     In some examples, representations for subsets can be normalized across the time period such that the highest representation for a subset of the time period can be displayed a certain size, with other representations normalized based upon the highest representation. For example, if Molly scored the most points for the time period on Friday, a representation for Molly on Friday will be the biggest representation. In such an example, a representation for either Molly or Aled with half the score will be represented as half the size of the representation for Molly on Friday. 
     It should be noted that representations associated with Molly are illustrated as being visually distinct from representations associated with Aled in  FIG. 6M . For example, icon  668 A for Molly is visually distinct from the icon for Aled. In addition, representations for subsets for Molly are visually distinct from representations for subsets for Aled. 
     In some examples, representations associated with a participant that is winning an activity competition can be highlighted as compared to a participant that is losing the activity competition. For example, because Molly&#39;s cumulative score is higher than Aled&#39;s cumulative score, representations associated with Molly visually appear to be highlighted as compared to representations associated with Aled. Visually highlighting representations associated with a participant that is winning can allow a participant to quickly assess how they are doing in the activity competition. 
     Graph  670  also includes a number of subsets remaining in the first activity competition (e.g., reference  670 F). For example, as depicted in  FIG. 6M , there are two days left in the first activity competition. 
     Representation  670  also includes icon  670 G. Icon  670 G can either indicate that selection of affordance  666 A or icon  670 G (depending upon configuration of icon  670 G) will cause a messaging interface to be displayed (as depicted in  FIG. 6J ). 
     As depicted in  FIG. 6M , second affordance  666 B includes information related to the second activity competition between John and Aled. Second affordance  666 B indicates that John and Aled have competed 11 times, where John has won 4 times and Aled has won 7 times. It should be noted that second affordance  666 B illustrates that different activity competitions can begin on different days. For example, the first activity competition began on Monday and the second activity competition began on Thursday. It should also be noted that second affordance  666 B illustrates that time periods (e.g., 7 days) can be the same across different activity competitions. 
     In addition to a notification being displayed when the activity competition begins and at a predefined time, notifications can be displayed in response to activity by another participant. For example, a notification can be displayed for Aled in response to physical activity by Molly, such as Molly reaching a goal for a day (such as closing three activity rings) or performing a workout. Such notifications can include information related to an activity competition with the other participant. 
     Referring to  FIG. 6N , user interface  672  is displayed on touch-sensitive display  602 B in response to Molly reaching her three ring goal for the day. User interface  672  includes a scrollable list of affordances  674 , where each affordance is associated with a different operation. For example, the scrollable list of affordances  674  includes first affordance  674 A for an activity competition between Molly and Aled, second affordance  674 B for displaying a messaging user interface (as depicted  FIG. 6I ), and third affordance  674 C for ceasing to display user interface  672 . First affordance  674 A is similar to that discussed above for first affordance  666 A in  FIG. 6M . 
     Notifications can be sent (e.g., displayed on respective devices of participants) to participants of an activity competition when the activity competition ends. Such notifications can provide results of the activity competition, including an award of a medal for the winner, and include an option to begin a new activity competition, as depicted in  FIG. 6O . 
     Referring to  FIG. 6O , user interface  676  is displayed on touch-sensitive display  602 A in response to an activity competition between Molly and Aled ending. User interface  676  can include text catered to Molly and the outcome of the activity competition. For example, user interface  676  states that “ALED WON.” and includes information that Molly&#39;s best days during the activity competition were Friday and Monday. 
     User interface  676  includes a scrollable list of affordances  678 , where each affordance is associated with a different operation. For example, the scrollable list of affordances  678  includes first affordance  678 A for the activity competition between Molly and Aled, second affordance  678 B for displaying a messaging user interface (as depicted  FIG. 6I ), third affordance  678 C for initiating a process to start a new activity competition (as further discussed below), and fourth affordance  678 D for ceasing to display user interface  672 . 
     Also in response to the activity competition between Molly and Aled ending, user interface  680  is displayed on touch-sensitive display  602 B. User interface  680  can include text catered to Aled and the outcome of the activity competition. For example, user interface  676  states that “YOU WON.” and includes information that Aled&#39;s best day during the activity competition was Saturday with 794 points. 
     User interface  680  includes icon  682 , representing that Aled won icon  682  in response to winning the activity competition. In response to winning icon  682 , icon  682  can be placed in a trophy case for Aled, as further discussed below for  FIG. 8V . 
     User interface  680  also includes a scrollable list of affordances  684 , where each affordance is associated with a different operation. For example, the scrollable list of affordances  684  includes first affordance  684 A for the activity competition between Molly and Aled, second affordance  684 B for displaying a messaging user interface (as depicted  FIG. 6I ), third affordance  684 C for initiating a process to start a new activity competition (as further discussed below), and fourth affordance  684 D for ceasing to display user interface  680 . 
     Having user interface  676  and user interface  680  side-by-side, it should be recognized that representations in a graph (e.g., the graph included in first affordance  678 A and the graph included in first affordance  684 A) can be swapped depending upon where the graph is being displayed. For example, when the graph is being displayed on Aled&#39;s device, representations associated with Aled are generally on the right of representations associated with Molly. Likewise, when the graph is being displayed on Molly&#39;s device, representations associated with Molly are generally on the right of representations associated with Alex. It should also be noted that  FIG. 6O  illustrates that highlighted representations have been changed (e.g., swapped) from Molly to Aled (relative to  FIG. 6M ) because Aled is winning the activity competition depicted in  FIG. 6O . Such swapping can occur anytime a lead for the activity competition changes. 
       FIG. 6P  again illustrates the user interfaces depicted in  FIG. 6O . As described above, user interface  676  on device  600 A includes third affordance  678 C. Referring to  FIG. 6P , user input (e.g., tap input)  611  is received, where user input  611  corresponds to selection of third affordance  678 C. In accordance with a determination that user input  611  is detected at third affordance  678 C, a user interface related to initiating an activity competition is displayed (e.g., user interface  686  as depicted in  FIG. 6Q ), an invitation for a new activity competition is sent to Aled, and a user interface related to the invitation is displayed (e.g., user interface  688  as depicted in  FIG. 6Q ). While device  600 A is depicted as receiving user input  611 , it should be recognized that device  600 B can receive a similar user input on third affordance  684 C, causing similar functionality to be performed. 
     Referring to  FIG. 6Q , user interface  686  is displayed on touch-sensitive display  602 A in response to selection of third affordance  678 C (as depicted in  FIG. 6P ). User interface  686  indicates that an invitation for an new activity competition has been sent to Aled. User interface  686  includes affordance  687  for ceasing to display user interface  686 . 
     Also referring to  FIG. 6Q , user interface  688  is displayed on touch-sensitive display  602 B in response to selection of third affordance  678 C (as depicted in  FIG. 6P ). User interface  688  indicates that Molly has invited Aled to a new activity competition. User interface  688  includes icon  689 , representing activity competitions between Molly and Aled. User interface  688  further includes a scrollable list of affordances  690 , where each affordance is associated with a different operation. For example, the scrollable list of affordances  690  includes first affordance  690 A and second affordance  690 B. 
     Similar to as described above for  FIG. 6E , selection of first affordance  690 A accepts the invitation sent by Molly, causing the new activity competition between Molly and Aled to begin at a predefined time (e.g., midnight of the current day) after selection of first affordance  690 A. Selection of second affordance  626 B can cause device  600 B to reject the invitation (e.g., cause the new activity competition to not begin) and cease to display user interface  688 . 
       FIG. 6R  again illustrates the user interfaces depicted in  FIG. 6Q . While device  600 A is continuing to display user interface  686  in  FIG. 6R , it should be recognized that device  600 A can display a different user interface. As described above, user interface  688  on device  600 B includes first affordance  690 A. Referring to  FIG. 6R , user input (e.g., tap input)  613  is received, where user input  613  corresponds to selection of first affordance  690 A. In accordance with a determination that user input  613  is detected at first affordance  690 A, a new activity competition between Molly and Aled can be set to initiate at a predefined time in the future. 
     Referring to  FIG. 6S , in response to receiving Aled&#39;s selection of affordance  690 A in user interface  688  (as depicted in  FIG. 6R ), user interface  694  is displayed on device  600 B and user interface  691  is displayed on device  600 A. User interface  694  indicates that the new activity competition with Molly will start tomorrow. User interface  694  includes icon  695  (which can have the same theme as icon  618 , as depicted in  FIG. 6C ) and affordance  696 , to cease to display user interface  694 . 
     User interface  691  indicates that the invitation that Molly sent was accepted and that the activity competition with Aled will start tomorrow. User interface  691  includes icon  692  (which can have the same theme as icon  618 , as depicted in  FIG. 6C ). User interface  691  further includes a scrollable list of affordances  693 , where each affordance is associated with a different operation. For example, the scrollable list of affordances  693  includes first affordance  693 A for displaying a messaging user interface (as depicted in  FIG. 6I ) and second affordance  693 B for ceasing to display user interface  691 . 
     While the figures described above depict an electronic device in the form of a smart watch, it should be recognized that any of the user interfaces discussed above can be displayed on different electronic devices, such as a smart phone. In some examples, display of the user interfaces discussed above on an electronic device with a larger display area can include further detail (as depicted in  FIG. 6T ) not shown on electronic devices with a smaller display. 
     Referring to  FIG. 6T , user interface  697  is displayed on touch-sensitive display  802  of device  800 . In some examples, device  800  includes one or more features of device  100 ,  300 ,  500 , or  600 . User interface  697  includes affordance  698 , which includes information related to an activity competition between Molly and Aled. Similar to as described above for  FIG. 6M , affordance  698  includes icon  698 A with a number indicating a number of times that Molly has won an activity competition against Aled. Affordance  698  further includes an identification of Molly (e.g., element  698 B) and a score for Molly for the activity competition so far (e.g., element  698 C) (sometimes referred to as a cumulative score). 
     Also similar to as described above for  FIG. 6M , affordance  698  further includes a graph for the activity competition, where the graph includes information regarding the activity competition for multiple subsets (e.g., days). The x-axis of the graph includes identifications of multiple subsets of the activity competition. As depicted in  FIG. 6T , each subset is a day of the week (e.g., reference  698 G points to “Mon” for Monday). It should be noted that “Mon” is located first to indicate that the activity competition began on Monday. In addition, it should be noted that “Fri” (e.g., reference  698 J) is visually highlighted (e.g., circled) in  FIG. 6T  to indicate that Friday is the current day. 
     The y-axis of the graph includes representations of physical activity detected for each participant in the activity competition for each subset. For example, representation  698 H indicates an amount of physical activity received for Molly (e.g., detected by device  600 A and transmitted to device  800 ) on Monday and representation  698 I indicates an amount of physical activity detected for Aled on Monday. By having representation  698 H adjacent to representation  698 I, physical activity for each participant for Monday can easily be compared. When a subset has not occurred yet (e.g., Saturday as depicted in  FIG. 6T ), representations corresponding to the subset (e.g., reference  618 K) can be displayed as zero. 
     In some examples, representations for subsets can be normalized across the time period such that the highest representation for a subset of the time period can be displayed a certain size, with other representations normalized based upon the highest representation. For example, if Aled scored the most points for the time period on Monday, a representation for Aled on Monday will be the biggest representation. In such an example, a representation for either Molly or Aled with half the score will be represented as half the size of the representation for Aled on Monday. As depicted in  FIG. 6T , the graph further includes value  698 L for indicating a scale of the graph. The scale can allow a participant to better understand a number of points for each representation in the graph. 
     It should be noted that representations associated with Molly are illustrated as being visually distinct from representations associated with Aled in  FIG. 6T . For example, icon  698 A for Molly is visually distinct from icon  698 D for Aled. In addition, representations for subsets for Molly are visually distinct from representations for subsets for Aled. 
     In some examples, representations associated with a participant that is winning an activity competition can be highlighted as compared to a participant that is losing the activity competition. For example, because Molly&#39;s cumulative score is higher than Aled&#39;s cumulative score, representations associated with Molly visually appear to be highlighted as compared to representations associated with Aled. Visually highlighting representations associated with a participant that is winning can allow a participant to quickly assess how they are doing in the activity competition. 
     Unlike graph  670  depicted in  FIG. 6M , the graph depicted in  FIG. 6T  further includes additional information regarding the activity competition. For example, the graph includes a daily average number of points for each participant during the activity competition (e.g., reference  698 M and  698 N). In particular, the graph states that Molly has a daily average of 487 points and Aled has a daily average of 442 points. In the example depicted in  FIG. 6T , the daily average for Molly is highlighted (e.g., bolded) because Molly is currently winning the activity competition. It should be recognized that other additional information not included in graph  670  (as depicted in  FIG. 6M ) can be included in the graph depicted in  FIG. 6T . 
     In some examples, points provided to a participant in an activity competition are based upon a percentage of a goal reached by the participant. For example, a goal can correspond to an amount of walking for each day. Such a goal can be set by the participant either before the activity begins (in some examples) or at any time during the activity competition (in other examples). In some examples, different participants in an activity competition can have different goals. In some examples, points provided to a participant in an activity completion are based upon a two-tier scoring system, where scoring changes when a participant reaches a threshold (e.g., bonus points after the threshold). 
       FIGS. 7A-7B  include a flow diagram illustrating a method for displaying an activity competition representation using an electronic device in accordance with some examples. Method  700  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 A,  600 B,  800 ) with a display. Some operations in method  700  are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  700  provides an intuitive way for displaying a user interface on a device corresponding to a first user, where the user interface includes an activity competition graph (associated with the first user and a second user) having (1) a score comparison for each day of an activity competition between the first user and the second user and (2) a total sum over the activity competition. The user interface permits a user viewing the user interface to readily access physical activity data corresponding to the second user. The method reduces the cognitive burden on a user for accessing physical activity data corresponding to another user, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to access physical activity data corresponding to another user faster and more efficiently conserves power and increases the time between battery charges. 
     At block  702 , the device (e.g.,  FIG. 6M, 600B , and  FIG. 6T, 800 ) receives first user activity data (e.g.,  FIG. 6M , data represented by top right portion of  666 A and representations for Aled, and  FIG. 6T , data represented by  698 D,  698 E,  698 F,  698 I, and other representations for Aled) for a time period (e.g., a day, a week, a month) (e.g.,  FIG. 6M , Monday through Sunday for first activity competition and Thursday through Wednesday for second activity competition, and  FIG. 6T , Monday through Sunday). The first user activity data includes at least first user activity data (e.g.,  FIG. 6M , data represented by representation  670 C, and  FIG. 6T , data represented by representation  698 I) for a first time subset (e.g., an hour, a day, a week) (e.g.,  FIG. 6M , Monday for first activity competition and Thursday for second activity competition, and  FIG. 6T , Monday) and first user activity data (e.g.,  FIG. 6M , data represented by Aled&#39;s representation for Tuesday, and  FIG. 6T , data represented by Aled&#39;s representation for Tuesday) for a second time subset (e.g.,  FIG. 6M , Tuesday for first activity competition and Wednesday for second activity competition, and  FIG. 6T , Tuesday). 
     In some examples, the first user activity data is received (e.g., via one or more antennas of the device) by the device (e.g.,  FIG. 6M, 600B , and  FIG. 6T, 800 ) from a second device (e.g.,  FIG. 6A, 600A ). For example, receiving the first user activity data can include detecting, using one or more sensors of the device, the first user activity data. In some examples, the one or more sensors include a heart rate monitor, a GPS locating device, a gyroscope, or the like. 
     At block  704 , the device (e.g.,  FIG. 6M, 600B , and  FIG. 6T, 800 ) receives second user activity data (e.g.,  FIG. 6M , data represented by top left portion of  666 A and representations for Molly, and  FIG. 6T , data represented by  698 A,  698 B,  698 C,  698 H, and other representations for Molly) for the time period. The second user activity data includes at least second user activity data (e.g.,  FIG. 6M , data represented by representation  670 B, and  FIG. 6T , data represented by representation  698 H) for the first time subset and second user activity data (e.g.,  FIG. 6M , data represented by Molly&#39;s representation for Tuesday, and  FIG. 6T , data represented by Molly&#39;s representation for Tuesday) for the second time subset. 
     In some examples, the second user activity data is received (e.g., via one or more antennas of the device) by the device from a second device (e.g.,  FIG. 6A, 600A ). For example, receiving the second user activity data can include receiving the second user activity data from an external device (e.g., via a transmission from the external device) (e.g.,  FIG. 6A, 600A ). 
     In some examples, in response to receiving the second user activity data from an external device (e.g.,  FIG. 6A, 600A ), the device (e.g.,  FIG. 6M, 600B , and  FIG. 6T, 800 ) can output an activity notification (e.g., visual, haptic, or audio alert) ( FIG. 6A, 612 ). 
     At  712 , the device (e.g.,  FIG. 6M, 600B , and  FIG. 6T, 800 ) displays, on the display (e.g.,  FIG. 6M, 602B , and  FIG. 6T, 802 ), a user interface (e.g.,  FIG. 6M, 664 , and  FIG. 6T, 697 ). In some examples, the activity notification (e.g.,  FIG. 6M, 612 ) described above is outputted prior to displaying the user interface. 
     In some examples, prior to displaying the user interface (e.g.,  FIG. 6M, 664 , and  FIG. 6T, 697 ), the device (e.g.,  FIG. 6M, 600B , and  FIG. 6T, 800 ) displays an activity summary notification (e.g.,  FIG. 6M, 664  when the user interface is  FIG. 6N, 672 ). The activity summary notification can include: (1) a first notification element (e.g., information relating to an activity competition between the first and second user) (e.g.,  FIG. 6M, 666A ) based on the first user activity data and/or the second user activity data; and (2) a second notification element (e.g., information relating to an activity competition between the third user and the first user) (e.g.,  FIG. 6M, 666B ) based on at least third user activity data, different from the first user activity data and different than the second user activity data. 
     At  714 , the user interface (e.g.,  FIG. 6M, 664 , and  FIG. 6T, 697 ) includes a representation (e.g., graphical or textual indication of a value) (e.g.,  FIG. 6M, 670C ) of the first user activity data for the first time subset. 
     At  716 , the user interface (e.g.,  FIG. 6M, 664 , and  FIG. 6T, 697 ) further includes a representation (e.g., graphical or textual indication of a value) (e.g.,  FIG. 6M , Aled&#39;s representation for Tuesday) of the first user activity data for the second time subset. 
     At  718 , the user interface (e.g.,  FIG. 6M, 664 , and  FIG. 6T, 697 ) further includes a cumulative representation (e.g., a graphical or textual summary of activity data for the entire time period) (e.g.,  FIG. 6M , top right portion) of the first user activity data for the time period. The cumulative representation of the first user activity data for the time period is based on at least the first user activity data for a first time subset and the first user activity data for a second time subset. In some examples, the cumulative representation is presented in the same units as (or different units than) the representations of the activity data for the time subsets. 
     At  720 , the user interface (e.g.,  FIG. 6M, 664 , and  FIG. 6T, 697 ) further includes a representation (e.g.,  FIG. 6M, 670B ) of the second user activity data for the first time subset. Displaying scores for different users for a day provides feedback as to activity data received by the device for the day. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. The scores also provide an improved man-machine interface by reducing the number of interactions to display activity data information for multiple users. 
     In some examples, the representation of the second user activity data for the first time subset is displayed adjacent to (e.g., next to or in a first region of the user interface) the representation (e.g.,  FIG. 6M, 670C ) of the first user activity data for the first time subset. In some examples, the representation of the first user activity data for the first time subset is adjacent (e.g., without any interceding representations of activity data for other time subsets) to the representation of the second user activity data for the first time subset. Displaying a score for a first user adjacent to a score for a second user provides comparative feedback to physical activity being detected by the device. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     At  722 , the user interface (e.g.,  FIG. 6M, 664 , and  FIG. 6T, 697 ) further includes a representation (e.g.,  FIG. 6M , Molly&#39;s representation for Tuesday) of the second user activity data for the second time subset. Displaying scores for different days provides feedback as to activity data received by the device for different days. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. The scores also provide an improved man-machine interface by reducing the number of interactions to display activity data information for separate time subsets. 
     In some examples, the representation of the second user activity data for the second time subset is displayed adjacent to (e.g., next to or in a second region of the user interface) the representation (e.g.,  FIG. 6M , Aled&#39;s representation for Tuesday) of the first user activity data for the second time subset and is not displayed adjacent to representations of second user activity data for any other time subsets. 
     At  724 , the user interface (e.g.,  FIG. 6M, 664 , and  FIG. 6T, 697 ) further includes a cumulative representation (e.g.,  FIG. 6M, 668A, 668B, and 669C ) of the second user activity data for the time period. The cumulative representation of the second user activity data for the time period can be based on at least the second user activity data for a first time subset and the second user activity data for a second time subset. Displaying total scores for users provides feedback as to activity data being received by the device for the first user and the second user. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. Displaying total scores for users provides feedback as to activity data being received by the device for the first user and the second user. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, the first time subset of the first user activity data corresponds to the first time subset of the second user activity data. 
     In some examples, the user interface (e.g.,  FIG. 6M, 664 , and  FIG. 6T, 697 ) can further include a representation (e.g., a textual representation; a graphical representation) (e.g.,  FIG. 6M, 670F ) of the number of remaining time subsets in the time period. 
     In some examples, the user interface (e.g.,  FIG. 6M, 664 , and  FIG. 6T, 697 ) includes an identification of a current time subset (e.g.,  FIG. 6M , “F” in first activity competition), where the identification of the current time subset is visually emphasized (e.g.,  FIG. 6M , circle around “F”). 
     In some examples, a length of the first time subset is equal to a length of the second time subset (e.g.,  FIG. 6M , Monday through Sunday). 
     In some examples, displaying the user interface (e.g.,  FIG. 6M, 664 , and  FIG. 6T, 697 ) can further include: (1) in accordance with a determination that a first value (e.g.,  FIG. 6M , “ 2136 ”) corresponding to the cumulative representation of the first user activity data exceeds a second value (e.g.,  FIG. 6M , “ 2303 ”) corresponding to the cumulative representation of the second user activity data, visually emphasizing (e.g., highlighting) the cumulative representation of the first user activity data for the time period; and (2) in accordance with a determination that the second value exceeds the first value, visually emphasizing (e.g.,  FIG. 6M, 668A ) the cumulative representation of the second user activity data for the time period. 
     In some examples, the representations can be normalized. 
     In some examples, the representations can be based upon percentage completion of one or more goals. Optionally, the one or more goals are user defined. 
     In some examples, the first user activity data corresponds to a first user and the second user activity data corresponds to a second user. In such examples, prior to displaying the user interface (e.g.,  FIG. 6M, 664 , and  FIG. 6T, 697 ), the device displays a competition completion user interface (e.g., an interface showing details of a previously completed competition) (e.g.,  FIG. 6P, 680 ). The competition completion user interface can include a representation (e.g.,  FIG. 6P , Aled&#39;s portion of graph) of activity data for the first user for a preceding time period (e.g.,  FIG. 6P , Monday through Sunday), a representation (e.g.,  FIG. 6P , Molly&#39;s portion of graph) of activity data for the second user for the preceding time period, and a new competition initiation affordance (e.g.,  FIG. 6P, 684C ). The competition completion user interface can also include content (e.g.,  FIG. 6P , text at top of  680 ) based upon whether the first user or the second user had more activity data for the preceding time period. In such examples, the device receives a first user input (e.g.,  FIG. 6P, 611  but on wrong device) corresponding to selection of the new competition initiation affordance and, in response to receiving the first user input, initiates a process for an activity competition between the first user and the second user (e.g., sending an invitation to the second user to accept/start a competition between the first and second user). In such examples, the user interface is displayed after (e.g., in response to the second user accepting the invitation to start the competition) initiating the process for an activity competition between the first user and the second user. Providing different entry points to activity competitions provides increased interaction with the device by allowing the initiation of activity competitions to be available in an intuitive manner and in multiple locations. Providing entry points as described herein increases user participation in activity competitions, enhances the operability of the device, and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, while displaying the user interface, the device receives a second user input corresponding to a request to display additional information corresponding to the first user activity data and/or the second user activity data. In such examples, in response to receiving the second user input, the device displays a second user interface including additional information corresponding to the first user activity data and/or the second user activity data. In such examples, the additional information was not included in the user interface. In some examples, the additional information includes contact information, daily average, actual number of points corresponding to activity data for particular days, or the like. In some examples, the additional information functionality occurs when the affordance is included in an alert rather than a notification, where an alert must be dismissed before looking at other content using the device and a notification is available for a user to view in the background. 
     In some examples, while displaying the user interface, the device receives a third user input corresponding to a request to display a messaging user interface (e.g.,  FIG. 6I, 646 ) for sending a message to an external device (e.g.,  FIG. 6I, 600A ). In such examples, in response to receiving the third user input, the device displays the messaging user interface. In some examples, the messaging interface functionality occurs when the affordance is included in a notification rather than an alert. In some examples, the messaging user interface includes one or more predefined replies (e.g.,  FIG. 6I, 648 ). 
     In some examples, in response to user input at a location corresponding to a representation, the device displays a messaging user interface (e.g.,  FIG. 6I, 646 ). In other examples, in response to user input at a location corresponding to a representation, the device displays additional information regarding a second user corresponding to the second user activity data. 
     In some examples, the first user activity data includes standing data, moving data, and exercise data. 
     In some examples, the first user activity data corresponds to a first user and the second user activity data corresponds to a second user. In such examples, the user interface further can include a representation (e.g.,  FIG. 6M, 668A ) based on a comparison of activity data for the first user and the second user for one or more previous time periods, preceding the time period. 
     Note that details of the processes described above with respect to method  700  (e.g.,  FIGS. 7A-7B ) are also applicable in an analogous manner to the methods described below. For example, method  700  optionally includes one or more of the characteristics of the various methods described below with reference to method  900 , method  1100 , or method  1300 . For example, the user interface of method  700  can be included in an affordance for an activity competition of method  900 . For another example, the user interface of method  700  can be based upon activity data detected based upon the alert of method  1100 . For another example, the user interface of method  700  can include pace information detected based upon a pace configured as described in method  1300 . For brevity, these details are not repeated below. 
       FIGS. 8A-8Y  illustrate exemplary user interfaces related to a friends list for activity sharing in accordance with some examples. The activity sharing can include representations for activity competitions (as discussed above in  FIGS. 6A-6T and 7A-7B ). The friends list can also include affordances for initiating activity competitions in an intuitive manner, as further described below. 
     Referring to  FIG. 8A , user interface  804  (referred to as a home screen) is displayed on touch-sensitive display  802  of device  800 . For explanatory purposes, device  800  belongs to a first user, Aled. User interface  804  includes multiple affordances  806  for different applications, including affordance  806 A for an activity application. In  FIG. 8B , device  800  receives selection of affordance  806 A and, in response, causes a user interface (e.g., user interface  808  as depicted in  FIG. 8C ) corresponding to the activity application to be displayed. 
     Referring to  FIG. 8C , user interface  808  includes affordance  810 D for displaying a user interface corresponding to sharing activity data. As depicted in  FIG. 8C , affordance  810 D includes an indication that three notifications related to the user interface corresponding to sharing activity data are pending. In  FIG. 8D , device  800  receives selection of affordance  810 D and, in response, causes a user interface (e.g., user interface  812  as depicted in  FIG. 8E ) corresponding to sharing activity data to be displayed. 
       FIG. 8E  illustrates device  800  displaying user interface  812  (sometimes referred to as a friends list). User interface  812  includes first portion  814 A for information related to activity competitions and second portion  814 B for information related to friends. 
     As depicted in  FIG. 8E , first portion  814 A is above second portion  814 B such that first portion  814 A is displayed before (when scrolling through the interface) second portion  814 B. Displaying first portion  814 A before second portion  814 B can affect what is displayed when first portion  814 A and second portion  814 B include too much content to be displayed on touch-sensitive display  802 . For example, first portion  814 A will be displayed in its entirety before any of second portion  814 B when first portion  814 A is before second portion  814 B in user interface  812 . In such an example, content not included in touch-sensitive display  802  can be displayed by in response to a scrolling input. 
     First portion  812  includes a scrollable list of affordances  816 , where each affordance is associated with a different activity competition. For example, the scrollable list of affordances  816  includes first affordance  816 A for a first activity competition (between Molly and Aled) and second affordance  816 B for a second activity competition (between John and Aled). In some examples, the order of affordances for activity competitions can be based upon when the activity competitions are finishing. For example, activity competitions finishing sooner can be included in the scrollable list of affordances  816  before activity competitions finishing later. 
     First affordance  816 A includes information related to the first activity competition, such as a cumulative score for Molly (i.e.,  2303 ) and Aled (i.e.,  2136 , labeled “ME”), a number of times Molly has won a past activity competition between Molly and Aled (i.e., 23 times), a number of times Aled has won a past activity competition between Molly and Aled (i.e., 7 times), and an amount of time left in the first activity competition (i.e., 2 days left). Second affordance  616 B includes information related to the second activity competition, which can be similar to the information related to the first activity competition described above. It should be noted that, in some examples, affordances in the scrollable list of affordances  816  can include more or less information than depicted in  FIG. 8E , including an affordance including more information than another affordance. 
     Second portion  814 B includes a scrollable list of affordances  818 , where each affordance is associated with a different friend of a user (e.g., Aled) logged into device  800 . For example, the scrollable list of affordances  818  includes first affordance  818 A for a first friend (i.e., Jane), second affordance  818 B for a second friend (i.e., Molly), and third affordance  818 C for a third friend (i.e., John). It should be noted that, in some examples, friends included in second portion  814 B can also be included in an activity competition in first portion  814 A. For example, Molly is a participant of the first activity competition (e.g., first affordance  816 A) and included in the scrollable list of affordances  818  (e.g., second affordance  818 B). In other examples, friends included in first portion  814 A are not included in second portion  814 B. 
     Each affordance in the scrollable list of affordances  818  includes information related to the corresponding friend. For example, first affordance  818 A corresponds to Jane and includes an identification of Jane (e.g., “Jane”), a percent of goals for Jane that Jane has completed (e.g., “95%), an absolute amount of a goal that Joan has completed with the absolute amount of the goal (e.g., “400/450”), and icon  818 AA visually depicting an amount of multiple goals that Joan has completed. 
     User interface  812  further includes sharing affordance  820 . Selection of sharing affordance  820  causes device  800  to display a user interface (e.g., user interface  834  as depicted in  FIG. 8O ) with sharing details, as further described below with respect to  FIG. 8O . Sharing affordance  820  includes an indication that three notifications related to sharing data are pending. 
       FIG. 8F  again illustrates user interface  812  (as depicted in  FIG. 8E ). As described above, user interface  810  includes first affordance  816 A. Referring to  FIG. 8F , user input (e.g., tap input)  805  is received by device  800 , where user input  805  corresponds to selection of first affordance  816 A in first portion  814 A. In accordance with a determination that user input  805  is detected at first affordance  816 A in the scrollable list of affordances  816 , a user interface (e.g., user interface  822  as depicted in  FIG. 8G ) with additional information related to the first activity competition (not included in first affordance  816 A) is displayed. 
     Referring to  FIG. 8G , device  800  displays user interface  822  on touch-sensitive display  802  in response to selection of first affordance  816 A in first portion  814 A (as depicted in  FIG. 8F ). User interface  822  includes multiple representations  824  of information related to the first activity competition. For example, representation  824 A is a visual representation of Molly&#39;s current completion of activity goals for the current day. The visual representation includes three circles, each circle corresponding to a different goal. Representation  824 B includes information for the first activity competition, as discussed above in  FIG. 6T . Representation  824 C includes a current status (e.g., 50/500) for Molly completing a first goal (e.g., move goal). Representation  824 D includes a current status for Molly completing a second goal (e.g., exercise goal). It should be recognized that user interface  816  can include more or fewer representations of information related to the first activity competition than depicted in  FIG. 8G . 
     User interface  822  also includes back affordance  826  to cause a previous user interface (e.g., user interface  812  as depicted in  FIG. 8E ) to be displayed. Referring to  FIG. 8H , user input (e.g., tap input)  807  is received, where user input  807  corresponds to selection of back affordance  826 . In accordance with a determination that user input  807  is detected at back affordance  826 , a user interface (e.g., user interface  812  as depicted in  FIG. 8I ) is displayed. 
       FIG. 8I  illustrates device  800  displaying user interface  812  in response to selection of back affordance  826  (as depicted in  FIG. 8H ). As described above, user interface  812  includes first affordance  818 A in second portion  814 B. Referring to  FIG. 8J , user input (e.g., tap input)  809  is received, where user input  809  corresponds to selection of first affordance  818 A. In accordance with a determination that user input  809  is detected at first affordance  818 A, a user interface (e.g., user interface  812  as depicted in  FIG. 8I ) with information related to a friend (e.g., Jane) corresponding to first affordance  818 A is displayed. 
     Referring to  FIG. 8K , device  800  displays user interface  828  on touch-sensitive display  802  in response to selection of first affordance  818 A in second portion  814 B (as depicted in  FIG. 8J ). User interface  828  includes multiple representations  830  of information related to Jane. For example, representation  830 A is a visual representation of Jane&#39;s current completion of activity goals for the current day. The visual representation includes three circles, each circle corresponding to a different goal. Representation  830 B includes information related to past activity competitions between Jane and Aled. For example, icon  830 BA indicates a number (e.g., 7) of past activity competitions that Jane beat Aled (e.g., “ME”) and icon  830 BB indicates a number (e.g., 2) of past activity competitions that Aled beat Jane. Representation  830 C includes a current status (e.g., 400/500) for Jane completing a first goal (e.g., move goal). 
     User interface  828  also includes invite affordance  831  to initiate a process for beginning an activity competition between Jane and Aled. For explanatory purposes, selection of invite affordance  831  can cause user interface  616  (as depicted in  FIG. 6C ) or user interface  686  (as depicted in  FIG. 6Q ) to be displayed on touch-sensitive display  802 . 
     Referring to  FIG. 8K , user interface  828  also includes back affordance  832  to cause a previous user interface (e.g., user interface  812  as depicted in  FIG. 8J ) to be displayed. Referring to  FIG. 8L , user input (e.g., tap input)  811  is received, where user input  811  corresponds to selection of back affordance  832 . In accordance with a determination that user input  811  is detected at back affordance  832 , a user interface (e.g., user interface  812  as depicted in  FIG. 8M ) is displayed. 
       FIG. 8M  illustrates device  800  displaying user interface  812  in response to selection of back affordance  832  (as depicted in  FIG. 8L ). As described above, user interface  812  includes sharing affordance  820 . Referring to  FIG. 8N , user input (e.g., tap input)  813  is received, where user input  813  corresponds to selection of sharing affordance  820 . In accordance with a determination that user input  813  is detected at sharing affordance  820 , a user interface (e.g., user interface  834  as depicted in  FIG. 8O ) is displayed. 
     Referring to  FIG. 8O , device  800  displays user interface  834  on touch-sensitive display  802  in response to selection of sharing affordance  820  (as depicted in  FIG. 8N ). User interface  834  is divided into multiple portions (e.g., first portion  836  and second portion  838 ), each portion including a different type of information. 
     First portion  836  includes information related to invitations for activity competitions received by device  800 . For example, first portion  836  includes invitation  836 A. Invitation  836 A indicates that Tom has sent an invitation to begin an activity competition to Aled (e.g., to one or more devices (e.g., device  800 ) associated with Aled). Invitation  836 A includes an accept affordance and an ignore affordance in order to respond to the invitation from Tom. Selection of the accept affordance initiates a process to begin an activity competition between Tom and Aled. Selection of the ignore affordance removes invitation  836 A from first portion  836 . 
     Second portion  838  includes information related to invitations for activity competitions sent by device  800 . For example, second portion  838  includes invitation  838 A. Invitation  838 A indicates that Aled has sent an invitation to begin an activity competition to Jane. Invitation  838 A includes a representation of the amount of time that remains for Jane to accept the invitation. 
       FIG. 8P  illustrates device  600 B (e.g., a second device associated with the same user, Aled) displaying user interface  840  on touch-sensitive display  602 B. User interface  840 , like user interface  812  (as depicted in  FIG. 8E ), corresponds to a friends list. However, unlike user interface  812 , user interface  840  is configured to be used on an electronic device with a smaller display area than device  800 . 
     Similar to user interface  812 , user interface  830  includes first portion  842 A and second portion  842 B. As depicted in  FIG. 8P , first portion  842 A is above second portion  842 B such that first portion  842 A is displayed before second portion  842 B. Displaying first portion  842 A before second portion  842 B can affect what is displayed when first portion  842 A and second portion  842 B include too much content to be displayed on touch-sensitive display  602 B. For example, first portion  842 A will be displayed in its entirety before any of second portion  842 B when first portion  842 A is before second portion  842 B in user interface  812 . In such an example, content not included in touch-sensitive display  802  can be displayed by in response to a scrolling input (e.g., rotation of rotatable input mechanism  604 A). 
     Referring to  FIG. 8P , first portion  842 A includes a scrollable list of affordances  844 , where each affordance is associated with a different activity competition. For example, the scrollable list of affordances  844  includes first affordance  844 A for a first activity competition (between Molly and Aled) and second affordance  816 B for a second activity competition (between John and Aled). In some examples, the order of affordances for activity competitions can be based upon when the activity competitions are finishing. For example, activity competitions finishing sooner can be included in the scrollable list of affordances  844  before activity competitions finishing later. 
     First affordance  844 A includes information related to the first activity competition, such as a cumulative score for Molly (i.e.,  2303 ) and Aled (i.e.,  2136 ), a number of times Molly has won a past activity competition between Molly and Aled (i.e., 23 times), a number of times Aled has won a past activity competition between Molly and Aled (i.e., 7 times), and an amount of time left in the first activity competition (i.e., 2 days left). Second affordance  616 B includes information related to the second activity competition, which can be similar to the information related to the first activity competition described above. It should be noted that, in some examples, affordances in the scrollable list of affordances  816  can include more or less information than depicted in  FIG. 8E , including an affordance including more information than another affordance. 
     It should also be noted that while user interface  840  is depicted as having the same information in first portion  842 A as user interface  812  in first portion  814 A, an organization of the information in user interface  840  is different than an organization of the information in user interface  812 . The difference in organization can be because of touch-sensitive display  602 B having a smaller display area than touch-sensitive display  802 . 
     Second portion  842 B includes a scrollable list of affordances  846 , where each affordance is associated with a different friend of a user (e.g., Aled) logged into device  800 . For example, the scrollable list of affordances  846  includes first affordance  846 A for a first friend (i.e., Jane), second affordance  846 B for a second friend (i.e., Molly), third affordance  846 C for a third friend (i.e., John), and fourth affordance  846 D for a fourth friend (i.e., Tom). It should be noted that, in some examples, friends included in second portion  842 B can also be included in an activity competition in first portion  842 A. For example, Molly is a participant of the first activity competition (e.g., first affordance  842 A) and included in the scrollable list of affordances  846  (e.g., second affordance  846 B). In other examples, friends included in first portion  842 A are not included in second portion  842 B. 
     Each affordance in the scrollable list of affordances  846  includes information related to the corresponding friend. For example, first affordance  846 A corresponds to Jane and includes an identification of Jane (e.g., “Jane”), a percent of goals for Jane that Jane has completed (e.g., “95%), an absolute amount of a goal that Joan has completed with the absolute amount of the goal (e.g., “400/450”), and an icon visually depicting an amount of multiple goals that Joan has completed. 
       FIG. 8P  depicts some information related to a friend not illustrated in  FIG. 8E . Such information can also be included in  FIG. 8E . For example, second affordance  846 B in second portion  842 B includes icon  846 BA. Icon  846 BA indicates that Aled has won an activity competition between Aled and Molly. Icon  846 BA can be a unique identification of activity competitions between Aled and Molly such that other icons for other activity competitions between other participants have a different theme (as depicted for icon  846 CA). 
       FIG. 8P  also depicts invitation icon  842  included in third affordance  846 D in second portion  842 B. Invitation icon  842  indicates that a friend corresponding to third affordance  846 D (e.g., Tom) has sent an invitation to compete in an activity competition with Aled. Invitation icon  842  also includes a number indicating how many invitations from Tom have been received. 
       FIG. 8Q  again illustrates user interface  840  (as depicted in  FIG. 8P ). As described above, user interface  810  includes fourth affordance  846 D with invitation icon  842 . Referring to  FIG. 8Q , user input (e.g., tap input)  815  is received, where user input  815  corresponds to selection of invitation icon  842  or fourth affordance  846 D (depending upon how user interface  840  is configured). In accordance with a determination that user input  815  is detected at invitation icon  842  (or fourth affordance  846 D), a user interface (e.g., user interface  848  as depicted in  FIG. 8R ) is displayed. 
     Referring to  FIG. 8R , device  800  is displaying user interface  848  in response to selection of invitation icon  842  (or fourth affordance  846 D) (as depicted in  FIG. 8Q ). User interface  848  indicates that Tom has invited Aled to a 7 day activity competition. User interface  848  includes activity data for Tom for a current day. User interface  848  further includes a scrollable list of affordances  850 , where each affordance is associated with a different operation. For example, the scrollable list of affordances  850  includes first affordance  850 A and second affordance  850 B. 
     Selection of first affordance  850 A can accept the invitation for the activity competition sent by Tom. Acceptance of the invitation can cause the activity competition to begin at a predefined time after the selection (e.g., midnight of the current day), as further described below. Selection of second affordance  850 B can cause device  600 B to reject the invitation (e.g., cause the activity competition to not begin) and cease to display user interface  848 . Selection of second affordance  850 B can further cause invitation icon  842  to be removed from fourth affordance  846 D. 
       FIG. 8S  again illustrates user interface  848  (as depicted in  FIG. 8R ). As described above, user interface  810  includes first affordance  850 A. Referring to  FIG. 8S , user input (e.g., tap input)  817  is received, where user input  817  corresponds to selection of first affordance  850 A. In accordance with a determination that user input  817  is detected at first affordance  850 A, a user interface (e.g., user interface  852  as depicted in  FIG. 8T ) is displayed. 
     Referring to  FIG. 8T , device  600 B displays user interface  852  in response to selection of first affordance  850 A in user interface  848  (as depicted in  FIG. 8S ). User interface  852  indicates that an activity competition between Tom and Aled starts tomorrow. User interface  852  includes icon  854 , which represents activity competitions between Tom and Aled. User interface also includes affordance  856 . Selection of affordance  856  causes device  600 B to cease to display user interface  852 . 
       FIG. 8U  again illustrates user interface  808  (as depicted in  FIG. 8C ). User interface  810  includes third affordance  810 C. In response to selection of third affordance  810 C (as depicted in  FIG. 8V ), device  800  displays user interface  858  (as depicted in  FIG. 8W ). 
     Referring to  FIG. 8W , user interface  858  (sometimes referred to as a trophy case) relates to awards that have been given to Aled. User interface  858  is divided into multiple portions  860 , where each portion includes a different type of award. For example, portions  860  includes recents  860 A, competitions  860 B, monthly challenges  860 C, achievements  860 D, and workouts  860 E. 
     Each portion can include one or more awards associated with a corresponding type of award. For example, recents  860  can include awards that have been awarded within a particular amount of time from a current time. In some examples, awards in recents  860  can be larger than awards in other portions. Competitions  860 B can include awards that have been awarded for activity competitions. Monthly challenges  860 C can include awards that have been predefined as a monthly challenge. Achievements  860 D can include awards that have been predefined as an achievement. Workouts  860 E can include awards that have been awarded using a workout application (as described herein). 
     In some examples, some awards in a portion might not be visible. In such examples, the awards can be navigated by side scrolling through them. 
     Display of awards in user interface  858  can differ based upon the particular award. For example, a representation for an award that is received only once on a particular day can include an icon (e.g., icon  862 A), an identification of the award (e.g., identification  862 B), and a date that the award was received (e.g., date  862 C). In some examples, a representation for an award that is received only once on a particular day can include an icon (e.g., icon  862 A), an identification of the award (e.g., identification  862 B), and further information related to achieving the award, such as a number of calories burned which satisfied at least a minimum amount for the award (e.g., calories  872 C). In such examples, the representation might not include a date that the award was received because the identification indicates the date. 
     For another example, a representation for an award that is received multiple times can include an icon (e.g., icon  864 A or  866 A), an identification of the award (e.g., identification  864 B or  866 B), and a number of times that the award has been received (e.g., number  864 D or  866 C). In some examples, the representation for an award that is received multiple times can also include a date that the award has last been received (e.g., date  864 C). In such examples, the representation can also include the date when the award is predefined as hard to receive or the award has been received below a particular number of times. 
     It should be noted that each icon for each award in competitions  860 B (e.g., icons  866 A,  868 A, and  870 A) is different. This can be due to each activity competition being assigned a different representation, as discussed herein. 
       FIG. 8X  again illustrates user interface  858  (as depicted in  FIG. 8W ). User interface  810  includes icon  866 A of representation  866 . In response to selection of icon  866 A (or representation  866 ) (as depicted in  FIG. 8X ), device  800  displays user interface  876  (as depicted in  FIG. 8X ). Referring to  FIG. 8X , user interface  876  includes icon  878 A (which corresponds to icon  866 A (as depicted in  FIG. 8W ), identification  873 B of an award corresponding to icon  878  (which corresponds to identification  866 B), and further information not included in representation  866  (as depicted in  FIG. 8W ). The further information includes a description of the award (reference  878 C) and a date that the award was last received (reference  878 D). 
       FIGS. 9A-9B  include a flow diagram illustrating a method for displaying a friends list representation using an electronic device in accordance with some examples. Method  900  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 A,  600 B,  800 ) with a display. Some operations in method  900  are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  900  provides an intuitive way for displaying a user interface on a device corresponding to a first user, where the user interface includes affordances for multiple activity competitions, where each activity competition (1) is between the first user and another user and (2) is represented by current scores for the activity competition and a number of days remaining in the activity competition. The user interface permits a user viewing the user interface to readily access physical activity data corresponding to multiple users. The method reduces the cognitive burden on a user for accessing physical activity data corresponding to multiple user, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to access physical activity data corresponding to multiple users faster and more efficiently conserves power and increases the time between battery charges. 
     At  902 , the device (e.g.,  FIG. 8A, 800 ) receives first user activity data (e.g.,  FIG. 8C , data represented in  FIG. 8C ) for a first user (e.g., Aled), where the first user activity data corresponds to a first time period (e.g., a day, a week, a month, a duration of an activity competition between the first user and a second user) (e.g.,  FIG. 8I , Monday through Sunday for activity competition with Molly) and a second time period (e.g., a day, a week, a month, a duration of an activity competition between the first user and a user; a time period different than the first time period) (e.g.,  FIG. 8I , Thursday through Wednesday for activity competition with John). In some examples, the first user activity data is received via one or more sensors of the device. 
     In some examples, a length (e.g.,  FIG. 8I , 7 days for activity competition with Molly) of the first time period is the same as a length (e.g.,  FIG. 8I , 7 days for activity competition with John) of the second time period. In some examples, a length of the first time period is different from a length of the second time period. In some examples, the first time period and the second time period overlap (e.g.,  FIG. 8I , activity competition with Molly and activity competition with John). 
     At  904 , the device (e.g.,  FIG. 8A, 800 ) receives second user activity data (e.g.,  FIG. 8H , data represented by representations for Molly) for a second user (e.g.,  FIG. 8I , Molly), where the second user activity data corresponds to the first time period, and where the first time period includes a first elapsed (e.g., completed) sub-period (e.g.,  FIG. 8H , Monday through Friday) and a first unelapsed (e.g., remaining) sub-period (e.g.,  FIG. 8H , Saturday through Sunday) for an activity competition (e.g.,  FIG. 8H ) between the first user and the second user. In some examples, the second user activity data is received (e.g., via one or more antennas of the device) by the device from a second device (e.g., a device associated with Molly). 
     At  906 , the device (e.g.,  FIG. 8A, 800 ) receives third user activity data (e.g.,  FIG. 8I , data represented by representations for John) for the third user (e.g.,  FIG. 8I , John), where the third user activity data corresponds to the second time period, and where the second time period includes a second elapsed sub-period (e.g.,  FIG. 8I , Thursday through Friday) and a second unelapsed sub-period (e.g.,  FIG. 8I , Saturday through Wednesday) for an activity competition (e.g.,  FIG. 8I , activity competition with John) between the first user and the third user. In some examples, the third user activity data is received (e.g., via one or more antennas of the device) by the device from a third electronic device (e.g., a device associated with John). 
     In some examples, the activity competition between the first user and the second user began at a first time (e.g.,  FIG. 8I , Monday), and where the activity competition between the first user and the third user began at a second time (e.g.,  FIG. 8I , Thursday) different from the first time. 
     At  908 , the device (e.g.,  FIG. 8A, 800 ) displays, on the display (e.g.,  FIG. 8A, 802 ), a user interface (e.g.,  FIG. 8E, 812 ). In some examples, the user interface is for a friends list. 
     At  910 , the user interface (e.g.,  FIG. 8E, 812 ) includes a representation (e.g.,  FIG. 8E, 816A ) of the first user activity data and the second user activity data during the first elapsed sub-period for the activity competition between the first user and the second user. In some examples, the representation of the first activity data and the second activity data is a score for each of the first user and the second user. 
     At  912 , the user interface (e.g.,  FIG. 8E, 812 ) includes an indication of an amount of time in the first unelapsed sub-period (e.g.,  FIG. 8E, 816A  with “2 days left”) for the activity competition between the first user and the second user. In some examples, the indication is a remaining amount of time in the activity competition. 
     At  914 , the user interface (e.g.,  FIG. 8E, 812 ) includes a representation (e.g.,  FIG. 8E, 816B ) of the first activity data and the third activity data during the second elapsed sub-period for the activity competition between the first user and the third user. In some examples, the representation of the first activity data and the third activity data is a score for each of the first user and the third user. Displaying information for multiple activity competitions provides feedback as to activity data being received by the device for multiple different users. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. The information for multiple activity competitions also provides an improved man-machine interface by reducing number of interactions to display information for different activity competitions. 
     At  916 , the user interface (e.g.,  FIG. 8E, 812 ) includes an indication of an amount of time in the second unelapsed sub-period (e.g.,  FIG. 8E, 816B  with “5 days left”) for the activity competition between the first user and the third user. Displaying remaining time in activity competitions provides feedback as to activity data to be received in the future. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. The remaining time also provides an improved man-machine interface by increasing an amount of sustained interaction with the device based upon an amount of the remaining time. 
     In some examples, the user interface (e.g.,  FIG. 8E, 812 ) further comprises: (1) a first portion (e.g.,  FIG. 8E, 814A ) including the representations and the indications; and (2) a second portion (e.g.,  FIG. 8E, 814B ) visually distinct from the first portion, the second portion including: (1) a first affordance (e.g.,  FIG. 8E, 818A ) with an identification (e.g.,  FIG. 8E , “Jane) of the second user; (2) a second affordance (e.g.,  FIG. 8E, 818B ) with an identification (e.g.,  FIG. 8E , “Molly”) of the third user; and (3) a third affordance (e.g.,  FIG. 8E, 818C ) with an identification (e.g.,  FIG. 8E , “John”) of a fourth user not in an active activity competition with the first user. Displaying competing friends different than non-competing friends provides feedback as to data received by the device (e.g., where the data is coming from). Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. Displaying a first set of friends differently from a second set of friends also provides an improved man-machine interface by emphasizing one set of friends over another. 
     In some examples, the third affordance includes a notification (e.g.,  FIG. 8P, 842 ) that the fourth user has requested to initiate an activity competition between the first user and the fourth user. In such examples, the device receives a first user input (e.g.,  FIG. 8Q, 815 ) corresponding to selection of the third affordance. In response to receiving the first user input, the device initiates a process for starting an activity competition between the first user and the fourth user, where the activity competition between the first user and the fourth user causes first user activity data and fourth user activity data to be received during a time period (e.g., 7 days starting from when the activity competition between Tom and Aled begins). Displaying an additional entry point for an activity competition next to a friend&#39;s name in a friends list provides feedback as to pending requests from user&#39;s in an intuitive location. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, the notification is removed from the third affordance after an amount of time (e.g., 48 hours) has passed since the fourth user sent a corresponding request to initiate the activity competition between the first user and the fourth user. 
     In some examples, while displaying the user interface (e.g.,  FIG. 8E, 812 ), the device (e.g.,  FIG. 8A, 800 ) receives a second user input (e.g., an input corresponding to the representation of the first user activity data and the second user activity data) (e.g.,  FIG. 8F, 805 ) corresponding to a request to display additional information regarding the activity competition between the first user and the second user. In response to receiving the second user input, the device displays a second user interface (e.g.,  FIG. 8G, 822 ) including the additional information. In some examples, the additional information includes (1) a representation (e.g.,  FIG. 8E , “Me”) of the first user activity data during a portion of the first elapsed sub-period for the activity competition between the first user and the second user and (2) a representation (e.g.,  FIG. 8G, 824B ) of the second user activity data during the portion of the first elapsed sub-period for the activity competition between the first user and the second user. 
     In some examples, the representation of the first user activity data and the second user activity data includes: an identification of the first user (e.g.,  FIG. 8E , “Me”); an identification of the second user (e.g.,  FIG. 8E , “Molly”); and a representation based on a comparison of activity data for the first user and the second user for one or more previous time periods, preceding the time period (e.g.,  FIG. 8E , “23” in  816 A) 
     In some examples, the third affordance (e.g.,  FIG. 8P, 846C ) includes a first icon (e.g., a graphical element) (e.g.,  FIG. 8P, 846CA ) indicating previous (e.g., assigned to) activity competitions between the first user and the fourth user. 
     In some examples, selection of the fourth affordance (e.g.,  FIG. 8J, 809 ) causes a user interface (e.g.,  FIG. 8K, 828 ) to be displayed with a representation (e.g.,  FIG. 8K, 830BA ) indicating previous activity competitions between the first user and the fourth user. 
     In some examples, the second affordance includes a second icon indicating previous activity competitions between the first user and the third user, where the first icon has a first visual theme (e.g., a shape, a background color or pattern, and where the second icon with a second visual theme different from the first visual theme. In some examples, two graphical indications may share a common visual theme, while differing in non-thematic visual elements (e.g., such as a number or initials that are not part of the visual theme. In some examples, unique visual themes are assigned to each other user (e.g., a second user, a third user) that has been, or is currently, in a competition with the user of the electronic device (e.g., the first user. 
     In some examples, icons for different activity competitions between the same two participants are the same. 
     In some examples, while displaying the user interface, receiving a third user input (e.g.,  FIG. 8V, 819 ) corresponding to a request to display an awards user interface (e.g.,  FIG. 8W, 858 ); in response to receiving the third user input, the device displays, on the display, a third user interface (e.g.,  FIG. 8W, 858 ) including: a first portion (e.g.,  FIG. 8W, 860B ) corresponding to a first type of icons, where the first type of icons relates to activity competitions, where the first portion includes the first icon (e.g.,  FIG. 8W, 866A ) and the second icon (e.g.,  FIG. 8W, 868A ); and a second portion (e.g.,  FIG. 8W, 860E ) corresponding to a second type of icons, where the second portion includes a third icon (e.g.,  FIG. 8W , star icon). In some examples, the third user interface is a trophy case. In some examples, the first portion includes icons related to activity competitions. In some examples, the second portion includes icons related to workouts. In some examples, the third user interface further includes a third portion (e.g.,  FIG. 8W, 860A ) corresponding to icons recently received, where icons included in the third portion are visually distinct (e.g., bigger) than icons in other portions. In some examples, icons in a portion are configured to be side scrolled. 
     In some examples, the third user interface, for an icon (e.g.,  FIG. 8W, 864 ) included in the third user interface, includes one or more of the following adjacent to the icon: an identification of the icon (e.g.,  FIG. 8W, 864B ) and a number of times the icon has been earned (e.g.,  FIG. 8W, 864D ). 
     In some examples, the device receives a fourth user input (e.g.,  FIG. 8Q, 815 ) corresponding to selection of the third affordance. In response to receiving the fourth user input, the device displays a third user interface (e.g.,  FIG. 8R, 848 ) comprising a competition initiation affordance (e.g.,  FIG. 8R, 850A ). The device receives a fifth user input (e.g.,  FIG. 8S, 817 ) corresponding to the competition initiation affordance. In response to receiving the fifth user input, the device initiates an activity competition between the first user and the fourth user, where the activity competition between the first user and the fourth user causes first user activity data and fourth user activity data to be received during a third time period. 
     In some examples, the representation of the first user activity data and the second user activity data during the first elapsed sub-period for the activity competition between the first user and the second user is based upon a two-tier scoring system, where scoring changes when a user reaches a threshold (e.g., bonus points). 
     In some examples, while displaying the user interface, the device receives, using a rotatable input mechanism (e.g., an input mechanism that can rotate relative to a housing of the device) (e.g.,  FIG. 8P, 604A ) of the device, a sixth user input. In response to receiving the sixth user input, the device updates the user interface to display a fourth affordance for a fifth user, where the fourth affordance is not visible prior to receiving the sixth user input. 
     Note that details of the processes described above with respect to method  900  (e.g.,  FIGS. 9A-9B ) are also applicable in an analogous manner to the methods described below/above. For example, method  900  optionally includes one or more of the characteristics of the various methods described below with reference to method  700 , method  1100 , or method  1300 . For example, the user interface of method  900  can lead to (e.g., by selecting an affordance in first portion) to the user interface of method  700 . For another example, the user interface of method  1100  can generate activity data that is represented in the user interface of method  900 . For another example, the user interface of method  1300  can generate activity data that is represented in the user interface of method  900 . For brevity, these details are not repeated below. 
       FIGS. 10A-10Q  illustrate exemplary user interfaces associated with alerts presented to a user in response to automatically determining a boundary of a workout in accordance with some examples. For example,  FIG. 10A  depicts an alert presented in response to automatically determining a beginning of a workout and  FIG. 10D  depicts an alert presented in response to automatically determining an end of a workout. Such alerts reduce the need for a user to remember to start and/or end a workout. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIG. 11 . 
     Referring to  FIG. 10A , user interface  1004  of a workout application is displayed on touch-sensitive display  602 A of device  600 A. In some examples, user interface  1004  is displayed in response to a determination that a user wearing device  600 A has begun an outdoor run. The determination can be based upon data detected by one or more sensors associated with device  600 A. For example, device  600 A can include or be paired with a heart-rate monitor and a GPS sensor. In response to heart-rate information detected by the heart-rate monitor and GPS information detected by the GPS sensor, device  600 A (or a device connected to device  600 A) can determine that the user is likely running outside. 
     User interface  1004  includes a scrollable list of affordances  1006 , where each affordance is associated with a different operation. For example, the scrollable list of affordances  1006  includes start affordance  1006 A, change affordance  1006 B, and dismiss affordance  1006 C. Start affordance  1006 A causes a physical activity tracking function configured for outdoor runs to be launched. Change affordance  1006 B allows a user to pick a different type of workout such that a physical tracking function configured for the different type of workout is launched. Dismiss affordance  1006 C causes user interface  1004  to cease to display. 
     User interface  1004  further includes physical activity icon  1008  corresponding to the outdoor run. Physical activity icon  1008  is an icon of a runner. In various examples, physical activity icon  1008  is displayed in an animated state, as further illustrated in  FIG. 10I . 
     In some examples, content included in user interface  1004  might not fit within touch-sensitive display  602 A; in which case content not displayed can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism  604 A). 
     In some examples, an alert (e.g., user interface  1004 ) is reissued (e.g., re-displayed or a new alert corresponding to the alert is displayed) after an amount of time (e.g., a predetermined amount of time) has passed without causing the alert to be dismissed (e.g., selecting an affordance in the scrollable list of affordances  1006 ). For example, if a user does not select an affordance in the scrollable list of affordances  1006  within 3 minutes, a new user interface that is the same or similar to user interface  1004  is displayed on touch-sensitive display  602 A of device  600 A. In some examples, if the user does select an affordance (e.g., dismiss affordance  1006 A) within three minutes of user interface  1004  being displayed, user interface  1004  is not reissued after 3 minutes. While 3 minutes is used as an example, it should be recognized that a different amount of time may be used. 
     In some examples, the alert is only reissued when the alert has been interrupted (e.g., user interface  1004  is no longer being displayed due to another alert). In some examples, if the alert has not been interrupted, the alert remains (e.g., continues to be displayed and/or is displayed whenever touch-sensitive display  602 A transitions from an inactive state to an active state) for a particular amount of time. In some examples, the particular amount of time is based on a type of workout corresponding to the alert. For example, if the alert corresponds to swimming, the alert can remain for 60 minutes; and if the alert corresponds to running or some other type of workout other than swimming, the alert can remain for 30 minutes. In some examples, a notification corresponding to user interface  1004  can be sent to a notification center such that a user is able to view the notification after user interface  1004  ceases to display. 
     In some examples, prior to displaying user interface  1004 , user interface  1064  is displayed on touch-sensitive display  602 A of device  600 A, as depicted in  FIG. 10L . In such examples: user interface  1064  is displayed in response to the determination that a user wearing device  600 A has begun an outdoor run, and user interface  1004  is displayed after displaying user interface  1064  (e.g., in response to user interface  1004  being displayed for a particular amount of time). In some examples, when user interface  1064  is displayed, user interface  1004  is displayed in response to a determination that a set of one or more short-look criteria has been met and user interface  1064  is displayed in response to a determination that a set of one or more long-look criteria has been met, as discussed below. 
     As depicted in  FIG. 10L , user interface  1064  includes physical activity icon  1066  corresponding to the outdoor run. In various examples, physical activity icon  1064  is displayed in an animated state, as further illustrated in  FIG. 10I . In some examples, content such as physical activity icon  1064  is included in both user interface  1064  and user interface  1004  (where it is referred to as physical activity icon  1008 ). In such examples, user interface  1004  includes additional content that is not included in user interface  1064 , such as the scrollable list of affordances  1006 . User interface  1064  further includes text to indicate that user interface  1064  is being displayed because it has been determined that the user is running (e.g., “Looks like you&#39;re running”). 
     In some examples, user interface  1064  is displayed in response to detecting a user input within a first time interval following a perceptual output (e.g., thereby satisfying short-look criteria). Information in user interface  1064  may be referred to as first portion of information. In such examples, after raising a user&#39;s wrist to view user interface  1064 , the user may then wish to view more information associated with user interface  1064 . If device  600 A determines that the user continues to maintain device  600 A in a viewing position for a predetermined time interval (e.g., thereby satisfying a long-look criteria) after displaying user interface  1064 , device  600 A displays user interface  1004 , which may be referred to as a second portion of the information. That is, in some examples, device  600 A can automatically transition from displaying user interface  1064  to displaying user interface  1004  when the user holds device  600 A in a viewing position and waits. 
       FIG. 10B  again illustrates user interface  1004  (as depicted in  FIG. 10A ). As described above, user interface  1004  includes start affordance  1006 A. Referring to  FIG. 10B , user input (e.g., tap input)  1001  is received, where user input  1001  corresponds to selection of start affordance  1006 A. In accordance with a determination that user input  1001  is detected at start affordance  1006 A in the scrollable list of affordances  1006 , a physical activity tracking function configured for outdoor runs is launched. 
     In response to selection of start affordance  1006 A, user interface  1026  (which is depicted in  FIG. 10C ) is displayed. User interface  1026  displays (e.g., provide feedback regarding) data detected by device  600 A for the outdoor run. In some examples, the displayed data can be based upon data detected prior to selection of start affordance  1006 A and/or prior to display of user interface  1004 . For example, a preliminary determination that the user is performing the outdoor run can be made. At some time after the preliminary determination, a final determination that the user is performing the outdoor run can be made, the final determination causing user interface  1004  to be displayed. In such an example, all data since the preliminary determination can be used when calculating data to display in user interface  1026 . For another example, in response to selection of start affordance  1006 A, an amount of data prior to the selection can be determined to likely (e.g., above a threshold) be associated with the outdoor run, where the amount of data is used when calculating data to display in user interface  1026 . 
     To display the data detected by device  600 A, user interface  1026  includes representations  1028 . In  FIG. 10C , representations  1028  include total mileage  1028 A (e.g., an indication of a number of miles traveled during the outdoor run), average pace per mile  1028 B (e.g., an indication of an average amount of time it has taken for device  600 A to travel a mile during the outdoor run), total time  1028 C (e.g., an indication of a duration of the outdoor run), and total calories  1028 D (e.g., an indication of an amount of calories determined to be burned by the user during the outdoor run). It should be recognized that, in some examples, user interface  1026  can include more or fewer representations. 
     User interface  1026  also includes a current time, a physical activity icon (as discussed above), or other information determinable by device  600 A. The physical activity icon depicted in user interface  1026  can be animated. While  FIG. 10C  depicts a particular visual appearance of representations  1028 , it should be recognized that representations  1028  can appear differently. 
     At some point after a workout has started (e.g., after selection of start affordance  1006 A), it can be determined that the user is likely (e.g., above a threshold criteria) no longer running outside. The determination can be based upon similar data as described above for beginning the outdoor run, such as data detected by one or more sensors associated with device  600 A. In response to the determination that the user is likely no longer running outside, user interface  1038  (as depicted in  FIG. 10D ) is displayed on touch-sensitive display  602 A. 
     User interface  1038  includes a scrollable list of affordances  1040 , which are associated with different operations. For example, the scrollable list of affordances  1040  includes end affordance  1040 A, pause affordance  1040 B, change affordance  1040 C, and dismiss affordance  1006 D. End affordance  1040 A causes the physical activity tracking function corresponding to the outdoor run to stop and data generated by the physical tracking function to be stored as a previous workout. Pause affordance  1040 B causes the physical activity tracking function corresponding to the outdoor run to pause. Change affordance  1040 C allows a user to choose a different type of workout so that a different physical activity tracking function corresponding to the different type of workout can be launched. Dismiss affordance  1006 D causes user interface  1038  to cease to display and the physical activity tracking function for the outdoor run to continue to execute. 
     User interface  1038  further includes physical activity icon  1042  corresponding to the outdoor run. Physical activity icon  1042  is an icon of a runner. In various examples, physical activity icon  1042  is displayed in a static state. 
     In some examples, content included in user interface  1038  might not fit within touch-sensitive display  602 A; in which case content not displayed can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism  604 A). 
     Referring to  FIG. 10E , user input (e.g., tap input)  1005  is received, where user input  1005  corresponds to selection of end affordance  1040 A. In accordance with a determination that user input  1005  is detected at end affordance  1040 A in the scrollable list of affordances  1040 , the physical activity tracking function for the outdoor run is discontinued. That is, execution of the physical activity tracking function for the outdoor run is stopped in accordance to the selection of end affordance  1040 A. The selection can cause data to be stored for the outdoor run as a previous workout. It should be recognized that data can be stored for the outdoor run as the data is detected. 
     Referring to  FIG. 10F , user interface  1044  is displayed in response to selection of end affordance  1040 A. User interface  1044  can provide feedback regarding data detected by device  600 A for the outdoor run. For example, user interface  1044  includes representations  1046  of different types of data detected by device  600 A for the outdoor run. In  FIG. 10F , representations  1046  include total mileage  1046 A (e.g., an indication of a number of miles traveled during the outdoor run), average pace per mile  1046 B (e.g., an indication of an average amount of time it has taken for device  600 A to travel a mile during the outdoor run), total time  1046 C (e.g., an indication of a duration of the outdoor run), total active calories  1046 D (e.g., an indication of an amount of calories determined to be burned by the user wearing device  600 A during an active state for the outdoor run), and total calories  1046 E (e.g., an indication of an amount of calories determined to be burned by the user wearing device  600 A during the outdoor run). It should be recognized that, in some examples, user interface  1044  can include more or fewer representations. 
     User interface  1044  also includes an identification of the outdoor run (e.g., representation  1048 ), a physical activity icon (e.g., physical activity icon  1050 ), or other information known by device  600 A. While  FIG. 10F  depicts a particular visual appearance of representations  1046 , it should be recognized that representations can appear differently. 
       FIG. 10G  again illustrates user interface  1004  (as depicted in  FIG. 10A  and under circumstances as described with respect to  FIG. 10A ). As described above, user interface  1004  includes change affordance  1006 B. Referring to  FIG. 10G , user input (e.g., tap input)  1003  is received, where user input  1003  corresponds to selection of change affordance  1006 B. In some examples, when selecting to change a type of workout, data detected prior to selecting change affordance  1006 B is not configured to be associated with the new type of workout. For example, changing the workout causes a new workout to begin after the new workout is selected, unlike what occurs (in some examples) when selecting to start a workout using affordance  1006 A) (e.g., data detected prior to starting the workout using affordance  1006 A can be configured to be associated with the workout). In other words, start affordance  1006 A causes data detected prior to selection of start affordance  1006 A to be used and change affordance  1006 B causes data detected prior to selection of change affordance  1006 B to not be used. In accordance with a determination that user input  1003  is detected at change affordance  1006 B in the scrollable list of affordances  1006 , user interface  1030  illustrated in  FIG. 10H  is displayed. 
     User interface  1030  allows a user to select a different type of workout for a current workout. For example, when it is determined that the user is running outside, the user can change the outdoor run to a second type of workout, indicating that the determination of the outdoor run was incorrect. When a different type of workout is selected, a physical activity tracking function corresponding to the different type of workout launches automatically. 
     User interface  1030  includes a scrollable list of affordances  1032 , which are associated with respective physical activity tracking functions for a physical activity. For example, the scrollable list of affordances  1032  includes affordance  1032 A (which corresponds to a physical activity tracking function for climbing stairs (referred to as stair stepping)), affordance  1032 B (which corresponds to a physical activity tracking function for an outdoor run), and affordance  1032 C (which corresponds to a physical activity tracking function for a walk). It is noted that the scrollable list of affordances  1032  can include additional affordances corresponding to other physical activity tracking functions that are not currently displayed but can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism  604 A). 
     In some examples, each of one or more affordances in the scrollable list of affordances  1032  includes representations  1034  corresponding to a physical activity associated with the affordance. Representations  1034  includes a physical activity icon corresponding to the physical activity associated with the affordance. For example, affordance  1032 A includes physical activity icon  1034 A (e.g., icon of a person climbing stairs). Similarly, affordance  1032 C includes physical activity icon  1034 D (e.g., icon of a person walking). In various examples, physical activity icons are displayed in a first state (e.g., static state). 
     Representations  1034  further includes a workout identifier. For example, affordance  1032 A includes workout identifier  1034 B that indicates that affordance  1032 A is associated with a stair stepper workout. Similarly, affordance  1032 B includes a workout identifier that indicates that affordance  1032 B is associated with an outdoor run workout. 
     In some examples, one or more affordances in the scrollable list of affordances  1032  includes workout goal information. For example, affordance  1032 A includes workout goal information  1034 C that indicates that the stair stepper workout associated with affordance  1032 A has a predetermined goal of twenty minutes. That is, when affordance  1032 A is selected, the associated physical activity tracking function will automatically track information for the stair stepper workout with a preset goal of twenty minutes. Affordance  1032 B includes a goal workout affordance that indicates that the outdoor run associated with affordance  1032 B is an “open goal.” An open goal indication indicates to the user that the associated workout does not currently have any preset goals. Accordingly, when affordance  1032 B is selected, various metrics will be tracked by the associated physical activity tracking function, wherein the metrics do not include any preset goal values. 
       FIG. 10I  illustrates a series of states of device  600 A with touch-sensitive display  602 A. The series of states depict user interface  1004  (which is also depicted in  FIG. 10A ) over time. 
     By depicting user interface  1004  over time, it is illustrated how physical activity icon  1008  can be animated. For example, physical activity icon  1008 A depicts physical activity icon  1008  in a first state, physical activity icon  1008 B depicts physical activity icon  1008  in a second state subsequent to the first state, and physical activity icon  1008 C depicts physical activity icon  1008  in a third state subsequent to the second state. 
     The animation can give the impression that a person is running. Animating physical activity icon  1008  can provide feedback to a user that device  600 A has determined (e.g., detected) that a workout has begun. 
       FIGS. 10J and 10K  illustrate user interfaces displayed in response to determinations that different types of workouts have begun. For example, different types of workouts can be associated with different sets of one or more criteria. When a set of one or more criteria for a particular type of workout is satisfied, a user interface for beginning a workout corresponding to the particular type of workout can be displayed. 
     Referring to  FIG. 10J , user interface  1052  of a workout application is displayed on touch-sensitive display  602 A. User interface  1052  includes a scrollable list of affordances  1054 , which is similar (e.g., functions in a similar manner) to the scrollable list of affordances  1006 . For example, the scrollable list of affordances  1054  includes start affordance  1054 A (which corresponds to a physical activity tracking function for a walk). It is noted that the scrollable list of affordances  1054  might not fit within touch-sensitive display  602 A; in which case one or more affordances not displayed can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism  604 A). 
     User interface  1054  further includes physical activity icon  1056  corresponding to a physical activity associated with start affordance  1054 A. Physical activity icon  1056  is an icon of a person walking. In various examples, physical activity icon  1056  is displayed in an animated state. 
     Referring to  FIG. 10K , user interface  1058  of a workout application is displayed on touch-sensitive display  602 A. User interface  1058  includes a scrollable list of affordances  1060 , which is similar (e.g., functions in a similar manner) to the scrollable list of affordances  1006 . For example, the scrollable list of affordances  1060  includes start affordance  1060 A (which corresponds to a physical activity tracking function for a rowing exercise). It is noted that the scrollable list of affordances  1060  might not fit within touch-sensitive display  602 A; in which case one or more affordances not displayed can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism  604 A). 
     User interface  1058  further includes physical activity icon  1062  corresponding to a physical activity associated with start affordance  1060 A. Physical activity icon  1062  is an icon of a person rowing. In various examples, physical activity icon  1062  is displayed in an animated state. 
     In some examples, instead of displaying user interface  1004 , user interface  1068  is displayed, as depicted in  FIG. 10M . In such examples, user interface  1068  is displayed when a determination is made that there are multiple types of workouts that have potentially begun. User interface  1068  includes a scrollable list of affordances  1070 , where each affordance is associated with a different operation. For example, the scrollable list of affordances  1070  includes start outdoor run affordance  1070 A, start indoor run affordance  1070 B, change affordance  1070 C, and dismiss affordance  1070 D. Start outdoor run affordance  1070 A causes a physical activity tracking function configured for outdoor runs to be launched (similar to start affordance  1006 A). Start indoor run affordance  1070 B causes a physical activity tracking function configured for indoor runs to be launched. Change affordance  1070 C allows a user to pick a different type of workout such that a physical tracking function configured for the different type of workout is launched (similar to start affordance  1006 B). Dismiss affordance  1070 D causes user interface  1068  to cease to display (similar to start affordance  1006 C). 
     In some examples, start indoor run affordance  1070 B is related to a type of workout that is an alternative to a type of workout corresponding to start outdoor run affordance  1070 A (in some examples, types of workouts are related when tracking data used for one can be used for the other). In such examples, start outdoor run affordance  1070 A is visually highlighted (e.g., a different color and/or a different size) as compared to start indoor run affordance  1070 B (and in comparison to the other affordances  1070 C and  1070 D). In some examples, start outdoor run affordance  1070 A is visually highlighted because a determination, based on sensor data, has been made that it is more likely that a user is running outdoor than indoors. In some examples, start indoor run affordance  1070 B is not visually highlighted as compared to change affordance  1070 C and dismiss affordance  1070 D. In other words, start indoor run affordance  1070 B, change affordance  1070 C, and dismiss affordance  1070 D can appear similar while start outdoor run affordance  1070 A is visually distinct from all three. Examples of types of workouts that might commonly be paired together as a main workout and an alternative workout include outdoor/indoor run, outdoor/indoor walk, and pool swim/open water swim. While only a single alternative is illustrated in  FIG. 10M , it should be recognized that more than one alternative may be included in the scrollable list of affordances  1070 . 
     In some examples, after an alert is issued (e.g., user interface  1004 ), a user interface (e.g., user interface  1076 ) for selecting to start a workout from a list of workouts includes one or more representations corresponding to the alert, as depicted in  FIGS. 10P-10Q  and discussed below. Such a user interface can be navigated to as depicted in  FIGS. 10N-100  and discussed below. 
       FIG. 10N  illustrates user interface  1072  displayed on touch-sensitive display  602 A of device  600 A. User interface  1072  includes multiple application affordances  1074  associated with applications. For example, affordance  1074 A is associated with an audio application and affordance  1074 B is associated with a workout application. In some examples, user interface  1072  can be displayed to present which application can be launched using device  600 A. Selection of an affordance included in user interface  1072  can cause a corresponding application to be launched. 
       FIG. 10O  again illustrates user interface  1072  (as depicted in  FIG. 10N ). As described above, user interface  1072  includes affordance  1074 B. Referring to  FIG. 10O , user input (e.g., tap input)  1007  is received, where user input  1007  corresponds to selection of affordance  1074 B. In accordance with a determination that user input  1007  is detected at affordance  1074 B, the workout application that corresponds to affordance  1074 B is launched and user interface  1076  (which is discussed below and depicted in  FIG. 10P ) is displayed. 
     Referring to  FIG. 10P , user interface  1076  includes a scrollable list of affordances  1078 , which are associated with respective physical activity tracking functions for respective physical activities. In some examples, the scrollable list of affordances  1078  includes at least two types of affordances: a first type of affordance associated with physical activity tracking functions corresponding to an alert (e.g., user interface  1004 ) issued by device  600 A; and a second type of affordance (e.g.,  1078 C) associated with physical activities that are track-able by device  600 A (but do not correspond to an alert (e.g.,  1004 ) issued by device  600 A). In some examples, physical activities are represented in both the first type and the second type such that the scrollable list of affordances  1078  includes (1) a first affordance (of a first type of affordance) associated with a particular type of physical activity and (2) a second affordance (of a second type of affordance different from the first type of affordance) associated with the particular type of physical activity. In other examples, physical activities represented by the first type of affordance are not represented by the second type of affordance. 
     As depicted in  FIG. 10P , the scrollable list of affordances  1078  includes multiple affordances of the first type of affordance: affordance  1078 A (which corresponds to continuing a physical activity tracking function for an outdoor run that began at 10 AM) and affordance  1078 B (which corresponds to continuing a physical activity tracking function for an indoor run that began at 10 AM). The scrollable list of affordances  1078  includes multiple affordances of the first type of affordance in response to either (1) multiple different alerts (e.g., user interface  1004 ) have been issued without initiating a physical activity tracking function corresponding to one of the multiple different alerts or (2) an alert with multiple types of workouts (e.g., user interface  1068 ) has been issued without initiating a physical activity tracking function corresponding to one of the multiple types of workouts. 
     It should be noted that user interface  1076  includes a clock indicating that the time is “10:09” and affordance  1078 A indicates a workout starting at 10 AM. This illustrates that selection of affordance  1078 A causes data tracked since 10 AM to be recorded for a current outdoor running workout even though a user did not indicate to begin an outdoor running workout at 10 AM. 
     In some examples, the scrollable list of affordances  1078  can include additional affordances corresponding to other physical activity tracking functions that are not currently displayed but can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism  604 A).  FIG. 10Q  depicts user interface  1076  in response to a scrolling input. User interface  1076  in  FIG. 10Q  again includes the scrollable list of affordances  1078 . 
     As depicted in  FIG. 10Q , the scrollable list of affordances  1078  includes an affordance of the first type of affordance (i.e., affordance  1078 B) and multiple affordances of the second type of affordance, the multiple affordances including: affordance  1078 C (which corresponds to a physical activity tracking function for a stair stepping workout) and affordance  1078 D (which corresponds to a physical activity tracking function for a walk). The scrollable list of affordances  1206  is configured such that a type of physical activity can be selected for a current workout. In some examples, when an affordance of the first type of affordance is selected, a workout is started using data detected before selection of the affordance. In such examples, when a affordance of the second type of affordance is selected, a workout is started that does not use data detect before selection of the affordance (only data detected after selection of the affordance). In some examples, affordances of the first type of affordance (e.g., affordance  1078 A and affordance  1078 B) are visually highlighted as compared to affordances of the second type of affordance (e.g., affordance  1078 C and affordance  1078 D). 
       FIG. 11  is a flow diagram illustrating a method for displaying an alert in response to automatically determining a boundary of physical activity using an electronic device in accordance with some examples. Method  1100  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 A,  600 B,  800 ) with a display and one or more sensors (e.g., a gyroscope, a camera, an accelerometer, GPS sensor, heart rate monitor, clock, the like, or any combination thereof. Some operations in method  1100  are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  1100  provides an intuitive way for displaying an alert in response to automatically determining a boundary of physical activity (e.g., a workout). The method reduces the cognitive burden on a user for starting and stopping a physical activity tracking function, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to track activity data faster and more efficiently conserves power and increases the time between battery charges. 
     At  1102 , the device (e.g.,  600 A) detects, via the one or more sensors, activity data (e.g., heart rate data, GPS data, movement data, or the like) (e.g.,  FIG. 10A , data detected to cause user interface  1004  to be displayed). In some examples, the one or more sensors used to detect the activity data are a subset of sensors included with the electronic device (e.g., some sensors may not be used to detect the activity data). 
     In some examples, the activity data is detected before a physical activity tracking function is active (e.g., a tracking function corresponding to  1026 ). In such examples the activity data is used to determine whether to initiate a physical activity tracking function (e.g., the boundary condition is a start of a workout). 
     At  1102 , in response to detecting the activity data, in accordance with a determination that the activity data satisfies activity boundary alert criteria (e.g., criteria for categorizing activity data as corresponding to a boundary (e.g., a start, an end, a transition from one type of activity to another) of user activity (e.g., a user workout)), the device (e.g.,  600 A) displays an activity boundary alert (e.g., a user interface including a confirmation affordance and an indication of the type of activity boundary detected) (e.g.,  1004  or  1038 ). Displaying an activity boundary alert provides feedback as to when a device detects an activity boundary. Providing improved feedback and performing an operation when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, the activity boundary alert (e.g.,  1004 ) includes a first affordance (e.g.,  1006 A). In such examples, the device (e.g.,  600 A) receives a first user input (e.g.,  1001 ) corresponding to selection of the first affordance. In response to receiving the first user input, the device initiates a physical activity tracking function (e.g., user interface  1026  can be displayed with information from physical activity tracking function) corresponding to a type of physical activity (e.g., running, HIIT, yoga, or the like) corresponding to the activity boundary alert (e.g., the physical tracking functions corresponds to the first affordance). In some examples, the activity boundary alert includes a third affordance (e.g.,  1006 C). In such examples, selection of the third affordance causes the device to forgo initiating the physical activity tracking function corresponding to a type of physical activity corresponding to the activity boundary alert. In such examples, the device continues to determine when a workout begins. 
     In some examples, the physical activity tracking function corresponding to the activity boundary alert (e.g.,  1004 ) tracks activity data detected prior to displaying the activity boundary alert. 
     In some examples, the activity boundary alert (e.g.,  1004 ) corresponds to a first physical activity tracking function (e.g., an activity tracking function corresponding to a predicted type of activity (e.g., running, swimming, rowing)). In such examples, the activity boundary alert includes a second affordance (e.g.,  1006 ). In such examples, the device receives a second user input (e.g.,  1003 ) corresponding to selection of the second affordance in the activity boundary alert. In response to receiving the second user input, the device displays a first user interface (e.g.,  1030 ) including: a third affordance (e.g.,  1032 A) corresponding to a second physical activity tracking function different than the first physical activity tracking function; and a fourth affordance (e.g.,  1032 C) corresponding to a third physical activity tracking function different than the first physical activity tracking function. While displaying the first user interface the device receives a third user input. In accordance with the third user input corresponding to selection of the third affordance in the first user interface, the device configures the electronic device to track activity data detected after selection of the third affordance using the second physical activity tracking function. In accordance with the third user input corresponding to selection of the fourth affordance in the second user interface, the device configures the electronic device to track activity data detected after selection of the fourth affordance using the third physical activity tracking function. In some examples, the activity boundary alert includes an animated affordance (e.g.,  FIG. 10I ) representing a type of workout associated with the activity boundary alert. 
     In some examples, the activity data was detected via a first sensor of the one or more sensors. In such examples, initiating the physical activity tracking function corresponding to the type of physical activity corresponding to the activity boundary alert (e.g., the physical tracking functions corresponds to the first affordance) includes detecting second activity data via a second sensor, different than the first sensor (e.g., the first sensor is an accelerometer and the second sensor is a GPS sensor), of the one or more sensors. In some examples, the second sensor is activated, from an inactive state. 
     In some examples, the activity data is detected while an existing physical activity tracking function is active (e.g., a tracking function corresponding to  1026 ). 
     In some examples, the activity data is detected while an existing physical activity tracking function is active. For example, the device is already tracking a workout. In such examples, the activity boundary alert (e.g.,  1038 ) includes a fifth affordance (e.g.,  1040 A). In such examples, the device receives a first fourth input (e.g.,  1005 ) corresponding to selection of the fifth affordance. In response to receiving the fourth user input, the device ends the current physical activity tracking function. In further response to receiving the fourth user input, the device stores activity data (e.g., including the activity data) detected prior to receiving the fourth user input as a previous workout. 
     In some examples, the activity boundary alert (e.g.,  1038 ) includes a sixth affordance (e.g.,  1040 B). In such examples, the device receives a fifth user input corresponding to selection of the sixth affordance. In response to receiving the fifth user input, the device pauses execution of a physical activity tracking function. In some examples, the activity boundary alert includes a dismiss affordance (e.g.,  1040 D) to not stop recording a workout. 
     In some examples, the activity boundary alert (e.g.,  1038 ) corresponds to a first physical activity tracking function. In such examples, the activity boundary alert includes a seventh affordance (e.g.,  1040 C). In such examples, the device receives a sixth user input (e.g., similar to  1003 ) corresponding to selection of the seventh affordance. In response to receiving the sixth third input, the device initiates a process for ceasing execution of a first physical activity tracking function. In further response to receiving the sixth third input, the device displays a second user interface (e.g.,  1030 ) including: a eighth affordance (e.g.,  1032 A) corresponding to a second physical activity tracking function different than the first physical activity tracking function, and a ninth affordance (e.g.,  1032 C) corresponding to a third physical activity tracking function different than the first physical activity tracking function. In such examples, the device receives a seventh user input. In accordance with the seventh user input corresponding to selection of the eighth affordance in the second user interface, the device initiates the second physical activity tracking function. In accordance with the seventh user input corresponding to selection of the ninth affordance in the second user interface, the device initiates the third physical activity tracking function. 
     In some examples, the activity boundary alert includes a static affordance (e.g.,  FIG. 10G , icon of running man) representing a type of workout associated with the activity boundary alert. 
     In some examples, the determination that the activity data satisfies activity boundary alert criteria can update over time based upon user interactions. 
     In some examples, the activity boundary alert (e.g.,  1068 ) includes a tenth affordance (e.g.,  1070 B) (in some examples, the tenth affordance is an affordance for an alternative type of workout as compared to the first affordance (e.g.,  1070 A)), and wherein the physical activity tracking function corresponding to the activity boundary alert is a first physical activity tracking function. In such examples, the electronic device receives an eighth user input corresponding to selection of the tenth affordance and, in response to receiving the eighth user input, initiates a second physical activity tracking function corresponding to the activity boundary alert, wherein the second physical activity tracking function is different from the first physical activity tracking function (in some examples, each of the first physical activity tracking function and the second physical activity tracking function uses the activity data in a first manner (e.g., tracking number of miles) while a third physical activity tracking function that does not correspond to the activity boundary alert criteria uses the activity data in a second manner different from the first manner (e.g., tracking number of laps)). 
     In some examples, the first affordance (e.g.,  1070 A) and the tenth affordance (e.g.,  1070 B) are ordered based upon which respective workout is determined to be more likely the type of workout being performed. For example, if a determination is made that it is more likely that a user is performing an outdoor run than an indoor run, an affordance associated with an outdoor run precedes an affordance associated with an indoor run, as illustrated in  FIG. 10M . 
     In some examples, the first affordance is highlighted as compared to the tenth affordance, to highlight that a workout corresponding to the first affordance has been determined to be more likely being performed than a workout corresponding to the tenth affordance. 
     In some examples, wherein the activity boundary alert is a first activity boundary alert (e.g.,  1064 ) including (in some examples, the activity boundary alert is displayed in response to a short look) first content, after displaying the first activity boundary alert, the electronic device displays a second activity boundary alert (e.g.,  1004 ) (in some examples, the second activity boundary alert is displayed in response to a long look) including second content, wherein the second content is different from the first content (e.g., the second content includes the first content and additional content) (in some examples, the second activity boundary alert is displayed in accordance with a determination that look criteria have been satisfied). 
     At  1106 , in further response to detecting the activity data and in accordance with a determination that the activity data does not satisfy the activity boundary alert criteria, the device forgoes display of the activity boundary alert (e.g., forgoes displaying  1004 ). 
     In some examples, further in response to detecting the activity data and in accordance with a determination that the activity data satisfies second activity boundary alert criteria, the device displays a second activity boundary alert (e.g., alert  1058 ), where the activity boundary alert criteria and the activity boundary alert (e.g., alert  1004 ) relate to a first type of physical activity (e.g., running), and where the second activity boundary alert criteria and the second activity boundary alert relate to a second type of physical activity (e.g., rowing) different than the first type. In accordance with a determination that the activity data does not satisfy the second activity boundary alert criteria, the device forgoes display of the second activity boundary alert (e.g., forgoes displaying  1004 ). 
     In some examples, where the activity boundary alert is a first activity boundary alert, after a predetermined time (e.g., 3 minutes) has lapsed without initiating a physical activity tracking function corresponding to the first activity boundary alert, the electronic device displays a second activity boundary alert (e.g.,  1004 ), wherein a physical activity tracking function corresponding to the second activity boundary alert tracks activity data detected prior to displaying the first activity boundary alert. 
     In some examples, after displaying the activity boundary alert and before a physical activity tracking function is active, the electronic device displays a third user interface (e.g.,  1076 ) (in some examples, the third user interface is the first user interface) including a scrollable list of affordances (e.g.,  1078 ) associated with physical activities. In some examples, the electronic device receives a ninth user input. In some examples, in accordance with a determination that the ninth user input is detected at an eleventh affordance (e.g.,  1078 A) in the scrollable list of affordances, the electronic device launches a physical activity tracking function corresponding to the activity boundary alert (in some examples, the physical activity tracking function associated corresponding to the activity boundary alert tracks activity data detected prior to displaying the third user interface) (in some examples, the physical activity tracking function corresponding to the activity boundary alert tracks activity data detected prior to displaying the activity boundary alert). In some examples, in accordance with a determination that the ninth user input is detected at a twelfth affordance (e.g.,  1078 C) in the scrollable list of affordances, the electronic device launches a physical activity tracking function (1) not corresponding to the activity boundary alert and (2) different from the physical activity tracking function corresponding to the activity boundary alert. In some examples, wherein the physical activity tracking function corresponding to the activity boundary alert is a first the physical activity tracking function, in accordance with a determination that the ninth user input is detected at a thirteenth affordance (e.g.,  1078 B) in the scrollable list of affordances, the electronic device launches a second physical activity tracking function corresponding to the activity boundary alert, wherein the second physical activity tracking function is different from the first physical activity tracking function, and wherein the second physical activity tracking function corresponding to the activity boundary alert tracks activity data detected after receiving the ninth user input (in some examples, the second physical activity tracking function tracks activity data detected after launching the second physical activity tracking function) (in some examples, one of the physical activity tracking functions corresponding to with the eleventh or twelfth affordance is the same physical activity tracking function corresponding to the thirteenth affordance). 
     In some examples, the eleventh affordance and the thirteenth affordance are visually highlighted (e.g., different color and/or bigger) as compared to the twelfth affordance, to indicate that the eleventh affordance and the thirteenth affordance are a different type of affordance from the twelfth affordance. 
     Note that details of the processes described above with respect to method  1100  (e.g.,  FIG. 11 ) are also applicable in an analogous manner to the methods described below/above. For example, method  1100  optionally includes one or more of the characteristics of the various methods described below with reference to method  700 , method  900 , or method  1300 . For example, in response to the user interface of method  1100 , the user interface of method  700  can be displayed. For another example, the user interface of method  1100  can lead (e.g., ending a workout can cause activity data to be generated) to the user interface of method  900  being displayed in response to activity data generated. For another example, a pace set using method  1100  can cause the user interface of method  1300  to be displayed. For brevity, these details are not repeated below. 
       FIGS. 12A-12AK  illustrate exemplary user interfaces associated with configuring a pace alert for a workout application in accordance with some examples. The user interfaces allow a user to configure the dataset used to calculate a pace for the pace alert. For example, the dataset used can include data starting from the beginning of a workout (referred to as an average). For another example, the dataset used can be a previous amount of data relative to a current time such that the dataset does not include data from the beginning of the workout (referred to as a rolling average). The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIG. 13 . 
       FIG. 12A  illustrates user interface  1256  displayed on touch-sensitive display  602 A of device  600 A. User interface  1256  includes multiple application affordances  1258  associated with applications. For example, affordance  1258 A is associated with an audio application and affordance  1258 B is associated with a workout application. In some examples, user interface  1256  can be displayed to present which application can be launched using device  600 A. Selection of an affordance included in user interface  1256  can cause a corresponding application to be launched. 
       FIG. 12B  again illustrates user interface  1256  (as depicted in  FIG. 12A ). As described above, user interface  1256  includes affordance  1258 B. Referring to  FIG. 12B , user input (e.g., tap input)  1229  is received, where user input  1229  corresponds to selection of affordance  1258 B. In accordance with a determination that user input  1229  is detected at affordance  1258 B, the workout application that corresponds to affordance  1258 B is launched and user interface  1204  (which is discussed below and depicted in  FIG. 12C ) is displayed. 
     Referring to  FIG. 12C , user interface  1204  includes a scrollable list of affordances  1206 , which are associated with respective physical activity tracking functions for respective physical activities. For example, the scrollable list of affordances  1206  includes affordance  1206 A (which corresponds to a physical activity tracking function for an outdoor run), affordance  1206 B (which corresponds to a physical activity tracking function for an indoor cycling workout), and affordance  1206 C (which corresponds to a physical activity tracking function for a walk). In some examples, the scrollable list of affordances  1206  can include additional affordances corresponding to other physical activity tracking functions that are not currently displayed but can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism  604 A). The scrollable list of affordances  1206  is configured such that a type of physical activity can be selected for a current workout. 
     In some examples, one or more affordances in the scrollable list of affordances  1206  includes an options affordance, as further discussed below. For example, affordance  1206 A includes options affordance  1208 . 
     Referring to  FIG. 12D , user input (e.g., tap input)  1201  is received, where user input  1201  corresponds to selection of options affordance  1208 . In accordance with a determination that user input  1201  is detected at options affordance  1208 , a user interface (e.g., user interface  1210  as depicted in  FIG. 12E ) is displayed with options related to a physical activity corresponding to affordance  1206 A. 
     Referring to  FIG. 12E , user interface  1210  is displayed in response to selection of options affordance  1208  (as depicted in  FIG. 12D ). User interface  1210  provides options to change how device  600 A operates when executing a physical activity tracking function corresponding to affordance  1206 A. User interface  1210  includes back affordance  1212  to cause user interface  1204  (as depicted in  FIG. 12C ) to be displayed. User interface  1210  further includes pace-alert affordance  1214  to allow a user to configure a pace alert for the physical activity tracking function corresponding to affordance  1206 A. 
       FIG. 12F  again illustrates user interface  1210  (as depicted in  FIG. 12E ). As described above, user interface  1210  includes pace-alert affordance  1214 . Referring to  FIG. 12F , user input (e.g., tap input)  1203  is received, where user input  1203  corresponds to selection of pace-alert affordance  1214 . 
     In some examples, in accordance with a determination that user input  1203  is detected at pace-alert affordance  1214 , a user interface (e.g., user interface  1216  as depicted in  FIG. 12G ) is displayed with options related to a pace alert. In other examples, in accordance with a determination that user input  1203  is detected at pace-alert affordance  1214 , a user interface (e.g., user interface  1222  as depicted in  FIG. 12I ) is displayed with options related to setting a pace for a pace alert. 
     Referring to  FIG. 12G , user interface  1216  is displayed in response to selection of pace-alert affordance  1214 . User interface  1216  provides options to configure a pace alert. User interface  1216  includes back affordance  1220  to cause user interface  1210  (as depicted in  FIG. 12E ) to be displayed. 
     User interface  1216  further includes a scrollable list of affordances  1218 , which are associated with different operations. For example, the scrollable list of affordances  1218  includes set-pace affordance  1218 A (which corresponds to causing a display for setting a pace to be displayed), average affordance  1218 B (which corresponds to causing a pace to be calculated using data from an entire workout), rolling affordance  1218 C (which corresponds to causing a pace to be calculated using a subset of data from a workout, where the subset is less than the entire workout), off affordance  1218 D (which corresponds to turning off a pace alert), or any combination thereof. It is noted that, in some examples, the scrollable list of affordances  1218  might not fit within touch-sensitive display  602 A; in which case one or more affordances not displayed can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism  604 A). 
     As used herein, pace can refer to speed (e.g., an amount of distance that a device travels in an amount of time or an amount of time that it takes for a device to travel an amount of distance). In regards to pace, the different calculations described herein (e.g., average and rolling) can refer to changing an amount of a dataset for a current workout that is used when performing a pace calculation. For example, for average, the pace calculation can be based upon data detected during the entire current workout. For rolling, the pace calculation can be based upon data detected during an amount prior to a current location (e.g., data detected for the last mile or data detected for the last 5 minutes). 
       FIG. 12H  again illustrates user interface  1216  (as depicted in  FIG. 12G ). As described above, user interface  1216  includes set-pace affordance  1218 A. Referring to  FIG. 12H , user input (e.g., tap input)  1205  is received, where user input  1205  corresponds to selection of set-pace affordance  1218 A. In accordance with a determination that user input  1205  is detected at set-pace affordance  1218 A, a user interface (e.g., user interface  1222  as depicted in  FIG. 12I ) is displayed with options related to setting a pace for a pace alert. 
     Referring to  FIG. 12I , user interface  1222  can be displayed in response to selection of set-pace affordance  1218 A (as depicted in  FIG. 12H ) in some examples. In other examples, user interface  1222  can be displayed in response to selection of pace-alert affordance  1214  in user interface  1210  (as depicted in  FIG. 12E ). User interface  1222  can provide options to allow a user to set a pace for a pace alert. User interface  1222  can include back affordance  1228  to cause user interface  1210  to be displayed. 
     User interface  1222  further includes multiple affordances for setting a time (e.g., minutes-setting affordance  1224 A and seconds-setting affordance  1224 B). Minutes-setting affordance  1224 A is used to set a number of minutes for a pace. Seconds-setting affordance  1224 B is used to set a number of seconds for the pace. 
     As depicted in  FIG. 12I , each affordance for setting the time is independently selectable. For example, each of minutes-setting affordance  1224 A and seconds-setting affordance  1224 B can be selected. When an affordance of the multiple affordances for setting a time is selected, the affordance can be visually distinguished. For example, in  FIG. 12I , minutes-setting affordance  1224 A has a thicker border than seconds-setting affordance  1224 B, indicating minutes-setting affordance  1224 A is selected (e.g., in focus). 
     User interface  1222  further includes a scrollable list of affordances  1226 , which are each associated with different operations. For example, the scrollable list of affordances  1226  includes set-pace affordance  1226 A (which corresponds to setting a pace identified using the multiple affordances for setting a time) and cancel affordance  1226 B (which corresponds to displaying a user interface for providing options to configure a pace alert, such as user interface  1216  in  FIG. 12G ), or any combination thereof. It is noted that, in some examples, the scrollable list of affordances  1226  might not fit within touch-sensitive display  602 A; in which case one or more affordances not displayed can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism  604 A). 
       FIG. 12J  again illustrates user interface  1222  (as depicted in  FIG. 12I ). As described above, user interface  1222  includes seconds-setting affordance  1224 B. Referring to  FIG. 12J , user input (e.g., tap input)  1207  is received, where user input  1207  corresponds to selection of seconds-setting affordance  1224 B. In accordance with a determination that user input  1207  is detected at seconds-setting affordance  1224 B, seconds-setting affordance  1224 B can be visually distinguished from minutes-setting affordance  1224 A. For example, selection of seconds-setting affordance  1224 B can cause seconds-setting affordance  1224 B to be visually distinguished instead of minutes-setting affordance  1224 A. 
       FIG. 12K  again illustrates user interface  1222 . Referring to  FIG. 12K , seconds-setting affordance  1224 B is visually distinguished instead of minutes-setting affordance  1224 A. In particular, seconds-setting affordance  1224 B has a thicker border than minutes-setting affordance  1224 A, indicating seconds-setting affordance  1224 B is selected (e.g., in focus). 
       FIG. 12L  depicts an example of user interface  1222  for scrolling of seconds-setting affordance  1224 B. Referring to  FIG. 12L , rotational input  1209  is received at rotatable input mechanism  604 A. In response to rotational input  1209 , options for seconds-setting affordance  1224 B is scrolled in an upward direction such that different options for seconds-setting affordance  1224 B are displayed, as depicted in  FIG. 12M . For example,  FIG. 12M  depicts user interface  1222  changing seconds-setting affordance  1224 B from “30” (as depicted in  FIG. 12L ) to “29” (as depicted in  FIG. 12M ). Similar scrolling can occur when minutes-setting affordance  1224 A is selected and rotational input  1209  is received. Scrolling the opposite direction for both affordances may also be performed. 
       FIG. 12N  again illustrates user interface  1222  (as depicted in  FIG. 12M ). As described above, user interface  1222  includes set-pace affordance  1226 A. Referring to  FIG. 12N , user input (e.g., tap input)  1211  is received, where user input  1211  corresponds to selection of set-pace affordance  1226 A. In accordance with a determination that user input  1211  is detected at set-pace affordance  1226 A, a user interface (e.g., user interface  1216  as depicted in  FIG. 12O ) is displayed with options related to a pace alert. 
     Referring to  FIG. 12O , user interface  1216  can be displayed in response to selection of set-pace affordance  1226 A. User interface  1216  can provide options to change how device  600 A operates when executing a physical activity tracking function corresponding to affordance  1206 A. As depicted in  FIG. 12O , user interface  1216  can include a scrollable list of affordances  1218 , which are associated with different operations. Text in set-pace affordance  1218 A (as depicted in  FIG. 12O ) has been changed from “Set Pace” (as depicted in  FIG. 12G ) to a pace set by a user (e.g., “8′29” MI″), such as the pace set in  FIG. 12N . 
     As discussed above, the scrollable list of affordances  1218  includes average affordance  1218 B. Referring to  FIG. 12P , user input (e.g., tap input)  1213  is received, where user input  1213  corresponds to selection of average affordance  1218 B, causing the physical activity tracking function corresponding to affordance  1206 A to use an average calculation. 
       FIG. 12Q  illustrates user interface  1216  in response to selection of average affordance  1218 B. Referring to  FIG. 12Q , average affordance  1218 B is updated to include an indication (e.g., a check mark) that a pace will be calculated according to an average operation. 
     Referring to  FIG. 12R , user input (e.g., tap input)  1215  is received, where user input  1215  corresponds to selection of back affordance  1220 . In some examples, in accordance with a determination that user input  1215  is detected at back affordance  1220 , a user interface (e.g., user interface  1210  as depicted in  FIG. 12S ) is displayed with options to change how device  600 A operates when executing a physical activity tracking function corresponding to affordance  1206 A. 
     Referring to  FIG. 12S , user interface  1210  can be displayed in response to selection of back affordance  1220 . User interface  1210  can provide options to change how device  600 A operates when executing a physical activity tracking function corresponding to affordance  1206 A. Text in pace-alert affordance  1214  (as depicted in  FIG. 12S ) has been updated to include an indication of a pace set by a user (e.g., “8′29” MI AVG″, as depicted at  1214 A). In some examples, The text can be in the updated state any time device  600 A is navigated to user interface  1210 . By including “MI AVG” in the text, pace-alert affordance  1214  can indicate that the pace alert for a physical activity tracking function corresponding to affordance  1206 A will be calculated using an average operation, as discussed herein. 
       FIG. 12T  again illustrates user interface  1210 . Referring to  FIG. 12T , user input (e.g., tap input)  1217  is received, where user input  1217  corresponds to selection of back affordance  1212 . In some examples, in accordance with a determination that user input  1217  is detected at back affordance  1212 , a user interface (e.g., user interface  1204  as depicted in  FIG. 12U ) is displayed. 
     Referring to  FIG. 12U , affordance  1206 A is updated to include an indication of a pace set by a user (e.g., “8′29” AVG PACE″, as depicted at  1208 B). It should be recognized that multiple affordances in the list of affordances  1206  can include a pace set by a user. In some examples, different affordances in the list of affordances  1206  can include different paces set by a user. 
       FIG. 12V  again illustrates user interface  1204 . Referring to  FIG. 12V , user input (e.g., tap input)  1219  is received, where user input  1219  corresponds to selection of affordance  1206 A. In accordance with a determination that user input  1219  is detected at affordance  1206 A in the scrollable list of affordances  1206 , a physical activity tracking function configured for outdoor runs is launched. The physical activity tracking function can include a pace alert when a user is below, on target, or above a user-specified pace for outdoor runs. The user-specified pace, as depicted in  FIG. 12V  is “8′29″”. 
     In response to selection of affordance  1206 A, user interface  1250  (which is depicted in  FIG. 12W ) is displayed. User interface  1250  displays (e.g., provides feedback regarding) data detected by device  600 A for an outdoor run. To display the data detected by device  600 A, user interface  1250  includes representations  1252 . In  FIG. 12W , representations  1252  include icon  1252 A (e.g., an animated icon of a running man to represent the outdoor run), total mileage  1252 B (e.g., an indication of a number of miles traveled during the outdoor run), total calories  1252 C (e.g., an indication of an amount of calories determined to be burned by the user during the outdoor run), average pace per mile  1252 D (e.g., an indication of an average amount of time it has taken for device  600 A to travel a mile during the outdoor run), total time  1252 E (e.g., an indication of a duration of the outdoor run), and BPM  1252 F (e.g., a calculated number of beats per minute for a heart of a user wearing device  600 A). It should be recognized that, in some examples, user interface  1250  can include more or fewer representations, similar to as depicted in  FIG. 12AK  and discussed below. 
     While a user is performing the outdoor run, a pace of the user might goes above a pace set for the outdoor run. When the pace of the user is above the pace set for the outdoor run, an alert that the pace of the user is above the pace set for the outdoor run can be displayed, as depicted in  FIG. 12X . 
     Referring to  FIG. 12X , the alert can be included in user interface  1244 . The alert can include an icon corresponding to a current workout and information  1246 . Information  1246  can include status  1246 A and current pace  1246 B. Status  1246 A can indicate whether the user is below, on target, or above a pace set for the current workout. Referring to  FIG. 12X , status  1246 A indicates that the user is “above target pace”. Current pace  1246 B can indicate a current pace for the user. For example, current pace  1246 B (as depicted in  FIG. 12X ) indicates that the user is currently running at a “8′52″” pace, which (due to average being selected for calculating the pace) is calculated over the entire current workout. Because “8′52″” is above the pace set at “8′29″”, the “above target pace” text can be displayed 
     In response to the user running quicker and bringing their pace to “8′29″”, user interface  1244  can be updated to reflect that the user is on target pace. Referring to  FIG. 12Y , status  1246 A can be updated to indicate that the user in “on target pace” and current pace  1246 B can be updated to indicate that the user&#39;s current pace is “8′29″” when calculated over the entire current workout. 
     In response to the user running even quicker and bringing their pace to “7′57″”, user interface  1244  can be updated to reflect that the user is below target pace. For example, status  1246 A can be updated to indicate that the user in “on target pace” and current pace  1246 B can be updated to indicate that the user&#39;s current pace is “7′57″” when calculated over the entire current workout. It should be recognized that what values constitute below, on target, and above a target pace can include one or more values around a target pace. For example, a number of seconds above and below target pace can still be considered on target. 
     In some examples, interface  1244  (as depicted in each of  FIG. 12X-12Z ) can be displayed to the user once after it is determined that the user is below, on target, or above a target pace. The one time can be when a user brings device  600 A into a position to look at device  600 A. In such examples, additional views of device  600 A while the same alert is applicable can cause user interface  1250  (as depicted in  FIG. 12W ) to be displayed. When user interface  1250  is displayed after an alert, average pace per mile  1252 D can be visually highlighted such that it can easily be located on user interface  1250 . 
     Referring back to after set-pace affordance  1226 A is selected (as depicted in  FIG. 12N ),  FIG. 12AA  again illustrates user interface  1216 . While average affordance  1218 B is illustrated without a check mark in  FIG. 12AA , it should be recognized that average affordance  1218 B can include the check mark (as depicted in  FIG. 12Q ). 
     Referring to  FIG. 12AA , user interface  1216  can include rolling affordance  1218 C. Rolling affordance  1218 C can correspond to calculating a pace using a rolling average during a physical activity. Rolling average can relate to using a subset of data for the physical activity. For example, while an average for the physical activity might use data from a beginning point to a present point of the physical activity, a rolling average can use an amount before the present point such that not all of the data from the beginning is used. 
     In one illustrative example, the user can run 2 miles in 10 minutes. The average for the run would be 5 minutes per mile. If the rolling average is calculated for the last 5 minutes, the rolling average for the run would be 5 divided by however much distance was covered in the last 5 minutes. For example, if the user ran 1.2 miles in the last 5 minutes, the rolling average for the user is 5 divided by 1.2 (i.e., 4 minutes and 10 seconds per mile). 
     Referring to  FIG. 12AA , user input (e.g., tap input)  1221  is received, where user input  1221  corresponds to selection of rolling affordance  1218 C. In accordance with a determination that user input  1221  is detected at rolling affordance  1218 C in the scrollable list of affordances  1218 , user interface  1230  can be displayed, as depicted in  FIG. 12AB . 
     Referring to  FIG. 12AB , user interface  1230  includes a list of affordances  1232  for configuring how a rolling calculation will be performed. The list of affordances  1232  can include first affordance  1232 A and second affordance  1232 B. First affordance  1232 A corresponds to distance such that the rolling calculation includes data detected for a previous amount of distance. For example, an average can be calculated for data detected in the last mile. Selection of first affordance  1232 A can cause a user interface (e.g., user interface  1236  as depicted in  FIG. 12AD  and discussed below) to be displayed to allow the user to select an amount of distance. Second affordance  1232 B corresponds to time such that the rolling calculation includes data detected for a previous amount of time. For example, an average can be calculated for data detected in the last 5 minutes. Selection of second affordance  1232 B can cause a user interface (e.g., similar to user interface  1222  as depicted in  FIG. 12I ) to be displayed to allow the user to select an amount of time. 
       FIG. 12AC  again illustrates user interface  1230 . As described above for  FIG. 12AB , user interface  1230  includes first affordance  1232 A, which corresponds to distance. Referring to  FIG. 12AC , user input (e.g., tap input)  1223  is received, where user input  1223  corresponds to selection of first affordance  1232 A. In accordance with a determination that user input  1223  is detected at first affordance  1232 A in the scrollable list of affordances  1232 , a user interface (user interface  1236  as depicted in  FIG. 12AD ) for selecting a distance is displayed. 
     Referring to  FIG. 12AD , user interface  1236  can be displayed in response to selection of first affordance  1232 A in user interface  1230 . User interface  1236  includes multiple affordances  1238  for setting a rolling pace (e.g., integer-setting affordance  1238 A and decimal-setting affordance  1238 B). Integer-setting affordance  1238 A is used to set a number of previous whole miles to use for the rolling pace. Decimal-setting affordance  1224 B is used to set a number of previous fractional miles to use for the rolling pace. 
     As depicted in  FIG. 12AD , each affordance for setting the rolling pace is independently selectable. For example, each of integer-setting affordance  1238 A and decimal-setting affordance  1238 B can be selected. When an affordance of multiple affordances  1238  for setting the rolling pace is selected, the affordance can be visually distinguished. For example, in  FIG. 12AD , integer-setting affordance  1238 A has a thicker border than decimal-setting affordance  1238 B, indicating integer-setting affordance  1238 A is selected (e.g., in focus). 
     User interface  1236  further includes a scrollable list of affordances  1240 , which are associated with different operations. For example, the scrollable list of affordances  1240  includes set-pace affordance  1240 A (which corresponds to setting a pace identified using the multiple affordances for setting the rolling pace) and cancel affordance  1240 B (which corresponds to displaying a user interface for providing options to configure a pace alert, such as user interface  1230  in  FIG. 12AB ), or any combination thereof. It is noted that the scrollable list of affordances  1240  might not fit within touch-sensitive display  602 A; in which case one or more affordances not displayed can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism  604 A). 
     Referring to  FIG. 12AE , user input (e.g., tap input)  1225  is received, where user input  1225  corresponds to selection of set-pace affordance  1240 A. In accordance with a determination that user input  1225  is detected at set-pace affordance  1240 A in the scrollable list of affordances  1240 , user interface  1210  can be displayed, as depicted in  FIG. 12AF . 
       FIG. 12AF  again illustrates user interface  1210 . User interface  1210  can be displayed in response to selection of set-pace affordance  1240 A. User interface  1210  can provide options to change how device  600 A operates when executing a physical activity tracking function corresponding to affordance  1206 A. Text in pace-alert affordance  1214  (as depicted in  FIG. 12AF ) has been updated to include an indication of a pace set by a user (e.g., “8′29″/1.00 MI”, as depicted at  1214 A). By including “/1.00 MI” in the text, pace-alert affordance  1214  can indicate that the pace alert for a physical activity tracking function corresponding to affordance  1206 A will be calculated using a rolling operation, as discussed herein. 
     Referring to  FIG. 12AG , user input (e.g., tap input)  1227  is received, where user input  1227  corresponds to selection of back affordance  1212 . In accordance with a determination that user input  1227  is detected at back affordance  1212 , user interface  1204  can be displayed, as depicted in  FIG. 12AH . 
     Referring to  FIG. 12AH , affordance  1206 A is updated to include an indication of a pace set by a user (e.g., “8′29″/1.00 MI”, as depicted at  1208 B). It should be recognized that multiple affordances in the list of affordances  1206  can include a pace set by a user. In some examples, different affordances in the list of affordances  1206  can include different paces set by a user. In addition, different paces set by a user can be calculated using a different operation (e.g., average or rolling). 
       FIG. 12AI  again illustrates user interface  1204 . Referring to  FIG. 12AI , user input (e.g., tap input)  1229  is received, where user input  1229  corresponds to selection of affordance  1206 A. In accordance with a determination that user input  1229  is detected at affordance  1206 A in the scrollable list of affordances  1206 , a physical activity tracking function configured for outdoor runs is launched. Launching the physical activity tracking function can cause a user interface to be displayed (e.g., user interface  1260 A as depicted in  FIG. 12AJ ). 
     Referring to  FIG. 12AJ , user interface  1260 A is displayed in response to selection of affordance  1206 A. User interface  1260 A displays (e.g., provides feedback regarding) data detected by device  600 A for an outdoor run. To display the data detected by device  600 A, user interface  1250 A includes representations  1262 . In  FIG. 12W , representations  1262  include icon  1262 AA (e.g., an animated icon of a running man to represent the outdoor run), total mileage  1262 B (e.g., an indication of a number of miles traveled during the outdoor run), total calories  1262 C (e.g., an indication of an amount of calories determined to be burned by the user during the outdoor run), average pace per mile  1262 D (e.g., an indication of an average amount of time it has taken for device  600 A to travel a mile during the last mile of the outdoor run), total time  1262 E (e.g., an indication of a duration of the outdoor run), and BPM  1262 F (e.g., a calculated number of beats per minute for a heart of a user wearing device  600 A). It should be recognized that, in some examples, user interface  1260 A can include more or fewer representations, similar to as depicted in  FIG. 12AK  and discussed below. 
       FIG. 12AK  illustrates multiple user interfaces  1260 . User interfaces  1260  can be alternatives for displaying (e.g., providing feedback regarding) data detected by device  600 A for an outdoor run (e.g., an alternative to user interface  1250  as depicted in  FIG. 12W  or user interface  1260 A as depicted in  FIG. 12AJ ). Each of user interfaces  1260  include a different number of representations  1262 . For example, user interface  1260 B includes 5 representations  1262 , user interface  1260 C includes 4 representations  1262 , and user interface  1260 D includes 3 representations  1262 . Each of user interfaces  1260  are meant to be an example. It should be recognized that other subsets of representations  1262  can be used and/or a different order of representations  1262 . 
     It should also be recognized that icon  1262 A can be different depending upon a number of representations  1262 . When there are less representations  1262  (e.g., user interface  1260 C includes less representations  1262  than user interface  1260 B), icon  1262 A can be bigger, more detailed, and/or include additional information. For example, icon  1262 AD in user interface  1260 D includes a running man and portion  1264 . In some examples, portion  1264  can indicate a percent of a daily goal completed using device  600 A. In other examples, portion  1264  can indicate a percent of a current workout completed using device  600 A. 
       FIG. 13  is a flow diagram illustrating a method for displaying a user interface to configure a dataset that is used to calculate a pace using an electronic device in accordance with some examples. Method  1300  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 A,  600 B,  800 ) with a display. Some operations in method  1300  are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted. 
     As described below, method  1300  provides an intuitive way for displaying a user interface to configure a dataset that is used to calculate a pace. The method reduces the cognitive burden on a user for configuring the dataset to calculate the pace, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to configure a pace faster and more efficiently conserves power and increases the time between battery charges. 
     At  1302 , the device (e.g.,  600 A) displays a physical activity rate (e.g., a pace (e.g., a mile pace while running)) user interface (e.g.,  1216 ) including a first setting affordance (e.g.,  1218 B) and a second setting affordance (e.g.,  1218 C). In some examples, the user interface father includes a third affordance (e.g.,  1218 A) for setting a pace. 
     At  1304 , while displaying the physical activity rate user interface, the device (e.g.,  600 A) receives a first user input (e.g.,  1213 ). In some examples, the user input is a finger gesture, such as a tap, on either the first or second affordance. 
     At  1306 , in response to receiving the first user input, in accordance with the first user input corresponding to selection of the first setting affordance (e.g.,  1213 ), the device configures a physical activity rate calculation to use a first portion of a dataset (e.g., average). 
     In some examples, the first portion of the dataset includes all of the dataset (e.g., for an average pace). 
     At  1308 , in further response to receiving the first user input, in accordance with the first user input corresponding to selection of the second setting affordance (e.g.,  1221 ), the device configures a physical activity rate calculation to use a second portion of the dataset (e.g., rolling) different than the first portion. In some examples, the first portion of the dataset and the second portion of the dataset overlap. Displaying an option to choose between different types of physical activity rate calculations provides additionally configurability regarding how the device operates. Providing additional control options without cluttering the UI enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. 
     In some examples, configuring the physical activity calculation to use the second portion of the dataset includes displaying a second user interface (e.g.,  1230 ) with a first affordance (e.g.,  1232 A) and a second affordance (e.g.,  1232 B). In such examples while displaying the second user interface, the device receives a second user input (e.g.,  1223 ). In response to receiving the second user input, in accordance with a determination that the second user input is detected at the first affordance, the device causes the second portion to be determined based upon an amount of time. In further response to receiving the second user input, in accordance with a determination that the second user input is detected at the second affordance (e.g.,  1223 ), the device causes the second portion to be determined based upon an amount of distance. 
     In some examples, after a physical activity rate is set for a type of physical activity and while a physical activity tracking function corresponding to the type of physical activity is executing, the device detects a current physical activity rate (e.g.,  1262 D). In response to detecting the current physical activity rate, in accordance with a determination that the current physical activity rate does not satisfy a first set of one or more alert criteria, the device forgoes output of a first alert. In some examples, the first set of one or more alert criteria includes whether the current physical activity rate is off pace. In some examples, the first alert is a haptic, audio, or visual alert. In further response to detecting the current physical activity rate, in accordance with a determination that the current physical activity rate satisfies the first set of one or more alert criteria, the device outputs the first alert. 
     In some examples, after outputting the first alert (e.g., a haptic our audio alert), the device receives a third user input. In some examples, the third user input is finger tap or a movement of the device (e.g., detected using one or more accelerometers), such as a wrist raise. In response to determining that the third user input satisfies a first set of one or more visual alert criteria, the device displays a visual alert (e.g.,  1244 ). In some examples, a criterion of the set of one or more visual alert criteria is that movement of the device corresponds to a wrist raise gesture. The visual alert, in accordance with a determination that the current physical activity rate is less than the physical activity rate assigned to the type of physical activity, includes a representation (e.g.,  FIG. 12Z, 1244 ) corresponding to being below the physical activity rate assigned to the type of physical activity (e.g., the current physical activity pace (e.g., a running pace) has transitioned from being on or above a target activity pace to being below the target activity pace). In some examples, less than is within a threshold. The visual alert, in accordance with a determination that the current physical activity rate is within a threshold of the physical activity rate assigned to the type of physical activity, includes a representation (e.g.,  FIG. 12Y, 1244 ) corresponding to being on target for the physical activity rate set assigned to the type of physical activity (e.g., the current physical activity pace has transitioned from being above or below a target activity pace to matching the target activity pace). The visual alert, in accordance with a determination that the current physical activity rate is more than the physical activity rate assigned to the type of physical activity, includes a representation (e.g.,  FIG. 12X, 1244 ) corresponding to being above the physical activity rate assigned to the type of physical activity (e.g., the current physical activity pace has transitioned from being on or below a target activity pace to being above the target activity pace). 
     In some examples, after displaying the visual alert (e.g.,  1244 ), the device receives a fourth user input. In some examples, the fourth user input is a gesture (e.g., wrist raise gesture, a tap gesture, or the like) that is detected within a predetermined time since receiving a first input gesture (e.g., a third user input, described above). In response to determining that the fourth user input satisfies a second set of one or more visual alert criteria, the device displays a second visual alert (e.g.,  1250 ) with additional information not in the first visual alert. In some examples, the additional information includes metrics for a current workout, such as mileage, time, or the like. 
     In some examples, a current pace is highlighted in the second visual alert. 
     In some examples, physical activities that are capable of being tracked by the device have animated affordances (e.g., running man animation with no ring,  FIG. 10I ) and physical activities that are not capable of being tracked by the device have static affordances. For example, one or more sensors of the device might not be able to detect that a particular physical activity is being performed (e.g., a physical activity that appears, to one or more sensors of the device, to be similar to a routine physical activity). In such an example, user interfaces with an affordance corresponding to the particular physical activity can include a static affordance to indicate that the particular physical activity is not capable of being tracked by the device. 
     In some examples, prior to displaying the physical activity rate user interface, the device displays a third user interface (e.g.,  1210 ) with a third affordance (e.g.,  1214 ). In such examples, the device receives a fifth user input (e.g.,  1214 ) corresponding to the third affordance, where the physical activity rate user interface (e.g.,  1216 ) is displayed in response to receiving the fifth user input. After receiving the first user input, the device redisplays the third user interface (e.g.,  1210 ), wherein the third affordance (e.g.,  1214 ) in the redisplayed third user interface includes an identification (e.g.,  1214 A) of whether the physical activity calculation is configured to use the first portion or the second portion of the dataset, and where the third affordance did not include the identification before receiving the first user input. 
     In some examples, prior to displaying the third user interface (e.g.,  1210 ), the device displays a fourth user interface (e.g.,  1204 ) with a scrollable list of affordances associated with different physical activities, where a fourth affordance (e.g.,  1206 A) in the scrollable list includes a fifth affordance (e.g.,  1208 ). In some examples, the fourth affordance is to start an outdoor run workout. In some examples, the fifth affordance is an options button for the fourth affordance. The device receives a sixth user input (e.g.,  1201 ) corresponding to selection of the fifth affordance, where the third user interface (e.g.,  1210 ) is displayed in response to receiving the sixth user input. After receiving the first user input, the device redisplays the fourth user interface (e.g.,  1204 ), where the fourth affordance (e.g.,  1206 A) in the redisplayed fourth user interface includes an identification (e.g.,  1208 B) of whether the physical activity calculation is configured to use the first portion or the second portion of the dataset, and where the fourth affordance did not include the identification before receiving the first user input. 
     In some examples, the fourth affordance (e.g.,  1206 A) includes an identification (e.g.,  1208 B) of a first pace assigned to a physical activity corresponding to the fourth affordance, where a sixth affordance (e.g.,  1206 B) in the scrollable list includes an identification of a second pace assigned to a physical activity corresponding to the sixth affordance, and where the second pace is different from the first pace. 
     In some examples, the physical activity rate user interface is displayed further in response to a physical activity rate being set (as depicted in  FIGS. 12I-12N ). 
     Note that details of the processes described above with respect to method  1300  (e.g.,  FIG. 13 ) are also applicable in an analogous manner to the methods described above. For example, method  1300  optionally includes one or more of the characteristics of the various methods described below with reference to method  700 , method  900 , or method  1100 . For example, the user interface of method  700  can be based upon a number of pace alerts output that were configured using method  1300 . For another example, the user interface of method  900  can be based upon a number of pace alerts output that were configured using method  1300 . For another example, the user interface of method  1300  can configure a pace that is then used to determine a boundary of a workout (as provided in method  1100 ). For brevity, these details are not repeated below. 
     The foregoing description, for purpose of explanation, has been described with reference to specific examples. 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 examples 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 examples 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 increase interactions between users. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records relating to a user&#39;s health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information. 
     The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to display representations of the personal information. Accordingly, use of such personal information data enables users to view feedback regarding data received from other users. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user&#39;s general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals. 
     The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country. 
     Despite the foregoing, the present disclosure also contemplates examples in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of activity and workout services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In another example, users can select not to provide activity associated data for activity and/or workout services. In yet another example, users can select to limit the length that activity associated data is maintained or entirely prohibit the development of user interfaces described herein. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app. 
     Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user&#39;s privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods. 
     Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed examples, the present disclosure also contemplates that the various examples can also be implemented without the need for accessing such personal information data. That is, the various examples 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 activity 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 services described herein, or publicly available information.

Metadata:
Filing Date: 20180927
Publication Date: 20200609
Grant Date: 20200609
Priority Date: 20180507
Inventors: WILLIAMS, ALED HYWEL
BUTCHER, GARY IAN
Sundstrom, Matthew J.
WIEBE, MOLLY PRAY
Assignee: APPLE INC
CPC Classifications: [{"code": "A61B5/681", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04M1/72583", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/04847", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0481", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/1118", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/0488", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0485", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F1/163", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B2562/0219", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04L67/04", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W4/029", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B71/0619", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04M1/72409", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L67/04", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04M1/72469", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/0481", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0488", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L51/04", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F11/3438", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F11/327", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0485", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04817", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/038", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0346", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/011", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F1/1626", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B24/00", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04847", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04106", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/0484", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F2203/04104", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B2562/0219", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/016", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/00", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/681", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0483", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0362", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F1/163", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/041", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0485", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04105", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/0485", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/1118", "inventive": true, "first": true, "tree": "[]"}, {"code": "A61B5/1118", "inventive": true, "first": true, "tree": "[]"}, {"code": "A63B22/00", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/681", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/11", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F1/163", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F1/1643", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/048", "inventive": true, "first": true, "tree": "[]"}, {"code": "A61B2562/0219", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04W4/029", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B71/0619", "inventive": true, "first": false, "tree": "[]"}]
Family ID: 68384176