PATENT DOCUMENT

Publication Number: US-12036018-B2
Application Number: US-202217892534-A
Country: US
Kind Code: B2

Title: Workout monitor interface

Abstract:
The present disclosure relates to systems and processes for monitoring a workout and for generating improved interfaces for the same. In one example, while receiving activity data for a workout session, a first user interface of a workout application is displayed. While displaying the first user interface of the workout application, user input of a first type is detected. In response to detecting the user input of the first type, a first control affordance to pause receiving the activity data for the workout session is displayed, and activity data for the workout session is continued to be received.

Claims:
What is claimed is: 
     
       1. A wearable electronic device, comprising:
 a display; 
 one or more input devices; 
 one or more processors; 
 memory; and 
 one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for:
 while receiving activity data for a workout session:
 displaying, via the display, a first user interface of a workout application; and 
 while displaying the first user interface of the workout application, detecting, via the one or more input devices, user input of a first type; 
 
 in response to detecting the user input of the first type:
 displaying, via the display, a transition from the first user interface of the workout application to a second user interface of the workout application, wherein the second user interface includes a first control affordance to pause receiving the activity data for the workout session; and 
 continuing to receive activity data for the workout session; 
 
 while displaying the second user interface and while receiving activity data for the workout session, detecting, via the one or more input devices, a selection of the first control affordance; and 
 in response to detecting the selection of the first control affordance, pausing the receiving of the activity data for the workout session. 
 
 
     
     
       2. The wearable electronic device of  claim 1 , wherein the user input of the first type is a touch gesture. 
     
     
       3. The wearable electronic device of  claim 1 , the one or more programs further including instructions for:
 in response to detecting the user input of the first type, displaying, via the display, a second control affordance to stop the workout session, wherein the second control affordance is displayed concurrently with the first control affordance. 
 
     
     
       4. The wearable electronic device of  claim 1 , the one or more programs further including instructions for:
 in response to detecting the selection of the first control affordance:
 displaying, via the display, a third control affordance to stop the workout session; and 
 displaying, via the display, a fourth control affordance to resume receiving activity data for the workout session. 
 
 
     
     
       5. The wearable electronic device of  claim 4 , the one or more programs further including instructions for:
 in response to detecting the selection of the first control affordance:
 displaying, via the display, a first indication that the workout session is paused in a first portion of a user interface, wherein the third control affordance to stop the workout session and the fourth control affordance to resume receiving the activity data for the workout session are displayed in a second portion of the user interface different from the first portion. 
 
 
     
     
       6. The wearable electronic device of  claim 1 , the one or more programs further including instructions for:
 in response to detecting the user input of the first type:
 displaying, via the display, a second indication of a type of workout session; and 
 displaying, via the display, a fifth control affordance to stop the workout session. 
 
 
     
     
       7. The wearable electronic device of  claim 6 , wherein displaying the first user interface of the workout application includes:
 displaying, via the display, a third indication of the type of workout session, the third indication of the type of workout session different from the second indication. 
 
     
     
       8. The wearable electronic device of  claim 1 , wherein the first user interface of the workout application includes a set of one or more workout metrics. 
     
     
       9. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a wearable electronic device with a display and one or more input devices, the one or more programs including instructions for:
 while receiving activity data for a workout session:
 displaying, via the display, a first user interface of a workout application; and 
 while displaying the first user interface of the workout application, detecting, via the one or more input devices, user input of a first type; 
 
 in response to detecting the user input of the first type:
 displaying, via the display, a transition from the first user interface of the workout application to a second user interface of the workout application, wherein the second user interface includes a first control affordance to pause receiving the activity data for the workout session; and 
 continuing to receive activity data for the workout sessions; 
 
 while displaying the second user interface and while receiving activity data for the workout session, detecting, via the one or more input devices, a selection of the first control affordance; and 
 in response to detecting the selection of the first control affordance, pausing the receiving of the activity data for the workout session. 
 
     
     
       10. The non-transitory computer-readable storage medium of  claim 9 , wherein the user input of the first type is a touch gesture. 
     
     
       11. The non-transitory computer-readable storage medium of  claim 9 , the one or more programs further including instructions for:
 in response to detecting the user input of the first type, displaying, via the display, a second control affordance to stop the workout session, wherein the second control affordance is displayed concurrently with the first control affordance. 
 
     
     
       12. The non-transitory computer-readable storage medium of  claim 9 , the one or more programs further including instructions for:
 in response to detecting the selection of the first control affordance:
 displaying, via the display, a third control affordance to stop the workout session; and 
 displaying, via the display, a fourth control affordance to resume receiving activity data for the workout session. 
 
 
     
     
       13. The non-transitory computer-readable storage medium of  claim 12 , the one or more programs further including instructions for:
 in response to detecting the selection of the first control affordance:
 displaying, via the display, a first indication that the workout session is paused in a first portion of a user interface, wherein the third control affordance to stop the workout session and the fourth control affordance to resume receiving the activity data for the workout session are displayed in a second portion of the user interface different from the first portion. 
 
 
     
     
       14. The non-transitory computer-readable storage medium of  claim 9 , the one or more programs further including instructions for:
 in response to detecting the user input of the first type:
 displaying, via the display, a second indication of a type of workout session; and 
 displaying, via the display, a fifth control affordance to stop the workout session. 
 
 
     
     
       15. The non-transitory computer-readable storage medium of  claim 14 , wherein displaying the first user interface of the workout application includes:
 displaying, via the display, a third indication of the type of workout session, the third indication of the type of workout session different from the second indication. 
 
     
     
       16. The non-transitory computer-readable storage medium of  claim 9 , wherein the first user interface of the workout application includes a set of one or more workout metrics. 
     
     
       17. A method, comprising:
 at a wearable electronic device including display and one or more input devices:
 while receiving activity data for a workout session:
 displaying, via the display, a first user interface of a workout application; and 
 while displaying the first user interface of the workout application, detecting, via the one or more input devices, user input of a first type; 
 
 in response to detecting the user input of the first type:
 displaying, via the display, a transition from the first user interface of the workout application to a second user interface of the workout application, wherein the second user interface includes a first control affordance to pause receiving the activity data for the workout session; and 
 continuing to receive activity data for the workout session; 
 
 while displaying the second user interface and while receiving activity data for the workout session, detecting, via the one or more input devices, a selection of the first control affordance; and 
 in response to detecting the selection of the first control affordance, pausing the receiving of the activity data for the workout session. 
 
 
     
     
       18. The method of  claim 17 , wherein the user input of the first type is a touch gesture. 
     
     
       19. The method of  claim 17 , further comprising:
 in response to detecting the user input of the first type, displaying, via the display, a second control affordance to stop the workout session, wherein the second control affordance is displayed concurrently with the first control affordance. 
 
     
     
       20. The method of  claim 17 , further comprising:
 in response to detecting the selection of the first control affordance:
 displaying, via the display, a third control affordance to stop the workout session; and 
 displaying, via the display, a fourth control affordance to resume receiving activity data for the workout session. 
 
 
     
     
       21. The method of  claim 20 , further comprising:
 in response to detecting the selection of the first control affordance:
 displaying, via the display, a first indication that the workout session is paused in a first portion of a user interface, wherein the third control affordance to stop the workout session and the fourth control affordance to resume receiving the activity data for the workout session are displayed in a second portion of the user interface different from the first portion. 
 
 
     
     
       22. The method of  claim 17 , further comprising:
 in response to detecting the user input of the first type:
 displaying, via the display, a second indication of a type of workout session; and 
 displaying, via the display, a fifth control affordance to stop the workout session. 
 
 
     
     
       23. The method of  claim 22 , wherein displaying the first user interface of the workout application includes:
 displaying, via the display, a third indication of the type of workout session, the third indication of the type of workout session different from the second indication. 
 
     
     
       24. The method of  claim 17 , wherein the first user interface of the workout application includes a set of one or more workout metrics. 
     
     
       25. The wearable electronic device of  claim 1 , wherein the first user interface does not include the first control affordance to pause receiving the activity data for the workout session. 
     
     
       26. The wearable electronic device of  claim 1 , wherein the first user interface includes an activity metric associated with the workout session, the one or more programs further including instructions for:
 in response to detecting the user input of the first type, ceasing display of the activity metric associated with the workout session. 
 
     
     
       27. The wearable electronic device of  claim 1 , wherein:
 the first user interface includes at least one activity metric associated with the activity data for the workout session; 
 displaying the transition from the first user interface of the workout application to the second user interface of the workout application includes ceasing display of the at least one activity metric associated with the activity data for the workout session; and 
 the second user interface does not include an activity metric associated with the activity data for the workout session. 
 
     
     
       28. The wearable electronic device of  claim 1 , wherein the user input of a first type is a swipe input. 
     
     
       29. The non-transitory computer-readable storage medium of  claim 9 , wherein the first user interface does not include the first control affordance to pause receiving the activity data for the workout session. 
     
     
       30. The non-transitory computer-readable storage medium of  claim 9 , wherein the first user interface includes an activity metric associated with the workout session, the one or more programs further including instructions for:
 in response to detecting the user input of the first type, ceasing display of the activity metric associated with the workout session. 
 
     
     
       31. The non-transitory computer-readable storage medium of  claim 9 , wherein:
 the first user interface includes at least one activity metric associated with the activity data for the workout session; 
 displaying the transition from the first user interface of the workout application to the second user interface of the workout application includes ceasing display of the at least one activity metric associated with the activity data for the workout session; and 
 the second user interface does not include an activity metric associated with the activity data for the workout session. 
 
     
     
       32. The non-transitory computer-readable storage medium of  claim 9 , wherein the user input of a first type is a swipe input. 
     
     
       33. The method of  claim 17 , wherein the first user interface does not include the first control affordance to pause receiving the activity data for the workout session. 
     
     
       34. The method of  claim 17 , wherein the first user interface includes an activity metric associated with the workout session, the method further comprising:
 in response to detecting the user input of the first type, ceasing display of the activity metric associated with the workout session. 
 
     
     
       35. The method of  claim 17 , wherein:
 the first user interface includes at least one activity metric associated with the activity data for the workout session; 
 displaying the transition from the first user interface of the workout application to the second user interface of the workout application includes ceasing display of the at least one activity metric associated with the activity data for the workout session; and 
 the second user interface does not include an activity metric associated with the activity data for the workout session. 
 
     
     
       36. The method of  claim 17 , wherein the user input of a first type is a swipe input.

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

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

     It should be noted that the icon labels illustrated in  FIG.  4 A  are merely exemplary. For example, icon  422  for video and music player module  152  is labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon. 
       FIG.  4 B  illustrates an exemplary user interface on a device (e.g., device  300 ,  FIG.  3   ) with a touch-sensitive surface  451  (e.g., a tablet or touchpad  355 ,  FIG.  3   ) that is separate from the display  450  (e.g., touch screen display  112 ). Device  300  also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors  359 ) for detecting intensity of contacts on touch-sensitive surface  451  and/or one or more tactile output generators  357  for generating tactile outputs for a user of device  300 . 
     Although some of the examples that follow will be given with reference to inputs on touch screen display  112  (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in  FIG.  4 B . In some embodiments, the touch-sensitive surface (e.g.,  451  in  FIG.  4 B ) has a primary axis (e.g.,  452  in  FIG.  4 B ) that corresponds to a primary axis (e.g.,  453  in  FIG.  4 B ) on the display (e.g.,  450 ). In accordance with these embodiments, the device detects contacts (e.g.,  460  and  462  in  FIG.  4 B ) with the touch-sensitive surface  451  at locations that correspond to respective locations on the display (e.g., in  FIG.  4 B,  460    corresponds to  468  and  462  corresponds to  470 ). In this way, user inputs (e.g., contacts  460  and  462 , and movements thereof) detected by the device on the touch-sensitive surface (e.g.,  451  in  FIG.  4 B ) are used by the device to manipulate the user interface on the display (e.g.,  450  in  FIG.  4 B ) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein. 
     Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously. 
       FIG.  5 A  illustrates exemplary personal electronic device  500 . Device  500  includes body  502 . In some embodiments, device  500  can include some or all of the features described with respect to devices  100  and  300  (e.g.,  FIGS.  1 A- 4 B ). In some embodiments, device  500  has touch-sensitive display screen  504 , hereafter touch screen  504 . Alternatively, or in addition to touch screen  504 , device  500  has a display and a touch-sensitive surface. As with devices  100  and  300 , in some embodiments, touch screen  504  (or the touch-sensitive surface) optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touch screen  504  (or the touch-sensitive surface) can provide output data that represents the intensity of touches. The user interface of device  500  can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device  500 . 
     Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety. 
     In some embodiments, device  500  has one or more input mechanisms  506  and  508 . Input mechanisms  506  and  508 , if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device  500  has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device  500  with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device  500  to be worn by a user. 
       FIG.  5 B  depicts exemplary personal electronic device  500 . In some embodiments, device  500  can include some or all of the components described with respect to  FIGS.  1 A,  1 B, and  3   . Device  500  has bus  512  that operatively couples I/O section  514  with one or more computer processors  516  and memory  518 . I/O section  514  can be connected to display  504 , which can have touch-sensitive component  522  and, optionally, intensity sensor  524  (e.g., contact intensity sensor). In addition, I/O section  514  can be connected with communication unit  530  for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. Device  500  can include input mechanisms  506  and/or  508 . Input mechanism  506  is, optionally, a rotatable input device or a depressible and rotatable input device, for example. Input mechanism  508  is, optionally, a button, in some examples. 
     Input mechanism  508  is, optionally, a microphone, in some examples. Personal electronic device  500  optionally includes various sensors, such as GPS sensor  532 , accelerometer  534 , directional sensor  540  (e.g., compass), gyroscope  536 , motion sensor  538 , and/or a combination thereof, all of which can be operatively connected to I/O section  514 . 
     Memory  518  of personal electronic device  500  can be a non-transitory computer-readable storage medium, 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 process  900  ( FIG.  9   ). The computer-executable instructions can also be stored and/or transported within any non-transitory computer-readable storage medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For purposes of this document, a “non-transitory 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. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device  500  is not limited to the components and configuration of  FIG.  5 B , but can include other or additional components in multiple configurations. 
     As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices  100 ,  300 , and/or  500  ( FIGS.  1 A-B ,  3 , and  5 A-B). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) each optionally constitute an affordance. 
     As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad  355  in  FIG.  3    or touch-sensitive surface  451  in  FIG.  4 B ) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system  112  in  FIG.  1 A  or touch screen  112  in  FIG.  4 A ) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user&#39;s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device). 
     As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation. 
     In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity. 
     The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures. 
     An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero. 
     In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input). 
     In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances). 
     For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. 
     Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device  100 , device  300 , or device  500 . 
     Exemplary User Interfaces 
     Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device  100 , device  300 , or device  500 . 
       FIG.  6    illustrates an example system  600  for aggregating wellness and other types of data. Wellness data can include, but is not limited to, any type of data associated with a person&#39;s health, such as their physical activity data, workout data, weight, heart rate, blood pressure, blood glucose level, medication compliance, or the like. System  600  can be used to collect wellness data associated with a user, store the wellness data, present the wellness data to the user in useful ways, and selectively share the user&#39;s wellness data with other users or entities based on permissions set by the user. In addition, in some examples, system  600  can further be used to collect non-wellness data along with wellness data, correlate the non-wellness data with the wellness data, and display the non-wellness data with the wellness data. 
     System  600  can include one or more user devices  610 , which can include any type of electronic device, such as a mobile phone, tablet computer, desktop computer, laptop computer, PDA, or the like. In some examples, user device  610  can include a device similar or identical to devices  100 ,  300 , or  500 , described above. User device  610  can include an operating system and a wellness database  611  (e.g., memory  102 ,  370 , or  518 ) for securely storing wellness or non-wellness data along with associated metadata, such as the time the data was recorded, type of data, device used to record the data, user associated with the data, and the like. User device  610  can further include application programming interfaces (APIs) with access controls for storing data in the wellness database  611  and for accessing data stored in the wellness database  611 . 
     User device  610  can be configured to receive wellness or non-wellness data from various sources and can store the received data in the wellness database  611 . For example, user device  610  can be configured to receive wellness or non-wellness data from sensors  602 ,  604 ,  606 , and  608 . These sensors can include any type of sensor capable of obtaining wellness data, such as a biometric sensor, activity tracker, or the like. For example, sensors  602 ,  604 ,  606 , and  608  can include, but are not limited to, a scale, blood pressure cuff, blood glucose monitor, electrocardiogram, step counter, gyroscope, accelerometer, SpO2 sensor, respiration sensor, posture sensor, stress sensor, photoplethysmogram, galvanic skin response sensor, temperature sensor, or the like. Sensors  602 ,  604 ,  606 , and  608  can also include other types of sensors, such as audio sensors, ambient light sensors, electromagnetic sensors, touch sensors, capacitive sensors, and the like, for obtaining non-wellness data, such as situational data, temporal data, personal data, contact data, and the like data. In some examples, each sensor can be a separate device, while, in other examples, any combination of two or more of the sensors can be included within a single device. For example, the gyroscope, accelerometer, photoplethysmogram, galvanic skin response sensor, and temperature sensor can be included within a wearable electronic device, such as a smart watch, while the scale, blood pressure cuff, blood glucose monitor, SpO2 sensor, respiration sensor, posture sensor, stress sensor, and asthma inhaler can each be separate devices. While specific examples are provided, it should be appreciated that other sensors can be used and other combinations of sensors can be combined into a single device. 
     Sensors  602 ,  604 ,  606 , and  608  can be used to measure wellness or non-wellness data continuously, intermittently, periodically, or at any other desired frequency or interval of time. For example, sensors  602 ,  604 ,  606 , and  608  can be used to obtain a single measurement or multiple measurements over a length of time. Sensors  602 ,  604 ,  606 , and  608  can be configured to measure wellness or non-wellness data at the same intervals of time, or can be configured to measure wellness or non-wellness data at different intervals of time. These intervals may be set by a user or may be a default setting for each sensor. Additionally, sensors  602 ,  604 ,  606 ,  608  can be used to measure wellness or non-wellness data at any time or location desired by the user. Moreover, sensors  602 ,  604 ,  606 , and  608  can be used with or without the supervision of a healthcare provider. For example, a user can use sensors  602 ,  604 ,  606 , and  608  to obtain sensor measurements at home without the supervision of a medical professional. 
     In some examples, user device  610  can include software sensor applications  613  (e.g., third party applications) associated with each of sensors  602 ,  604 ,  606 , and  608  for interfacing with the sensors to allow user device  610  to receive the wellness or non-wellness data. In these examples, the applications  613  can use the device&#39;s APIs to store the wellness or non-wellness data in the wellness database  611  of user device  610 . In some examples, device  610  can be a smart phone, tablet computer, or the like, and the software sensor applications  613  can include software applications downloadable onto device  610 . It should be understood that “third party” can correspond to an entity different than the manufacturer of device  610  and/or the entity that created and/or maintains the operating system of device  610 . In these instances, third party applications and their corresponding sensors can communicate and function within the operating system of device  610  according to a predefined device protocol associated with device  610 . 
     The applications  613  can similarly use the device&#39;s APIs to access data stored in the wellness database  611 . In other examples, user device  610  can be configured to share one or more communication formats with sensors  602 ,  604 ,  606 , and  608  to allow user device  610  to receive and interpret the wellness or non-wellness data from the sensors. The received data can then be stored in the wellness database  611  of user device  610 . 
     User device  610  can further receive wellness or non-wellness data from its own wellness or non-wellness data sensors  620  (e.g., sensors  168 ,  359 , and  520 ), from a user interacting with user device  610 , from another entity, such as a physician, or from other non-sensor sources. For example, using the device&#39;s APIs, wellness or non-wellness data can be received from applications  617  (third party or first party applications) on user device  610 , such as a clock application, a calendaring application, a gaming application, an application from a healthcare provider, a messaging application, a physical activity application, a workout application, or the like. The wellness or non-wellness data from the applications  617  can originate from sensors  620 , a user interacting with the applications, a remote database (e.g., database for a medical website), a healthcare provider institution (e.g., via the institution&#39;s application  617 ), or the like. In these examples, the usage of the application  617  (e.g., how long you play a video game application, when you play the video game, number of times interacting with a stock application, number of times interacting with a social networking application, length of time interacting with a social networking application, etc.), usage of user device  610  (e.g., length of time on the phone or number of text messages sent as determined from a phone payment application, time spent browsing the Internet as determined from the device&#39;s browser, etc.), time spent listening to music as determined from a music or streaming radio application, time spent using a remote application for controlling a television, amount of time or money spent on shopping websites, weather data from a weather application (e.g., to determine how weather affects a user&#39;s health), type of events occurring in the user&#39;s life as determined from a calendar (e.g., meetings, birthdays, holidays, etc.), interactions with certain people as determined from a contact list and/or calendar application and/or a messaging application and/or phone of user device  610 , or the like, can be received by user device  610  and stored in the wellness database  611 . 
     In some examples, default or user-selected settings can be provided to restrict the access that at least one application (e.g., at least one of applications  613  and  617 ) on user device  610  has to the wellness database  611  of user device  610  (for both storage and retrieval purposes) and to the sensor data generated by sensors  620  within user device  610  and/or sensor data generated by sensors  602 ,  604 ,  606 , and  608 . For example, an application for tracking a user&#39;s running sessions can be granted access to the data generated by the GPS sensor of user device  610 , but can be prevented from accessing the user&#39;s blood pressure data stored in the wellness database  611 . In some examples, an entity other than the owner of user device  610  can set the authorization settings for various applications on user device  610 . For example, the manufacturer of user device  610  and/or the entity that created and/or maintains the operating system of user device  610  can evaluate the applications to determine if they should be given access to the user&#39;s wellness data and/or sensor data generated or received by user device  610 . In some examples, these settings can be overridden by the user. User device  610  can further include a display for displaying the stored wellness data or non-wellness data. 
       FIG.  7    illustrates system  700  for sharing user wellness data. System  700  can include user server  714  communicatively coupled to user device  610  via network  712 , which can include the Internet, an intranet, or any other wired or wireless public or private network. User device  610  can be configured to securely transmit the aggregated wellness or non-wellness data and associated metadata stored on the device to user server  714  for storage in user database  716 . In some examples, the wellness or non-wellness data and associated metadata can be transmitted to user server  714  for storage in user database  716  in response to an explicit request for such a transfer by the user of device  610 , while, in other examples, the wellness or non-wellness data can be synced with the data in user database  716  continuously, periodically, intermittently, or at any desired frequency. In yet other examples, the user&#39;s wellness or non-wellness data can be stored only on user device  610  and may not be stored in an external database. 
     In some examples, user server  714  and user database  716  can be configured to securely store a user&#39;s wellness or non-wellness data using a public/private key system that only allows the owner of the wellness or non-wellness data to decrypt the data. Additionally, the wellness or non-wellness data stored in user database  716  can be stored anonymously (e.g., without identifying and/or personal information about the user, such as a legal name, username, time and location data, or the like). In this way, other users, hackers, and the owner/operator of user database  716  cannot determine the identity of the user associated with the data stored in database  716 . In some examples, a user can access their wellness or non-wellness data stored in user database  716  from a user device that is different than the one used to upload the wellness or non-wellness data to user server  714 . In these instances, the user can be required to provide login credentials to access their wellness or non-wellness data. User server  714  can be configured to perform the authorization process to restrict access to the data within user database  716 . 
     System  700  can further include any number of other user devices  722  and  724  coupled to network  712 . In some examples, user devices  722  and  724  can be operated by the same user as user device  610 . In these instances, the user can access their wellness or non-wellness data stored in user database  716  by providing user server  714  with the appropriate credentials. In some examples, wellness and non-wellness data can be synced between user database  716  and one or more of user device  610 ,  722 , and  724 . In other examples, the user of user devices  722  and  724  can be a person that is different than the user of user device  610 . In these examples, the users of devices  722  and  724  cannot access the wellness or non-wellness data of the user of user device  610  without the authorization of the user of user device  610 . If authorization is given, wellness or non-wellness data can be shared with the users of user devices  722  and  724 . 
     In some examples, any of the above described sources of wellness or non-wellness data can be configured to measure, generate, or receive wellness or non-wellness data continuously, intermittently, periodically, or at any other desired frequency or interval of time. As such, the wellness or non-wellness data can similarly be stored or updated in wellness database  611  or user database  716  continuously, intermittently, periodically, or at any other desired frequency or interval of time. The frequencies and intervals of time used for measuring, generating, receiving, or storing wellness or non-wellness can be the same or they can be different. Additionally, these frequencies and intervals can be default values or they can be set by a user to provide the user with wellness or non-wellness data that has been updated within a desired length of time. 
     While not shown, it should be appreciated that many other user devices can be coupled to user server  714  through network  712  to collect and store wellness or non-wellness data for other users in a manner similar to that described above. 
     Workout Monitor 
       FIG.  8    illustrates an exemplary interface  800  for displaying a menu of applications on an electronic device, such as device  100 ,  300 ,  500 , or  610 . As shown, interface  800  includes multiple application icons  802  that, when selected by a user, causes the electronic device to open the associated application. For example, in response to a user selection of an application icon  802  corresponding to a workout application for monitoring a user&#39;s workout, the workout application can be opened and process  900 , shown in  FIG.  9   , can be performed. Process  900  can be performed by device  100 ,  300 ,  500 , or  610  to detect movement associated with the device during a workout, recognizing it as being associated with a physical activity performed by the user using the device, monitoring various metrics of the detected physical activity, determining metrics of the workout based on the monitored metrics of the detected physical activity, and displaying one or more of the metrics of the workout on a display of the device. 
     At block  902 , one or more processors of the device can receive a selection of a type of workout. The selected type of workout can include any type of workout, such as running, walking, cycling, swimming, yoga, dancing, climbing, cross-training, rowing, or the like. In some examples, the one or more processors of the device can cause, on the display of the device, a display of a list of available types of workouts that a user can select. In these examples, the selection of the type of workout can be received by the one or more processors of the device in response to a user indicating a selection of one of the displayed available types of workouts (e.g., via mouse click, touch on a touch sensitive display, or the like). 
     For example,  FIG.  10    illustrates an example interface  1000  that can be displayed at block  902  of process  900 . As shown, interface  1000  can include an application identifier  1002  indicating that the “Workout” application is being displayed, a time indicator  1004  indicating the current time, and a list of workout types  1006  that includes a list of selectable objects associated with available workouts that can be selected by a user. The types of workouts contained in the list of workout types  1006  can be ordered in any desired manner, such as alphabetically, by frequency of performance, by time since last performed, in a user-selected order, or combinations thereof. For example, the first selectable object can correspond to the workout that was most recently performed by the user (“Running”), and the remaining selectable objects can be ordered based on a frequency that the corresponding workouts have been performed. In some examples, the list of workout types  1006  can include more types of workouts than can be displayed at one time on the display of the device. In these examples, the device can display the other types of workouts in response to a user initiating a scroll operation (e.g., by making a swipe or touch and drag motion on the touch sensitive display). While  FIG.  10    shows an example list of workout types  1006 , it should be appreciated that the list of workout types  1006  can include any number and types of workouts. 
     The type of workout selected in block  902  may have multiple workout metrics associated with it. For example, if the workout type “Running” is selected, the workout metrics of elapsed time, distance, pace, and heart rate may be associated with the workout type. In another example, the “Running” workout type may be associated with the elapsed time, distance, pace, heart rate, and calories burned workout metrics. In another example, the cycling workout type may be associated with the elapsed time and distance workout metrics. While a few examples of workout metrics have been given, other workout metrics may also be possible, such as speed, rotations per minute (RPM), and laps. 
     Additionally, while there may be a default set of workout metrics associated with a given workout type, the set of workout metrics associated with a workout type may be user configurable via a user configuration interface. For example, using a touch-screen or other user input, a user can select workout metrics that are an associated with a given workout metric. 
       FIG.  11    illustrates another example interface  1100  that can be displayed at block  902  of process  900 . Similar to interface  1000 , interface  1100  can include an application identifier  1002 , a time indicator  1004 , and a list of workout types  1006 . However, in interface  1100 , one selectable object associated with a type of workout in the list of workout types  1006  can be larger than the selectable objects associated with other types of workouts and can include additional information about the workout type. This selectable object can correspond to the workout that was most recently performed by the user. For example, as shown in  FIG.  11   , the selectable object for the “Running” workout type can be twice as large as the other selectable objects and can include information associated with the most recent workout of that type. In particular, information about the date, distance, pace, and elapsed time of the most recent run is displayed on the selectable object for the “Running” type of workout. The selectable objects below the larger selectable object can be ordered based on a frequency that the corresponding workouts are performed. Alternatively, the objects may be ordered by recency, or a combination of recency and frequency. In some examples, an interface similar to interface  1000  can be displayed the first time that a user is using the workout application on the device, while an interface similar to interface  1100  can be displayed during any subsequent use of the application. 
     Optionally, in block  902 , a later block of process  900 , or in a block after block  902  that is not depicted in  FIG.  9   , a goal for the type of workout selected can be received. The goal can include an identification of a workout metric of the selected workout (e.g., a distance, a duration, a number of Calories burned, a pace, or the like) and a goal value for the workout metric. For example, for a running type of workout, the goal received at block  904  can include a distance workout metric and a value of 10 kilometers. Another example goal can include a duration workout metric and a value of 45 minutes, or a Calorie workout metric and a value of 110 Calories. In some examples, the one or more processors of the device can cause, on the display of the device, a display of an interface that allows the user to select a workout metric of the workout and to enter a desired value for that workout metric. 
     For example,  FIG.  12    illustrates an example interface  1200  that can be displayed at block  904  of process  900  in response to receiving a selection of a “running” type of workout at block  902  (e.g., by a user selecting the “Running” option in either interface  1000  or  1100 ). As shown, interface  1200  can include a workout type identifier  1202  indicating that the “Running” type of workout was selected, a time indicator  1204  indicating the current time, a value  1206  for the workout metric of the workout, buttons  1208  and  1210  for adjusting the value  1206 , a best value  1212  of the workout metric of the workout, and a start button  1214  for selecting the goal and beginning the workout. In this example, the distance workout metric of the workout is being selected and the value for that workout metric can be selected by adjusting value  1206  up or down using buttons  1210  or  1208 , respectively. In other examples, the value for that attribute can be selected by moving (e.g., rotating) a rotatable input mechanism of the device. The initial value  1206  displayed in interface  1200  can be a default value (e.g., 0), a value used in a previous workout, an average value from two or more previous workouts, or any other desired value. Once the desired value  1206  is displayed, a user can select the start button  1214  to set the workout goal to be a distance goal having the value of value  1206 . In some examples, best value  1212  can be selectable and can cause the goal of the workout to be the attribute and value of the displayed best value  1212 . For example, in response to a selection of best value  1212  made by a user tapping on the touch-sensitive display at a location corresponding to best value  1212 , the goal of the workout can be set to a distance goal of 5.0 miles. In other examples, best value  1212  can represent a value determined based on past performance of the user, the user&#39;s contacts, the user&#39;s friends, a predefined group of users, or the like. For example, best value  1212  can instead represent the longest distance run by the user over a predetermined length of time (e.g., the last week), an average distance run by the user, an average distance run by the user over a predetermined length of time (e.g., the last week), a longest distance run by the user&#39;s contacts/friends/running group, a longest distance run by the user&#39;s contacts/friends/running group over a predetermined length of time (e.g., the last week), an average distance run by the user&#39;s contacts/friends/running group, an average distance run by the user&#39;s contacts/friends/running group over a predetermined length of time (e.g., the last week), or the like. In some examples, the device can allow a user to select a different workout metric of the workout as the goal by displaying a different interface associated with a different workout metric of the workout in response to a request from the user. In some examples, the request can be made by a vertical or horizontal swipe gesture across the touch sensitive display of the device, a button press, a movement of a rotatable input mechanism of the device, a user contact having a characteristic intensity above an intensity threshold on a display of the device, or any other desired form of input. 
     In other examples, the device can select from other of interfaces similar to interface  1200  that allows for other types of goals to be set. For example, while example interfaces for selecting specific workout metrics for the “Running” type of workout have been provided in  FIG.  12   , it should be appreciated that interfaces for selecting any workout metric of any type of workout can be provided based on the types of workout metrics associated with the workout type selected at block  902 . For example, if the type of workout selected at block  902  was “yoga,” an interface for selecting a duration goal or a Calorie goal may be displayed, but an interface for selecting a distance goal may not be displayed. 
     In some examples, in response to a selection of start button  1214  in interface  1200 , the device can optionally display a countdown before beginning the workout selected at block  902  using the selected goal. 
     Referring back to  FIG.  9   , at block  904 , in response to a request to display workout metric data, a pro-view display of the workout metrics associated with the workout type selected in block  902  is made on the device. The request to display workout metric data may take the form of, for example, detection of activity associated with start button  1214  of  FIG.  12   . As another example, the request to display workout metric data could also take the form of the selection of workout type in block  902 . As another example, the request to display workout metric data could be associated with detecting movement or some other information associated with sensors  620  of user device  610  ( FIG.  6   ). 
     The pro-view display includes an indicator representative of each of the plurality of workout metrics associated with the workout type selected in block  902 . For example,  FIG.  13    depicts interface  1300 , which is an example of the pro-view displayed in block  904 .  FIG.  13    is the pro-view for the workout type “Running” and includes two associated workout metrics. Interface  1300  includes a first indicator  1310  representing a first workout metric, in this case a distance traveled metric, and a second indicator  1312  representing a second workout metric, in this case a pace workout metric. Interface  1300  may also include the selected workout type in the form of workout type  1302  and other information, such as time  1304 . 
     Interface  1300  also includes a focus indicator  1320  that highlights a workout metric indicator that is currently selected as the focused workout metric. In interface  1300 , first indicator  1310  represents the focused workout metric. The focus indicator  1320  may be a box or other shape around one of the workout metric indicators, but other methods of highlighting a workout metric indicator may also be used, such as a different coloring, a larger font size, a different background color, or blinking of the indicator. The focus indicator  1320  may be moved to other workout metrics indicators based on, for example, user input. Examples of user input include receiving a gesture on a touch-sensitive display or mechanical user input device, such as a rotatable crown or button. Focus indicator  1320  may aid in a user concentrating on a particular workout metric that is important to the user or for the particular workout type. 
     As explained above, the workout metrics associated with a given workout type may be configurable.  FIG.  14    depicts interface  14  for the “Running” workout type but with a different set of workout metrics associated with the “Running” workout type as compared to interface  1300  of  FIG.  13   . Interface  1400  includes first indicator  1410  for the distance workout metric, second indicator  1412  for the pace workout metric, third indicator  1414  for the Calories workout metric, fourth indicator  1416  for the time elapsed workout metric, and fifth indicator  1418  for the heartrate workout metric. In interface  1400 , focus indicator  1420  has been moved to represent that second indicator  1412  represents the focused workout metric. While two example interfaces having two and five workout metric indicators have been provided, other numbers of indicators may be included in the pro-view. For example, the pro-view may include exactly four indicators of workout metrics. Additionally, the different indicators for the workout metrics may use different colors to set apart the different indicators and make for a more pleasant viewing experience. 
     The ordering of the workout metric indicators in pro-view displays may be configurable. For example, the position of first indicator  1410  with respect to second indicator  1412  may be changed. In some cases, the position may be changed by, for example, dragging the first indicator to a new position while in a position configuration user interface. 
     Also at block  904 , before or after displaying the pro-view, the workout may also be initiated. Initiating the workout can include activating one or more activity sensors (e.g., sensors  168 ,  359 , and  520 ) and recording activity data provided by those one or more activity sensors. In some examples, the activity sensors activated at block  904  can be selected based on the type of workout selected at block  902 . For example, a biometric sensor for measuring heart rate, GPS sensor for measuring position, and accelerometer for measuring motion to determine distance traveled can be activated if a running type of workout was selected at block  902 . However, if a cycling type of workout was selected at block  902 , a biometric sensor for measuring heart rate and a GPS sensor for measuring position may be activated at block  902 , but an accelerometer may not be activated. This may be done because an accelerometer may not provide reliable information in determining distance traveled on a bike and can be left inactive to save power. Other combinations of activity sensors can selectively be activated for other types of workouts. 
     Referring back to  FIG.  9   , at block  906  one or more processors of the device can receive activity data that is representative of sensed physical activity of a user from an activity sensor. At block  908 , the one or more processors can process the received activity data to update values of attributes of the workout stored on the device. For example, a timer can be used to update the duration of the workout based on a difference between a current value of the timer and a value of the timer when the workout was initiated at block  904 . Additionally, an accelerometer, motion sensor, gyroscope, biometric sensor, and/or GPS sensor can be used to update a distance traveled during the workout and can additionally or alternatively be used to update a number of Calories burned during the workout (in combination with the user&#39;s age, gender, and weight). The timer can be used in combination with the accelerometer, motion sensor, and/or GPS sensor to update a pace of the user during the workout. Other activity sensors can similarly be used to determine and update values of other workout attributes. 
     At block  910 , one or more processors of the device can update the pro-view display (e.g., those shown in  FIGS.  13  and  14   ) to reflect the updated values of the workout metrics determined at block  908 . For example, with reference to  FIG.  14   , the first indicator  1310  can be adjusted to reflect the total distance traveled, second indicator  1312  can be moved to reflect the updated pace value, and third indicator  1314  can be updated to reflect the updated value of Calories burned, fourth indicator  1416  can be updated to reflect the updated value of the time elapsed, and fifth indicator  1418  can be update to reflect the updated value of the heart rate. 
     Blocks  906 ,  908 , and  910  can continue to be repeated to provide the user with up to date information associated with the workout metrics of the workout type via the pro-view display. In some examples where the workout application is running in the background of the device or while the display of the device is deactivated, block  910  can be omitted and blocks  906  and  908  can repeatedly be performed to monitor the user&#39;s workout and update the monitored workout metrics such that an accurate display of the metrics can later be provided to the user when the physical activity application is reopened or the display of the device is activated. In some examples, upon activating the display of the device, the workout interface previously displayed (e.g., one of the interfaces displayed in  FIGS.  13  and  14   ) before deactivating the display can be displayed. This workout interface can be displayed while the device is in a locked state or can be displayed in response to unlocking the device. 
     In block  912 , one or more processors of the device can cause the pro-view display to continue to be displayed. Alternatively, something may trigger a simple-view display to be displayed. For example, a gesture, such as a horizontal swipe, may be detected that causes a transition from the pro-view display to the simple-view display. Other user input could also cause the transition from the pro-view display to the simple-view display. 
     In block  914 , the simply-view display is displayed on the display of the device. The simple-view display includes an indicator for less than all of the workout metrics associated with the selected workout type of block  902 . For example,  FIG.  15    depicts interface  1500 , which is an example of a simple view. Interface  1500  includes a focus indicator  1510  for the workout metric that was focused in the pro-view display. In the case of interface  1500 , the pro-view display (i.e., interface  1400  of  FIG.  14   ) was focusing the pace workout metric. Accordingly, focused workout metric  1512  is the pace workout metric and focused indicator  1510  represents a value of the pace. Interface  1500  does not include an indicator representative of the other workout metrics included in the pro-view display. For example, neither progress indicator  1506  nor goal indicator  1508  represent any of the workout metrics represented in the pro-view display. In other examples, however, progress indicator  1506  and goal indicator  1508  may be related to one of the workout metrics of the pro-view display. 
     Referring back to  FIG.  9   , at block  916  one or more processors of the device can receive activity data that is representative of sensed physical activity of a user from an activity sensor. At block  918 , the one or more processors can process the received activity data to update values of workout metrics of the workout stored on the device. For example, a timer can be used to update the duration of the workout based on a difference between a current value of the timer and a value of the timer when the workout was initiated at block  904 . Additionally, an accelerometer, motion sensor, gyroscope, biometric sensor, and/or GPS sensor can be used to update a distance traveled during the workout and can additionally or alternatively be used to update a number of Calories burned during the workout (in combination with the user&#39;s age, gender, and weight). The timer can be used in combination with the accelerometer, motion sensor, and/or GPS sensor to update a pace of the user during the workout. Other activity sensors can similarly be used to determine and update values of other workout attributes. 
     At block  920 , one or more processors of the device can update the simple-view display (e.g., those shown in  FIGS.  15 ,  16 ,  19  and  20   ) to reflect the updated values of the workout metrics determined at block  918 . For example, with reference to  FIG.  15   , the focused indicator  1510  can be adjusted to reflect an updated value for the pace. 
     Blocks  916 ,  918 , and  920  can continue to be repeated to provide the user with up to date information associated with the attributes of the workout via the workout interface. In some examples where the workout application is running in the background of the device or while the display of the device is deactivated, block  920  can be omitted and blocks  916  and  918  can repeatedly be performed to monitor the user&#39;s workout and update the monitored attributes such that an accurate display of the attributes can later be provided to the user when the physical activity application is reopened or the display of the device is activated. In some examples, upon activating the display of the device, the workout interface previously displayed (e.g., one of the interfaces displayed in  FIGS.  15 ,  16 ,  19 , and  20   ) before deactivating the display can be displayed. This workout interface can be displayed while the device is in a locked state or can be displayed in response to unlocking the device. 
     In block  922 , one or more processors of the device can cause the simple-view display to continue to be displayed. Alternatively, something may trigger the pro-view to be displayed. For example, a gesture, such as a horizontal swipe, may be detected that causes a transition from the simple-view display to the pro-view display. Other user input could also cause the transition from the pro-view display to the simple-view display. 
     In the case of the simple-view display in  FIG.  15   , a transition back to the pro-view would cause the pro-view display of interface  1400  ( FIG.  14   ) to be displayed. The focus of the pace workout metric, as shown by focused indicator  1510  and focused workout metric  1512 , is carried over to the pro-view as indicated by focus indicator  1420  of interface  1400  ( FIG.  14   ). 
     When simple-view is displayed, focused workout metric  1512  and its representative focused indicator  1510  may be changed. For example, by receiving a user input, such as a gesture on a touch-sensitive screen or other user input on a rotatable crown or button, focused workout metric may be changed to the distance workout metric, which is depicted in simple-view display in interface  1600  of  FIG.  16   . In interface  1600 , focused workout metric  1612  is the distance workout metric and focused indicator  1610  represents a value for focused workout metric  1612 . 
     If the focused workout metric of the simple-view display changes, as is the case with the change from interface  1500  of  FIG.  15    to interface  1600  of  FIG.  16   , the focused indicator will change with a transition back to the pro-view as described above with respect to block  922 . For example, the result of a transition of the simple-view display of interface  1600  of  FIG.  16    back to a pro-view display is represented in interface  1700  of  FIG.  17   , which shows a pro-view display with focus indicator  1720  now highlighting first indicator  1710  representing the distance workout metric. 
     The transition from the pro-view back to the simple view operates in a similar manner. For example, if the focus indicator changes from the first indicator (e.g., first indicator  1710  in interface  1700  of  FIG.  17   ) to the fourth indicator (e.g., fourth indicator  1816  of interface  1800  of  FIG.  18   ), then the result of a transition from the pro-view display to the simple-view display is shown in the simple-view display of interface  1900  of  FIG.  19   , which depicts focused workout metric  1912  being the elapsed time workout metric that is represented by focused indicator  1910 . 
     The simple-view display of interface  2000  of  FIG.  20    depicts another change in the focused workout metric as compared to the simple-view display in interface  1700  of  FIG.  17   . Focus workout metric  2012  is now the Calories workout metric, which is represented by focused indicator  2010 . The result of a transition back to the pro-view display is depicted by the pro-view display of interface  2100  of  FIG.  21   . In interface  2100 , focus indicator  2120  is now on third indicator  2114 , which represents the Calories workout metric. 
     The transitions between pro-views and simple-views may use animations. For example, the focused workout metric of the pro-view display may be animated to move into position in the simple-view display. Similar animations can also be used for the transitions between simple-views and pro-views. 
     User input, such as gestures, can also be used to transition to other displays, such as a workout control or a music control. For example,  FIG.  22    depicts interface  2200  for controlling workout  2202  having control buttons that include, stop button  2204  and pause button  2206 . Activation of stop button  2204  ends the workout. Activation of pause button  2206 , pauses the workout (for example, pauses the collection or recording of activity data) and displays a paused workout control, as depicted in interface  2300  of  FIG.  23   , which includes stop button  2204  and resume button  2302  that resumes the workout.  FIG.  24    depicts an example music control in interface  2400  for controlling music  2402  with skip button  2404  for skipping the current music and pause button  2406  for pausing the music. 
     While process  900  ( FIG.  9   ) is illustrated as starting with the pro-view, other embodiments of process  900  may start with the simple-view. In some cases, the initial view that is displayed may be user configurable or based on last view used during the last workout. 
       FIG.  25    shows a functional block diagram of an electronic device  25  configured in accordance with the principles of the various described examples. The functional blocks of the device can be implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG.  25    can be combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG.  25   , electronic device  2500  can include a touch-sensitive display unit  2504  configured to display graphical objects and receive user gestures, activity sensor units  2506  configured to detect movement associated with the electronic device, and a processing unit  2502 . In some examples, processing unit  2502  can include an identifying unit  2508 , a movement detecting unit  2510 , a generating unit  2512 , a determining unit  2514 , a gesture detecting unit  2516 , and a displaying unit  2518 . 
     Processing unit  2502  can be configured to detect (e.g., using identifying unit  2508 ) an identification of a type of workout to be performed. The type of workout is associated with a plurality of workout metrics, including a first workout metric and a second workout metric. Movement detecting unit  2510  can be configured to detect movement associated with an electronic device using activity sensor units  2506 . Generation unit  2512  can be configured to generate activity data based on the detected movement from movement detecting unit  2510 . Determining unit  2514  can be configured to determine a current value of the first workout metric and a current value of a second workout metric based on the activity data. Gesture detecting unit  2516  can be configured to detect a first user gesture corresponding to a request to display workout metric data. Displaying unit  2518  can be configured to, in response to gesture detecting unit  2516 , cause, on the touch-sensitive display unit  2504  a first display. The first display can include a plurality of indicators representative of the plurality of workout metrics, including a first indicator representative of the first workout metric and a second indicator representative of the second workout metric. The first display also can include a focus indicator for one of the plurality of indicators, wherein the focus indicator indicates a focused workout metric. The gesture detecting unit  25  can be further configured to detect, while the first displaying is being displayed, a second user gesture corresponding to a request to transition between the first display and a second display. Displaying unit  2518  can be further configured to, in response to the second user gesture being detected while the first display is being displayed, cause, on the touch-sensitive display unit a first transition to the second display. The second display can include an indicator representative of the focused workout metric. Not all of the plurality of workout metrics is represented in the second display. Gesture detecting unit  2516  can be further configured to, while the second display is being displayed, detect a third user gesture corresponding to a request to transition between the second display and the first display. Displaying unit  2518  can be further configured to, in response to the third user gesture being detected while the second display is being displayed, cause, on the touch-sensitive display unit a second transition to the first display. 
     In some examples, the plurality workout metrics that are associated with the type of workout are configurable. 
     In some examples, the plurality of workout metrics includes a third workout metric and a fourth workout metric, and the plurality of indicators representative of the plurality of workout metrics further includes a third indicator representative of a third workout metric associated with the type of workout and a fourth indicator representative of a fourth workout metric associated with the type of workout. The plurality of workout metrics include at least four workout metrics selected from: a workout metric related to calories, a workout metric related to heart rate, a workout metric related to speed, a workout metric related to distance traveled, and a workout metric related to time. In some examples, the plurality of indicators in the first display includes only four indicators representative of workout metrics. 
     In some examples, the first indicator has a position relative to the second indicator in the first display. Gesture detecting unit  2516  can be further configured to detect a fourth user gesture corresponding to a request to change the position of the first indicator relative to the second indicator in the first display. Processing unit  2502  can be further configured to have optional changing unit  2520 , which can be configured to, in response to the fourth user gesture being detected, change the position of the first indicator relative to the second indicator. 
     In some examples, the first indicator has a first color and the second indicator has a second color different than the first color. In some examples, the transition from the first display to the second display includes an animation. In some examples, gesture detecting unit  2516  can be further configured to detect a fifth user gesture corresponding to a request to transition from the first display or the second display to a third display. Displaying unit  2518  can be further configured to, in response to the fifth user gesture being detected while the first display or the second display is being displayed, cause on the touch-sensitive display unit the third display, including workout controls or music controls. 
     In some examples, gesture detecting unit  2516  can be configured to, while the first display is being displayed, detect a sixth user gesture corresponding to a request to move the focus indicator to a different indicator of the plurality of indicators on the first display. Displaying unit  2518  can be further configure to, in response to the sixth user gesture being detected, move the focus indicator to the different indicator on the first display. 
     In some examples, generation unit  2512  can be further configured to generate the activity data after gesture detecting unit  2516  detects the first user gesture corresponding to the request to display workout metrics. 
     As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the delivery to users of invitational content or any other content that may be of interest to them. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information. 
     The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. 
     The present disclosure further contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. For example, personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection should occur only after receiving the informed consent of the users. Additionally, such entities would take any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. 
     Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of advertisement delivery services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services. In another example, users can select not to provide location information for targeted content delivery services. In yet another example, users can select to not provide precise location information, but permit the transfer of location zone information. 
     Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content delivery services, or publically available information. 
     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 appended claims.

Metadata:
Filing Date: 20220822
Publication Date: 20240716
Grant Date: 20240716
Priority Date: 20160922
Inventors: CHEN, KEVIN WILL
BLAHNIK, JAY
BUTCHER, GARY IAN
FENNIS, Jules K.
GRAHAM, DAVID CHANCE
YANG, LAWRENCE Y.
Assignee: APPLE INC
CPC Classifications: [{"code": "G16H20/30", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B2225/50", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B2503/10", "inventive": false, "first": false, "tree": "[]"}, {"code": "A63B24/0062", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/6801", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/7435", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/1123", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B2503/10", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B5/6801", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/7435", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/1123", "inventive": false, "first": false, "tree": "[]"}, {"code": "G16H20/30", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/1118", "inventive": true, "first": true, "tree": "[]"}, {"code": "A61B5/1118", "inventive": true, "first": true, "tree": "[]"}, {"code": "A63B2225/50", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B2503/10", "inventive": false, "first": false, "tree": "[]"}, {"code": "A61B5/1123", "inventive": false, "first": false, "tree": "[]"}, {"code": "G16H20/30", "inventive": true, "first": false, "tree": "[]"}, {"code": "A63B24/0062", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/7435", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/6801", "inventive": true, "first": false, "tree": "[]"}, {"code": "A61B5/1118", "inventive": true, "first": true, "tree": "[]"}]
Family ID: 61617625