PATENT DOCUMENT

Publication Number: US-11960701-B2
Application Number: US-202016861651-A
Country: US
Kind Code: B2

Title: Using an illustration to show the passing of time

Abstract:
The present disclosure generally relates to providing electronic devices with faster, more efficient methods and context-specific user interfaces for indicating time. Such methods and interfaces optionally complement or replace other methods for indicating time. 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.

Claims:
What is claimed is: 
     
       1. An electronic device, comprising:
 a display device; 
 one or more processors; and 
 memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for:
 displaying, via the display device and at a first time of a day that is within a first hour of the day:
 an indication of time that indicates the first time of the day; and 
 a first user interface object, wherein the first user interface object has a first shape that indicates the first hour of the day; 
 
 displaying, via the display device and at a second time of the day, wherein the second time of the day is a time that is within a threshold time of an hour boundary between the first hour of the day and a second hour of the day:
 the indication of time, wherein the indication of time indicates the second time of the day; and 
 a first transitional user interface object that is a combination of the first user interface object and a second user interface object; 
 
 displaying, via the display device and at a third time of the day, wherein the third time of the day is within the second hour of the day:
 the indication of time, wherein the indication of time indicates the third time of the day; and 
 the second user interface object different from the first user interface object, wherein the second user interface object includes a second shape that indicates the second hour of the day; 
 
 displaying, via the display device and at a fourth time of the day, wherein the fourth time of the day is a time that is within the threshold time of an hour boundary between the second hour of the day and a third hour of the day:
 the indication of time, wherein the indication of time indicates the fourth time of the day; and 
 a second transitional user interface object that is a combination of the second user interface object and a third user interface object; and 
 
 displaying, via the display device and at a fifth time of the day, wherein the fifth time of the day is within the third hour of the day:
 the indication of time, wherein the indication of time indicates the fifth time of the day; and 
 the third user interface object different from the first user interface object and the second user interface object, wherein the third user interface object includes a third shape that indicates the third hour of the day. 
 
 
 
     
     
       2. The electronic device of  claim 1 , wherein the one or more programs further include instructions for:
 outputting, by the electronic device and at a sixth time of the day, wherein the sixth time of the day is within the first hour of the day, an alert; 
 after outputting the alert, receiving user input; and 
 in response to receiving the user input:
 in accordance with a determination that the user input is not received within a predefined duration of time after outputting the alert, displaying, via the display device, the indication of time without displaying the first transitional user interface object that is the combination of the first user interface object and the second user interface object. 
 
 
     
     
       3. The electronic device of  claim 1 , wherein the one or more programs further include instructions for:
 in accordance with a determination that the display device is in a non-active state, displaying, via the display device, the indication of time without displaying the first transitional user interface object that is the combination of the first user interface object and the second user interface object. 
 
     
     
       4. The electronic device of  claim 1 , wherein the one or more programs further include instructions for:
 transitioning from displaying the first user interface object to displaying the second user interface object, wherein the transitioning corresponds to the first user interface object turning into the second user interface object. 
 
     
     
       5. The electronic device of  claim 4 , wherein the transitioning is continual from the first time to the third time. 
     
     
       6. The electronic device of  claim 1 , wherein the first transitional user interface object that is the combination of the first user interface object and the second user interface object depicts the first user interface object interacting with the second user interface object. 
     
     
       7. The electronic device of  claim 1 , wherein displaying the first transitional user interface object that is the combination of the first user interface object and the second user interface object includes displaying an animation involving the first user interface object and the second user interface object. 
     
     
       8. The electronic device of  claim 1 , wherein the first transitional user interface object that is the combination of the first user interface object and the second user interface object includes a visual blend of the first shape of the first user interface object and the second shape of the second user interface object. 
     
     
       9. The electronic device of  claim 1 , wherein:
 the indication of time and the third user interface object are displayed at the fifth time of the day without displaying the first user interface object, the second user interface object, and a fourth user interface object, 
 the fourth user interface object has a fourth shape that indicates a fourth hour of the day, 
 the fourth user interface object is different from the first user interface object, the second user interface object, and the third user interface object, and 
 the one or more programs further include instructions for:
 displaying, via the display device and at a seventh time of the day:
 the indication of time, wherein the indication of time indicates the seventh time of the day; and 
 a third transitional user interface object that is a combination of the third user interface object and the fourth user interface object; 
 
 displaying, via the display device and at an eighth time of the day:
 the indication of time, wherein the indication of time indicates the eighth time of the day; and 
 the fourth user interface object. 
 
 
 
     
     
       10. The electronic device of  claim 1 , wherein:
 the indication of time that indicates the first time of the day and the first user interface object are displayed at the first time of the day without displaying the second user interface object and the third user interface object, 
 the second time of the day is after the first time of the day and is within the first hour of the day, 
 the second hour of the day does not include the first time of the day, 
 the third time of the day is after the second time of the day and is not within the first hour of the day, 
 the indication of time that indicates the third time of the day and the second user interface object are displayed at the third time of the day without displaying the first user interface object and the third user interface object, 
 the third hour of the day does not include the third time of the day, 
 the fourth time of the day is after the third time of the day and is within the second hour of the day, 
 the fifth time of the day is after the fourth time of the day, 
 the fifth time of the day is not within the first hour of the day and is not within the second hour of the day, and 
 the indication of time that indicates the fifth time of the day and the third user interface object are displayed at the fifth time of the day without displaying the first user interface object and without displaying the second user interface object. 
 
     
     
       11. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display device, the one or more programs including instructions for:
 displaying, via the display device and at a first time of a day that is within a first hour of the day:
 an indication of time that indicates the first time of the day; and 
 a first user interface object, wherein the first user interface object has a first shape that indicates the first hour of the day; 
 
 displaying, via the display device and at a second time of the day, wherein the second time of the day is a time that is within a threshold time of an hour boundary between the first hour of the day and a second hour of the day:
 the indication of time, wherein the indication of time indicates the second time of the day; and 
 a first transitional user interface object that is a combination of the first user interface object and a second user interface object; 
 
 displaying, via the display device and at a third time of the day, wherein the third time of the day is within the second hour of the day:
 the indication of time, wherein the indication of time indicates the third time of the day; and 
 the second user interface object different from the first user interface object, wherein the second user interface object includes a second shape that indicates the second hour of the day; 
 
 displaying, via the display device and at a fourth time of the day, wherein the fourth time of the day is a time that is within the threshold time of an hour boundary between the second hour of the day and a third hour of the day:
 the indication of time, wherein the indication of time indicates the fourth time of the day; and 
 a second transitional user interface object that is a combination of the second user interface object and a third user interface object; and 
 
 displaying, via the display device and at a fifth time of the day, wherein the fifth time of the day is within the third hour of the day:
 the indication of time, wherein the indication of time indicates the fifth time of the day; and 
 the third user interface object different from the first user interface object and the second user interface object, wherein the third user interface object includes a third shape that indicates the third hour of the day. 
 
 
     
     
       12. The non-transitory computer-readable storage medium of  claim 11 , wherein the one or more programs further include instructions for:
 outputting, by the electronic device and at a sixth time of the day, wherein the sixth time of the day is within the first hour of the day, an alert; 
 after outputting the alert, receiving user input; and 
 in response to receiving the user input:
 in accordance with a determination that the user input is not received within a predefined duration of time after outputting the alert, displaying, via the display device, the indication of time without displaying the first transitional user interface object that is the combination of the first user interface object and the second user interface object. 
 
 
     
     
       13. The non-transitory computer-readable storage medium of  claim 11 , wherein the one or more programs further include instructions for:
 in accordance with a determination that the display device is in a non-active state, displaying, via the display device, the indication of time without displaying the first transitional user interface object that is the combination of the first user interface object and the second user interface object. 
 
     
     
       14. The non-transitory computer-readable storage medium of  claim 11 , wherein the one or more programs further include instructions for:
 transitioning from displaying the first user interface object to displaying the second user interface object, wherein the transitioning corresponds to the first user interface object turning into the second user interface object. 
 
     
     
       15. The non-transitory computer-readable storage medium of  claim 14 , wherein the transitioning is continual from the first time to the third time. 
     
     
       16. The non-transitory computer-readable storage medium of  claim 11 , wherein the first transitional user interface object that is the combination of the first user interface object and the second user interface object depicts the first user interface object interacting with the second user interface object. 
     
     
       17. The non-transitory computer-readable storage medium of  claim 11 , wherein displaying the first transitional user interface object that is the combination of the first user interface object and the second user interface object includes displaying an animation involving the first user interface object and the second user interface object. 
     
     
       18. The non-transitory computer-readable storage medium of  claim 11 , wherein the first transitional user interface object that is the combination of the first user interface object and the second user interface object includes a visual blend of the first shape of the first user interface object and the second shape of the second user interface object. 
     
     
       19. The non-transitory computer-readable storage medium of  claim 11 , wherein:
 the indication of time and the third user interface object are displayed at the fifth time of the day without displaying the first user interface object, the second user interface object, and a fourth user interface object, 
 the fourth user interface object has a fourth shape that indicates a fourth hour of the day, 
 the fourth user interface object is different from the first user interface object, the second user interface object, and the third user interface object, and 
 the one or more programs further include instructions for:
 displaying, via the display device and at a seventh time of the day:
 the indication of time, wherein the indication of time indicates the seventh time of the day; and 
 a third transitional user interface object that is a combination of the third user interface object and the fourth user interface object; 
 
 displaying, via the display device and at an eighth time of the day:
 the indication of time, wherein the indication of time indicates the eighth time of the day; and 
 the fourth user interface object. 
 
 
 
     
     
       20. The non-transitory computer-readable storage medium of  claim 11 , wherein:
 the indication of time that indicates the first time of the day and the first user interface object are displayed at the first time of the day without displaying the second user interface object and the third user interface object, 
 the second time of the day is after the first time of the day and is within the first hour of the day, 
 the second hour of the day does not include the first time of the day, 
 the third time of the day is after the second time of the day and is not within the first hour of the day, 
 the indication of time that indicates the third time of the day and the second user interface object are displayed at the third time of the day without displaying the first user interface object and the third user interface object, 
 the third hour of the day does not include the third time of the day, 
 the fourth time of the day is after the third time of the day and is within the second hour of the day, 
 the fifth time of the day is after the fourth time of the day, 
 the fifth time of the day is not within the first hour of the day and is not within the second hour of the day, and 
 the indication of time that indicates the fifth time of the day and the third user interface object are displayed at the fifth time of the day without displaying the first user interface object and without displaying the second user interface object. 
 
     
     
       21. A method, comprising:
 at an electronic device with a display device, one or more processors, and memory:
 displaying, via the display device and at a first time of a day that is within a first hour of the day:
 an indication of time that indicates the first time of the day; and 
 a first user interface object, wherein the first user interface object has a first shape that indicates the first hour of the day; 
 
 displaying, via the display device and at a second time of the day, wherein the second time of the day is a time that is within a threshold time of an hour boundary between the first hour of the day and a second hour of the day:
 the indication of time, wherein the indication of time indicates the second time of the day; and 
 a first transitional user interface object that is a combination of the first user interface object and a second user interface object; 
 
 displaying, via the display device and at a third time of the day, wherein the third time of the day is within the second hour of the day:
 the indication of time, wherein the indication of time indicates the third time of the day; and 
 the second user interface object different from the first user interface object, wherein the second user interface object includes a second shape that indicates the second hour of the day; 
 
 displaying, via the display device and at a fourth time of the day, wherein the fourth time of the day is a time that is within the threshold time of an hour boundary between the second hour of the day and a third hour of the day:
 the indication of time, wherein the indication of time indicates the fourth time of the day; and 
 a second transitional user interface object that is a combination of the second user interface object and a third user interface object; and 
 
 displaying, via the display device and at a fifth time of the day, wherein the fifth time of the day is within the third hour of the day:
 the indication of time, wherein the indication of time indicates the fifth time of the day; and 
 the third user interface object different from the first user interface object and the second user interface object, wherein the third user interface object includes a third shape that indicates the third hour of the day. 
 
 
 
     
     
       22. The method of  claim 21 , further comprising:
 outputting, by the electronic device and at a sixth time of the day, wherein the sixth time of the day is within the first hour of the day, an alert; 
 after outputting the alert, receiving user input; and 
 in response to receiving the user input:
 in accordance with a determination that the user input is not received within a predefined duration of time after outputting the alert, displaying, via the display device, the indication of time without displaying the first transitional user interface object that is the combination of the first user interface object and the second user interface object. 
 
 
     
     
       23. The method of  claim 21 , further comprising:
 in accordance with a determination that the display device is in a non-active state, displaying, via the display device, the indication of time without displaying the first transitional user interface object that is the combination of the first user interface object and the second user interface object. 
 
     
     
       24. The method of  claim 21 , further comprising:
 transitioning from displaying the first user interface object to displaying the second user interface object, wherein the transitioning corresponds to the first user interface object turning into the second user interface object. 
 
     
     
       25. The method of  claim 24 , wherein the transitioning is continual from the first time to the third time. 
     
     
       26. The method of  claim 21 , wherein the first transitional user interface object that is the combination of the first user interface object and the second user interface object depicts the first user interface object interacting with the second user interface object. 
     
     
       27. The method of  claim 21 , wherein displaying the first transitional user interface object that is the combination of the first user interface object and the second user interface object includes displaying an animation involving the first user interface object and the second user interface object. 
     
     
       28. The method of  claim 21 , wherein the first transitional user interface object that is the combination of the first user interface object and the second user interface object includes a visual blend of the first shape of the first user interface object and the second shape of the second user interface object. 
     
     
       29. The method of  claim 21 , wherein:
 the indication of time and the third user interface object are displayed at the fifth time of the day without displaying the first user interface object, the second user interface object, and a fourth user interface object, 
 the fourth user interface object has a fourth shape that indicates a fourth hour of the day, 
 the fourth user interface object is different from the first user interface object, the second user interface object, and the third user interface object, and 
 the method further comprises:
 displaying, via the display device and at a seventh time of the day:
 the indication of time, wherein the indication of time indicates the seventh time of the day; and 
 a third transitional user interface object that is a combination of the third user interface object and the fourth user interface object; 
 
 displaying, via the display device and at an eighth time of the day:
 the indication of time, wherein the indication of time indicates the eighth time of the day; and 
 the fourth user interface object. 
 
 
 
     
     
       30. The method of  claim 21 , wherein
 the indication of time that indicates the first time of the day and the first user interface object are displayed at the first time of the day without displaying the second user interface object and the third user interface object, 
 the second time of the day is after the first time of the day and is within the first hour of the day, 
 the second hour of the day does not include the first time of the day, 
 the third time of the day is after the second time of the day and is not within the first hour of the day, 
 the indication of time that indicates the third time of the day and the second user interface object are displayed at the third time of the day without displaying the first user interface object and the third user interface object, 
 the third hour of the day does not include the third time of the day, 
 the fourth time of the day is after the third time of the day and is within the second hour of the day, 
 the fifth time of the day is after the fourth time of the day, 
 the fifth time of the day is not within the first hour of the day and is not within the second hour of the day, and 
 the indication of time that indicates the fifth time of the day and the third user interface object are displayed at the fifth time of the day without displaying the first user interface object and without displaying the second user interface object.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application claims priority to U.S. Provisional Patent Application No. 62/843,723, entitled “USING AN ILLUSTRATION TO SHOW THE PASSING OF TIME,” filed on May 6, 2019, the contents of which is hereby incorporated by reference in its entirety. 
    
    
     FIELD 
     The present disclosure relates generally to computer user interfaces, and more specifically to techniques for indicating time on context-specific user interfaces. 
     BACKGROUND 
     Users rely on portable multifunction devices for a variety of operations, including keeping time and running an assortment of software applications that enhance device functionality. A user may also want to access different types of information, such as various forms of timekeeping-related data, or different application data, in different contexts. 
     BRIEF SUMMARY 
     Some techniques for indicating time on context-specific user interfaces using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface. It is therefore desirable to allow the user to access time-related and application-related information while keeping the interface simple and intuitive to use. Other existing techniques rely on the ability of a user to decipher textual, numerical, or radial markings, and to determine the position of multiple graphical elements relative to such markings. Furthermore, existing techniques require large amounts of display area to the exclusion of other graphical content, an acute concern for electronic devices with reduced-sized displays. It is therefore also desirable to allow the user to customize the user interface and the types of information provided through the user interface in a manner that provides improved visual feedback regarding the state of portable multifunctional device relative to time-keeping and application driven operations. Existing techniques may be prone to error or require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices. 
     Accordingly, the present techniques provide electronic devices with faster, more efficient methods and context-specific user interfaces for indicating time. Such methods and interfaces optionally complement or replace other methods for indicating time. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges. 
     In some embodiments, a method comprises, at an electronic device with a display device: at a first time, displaying, via the display device, a first user interface object without displaying a second user interface object, where the second user interface object is different from the first user interface object, and where the first user interface object represents a first period of time that includes the first time; at a second time after the first time and within the first period of time, displaying, via the display device, a combination of the first user interface object and the second user interface object; and at a third time after the second time, displaying, via the display device, the second user interface object without displaying the first user interface object, where the second user interface object represents a second period of time that includes the third time. 
     In some embodiments, a method comprises, at an electronic device with a display device: displaying a clock face via the display device; at a first time, displaying, via the display device, a user interface object at a first location of the clock face, where the user interface object has a first appearance at the first time; at a second time different from the first time, displaying, via the display device, the user interface object at a second location of the clock face, where the user interface object has the first appearance at the second time, and where a difference between the first time and the second time is at least one unit according to a first time scale; and at a third time different from each of the second time and the first time, displaying, via the display device, the user interface object at the first location of the clock face, where the user interface object has a second appearance at the third time, where a difference between the first time and the third time is at least one unit according to a second time scale different from the first time scale. 
     In some embodiments, a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display device, the one or more programs including instructions for: at a first time, displaying, via the display device, a first user interface object without displaying a second user interface object, where the second user interface object is different from the first user interface object, and where the first user interface object represents a first period of time that includes the first time; at a second time after the first time and within the first period of time, displaying, via the display device, a combination of the first user interface object and the second user interface object; and at a third time after the second time, displaying, via the display device, the second user interface object without displaying the first user interface object, where the second user interface object represents a second period of time that includes the third time. 
     In some embodiments, a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display device, the one or more programs including instructions for: at a first time, displaying, via the display device, a user interface object at a first location of the clock face, where the user interface object has a first appearance at the first time; at a second time different from the first time, displaying, via the display device, the user interface object at a second location of the clock face, where the user interface object has the first appearance at the second time, and where a difference between the first time and the second time is at least one unit according to a first time scale; and at a third time different from each of the second time and the first time, displaying, via the display device, the user interface object at the first location of the clock face, where the user interface object has a second appearance at the third time, where a difference between the first time and the third time is at least one unit according to a second time scale different from the first time scale. 
     In some embodiments, a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display device, the one or more programs including instructions for: at a first time, displaying, via the display device, a first user interface object without displaying a second user interface object, where the second user interface object is different from the first user interface object, and where the first user interface object represents a first period of time that includes the first time; at a second time after the first time and within the first period of time, displaying, via the display device, a combination of the first user interface object and the second user interface object; and at a third time after the second time, displaying, via the display device, the second user interface object without displaying the first user interface object, where the second user interface object represents a second period of time that includes the third time. 
     In some embodiments, a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display device, the one or more programs including instructions for: at a first time, displaying, via the display device, a user interface object at a first location of the clock face, where the user interface object has a first appearance at the first time; at a second time different from the first time, displaying, via the display device, the user interface object at a second location of the clock face, where the user interface object has the first appearance at the second time, and where a difference between the first time and the second time is at least one unit according to a first time scale; and at a third time different from each of the second time and the first time, displaying, via the display device, the user interface object at the first location of the clock face, where the user interface object has a second appearance at the third time, where a difference between the first time and the third time is at least one unit according to a second time scale different from the first time scale. 
     In some embodiments, an electronic device comprising a display device; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: at a first time, displaying, via the display device, a first user interface object without displaying a second user interface object, where the second user interface object is different from the first user interface object, and where the first user interface object represents a first period of time that includes the first time; at a second time after the first time and within the first period of time, displaying, via the display device, a combination of the first user interface object and the second user interface object; and at a third time after the second time, displaying, via the display device, the second user interface object without displaying the first user interface object, where the second user interface object represents a second period of time that includes the third time. 
     In some embodiments, an electronic device comprising a display device; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: at a first time, displaying, via the display device, a user interface object at a first location of the clock face, where the user interface object has a first appearance at the first time; at a second time different from the first time, displaying, via the display device, the user interface object at a second location of the clock face, where the user interface object has the first appearance at the second time, and where a difference between the first time and the second time is at least one unit according to a first time scale; and at a third time different from each of the second time and the first time, displaying, via the display device, the user interface object at the first location of the clock face, where the user interface object has a second appearance at the third time, where a difference between the first time and the third time is at least one unit according to a second time scale different from the first time scale. 
     In some embodiments, an electronic device comprising a display device; means for displaying at a first time, via the display device, a first user interface object without displaying a second user interface object, where the second user interface object is different from the first user interface object, and where the first user interface object represents a first period of time that includes the first time; means for displaying at a second time after the first time and within the first period of time, via the display device, a combination of the first user interface object and the second user interface object; and means for displaying at a third time after the second time, via the display device, the second user interface object without displaying the first user interface object, where the second user interface object represents a second period of time that includes the third time. 
     In some embodiments, an electronic device comprising a display device; means for displaying at a first time, via the display device, a user interface object at a first location of the clock face, where the user interface object has a first appearance at the first time; means for displaying at a second time different from the first time, via the display device, the user interface object at a second location of the clock face, where the user interface object has the first appearance at the second time, and where a difference between the first time and the second time is at least one unit according to a first time scale; and means for displaying at a third time different from each of the second time and the first time, via the display device, the user interface object at the first location of the clock face, where the user interface object has a second appearance at the third time, where a difference between the first time and the third time is at least one unit according to a second time scale different from the first time scale. 
     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 indicating time, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for in. 
    
    
     
       DESCRIPTION OF THE FIGURES 
       For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures. 
         FIG.  1 A  is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments. 
         FIG.  1 B  is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. 
         FIG.  2    illustrates a portable multifunction device having a touch screen in accordance with some embodiments. 
         FIG.  3    is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. 
         FIG.  4 A  illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments. 
         FIG.  4 B  illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments. 
         FIG.  5 A  illustrates a personal electronic device in accordance with some embodiments. 
         FIG.  5 B  is a block diagram illustrating a personal electronic device in accordance with some embodiments. 
         FIGS.  6 A- 6 E  illustrate context-specific user interfaces in accordance with some embodiments. 
         FIGS.  7 A- 7 D  illustrate context-specific user interfaces in accordance with some embodiments. 
         FIGS.  8 A- 8 B  illustrate a flow diagram depicting a process for providing context-specific user interfaces in accordance with some embodiments. 
         FIGS.  9 A- 9 E  illustrate context-specific user interfaces in accordance with some embodiments. 
         FIGS.  10 A- 10 G  illustrate context-specific user interfaces in accordance with some embodiments. 
         FIGS.  11 A- 11 D  illustrate context-specific user interfaces in accordance with some embodiments. 
         FIGS.  12 A- 12 C  illustrate a flow diagram depicting a process for providing context-specific user interfaces in accordance with some embodiments. 
     
    
    
     DESCRIPTION OF EMBODIMENTS 
     The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments. 
     There is a need for electronic devices that provide efficient methods and context-specific user interfaces, e.g., that display time along with additional information. This is particularly true for portable multifunction devices with reduced-sized displays. Providing context-specific user interfaces that include alternative modalities through which to convey information reduces the cognitive burden on a user attempting to access information and/or keep time, thereby enhancing user satisfaction, productivity, usability, and accessibility. Such interfaces provides more efficient use of limited screen “real estate,” which in turn reduces the number of user interactions required to access relevant data at any time of day. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs. 
     Below,  FIGS.  1 A- 1 B,  2 ,  3 ,  4 A- 4 B, and  5 A- 5 B  provide a description of exemplary devices for performing techniques for indicating time.  FIGS.  6 A- 6 E and  7 A- 7 D  illustrate exemplary user interfaces for indicating time.  FIGS.  8 A- 8 B  are flow diagrams illustrating methods of indicating time on a context-specific user interface in accordance with some embodiments. The user interfaces in  FIGS.  6 A- 6 E and  7 A- 7 D  are used to illustrate the processes described below, including the processes in  FIGS.  8 A- 8 B .  FIGS.  9 A- 9 E,  10 A- 10 G, and  11 A- 11 D  illustrate exemplary user interfaces for indicating time.  FIGS.  12 A- 12 C  are flow diagrams illustrating methods of indicating time on a context-specific user interface in accordance with some embodiments. The user interfaces in  FIGS.  9 A- 9 E,  10 A- 10 G, and  11 A- 11 D  are used to illustrate the processes described below, including the processes in  FIGS.  12 A- 12 C . 
     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 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 , depth camera controller  169 , intensity sensor controller  159 , haptic feedback controller  161 , and one or more input controllers  160  for other input or control devices. The one or more input controllers  160  receive/send electrical signals from/to other input control devices  116 . The other input control devices  116  optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s)  160  are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g.,  208 ,  FIG.  2   ) optionally include an up/down button for volume control of speaker  111  and/or microphone  113 . The one or more buttons optionally include a push button (e.g.,  206 ,  FIG.  2   ). 
     A quick press of the push button optionally disengages a lock of touch screen  112  or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g.,  206 ) optionally turns power to device  100  on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen  112  is used to implement virtual or soft buttons and one or more soft keyboards. 
     Touch-sensitive display  112  provides an input interface and an output interface between the device and a user. Display controller  156  receives and/or sends electrical signals from/to touch screen  112 . Touch screen  112  displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects. 
     Touch screen  112  has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen  112  and display controller  156  (along with any associated modules and/or sets of instructions in memory  102 ) detect contact (and any movement or breaking of the contact) on touch screen  112  and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen  112 . In an exemplary embodiment, a point of contact between touch screen  112  and the user corresponds to a finger of the user. 
     Touch screen  112  optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen  112  and display controller  156  optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen  112 . In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California. 
     A touch-sensitive display in some embodiments of touch screen  112  is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen  112  displays visual output from device  100 , whereas touch-sensitive touchpads do not provide visual output. 
     A touch-sensitive display in some embodiments of touch screen  112  is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety. 
     Touch screen  112  optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen  112  using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user. 
     In some embodiments, in addition to the touch screen, device  100  optionally includes a touchpad for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen  112  or an extension of the touch-sensitive surface formed by the touch screen. 
     Device  100  also includes power system  162  for powering the various components. Power system  162  optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices. 
     Device  100  optionally also includes one or more optical sensors  164 .  FIG.  1 A  shows an optical sensor coupled to optical sensor controller  158  in I/O subsystem  106 . Optical sensor  164  optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor  164  receives light from the environment, projected through one or more lenses, and converts the light to data representing an image. In conjunction with imaging module  143  (also called a camera module), optical sensor  164  optionally captures still images or video. In some embodiments, an optical sensor is located on the back of device  100 , opposite touch screen display  112  on the front of the device so that the touch screen display is enabled for use as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user&#39;s image is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of optical sensor  164  can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor  164  is used along with the touch screen display for both video conferencing and still and/or video image acquisition. 
     Device  100  optionally also includes one or more depth camera sensors  175 .  FIG.  1 A  shows a depth camera sensor coupled to depth camera controller  169  in I/O subsystem  106 . Depth camera sensor  175  receives data from the environment to create a three dimensional model of an object (e.g., a face) within a scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with imaging module  143  (also called a camera module), depth camera sensor  175  is optionally used to determine a depth map of different portions of an image captured by the imaging module  143 . In some embodiments, a depth camera sensor is located on the front of device  100  so that the user&#39;s image with depth information is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display and to capture selfies with depth map data. In some embodiments, the depth camera sensor  175  is located on the back of device, or on the back and the front of the device  100 . In some embodiments, the position of depth camera sensor  175  can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a depth camera sensor  175  is used along with the touch screen display for both video conferencing and still and/or video image acquisition. 
     Device  100  optionally also includes one or more contact intensity sensors  165 .  FIG.  1 A  shows a contact intensity sensor coupled to intensity sensor controller  159  in I/O subsystem  106 . Contact intensity sensor  165  optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor  165  receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system  112 ). In some embodiments, at least one contact intensity sensor is located on the back of device  100 , opposite touch screen display  112 , which is located on the front of device  100 . 
     Device  100  optionally also includes one or more proximity sensors  166 .  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 and a GPS (or GLONASS or other global navigation system) receiver for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device  100 . 
     In some embodiments, the software components stored in memory  102  include operating system  126 , communication module (or set of instructions)  128 , contact/motion module (or set of instructions)  130 , graphics module (or set of instructions)  132 , text input module (or set of instructions)  134 , Global Positioning System (GPS) module (or set of instructions)  135 , and applications (or sets of instructions)  136 . Furthermore, in some embodiments, memory  102  ( FIG.  1 A ) or  370  ( FIG.  3   ) stores device/global internal state  157 , as shown in  FIGS.  1 A and  3   . Device/global internal state  157  includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display  112 ; sensor state, including information obtained from the device&#39;s various sensors and input control devices  116 ; and location information concerning the device&#39;s location and/or attitude. 
     Operating system  126  (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components. 
     Communication module  128  facilitates communication with other devices over one or more external ports  124  and also includes various software components for handling data received by RF circuitry  108  and/or external port  124 . External port  124  (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices. 
     Contact/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 or a higher level object from which application  136 - 1  inherits methods and other properties. In some embodiments, a respective event handler  190  includes one or more of: data updater  176 , object updater  177 , GUI updater  178 , and/or event data  179  received from event sorter  170 . Event handler  190  optionally utilizes or calls data updater  176 , object updater  177 , or GUI updater  178  to update the application internal state  192 . Alternatively, one or more of the application views  191  include one or more respective event handlers  190 . Also, in some embodiments, one or more of data updater  176 , object updater  177 , and GUI updater  178  are included in a respective application view  191 . 
     A respective event recognizer  180  receives event information (e.g., event data  179 ) from event sorter  170  and identifies an event from the event information. Event recognizer  180  includes event receiver  182  and event comparator  184 . In some embodiments, event recognizer  180  also includes at least a subset of: metadata  183 , and event delivery instructions  188  (which optionally include sub-event delivery instructions). 
     Event receiver  182  receives event information from event sorter  170 . The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device. 
     Event comparator  184  compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator  184  includes event definitions  186 . Event definitions  186  contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 ( 187 - 1 ), event 2 ( 187 - 2 ), and others. In some embodiments, sub-events in an event ( 187 ) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 ( 187 - 1 ) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 ( 187 - 2 ) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display  112 , and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers  190 . 
     In some embodiments, event definition  187  includes a definition of an event for a respective user-interface object. In some embodiments, event comparator  184  performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display  112 , when a touch is detected on touch-sensitive display  112 , event comparator  184  performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler  190 , the event comparator uses the result of the hit test to determine which event handler  190  should be activated. For example, event comparator  184  selects an event handler associated with the sub-event and the object triggering the hit test. 
     In some embodiments, the definition for a respective event ( 187 ) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer&#39;s event type. 
     When a respective event recognizer  180  determines that the series of sub-events do not match any of the events in event definitions  186 , the respective event recognizer  180  enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture. 
     In some embodiments, a respective event recognizer  180  includes metadata  183  with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata  183  includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata  183  includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy. 
     In some embodiments, a respective event recognizer  180  activates event handler  190  associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer  180  delivers event information associated with the event to event handler  190 . Activating an event handler  190  is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer  180  throws a flag associated with the recognized event, and event handler  190  associated with the flag catches the flag and performs a predefined process. 
     In some embodiments, event delivery instructions  188  include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process. 
     In some embodiments, data updater  176  creates and updates data used in application  136 - 1 . For example, data updater  176  updates the telephone number used in contacts module  137 , or stores a video file used in video player module. In some embodiments, object updater  177  creates and updates objects used in application  136 - 1 . For example, object updater  177  creates a new user-interface object or updates the position of a user-interface object. GUI updater  178  updates the GUI. For example, GUI updater  178  prepares display information and sends it to graphics module  132  for display on a touch-sensitive display. 
     In some embodiments, event handler(s)  190  includes or has access to data updater  176 , object updater  177 , and GUI updater  178 . In some embodiments, data updater  176 , object updater  177 , and GUI updater  178  are included in a single module of a respective application  136 - 1  or application view  191 . In other embodiments, they are included in two or more software modules. 
     It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices  100  with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized. 
       FIG.  2    illustrates a portable multifunction device  100  having a touch screen  112  in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI)  200 . In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers  202  (not drawn to scale in the figure) or one or more styluses  203  (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device  100 . In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap. 
     Device  100  optionally also include one or more physical buttons, such as “home” or menu button  204 . As described previously, menu button  204  is, optionally, used to navigate to any application  136  in a set of applications that are, optionally, executed on device  100 . Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen  112 . 
     In some embodiments, device  100  includes touch screen  112 , menu button  204 , push button  206  for powering the device on/off and locking the device, volume adjustment button(s)  208 , subscriber identity module (SIM) card slot  210 , headset jack  212 , and docking/charging external port  124 . Push button  206  is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device  100  also accepts verbal input for activation or deactivation of some functions through microphone  113 . Device  100  also, optionally, includes one or more contact intensity sensors  165  for detecting intensity of contacts on touch screen  112  and/or one or more tactile output generators  167  for generating tactile outputs for a user of device  100 . 
       FIG.  3    is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device  300  need not be portable. In some embodiments, device  300  is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child&#39;s learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device  300  typically includes one or more processing units (CPUs)  310 , one or more network or other communications interfaces  360 , memory  370 , and one or more communication buses  320  for interconnecting these components. Communication buses  320  optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device  300  includes input/output (I/O) interface  330  comprising display  340 , which is typically a touch screen display. I/O interface  330  also optionally includes a keyboard and/or mouse (or other pointing device)  350  and touchpad  355 , tactile output generator  357  for generating tactile outputs on device  300  (e.g., similar to tactile output generator(s)  167  described above with reference to  FIG.  1 A ), sensors  359  (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s)  165  described above with reference to  FIG.  1 A ). Memory  370  includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory  370  optionally includes one or more storage devices remotely located from CPU(s)  310 . In some embodiments, memory  370  stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory  102  of portable multifunction device  100  ( FIG.  1 A ), or a subset thereof. Furthermore, memory  370  optionally stores additional programs, modules, and data structures not present in memory  102  of portable multifunction device  100 . For example, memory  370  of device  300  optionally stores drawing module  380 , presentation module  382 , word processing module  384 , website creation module  386 , disk authoring module  388 , and/or spreadsheet module  390 , while memory  102  of portable multifunction device  100  ( FIG.  1 A ) optionally does not store these modules. 
     Each of the above-identified elements in  FIG.  3    is, optionally, stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The above-identified modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. In some embodiments, memory  370  optionally stores a subset of the modules and data structures identified above. Furthermore, memory  370  optionally stores additional modules and data structures not described above. 
     Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device  100 . 
       FIG.  4 A  illustrates an exemplary user interface for a menu of applications on portable multifunction device  100  in accordance with some embodiments. Similar user interfaces are, optionally, implemented on device  300 . In some embodiments, user interface  400  includes the following elements, or a subset or superset thereof:
         Signal strength indicator(s)  402  for wireless communication(s), such as cellular and Wi-Fi signals;   Time  404 ;   Bluetooth indicator  405 ;   Battery status indicator  406 ;   Tray  408  with icons for frequently used applications, such as:
           Icon  416  for telephone module  138 , labeled “Phone,” which optionally includes an indicator  414  of the number of missed calls or voicemail messages;   Icon  418  for e-mail client module  140 , labeled “Mail,” which optionally includes an indicator  410  of the number of unread e-mails;   Icon  420  for browser module  147 , labeled “Browser;” and   Icon  422  for video and music player module  152 , also referred to as iPod (trademark of Apple Inc.) module  152 , labeled “iPod;” and   
           Icons for other applications, such as:
           Icon  424  for IM module  141 , labeled “Messages;”   Icon  426  for calendar module  148 , labeled “Calendar;”   Icon  428  for image management module  144 , labeled “Photos;”   Icon  430  for camera module  143 , labeled “Camera;”   Icon  432  for online video module  155 , labeled “Online Video;”   Icon  434  for stocks widget  149 - 2 , labeled “Stocks;”   Icon  436  for map module  154 , labeled “Maps;”   Icon  438  for weather widget  149 - 1 , labeled “Weather;”   Icon  440  for alarm clock widget  149 - 4 , labeled “Clock;”   Icon  442  for workout support module  142 , labeled “Workout Support;”   Icon  444  for notes module  153 , labeled “Notes;” and   Icon  446  for a settings application or module, labeled “Settings,” which provides access to settings for device  100  and its various applications  136 .   
               

     It should be noted that the icon labels illustrated in  FIG.  4 A  are merely exemplary. For example, icon  422  for video and music player module  152  is labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon. 
       FIG.  4 B  illustrates an exemplary user interface on a device (e.g., device  300 ,  FIG.  3   ) with a touch-sensitive surface  451  (e.g., a tablet or touchpad  355 ,  FIG.  3   ) that is separate from the display  450  (e.g., touch screen display  112 ). Device  300  also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors  359 ) for detecting intensity of contacts on touch-sensitive surface  451  and/or one or more tactile output generators  357  for generating tactile outputs for a user of device  300 . 
     Although some of the examples that follow will be given with reference to inputs on touch screen display  112  (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in  FIG.  4 B . In some embodiments, the touch-sensitive surface (e.g.,  451  in  FIG.  4 B ) has a primary axis (e.g.,  452  in  FIG.  4 B ) that corresponds to a primary axis (e.g.,  453  in  FIG.  4 B ) on the display (e.g.,  450 ). In accordance with these embodiments, the device detects contacts (e.g.,  460  and  462  in  FIG.  4 B ) with the touch-sensitive surface  451  at locations that correspond to respective locations on the display (e.g., in  FIG.  4 B,  460    corresponds to  468  and  462  corresponds to  470 ). In this way, user inputs (e.g., contacts  460  and  462 , and movements thereof) detected by the device on the touch-sensitive surface (e.g.,  451  in  FIG.  4 B ) are used by the device to manipulate the user interface on the display (e.g.,  450  in  FIG.  4 B ) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein. 
     Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously. 
       FIG.  5 A  illustrates exemplary personal electronic device  500 . Device  500  includes body  502 . In some embodiments, device  500  can include some or all of the features described with respect to devices  100  and  300  (e.g.,  FIGS.  1 A- 4 B ). In some embodiments, device  500  has touch-sensitive display screen  504 , hereafter touch screen  504 . Alternatively, or in addition to touch screen  504 , device  500  has a display and a touch-sensitive surface. As with devices  100  and  300 , in some embodiments, touch screen  504  (or the touch-sensitive surface) optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touch screen  504  (or the touch-sensitive surface) can provide output data that represents the intensity of touches. The user interface of device  500  can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device  500 . 
     Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety. 
     In some embodiments, device  500  has one or more input mechanisms  506  and  508 . Input mechanisms  506  and  508 , if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device  500  has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device  500  with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device  500  to be worn by a user. 
       FIG.  5 B  depicts exemplary personal electronic device  500 . In some embodiments, device  500  can include some or all of the components described with respect to  FIGS.  1 A,  1 B , and  3 . Device  500  has bus  512  that operatively couples I/O section  514  with one or more computer processors  516  and memory  518 . I/O section  514  can be connected to display  504 , which can have touch-sensitive component  522  and, optionally, intensity sensor  524  (e.g., contact intensity sensor). In addition, I/O section  514  can be connected with communication unit  530  for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. Device  500  can include input mechanisms  506  and/or  508 . Input mechanism  506  is, optionally, a rotatable input device or a depressible and rotatable input device, for example. Input mechanism  508  is, optionally, a button, in some examples. 
     Input mechanism  508  is, optionally, a microphone, in some examples. Personal electronic device  500  optionally includes various sensors, such as GPS sensor  532 , accelerometer  534 , directional sensor  540  (e.g., compass), gyroscope  536 , motion sensor  538 , and/or a combination thereof, all of which can be operatively connected to I/O section  514 . 
     Memory  518  of personal electronic device  500  can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors  516 , for example, can cause the computer processors to perform the techniques described below, including processes  800 - 1200  ( FIGS.  8 A- 8 B and  12 A- 12 C ). A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device  500  is not limited to the components and configuration of  FIG.  5 B , but can include other or additional components in multiple configurations. 
     As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices  100 ,  300 , and/or  500  ( FIGS.  1 A,  3 , and  5 A- 5 B ). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) each optionally constitute an affordance. 
     As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad  355  in  FIG.  3    or touch-sensitive surface  451  in  FIG.  4 B ) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system  112  in  FIG.  1 A  or touch screen  112  in  FIG.  4 A ) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user&#39;s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device). 
     As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation. 
     In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity. 
     The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures. 
     An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero. 
     In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input). 
     In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances). 
     For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. 
     Attention is now directed towards embodiments for providing context-specific user interfaces and associated processes that are implemented on an electronic device, such as portable multifunction device  100 , device  300 , or device  500 . 
     The following examples illustrate exemplary embodiments of context-specific user interfaces. Described herein are concepts related to interactive and/or customizable context-specific user interfaces. The context-specific user interfaces described herein are, optionally, editable in a number of ways. A user interface can display or otherwise indicate various types of information (e.g., a current time), and the type(s) of information can be customizable by the user according to some embodiments. A user interface can include aspects such as colors, density of display, and complications (or lack of complications) that are also customizable. As used here, consistent with its accepted meaning in art, a complication refers to any clock face feature other than those used to indicate the hours and minutes of a time (e.g., clock hands or hour/minute indications). Complications can provide different types of information to a user, such as data obtained from an application, and the information conveyed to a user by a complication is also customizable, as described below. In some embodiments, a complication also serves as an affordance for launching an application. Additional descriptions of context-specific user interfaces, as well as features thereof and techniques related thereto (e.g., editing and/or selecting context-specific user interfaces), are found in International Patent Application Serial No. PCT/US2015/034604, titled “Context-Specific User Interfaces,” filed Jun. 7, 2015, published as WIPO Publication No. WO/2016/022203; International Patent Application Serial No. PCT/US2015/034606, titled “Context-Specific User Interfaces,” filed Jun. 7, 2015, published as WIPO Publication No. WO/2016/022204; and International Patent Application Serial No. PCT/US2015/034607, titled “Context Specific User Interfaces,” filed Jun. 7, 2015, published as WIPO Publication No. WO/2016/022205; each of which is incorporated by reference herein in its entirety. 
       FIGS.  6 A- 6 E  illustrate user interfaces for indicating time on device  600  (e.g., device  100 ,  300 , or  500 ) in accordance with some embodiments. Device  600  has display  602 . In some embodiments, display  602  is a touch-sensitive display or other display device capable of displaying or presenting graphical content. In some embodiments, device  600  includes a rotatable and depressible input mechanism  604  and a button  606 . It should be recognized that the input mechanisms (e.g., mechanism  604  and button  606 ) are merely examples of potential mechanisms that can be included in device  600 . 
       FIGS.  6 A- 6 D  depict watch user interface  608  changing based on a current time. In  FIGS.  6 A- 6 D , watch user interface  608  includes digital indication of time  610  and analog indication of time  612 . The digital and analog indications of time both indicate the current time of the day (e.g., as measured by device  600 ) (e.g.,  3 : 00  as depicted in  FIG.  6 A ) and update with the passage of time. 
     As depicted in  FIGS.  6 A- 6 D , digital indication of time  610  is located in the upper right corner of watch user interface  608 . In some embodiments, digital indication of time  610  is displayed at other locations on watch user interface  608  (e.g., bottom right, top center, within first graphical object  614 , etc.). Digital indication of time  610  includes a representation of a digital clock with a numerical indication of an hour value (e.g., 3 as depicted in  FIG.  6 A ) and a numerical indication of a minute value (e.g., 00 as depicted in  FIG.  6 A ). In some embodiments, digital indication of time  610  indicates the current time in a different way than illustrated in  FIGS.  6 A- 6 D  (e.g., hours alone, minutes alone, seconds alone, hours with minutes and seconds). In some embodiments, digital indication of time  610  is not displayed on watch user interface  608 . 
     As depicted in  FIGS.  6 A- 6 D , analog indication of time  612  is located at approximately the center of watch user interface  608  and within first graphical object  614 . In some embodiments, analog indication of time  612  is displayed at other locations on watch user interface  608  (e.g., bottom right, top center, outside (or partially outside) of first graphical object  614 , etc.). Analog indication of time  612  includes a minute hand indicating a minute value (e.g., 00 as depicted in  FIG.  6 A ) and an hour hand indicating an hour value (e.g., 3 as depicted in  FIG.  6 A ). The minute and hour hand indicate their respective values based on their angular position relative to display  602  or relative to portions of watch user interface  608  (e.g., displayed tick marks, a dial, or bezel markings). In some embodiments, analog indication of time  612  indicates the current time in a different way than illustrated in  FIGS.  6 A- 6 D  (e.g., hour hand only, hour hand in addition to a minute hand, minute hand only, hour hand in addition to a minute hand and a second hand, hour and in addition to a second hand, or second hand only). In some embodiments, analog indication of time  612  is not displayed on watch user interface  608  (e.g.,  FIG.  6 E ). 
     Device  600  updates the appearance of objects on watch user interface  608  based on a current time (as further discussed below), which provides an additional indication of the current time when presented with digital indication of time  610  and/or analog indication of time  612 . The user interfaces depicted in  FIGS.  6 A- 6 E  are used to illustrate an embodiment covering the processes described below, including method  800  in  FIGS.  8 A- 8 B . 
     In  FIG.  6 A , device  600  displays watch user interface  608  via display  602  at a current time of 3:00. Watch user interface  608  as depicted in  FIG.  6 A  includes first graphical object  614  (e.g., a triangle) to indicate the current time (e.g., the 3 o&#39;clock hour, as depicted in  FIG.  6 A ). In some embodiments, first graphical object  614  is a different geometric shape than illustrated in  FIG.  6 A , such as a square, pentagon, hexagon, or the like. While illustrated as a single object in  FIG.  6 A , it should be recognized that first graphical object  614  can include multiple shapes or objects (e.g., a square in addition to a triangle, a pair of hands, a tree with a shadow, a mandala shape, a zodiac sign or other astrological symbol, a linguistic symbol or character, etc.). In some embodiments, first graphical object  614  includes a character user interface object. A character user interface object includes any representation of a character, for example a realistic figure or anthropomorphized character. In some embodiments, a character includes a cartoon figure. In some embodiments, a character includes a human, animal (e.g., a rat, ox, tiger, rabbit, dragon, snake, horse, sheep, monkey, rooster, dog, pig, lion, dragon, etc.), plant, organism, non-living object, or portion thereof. In some embodiments, a character user interface object includes other objects (e.g., a cartoon pushing a lawnmower, a man or woman holding a sign, a dragon breathing fire, etc.). 
     As discussed above, the appearance of first graphical object  614  provides the user of device  600  with an indication of the current time of day. For example, the triangular appearance of first graphical object  614  indicates to the user of device  600  that the hour value corresponding to the current time as depicted in  FIG.  6 A  is three. In some embodiments, the appearance of first graphical object  614  indicates a unit of time other than hours (e.g., minutes, seconds, days, etc.). 
     An aspect of the appearance of first graphical object  614 , as illustrated in  FIG.  6 A , relates to a numerical value (e.g., first graphical object  614  has three sides). In some embodiments, the appearance of first graphical object  614  does not literally relate to a numerical value (e.g., a user unfamiliar with the device is not readily able to read, interpret, or otherwise infer a specific numerical value associated with the first graphical object or an aspect of the appearance of the first graphical object). For example, in some embodiments, first graphical object  614  does not include one or more symbols with a physical or linguistic association with a numeric value (e.g., the graphical object does not, without additional context, represent or express a numerical value). 
     In some embodiments, the user of device  600  learns the corresponding numerical and temporal meaning of graphical objects through use of watch user interface  608 . For example, consider an embodiment where first graphical object  614  is a cow rather than an object with a three-sided appearance. In such an embodiment, a new user of watch user interface  608  would not recognize the cow as having a meaning associated with a particular numerical value. However, as the user of watch user interface  608  gains experience with watch user interface  608 , the user would readily begin to associate the cow-shaped graphical object with the 3 o&#39;clock hour, if the cow-shaped graphical object appeared on watch user interface  608  every day from 3:00 until 3:59, and only appeared during that period. As a result, after acquiring familiarity with watch user interface  608 , the user of watch user interface  608  is able to efficiently resolve the appearance of first graphical object  614  into a corresponding indication of time. 
       FIG.  6 B  illustrates watch user interface  608  at a current time of 3:58 (e.g., after 58 minutes have elapsed since the device  600  displayed watch user interface  608  as depicted in  FIG.  6 A ). Compared to  FIG.  6 A , digital indication of time  610  and analog indication of time  612  have updated to reflect the current time, and device  600  continues to display first graphical object  614  (e.g., a triangle) because the current time as depicted in  FIG.  6 B  remains within the 3 o&#39;clock hour. While displaying watch user interface  608  at 3:58, device  600  generates a tactile output  616  to indicate to the user of device  600  that an hour boundary is approaching (e.g., the boundary between the 3 o&#39;clock hour and the 4 o&#39;clock hour is within two minutes). In some embodiments, device  600  generates tactile output  616  in response to the current time being a predetermined time (e.g., the current time is a predetermined amount of time (e.g., one minute) before a predetermined time (e.g., 4:00)). In some embodiments, tactile output  616  is replaced with or accompanied by one or more additional alerts such as an audible alert or visual indicator. In some embodiments, device  600  generates tactile output after 4:00 to indicate to the user of device  600  that an hour boundary is currently passing or has recently passed. In some embodiments, device  600  generates tactile output  616  in response to the current time being a predetermined time (e.g., the current time is a predetermined amount of time (e.g., one minute) after a predetermined time (e.g., 4:00)). 
     After generating tactile output  616 , device  600  initiates an animation. In some embodiments, device  600  initiates an animation in response tactile output  616 . In some embodiments, device  600  initiates an animation in response to the current time being a predetermined time (e.g., the current time is a predetermined amount of time (e.g., one minute) before or after device  600  generates tactile output  616 ).  FIG.  6 C  depicts a frame of an exemplary animation. The frame depicted in  FIG.  6 C  includes transitional graphical object  618 , which is a visual blend of first graphical object  614  (representing the outgoing 3 o&#39;clock hour) and second graphical object  620  (representing the incoming 4 o&#39;clock hour, see  FIG.  6 D ). As illustrated in  FIG.  6 C , transitional graphical object  618  combines features of first graphical object  614  and features of second graphical object  620 . 
     In some embodiments, device  600  displays transitional graphical object  618  as part of a transition animation illustrating the gradual transformation of first graphical object  614  into second graphical object  620  (e.g., an animation shows the transition from a triangle to a square). In some embodiments, a transition animation includes at least an initial frame including first graphical object  614  without second graphical object  620 , a final frame including second graphical object  620  without first graphical object  614 , and an intermediate frame (e.g., occurring after the initial frame and before the final frame) including first graphical object  614  and second graphical object  620  (or an object representing a combination of first graphical object  614  and second graphical object  620  (e.g., transitional graphical object  618 ). 
     In some embodiments, an animation occurs over a fixed period of time (e.g., 3:00 to 3:59, 3:50 to 3:59, 3:58 to 4:00, 3:59 to 4:00, etc.). In some embodiments, the duration of the animation is selected (e.g., by device  600 ) based at least in part on the timing of tactile output  616  relative to a predetermined time (e.g., an upcoming hourly boundary). For example, as illustrated in  FIG.  6 B , haptic  616  occurs two minutes prior to the 4 o&#39;clock hourly boundary, resulting in device  600  displaying a transition animation with a duration of two minutes or less on watch user interface  608 . In some embodiments, the transition animation concludes display on watch user interface  608  prior to passing the upcoming hourly boundary, allowing watch user interface  608  to maintain an accurate depiction of the current time (e.g., providing an animation with a duration longer than two minutes would result in the appearance of second graphical object  620 , as illustrated in  FIG.  6 D , only after the 4 o&#39;clock hourly boundary). 
     After displaying transitional graphical object  618 , device  600  updates watch user interface  608  as depicted in  FIG.  6 D . In some embodiments, device  600  displays watch user interface  608  as depicted in  FIG.  6 D  in response device  600  ceasing to display transitional graphic  618  (e.g., a transition animation depicting transitional graphical object  618  concludes). In  FIG.  6 D , digital indication of time  610  and analog indication of time  612  have updated to reflect the current time (4:00); however, compared to  FIGS.  6 A- 6 C , watch user interface  608  includes second graphical object  620  (e.g., a square) rather than first graphical object  614  (e.g., a triangle), because the current time has progressed and is within the 4 o&#39;clock hour. In  FIG.  6 D , the four-sided appearance of second graphical object  620  indicates to the user that the current time is within the 4 o&#39;clock hour. 
     Turning to  FIG.  6 E , device  600  displays watch user interface  609  on display  602 . Watch user interface  622  includes transitional graphical object  622 , which illustrates an anthropomorphized representation of second graphical object  620  interacting with (e.g., eating) a representation of first graphical object  614 . In some embodiments, interacting includes a graphical object performing an action that affects another graphical object (e.g., a first graphical object pushing a second graphical object). In some embodiments, transitional graphical object  622  is presented (e.g., displayed) in addition to or instead of transitional graphical object  618  discussed above with reference to  FIG.  6 C . 
     In contrast to the blended transitional graphical object  618  illustrated in  FIG.  6 C , transitional graphical object  622  includes first representational object  626  and second representational object  624  (e.g., corresponding to first graphical object  614  and second graphical object  620 , respectively). 
     In some embodiments, representational objects (e.g., first representational object  626  and second representational object  624 ) vary somewhat in appearance from their respective objects but are otherwise recognizable as their respective objects. In some embodiments, a representational object includes a resized version of the corresponding graphical object (e.g., first representational object  626  is a smaller version of first graphical object  614 ). In some embodiments, a representational object includes details not present in the graphical object it represents (e.g. second representational object  624  includes teeth). In some embodiments, a representational object does not include details present in the graphical object it represents (e.g., second representational object  624  does not include an indication of time). 
     The user interfaces depicted in  FIGS.  7 A- 7 D  illustrate an embodiment covering the processes described below, including method  800  in  FIGS.  8 A- 8 B . In particular,  FIGS.  7 A- 7 D  illustrates an embodiment in which the display of transitional graphical objects is conditional. 
     In  FIG.  7 A , device  600  displays watch user interface  708  on display  602  at a current time of 4:58. While displaying watch user interface  708 , device  600  generates tactile output  704  (e.g., device  600  generates tactile output  704  in response to the current time corresponding to a predetermined time). In some embodiments, tactile output  704  is replaced with or accompanied by one or more additional alerts such as an audible alert or visual indicator. Rather than displaying a transitional graphical object along with presenting the haptic (e.g., as depicted in  FIGS.  6 B and  6 C ), device  600  continues to display the watch user interface of  FIG.  7 A  until further conditions are satisfied, as discussed below. 
     As illustrated by  FIG.  7 B , after emitting tactile output  704 , device detects user input  706  (e.g., a tap gesture). In some embodiments, user input  706  includes one or more inputs associated with a user of the device responding to tactile output  704  (e.g., device  600  receives orientation data from an internal sensor indicating that the user has raised or is raising device  600  into a viewing position, device  600  detects a rotation of rotatable and depressible input mechanism  604 , device  600  detects a depression of button  606 , etc.). 
     Upon (e.g., in response to) receiving user input  706  within a response interval (e.g., within two minutes of tactile output  704  or alternatively, within 60 seconds of the current time transitioning to a new hour), device  600  displays the watch user interface of  FIG.  7 C . As illustrated in  FIG.  7 C , device  600  displays watch user interface  708  with transitional graphical object  710 . Transitional graphical object  710  includes a portion of third graphical object  702  (representing the outgoing 4 o&#39;clock hour), and a portion of fourth graphical object  712  (representing the incoming 5 o&#39;clock hour, see  FIG.  7 D ). In some embodiments second graphical object  620  is the same object as third graphical object  702 . In some embodiments, transitional graphical object  710  includes representations of objects that are similar in appearance to third graphical object  702  and fourth graphical object  712  (e.g., resized versions of the graphical objects, representations of the graphical objects that include more visual details, simplified representations of the graphical objects that include less visual details, or other representations that are recognizable by the user of device  600  as the respective graphical objects). 
     Similar to the discussion above with respect to  FIGS.  6 C and  6 E , in some embodiments, device  600  displays transitional graphical object  710  as part of a transition animation illustrating the transition between the 4 o&#39;clock hour and the 5 o&#39;clock hour.  FIG.  7 C  illustrates a frame of a transition animation showing third graphical object  702  (e.g., square) being pushed off of the rightmost edge of watch user interface  708  by fourth graphical object  712  (e.g., pentagon). In some embodiments, a transition animation occurs over a fixed period of time (e.g., 4:59 to 5:00, 5:00 to 5:01, 4:59 to 5:02, etc.). In some embodiments, a transition animation includes at least an initial frame including third graphical object  702  without fourth graphical object  712 , a final frame including fourth graphical object  712  without third graphical object  702 , and an intermediate frame (e.g., occurring after the initial frame and before the final frame) including at least a portion of third graphical object  702  and at least a portion of fourth graphical object  712 . 
     In some embodiments, device  600  determines the duration of a transition animation based in part on a time at which device  600  receives user input gesture  706  relative to a predetermined time (e.g., an upcoming hourly boundary). In some embodiments, a duration is determined based upon the difference between the time at which device  600  receives user input gesture  706  and a predetermined time (e.g., an upcoming hourly boundary). In some embodiments, a duration is determined based upon the difference between the time at which device  600  receives user input gesture  706  and the minute past an hourly boundary (e.g., 5:01). In this manner, device  600  determines a shorter animation duration for a user input received closer (e.g., 4:59) to an hourly boundary (e.g., 5:00) and a longer animation duration for a user input gesture received further (4:58) from the hourly 5:00 hourly boundary. In some embodiments, device  600  determines a duration of a transition animation such that the transition animation will complete prior to an event (e.g., the current time reaching the next hourly boundary, the current time reaching a minute past the next hourly boundary). 
     In some embodiments, device  600  determines the duration of a transition animation based in part on a time at which device  600  emits haptic  704  relative to an hourly boundary (e.g., the difference between the current time at which device  600  emits haptic  704  and the upcoming hourly boundary). For example, if device emits haptic  704  at 4:58 as illustrated in  FIG.  7 A , device  600  sets the duration of a transition animation to two minutes. In some embodiments, a duration of a transition animation is dynamically adjusted by device  600 , which selects a subset of available animation frames. In some embodiments, a duration of a transition animation is dynamically adjusted by modifying an animation playback rate (e.g., the number of frames displayed in a given period of time) associated with a respective transition animation. 
     In contrast, if device  600  does not receive user input  706  (or other device inputs associated with a user of the device responding to tactile output  704  as described above) within the response interval (e.g., within two minutes of the alert), device  600  forgoes displaying transitional graphical object  710  or any associated animation (e.g., device  600  displays watch user interface  708  with fourth graphical object  712  as shown in  FIG.  7 D  without displaying transitional graphic  710 ). 
     In some embodiments, device  600  displays the user interface of  FIG.  7 C  (including transitional graphical object  710 ) upon determining (e.g., by device  600 ) that display  602  is in an active state, and forgoes displaying transitional graphical object  710  or any associated animation upon determining that display  602  is in a non-active state. In some embodiments, determining display  602  is in an active state includes determining by device  600  that a user is viewing display  602 . In some embodiments determining display  602  is in an active state includes determining by device  600  that display  602  is displaying content. In some embodiments, determining that display  602  is in a non-active state includes determining by device  600  that a user is not viewing display  602 . In some embodiments, determining that display  602  is in a non-active state includes determining by device  600  that display  602  is not displaying content. 
     After displaying transitional graphical object  710 , device  600  updates watch user interface  708  as depicted in  FIG.  7 D . In  FIG.  7 D , digital indication of time  610  and analog indication of time  612  have updated to reflect the current time (5:02) and device  600  displays fourth graphical object  712  (e.g., pentagon) rather than third graphical object  702  (e.g., square) because the current time has progressed and is within the 5 o&#39;clock hour. In  FIG.  7 D , the five-sided appearance of third graphical object  712  indicates to the user that the current time is within the 5 o&#39;clock hour. 
       FIGS.  8 A- 8 B  are a flow diagram illustrating method  800  for indicating a current time using an electronic device in accordance with some embodiments. Method  800  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 ) with a display device (e.g.  602 ). Some operations in method  800  are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted. In one example, method  800  relates to having (1) one object (e.g., a dragon) during a unit of time (e.g., one hour) indicate a current time (e.g., 10:00), (2) a point in time within the unit of time (e.g., 10:30) where a combination of objects (e.g., a dragon eating a rat, 3 turning into 4, etc.) are displayed, and (3) objects switch when switching between units of time (e.g., from the 10 o&#39;clock hour to the 11 o&#39;clock hour). 
     As described below, method  800  provides a technique for dynamically modifying a user interface object based on a current time. The method provides a user with an easily decipherable visual indication that quickly draws the user&#39;s attention to relevant information (e.g., a current hour measured by a device) and/or reduces the cognitive burden on a user for identifying a state of a device (e.g., a current time as measured by a device), thereby creating a more efficient human-machine interface. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to quickly resolve the current time, the user does not need to spend as much time interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more efficiently. 
     At  802 , the device (e.g., 600) displays, via the display device (e.g., 602) at a first time (e.g., 10:00), a first user interface object (e.g.,  614  in  FIG.  6 A or  702    in  FIG.  7 A ) without displaying a second user interface object (e.g.,  620  in  FIG.  6 D or  712    in  FIG.  7 D ), where the second user interface object is different from the first user interface object, and where the first user interface object represents a first period of time that includes the first time (e.g., the first user interface object specifically represents the one hour period of time from 10:00 to (but not including)  11 : 00 ). In some embodiments, the first and/or second user interface object is a character user interface object. 
     At  804 , the device displays, via the display device at a second time after the first time and within the first period of time (e.g., 10:59), a combination (e.g.,  618  in  FIG.  6 C,  622    in  FIG.  6 E , or  710  in  FIG.  7 C ) of the first user interface object and the second user interface object (e.g., simultaneous display of both, a gradual transition from one to other, or an animation of one turning into other) (in some examples, the combination is displayed in response to user interaction, such as a wrist raise or tap). In some embodiments, displaying the combination occurs in accordance with a determination that the user input is received ( 806 ) within a threshold of time after outputting the alert ( 804 ). 
     In some embodiments, the combination occurs at or near an hour boundary (e.g., a time prior to the hour boundary providing enough time for the combination to finish before the hour boundary). In some embodiments, a haptic (e.g.,  616  in  FIG.  6 B or  704    in  FIG.  7 A ) is played after or near the hour boundary, indicating that a user can look at the device to see an animation for the hour boundary (e.g., an animation is played, in whole, if user input is received within a window of time after the haptic). In some embodiments, an alert (e.g., audio, visual indication, or haptic) is output at the hour boundary (e.g., a boundary between units of time). In some embodiments, if a user responds within a time threshold (e.g., the device detects a tap input or a wrist raise), an animation is displayed (e.g.,  708  in  FIG.  7 C  illustrates a frame of an animation). In some embodiments, if a user responds after the time threshold (e.g., the device detects a tap input or wrist raise), an indication of time is displayed without displaying the animation. For example, at  806 , the device, before the second time and within the first period of time, outputs an alert (e.g.,  704 ) (e.g., haptic feedback). 
     At  808 , in some embodiments, the device receives user input (e.g.,  706 ) (e.g., a tap or wrist raise), wherein displaying the combination occurs in accordance with a determination that the user input is received within a threshold of time after the alert. 
     At  810 , in some embodiments, the device, in response to receiving the user input ( 806 ) and in accordance with a determination that the user input is not received within the threshold, forgoes display, via the display device, of the combination of the first user interface object and the second user interface object. Determining whether to display information (e.g., a transitional graphical object including the combination of the first user interface object and the second user interface object) based receiving a timely user input response to an alert, emphasizes to a user that an easily decipherable visual indication of relevant information (e.g., the current hour measured by the watch) is only temporarily available. Providing improved user feedback regarding the state of the device (e.g., the availability of data) enhances the operability of the device and makes the user-device interface more efficient (e.g., by allowing the user to quickly resolve the current time when additional visual aids are available, the user does not need to spend as much time interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more efficiently. 
     In some embodiments, an animation is displayed at a time boundary if a user is viewing the device (e.g., watch). For example, displaying the combination occurs in accordance with a determination that the display device is actively displaying content at the second time (e.g., a user is currently looking at her watch). At  812 , in some embodiments, in accordance with a determination that the display device is not actively displaying content at the second time, the device forgoes display, via the display device, of the combination of the first user interface object and the second user interface object. 
     At  814 , in some embodiments, the device displays, via the display device, one character turning into another character. For example, the device displays a transition (e.g.,  618  in  FIG.  6 C ) from the first user interface object to the second user interface object, where the transition corresponds to the first user interface object turning (e.g., morphing, transforming, or changing) into the second user interface object. In some embodiments, transitioning from the first user interface object to the second user interface object includes an animation beginning with the first user interface object and ending with the second user interface object such that a frame (e.g., as depict by  608  of  FIG.  6 C ) of the animation between the beginning and the ending includes a user interface object that is based on the first user interface object and the second user interface object, where the frame does not include solely the first user interface object or solely the second user interface object. 
     At  816 , in some embodiments, the device displays, via the display device, the combination as a gradual transition (e.g., as depicted by  608  of  FIG.  6 C ). For example, the transitioning is continual (e.g., a character starts transitioning at 10:00 and continues to transition throughout the hour) from the first time (e.g., 10:00) to the third time (e.g., 11:00). Gradually transitioning a user interface object into another user interface object provides the user with an easily decipherable visual indication that quickly draws the user attention to relevant information (e.g., the current hour measured by the watch). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to quickly resolve the current time, the user does not need to spend as much time interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more efficiently. 
     At  818 , in some embodiments, the device displays, via the display device, one character interacting with another character. For example, the combination of the first user interface object and the second user interface object depicts the first user interface object interacting (e.g.,  622  in  FIG.  6 E ) (e.g., a dragon eats a rat, or a square eats a triangle) with the second user interface object. In some embodiments, the combination includes an animation (e.g., the first user interface object physically moving and/or changing appearance), and the animation includes a frame with at least a portion of the first user interface object and at least a portion of the second user interface object. 
     At  820 , in some embodiments, the device displays, via the display device, a transition animation at a boundary (e.g., 11:00), where the animation involves both characters (e.g., as depict by  710  in  FIG.  7 C ). For example, displaying the combination of the first user interface object and the second user interface object includes displaying an animation involving the first user interface object and the second user interface object (e.g.,  710  in  FIG.  7 C ). In some embodiments, the animation includes a frame with the first user interface object and the second user interface object (e.g., the first user interface object pushing the second user interface object such that the second user interface object is eventually no longer displayed). 
     At  822 , the device displays, via the display device and at a third time (e.g., 11:00) after the second time (e.g., 10:59), the second user interface object without displaying the first user interface object, where the second user interface object represents a second period of time that includes the third time (e.g., 11:00). In some embodiments, the first period of time and the second period of time are mutually exclusive. 
     Note that details of the processes described above with respect to method  800  (e.g.,  FIGS.  8 A- 8 B ) are also applicable in an analogous manner to the methods described below. For example, method  1200  optionally includes one or more of the characteristics of the various methods described below with reference to method  800 . For example, the techniques for illustrating the transition from a first object to a second object (e.g., via a transition animation) discussed in method  800  can be used in method  1200  to illustrate graphical objects transitioning from a first appearance to a second appearance at hourly boundaries. For brevity, these details are not repeated below. 
       FIGS.  9 A- 9 E  illustrate user interfaces for indicating time on device  600  (as described above) in accordance with some embodiments. The user interfaces depicted in these figures are used to illustrate an example covering the processes described below, including the processes in  FIGS.  12 A- 12 C . 
     In  FIG.  9 A , device  600  displays watch user interface  908  via display  602  at a current time of 3:15. Watch user interface  908  includes digital indication of time  610  and analog indication of time  612  (as describe above), each indicating a current time of 3:15. Watch user interface  908  also includes graphical object  904  which indicates a current time of day based at least in part on its appearance (e.g., shape) and location on watch user interface  908 . In some embodiments, the appearance represents a first unit of time (e.g., hours) and does not represent a second unit of time (e.g., minutes) such that the appearance alone only indicates a current time according to the first unit of time and does not indicate a time according to the second unit of time. Similarly, in some embodiments, the location represents the second unit of time (e.g., minutes) and does not represent the first unit of time (e.g., hours) such that the location alone only indicates a current time according to the second unit of time and does not indicate a time according to the first unit of time. 
     As illustrated in  FIG.  9 A , graphical object  904  is a triangle to indicate the current hour (i.e., 3 o&#39;clock hour). In some embodiments, graphical object  904  is a different geometric shape than illustrated, such as square, pentagon, hexagon, or the like. While illustrated as a single object, in some embodiments, graphical object  904  includes multiple shapes or objects (e.g., a square in addition to a triangle, a pair of hands, a tree with a shadow, a mandala shape, a zodiac sign or other astrological symbol, a linguistic symbol or character, etc.). In some embodiments, graphical object  904  includes a character user interface object. In some embodiments, a character user interface object includes a representation of a character, for example a realistic or anthropomorphized character. In some embodiments, a character includes a cartoon figure. In some embodiments, a character includes a human, animal (e.g., a rat, ox, tiger, rabbit, dragon, snake, horse, sheep, monkey, rooster, dog, pig, lion, dragon, etc.), plant, organism, non-living object, or portion thereof. In some embodiments, a character user interface object includes other objects (e.g., a cartoon pushing a lawnmower, a woman holding a sign, a man holding a briefcase, a dragon breathing fire, etc.). 
     As discussed above, the appearance of graphical object  904  provides the user of device  600  with an indication of the current time of day. For example, the triangular shape (i.e., three-sided appearance) of graphical object  904   a  as illustrated in  FIG.  9 A  indicates to the user of device  600  that the hour value corresponding to the current time is three (e.g., the time is in the range 3:00-3:59). In some embodiments, the appearance of graphical object  904  indicates a unit of time other than hours (e.g., minutes, seconds, days, etc.). 
     An aspect of the appearance of graphical object  904   a , as illustrated in  FIG.  9 A , relates to a numerical value (e.g., graphical object  904  has three sides). In some embodiments, no aspect of the appearance of graphical object  904  literally relates to a numerical value (e.g., a user unfamiliar with the device is not readily able to read, interpret, or otherwise infer a specific numerical value associated with the graphical object or an aspect of the appearance of the graphical object). For example, in some embodiments, graphical object  904  does not include one or more symbols with a physical or linguistic association with a numerical value (e.g., the graphical object does not, without additional context, represent or express a numerical value). 
     In some embodiments, the user of device  600  learns the corresponding numerical and temporal meaning of graphical objects through use of watch user interface  908 . For example, consider an embodiment where the graphical object  904  is a soccer ball rather than an object with a three-sided appearance. In such an embodiment, a new user of watch user interface  908  would not recognize the soccer ball as having a meaning associated with a particular numerical or temporal value. However, as the user of watch user interface  908  gains experience with watch user interface  908 , the user would readily begin to associate the soccer ball-shaped hourly object with the 3 o&#39;clock hour, if the soccer ball-shaped graphical object appeared on watch user interface  908  every day from 3:00 until 3:59, and only appeared during that period. As a result, after acquiring familiarity with watch user interface  908 , the user of watch user interface  908  is able to efficiently resolve the appearance of hourly graphical object  904  into a corresponding indication of time. 
     As discussed above, the location of graphical object  904  on watch user interface  908  provides the user of device  600  with an indication of the current time of day. In  FIG.  9 A , graphical object  904   a  is located at a position on graphical user interface  908  corresponding to a minute value of fifteen (e.g., 15). In some embodiments, the location of graphical object  904  indicates a unit of time other than minutes (e.g., hours, seconds, days, etc.). 
     As illustrated in  FIG.  9 A , watch user interface  908  also includes radial time-scale  902  (e.g. minute and/or hour markers, a dial, or bezel markings). Radial time-scale  902  includes twelve individual markers angularly spaced about a central point on watch user interface  908 . Radial time-scale  902  serves as visual reference to users of device  600  in deciphering the time indicated by the location of graphical object  904  on watch user interface  908  (e.g., a user of device  600  interprets the position graphical object  904  relative to the markers). As illustrated in  FIG.  9 A , starting at a value of zero (e.g., 0) for the marker centered along the top edge of watch user interface  908 , successive markers (moving clock wise around watch user interface  908 ) each represent minute values increasing by 5 (e.g., 5, 10, 15, 20, etc.). In some embodiments, radial time-scale  902  includes more or less than twelve markers (e.g., one, twenty-four, sixty, etc.) to provide varying degrees of precision. However, since users are accustomed to perceiving analog clock faces, a radial time-scale markers is optional, as the relative positioning of objects (e.g., hourly object  904 ) on an interface resembling a clock indicates an approximate time even without such markings. 
     While the location of graphical object  904   a , as illustrated in  FIG.  9 A , relates to a minute value of 15 according to its position relative to radial time-scale  902 , in some embodiments, the location of graphical object  904  does not relate to a numerical value based on its positioning relative any scale. For example, in some embodiments, graphical object  904  is located at a position on watch user  908  that does not readily correspond to a numeric value (e.g., the graphical object does not, without additional context, represent a numerical value). 
     In some embodiments, the user of device  600  learns the corresponding numerical and temporal meaning of a graphical objects location on watch user interface  908  through use of watch user interface  908 . For example, consider an embodiment where graphical object  904  is located at the center of watch user interface  908 . In such an embodiment, a new user of watch user interface  908  would not recognize the central location as having a meaning associated with a particular numerical or temporal value. However, as the user of watch user interface  908  gains experience with watch user interface  908 , the user would readily begin to associate the central location of the graphical object with the 20 th  minute of an hour, if graphical object  904  appeared on watch user interface  908  at that location every at twenty minutes past each hour (e.g. 1:20, 2:20, 3:30, etc.). As a result, after acquiring familiarity with watch user interface  908 , the user of watch user interface  908  is able to efficiently resolve the location of graphical object  904  into a corresponding indication of time. 
       FIG.  9 B  illustrates watch user interface  908  at a current time of 3:45 (e.g., after 30 minutes have elapsed since device  600  displayed watch user interface  908  as depicted in  FIG.  9 A ). Device  600  displays updated digital and analog indications of time reflecting a current time of 3:45. Graphical object  904   a  remains displayed on watch user interface  908  as a triangle; however, device  600  displays the object at an updated position on watch user interface  908  indicating a current minute value of 45. 
       FIG.  9 C  illustrates watch user interface  908  at a current time of 3:59 (e.g., after 14 minutes have elapsed since device  600  displayed watch user interface  908  as depicted in  FIG.  9 B ). Device  600  displays updated digital and analog indications of time reflecting a current time of 3:59. Graphical object  904   a  remains displayed on watch user interface  908  as a triangle; however, device  600  displays the object at an updated position on watch user interface  908  indicating a current minute value of 59. 
       FIG.  9 D  illustrates watch user interface  908  at a current time of 4:00 (e.g., after one minute has elapsed that device  600  displayed watch user interface  908  as depicted in  FIG.  9 C ). Device  600  displays updated digital and analog indications of time reflecting a current time of 4:00. Device  600  now displays graphical object  904   b  (e.g., the appearance of the graphical object has changed from a triangle to a square) at a position on watch user interface  908  indicating a current minute value of 00. 
       FIG.  9 E  illustrates watch user interface  908  at a current time of 4:15 (e.g., after 15 minutes have elapsed since device  600  displayed watch user interface  908  as depicted in  FIG.  9 D ). Device  600  displays updated digital and analog indications of time reflecting a current time of 4:15. Device  600  continues to display graphical object  904   b  (e.g. the appearance of the graphical object remains a square, however, device  600  displays the object at an updated position on watch user interface  908  indicating a current minute value of 15. 
       FIGS.  10 A- 10 G  illustrate user interfaces for indicating time on device  600  (as described above) in accordance with some embodiments. The user interfaces depicted in these figures are used to illustrate an example covering the processes described below, including the processes in  FIGS.  12 A- 12 C . 
     In  FIG.  10 A , device  600  displays watch user interface  1008  via display  602  at a current time of 2:59. Watch user interface  1008  includes digital indication of time  610  and analog indication of time  612  (as describe above), both displaying a current time of 2:59. As illustrated in  FIG.  10 A , watch user interface  1008  also includes radial time-scale  1002 . Radial time-scale  1002  includes twelve individual holes angularly spaced about a central point on watch user interface  1008 . Radial time-scale  1002  serves as visual reference to assist users of device  600  in deciphering the time indicated by the position of character user interface object  1010  on watch user interface  1008  (e.g., a user of device  600  interprets the position of character user interface object  1010  on watch user interface  1008  relative to the holes of radial time-scale  1002 ). As illustrated in  FIG.  10 A , each hole is associated with an hourly value (e.g., values corresponding to the hourly markers a clock dial or bezel). 
     In  FIG.  10 A , device receives tap gesture  1004 . In some embodiments, tap gesture  1004  is replaced with or accompanied by one or more other device inputs (e.g., device  600  receives orientation data from an internal sensor indicating that the user has raised or is raising device  600  into a viewing position). Upon receiving tap gesture  1004 , device  600  updates watch user interface  1008  to appear as depicted in  FIG.  10 B . 
       FIG.  10 B  illustrates watch user interface  1008  at current time of 3:00 (e.g., after one minute has elapsed since device  600  displayed watch user interface  1008  as depicted in  FIG.  10 A ). Device  600  displays updated digital indication of time  610  and analog indication of time  612 , both reflecting a current time of 3:00. As illustrated in  FIG.  10 B , device  600  begins displaying an animation including character user interface object  1010   a  at a position on watch user interface  1008  indicating a current hour value of 3 (e.g., character user interface object  1010   a  begins emerging from hole  1006 , which is associated the 3 o&#39;clock hour). The location of character user interface object  1010   a  indicates to the user of device  600  that the current time is within the 3 o&#39;clock hour. In some embodiments, device  600  initiates an animation in response receiving user input (e.g., device  600  receives orientation data from an internal sensor indicating that the user has raised or is raising device  600  into a viewing position, device  600  detects a rotation of rotatable and depressible input mechanism  604 , device  600  detects a depression of button  606 , device  600  detects a tap gesture on watch user interface  1008 , etc.). 
     In some embodiments, a character user interface object includes a representation of a character, for example a realistic or anthropomorphized character. In some embodiments, a character includes a cartoon figure. In some embodiments, a character includes a human, animal (e.g., a rat, ox, tiger, rabbit, dragon, snake, horse, sheep, monkey, rooster, dog, pig, lion, dragon, etc.), plant, organism, non-living object, or portion thereof. In some embodiments, a character user interface object includes more than one object (e.g., a cartoon pushing a lawnmower, a woman holding a sign, a man holding a briefcase, a dragon breathing fire, etc.). 
       FIG.  10 C  illustrates watch user interface  1008  as device continues to display an animation of character graphical object  1010   a  emerging from hole  1006  (e.g., device  600  displays a subsequent frame of the animation of character user interface object  1010   a  emerging from hole  1006 ). As depicted in  FIG.  10 C , character user interface object  1010   a  includes a person sleeping with a sleeping mask. As discussed above, the appearance of character user interface object  1010   a  provides the user of device  600  with an indication of a current time of day. For example, messy morning hair and a sleeping mask indicate to the user of device  600  that the position on watch user interface  1008  of character user interface object  1010   a  (e.g., hole  1006 ) corresponds to three in the morning (e.g., 3 am) rather than three in the afternoon (e.g., 3 pm). In addition, the numbers on the sleeping mask indicate a minute value of the current time (e.g., 00). 
     In some embodiments, character user interface object  1010  represents nighttime by depicting a yawn and holding a candle. In some embodiments, character user interface object  1010  is altered to depict wearing clothing associated with nighttime, such as pajamas. In some embodiments, the character interface object is modified to yawn or wear pajamas in accordance with a determination that the user should go to sleep. In some embodiments, the determination is be based on, for example, any of a preset time, recognition of a pattern of the user&#39;s sleep, indication of an early event on the next day&#39;s calendar, recognition that the user has been active for longer than a predetermined time, etc. In some embodiments, the appearance of character user interface object  1010  indicates a time of day other than morning or nighttime (e.g., breakfast time, lunch time, dinner time, bedtime, a time corresponding to an event such as a calendar appointment, etc.). 
     In some embodiments, the animation of character user interface object  1010   a  emerging from hole  1006  includes the character performing an action related to the time of day (e.g., snoring, yawning, eating a particular meal, carrying a brief case, reading a morning newspaper, etc.). In some embodiments, the animation of character user interface objects  1010  includes the character performing different actions for each hour of the day (e.g., a cartoon character user interface object holds up a sign indicating the current hour, a dragon character user interface object breathes fire in the shape of an hourly indicator or contort its body into a shape indicating the current hour, etc.). In some embodiments, the animation of character user interface object  1010   a  emerging from hole  1006  has a fixed duration (e.g., character user interface object is only displayed by device  600  for a duration of 5 seconds). 
       FIG.  10 D  illustrates watch user interface  1008  at a current time of 4:15 (e.g., after approximately 13.25 hours have elapsed since device  600  displayed watch user interface  1008  as depicted in  FIG.  10 C ). Device  600  displays digital indication of time  610  and analog indication of time  612 , both reflecting a current time of 4:15. Device  600  displays character user interface object  1010   a  on watch user interface  1008  at position on watch user interface  1008  indicating a current hour value of four (e.g., 4). The location of character user interface object  1010   a  indicates to the user of device  600  that the current time is within the 4 o&#39;clock hour. The appearance of character user interface object  1010   a  with messy morning hair and a sleeping mask indicates to the user of device  600  that the position on watch user interface  1008  of character user interface object  1010   a  (e.g., hole  1014 ) corresponds to four in the morning (e.g., 4 am) rather than four in the afternoon (e.g., 4 pm). In addition, the numbers on the sleeping mask indicate a minute value of the current time (e.g., 15). 
       FIG.  10 E  illustrates watch user interface  1008  at a current time of 3:00 (e.g., after approximately 10.75 hours have elapsed since device  600  displayed watch user interface  1008  as depicted in  FIG.  10 D ). Device  600  displays digital indication of time  610  and analog indication of time  612 , both reflecting a current time of 3:00. Device  600  updates watch user interface  1008  to display character user interface object  1010   b  at position on watch user interface  1008  indicating a current hour value of three (e.g., 3). The location of character user interface object  1010   a  indicates to the user of device  600  that the current time is within the 3 o&#39;clock hour. The appearance of character user interface object  1010   b  (e.g., dressed in workday attire with neat hair carrying briefcase  1012 ) indicates to the user of device  600  that the position on watch user interface  1008  of character user interface object  1010   b  (e.g., hole  1006 ) corresponds to three in the afternoon (e.g., 3 pm, a time corresponding to a typical workday schedule) rather than three in the morning (e.g., 3 am). In addition, device  600  display numbers on briefcase  1012  corresponding to a minute value of the current time (e.g., 00). 
       FIG.  10 F  illustrates watch user interface  1008  at a current time of 3:00 (e.g., after approximately 12 hours have elapsed since device  600  displayed watch user interface  1008  as depicted in  FIG.  10 E ). Device  600  displays digital indication of time  610  and analog indication of time  612 , both reflecting a current time of 3:30. Device  600  continues to display watch user interface  1008  to display character user interface object  1010   b  at position on watch user interface  1008  indicating a current hour value of three (e.g., 3). The appearance of character user interface object  1010   b  (e.g., dressed in workday attire with neat hair carrying briefcase  1012 ) indicates to the user of device  600  that the position on watch user interface  1008  of character user interface object  1010   b  (e.g., hole  1006 ) corresponds to three in the afternoon (e.g., 3 pm). In addition, device  600  display numbers on briefcase  1012  corresponding to a minute value of the current time (e.g., 30). 
       FIG.  10 G  illustrates watch user interface  1008  at a current time of 4:15 (e.g., after approximately 13.25 hours have elapsed since device  600  displayed watch user interface  1008  as depicted in  FIG.  10 F ). Device  600  displays digital indication of time and analog indication of time  612 , both reflecting a current time of 4:15. Device  600  displays character user interface object  1010   b  on watch user interface  1008  at position on watch user interface  1008  indicating a current hour value of four (e.g., 4). The appearance of character user interface object  1010   b  (e.g., dressed in workday attire with neat hair carrying briefcase  1012 ) indicates to the user of device  600  that the position on watch user interface  1008  of character user interface object  1010   b  (e.g., hole  1014 ) corresponds to four in the afternoon (e.g., 4 pm). In addition, device  600  display numbers on briefcase  1012  corresponding to a minute value of the current time (e.g., 15). 
     In some embodiments, device  600  receives first data indicative of an event (e.g., a calendar appointment). Device  600  determines whether the event meets a condition (e.g., the event corresponds to the current date). In accordance with the determination that the event meets the condition, device  600  updates a character user interface object by changing a visual aspect of the character user interface object (e.g., displaying character user interface object with a birthday hat). In some embodiments, device  600  determines whether the current or forecasted weather corresponds to one or more designated weather conditions. In some embodiments, designated weather conditions are system-designated. In some embodiments, designated weather conditions include favorable weather conditions such as sunshine or inclement weather conditions such as rain, thunderstorms, wind, snow, and so forth. If device  600  determines that the current or forecasted weather corresponds to one or more designated weather conditions, device  600  updates a character user interface object to reflect the current or forecasted weather. For example, a user interface screen including a character user interface object with a umbrella, as well as raindrops. In some embodiments, device  600  displays a user interface object reflecting the designated weather condition. In some embodiments, a character user interface object is animated to react to a user interface object reflective of a designated weather condition. As another example, a user interface screen displays a character user interface object with sunglasses and surfboard, as well as sun. 
     In some embodiments, a device (such as device  600 ) displays a character user interface object indicating when data indicating user activity can be received. For example, the device includes a user activity monitor (such as a workout monitor), an accelerometer, a gyroscope, a motion sensor, and/or a combination thereof. The device determines whether the data indicating user activity is received outside of a threshold interval after a previous user activity. For example, the device determines whether a threshold period of time has elapsed since the last data indicating user activity (e.g., the last user workout). If the device determines that the data indicating user activity is received outside of the threshold interval after a previous user activity, the device animates the character user interface object to reflect inactivity. For example, the character changes an expression and/or posture to represent boredom, a sedentary or recumbent posture, a sullen or apathetic appearance, and so forth. 
     In some embodiments, device  600  determines whether the user activity is current user activity, and, if so, animates a character user interface object to represent exercise. For example, a user interface screen including a character user interface object and barbell. In some embodiments, device  600  animates a character user interface object to depict an activity related to exercise, such as motion, running, weight lifting, swimming, bicycling, pushups, and/or sweat, heavy breathing, or any other signs of physical exertion. In some embodiments, the activity monitor includes options for the user to indicate which activity they are going to begin. In these cases the character appearance is changed to reflect the selected activity option. 
       FIGS.  11 A- 11 D  illustrate user interfaces for indicating time on device  600  (as described above) in accordance with some embodiments. The user interfaces depicted in these figures are used to illustrate an example covering the processes described below, including the processes in  FIGS.  12 A- 12 C . 
     In  FIG.  11 A , device  600  displays watch user interface  1108  via display  602  at a current time of 3:30. In addition to digital indication of time  610  indicating a current time of 3:30, watch user interface  1108  includes character user interface object  1102 . As discussed above, a character user interface object can include a character figure in addition to other objects. For example, as depicted in  FIG.  11 A , character user interface object  1102  includes man object  1102   a  pushing mower object  1102   b  over a lawn that contains lawn emblem object  1102   c  (e.g., “3”). 
     An aspect of the appearance of character user interface object  1102  provides the user of device  600  with an indication of the current time of day. For example, as illustrated in  FIG.  11 A , device  600  displays lawn emblem object  1102   c  (e.g., a “3”) indicating to the user of device  600  that the hour value corresponding to the current time is three (e.g., 3). In some embodiments, an aspect of the appearance of character user interface object  1102  (e.g., lawn emblem object  1102   c ) indicates a unit of time other than hours (e.g., minutes, seconds, days, etc.). 
     A location of at least a portion of character user interface object  1102  on watch user interface  1108  also provides the user of device  600  with an indication of the current time of day. In  FIG.  11 A , device  600  displays character user interface object  1102  (e.g., man object  1102   a  and mover object  1102   b ) at a position on graphical user interface  1108  illustrative of the man having cut half of the lawn (e.g., un-mowed grass  1104   a  and mowed grass  1104   b  occupy the same amount of graphical user interface  1108 ). In some embodiments, the amount of lawn mown is based on the corresponding position of character user interface object  1102  (e.g., the position of man object  1102   a  and mower object  1102   b ) on watch user interface  1108  is proportional to the minute value of the current time. For example, as depicted in  FIG.  11 A , the position of character user interface object  1102  (e.g., half way through mowing the lawn) indicates a minute value corresponding to half of the minutes within the current hour (e.g., 30 minutes). In some embodiments, the location of character user interface object  1102  indicates a unit of time other than minutes (e.g., hours, seconds, days, etc.). 
       FIG.  11 B  illustrates watch user interface  1108  at a current time of 3:59 (e.g., after 29 minutes have elapsed since device  600  displayed watch user interface  1108  as depicted in  FIG.  11 A ). Device  600  displays an updated digital indication of time  610  reflecting a current time of 3:59. As depicted in  FIG.  11 B , device  600  maintains display of lawn emblem  1102   c  as a “3” however, the location of character user interface object  1102  has been updated. As illustrated in  FIG.  11 B , device  600  displays character user interface object  1102  at a location indicating a minute value corresponding to the current time as 59. 
       FIG.  11 C  illustrates watch user interface  1108  at a current time of 4:00 (e.g., after one minute has elapsed since device  600  displayed watch user interface  1108  as depicted in  FIG.  11 B ). Device  600  displays an updated digital indication of time  610  reflecting a current time of 4:00. Device  600  displays of lawn emblem  1102   c  as a “3” however, the location of character user interface object  1102  has been updated. As illustrate in  FIG.  11 C , device  600  displays user interface object  1102  at a location indicating a minute value corresponding to the current time is zero (e.g., 00). 
       FIG.  11 D  illustrates watch user interface  1108  at a current time of 4:30 (e.g., after 30 minutes have elapsed since device  600  displayed watch user interface  1108  as depicted in FIG.  11 C). Device  600  displays an updated digital indication of time  610  reflecting a current time of 4:30. Device  600  updates watch user interface  1108  to display lawn emblem  1102   c  as a “4,” and to display character user interface object  1102  at a location indicating a minute value corresponding to the current time as thirty (e.g., 30). 
     In some embodiments, the current time of day is depicted as an ongoing animation, with each animation frame corresponding to a minute value of the respective hour of day. For example, device  600  updates watch user interface  1108  at every minute, displaying a frame depicting the progress of character user interface object  1102  mowing the lawn (i.e., mowing un-mowed grass  1102   a ).  FIGS.  11 A- 11 D  illustrate exemplary animation frames (e.g.,  FIG.  11 A  illustrates an animation frame corresponding to 30 minutes,  FIG.  11 B  illustrates an animation frame corresponding to 59 minutes, etc.). In some embodiments, the number of frames included in an animation is based in part on a unit of time associated with the position of character user interface object  1102 . For example, as described above in reference to  FIGS.  11 A- 11 D , the position of character user interface object  1102  relates to a minute value of the current hour, thus, a corresponding animation includes 60 frames (e.g., corresponding to each minute within an hour). 
     In some embodiments, device  600  displays an animation in response to the current time being a predetermined time (e.g., the current time is a predetermined amount of time (e.g., one minute) before or after a predetermined time (e.g., 4:00)). In some embodiments, device  600  initiates an animation in response receiving user input (e.g., device  600  receives orientation data from an internal sensor indicating that the user has raised or is raising device  600  into a viewing position, device  600  detects a rotation of rotatable and depressible input mechanism  604 , device  600  detects a depression of button  606 , etc.). 
       FIGS.  12 A- 12 C  are a flow diagram illustrating method  1200  for indicating a current time using an electronic device in accordance with some embodiments. Method  1200  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 ) with a display device (e.g.,  602 ). Some operations in method  1200  are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted. In some embodiments, method  1200  relates to having an animated character move around an outside of a watch face as time progresses while performing actions to indicate time, where actions represent time according to one time unit (e.g., hours) and location represents time according to a different time unit (e.g., minutes). In some embodiments, a dragon moves around the watch face to indicate minute based on the dragon&#39;s location and then the dragon contorting to a number to indicate hour. 
     As described below, method  1200  provides a technique for dynamically modifying a location and appearance of a user interface object based on a current time. The method provides a user with an easily decipherable visual indication that quickly draws the user&#39;s attention to relevant information (e.g., a current hour measured by a device) and/or reduces the cognitive burden on a user for identifying a state of a device (e.g., a current time as measured by a device, thereby creating a more efficient human-machine interface. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to quickly resolve the current time, the user does not need to spend as much time interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more efficiently. 
     At  1202 , the device (e.g.,  600 ) device displays, via the display device (e.g.,  602 ) at a first time (e.g., 10:10), a user interface object (e.g.,  904   a  in  FIG.  9 A,  1010     a  in  FIG.  10 C,  1102     a  in  FIG.  11 A ) (in some embodiments, the user interface object is a character user interface object) (e.g., in some embodiments, the user interface object is a single user interface object) at a first location of the clock face, where the user interface object has a first appearance at the first time. 
     At  1204 , the device displays, via the display device at a second time (e.g., 10:11) different from the first time), the user interface object (e.g.,  904   a  in  FIG.  9 C,  1010     a  in  FIG.  10 D,  1102     a  in  FIG.  11 B ) at a second location of the clock face, where the user interface object has the first appearance at the second time, and where a difference between the first time and the second time is at least one unit (e.g., a minute) according to a first time scale (e.g., minutes). 
     At  1206 , in some embodiments, the device displays, via the display device the user interface object (e.g.,  1010   a  and  1010   b ) for a first amount of time (e.g., 1 minute) after the first time (e.g., 10:10), and displays the user interface object for a second amount of time (e.g., 1 minute) after the second time (e.g., 11:10), where the first location is indicative of a first unit (e.g., 10 when it is 10:12) according to the second time scale (e.g., hours, even though the second time scale is interpreted as minutes above), the second location is indicative of a second unit (e.g., 11 when it is 11:12) according to the second time scale (e.g., hours), the second unit is different from the first unit. 
     At  1208 , in some embodiments, the device ceases to display, via the display device, the user interface object after the first amount of time. 
     At  1210 , in some embodiments, the device ceases to display, via the display device, the user interface object after the second amount of time. 
     At  1212 , in some embodiments, the device displays via the display device an animation of the user interface object (e.g.,  1010   a  and  1010   b ) performing (e.g., a character yawns, stretches, puts on sunglasses, or the like) at a plurality of time boundaries according to the second time scale, the animation at a first time boundary including an activity corresponding to a first time of day at the first time boundary (e.g., in the morning, eating a bowl of cereal, reading a newspaper, or drinking a cup of coffee, etc.), and the animation at second first time boundary that is different from the first time boundary including an activity corresponding to a second time of day that is different from the first time of day at the second time boundary (e.g., in the evening, putting on pajamas or turning off a light switch, etc.). In some embodiments, the character acts out activity corresponding to the time of day switch at an hourly boundary (e.g.,  1010   a  in  FIG.  10 C and  1010     b  in  FIG.  10 E ). 
     In some embodiments, displaying an animation at each time boundary corresponding to the particular time of day provides the user with additional feedback about the current state of the watch (e.g., the current time relative to activities a user normally performs at the time of day corresponding to the respective time boundary). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to quickly resolve the current time, without the need to decipher textual or numerical symbols, the user does not need to spend as much time interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more efficiently. 
     At  1214 , in some embodiments, the device displays via the display device an illustration ( 1010   a  and  1010   b ) that changes as time of day time of day changes. For example, in some embodiments, the animation at the first time boundary is different from the animation at the second time boundary. 
     At  1216 , the device displays, via the display device at a third time (e.g., 11:10) different from each of the second time and the first time, the user interface object (e.g.,  904   b  in  FIG.  9 E,  1010     b  in  FIG.  10 E,  1102     c  in  FIG.  11 C ) at the first location of the clock face, where the user interface object has a second appearance at the third time, where a difference between the first time and the third time is at least one unit (e.g., an hour) according to a second time scale (e.g., hours) (e.g., where the user interface object maintains the representation between the first time and the second time) different from the first time scale. 
     At  1218 , in some embodiments, the device displays via the display device the user interface object performing a first animation at the first time (e.g., the user interface object performs an action that is indicative of the time, such as yawning when it is late or stretching if it is early) and a second animation at the third time (e.g., interacting with an object of a first type at the first location and interacting with a different object of the first type at the second location) (e.g.,  1010   a  in  FIGS.  10 C and  10 D,  1010     b  in  FIGS.  10 F and  10 G ). For example, a character walks around watch face eating items at each number. 
     At  1220 , in some embodiments, the device displays via the display device an animation including a number of frames based on divisions of time) (e.g.,  1108  in  FIGS.  11 A- 11 D ) (e.g., 60 frames for a 60 second animation, 24 frames for a 24 hour animation). For example, in some embodiments, the user interface object performs an animation between the first time and the third time (e.g., a person mowing a lawn or the user interface object transforming from one appearance (e.g., shape, such as a triangle) to another appearance (e.g., a different shape, such as a square)), and where a number of frames of the animation is based on a number of divisions of time according to the second time scale (e.g., when the second time scale is minutes, the number of frames is 60 to correspond to how many minutes are in an hour. 
     In some embodiments, varying the number of frames of a displayed animation based on a time scale provides the user with additional feedback about the current state of the watch (e.g., the current time relative to a specific temporal scale). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to quickly resolve the current time, without the need to decipher textual or numerical symbols, the user does not need to spend as much time interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more efficiently. 
     At  1222 , in some embodiments, the device displays via the display device, a character (e.g.,  904   a  in  FIG.  9 C and  904     b  in  FIG.  9 D ) changing shape to represent a number indicative of the current time at the location (e.g., changing in shape to look like a 3). In some embodiments, the first appearance is indicative of a first unit (e.g., a hand showing 2 fingers or a snake contorted to look like the number 2) according to the second time scale, the second appearance is indicative of a second unit according to the second time scale, and the second unit is different from the first unit. 
     At  1224 , in some embodiments, the device displays, via the display device at a fourth time (e.g., 10:12) different from each of the first time, the second time, and the third time, the user interface object (e.g.,  904   a  in  FIG.  9 B ) at a third location of the clock face different from the first location and the second location, where the user interface object has the first appearance at the fourth time. 
     At  1226 , in some embodiments, the device displays, via the display device, the user interface object (e.g.,  904   a  and  904   b  throughout  FIGS.  9 A- 9 E ) sequentially at a plurality of locations around the clock face where sequential location of the user interface object are shifted in a respective direction from prior locations of the user interface object so that the user interface object appears to move around the clock face in the respective direction. For example, the character runs or climbs around watch face once per minute or once per hour. In some embodiments, the object moves through a plurality of positions as the appearance of the object remains substantially the same (e.g., a dragon stays in the same shape while moving from the 2 to the 3). 
     At  1228 , in some embodiments, the device displays, via the display device the animation (e.g.,  1008  in  FIGS.  10 A- 10 C ) upon user interaction (e.g., wrist raise or tap). For example, the device animates the user interface object (e.g., a character pops out of a hole, a character transforms into another character, or a character eats food or performs some other action) in response to user input. 
     Note that details of the processes described above with respect to method  1200  (e.g.,  FIGS.  12 A- 12 C ) are also applicable in an analogous manner to the methods described above. For example, method  800  optionally includes one or more of the characteristics of the various methods described above with reference to method  1200 . For example, the techniques for modifying the appearance of character user interface objects to illustrate an activity indicative of a time of day (e.g., sleeping) discussed in method  1200  can be used in method  800  to provide an indication of, for example, whether indications of time on a watch user interface correspond to Ante Meridiem (i.e., AM) or Post Meridiem (i.e., PM) time. For brevity, these details are not repeated below. 
     The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated. 
     Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims. 
     As described above, one aspect of the present technology is the gathering and use of data available from various sources provide context-specific user interfaces with improved time indicating functionality. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records relating to a user&#39;s health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information. 
     The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to initiate energy intensive operations, such as displaying animated content, only at times such content will be of great interest to the user. Accordingly, use of such personal information data enables users to have calculated control of device energy usage, which is of great concern in portable battery-operated electronic devices. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user&#39;s general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals. 
     The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country. 
     Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in context-specific user interfaces which indicate time, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In another example, users can select not to provide device orientation data or device usage data for specific purposes, such as targeted content delivery services. In yet another example, users can select to limit the length of time device orientation data or device usage data is maintained or entirely prohibit the development of a baseline device orientation or device usage profile. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app. 
     Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user&#39;s privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods. 
     Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, animation content can be selected and delivered to users only in particular contexts (i.e., while the user is viewing the device) by inferring preferences based on non-personal information data (e.g., settings) 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 device, or publicly available information.

Metadata:
Filing Date: 20200429
Publication Date: 20240416
Grant Date: 20240416
Priority Date: 20190506
Inventors: WILSON, CHRISTOPHER
Assignee: APPLE INC
CPC Classifications: [{"code": "G06F3/0482", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/011", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/017", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04845", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F9/542", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06T13/80", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0488", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/0481", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0484", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/017", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06T13/80", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06T2200/24", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F1/163", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04845", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06T13/80", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/017", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F9/542", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/011", "inventive": true, "first": false, "tree": "[]"}]
Family ID: 73047405