PATENT DOCUMENT

Publication Number: US-10572132-B2
Application Number: US-201815881544-A
Country: US
Kind Code: B2

Title: Formatting content for a reduced-size user interface

Abstract:
The present disclosure generally relates to displaying content on a reduced-size user interface. An electronic device with one or more processors, memory, and a display, receives content associated with a designated area of the display, where the content is associated with a plurality of available display formats stored in the memory. The device determines a size of the designated area and determines a first display format for the content from the plurality of available display formats based on at least the content and the size of the designated area. The device displays a representation of the content according to the first display format.

Claims:
What is claimed is: 
     
       1. An electronic device, comprising:
 a display; 
 one or more processors; 
 a memory; and 
 one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for:
 receiving content; 
 determining a size of a first designated area of the display; 
 determining, for the content, a first display format from a plurality of available display formats based on at least the content and the size of the first designated area, wherein the first display format corresponds to a first amount of abbreviation; 
 abbreviating, according to the first display format, a first portion of the content to produce a first representation of the content; 
 displaying the first representation; 
 determining a size of a second designated area of the display different from the first designated area; 
 determining, for the content, a second display format for the content from the plurality of available display formats based on at least the content and the size of the second designated area, wherein the second display format is different from the first display format and corresponds to a second amount of abbreviation different from the first amount of abbreviation; 
 abbreviating, according to the second display format, a second portion of the content to produce a second representation of the content; and 
 displaying the second representation. 
 
 
     
     
       2. The device of  claim 1 ,
 wherein the content is associated with a display style, and 
 wherein determining the first display format is further based on the display style associated with the content. 
 
     
     
       3. The device of  claim 2 , wherein the display style includes a font associated with the content. 
     
     
       4. The device of  claim 1 ,
 wherein each display format of the plurality of available display formats corresponds to a display size of the content formatted according to the respective display format, and 
 wherein determining the first display format of the content from the plurality of available display formats comprises:
 determining an optimized display format, wherein the optimized display format is determined to be the display format of the plurality of available display formats that corresponds to the largest display size of the display sizes corresponding to the plurality of available display formats that does not exceed the size of the designated area; and 
 determining the first display format to be the optimized display format. 
 
 
     
     
       5. The device of  claim 4 ,
 wherein the plurality of available display formats forms a hierarchy ranked according to the display sizes corresponding to the display formats of the plurality of available display formats, and 
 wherein determining the first display format of the content from the plurality of available display formats further comprises:
 determining whether the optimized display format is below a predetermined lowest allowable display format in the hierarchy; and 
 in accordance with a determination that the optimized display format is below the lowest allowable display format in the hierarchy, determining the first display format to be the lowest allowable display format. 
 
 
     
     
       6. The device of  claim 5 ,
 wherein determining the first display format of the content from the plurality of available display formats further comprises:
 determining whether the optimized display format is above a predetermined highest allowable display format in the hierarchy; and 
 in accordance with a determination that the optimized display format is above the highest allowable display format in the hierarchy, determining the first display format to be the highest allowable display format. 
 
 
     
     
       7. The device of  claim 5 , the one or more programs further including instructions for:
 determining whether the display size corresponding to the first display format exceeds the size of the designated area; and 
 in accordance with a determination that the display size corresponding to the first display format exceeds the size of the designated area, truncating the representation of the content to the size of the designated area. 
 
     
     
       8. The device of  claim 1 , wherein the plurality of available display formats associated with the content is a defined set. 
     
     
       9. The device of  claim 1 , wherein the content represents a point in time, a duration, an offset, or a decimal number. 
     
     
       10. The device of  claim 1 , wherein the content is at least part of data representing a watch face complication. 
     
     
       11. The device of  claim 10 , wherein the complication includes a layout with one or more designated areas including the designated area associated with the content. 
     
     
       12. The device of  claim 11 , wherein the data representing the complication includes second content associated with a second designated area of the one or more designated areas, wherein the second designated area is distinct from the designated area associated with the content. 
     
     
       13. The electronic device of  claim 1 , wherein the first portion describes a property of the content, and wherein the second portion describes the property of the content. 
     
     
       14. The electronic device of  claim 13 , wherein the property is a day or a month. 
     
     
       15. A method, comprising:
 at an electronic device with one or more processors, memory, and a display:
 receiving content; 
 determining a size of a first designated area of the display; 
 determining, for the content, a first display format from a plurality of available display formats based on at least the content and the size of the first designated area, wherein the first display format corresponds to a first amount of abbreviation; 
 abbreviating, according to the first display format, a first portion of the content to produce a first representation of the content; 
 displaying the first representation; 
 determining a size of a second designated area of the display different from the first designated area; 
 determining, for the content, a second display format for the content from the plurality of available display formats based on at least the content and the size of the second designated area, wherein the second display format is different from the first display format and corresponds to a second amount of abbreviation different from the first amount of abbreviation; 
 abbreviating, according to the second display format, a second portion of the content to produce a second representation of the content; and 
 displaying the second representation. 
 
 
     
     
       16. The method of  claim 15 ,
 wherein the content is associated with a display style, and 
 wherein determining the first display format is further based on the display style associated with the content. 
 
     
     
       17. The method of  claim 16 , wherein the display style includes a font associated with the content. 
     
     
       18. The method of  claim 15 ,
 wherein each display format of the plurality of available display formats corresponds to a display size of the content formatted according to the respective display format, and 
 wherein determining the first display format of the content from the plurality of available display formats comprises:
 determining an optimized display format, wherein the optimized display format is determined to be the display format of the plurality of available display formats that corresponds to the largest display size of the display sizes corresponding to the plurality of available display formats that does not exceed the size of the designated area; and 
 determining the first display format to be the optimized display format. 
 
 
     
     
       19. The method of  claim 18 ,
 wherein the plurality of available display formats forms a hierarchy ranked according to the display sizes corresponding to the display formats of the plurality of available display formats, and 
 wherein determining the first display format of the content from the plurality of available display formats further comprises:
 determining whether the optimized display format is below a predetermined lowest allowable display format in the hierarchy; and 
 in accordance with a determination that the optimized display format is below the lowest allowable display format in the hierarchy, determining the first display format to be the lowest allowable display format. 
 
 
     
     
       20. The method of  claim 19 ,
 wherein determining the first display format of the content from the plurality of available display formats further comprises:
 determining whether the optimized display format is above a predetermined highest allowable display format in the hierarchy; and 
 in accordance with a determination that the optimized display format is above the highest allowable display format in the hierarchy, determining the first display format to be the highest allowable display format. 
 
 
     
     
       21. The method of  claim 19 , further comprising:
 determining whether the display size corresponding to the first display format exceeds the size of the designated area; and 
 in accordance with a determination that the display size corresponding to the first display format exceeds the size of the designated area, truncating the representation of the content to the size of the designated area. 
 
     
     
       22. The method of  claim 15 , wherein the plurality of available display formats associated with the content is a defined set. 
     
     
       23. The method of  claim 15 , wherein the content represents a point in time, a duration, an offset, or a decimal number. 
     
     
       24. The method of  claim 15 , wherein the content is at least part of data representing a watch face complication. 
     
     
       25. The method of  claim 24 , wherein the complication includes a layout with one or more designated areas including the designated area associated with the content. 
     
     
       26. The method of  claim 25 , wherein the data representing the complication includes second content associated with a second designated area of the one or more designated areas, wherein the second designated area is distinct from the designated area associated with the content. 
     
     
       27. The method of  claim 15 , wherein the first portion describes a property of the content, and wherein the second portion describes the property of the content. 
     
     
       28. The method of  claim 27 , wherein the property is a day or a month. 
     
     
       29. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and memory, cause the electronic device to:
 receive content; 
 determine a size of a first designated area of the display; 
 determine, for the content, a first display format from a plurality of available display formats based on at least the content and the size of the first designated area, wherein the first display format corresponds to a first amount of abbreviation; 
 abbreviate, according to the first display format, a first portion of the content to produce a first representation of the content; 
 display the first representation; 
 determine a size of a second designated area of the display different from the first designated area; 
 determine, for the content, a second display format for the content from the plurality of available display formats based on at least the content and the size of the second designated area, wherein the second display format is different from the first display format and corresponds to a second amount of abbreviation different from the first amount of abbreviation; 
 abbreviate, according to the second display format, a second portion of the content to produce a second representation of the content; and 
 display the second representation. 
 
     
     
       30. The non-transitory computer-readable storage medium of  claim 29 ,
 wherein the content is associated with a display style, and 
 wherein the instructions further cause the device to determine the first display format is further based on the display style associated with the content. 
 
     
     
       31. The non-transitory computer-readable storage medium of  claim 30 , wherein the display style includes a font associated with the content. 
     
     
       32. The non-transitory computer-readable storage medium of  claim 29 ,
 wherein each display format of the plurality of available display formats corresponds to a display size of the content formatted according to the respective display format, and 
 wherein the instructions further cause the device to determine the first display format of the content from the plurality of available display formats, and wherein the instructions further cause the device to:
 determine an optimized display format, wherein the optimized display format is determined to be the display format of the plurality of available display formats that corresponds to the largest display size of the display sizes corresponding to the plurality of available display formats that does not exceed the size of the designated area; and 
 determine the first display format to be the optimized display format. 
 
 
     
     
       33. The non-transitory computer-readable storage medium of  claim 32 ,
 wherein the plurality of available display formats forms a hierarchy ranked according to the display sizes corresponding to the display formats of the plurality of available display formats, and 
 wherein the instructions further cause the device to determine the first display format of the content from the plurality of available display formats, and wherein the instructions further cause the device to:
 determine whether the optimized display format is below a predetermined lowest allowable display format in the hierarchy; and 
 in accordance with a determination that the optimized display format is below the lowest allowable display format in the hierarchy, determine the first display format to be the lowest allowable display format. 
 
 
     
     
       34. The non-transitory computer-readable storage medium of  claim 33 ,
 wherein the instructions further cause the device to determine the first display format of the content from the plurality of available display formats, and wherein the instructions further cause the device to:
 determine whether the optimized display format is above a predetermined highest allowable display format in the hierarchy; and 
 in accordance with a determination that the optimized display format is above the highest allowable display format in the hierarchy, determine the first display format to be the highest allowable display format. 
 
 
     
     
       35. The non-transitory computer-readable storage medium of  claim 33 , wherein the instructions further cause the device to:
 determine whether the display size corresponding to the first display format exceeds the size of the designated area; and 
 in accordance with a determination that the display size corresponding to the first display format exceeds the size of the designated area, truncate the representation of the content to the size of the designated area. 
 
     
     
       36. The non-transitory computer-readable storage medium of  claim 29 , wherein the plurality of available display formats associated with the content is a defined set. 
     
     
       37. The non-transitory computer-readable storage medium of  claim 29 , wherein the content represents a point in time, a duration, an offset, or a decimal number. 
     
     
       38. The non-transitory computer-readable storage medium of  claim 29 , wherein the content is at least part of data representing a watch face complication. 
     
     
       39. The non-transitory computer-readable storage medium of  claim 38 , wherein the complication includes a layout with one or more designated areas including the designated area associated with the content. 
     
     
       40. The non-transitory computer-readable storage medium of  claim 39 , wherein the data representing the complication includes second content associated with a second designated area of the one or more designated areas, wherein the second designated area is distinct from the designated area associated with the content. 
     
     
       41. The non-transitory computer-readable storage medium of  claim 29 , wherein the first portion describes a property of the content, and wherein the second portion describes the property of the content. 
     
     
       42. The non-transitory computer-readable storage medium of  claim 41 , wherein the property is a day or a month.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of U.S. patent application Ser. No. 14/839,889, filed Aug. 28, 2015, which claims priority to U.S. Provisional Patent Application Ser. No. 62/172,033, filed Jun. 5, 2015. The contents of which are hereby incorporated by reference in their entirety. 
    
    
     FIELD 
     The present disclosure relates generally to computer user interfaces, and more specifically to techniques for formatting content for display on a reduced-size user interface. 
     BACKGROUND 
     Many modern electronic devices, such as smartphones, tablet computers, watches, and the like, include a display that serves as the primary user interface for the device. The size of the display on such devices is often small, which makes it difficult to display significant amounts of content in a discernable, comprehensible, and aesthetically pleasing manner. 
     Some techniques for displaying content on a reduced-size user interface using electronic devices, however, are generally inefficient. For example, some existing techniques do not accommodate different interface sizes. Existing techniques may fail to display key information (e.g., if the size of the content exceeds the size of the display area) or display content in a manner that is difficult to view, making it challenging for a user to interact with the device. 
     In addition, modern devices may accommodate simultaneous display of content from multiple different sources (e.g., different applications), each with a different style, format, color, etc. The lack of a consistent general appearance can result in an interface that is distracting and makes it difficult for a user to process the displayed information. 
     BRIEF SUMMARY 
     In view of the issues discussed above, the present disclosure provides, inter alia, the benefit of electronic devices with more efficient methods and interfaces for displaying content on a reduced-size user interface. Such methods and interfaces optionally complement or replace other methods for displaying content on a reduced-size user interface. Such methods and interfaces may reduce the cognitive burden on a user and produce a more efficient human-machine interface. Such methods and interfaces may also reduce the number of unnecessary, extraneous, repetitive, and/or redundant inputs, and may create a faster and more efficient user interface arrangement, which may reduce the number of required inputs, reduce processing power, and reduce the amount of time for which user interfaces need to be displayed in order for desired functions to be accessed and carried out. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges. 
     The above deficiencies and other problems are reduced or eliminated by the disclosed devices, methods, and computer-readable media. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen” or “touch screen display”). In some embodiments, the device has hardware input mechanisms such as depressible buttons and/or rotatable input mechanisms. In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI through finger contacts and gestures on the touch-sensitive surface and/or through rotating the rotatable input mechanism and/or through depressing hardware buttons. In some embodiments, the functions optionally include image editing, drawing, presenting, word processing, website creating, disk authoring, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music playing, and/or digital video playing. 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 medium or other computer program product configured for execution by one or more processors. 
     In some embodiments, a method is performed at an electronic device with one or more processors, memory, and a display. The method includes: receiving content associated with a designated area of the display, where the content is associated with a plurality of available display formats stored in the memory; determining a size of the designated area; determining a first display format for the content from the plurality of available display formats based on at least the content and the size of the designated area; and displaying a representation of the content according to the first display format. 
     In some embodiments, an electronic device includes a display, one or more processors, a memory, and one or more programs, where the one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for: receiving content associated with a designated area of the display, where the content is associated with a plurality of available display formats stored in the memory; determining a size of the designated area; determining a first display format for the content from the plurality of available display formats based on at least the content and the size of the designated area; and displaying a representation of the content according to the first display format. 
     In some embodiments, a non-transitory computer-readable storage medium stores one or more programs, where the one or more programs include instructions, which when executed by one or more processors of an electronic device with a display, cause the device to: receive content associated with a designated area of the display, where the content is associated with a plurality of available display formats stored in the memory; determine a size of the designated area; determine a first display format for the content from the plurality of available display formats based on at least the content and the size of the designated area; and display a representation of the content according to the first display format. 
     In some embodiments, a transitory computer-readable medium comprises instructions, which when executed by one or more processors of an electronic device with a display, cause the device to: receive content associated with a designated area of the display, where the content is associated with a plurality of available display formats stored in the memory; determine a size of the designated area; determine a first display format for the content from the plurality of available display formats based on at least the content and the size of the designated area; and display a representation of the content according to the first display format. 
     In some embodiments, an electronic device includes: a display; means for receiving content associated with a designated area of the display, where the content is associated with a plurality of available display formats stored in the memory; means for determining a size of the designated area; means for determining a first display format for the content from the plurality of available display formats based on at least the content and the size of the designated area; and means for displaying a representation of the content according to the first display format. 
     In some embodiments, an electronic device includes a display unit configured to display a graphic user interface; and a processing unit coupled to the display unit. The processing unit is configured to: receive content associated with a designated area of the display, where the content is associated with a plurality of available display formats stored in the memory; determine a size of the designated area; determine a first display format for the content from the plurality of available display formats based on at least the content and the size of the designated area; and enable display of a representation of the content according to the first display format. 
     In some embodiments, a method is performed at an electronic device with one or more processors, memory, and a display. The method includes receiving data representing an application and, in response to receiving the data representing the application, loading the application into the memory, where loading the application into the memory includes storing data representing one or more complications associated with the application. A first user interface screen including a clock face is displayed, where the clock face includes one or more complication areas. A first user input is received and, in response to receiving the first user input, a clock face edit mode of the electronic device is entered. While in the clock face edit mode, a second user input is received corresponding to selection of a first complication area of the one or more complication areas and, in response to receiving the second user input corresponding to selection of the first complication area, one or more representations of at least one of the one or more complications associated with the application is displayed, where the one or more representations includes a first representation of a first complication from the at least one of the one or more complications associated with the application and the first complication includes content associated with the first complication. A first display format for the content associated with the first complication is determined. A third user input corresponding to selection of the first representation of the first complication is received and, in response to receiving the third user input, the first complication is associated with the first complication area of the clock face. While in the clock face edit mode, a fourth user input is received and, in response to receiving the fourth user input: the clock face edit mode is exited; and a second user interface screen including the clock face is displayed, where the clock face on the second user interface screen includes the first complication in the first complication area and the first complication includes a representation of the content formatted according to the first display format. 
     In some embodiments, an electronic device includes: a display; one or more processors; a memory; and one or more programs, where the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: receiving data representing an application; in response to receiving the data representing the application, loading the application into the memory, where loading the application into the memory includes storing data representing one or more complications associated with the application; displaying a first user interface screen including a clock face, where the clock face includes one or more complication areas; receiving a first user input; in response to receiving the first user input, entering a clock face edit mode of the electronic device; while in the clock face edit mode, receiving a second user input corresponding to selection of a first complication area of the one or more complication areas; in response to receiving the second user input corresponding to selection of the first complication area, displaying one or more representations of at least one of the one or more complications associated with the application where the one or more representations includes a first representation of a first complication from the at least one of the one or more complications associated with the application, and where the first complication includes content associated with the first complication; determining a first display format for the content associated with the first complication; receiving a third user input corresponding to selection of the first representation of the first complication; in response to receiving the third user input, associating the first complication with the first complication area of the clock face; while in the clock face edit mode, receiving a fourth user input; and in response to receiving the fourth user input: exiting the clock face edit mode; and displaying a second user interface screen including the clock face, where the clock face on the second user interface screen includes the first complication in the first complication area, and where the first complication includes a representation of the content formatted according to the first display format. 
     In some embodiments, a non-transitory computer-readable storage medium stores one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display, cause the device to: receive data representing an application; in response to receiving the data representing the application, load the application into the memory, where loading the application into the memory includes storing data representing one or more complications associated with the application; display a first user interface screen including a clock face, where the clock face includes one or more complication areas; receive a first user input; in response to receiving the first user input, enter a clock face edit mode of the electronic device; while in the clock face edit mode, receive a second user input corresponding to selection of a first complication area of the one or more complication areas; in response to receiving the second user input corresponding to selection of the first complication area, display one or more representations of at least one of the one or more complications associated with the application, where the one or more representations includes a first representation of a first complication from the at least one of the one or more complications associated with the application, and where the first complication includes content associated with the first complication; determine a first display format for the content associated with the first complication; receive a third user input corresponding to selection of the first representation of the first complication; in response to receiving the third user input, associate the first complication with the first complication area of the clock face; while in the clock face edit mode, receiving a fourth user input; and in response to receiving the fourth user input: exit the clock face edit mode; and display a second user interface screen including the clock face, where the clock face on the second user interface screen includes the first complication in the first complication area, and where the first complication includes a representation of the content formatted according to the first display format. 
     In some embodiments, a transitory computer-readable medium comprises instructions, which when executed by one or more processors of an electronic device with a display, cause the device to: receive data representing an application; in response to receiving the data representing the application, load the application into the memory, where loading the application into the memory includes storing data representing one or more complications associated with the application; display a first user interface screen including a clock face, where the clock face includes one or more complication areas; receive a first user input; in response to receiving the first user input, enter a clock face edit mode of the electronic device; while in the clock face edit mode, receive a second user input corresponding to selection of a first complication area of the one or more complication areas; in response to receiving the second user input corresponding to selection of the first complication area, display one or more representations of at least one of the one or more complications associated with the application, where the one or more representations includes a first representation of a first complication from the at least one of the one or more complications associated with the application, and where the first complication includes content associated with the first complication; determine a first display format for the content associated with the first complication; receive a third user input corresponding to selection of the first representation of the first complication; in response to receiving the third user input, associate the first complication with the first complication area of the clock face; while in the clock face edit mode, receiving a fourth user input; and in response to receiving the fourth user input: exit the clock face edit mode; and display a second user interface screen including the clock face, where the clock face on the second user interface screen includes the first complication in the first complication area, and where the first complication includes a representation of the content formatted according to the first display format. 
     In some embodiments, an electronic device includes: a display; means for receiving data representing an application; means for, in response to receiving the data representing the application, loading the application into the memory, where loading the application into the memory includes storing data representing one or more complications associated with the application; means for displaying a first user interface screen including a clock face, where the clock face includes one or more complication areas; means for receiving a first user input; means for, in response to receiving the first user input, entering a clock face edit mode of the electronic device; means for, while in the clock face edit mode, receiving a second user input corresponding to selection of a first complication area of the one or more complication areas; means for, in response to receiving the second user input corresponding to selection of the first complication area, displaying one or more representations of at least one of the one or more complications associated with the application, where the one or more representations includes a first representation of a first complication from the at least one of the one or more complications associated with the application, and where the first complication includes content associated with the first complication; means for determining a first display format for the content associated with the first complication; means for receiving a third user input corresponding to selection of the first representation of the first complication; means for, in response to receiving the third user input, associating the first complication with the first complication area of the clock face; means for, while in the clock face edit mode, receiving a fourth user input; and means for, in response to receiving the fourth user input: exiting the clock face edit mode; and displaying a second user interface screen including the clock face, where the clock face on the second user interface screen includes the first complication in the first complication area, and where the first complication includes a representation of the content formatted according to the first display format. 
     In some embodiments, an electronic device includes: a display unit configured to display a graphic user interface; and a processing unit coupled to the display unit, the processing unit configured to: receive data representing an application; in response to receiving the data representing the application, load the application into the memory, where loading the application into the memory includes storing data representing one or more complications associated with the application; enable display of a first user interface screen including a clock face, where the clock face includes one or more complication areas; receive a first user input; in response to receiving the first user input, enter a clock face edit mode of the electronic device; while in the clock face edit mode, receive a second user input corresponding to selection of a first complication area of the one or more complication areas; in response to receiving the second user input corresponding to selection of the first complication area, enable display of one or more representations of at least one of the one or more complications associated with the application, where the one or more representations includes a first representation of a first complication from the at least one of the one or more complications associated with the application, and where the first complication includes content associated with the first complication; determine a first display format for the content associated with the first complication; receive a third user input corresponding to selection of the first representation of the first complication; in response to receiving the third user input, associate the first complication with the first complication area of the clock face; while in the clock face edit mode, receiving a fourth user input; and in response to receiving the fourth user input: exit the clock face edit mode; and enable display of a second user interface screen including the clock face, where the clock face on the second user interface screen includes the first complication in the first complication area, and where the first complication includes a representation of the content formatted according to the first display format. 
     Thus, devices are provided with faster, more efficient methods and interfaces for displaying content on a reduced-size display, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for displaying content on a reduced-size display. 
    
    
     
       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. 1A  is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments. 
         FIG. 1B  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. 4A  illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments. 
         FIG. 4B  illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments. 
         FIG. 5A  illustrates a personal electronic device in accordance with some embodiments. 
         FIG. 5B  is a block diagram illustrating a personal electronic device in accordance with some embodiments. 
         FIGS. 6A and 6F-6I  illustrate exemplary user interfaces in accordance with some embodiments. 
         FIGS. 6B-6E  illustrate exemplary display formats in accordance with some embodiments. 
         FIG. 7  is a flow diagram illustrating a method for operating an electronic device in accordance with some embodiments. 
         FIG. 8  shows an exemplary functional block diagram of an electronic device in accordance with some embodiments. 
         FIGS. 9A-9G  illustrate exemplary user interfaces in accordance with some embodiments. 
         FIGS. 10A-10B  are a flow diagram illustrating a method for operating an electronic device in accordance with some embodiments. 
         FIG. 11  shows an exemplary functional block diagram of an electronic device 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. 
     The present disclosure provides, inter alia, the benefit of electronic devices with efficient methods and techniques for displaying content on a reduced-size user interface. For example, a method may automatically adjust the format of content in a designated area of a display according to one of several established formats. Such a technique can thereby create a more efficient user interface that provides information in a more consistent and comprehensible manner. Also, for content provided by third parties, the methods described below may display, in a consistent and comprehensible format, content that has not been specifically designed for a particular display. 
     Below,  FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B  provide a description of exemplary devices for displaying content on a reduced-size user interface. Exemplary user interfaces for displaying content on a reduced-size display are described with reference to  FIGS. 6A-6I and 9A-8G .  FIGS. 7 and 10  are flow diagrams illustrating methods of displaying content on a reduced-size user interface in accordance with some embodiments. The user interfaces and display formats in  FIGS. 6A-6I and 9A-8G  are used to illustrate the processes described below, including the processes in  FIGS. 7 and 10 . 
     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” may be 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” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context. 
     Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad). 
     In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick. 
     The device may support 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. 1A  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. 1A  are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application-specific integrated circuits. 
     Memory  102  may include one or more computer-readable storage mediums. The computer-readable storage mediums may be tangible and non-transitory. Memory  102  may include high-speed random access memory and may also include 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  may control 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  may be implemented on a single chip, such as chip  104 . In some other embodiments, they may be 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 may be retrieved from and/or transmitted to memory  102  and/or RF circuitry  108  by peripherals interface  118 . In some embodiments, audio circuitry  110  also includes a headset jack (e.g.,  212 ,  FIG. 2 ). The headset jack provides an interface between audio circuitry  110  and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone). 
     I/O subsystem  106  couples input/output peripherals on device  100 , such as touch screen  112  and other input control devices  116 , to peripherals interface  118 . I/O subsystem  106  optionally includes display controller  156 , optical sensor controller  158 , intensity sensor controller  159 , haptic feedback controller  161 , and one or more input controllers  160  for other input or control devices. The one or more input controllers  160  receive/send electrical signals from/to other input control devices  116 . The other input control devices  116  optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s)  160  are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g.,  208 ,  FIG. 2 ) optionally include an up/down button for volume control of speaker  111  and/or microphone  113 . The one or more buttons optionally include a push button (e.g.,  206 ,  FIG. 2 ). 
     A quick press of the push button may disengage a lock of touch screen  112  or begin 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 ) may turn power to device  100  on or off. The user may be able to customize a functionality of one or more of the buttons. 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 may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond 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  may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen  112  and display controller  156  may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen  112 . In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif. 
     A touch-sensitive display in some embodiments of touch screen  112  may be 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  may be as 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  may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make 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  may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be 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  may include 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  may also include one or more optical sensors  164 .  FIG. 1A  shows an optical sensor coupled to optical sensor controller  158  in I/O subsystem  106 . Optical sensor  164  may include 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  may capture 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 may be used 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 may be 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  may be used along with the touch screen display for both video conferencing and still and/or video image acquisition. 
     Device  100  optionally also includes one or more contact intensity sensors  165 .  FIG. 1A  shows a contact intensity sensor coupled to intensity sensor controller  159  in I/O subsystem  106 . Contact intensity sensor  165  optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor  165  receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some 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  may also include one or more proximity sensors  166 .  FIG. 1A  shows proximity sensor  166  coupled to peripherals interface  118 . Alternately, proximity sensor  166  may be coupled to input controller  160  in I/O subsystem  106 . Proximity sensor  166  may perform 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. 1A  shows a tactile output generator coupled to haptic feedback controller  161  in I/O subsystem  106 . Tactile output generator  167  optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device). Contact intensity sensor  165  receives tactile feedback generation instructions from haptic feedback module  133  and generates tactile outputs on device  100  that are capable of being sensed by a user of device  100 . In some 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  may also include one or more accelerometers  168 .  FIG. 1A  shows accelerometer  168  coupled to peripherals interface  118 . Alternately, accelerometer  168  may be coupled to an input controller  160  in I/O subsystem  106 . Accelerometer  168  may perform as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device  100  optionally includes, in addition to accelerometer(s)  168 , a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device  100 . 
     In some embodiments, the software components stored in memory  102  include operating system  126 , communication module (or set of instructions)  128 , contact/motion module (or set of instructions)  130 , graphics module (or set of instructions)  132 , text input module (or set of instructions)  134 , Global Positioning System (GPS) module (or set of instructions)  135 , and applications (or sets of instructions)  136 . Furthermore, in some embodiments, memory  102  ( FIG. 1A ) or  370  ( FIG. 3 ) stores device/global internal state  157 , as shown in  FIGS. 1A and 3 . Device/global internal state  157  includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display  112 ; sensor state, including information obtained from the device&#39;s various sensors and input control devices  116 ; and location information concerning the device&#39;s location and/or attitude. 
     Operating system  126  (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components. 
     Communication module  128  facilitates communication with other devices over one or more external ports  124  and also includes various software components for handling data received by RF circuitry  108  and/or external port  124 . External port  124  (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some 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 may be 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  may 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 may 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 may be 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  may be 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  may be 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 may use 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 XIVIPP, 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 may 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 may be 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  may be 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  may be 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 may be combined or otherwise rearranged in various embodiments. For example, video player module may be combined with music player module into a single module (e.g., video and music player module  152 ,  FIG. 1A ). In some embodiments, memory  102  may store a subset of the modules and data structures identified above. Furthermore, memory  102  may store 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  may be 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. 1B  is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory  102  ( FIG. 1A ) or  370  ( FIG. 3 ) includes event sorter  170  (e.g., in operating system  126 ) and a respective application  136 - 1  (e.g., any of the aforementioned applications  137 - 151 ,  155 ,  380 - 390 ). 
     Event sorter  170  receives event information and determines the application  136 - 1  and application view  191  of application  136 - 1  to which to deliver the event information. Event sorter  170  includes event monitor  171  and event dispatcher module  174 . In some 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 may 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 may be called the hit view, and the set of events that are recognized as proper inputs may be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture. 
     Hit view determination module  172  receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module  172  identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module  172 , the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view. 
     Active event recognizer determination module  173  determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module  173  determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module  173  determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views. 
     Event dispatcher module  174  dispatches the event information to an event recognizer (e.g., event recognizer  180 ). In embodiments including active event recognizer determination module  173 , event dispatcher module  174  delivers the event information to an event recognizer determined by active event recognizer determination module  173 . In some embodiments, event dispatcher module  174  stores in an event queue the event information, which is retrieved by a respective event receiver  182 . 
     In some embodiments, operating system  126  includes event sorter  170 . Alternatively, application  136 - 1  includes event sorter  170 . In yet other embodiments, event sorter  170  is a stand-alone module, or a part of another module stored in memory  102 , such as contact/motion module  130 . 
     In some embodiments, application  136 - 1  includes a plurality of event handlers  190  and one or more application views  191 , each of which includes instructions for handling touch events that occur within a respective view of the application&#39;s user interface. Each application view  191  of the application  136 - 1  includes one or more event recognizers  180 . Typically, a respective application view  191  includes a plurality of event recognizers  180 . In other embodiments, one or more of event recognizers  180  are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application  136 - 1  inherits methods and other properties. In some embodiments, a respective event handler  190  includes one or more of: data updater  176 , object updater  177 , GUI updater  178 , and/or event data  179  received from event sorter  170 . Event handler  190  may utilize or call 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 may 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 may also include 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 may 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  may also include one or more physical buttons, such as “home” or menu button  204 . As described previously, menu button  204  may be used to navigate to any application  136  in a set of applications that may be 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. 1A ), sensors  359  (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s)  165  described above with reference to  FIG. 1A ). Memory  370  includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory  370  optionally includes one or more storage devices remotely located from CPU(s)  310 . In some 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. 1A ), or a subset thereof. Furthermore, memory  370  optionally stores additional programs, modules, and data structures not present in memory  102  of portable multifunction device  100 . For example, memory  370  of device  300  optionally stores drawing module  380 , presentation module  382 , word processing module  384 , website creation module  386 , disk authoring module  388 , and/or spreadsheet module  390 , while memory  102  of portable multifunction device  100  ( FIG. 1A ) optionally does not store these modules. 
     Each of the above-identified elements in  FIG. 3  may be 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 may be combined or otherwise rearranged in various embodiments. In some embodiments, memory  370  may store a subset of the modules and data structures identified above. Furthermore, memory  370  may store additional modules and data structures not described above. 
     Attention is now directed towards embodiments of user interfaces that may be implemented on, for example, portable multifunction device  100 . 
       FIG. 4A  illustrates an exemplary user interface for a menu of applications on portable multifunction device  100  in accordance with some embodiments. Similar user interfaces may be 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. 4A  are merely exemplary. For example, icon  422  for video and music player module  152  may optionally be 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. 4B  illustrates an exemplary user interface on a device (e.g., device  300 ,  FIG. 3 ) with a touch-sensitive surface  451  (e.g., a tablet or touchpad  355 ,  FIG. 3 ) that is separate from the display  450  (e.g., touch screen display  112 ). Device  300  also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors  357 ) for detecting intensity of contacts on touch-sensitive surface  451  and/or one or more tactile output generators  359  for generating tactile outputs for a user of device  300 . 
     Although some of the examples which 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. 4B . In some embodiments, the touch-sensitive surface (e.g.,  451  in  FIG. 4B ) has a primary axis (e.g.,  452  in  FIG. 4B ) that corresponds to a primary axis (e.g.,  453  in  FIG. 4B ) on the display (e.g.,  450 ). In accordance with these embodiments, the device detects contacts (e.g.,  460  and  462  in  FIG. 4B ) with the touch-sensitive surface  451  at locations that correspond to respective locations on the display (e.g., in  FIG. 4B, 460  corresponds to  468  and  462  corresponds to  470 ). In this way, user inputs (e.g., contacts  460  and  462 , and movements thereof) detected by the device on the touch-sensitive surface (e.g.,  451  in  FIG. 4B ) are used by the device to manipulate the user interface on the display (e.g.,  450  in  FIG. 4B ) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein. 
     Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some 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. 5A  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. 1A-4B ). 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) may have 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 . 
     Techniques for detecting and processing touch intensity may be 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, 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, 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 may permit device  500  to be worn by a user. 
       FIG. 5B  depicts exemplary personal electronic device  500 . In some embodiments, device  500  can include some or all of the components described with respect to  FIGS. 1A, 1B , and  3 . Device  500  has bus  512  that operatively couples I/O section  514  with one or more computer processors  516  and memory  518 . I/O section  514  can be connected to display  504 , which can have touch-sensitive component  522  and, optionally, touch-intensity sensitive component  524 . 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  may be a rotatable input device or a depressible and rotatable input device, for example. Input mechanism  508  may be a button, in some examples. 
     Input mechanism  508  may be a microphone, in some examples. Personal electronic device  500  can include various sensors, such as GPS sensor  532 , accelerometer  534 , directional sensor  540  (e.g., compass), gyroscope  536 , motion sensor  538 , and/or a combination thereof, all of which can be operatively connected to I/O section  514 . 
     Memory  518  of personal electronic device  500  can be a non-transitory computer-readable storage medium, for storing computer-executable instructions, which, when executed by one or more computer processors  516 , for example, can cause the computer processors to perform the techniques described above, including processes  700  and  1000  ( FIGS. 7 and 10A-10B ). The computer-executable instructions can also be stored and/or transported within any non-transitory computer-readable storage medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For purposes of this document, a “non-transitory computer-readable storage medium” can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device  500  is not limited to the components and configuration of  FIG. 5B , but can include other or additional components in multiple configurations. 
     As used here, the term “affordance” refers to a user-interactive graphical user interface object that may be displayed on the display screen of devices  100 ,  300 , and/or  500  ( FIGS. 1, 3, and 5 ). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) may each constitute an affordance. 
     As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad  355  in  FIG. 3  or touch-sensitive surface  451  in  FIG. 4B ) while the cursor is over a particular user interface element (e.g., a button, window, slider or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system  112  in  FIG. 1A  or touch screen  112  in  FIG. 4A ) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user&#39;s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device). 
     As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some 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 may include 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 may receive 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 may be 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 may be 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 may be characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures. 
     An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero. 
     In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input). 
     In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances). 
     For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. 
     As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices  100 ,  300 , and/or  500 ) and is ready to be launched (e.g., become opened) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system. 
     Attention is now directed towards embodiments of user interfaces and associated processes that may be implemented on an electronic device, such as portable multifunction device  100 , device  300 , or device  500 . 
       FIGS. 6A-6I  illustrate exemplary user interfaces and techniques for displaying content on a reduced-size user interface, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIG. 7 . 
       FIG. 6A  illustrates an exemplary electronic device  600  including a display  602  and rotatable input mechanism  604 . In some embodiments, device  600  is portable multifunction device  100 , device  300 , or device  500 . In  FIG. 6A , graphical interface  606  is displayed on display  602 . Graphical user interface  606  represents a watch face that includes a graphical interface object  608  indicating the time and a representation of content  610 . In some embodiments, content  610  is at least part of data representing a watch face complication. As used here, consistent with its accepted meaning in the art, a complication refers to any watch or clock face feature other than those used to indicate the hours and minutes of a time (e.g., clock hands or hour/minute indications). In the embodiment depicted in  FIG. 6A , content  610  includes date information, including the day of the week, month, day of the month, and year. 
     Although the following examples are described with reference to a watch face  602  of electronic device  600 , it should be recognized, that the techniques for displaying content described herein may be applied to various other graphical display interfaces and applications provided on an electronic device (e.g., in a graphical user interface of an application or a home screen for an operating system). 
     In some embodiments, device  600  receives content  610  from local memory or an application running on device  600 . In some embodiments, device  600  receives content  610  from an application running on a remote device (e.g., an Internet server or a companion device connected to device  600  via, for example, a short-range communication link such as near-field communication (NFC) or Bluetooth). 
     Content  610  is associated with a designated area  612  on graphical interface  602  indicated by the dashed outline. In some embodiments, designated area  612  is at least a portion of a “style window”. A “style window” can correspond to a part of a watch face that is designated to display a complication. In some embodiments, a user can configure a watch face by determining which data (e.g., by selecting a watch application) is to be displayed in a particular style window. Optionally, the content  610  associated with an area is designated by a user, as described in exemplary embodiments later on. In  FIG. 6A , content  610  is displayed in a format in which the day of the week (Saturday) and the month (November) are completely spelled out without abbreviation. 
     In some embodiments, content  610  is associated with a plurality of available display formats. In some embodiments, the plurality of available display formats is pre-defined and stored in the memory of device  600 .  FIG. 6B  illustrates an exemplary set  614  of available display formats  615 - 620  for content  610 . As can be seen, set  614  includes six available display formats that include various amounts of content  610  with various amounts of abbreviation. For example, display format  619  indicates the month and day of the month, whereas display format  620  only indicated the day of the month. In some embodiments, the available display formats associated with content  610  is a defined set. 
     In some embodiments, device  600  determines the type of data (“data type”) represented by content  610 , determines a set of available display formats based on the data type, and associates content  610  with the determined set. For example, device  600  optionally determines that content  610  includes date information, determines a set of available display formats for date information (e.g., set  614  including date display formats  615 - 620 ), and associates the set with content  610 . In some embodiments, a data type and/or set of available display formats associated with content  610  are pre-determined, pre-loaded, and simply received from memory. Exemplary data types include, but are not limited to, a point in time (e.g., a date, a time, or a date and time (a “date/time”)), a duration (e.g., a start date/time and an end date/time), an offset (e.g., a countdown to a point in time expressed in, for example, years, months, weeks, days, hours, minutes, seconds, or some combination thereof), and a decimal number. Set  614  is an exemplary set of available display formats for a point in time;  FIG. 6C  depicts an exemplary set of available display formats for a duration;  FIG. 6D  depicts an exemplary set of available display formats for an offset; and  FIG. 6E  depicts an exemplary set of available display formats for a decimal number. 
     Device  600  determines a particular display format from the set of display formats  615 - 620  to use for displaying content  610 . In some embodiments, device  600  determines or selects the particular display format based at least in part on content  610  itself (e.g., the information represented by content  610 ) and/or the size of the area in which content  610  is to be displayed (e.g., designated area  612 ). In some embodiments, aspects of content  610 , including the data type represented by content  610  or the information represented by content  610  (e.g., the specific date), are used to determine the particular display format. In some embodiments, device  600  either determines the size of designated area  612  or receives the size from local or remote memory. Optionally, device  600  determines the size of designated area  612  based on the physical dimensions of display  602 . The size of designated area  612  may be represented in terms of, for example, an absolute size (e.g., 2 cm), a number of pixels on display  602 , or a fraction of a physical dimension of display  602  (e.g., one half the width of display  602 ). Once the particular display format is determined, device  600  displays a representation of content  610  according to the determined display format. 
     In some embodiments, device  600  determines the display format with the least amount of abbreviation that does not exceed the size of designated area  612 . That is, device determines the largest display format that will completely fit in designated area  612 . In this way, device  600  may automatically maximize the amount of content  610  that is displayed. 
     In some embodiments, display formats  615 - 620  correspond to display sizes of content  610  formatted according to the respective display format. That is, the display size of a particular display format is the amount of space occupied by content  610  when displayed according to the particular display format. 
     In  FIG. 6B , for example, the horizontal extents of display formats  615 - 620  decrease from the top of the list to the bottom of the list. It should be recognized, however, that in some embodiments the size is measured in the vertical direction, horizontal direction, diagonal direction, or some combination thereof. 
     It should also be recognized that the display size of a display format can depend on the information represented by content  610 . Date information of a point in time, for example, can include the specific date. Accordingly, a single display format including the day of the week, month, day of the month, and year can have different display sizes depending on the actual date. For example, Saturday, Nov. 7, 2015 is larger than Friday, May 1, 2015. 
     In some embodiments, the display size of a display format can depend on a display style associated with content  610 . Exemplary aspects of a display style for text include font (e.g., Times New Roman) and font size (e.g., 12 pt.). A display style can be associated directly with content  610  or with a display format (e.g., display formats  615 - 620 ) associated with content  610 . Accordingly, a display format can have different display sizes depending on the style associated with content  610  or the display format in which it is displayed. For the purposes of this disclosure, display style includes aspects affecting aesthetic appearance, but does not include the amount of abbreviation or structure of displayed content, which are considered aspects of the display format. 
     In some embodiments, device  600  may determine the display size for each display format  615 - 620  based on the information represented by content  610  and a display style associated with content  610 . Similar to the size of designated area  612 , in some embodiments, device  600  determines the display size of a display format based on the physical dimensions of display  602 . A display size may be represented in terms of, for example, an absolute size (e.g., 2 cm), a number of pixels on display  602 , or a fraction of a physical dimension of display  602  (e.g., one half the width of display  602 ). 
     In some embodiments, determining the particular display format of content  610  includes determining an optimized display format. As used here, the optimized display format is the display format of set  614  having the largest display size that does not exceed the size of the designated area  612 . The particular display format is then determined to be the optimized display format such that the content is displayed according to the optimized display format. 
       FIG. 6F  illustrates an exemplary graphical interface in which content  610  is displayed according to an optimal display format. In  FIG. 6F , device  600  displays graphical interface  630  representing a watch face that includes graphical interface object  608  indicating the time, a representation  632  indicating the current weather in a designated area  634 , and a designated area  636  for content  610 . Compared to designated area  612  in graphical interface  604  depicted in  FIG. 6A , designated area  636  is circular and has a smaller horizontal extent. Based on the characteristics of content  610  and the size of designated area  636 , device  600  determines the optimal display format from set  614 . Notably, display formats  615 - 618  are too big to fit in designated area  636 . Display format  619 , November 7, is the largest format that will completely fit. Display format  620 , which only includes the day of the month, 7, also completely fits in designated area  636  but does not maximize the amount of information displayed (e.g., it does not include an indication of the month, November). 
     In some embodiments, the display format is determined based on the information represented by content  610 . As noted above, the information of date data, for example, can include the specific date, which can affect the size of a display format. 
       FIGS. 6G-6H  illustrate an example in which different dates result in use of different display formats.  FIG. 6G  depicts an exemplary graphical interface in which content  610  is displayed in designated area  638 . As shown, display format  617  (abbreviated day, abbreviated month, day of the month, and year) is the largest format that completely fits in designated area  638 . In  FIG. 6G , content  610  includes the same amount of information as content  610  (i.e., day of the week, month, day of the month, and year) but because of the particular date, a different display format (e.g., display format  615 , without any abbreviation) is used. 
     As noted above, a display style associated with the content can affect the size of a display format. Accordingly, in some embodiments, the display format is determined based at least in part on the display style associated with the content. For example, content associated with larger font may result in use of a display format with more abbreviation (e.g., Sat. instead of Saturday) or less content (e.g., “November 7” instead of “Nov. 7, 2015”). 
     In some embodiments, a plurality of available display formats forms a hierarchy ranked according to display size. Set  614  of available display formats  615 - 620  for content  610 , for example, forms a hierarch ranked in descending order from top to bottom according to display size. The largest display format  615  (e.g., most amount of information and least amount of abbreviation) is at the top of the hierarchy, and the smallest display format  620  (e.g., least amount of information and greatest amount of abbreviation) is at the bottom. 
     In some embodiments, only a portion of the display formats in set  614  are available. Optionally, only the display formats at or above a predetermined lowest threshold level of the hierarchy are available. In set  614 , for example, the lowest threshold level sets a minimum amount of content included in the display format and/or the greatest amount of abbreviation that is permitted. Optionally, only the display formats at or below a predetermined highest threshold level of the hierarchy are available. In set  614 , for example, the highest threshold level sets a maximum amount of content included in the display format and/or the least amount of abbreviation that is permitted. Optionally, only the display formats at or between a predetermined highest threshold level and a predetermined lowest threshold level of the hierarchy are available. 
     In some embodiments, the display format corresponding to a predetermined highest threshold level (e.g., maximum amount of content and/or least amount of abbreviation) is selected even though a display format higher in the hierarchy (e.g., a longer format) fits in the designated area for the content. In some embodiments, device  600  determines whether the optimized display format (e.g., the largest format that fits in a designated area) is above a predetermined highest allowable display format in the hierarchy (e.g., a predetermined highest threshold level). In accordance with a determination that the optimized display format is above the highest allowable display format in the hierarchy, device  600  determines the particular display format to be the highest allowable display format. 
     In some embodiments, the display format corresponding to a predetermined lowest threshold level (e.g., minimum amount of content and/or greatest amount of abbreviation) is selected even though it does not completely fit in the designated area (e.g., a display format lower in the hierarchy fits is required for the content to fit in the designated area). In some embodiments, device  600  determines whether the optimized display format (e.g., the largest format that fits in the designated area) is below a predetermined lowest allowable display format in the hierarchy (e.g., a predetermined lowest threshold level). In accordance with a determination that the optimized display format is below the lowest allowable display format in the hierarchy, device  600  determines the particular display format to be the lowest allowable display format. 
     Accordingly, in some embodiments, it is possible that the lowest allowable display format does not fit in the designated area. One potential option for dealing with this issue is to truncate the display of content  610  to the size of the designated area. In some embodiments, device  600  determines whether the display size corresponding to the determined display format exceeds the size of the designated area. In accordance with a determination that the display size corresponding to the selected display format exceeds the size of the designated area, the displayed representation of the content is truncated to the size of the designated area (e.g., the portion on the right side of the displayed format that does not fit in the designated area is not displayed). 
     In some embodiments, the designated area is included as part of a layout of a complication, which may include more than one area designated for the display of content. For example, in some embodiments, a watch face complication includes a layout with one or more designated areas for content. Optionally, the complication includes at least two designated areas, where the first designated areas is associated with first content and the second designated area is associated with different content. In some embodiments, the layout is defined by a “template”. “Templates” can be defined for “style windows.” A style window can have one or more templates, with each template specifying data to be displayed in a different manner. Different data can also be displayed, or the same data, but displayed in a different manner. 
       FIG. 6I  illustrates an exemplary watch face  642  including complication  644  associated generally with an upcoming event (e.g., a marathon or other running event). Complication  644  is located at complication area  652  and has a layout with three distinct designated areas: area  646  includes an image representative of the upcoming event, area  648  includes a countdown until the event, and area  650  includes the date of the event. In some embodiments, the display format for the content in one or more of the designated areas is determined in accordance with the techniques described above. 
       FIG. 7  is a flow diagram illustrating a method for displaying content on a reduced-size user interface using an electronic device in accordance with some embodiments. Method  700  is performed at a device (e.g.,  100 ,  300 ,  500 ,  600 ) with a display. Some operations in method  700  may be combined, the order of some operations may be changed, and some operations may be omitted. 
     As described below, method  700  provides an efficient way for displaying content on a reduced-size user interface. The method automatically adjusts the format of content in a designated area of a display according to an established format, thereby creating a more efficient user interface that provides information in a more consistent and comprehensible manner. Accordingly, method  700  may reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, the method may conserve power and increase the time between battery charges. 
     At block  702 , the device receives content (e.g., content  610 ) associated with a designated area (e.g., designated area  612 ) of the display, where the content is associated with a plurality of available display formats (e.g., display formats  615 - 620 ) stored in the memory. At block  704 , the device determines a size of the designated area. At block  706 , the device determines a first display format for the content from the plurality of available display formats based on at least the content and the size of the designated area. At block  708 , the device displays a representation of the content according to the first display format. 
     Note that details of the processes described below with respect to method  1000  (e.g.,  FIGS. 10A-10B ) are also applicable in an analogous manner to method  700 . For example, method  700  may include one or more of the characteristics of the various methods described below with reference to method  10000 . 
     In accordance with some embodiments,  FIG. 8  shows an exemplary functional block diagram of an electronic device  800  configured in accordance with the principles of the various described embodiments. In accordance with some embodiments, the functional blocks of electronic device  800  are configured to perform the techniques described above. The functional blocks of the device  800  are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG. 8  are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG. 8 , an electronic device  800  includes a memory unit  802 , a display unit  804  configured to display a graphic user interface, optionally, a touch-sensitive surface unit  806  configured to receive contacts, and a processing unit  808  coupled to the memory unit  802 , display unit  804 , and, optionally, the touch-sensitive surface unit  806 . In some embodiments, the processing unit  808  includes a receiving unit  810 , a determining unit  812 , and a display enabling unit  814 . 
     The processing unit  808  is configured to receive (e.g., with receiving unit  810 ) content associated with a designated area of the display, where the content is associated with a plurality of available display formats stored in memory unit  802 . Processing unit  808  is further configured to determine (e.g., with determining unit  812 ) a size of the designated area, determine (e.g., with determining unit  812 ) a first display format for the content from the plurality of available display formats based on at least the content and the size of the designated area, and enable (e.g., with display enabling unit  814 ) display of a representation of the content according to the first display format. 
     In some embodiments, the content is associated with a display style and determining the first display format is further based on the display style associated with the content. In some embodiments, the display style includes a font associated with the content. 
     In some embodiments, each display format of the plurality of available display formats corresponds to a display size of the content formatted according to the respective display format and determining the first display format of the content from the plurality of available display formats comprises: determining (e.g., with determining unit  812 ) an optimized display format, where the optimized display format is determined to be the display format of the plurality of available display formats that corresponds to the largest display size of the display sizes corresponding to the plurality of available display formats that does not exceed the size of the designated area; and determining (e.g., with determining unit  812 ) the first display format to be the optimized display format. 
     In some embodiments, the plurality of available display formats forms a hierarchy ranked according to the display sizes corresponding to the display formats of the plurality of available display formats and determining the first display format of the content from the plurality of available display formats further comprises: determining (e.g., with determining unit  812 ) whether the optimized display format is below a predetermined lowest allowable display format in the hierarchy; and in accordance with a determination that the optimized display format is below the lowest allowable display format in the hierarchy, determining (e.g., with determining unit  812 ) the first display format to be the lowest allowable display format. 
     In some embodiments, determining the first display format of the content from the plurality of available display formats further comprises: determining (e.g., with determining unit  812 ) whether the optimized display format is above a predetermined highest allowable display format in the hierarchy; and in accordance with a determination that the optimized display format is above the highest allowable display format in the hierarchy, determining (e.g., with determining unit  812 ) the first display format to be the lowest allowable display format. 
     In some embodiments, the processing unit  808  is further configured to determine (e.g., with determining unit  812 ) whether the display size corresponding to the first display format exceeds the size of the designated area and, in accordance with a determination that the display size corresponding to the first display format exceeds the size of the designated area, truncate (e.g., with display enabling unit  814 ) the representation of the content to the size of the designated area. 
     In some embodiments, the plurality of available display formats associated with the content is a defined set. In some embodiments, the content represents a point in time, a duration, an offset, or a decimal number. 
     In some embodiments, the content is at least part of data representing a watch face complication. In some embodiments, the complication includes a layout with one or more designated areas including the designated area associated with the content. In some embodiments, the data representing the complication includes second content associated with a second designated area of the one or more designated areas, where the second designated area is distinct from the designated area associated with the content. 
     The operations described above with reference to  FIG. 7  are, optionally, implemented by components depicted in  FIGS. 1A-1B  or  FIG. 8 . For example, receiving operation  702 , determining operations  704  and  706 , and displaying operation  708  may be implemented by event sorter  170 , event recognizer  180 , and event handler  190 . Event monitor  171  in event sorter  170  detects a contact on touch-sensitive display  112 , and event dispatcher module  174  delivers the event information to application  136 - 1 . A respective event recognizer  180  of application  136 - 1  compares the event information to respective event definitions  186 , and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub event, such as activation of an affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer  180  activates an event handler  190  associated with the detection of the event or sub-event. Event handler  190  may utilize or call data updater  176  or object updater  177  to update the application internal state  192 . In some embodiments, event handler  190  accesses a respective GUI updater  178  to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in  FIGS. 1A-1B . 
       FIGS. 9A-9G  illustrate exemplary techniques for displaying a complication provided by an application.  FIG. 9A  depicts electronic device  900  with display  902  and rotatable input mechanism  904 . User interface  906  representing a clock face is displayed on display  902 . The face includes an indication of the current time  908  and three complications: weather complication  910  displaying weather information, battery life complication  912  displaying the amount of battery life remaining for electronic device  900 , and complication  914  displaying date information. Each complication is associated with an area of the display, referred to as a complication area. 
     In some embodiments, device  900  receives data representing one or more applications. The received data may include data representing one or more complications associated with the applications. The applications can include applications developed and/or made available by a party other than the manufacturer of device  900  (e.g., a third party). Exemplary applications include applications that provide information from Twitter, Facebook, or a sports information source (e.g., MLB.com or Yahoo Sports). In some embodiments, the data representing the application is received from an Internet server or a companion device connected to device  900  via, for example, a short-range communication link such as NFC or Bluetooth. In some embodiments, the data representing the application, including complications associated with the application, are received when a companion application is downloaded on a companion device in accordance with various techniques. 
     In response to receiving the data representing the application, device  900  can load the application into local memory and, optionally, store data representing one or more complications associated with the applications. 
     As indicated in  FIG. 9A , device  900  receives an input. Specifically, device  900  receives a contact on the display caused by user touch  916 . Although a touch input is shown in the illustrated embodiment, it should be recognized that various other methods or types of input may be possible. In some embodiments, electronic device  900  is configured to detect intensity of contacts and receiving the user input includes detecting a contact on the display  902 , where the contact has a characteristic intensity. 
     In response to receiving input  916 , device  900  enters a clock face edit mode. For embodiments in which device  900  is configured to detect intensity of contacts, device  900  optionally determines whether the characteristic intensity of the contact is above an intensity threshold and, in accordance with a determination that the characteristic intensity is above the intensity threshold, enters the clock face edit mode. 
     In some embodiments, device  900  indicates that it is operating in the clock face edit mode by visually distinguishing the clock face or editable elements of the clock face.  FIG. 9B  depicts an example of user interface screen  902  when device  900  is in clock face edit mode. In  FIG. 9B , device  900  visually distinguishes that the complications  910 ,  912 , and  914  are editable with a dashed outline around their corresponding complication areas  911 ,  913 , and  915 , respectively. Other techniques that indicate device  900  is in clock face edit mode include, for example, reducing the size of the displayed clock face, highlighting the clock face or an editable element (e.g., a complication), and changing a color of the clock face or an editable element. 
     As shown in  FIG. 9B , while in the clock face edit mode, device  900  receives another input touch  918  corresponding to selection of complication area  915  at which complication  914  is displayed. In some embodiments, device  900  visually indicates a currently selectable complication area (e.g., by highlighting one of the complication areas) and provides functionality for a user to scroll to a different complication area by rotating the rotatable input mechanism  904 . Optionally, the currently selectable complication area is selected by pressing rotatable input mechanism  904 . 
     In response to receiving the input touch  918  corresponding to selection of complication area  915 , device  900  displays one or more representations of at least one of the one or more complications associated with the loaded applications. Optionally, device  900  displays only representations of complications that are available for the selected complication area based on, for example, the type of complication, size of the complication, or other factors. 
     In  FIG. 9C , device  900  displays representations  920 ,  921 , and  922  of third party complications (e.g., complications associated with third party applications) that provide content (e.g., complication data) from Twitter, Facebook, and a sports information source, respectively. The list of complications available for the selected complication area may be obtained from the respective applications and displayed on device  900 . Device  900  also displays representation  923  representing the date complication illustrated in  FIGS. 9A-9B . Optionally, representations of first party complications associated with applications provided by the manufacturer of device  900  are also displayed. 
     In  FIG. 9C , device  900  receives an input, touch input  924 , corresponding to selection of representation  922  of the sports complication. In response, device  900  associates the sports complication with the selected complication area of the clock face  915 . 
     After representation  922  is selected, device  900  displays the corresponding complication at the selected complication area  915 . In some embodiments, device  900  exits the clock face edit mode in response to selection of the representation of the complication. In other embodiments, in response to selection of the representation of the complication, device  900  removes the display of the representations while remaining in the clock face edit mode, and then exits the clock face edit mode in response to further input (e.g., selection of a “Done” affordance, a contact with a characteristic intensity that exceeds a threshold intensity, or a press of the rotatable input mechanism  904 ). 
       FIG. 9D  depicts a user interface  928  including content associated with the sports complication  926 . Sports complication  926  includes content, at least a portion of which is displayed on device  900 . The content associated with sports complication  926  in the illustrated example includes information of a baseball game. 
     In some embodiments, the content is received from a corresponding sports application loaded on device  900 . In some embodiments, the sports application receives content from an Internet source (e.g., MLB.com) and/or the local device. In some embodiments, a companion application executes on a companion device, retrieves data from a server, and provides the data to device  900  for displaying a complication in accordance with various techniques. In some embodiments, device  900  requests an update to complication data from the companion application. In some embodiments, the companion application provides an update to complication data to device  900 . 
     In some embodiments, device  900  determines a display format for the content included in the complication and displays, in the corresponding complication area, a representation of the content formatted according to the display format. It should be recognized that the display format can be determined at various times and is not necessarily determined upon or after selection of a complication. For example, in some embodiments, various display formats for a complication are pre-determined for complication areas of different sizes and layouts. 
     Returning to  FIG. 9D , user interface  928  depicts a clock face including content associated with the sports complication  926  displayed in a first format. In  FIG. 9D , the display format for the content of complication  926  includes the names of the teams, score, count on the batter, the inning, and number of outs. 
     In some embodiments, a display format for at least a portion of the content in a third party complication is determined in accordance with the techniques and methods described above with reference to  FIGS. 6A-6I, and 7 . In some embodiments, the content of the third party complication includes a point in time, a duration, an offset, and/or a decimal number, and device  900  determines a particular display format (e.g., an optimized display format) from a plurality of available display formats based on the data type, the information represented by the content, a display style, the size of the designated area for the content, or any combination thereof. 
     In some embodiments, different display formats are used for different complication areas. Optionally, the display format of the content is determined based at least in part on the size of the complication area.  FIG. 9E  depicts an example in which sports complication  926  is selected to be displayed at complication area  911 . Compared to complication area  915 , in complication area  911  sports complication  926  is displayed in a more compact format in which the team names are abbreviated with a single letter, the count on the batter is not included, and the inning indicator is reduced in size. In some embodiments, the display format is determined based on the information or data type of the complication. For example, a different display format may be used to indicate the score of a football game or status of a tennis match. Other examples include abbreviating the name of a team with a long name (e.g., abbreviating Diamondbacks to Dbacks as shown in  FIG. 9F ) or rearranging information and not including the count on the batter to accommodate a longer team name (as shown in  FIG. 9G ). 
       FIGS. 10A-10B  depict a flow diagram illustrating a method for displaying a complication using an electronic device in accordance with some embodiments. Method  1000  is performed at a device (e.g.,  100 ,  300 ,  500 ,  900 ) with a display. Some operations in method  1000  may be combined, the order of some operations may be changed, and some operations may be omitted. 
     As described below, method  1000  provides an efficient way for displaying complication content on a reduced-size user interface. The method automatically adjusts the format in which content is displayed based on the available space, thereby creating a more efficient user interface. For third party complications, method  1000  may display content in a more comprehensible format for complications that have not been specifically designed for a particular display area. Method  100  may also provide a more consistent visual appearance between complications from different sources, making it easier for a user to process the displayed information from each source. Accordingly, method  1000  may reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, the method may conserve power and increase the time between battery charges. 
     At block  1002 , the device receives data representing an application. 
     At block  1004 , in response to receiving the data representing the application, the device loads the application into memory and stores data representing one or more complications (e.g., complication  926 ) associated with the application. 
     At block  1006 , the device displays a first user interface screen (e.g., user interface  906 ) including a clock face, where the clock face includes one or more complication areas (e.g., complication areas  911 ,  913 ,  915 ). 
     At block  1008 , the device receives a first user input (e.g., touch  916 ). 
     At block  1010 , in response to receiving the first user input, the device enters a clock face edit mode (e.g.,  FIG. 9B ). 
     At block  1012 , while in the clock face edit mode, the device receives a second user input (e.g., touch  918 ) corresponding to selection of a first complication area (e.g., complication area  915 ) of the one or more complication areas. 
     At block  1014 , in response to receiving the second user input corresponding to selection of the first complication area, the device displays one or more representations of at least one of the one or more complications associated with the application (e.g., representations  920 - 922 ). 
     At block  1016 , the device determines a first display format for the content associated with a first complication (e.g., complication  926 ). 
     At block  1018 , the device receives a third user input (e.g., touch  924 ) corresponding to selection of a representation of the first complication (e.g., representation  922 ). 
     At block  1020 , in response to receiving the third user input, the device associates the first complication with the first complication area of the clock face. 
     At block  1022 , while in the clock face edit mode, the device receives a fourth user input (e.g., touch  924 ). 
     At block  1024 , in response to receiving the fourth user input, the device exits the clock face edit mode and displays a second user interface screen (e.g., user interface  928 ) including the clock face, where the clock face on the second user interface screen includes the first complication in the first complication area and the first complication includes a representation of the content formatted according to the first display format (e.g.,  FIG. 9D ). 
     Note that details of the processes described above with respect to method  700  (e.g.,  FIG. 7 ) are also applicable in an analogous manner to method  1000 . For example, method  1000  may include one or more of the characteristics of the various methods described above with reference to method  700 . For example, the device may determine a display format for content of the complication from a plurality of available display formats based on at least the content and the size of the area designated for the content, as described with reference to block  706 . For brevity, these details are not repeated below. 
     In accordance with some embodiments,  FIG. 11  shows an exemplary functional block diagram of an electronic device  1100  configured in accordance with the principles of the various described embodiments. In accordance with some embodiments, the functional blocks of electronic device  1100  are configured to perform the techniques described above. The functional blocks of the device  1100  are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG. 11  are, optionally, combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG. 11 , an electronic device  1100  includes a memory unit  1102 , a display unit  1104  configured to display a graphic user interface, optionally, a touch-sensitive surface unit  1106  configured to receive contacts, and a processing unit  1108  coupled to the memory unit  1102 , display unit  1104  and, optionally, the touch-sensitive surface unit  1106 . In some embodiments, the processing unit  1108  includes a receiving unit  1110 , a loading unit  1112 , a display enabling unit  1114 , and a determining unit  1116 . 
     The processing unit  1108  is configured to receive (e.g., with receiving unit  1110 ) data representing an application and, in response to receiving the data representing the application, load (e.g., with loading unit  1112 ) the application into the memory unit  1102 , where loading the application into memory unit  1102  includes storing data representing one or more complications associated with the application. Processing unit  1108  is further configured to enable (e.g., with display enabling unit  1114 ) display of a first user interface screen including a clock face, where the clock face includes one or more complication areas, receive (e.g., with receiving unit  1110 ) a first user input, and, in response to receiving the first user input, enter a clock face edit mode of the electronic device. Processing unit  1108  is further configured to, while in the clock face edit mode, receive (e.g., with receiving unit  1110 ) a second user input corresponding to selection of a first complication area of the one or more complication areas and, in response to receiving the second user input corresponding to selection of the first complication area, enable (e.g., with display enabling unit  1114 ) display of one or more representations of at least one of the one or more complications associated with the application, where the one or more representations includes a first representation of a first complication from the at least one of the one or more complications associated with the application and the first complication includes content associated with the first complication. Processing unit  1108  is further configured to determine (e.g., with determining unit  1116 ) a first display format for the content associated with the first complication, receive (e.g., with receiving unit  1110 ) a third user input corresponding to selection of the first representation of the first complication, and, in response to receiving the third user input, associate the first complication with the first complication area of the clock face. Processing unit  1108  is further configured to, while in the clock face edit mode, receive (e.g., with receiving unit  1110 ) a fourth user input and, in response to receiving the fourth user input: exit the clock face edit mode; and enable (e.g., with display enabling unit  1114 ) display of a second user interface screen including the clock face, where the clock face on the second user interface screen includes the first complication in the first complication area and the first complication includes a representation of the content formatted according to the first display format. 
     In some embodiments, the first complication includes a layout with one or more designated areas, where the content associated with the first complication is associated with a first designated area of the one or more designated areas and determining the first display format for the content includes: determining (e.g., with determining unit  1116 ) a size of the first designated area; and determining (e.g., with determining unit  1116 ) the first display format from a plurality of available display formats based on at least the content and the size of the first designated area. 
     In some embodiments, the content is associated with a display style and selecting the first display format is further based on the display style associated with the content. Optionally, the display style includes a font associated with the content. 
     In some embodiments, each display format of the plurality of available display formats corresponds to a display size of the information formatted according to the respective display format and determining the first display format further includes: determining (e.g., with determining unit  1116 ) an optimized display format, where the optimized display format is determined to be the display format of the plurality of available display formats that corresponds to the largest display size of the display sizes corresponding to the plurality of available display formats that does not exceed the size of the first designated area; and determining (e.g., with determining unit  1116 ) the first display format to be the optimized display format. 
     In some embodiments, the plurality of available display formats forms a hierarchy ranked according to the display sizes corresponding to the display formats of the plurality of available display formats and determining the first display format further includes: determining (e.g., with determining unit  1116 ) whether the optimized display format is below a predetermined lowest allowable display format in the hierarchy; and in accordance with a determination that the optimized display format is below the lowest allowable display format in the hierarchy, determining (e.g., with determining unit  1116 ) the first display format to be the lowest allowable display format. 
     In some embodiments, determining the first display format of the content from the plurality of available display formats further comprises: determining (e.g., with determining unit  1116 ) whether the optimized display format is above a predetermined highest allowable display format in the hierarchy; and in accordance with a determination that the optimized display format is above the highest allowable display format in the hierarchy, determining (e.g., with determining unit  1116 ) the first display format to be the lowest allowable display format. 
     In some embodiments, processing unit  1108  is further configured to: determine (e.g., with determining unit  1116 ) whether the display size corresponding to the first display format exceeds the size of the first designated area; and in accordance with a determination that the display size corresponding to the first display format exceeds the size of the first designated area, truncate the representation of the information to the size of the first designated area. 
     In some embodiments, the plurality of available display formats is a defined set that is based on the content of the information. In some embodiments, the content of the information represents a point in time, a duration, an offset, or a decimal number. 
     The operations described above with reference to  FIGS. 10A-10B  are, optionally, implemented by components depicted in  FIGS. 1A-1B  or  FIG. 11 . For example, receiving operations  1002 ,  1008 ,  1012 ,  1018 , and  1022 , loading and storing operation  1004 , displaying operations  1006  and  1014 , entering operation  1010 , determining operations  1016 , associating operation  1020 , and exiting and displaying operation  1024  may be implemented by event sorter  170 , event recognizer  180 , and event handler  190 . Event monitor  171  in event sorter  170  detects a contact on touch-sensitive display  112 , and event dispatcher module  174  delivers the event information to application  136 - 1 . A respective event recognizer  180  of application  136 - 1  compares the event information to respective event definitions  186 , and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub event, such as activation of an affordance on a user interface. When a respective predefined event or sub-event is detected, event recognizer  180  activates an event handler  190  associated with the detection of the event or sub-event. Event handler  190  may utilize or call data updater  176  or object updater  177  to update the application internal state  192 . In some embodiments, event handler  190  accesses a respective GUI updater  178  to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in  FIGS. 1A-1B . 
     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 disclosure 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.

Metadata:
Filing Date: 20180126
Publication Date: 20200225
Grant Date: 20200225
Priority Date: 20150605
Inventors: CHEN, KEVIN WILL
BLOCK, Eliza
YANG, LAWRENCE Y.
WILSON, CHRISTOPHER
WILSON, ERIC LANCE
SALZMAN, PAUL W.
SCHIMON, DAVID
Assignee: APPLE INC
CPC Classifications: [{"code": "G06F40/109", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F40/151", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04842", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F40/151", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0488", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04847", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F3/0488", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04842", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F17/2264", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04842", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F17/214", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0488", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04847", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F40/109", "inventive": true, "first": true, "tree": "[]"}]
Family ID: 57442339