Patent Publication Number: US-10775999-B2

Title: Device, method, and graphical user interface for displaying user interface objects corresponding to an application

Description:
RELATED APPLICATIONS 
     This application is a continuation of U.S. application Ser. No. 14/856,517, filed Sep. 16, 2015, which is a continuation of U.S. application Ser. No. 14/536,464, filed Nov. 7, 2014, which is a continuation of PCT Patent Application Serial No. PCT/US2013/040061, filed on May 8, 2013, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” which claims the benefit of and priority to U.S. Provisional Patent Application Ser. No. 61/778,191, filed on Mar. 12, 2013, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application;” U.S. Provisional Patent Application No. 61/747,278, filed Dec. 29, 2012, entitled “Device, Method, and Graphical User Interface for Manipulating User Interface Objects with Visual and/or Haptic Feedback;” and U.S. Provisional Patent Application No. 61/688,227, filed May 9, 2012, entitled “Device, Method, and Graphical User Interface for Manipulating User Interface Objects with Visual and/or Haptic Feedback,” which applications are incorporated by reference herein in their entireties. 
     This application is also related to the following: U.S. Provisional Patent Application Ser. No. 61/778,092, filed on Mar. 12, 2013, entitled “Device, Method, and Graphical User Interface for Selecting Object within a Group of Objects;” U.S. Provisional Patent Application Ser. No. 61/778,125, filed on Mar. 12, 2013, entitled “Device, Method, and Graphical User Interface for Navigating User Interface Hierarchies;” U.S. Provisional Patent Application Ser. No. 61/778,156, filed on Mar. 12, 2013, entitled “Device, Method, and Graphical User Interface for Manipulating Framed Graphical Objects;” U.S. Provisional Patent Application Ser. No. 61/778,179, filed on Mar. 12, 2013, entitled “Device, Method, and Graphical User Interface for Scrolling Nested Regions;” U.S. Provisional Patent Application Ser. No. 61/778,171, filed on Mar. 12, 2013, entitled “Device, Method, and Graphical User Interface for Displaying Additional Information in Response to a User Contact;” U.S. Provisional Patent Application Ser. No. 61/778,211, filed on Mar. 12, 2013, entitled “Device, Method, and Graphical User Interface for Facilitating User Interaction with Controls in a User Interface;” U.S. Provisional Patent Application Ser. No. 61/778,239, filed on Mar. 12, 2013, entitled “Device, Method, and Graphical User Interface for Forgoing Generation of Tactile Output for a Multi-Contact Gesture;” U.S. Provisional Patent Application Ser. No. 61/778,284, filed on Mar. 12, 2013, entitled “Device, Method, and Graphical User Interface for Providing Tactile Feedback for Operations Performed in a User Interface;” U.S. Provisional Patent Application Ser. No. 61/778,287, filed on Mar. 12, 2013, entitled “Device, Method, and Graphical User Interface for Providing Feedback for Changing Activation States of a User Interface Object;” U.S. Provisional Patent Application Ser. No. 61/778,363, filed on Mar. 12, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning between Touch Input to Display Output Relationships;” U.S. Provisional Patent Application Ser. No. 61/778,367, filed on Mar. 12, 2013, entitled “Device, Method, and Graphical User Interface for Moving a User Interface Object Based on an Intensity of a Press Input;” U.S. Provisional Patent Application Ser. No. 61/778,265, filed on Mar. 12, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning between Display States in Response to a Gesture;” U.S. Provisional Patent Application Ser. No. 61/778,373, filed on Mar. 12, 2013, entitled “Device, Method, and Graphical User Interface for Managing Activation of a Control Based on Contact Intensity;” U.S. Provisional Patent Application Ser. No. 61/778,412, filed on Mar. 13, 2013, entitled “Device, Method, and Graphical User Interface for Displaying Content Associated with a Corresponding Affordance;” U.S. Provisional Patent Application Ser. No. 61/778,413, filed on Mar. 13, 2013, entitled “Device, Method, and Graphical User Interface for Selecting User Interface Objects;” U.S. Provisional Patent Application Ser. No. 61/778,414, filed on Mar. 13, 2013, entitled “Device, Method, and Graphical User Interface for Moving and Dropping a User Interface Object;” U.S. Provisional Patent Application Ser. No. 61/778,416, filed on Mar. 13, 2013, entitled “Device, Method, and Graphical User Interface for Determining Whether to Scroll or Select Content;” and U.S. Provisional Patent Application Ser. No. 61/778,418, filed on Mar. 13, 2013, entitled “Device, Method, and Graphical User Interface for Switching between User Interfaces,” which are incorporated herein by reference in their entireties. 
     This application is also related to the following: U.S. Provisional Patent Application Ser. No. 61/645,033, filed on May 9, 2012, entitled “Adaptive Haptic Feedback for Electronic Devices;” U.S. Provisional Patent Application Ser. No. 61/665,603, filed on Jun. 28, 2012, entitled “Adaptive Haptic Feedback for Electronic Devices;” and U.S. Provisional Patent Application Ser. No. 61/681,098, filed on Aug. 8, 2012, entitled “Adaptive Haptic Feedback for Electronic Devices,” which are incorporated herein by reference in their entireties. 
    
    
     TECHNICAL FIELD 
     This relates generally to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that detect inputs for manipulating user interfaces. 
     BACKGROUND 
     The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Exemplary touch-sensitive surfaces include touch pads and touch screen displays. Such surfaces are widely used to manipulate user interface objects on a display. 
     Exemplary manipulations include adjusting the position and/or size of one or more user interface objects or activating buttons or opening files/applications represented by user interface objects, as well as associating metadata with one or more user interface objects or otherwise manipulating user interfaces. Exemplary user interface objects include digital images, video, text, icons, control elements such as buttons and other graphics. A user will, in some circumstances, need to perform such manipulations on user interface objects in a file management program (e.g., Finder from Apple Inc. of Cupertino, Calif.), an image management application (e.g., Aperture or iPhoto from Apple Inc. of Cupertino, Calif.), a digital content (e.g., videos and music) management application (e.g., iTunes from Apple Inc. of Cupertino, Calif.), a drawing application, a presentation application (e.g., Keynote from Apple Inc. of Cupertino, Calif.), a word processing application (e.g., Pages from Apple Inc. of Cupertino, Calif.), a website creation application (e.g., iWeb from Apple Inc. of Cupertino, Calif.), a disk authoring application (e.g., iDVD from Apple Inc. of Cupertino, Calif.), or a spreadsheet application (e.g., Numbers from Apple Inc. of Cupertino, Calif.). 
     But existing methods for performing these manipulations are cumbersome and inefficient. In addition, existing methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices. 
     SUMMARY 
     Accordingly, there is a need for electronic devices with faster, more efficient methods and interfaces for manipulating user interfaces. Such methods and interfaces optionally complement or replace conventional methods for manipulating user interfaces. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges. 
     The above deficiencies and other problems associated with user interfaces for electronic devices with touch-sensitive surfaces are reduced or eliminated by the disclosed devices. 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 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 primarily through finger contacts and gestures on the touch-sensitive surface. 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. 
     There is a need for electronic devices with faster, more efficient methods and interfaces for previewing content. Such methods and interfaces may complement or replace conventional methods for previewing content. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges. 
     In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface. The method includes: displaying a plurality of document icons, including a respective document icon corresponding to a respective electronic document associated with a respective application; and while a focus selector is over the respective document icon, detecting a gesture that includes a contact on the touch-sensitive surface. The method further includes, in response to detecting the gesture: in accordance with a determination that the contact had a maximum intensity during the gesture that was below a respective intensity threshold, displaying the electronic document in a new application window of the respective application; and in accordance with a determination that the contact reached an intensity during the gesture that was above the respective intensity threshold, displaying a preview of the respective electronic document without displaying a new application window of the respective application. 
     In accordance with some embodiments, an electronic device includes a display unit configured to display a plurality of document icons, including a respective document icon corresponding to a respective electronic document associated with a respective application; a touch-sensitive surface unit configured to receive gestures that include contacts; one or more sensor units configured to detect intensity of contacts with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the sensor units. The processing unit is configured to: while a focus selector is over the respective document icon, detect a gesture that includes a contact on the touch-sensitive surface unit. The processing unit is further configured to, in response to detecting the gesture: in accordance with a determination that the contact had a maximum intensity during the gesture that was below a respective intensity threshold, enable display of the electronic document in a new application window of the respective application; and in accordance with a determination that the contact reached an intensity during the gesture that was above the respective intensity threshold, enable display of a preview of the respective electronic document without enabling display of a new application window of the respective application. 
     Thus, electronic devices with displays, touch-sensitive surfaces, and one or more sensors to detect intensity of contacts with the touch-sensitive surface are provided with faster, more efficient methods and interfaces for previewing content, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for previewing content. 
     There is a need for electronic devices with faster, more efficient methods and interfaces for previewing content. Such methods and interfaces may complement or replace conventional methods for previewing content. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges. 
     In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface. The method includes: displaying a frame for previewing content, where the frame corresponds to a plurality of content items; detecting movement of a contact across the touch-sensitive surface; moving a focus selector across the frame in accordance with the movement of the contact across the touch-sensitive surface; sequentially displaying, in the frame, previews of respective content items in the plurality of content items in accordance with the movement of the focus selector across the frame, where a size of the previews is constrained to a size of the frame; while a respective preview of a respective content item is displayed in the frame at a first size, detecting an increase in intensity of the contact; in response to detecting the increase in intensity of the contact, increasing the size of the respective preview to a second size larger than the size of the frame; while displaying the respective preview at the second size, detecting a decrease in intensity of the contact; and in response to detecting the decrease in intensity of the contact, reducing the size of the respective preview to the first size. 
     In accordance with some embodiments, an electronic device includes a display unit configured to display a frame for previewing content, where the frame corresponds to a plurality of content items; a touch-sensitive surface unit configured to receive contacts; one or more sensor units configured to detect intensity of contacts with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the sensor units. The processing unit is configured to detect movement of a contact across the touch-sensitive surface unit; move a focus selector across the frame in accordance with the movement of the contact across the touch-sensitive surface unit; enable sequential display of, in the frame, previews of respective content items in the plurality of content items in accordance with the movement of the focus selector across the frame, wherein a size of the previews is constrained to a size of the frame; while a respective preview of a respective content item is displayed in the frame at a first size, detect an increase in intensity of the contact; in response to detecting the increase in intensity of the contact, increase the size of the respective preview to a second size larger than the size of the frame; while displaying the respective preview at the second size, detect a decrease in intensity of the contact; and in response to detecting the decrease in intensity of the contact, reduce the size of the respective preview to the first size. 
     Thus, electronic devices with displays, touch-sensitive surfaces and one or more sensors to detect intensity of contacts with the touch-sensitive surface are provided with faster, more efficient methods and interfaces for previewing content, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for previewing content. 
     There is a need for electronic devices with faster, more efficient methods and interfaces for displaying user interface objects corresponding to an application. Such methods and interfaces may complement or replace conventional methods for displaying user interface objects corresponding to an application. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges. 
     In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface and one or more sensors to detect intensity of contacts with the touch-sensitive surface. The method includes: displaying a plurality of application icons, where the plurality of application icons includes a respective application icon corresponding to a respective application; while a focus selector is over the respective application icon, detecting a gesture that includes a contact on the touch-sensitive surface; and in response to detecting the gesture: in accordance with a determination that the contact had a maximum intensity during the gesture that was below a respective intensity threshold, displaying an application window of the respective application; and in accordance with a determination that the contact reached an intensity during the gesture that was above the respective intensity threshold, displaying a plurality of user interface objects that correspond to the respective application. 
     In accordance with some embodiments, an electronic device includes a display unit configured to display a plurality of application icons, where the plurality of application icons include a respective application icon corresponding to a respective application; a touch-sensitive surface unit configured to receive gestures including contacts; one or more sensor units configured to detect intensity of contacts with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit and the sensor units. The processing unit is configured to: while a focus selector is over the respective application icon, detect a gesture that includes a contact on the touch-sensitive surface unit; and in response to detecting the gesture: in accordance with a determination that the contact had a maximum intensity during the gesture that was below a respective intensity threshold, enable display of an application window of the respective application; and in accordance with a determination that the contact reached an intensity during the gesture that was above the respective intensity threshold, enable display of a plurality of user interface objects that correspond to the respective application. 
     Thus, electronic devices with displays, touch-sensitive surfaces and one or more sensors to detect intensity of contacts with the touch-sensitive surface are provided with faster, more efficient methods and interfaces for displaying user interface objects corresponding to an application, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for displaying user interface objects corresponding to an application. 
     In accordance with some embodiments, an electronic device includes a display, a touch-sensitive surface, optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, one or more processors, memory, and one or more programs; the one or more programs are stored in the memory and configured to be executed by the one or more processors and the one or more programs include instructions for performing the operations of any of the methods referred to in the fifth paragraph of the Description of Embodiments. In accordance with some embodiments, a graphical user interface on an electronic device with a display, a touch-sensitive surface, optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, a memory, and one or more processors to execute one or more programs stored in the memory includes one or more of the elements displayed in any of the methods referred to in the fifth paragraph of the Description of Embodiments, which are updated in response to inputs, as described in any of the methods referred to in the fifth paragraph of the Description of Embodiments. In accordance with some embodiments, a computer readable storage medium has stored therein instructions which when executed by an electronic device with a display, a touch-sensitive surface, and optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, cause the device to perform the operations of any of the methods referred to in the fifth paragraph of the Description of Embodiments. In accordance with some embodiments, an electronic device includes: a display, a touch-sensitive surface, and optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface; and means for performing the operations of any of the methods referred to in the fifth paragraph of the Description of Embodiments. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a display and a touch-sensitive surface, optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, includes means for performing the operations of any of the methods referred to in the fifth paragraph of the Description of Embodiments. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures. 
         FIG. 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. 
         FIGS. 5A-5S  illustrate exemplary user interfaces for previewing content in accordance with some embodiments. 
         FIGS. 6A-6C  are flow diagrams illustrating a method of previewing content in accordance with some embodiments. 
         FIG. 7  is a functional block diagram of an electronic device in accordance with some embodiments. 
         FIGS. 8A-8W  illustrate exemplary user interfaces for previewing content in accordance with some embodiments. 
         FIGS. 9A-9C  are flow diagrams illustrating a method of previewing content in accordance with some embodiments. 
         FIG. 10  is a functional block diagram of an electronic device in accordance with some embodiments. 
         FIGS. 11A-11P  illustrate exemplary user interfaces for displaying user interface objects corresponding to an application in accordance with some embodiments. 
         FIGS. 12A-12B  are flow diagrams illustrating a method of displaying user interface objects corresponding to an application in accordance with some embodiments. 
         FIG. 13  is a functional block diagram of an electronic device in accordance with some embodiments. 
     
    
    
     DESCRIPTION OF EMBODIMENTS 
     The methods, devices and GUIs described herein provide visual and/or haptic feedback that makes manipulation of user interface objects more efficient and intuitive for a user. For example, in a system where the clicking action of a trackpad is decoupled from the contact intensity (e.g., contact force, contact pressure, or a substitute therefore) that is needed to reach an activation threshold, the device can generate different tactile outputs (e.g., “different clicks”) for different activation events (e.g., so that clicks that accomplish a particular result are differentiated from clicks that do not produce any result or that accomplish a different result from the particular result). Additionally, tactile outputs can be generated in response to other events that are not related to increasing intensity of a contact, such as generating a tactile output (e.g., a “detent”) when a user interface object is moved to a particular position, boundary or orientation, or when an event occurs at the device. 
     Additionally, in a system where a trackpad or touch-screen display is sensitive to a range of contact intensity that includes more than one or two specific intensity values (e.g., more than a simple on/off, binary intensity determination), the user interface can provide responses (e.g., visual or tactile cues) that are indicative of the intensity of the contact within the range. In some implementations, a pre-activation-threshold response and/or a post-activation-threshold response to an input are displayed as continuous animations. As one example of such a response, a preview of an operation is displayed in response to detecting an increase in contact intensity that is still below an activation threshold for performing the operation. As another example of such a response, an animation associated with an operation continues even after the activation threshold for the operation has been reached. Both of these examples provide a user with a continuous response to the force or pressure of a user&#39;s contact, which provides a user with visual and/or haptic feedback that is richer and more intuitive. More specifically, such continuous force responses give the user the experience of being able to press lightly to preview an operation and/or press deeply to push “past” or “through” a predefined user interface state corresponding to the operation. 
     Additionally, for a device with a touch-sensitive surface that is sensitive to a range of contact intensity, multiple contact intensity thresholds can be monitored by the device and different functions can be mapped to different contact intensity thresholds. This serves to increase the available “gesture space” providing easy access to advanced features for users who know that increasing the intensity of a contact at or beyond a second “deep press” intensity threshold will cause the device to perform a different operation from an operation that would be performed if the intensity of the contact is between a first “activation” intensity threshold and the second “deep press” intensity threshold. An advantage of assigning additional functionality to a second “deep press” intensity threshold while maintaining familiar functionality at a first “activation” intensity threshold is that inexperienced users who are, in some circumstances, confused by the additional functionality can use the familiar functionality by just applying an intensity up to the first “activation” intensity threshold, whereas more experienced users can take advantage of the additional functionality by applying an intensity at the second “deep press” intensity threshold. 
     Additionally, for a device with a touch-sensitive surface that is sensitive to a range of contact intensity, the device can provide additional functionality by allowing users to perform complex operations with a single continuous contact. For example, when selecting a group of objects, a user can move a continuous contact around the touch-sensitive surface and can press while dragging (e.g., applying an intensity greater than a “deep press” intensity threshold) to add additional elements to a selection. In this way, a user can intuitively interact with a user interface where pressing harder with a contact causes objects in the user interface to be “stickier.” 
     A number of different approaches to providing an intuitive user interface on a device where a clicking action is decoupled from the force that is needed to reach an activation threshold and/or the device is sensitive to a wide range of contact intensities are described below. Using one or more of these approaches (optionally in conjunction with each other) helps to provide a user interface that intuitively provides users with additional information and functionality, thereby reducing the user&#39;s cognitive burden and improving the human-machine interface. Such improvements in the human-machine interface enable users to use the device faster and more efficiently. For battery-operated devices, these improvements conserve power and increase the time between battery charges. For ease of explanation, systems, methods and user interfaces for including illustrative examples of some of these approaches are described below, as follows:
         Many electronic devices allow users to interact with items such as documents. A document may reside in a folder or be attached to another document, such as an email. In some methods, if the user wants to look at the contents of the document, the user would have to open the document in the associated application. This can be tedious and wasteful of system resources, as the user may merely wish to view the document contents quickly. The embodiments described below improve on these methods of interacting with documents by allowing the user to preview a document or open the document based on the intensity of a contact corresponding to a focus selector interacting with a document icon. In particular,  FIGS. 5A-5S  illustrate exemplary user interfaces for previewing content.  FIGS. 6A-6C  are flow diagrams illustrating a method of previewing content. The user interfaces in  FIGS. 5A-5S  are used to illustrate the processes in  FIGS. 6A-6C .   Many electronic devices have user interfaces for browsing content items, such as photos. The content items are, optionally, organized into multiple sets of items. In some methods, to preview the items within a set, a user would need to first select and open the desired set of items as in opening a folder, and then preview the items in the set. This adds additional steps to the previewing process and can make the process tedious if the user is previewing items in multiple sets. The embodiments below improve on these methods by enabling a user to preview items within a set in accordance with movement and intensity of a contact. In particular,  8 A- 8 W illustrate exemplary user interfaces for previewing content.  FIGS. 9A-9C  are flow diagrams illustrating a method of previewing content. The user interfaces in  FIGS. 8A-8W  are used to illustrate the processes in  FIGS. 9A-9C .   At any one time, a user may have multiple windows for any one application opened, and not all of them are displayed. Some of these windows or documents are, optionally, minimized or hidden by other windows. Further, an application may have a recently opened documents history. In some methods, a user keeps track of the multiple windows by looking at a taskbar or opening a task list, both of which are, optionally, hidden at first. To look at a recently opened documents history for an application, the user has to open the application. These methods add additional steps for the user and can be confusing and time consuming. The embodiments described below improve on these methods by providing a more efficient way to review currently opened windows and a history of recently opened documents in accordance with an intensity of a contact. In particular,  FIGS. 11A-11P  illustrate exemplary user interfaces for displaying user interface objects corresponding to an application.  FIGS. 12A-12B  are flow diagrams illustrating a method of displaying user interface objects corresponding to an application. The user interfaces in  FIGS. 11A-11P  are used to illustrate the processes in  FIGS. 12A-12B .       

     Exemplary Devices 
     Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments. 
     It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact. 
     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. 
     As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context. 
     Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads), 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 touch pad). 
     In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick. 
     The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application. 
     The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user. 
     Attention is now directed toward embodiments of portable devices with touch-sensitive displays.  FIG. 1A  is a block diagram illustrating portable multifunction device  100  with touch-sensitive displays  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 (CPU&#39;s)  120 , peripherals interface  118 , RF circuitry  108 , audio circuitry  110 , speaker  111 , microphone  113 , input/output (I/O) subsystem  106 , other input or control devices  116 , and external port  124 . Device  100  optionally includes one or more optical sensors  164 . Device  100  optionally includes one or more 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). 
     As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user&#39;s sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user&#39;s hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user&#39;s movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user. 
     It should be appreciated that device  100  is only one example of a portable multifunction device, and that device  100  optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in  FIG. 1A  are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application specific integrated circuits. 
     Memory  102  optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory  102  by other components of device  100 , such as CPU  120  and the peripherals interface  118 , is, optionally, controlled by memory controller  122 . 
     Peripherals interface  118  can be used to couple input and output peripherals of the device to CPU  120  and memory  102 . The one or more processors  120  run or execute various software programs and/or sets of instructions stored in memory  102  to perform various functions for device  100  and to process data. 
     In some embodiments, peripherals interface  118 , CPU  120 , and memory controller  122  are, optionally, implemented on a single chip, such as chip  104 . In some other embodiments, they are, optionally, implemented on separate chips. 
     RF (radio frequency) circuitry  108  receives and sends RF signals, also called electromagnetic signals. RF circuitry  108  converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry  108  optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry  108  optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The 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, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document. 
     Audio circuitry  110 , speaker  111 , and microphone  113  provide an audio interface between a user and device  100 . Audio circuitry  110  receives audio data from peripherals interface  118 , converts the audio data to an electrical signal, and transmits the electrical signal to speaker  111 . Speaker  111  converts the electrical signal to human-audible sound waves. Audio circuitry  110  also receives electrical signals converted by microphone  113  from sound waves. Audio circuitry  110  converts the electrical signal to audio data and transmits the audio data to peripherals interface  118  for processing. Audio data is, optionally, retrieved from and/or transmitted to memory  102  and/or RF circuitry  108  by peripherals interface  118 . In some embodiments, audio circuitry  110  also includes a headset jack (e.g.,  212 ,  FIG. 2 ). The headset jack provides an interface between audio circuitry  110  and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone). 
     I/O subsystem  106  couples input/output peripherals on device  100 , such as touch screen  112  and other input control devices  116 , to peripherals interface  118 . I/O subsystem  106  optionally includes display controller  156 , optical sensor controller  158 , intensity sensor controller  159 , haptic feedback controller  161  and one or more input controllers  160  for other input or control devices. The one or more input controllers  160  receive/send electrical signals from/to other input or 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, infrared port, 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 ). 
     Touch-sensitive display  112  provides an input interface and an output interface between the device and a user. Display controller  156  receives and/or sends electrical signals from/to touch screen  112 . Touch screen  112  displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output corresponds to user-interface objects. 
     Touch screen  112  has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen  112  and display controller  156  (along with any associated modules and/or sets of instructions in memory  102 ) detect contact (and any movement or breaking of the contact) on touch screen  112  and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch screen  112 . In an exemplary embodiment, a point of contact between touch screen  112  and the user corresponds to a finger of the user. 
     Touch screen  112  optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen  112  and display controller  156  optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen  112 . In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif. 
     Touch screen  112  optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen  112  using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user. 
     In some embodiments, in addition to the touch screen, device  100  optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen  112  or an extension of the touch-sensitive surface formed by the touch screen. 
     Device  100  also includes power system  162  for powering the various components. Power system  162  optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices. 
     Device  100  optionally also includes one or more optical sensors  164 .  FIG. 1A  shows an optical sensor coupled to optical sensor controller  158  in I/O subsystem  106 . Optical sensor  164  optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor  164  receives light from the environment, projected through one or more lens, and converts the light to data representing an image. In conjunction with imaging module  143  (also called a camera module), optical sensor  164  optionally captures still images or video. In some embodiments, an optical sensor is located on the back of device  100 , opposite touch screen display  112  on the front of the device, so that the touch screen display is enabled for use as a viewfinder for still and/or video image acquisition. In some embodiments, another optical sensor is located on the front of the device so that the user&#39;s image is, optionally, obtained for videoconferencing while the user views the other video conference participants on the touch screen display. 
     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  optionally also includes one or more proximity sensors  166 .  FIG. 1A  shows proximity sensor  166  coupled to peripherals interface  118 . Alternately, proximity sensor  166  is coupled to input controller  160  in I/O subsystem  106 . 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  optionally also includes one or more accelerometers  168 .  FIG. 1A  shows accelerometer  168  coupled to peripherals interface  118 . Alternately, accelerometer  168  is, optionally, coupled to an input controller  160  in I/O subsystem  106 . 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  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, 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 thresholds 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 and intensities. 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 (lift off) 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 (lift off) event. 
     Graphics module  132  includes various known software components for rendering and displaying graphics on touch screen  112  or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like. 
     In some embodiments, graphics module  132  stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module  132  receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller  156 . 
     Haptic feedback module  133  includes various software components for generating instructions used by tactile output generator(s)  167  to produce tactile outputs at one or more locations on device  100  in response to user interactions with device  100 . 
     Text input module  134 , which is, optionally, a component of graphics module  132 , provides soft keyboards for entering text in various applications (e.g., contacts  137 , e-mail  140 , IM  141 , browser  147 , and any other application that needs text input). 
     GPS module  135  determines the location of the device and provides this information for use in various applications (e.g., to telephone  138  for use in location-based dialing, to camera  143  as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets). 
     Applications  136  optionally include the following modules (or sets of instructions), or a subset or superset thereof:
         contacts module  137  (sometimes called an address book or contact list);   telephone module  138 ;   video conferencing 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 ;   browser module  147 ;   calendar module  148 ;   widget modules  149 , which optionally include one or more of: weather widget  149 - 1 , stocks widget  149 - 2 , calculator widget  149 - 3 , alarm clock widget  149 - 4 , dictionary widget  149 - 5 , and other widgets obtained by the user, as well as user-created widgets  149 - 6 ;   widget creator module  150  for making user-created widgets  149 - 6 ;   search module  151 ;   video and music player module  152 , which is, optionally, made up of a video player module and a music player module;   notes module  153 ;   map module  154 ; and/or   online video module  155 .       

     Examples of other applications  136  that are, optionally, stored in memory  102  include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication. 
     In conjunction with touch screen  112 , display controller  156 , contact module  130 , graphics module  132 , and text input module  134 , contacts module  137  are, optionally, used to manage an address book or contact list (e.g., stored in application internal state  192  of contacts module  137  in memory  102  or memory  370 ), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone  138 , video conference  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 module  130 , graphics module  132 , and text input module  134 , telephone module  138  are, optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book  137 , modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols and technologies. 
     In conjunction with RF circuitry  108 , audio circuitry  110 , speaker  111 , microphone  113 , touch screen  112 , display controller  156 , optical sensor  164 , optical sensor controller  158 , contact module  130 , graphics module  132 , text input module  134 , contact list  137 , and telephone module  138 , videoconferencing 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 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 module  130 , graphics module  132 , and text input module  134 , the instant messaging module  141  includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in a 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 module  130 , graphics module  132 , text input module  134 , GPS module  135 , map module  154 , and music player module  146 , 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 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 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 system controller  156 , contact 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 system controller  156 , contact 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 system controller  156 , contact module  130 , graphics module  132 , text input module  134 , and browser module  147 , widget modules  149  are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget  149 - 1 , stocks widget  149 - 2 , calculator widget  149 - 3 , alarm clock widget  149 - 4 , and dictionary widget  149 - 5 ) or created by the user (e.g., user-created widget  149 - 6 ). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets). 
     In conjunction with RF circuitry  108 , touch screen  112 , display system controller  156 , contact module  130 , graphics module  132 , text input module  134 , and browser module  147 , the widget creator module  150  are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget). 
     In conjunction with touch screen  112 , display system controller  156 , contact 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 system controller  156 , contact 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 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 system controller  156 , contact module  130 , graphics module  132 , text input module  134 , GPS module  135 , and browser module  147 , map module  154  are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions. 
     In conjunction with touch screen  112 , display system controller  156 , contact 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. 
     Each of the above identified modules and applications correspond 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 (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory  102  optionally stores a subset of the modules and data structures identified above. Furthermore, memory  102  optionally stores additional modules and data structures not described above. 
     In some embodiments, device  100  is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device  100 , the number of physical input control devices (such as push buttons, dials, and the like) on device  100  is, optionally, reduced. 
     The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device  100  to a main, home, or root menu from any user interface that is displayed on device  100 . In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad. 
       FIG. 1B  is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory  102  (in  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, peripheral interface  118  transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration). 
     In some embodiments, event sorter  170  also includes a hit view determination module  172  and/or an active event recognizer determination module  173 . 
     Hit view determination module  172  provides software procedures for determining where a sub-event has taken place within one or more views, when touch sensitive display  112  displays more than one view. Views are made up of controls and other elements that a user can see on the display. 
     Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture. 
     Hit view determination module  172  receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module  172  identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (i.e., 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, 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 module  182 . 
     In some embodiments, operating system  126  includes event sorter  170 . Alternatively, application  136 - 1  includes event sorter  170 . In yet other embodiments, event sorter  170  is a stand-alone module, or a part of another module stored in memory  102 , such as contact/motion module  130 . 
     In some embodiments, application  136 - 1  includes a plurality of event handlers  190  and one or more application views  191 , each of which includes instructions for handling touch events that occur within a respective view of the application&#39;s user interface. Each application view  191  of the application  136 - 1  includes one or more event recognizers  180 . Typically, a respective application view  191  includes a plurality of event recognizers  180 . In other embodiments, one or more of event recognizers  180  are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application  136 - 1  inherits methods and other properties. In some embodiments, a respective event handler  190  includes one or more of: data updater  176 , object updater  177 , GUI updater  178 , and/or event data  179  received from event sorter  170 . Event handler  190  optionally utilizes or calls data updater  176 , object updater  177  or GUI updater  178  to update the application internal state  192 . Alternatively, one or more of the application views  191  includes one or more respective event handlers  190 . Also, in some embodiments, one or more of data updater  176 , object updater  177 , and GUI updater  178  are included in a respective application view  191 . 
     A respective event recognizer  180  receives event information (e.g., event data  179 ) from event sorter  170 , and identifies an event from the event information. Event recognizer  180  includes event receiver  182  and event comparator  184 . In some embodiments, event recognizer  180  also includes at least a subset of: metadata  183 , and event delivery instructions  188  (which optionally include sub-event delivery instructions). 
     Event receiver  182  receives event information from event sorter  170 . The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device. 
     Event comparator  184  compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator  184  includes event definitions  186 . Event definitions  186  contain definitions of events (e.g., predefined sequences of sub-events), for example, event  1  ( 187 - 1 ), event  2  ( 187 - 2 ), and others. In some embodiments, sub-events in an event  187  include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event  1  ( 187 - 1 ) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (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 lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers  190 . 
     In some embodiments, event definition  187  includes a definition of an event for a respective user-interface object. In some embodiments, event comparator  184  performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display  112 , when a touch is detected on touch-sensitive display  112 , event comparator  184  performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler  190 , the event comparator uses the result of the hit test to determine which event handler  190  should be activated. For example, event comparator  184  selects an event handler associated with the sub-event and the object triggering the hit test. 
     In some embodiments, the definition for a respective event  187  also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer&#39;s event type. 
     When a respective event recognizer  180  determines that the series of sub-events do not match any of the events in event definitions  186 , the respective event recognizer  180  enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture. 
     In some embodiments, a respective event recognizer  180  includes metadata  183  with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata  183  includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata  183  includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy. 
     In some embodiments, a respective event recognizer  180  activates event handler  190  associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer  180  delivers event information associated with the event to event handler  190 . Activating an event handler  190  is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer  180  throws a flag associated with the recognized event, and event handler  190  associated with the flag catches the flag and performs a predefined process. 
     In some embodiments, event delivery instructions  188  include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process. 
     In some embodiments, data updater  176  creates and updates data used in application  136 - 1 . For example, data updater  176  updates the telephone number used in contacts module  137 , or stores a video file used in video player module  145 . 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 touch-pads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized. 
       FIG. 2  illustrates a portable multifunction device  100  having a touch screen  112  in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI)  200 . In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers  202  (not drawn to scale in the figure) or one or more styluses  203  (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward) and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device  100 . In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap. 
     Device  100  optionally also includes one or more physical buttons, such as “home” or menu button  204 . As described previously, menu button  204  is, optionally, used to navigate to any application  136  in a set of applications that are, optionally executed on device  100 . Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen  112 . 
     In one embodiment, 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 , head set 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 (CPU&#39;s)  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  are, optionally, stored in one or more of the previously mentioned memory devices. Each of the above identified modules corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory  370  optionally stores a subset of the modules and data structures identified above. Furthermore, memory  370  optionally stores additional modules and data structures not described above. 
     Attention is now directed towards embodiments of user interfaces (“UI”) that is, optionally, implemented on 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 are, optionally, implemented on device  300 . In some embodiments, user interface  400  includes the following elements, or a subset or superset thereof:
         Signal strength indicator(s)  402  for wireless communication(s), such as cellular and Wi-Fi signals;   Time  404 ;   Bluetooth indicator  405 ;   Battery status indicator  406 ;   Tray  408  with icons for frequently used applications, such as:
           Icon  416  for telephone module  138 , labeled “Phone,” which optionally includes an indicator  414  of the number of missed calls or voicemail messages;   Icon  418  for e-mail client module  140 , labeled “Mail,” which optionally includes an indicator  410  of the number of unread e-mails;   Icon  420  for browser module  147 , labeled “Browser;” and   Icon  422  for video and music player module  152 , also referred to as iPod (trademark of Apple Inc.) module  152 , labeled “iPod;” and   
           Icons for other applications, such as:
           Icon  424  for IM module  141 , labeled “Text;”   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 “Map;”   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, 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  are 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  359 ) for detecting intensity of contacts on touch-sensitive surface  451  and/or one or more tactile output generators  357  for generating tactile outputs for a user of device  300 . 
     Although some of the examples 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. 
     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). 
     The user interface figures described below include various intensity diagrams that show the current intensity of the contact on the touch-sensitive surface relative to one or more intensity thresholds (e.g., a contact detection intensity threshold IT 0 , a light press intensity threshold IT L , a deep press intensity threshold IT D , and/or one or more other intensity thresholds). This intensity diagram is typically not part of the displayed user interface, but is provided to aid in the interpretation of the figures. 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 an intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold IT 0  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 intensity of the contact from an intensity below the light press intensity threshold IT L  to an intensity between the light press intensity threshold IT L  and the deep press intensity threshold IT D  is sometimes referred to as a “light press” input. An increase of intensity of the contact from an intensity below the deep press intensity threshold IT D  to an intensity above the deep press intensity threshold IT D  is sometimes referred to as a “deep press” input. An increase of intensity of the contact from an intensity below the contact-detection intensity threshold IT 0  to an intensity between the contact-detection intensity threshold IT 0  and the light press intensity threshold IT L  is sometimes referred to as detecting the contact on the touch-surface. A decrease of intensity of the contact from an intensity above the contact-detection intensity threshold IT 0  to an intensity below the contact intensity threshold IT 0  is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments IT 0  is zero. In some embodiments IT 0  is greater than zero. In some illustrations a shaded circle or oval is used to represent intensity of a contact on the touch-sensitive surface. In some illustrations a circle or oval without shading is used represent a respective contact on the touch-sensitive surface without specifying the intensity of the respective contact. 
     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 description 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. 
     User Interfaces and Associated Processes 
     Previewing Content 
     Many electronic devices allow users to interact with items such as documents. A document may reside in a folder or attached another document, such as an email. In some methods, if the user wants to look at the contents of the document, the user would have to open the document in the associated application. This can be tedious and wasteful of system resources, as the user may merely wish to view the document contents quickly. The embodiments below improve on existing methods of interacting with documents by allowing the user to preview a document or open the document based on the intensity of a contact corresponding to interacting with a document icon. If the gesture includes a contact with a high intensity, the device displays a preview of the document is displayed. If the gesture includes a contact with a relatively low intensity, the device opens the document in the associated application. The user is thus able to control whether the device opens the document or opens a preview the document by adjusting the intensity of a contact on a touch-sensitive surface. 
       FIGS. 5A-5S  illustrate exemplary user interfaces for previewing content in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIGS. 6A-6C .  FIGS. 5A-5S  include intensity diagrams that show the current intensity of the contact on the touch-sensitive surface relative to a plurality of intensity thresholds including a light press intensity threshold (e.g., “IT L ”) and a deep press intensity threshold (e.g., “IT D ”). In some embodiments, operations similar to those described below with reference to IT D  are performed with reference to a different intensity threshold (e.g., “IT L ”), and vice versa. 
       FIG. 5A  illustrates window  2404  of an application displayed on display  450  (e.g., display  340 , touch screen  112 ) of a device (e.g., device  300 ,  100 ). The application with which window  2404  is associated is an application that displays content, such as an email application. Content, such as document  2406 , is displayed in window  2404 . Document  2406  optionally includes embedded content, attached content, and/or links to other content (for convenience, collectively referred to below as “embedded content”). The embedded content is, optionally, represented by document icons  2408 . For example, document  2406  includes document icons  2408 - 1  and  2408 - 2 , each of which corresponds to respective embedded content (e.g., a document) embedded in document  2406 . The respective documents corresponding to icons  2408 - 1  and  2408 - 2  are associated with respective applications. For example, icon  2408 - 1  optionally corresponds to a presentation document, which is associated with a presentation application. The document associated with an icon  2408  is, optionally, a word processing document, a spreadsheet, a presentation, a drawing, a graphic or image, an audio file, a video file, a text document, or a Portable Document Format document (sometimes referred to as a PDF). 
     Cursor  2410  is also displayed on display  450 . Cursor  2410  is an example of a focus selector. A user may move cursor  2410  on display  450  (e.g., using touch-sensitive surface  451  of the device) to bring focus to an element displayed on display  450  (e.g., a user interface object, an icon, a link, etc.) by moving a contact on touch-sensitive surface  451 .  FIG. 5A  shows movement of contact  2412  down and to the left on touch-sensitive surface  451  that causes the device to move cursor  2410  down and to the left on display  450 . 
       FIG. 5B  shows gesture detected on touch-sensitive surface  451  while cursor  2410  is located over document icon  2408 - 1 . The gesture includes a press input corresponding to an increase in intensity of contact  2412  on touch-sensitive surface  451  from an intensity below the light press intensity threshold IT L  to an intensity above the light press intensity threshold IT L . Contact  2412  in the gesture is determined to have a maximum intensity that is below the deep press intensity threshold (e.g., “IT D ”). 
     In response to the detection of the gesture including contact  2412  and in accordance with the determination that contact  2412  had a maximum intensity that is below the deep press intensity threshold (e.g., “IT D ”), the document corresponding to document icon  2408 - 1  is displayed in a new application window of the application with which the document is associated. For example,  FIG. 5C  shows Document  1   2416 , which corresponds to document icon  2408 - 1 , displayed in new application window  2414  for the application with which Document  1   2416  is associated (e.g., if document  1  is a word processing document, then the application associated with application window  2414  is a word processing document creation application). Application window  2414  is, optionally, displayed over window  2404 . The application with which Document  1   2416  is associated is, optionally, different from the application with which window  2404  is associated (e.g., Document  1  is associated with a word processing creation application and window  2404  is a window of an email application). In some embodiments, Document  1   2416  is editable by the user while displayed in application window  2414 . In some embodiments, Document  1   2416  is displayed in application window  2414  after liftoff of contact  2412  is detected. For example, in  FIG. 5C , the device has detected a liftoff of contact  2412 , and Document  1   2416  is displayed after (or in response to) the liftoff of contact  2412 . 
     While Document  1   2416  is displayed in application window  2414 , focus is, optionally, taken away from Document  1   2416  in application window  2414 . For example, in  FIG. 5D , the device detects a gesture including movement of contact  2418  across touch-sensitive surface  451  to the location of contact  2418  in  FIG. 5E  and in response to detecting movement of contact  2418 , the device moves cursor  2410  across display  450 . In  FIG. 5E , the device detects an increase in the intensity of contact  2418  from an intensity below IT L  to an intensity above IT L  and in response to detecting the increase in intensity of contact  2418 , of the device moves focus away from application window  2414 . In response to detection of the gesture including the increase in intensity of contact  2418 , Document  1   2416  remains displayed in application window  2414  (e.g., the application associated with Document  1  does not cease to be displayed solely based on focus being shifted to a different element in the user interface). 
       FIGS. 5F-5G  shows a gesture including contact  2420  (e.g., a tap-and-hold gesture) detected on touch-sensitive surface  451  while cursor  2410  is located over icon  2408 - 1 . The gesture includes detecting an increase in intensity of contact  2420  on touch-sensitive surface  451  from an intensity below a deep press intensity threshold (e.g., “IT D ”) to an intensity above the deep press intensity threshold (e.g., “IT D ”). The contact has an intensity that is determined by the device throughout the gesture. The contact in gesture  2420  is determined to have reached an intensity during the gesture that is above the deep press intensity threshold (e.g., “IT D ”). 
     In response to the detection of the gesture including contact  2420  and in accordance with the determination that contact  2420  reached an intensity during the gesture that is above the deep press intensity threshold (e.g., “IT D ”), preview  2424  of Document  1   2416  is displayed in preview interface  2422 , and application window  2414  with Document  1   2416  is not displayed, as shown in  FIG. 5H . Preview interface  2422  is, optionally, a pop-up window. 
     In some embodiments, an animation showing a transformation of icon  2408 - 1  to preview interface  2422  is displayed. For example,  FIGS. 5F-5H  shows, in response to the detection of the gesture that includes the increase in intensity of contact  2420  from an intensity below the deep press intensity threshold (e.g., “IT D ”) to an intensity above the deep press intensity threshold (e.g., “IT D ”), the device expands icon  2408 - 1  into preview interface  2422 , showing an animation that includes one or more intermediate stages  2421 . The progression of the expansion animation is, optionally, determined in accordance with the intensity of contact  2420  in the gesture. For example, the higher the intensity of the contact (while remaining above the deep press intensity threshold), the faster the animation progresses. Alternatively, the progression of the transformation animation is mapped to various intensity values. As the intensity of contact  2420  increases through the various intensity values, the animation progresses, and the animation is reversed if the intensity decreases below the intensity values. 
     In some embodiments, preview  2424  is displayed in preview interface  2422  before liftoff of contact  2420  is detected. For example, in  FIGS. 5F-5H , contact  2420  continues to be detected on touch-sensitive surface  451  as preview interface  2422  is displayed in response to detection of the gesture including the increase in intensity of contact  2420 . 
     In some embodiments, preview interface  2422 , in which preview  2424  is displayed, is associated with a preview application for previewing documents associated with multiple different applications (e.g., the preview application can display read-only views of word processing documents, presentation documents, PDFs and spreadsheet documents). The preview application is different from the application with which application window  2414  is associated. For example, if Document  1   2416  is a presentation document, then application window  2414  is a window of a presentation application, and preview interface  2422  is an interface of a preview application that is configured to read the presentation document as well as other types of documents (e.g., word processing documents, PDFs and spreadsheet documents). In some embodiments, the preview application does not enable editing of Document  1   2416  while it is displayed as preview  2424  (e.g., Document  1   2416  is read-only while displayed as preview  2424  in preview interface  2422 ), and the application associated with application window  2414  does allow editing of Document  1   2416  while displayed in application window  2414 . In some embodiments, the application associated with application window  2414  has a set of document editing capabilities, and the preview application is missing one or more of the set of document editing capabilities (e.g., the preview application provides limited editing capabilities compared to the “full set” of editing capabilities provided by the application associated with application window  2414 ). 
     While preview  2424  is displayed in preview interface  2422 , focus is, optionally, taken away from preview  2424  in preview interface  2422 . For example, in Figure SI, the device detects a tap gesture including detecting contact  2426  on touch-sensitive surface  451 . In response to the detection of the tap gesture while cursor  2410  is at a location on display  450  that is remote from preview interface  2422 , the device moves focus away from preview window  2422  and ceases to display preview interface  2422  and preview  2424 , as shown in  FIG. 5J . 
       FIGS. 5J-5L  illustrate a gesture including movement of contact  2428  across touch-sensitive surface  451  and a press input including an increase in intensity of contact  2428  from an intensity below the deep press intensity threshold (e.g., “IT D ”) to an intensity above the deep press intensity threshold (e.g., “IT D ”) while cursor  2410  is located over icon  2408 - 1 . In response to detecting movement of contact  2428  upward and to the left on touch-sensitive surface while contact  2428  has an intensity between IT 0  and IT L  the device moves cursor  2410  upward and to the left on display. In response to the detection of intensity of the contact increase in intensity of contact  2428  from an intensity below the deep press intensity threshold (e.g., “IT D ”) to an intensity above the deep press intensity threshold (e.g., “IT D ”), the device changes the appearance of icon  2408 - 1  to indicate that preview  2424  will be displayed in response to detection of an end of the gesture (e.g., liftoff of contact  2428 ). For example, the change in appearance includes decreasing the size of icon  2408 - 1 , as shown in  FIG. 5L . The size decrease is, optionally, displayed as an animation in which the progression of the animation is determined in accordance with the intensity of the contact (e.g., icon  2408 - 1  decreases in size more as the intensity increases above IT D ). As the intensity of contact  2428  decreases toward a liftoff (and thus the end of the gesture), icon  2408 - 1  is animated to transform into preview interface  2422  with preview  2424 , as shown in  FIGS. 5M-5O . 
     In some embodiments, document icons  2408 - 1  and  2408 - 2  are not displayed within a document, and the corresponding documents are not embedded in another document. For example, document icons  2408 - 1  and  2408 - 2  are, optionally, displayed on a desktop user interface or in a listing of files in a folder; document icons  2408 - 1  and  2408 - 2  optionally represent respective shortcuts to the corresponding documents or the documents themselves. 
       FIGS. 5P-5S  illustrate an example of the user interfaces described above with reference to  FIGS. 5A-5O  implemented on a device with a touch-sensitive display  2430  (e.g., device  100  with touch screen  112 ).  FIG. 5P  shows document icons  2408 - 1  and  2408 - 2  displayed in document  2406 , on touch-sensitive display  2430 . A gesture including an increase in intensity of contact  2432  from an intensity below the light press intensity threshold (e.g., “IT L ”) to an intensity above the light press intensity threshold (e.g., “IT L ”) is detected on touch-sensitive display  2430  while a focus selector (e.g., contact  2432 ) is over icon  2408 - 1 . Contact  2432  in the gesture is determined to have a maximum intensity that is below the deep press intensity threshold (e.g., “IT D ”). In response to the detection of the gesture including contact  2432  and in accordance with the determination that the maximum intensity of the contact  2432  is below the deep press intensity threshold (e.g., “IT D ”), the device displays application window  2414  with Document  1   2416  on touch-sensitive display  2430 , as shown in  FIG. 5Q . 
       FIG. 5R  shows document icons  2408 - 1  and  2408 - 2  displayed in document  2406 , on touch-sensitive display  2430 . A gesture including an increase in intensity of contact  2434  from an intensity below the light press intensity threshold (e.g., “IT L ”) to an intensity above the light press intensity threshold (e.g., “IT L ”) detected on touch-sensitive display  2430  while a focus selector (e.g., contact  2434 ) is over  2408 - 1 . Contact  2434  in the gesture is determined to have reached an intensity during the gesture that is above the deep press intensity threshold (e.g., “IT D ”). In response to the detection of the gesture including contact  2434  and in accordance with the determination that the contact  2434  in the gesture reached an intensity during the gesture that is above the deep press intensity threshold (e.g., “IT D ”), preview interface  2422  and preview  2424  are displayed on display  2430 , as shown in  FIG. 5S . 
       FIGS. 6A-6C  are flow diagrams illustrating a method  2500  of previewing content in accordance with some embodiments. The method  2500  is performed at an electronic device (e.g., device  300 ,  FIG. 3 , or portable multifunction device  100 ,  FIG. 1A ) with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface. In some embodiments, the display is a touch screen display and the touch-sensitive surface is on the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations in method  2500  are, optionally, combined and/or the order of some operations are, optionally, changed. 
     As described below, the method  2500  provides an intuitive way to preview content. The method reduces the cognitive burden on a user when previewing content, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to preview content faster and more efficiently conserves power and increases the time between battery charges. 
     The device displays ( 2502 ) a plurality of document icons, including a respective document icon corresponding to a respective electronic document associated with a respective application. For example, document icons  2408 - 1  and  2408 - 2  are displayed on display  450  or touch-sensitive display  2430 , as shown in  FIG. 5A or 5P . Document icon  2408 - 1  corresponds to Document  1   2416 , which is associated with an application (e.g., Document  1  is a word processing document associated with a word processing document creation application, or Document  1  is a presentation document associated with a presentation document creation application). 
     While a focus selector (e.g., a selection box, a cursor, or a representative point corresponding to a contact such as a finger contact or a stylus contact) is over the respective document icon, the device detects ( 2504 ) a gesture that includes a contact on the touch-sensitive surface. For example, while cursor  2410  is located over icon  2408 - 1 , the gesture including the increase in intensity of contact  2412  in  FIGS. 5B-5C  (or the gesture including the increase in intensity of contact  2420  in  FIGS. 5F-5H ) is detected on touch-sensitive surface  451 . As another example, the gesture including the increase in intensity of contact  2432  in  FIGS. 5P-5Q  (or the gesture including the increase in intensity of contact  2434  in  FIGS. 5R-5S ) is detected on touch-sensitive display  2430  while the contact that increases in intensity during the gesture (e.g., contact  2432  or contact  2434 , respectively) is over icon  2408 - 1 . 
     In response ( 2506 ) to detecting the gesture, in accordance with a determination that the contact had a maximum intensity during the gesture that was below a respective intensity threshold (e.g., “IT D ”), the device displays ( 2508 ) the electronic document in a new application window of the respective application. For example, in response to the detection of the gesture that includes the increase in intensity of contact  2412  and in accordance with the determination that contact  2412  had a maximum intensity during the gesture that is below the intensity threshold, Document  1   2416  is displayed in application window  2414 , as shown in  FIG. 5C . In response to the detection of the gesture that includes the increase in intensity of contact  2432  and in accordance with the determination that contact  2432  had a maximum intensity during the gesture that is below the intensity threshold, Document  1   2416  is displayed in application window  2414 , as shown in  FIG. 5Q . In some embodiments, the respective electronic document is ( 2510 ) displayed in the new window of the respective application after detecting liftoff of the contact on the touch-sensitive surface. For example, Document  1   2416  is displayed in application window  2414  after detecting liftoff of contact  2412  as shown in  FIG. 5C  (or after liftoff of contact  2432 , as shown in  FIG. 5Q ). 
     In response ( 2506 ) to detecting the gesture, in accordance with a determination that the contact reached an intensity during the gesture that was above the respective intensity threshold (e.g., “IT D ”), the device displays ( 2512 ) a preview of the respective electronic document without displaying a new application window of the respective application. For example, in response to the detection of the gesture that includes the increase in intensity of contact  2420  and in accordance with the determination that contact  2420  had reached an intensity during the gesture that is above the intensity threshold (e.g., “IT D ”), the device displays preview  2424  of Document  1   2416  in preview interface  2422 , as shown in  FIG. 5H . Similarly, in response to the detection of the gesture that includes the increase in intensity of contact  2434  and in accordance with the determination that contact  2434  had reached an intensity during the gesture that is above the intensity threshold, the device displays preview  2424  of Document  1   2416  in preview interface  2422 , as shown in  FIG. 5S . 
     In some embodiments, displaying the preview of the respective electronic document includes ( 2514 ) displaying an animation of the respective document icon transforming into the preview of the respective electronic document, and a progression of the animation is determined in accordance with intensity of the contact on the touch-sensitive surface (e.g., the animation progresses at a speed determined by contact intensity or the animation progresses through a plurality of intermediate states that are mapped to particular intensity thresholds, so that as the user presses down harder the animation progresses further toward displaying the preview and if the user reduces the intensity of the contact, the animation progresses back toward displaying the icon). For example,  FIGS. 5L-5O  show an animation of icon  2408 - 1  transforming into preview interface  2422 . The progression of the animation is, optionally, determined in accordance with the intensity of contact  2428 . In some embodiments, the preview of the electronic document is ( 2516 ) displayed prior to detecting liftoff of the contact from the touch-sensitive surface. For example,  FIGS. 5F-5H  show preview  2424  displayed while contact  2420  is still detected on touch-sensitive surface  451 . 
     In some embodiments, the device includes a preview application (e.g., Quick Look by Apple Inc., Gloobus Preview, or Windows Picture and Fax Viewer by Microsoft Inc.) for previewing documents associated with a plurality of different applications, the preview application is distinct from the respective application, and the preview of the electronic document is ( 2518 ) displayed in the preview application. For example, preview interface  2422  is an interface for a preview application, which is different from the application with which Document  1   2416  is associated. 
     In some embodiments, the respective application includes ( 2520 ) a plurality of document editing capabilities for editing the respective electronic document, and the preview application does not include a respective document editing capability of the plurality of document editing capabilities. For example, in the preview application content of the electronic document cannot be modified, whereas in the respective application, content of the electronic document can be modified. However, in some situations, the preview application provides limited document editing capabilities such as rotating, renaming, modifying metadata, etc. For example, Document  1   2416  displayed in application window  2414  in  FIGS. 5C-5E and 5Q  is, optionally, editable in accordance with the editing capabilities of the application with which Document  1   2416  is associated (e.g., a word processing document creation application), and preview  2424  in  FIGS. 5H-5I, 5O and 5S  is, optionally, read-only or editable in accordance with the editing capabilities of the preview application (e.g., a dedicated electronic document preview application) that is less than the editing capabilities of the application with which Document  1   2416  is associated. 
     In some embodiments, while detecting the contact on the touch-sensitive surface, the device determines ( 2522 ) that the contact has exceeded the respective intensity threshold (e.g., “IT D ”). In response to determining that the contact has exceeded the respective intensity threshold (e.g., “IT D ”), the device changes ( 2524 ) an appearance of the document icon to indicate that a preview of the respective electronic document will be displayed in response to detecting an end of the gesture. For example,  FIGS. 5K-5L  show a gesture including an increase in intensity of contact  2428  detected on touch-sensitive surface  451 . In  FIG. 5L , contact  2428  is determined to exceed the deep press intensity threshold (e.g., “IT D ”), and in response, the device changes the appearance of icon  2408 - 1  by reducing the size of icon  2408 - 1 , as shown in  FIG. 5L . In some embodiments, changing an appearance of the document icon includes ( 2526 ) displaying an animation of the document icon growing smaller, where a progression of the animation is determined in accordance with an intensity of the contact. As shown in  FIG. 5L , for example, icon  2408 - 1  decreases in size. In some embodiments, how much icon  2408 - 1  decreases in size is, optionally, determined in accordance with the intensity of the contact  2428 . In some embodiments, the device displays the icon gradually decreasing in size as the intensity of contact  2428  gradually increases through intensities above the deep press intensity threshold (e.g., “IT D ”). 
     In some embodiments, after detecting the gesture, the device detects ( 2528 ) a subsequent gesture that corresponds to moving focus away from a representation of the electronic document. In response ( 2530 ) to detecting the subsequent gesture, in accordance with a determination that the representation of the electronic document is the new application window in which the electronic document was opened, the device maintains ( 2532 ) the electronic document in the new application window. For example,  FIGS. 5D-5E  show a gesture including movement of contact  2418  across the touch-sensitive surface and a subsequent increase in intensity of contact  2418  from an intensity below the light press intensity threshold (e.g., “IT L ”) to an intensity above the light press intensity threshold (e.g., “IT L ”), that is detected on touch-sensitive surface  451 . The gesture shown in  FIGS. 5D-5E  that includes the movement and increase in intensity of contact  2418  takes focus away from Document  1   2416  in application window  2414 . However, in response to the detection of the gesture shown in  FIGS. 5D-5E  that includes the movement and increase in intensity of contact  2418 , Document  1   2416  remains displayed in application window  2414 , as shown in  FIG. 5E , where Document  1   2416  is still displayed in application window  2414  after detecting a press input including the increase in intensity of contact  2418 . In contrast, in some embodiments, in response to detecting the subsequent gesture ( 2530 ), in accordance with a determination that the representation of the electronic document is a preview of the electronic document, the device ceases ( 2534 ) to display the preview of the electronic document. For example,  FIGS. 5I-5J  show a tap gesture including detection of contact  2426  for less than a predefined time threshold detected on touch-sensitive surface  451 . The tap gesture in Figure SI that includes contact  2426  takes focus away from preview  2424  in preview interface  2422 . In response to the detecting the tap gesture that includes detection of contact  2426 , the device ceases to display preview  2424 , as shown in  FIG. 5J . 
     It should be understood that the particular order in which the operations in  FIGS. 6A-6C  have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., those listed in the fifth paragraph of the Description of Embodiments) are also applicable in an analogous manner to method  2500  described above with respect to  FIGS. 6A-6C . For example, the contacts, gestures, icons, intensity thresholds, focus selectors, and animations described above with reference to method  2500  optionally have one or more of the characteristics of the contacts, gestures, icons, intensity thresholds, focus selectors, and animations described herein with reference to other methods described herein (e.g., those listed in the fifth paragraph of the Description of Embodiments). For brevity, these details are not repeated here. 
     In accordance with some embodiments,  FIG. 7  shows a functional block diagram of an electronic device  2600  configured in accordance with the principles of the various described embodiments. The functional blocks of the device are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described embodiments. It is understood by persons of skill in the art that the functional blocks described in  FIG. 7  are, optionally, combined or separated into sub-blocks to implement the principles of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG. 7 , an electronic device  2600  includes a display unit  2602  configured to display a plurality of document icons, including a respective document icon corresponding to a respective electronic document associated with a respective application; a touch-sensitive surface unit  2604  configured to receive gestures that include contacts; one or more sensor units  2605  configured to detect intensity of contacts with the touch-sensitive surface unit  2604 ; and a processing unit  2606  coupled to the display unit  2602 , the touch-sensitive surface unit  2604 , and the sensor units  2605 . In some embodiments, the processing unit  2606  includes a detecting unit  2608 , a display enabling unit  2610 , a maintaining unit  2612 , a ceasing unit  2614 , a determining unit  2616 , and a changing unit  2618 . 
     The processing unit  2606  is configured to: while a focus selector is over the respective document icon, detect a gesture that includes a contact on the touch-sensitive surface unit  2604  (e.g., with the detecting unit  2608 ); and in response to detecting the gesture: in accordance with a determination (e.g., with the determining unit  2616 ) that the contact had a maximum intensity during the gesture that was below a respective intensity threshold, enable display of the electronic document in a new application window of the respective application (e.g., with the display enabling unit  2610 ); and in accordance with a determination (e.g., with the determining unit  2616 ) that the contact reached an intensity during the gesture that was above the respective intensity threshold, enable display of a preview of the respective electronic document without enabling display of a new application window of the respective application (e.g., with the display enabling unit  2610 ). 
     In some embodiments, enabling display of the preview of the respective electronic document includes enabling display of an animation of the respective document icon transforming into the preview of the respective electronic document, and a progression of the animation is determined in accordance with intensity of the contact on the touch-sensitive surface unit  2604  (e.g., with the display enabling unit  2610 ). 
     In some embodiments, the respective electronic document is displayed in the new window of the respective application after detecting liftoff of the contact on the touch-sensitive surface unit  2604 . 
     In some embodiments, the preview of the electronic document is displayed prior to detecting liftoff of the contact from the touch-sensitive surface unit  2604 . 
     In some embodiments, the device includes a preview application for previewing documents associated with a plurality of different applications, the preview application is distinct from the respective application, and the preview of the electronic document is displayed in the preview application. 
     In some embodiments, the respective application includes a plurality of document editing capabilities for editing the respective electronic document, and the preview application does not include a respective document editing capability of the plurality of document editing capabilities. 
     In some embodiments, the processing unit  2606  is configured to: after detecting the gesture, detect a subsequent gesture that corresponds to moving focus away from a representation of the electronic document (e.g., with the detecting unit  2608 ); and in response to detecting the subsequent gesture: in accordance with a determination that the representation of the electronic document is the new application window in which the electronic document was opened, maintain the electronic document in the new application window (e.g., with the maintaining unit  2612 ); and in accordance with a determination that the representation of the electronic document is a preview of the electronic document, cease to display the preview of the electronic document (e.g., with the ceasing unit  2614 ). 
     In some embodiments, the processing unit  2606  is configured to: while detecting the contact on the touch-sensitive surface unit  2604 , determine that the contact has exceeded the respective intensity threshold (e.g., with the determining unit  2616 ); and in response to determining that the contact has exceeded the respective intensity threshold, change an appearance of the document icon to indicate that a preview of the respective electronic document will be displayed in response to detecting an end of the gesture (e.g., with the changing unit  2618 ). 
     In some embodiments, changing an appearance of the document icon includes enabling display of an animation of the document icon growing smaller, wherein a progression of the animation is determined in accordance with an intensity of the contact. 
     The operations in the information processing methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to  FIGS. 1A and 3 ) or application specific chips. 
     The operations described above with reference to  FIGS. 6A-6C  are, optionally, implemented by components depicted in  FIGS. 1A-1B  or  FIG. 7 . For example, detection operation  2504 , and displaying operations  2508  and  2512  are, optionally, 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 (or whether rotation of the device) corresponds to a predefined event or sub-event, such as selection of an object on a user interface, or rotation of the device from one orientation to another. 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  optionally utilizes or calls 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 . 
     Previewing Content 
     Many electronic devices have user interfaces for browsing content items, such as photos. The content items are, optionally, organized into multiple sets of items. In some methods, to preview the items within a set, a user would need to first select and open the desired set of items as in opening a folder, and then preview the items in the set. This adds additional steps to the previewing process and can make the process tedious if the user is previewing items in multiple sets. The embodiments below improve on these methods by enabling a user to preview items within a set in accordance with movement and intensity of a contact. In the embodiments below, the sets of items are represented by frames displayed in a user interface. The user, using a finger contact, positions a focus selector over a desired frame and moves the focus selector across the frame. As the focus selector moves across the frame, previews of the items are displayed in sequence within the frame. The user may press harder with the contact when a particular preview is displayed to increase the size of that particular preview, and reduce the intensity of the press with the contact to reduce the size of the preview back to the previous size. 
       FIGS. 8A-8W  illustrate exemplary user interfaces for previewing content in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIGS. 9A-9C .  FIGS. 8A-8W  include intensity diagrams that show the current intensity of the contact on the touch-sensitive surface relative to a plurality of intensity thresholds including a deep press intensity threshold (e.g., “IT D ”) and a light press intensity threshold (e.g., “IT L ”). In some embodiments, operations similar to those described below with reference to “IT D ” are performed with reference to a different intensity threshold (e.g., “IT L ”). 
       FIG. 8A  illustrates user interface  5700  for an application displayed on display  450  (e.g., display  340 ) of a device (e.g., device  300 ). User interface  5700  is, optionally, an interface for a content application, such as an image viewer application or a presentation application. One or more frames  5702  are displayed in user interface  5700 . Each of the frames  5702  displayed in  FIG. 8A  corresponds to a set of multiple content items. The content items are, for example, photos or individual slides in a presentation. A set of multiple content items are, optionally, for example, a set of photos (e.g., a set of photos from a trip, a set of photos with a particular person as a subject, a set of photos with a common topic) or a presentation with multiple slides. For example, frame  5702 - 1  corresponds to content items  5704 . Frame  5702 - 2  corresponds to content items  5706 . Frame  5702 - 3  corresponds to content items  5708 . Frame  5702 - 4  corresponds to content items  5710 . 
     For each frame  5702  in  FIG. 8A , preview  5707  (e.g., a thumbnail) of an item from the corresponding set is, optionally, displayed in the respective frame. For example, preview  5707  of item  5706 - 1  is displayed in frame  5702 - 2 . Preview  5707  of item  5706 - 1  is, optionally, displayed at a size that fills up the entire frame  5702 - 2  (e.g., fill height or fill width of frame  5702 - 2 , depending on the aspect ratio of item  5706 - 1 ), with the possibility that parts of preview  5707  of item  5706 - 1  is, optionally, cropped by the boundaries of frame  5702 - 2 . 
     Cursor  5712  is displayed in user interface  5700 . Cursor  5712  is an example of a focus selector. In  FIG. 8A , cursor  5712  is positioned away from frames  5702 . Contact  5714  is detected on touch-sensitive surface  451 . A user is enabled to move contact  5714  on touch-sensitive surface  451  to move cursor  5712  to a position over frame  5702 - 2 , as shown in  FIG. 8B . 
     When cursor  5712  is positioned over frame  5702 - 2 , a preview mode is, optionally, activated for frame  5702 - 2 . While the preview mode for frame  5702 - 2  is activated, previews of items  5706  is, optionally, displayed in sequence, as described below. The previews are, optionally, displayed to fill up frame  5702 - 2  (with cropping as needed) or at their respective original aspect ratios (with letterboxing or pillarboxing as needed). Regardless of whether a preview is displayed to fill up frame  5702 - 2  or at the original aspect ratio, the size of the preview is constrained by the size of frame  5702 - 2  (hereinafter “frame size” for convenience) as defined by the boundaries of frame  5702 - 2 . For example,  FIG. 8B  shows preview  5707  of item  5706 - 1  displayed in its original aspect ratio, at a size limited by the frame size. 
     While cursor  5712  is located over frame  5702 - 2 , contact  5716  is detected on touch-sensitive surface  451 . It should be appreciated that contact  5716  is, optionally, a continuation of contact  5714  without an intervening liftoff of contact  5714 , or a new contact detected on touch-sensitive surface  451  after a liftoff of contact  5714 . 
     While cursor  5712  is located over frame  5702 - 2 , contact  5716  moves  5715  substantially (e.g., at most 20 degrees above or below the horizontal) laterally (e.g., from the right to the left, or vice versa) on touch-sensitive surface  451  in  FIGS. 8B-8C . In response to detection of the substantially lateral movement  5715  of contact  5716 , cursor  5712  moves across frame  5702 - 2  in a direction corresponding to movement  5715 , and preview  5707  of item  5706 - 2  is displayed at a size limited by the frame size, as shown in  FIG. 8C . Item  5706 - 2  is a next item from item  5706 - 1  within a sequence of items  5706 . The sequence of items are, optionally, ordered by any suitable criterion or criteria, such as chronologically based on the date/time the image was taken or last modified, or alphabetically based on filename. 
     As contact  5716  continues to move laterally  5717 , cursor  5712  continues to move in  FIGS. 8C-8D , in response to movement  5717 , across frame  5702 - 2  in accordance with movement  5717 , and additional item(s) in the sequence of items  5706  are displayed. For example,  FIG. 8D  shows preview  5707  of item  5706 - 3 , which is a next item from item  5706 - 2  in the sequence, displayed in frame  5702 - 2  in response to detection of continued lateral movement  5717  of contact  5716 . It should be appreciated that the “next” item described above is, optionally, a previous or a subsequent item in the sequence of items, depending on the lateral direction of the movement of contact  5716  that moves cursor  5712  across frame  5702 - 2 . 
     In some embodiments, the order in which the sequence of items is previewed depends on the position of the cursor relative to the right and left boundaries or edges of the frame. For example, items  5706  are, optionally, a chronologically ordered set of images, the left edge of frame  5702 - 2  corresponds to the beginning of the set, and the right edge of frame  5702 - 2  corresponds to the end of the set. As cursor  5712  is moved from right to left (or vice versa) across frame  5702 - 2 , previews of items  5706  are displayed in chronological order based on the direction of movement. Thus, in  FIGS. 8B-8D , with cursor  5712  starting nearer to the right edge of frame  5702 - 2 , items  5706 - 1  through  5706 - 3 , for which previews are displayed, are items that are in reverse chronological order within items  5706 . Thus, in some embodiments, moving cursor  5712  from right to left within frame  5702 - 2  causes items  5706  to be scanned in reverse order, while moving cursor  5712  from left to right within frame  5702 - 2  causes items  5706  to be scanned in order. 
       FIG. 8D  also shows contact  5716  ceasing to substantially move on touch-sensitive surface  451 . While contact  5716  is substantially stationary on touch-sensitive surface  451 , an increase in the intensity of contact  5716  is detected (e.g., from an intensity below IT L  to an intensity above IT D ), as shown in  FIGS. 8E-8G . In response to detection of the increase in intensity of contact  5716 , the size of preview  5707  of item  5706 - 3  is increased to a size larger than the frame size, as shown in  FIG. 8G . Preview  5707  of item  5706 - 3  is no longer limited by the frame size. In some embodiments, the size increase is, optionally, displayed as an animation. For example, an animation of preview  5707  of item  5706 - 3  expanding in size, an instant of which is shown in  FIG. 8F , is, optionally, displayed. The animation optionally follows the increase in the intensity of contact  5716 ; the size of preview  5707  increases as the intensity of contact  5716  increases, as shown in  FIGS. 8D-8G . 
     While preview  5707  of item  5706 - 3  is displayed at the larger size, the intensity of contact  5716  is, optionally, decreased (e.g., from an intensity above IT D  to an intensity below IT L ), as shown in  FIGS. 8H-8J . In response to detection of the decrease in intensity of contact  5716 , the size of preview  5707  of item  5706 - 3  is decreased back to the earlier size that was limited by the frame size, as shown in  FIG. 8J . In some embodiments, the size decrease is, optionally, displayed as an animation. For example, an animation of preview  5707  of item  5706 - 3  contracting in size, an instant of which is shown in  FIG. 8I , is, optionally, displayed. The animation optionally follows the decrease in the intensity of contact  5716 ; the size of preview  5707  decreases as the intensity of contact  5716  decreases, as shown in  FIGS. 8H-8J . 
     In the description above, contact  5716 , from movement  5715  through the decrease in intensity ( FIG. 8B  through  FIG. 8J ), is an unbroken contact. Thus, in some embodiments, contact  5716  is not lifted off from touch-sensitive surface  451  from the time of movement  5715  through the decrease in intensity. 
     In some embodiments, the decrease in intensity of contact  5716  includes a liftoff of contact  5716 . For example, returning to, and continuing from  FIG. 8H , while preview  5707  of item  5706 - 3  is displayed at the larger size, a decrease in the intensity of contact  5716 , including a liftoff of contact  5716 , is detected, as shown in  FIG. 8K . In response to the detection of the decrease in the intensity of contact  5716 , including the liftoff of contact  5716 , the size of preview  5707  of item  5706 - 3  is decreased back to the earlier size that was limited by the frame size, as shown in  FIG. 8L . In some embodiments an animation similar to that shown in  FIGS. 8H-8J  is displayed in response to detecting liftoff of contact  5716 . 
     While preview  5707  of item  5706 - 3  is displayed at the size larger than the frame size, as in  FIG. 8G , contact  5716  is, optionally, moved laterally on touch-sensitive surface  451  by the user. For example,  FIG. 8M  shows preview  5707  of item  5706 - 3  displayed at the larger size, as in  FIG. 8G .  FIG. 8M  shows contact  5716  moving  5718  rightward on touch-sensitive surface  451 . In some embodiments, preview  5707  of item  5706 - 3  remains displayed at the larger size in response to detection of movement  5718  of contact  5716 , as shown in  FIG. 8N , where movement  5718  did not change the item being previewed. Thus, in some embodiments, while preview  5707  is displayed at the larger size, scanning or scrolling of previews of items  5706  at the larger size is not available. 
     In contrast, in some embodiments, in response to detection of movement  5718  of contact  5716  in  FIG. 8M , cursor  5712  moves across frame  5702 - 2  in accordance with movement  5718 , and display of preview  5707  of item  5706 - 3  is replaced with display of preview  5707  of item  5706 - 2 , as shown in  FIG. 8O . Thus, in these embodiments, previews of items  5706  are, optionally, scanned or scrolled while displayed at the larger size like previews of items  5706  are, optionally, scanned within frame  5702 - 2 , as described above with reference to  FIGS. 8B-8D . 
       FIGS. 8P-8W  illustrates an example of the user interfaces described above implemented on a device (e.g., device  100 ) with a touch screen  112 .  FIG. 8P  illustrates user interface  5730  for an application displayed on touch screen  112  of a device (e.g., device  100 ). User interface  5730  is, optionally, an interface for a content application, such as an image viewer application or a presentation application. One or more frames  5732  are displayed in user interface  5730 . Each frame  5732  in  FIG. 8P  corresponds to a set of multiple content items. The content items are, for example, photos or individual slides in a presentation. A set of multiple content items are, optionally, a set of photos or a presentation with multiple slides. For example, frame  5732 - 1  corresponds to content items  5734 . Frame  5732 - 2  corresponds to content items  5736 . Frame  5732 - 3  corresponds to content items  5738 . Frame  5732 - 4  corresponds to content items  5740 . 
     For each frame  5732  in  FIG. 8P , a preview (e.g., a thumbnail) of an item from the corresponding set is, optionally, displayed in the respective frame. For example, preview  5737  of item  5736 - 1  is displayed in frame  5732 - 2 . Preview  5737  of item  5736 - 1  is, optionally, displayed at a size that fills up the entire frame  5732 - 2  (e.g., fill height or fill width of frame  5732 - 2 , depending on the aspect ratio of item  5736 - 1 ), with the possibility that parts of preview  5737  of item  5736 - 1  are, optionally, cropped off by the boundaries of frame  5732 - 2 . 
     Contact  5742  is detected on touch screen  112  over frame  5732 - 2 . In response to detection of contact  5742  over frame  5732 - 2 , a preview mode is, optionally, activated for frame  5732 - 2 , as shown in  FIG. 8Q . While the preview mode for frame  5732 - 2  is activated, previews of items  5736  are, optionally, displayed in sequence, as described below. The previews are, optionally, displayed to fill up frame  5732 - 2  (with cropping as needed) or at their respective original aspect ratios (with letterboxing or pillarboxing as needed). Regardless of whether a preview is displayed to fill up frame  5732 - 2  or at the original aspect ratio, the size of the preview is constrained by the size of frame  5732 - 2  (hereinafter “frame size” for convenience) as defined by the boundaries of frame  5732 - 2 . For example,  FIG. 8Q  shows preview  5737  of item  5736 - 1  displayed in its original aspect ratio, at a size limited by the frame size. 
     While contact  5742  is located over frame  5732 - 2 , contact  5742  moves  5744  substantially (e.g., at most 20 degrees above or below the horizontal) laterally (e.g., from the right to the left, or vice versa) on touch screen  112 . In response to detection of the substantially lateral movement of contact  5742 , preview  5737  of item  536 - 2  is displayed at a size limited by the frame size, as shown in  FIG. 8R . Item  536 - 2  is a next item from item  5736 - 1  within a sequence of items  5736 . The sequence of items is, optionally, ordered by any suitable criterion or criteria, such as chronologically based on the date/time the image was taken or last modified, or alphabetically based on filename. 
     As contact  5742  continues to move laterally  5746 , additional item(s) in the sequence of items  5736  are displayed. For example,  FIG. 8S  shows preview  5737  of item  5736 - 3 , which is a next item from item  5736 - 2  in the sequence, displayed in frame  5732 - 2  in response to detection of continued lateral movement  5744  of contact  5742 . It should be appreciated that the “next” item described above is, optionally, a previous or a subsequent item in the sequence of items, depending on the lateral direction of the movement of contact  5742  across frame  5732 - 2 . 
       FIG. 8S  also shows contact  5742  ceasing to substantially move on touch screen  112 . While contact  5742  is substantially stationary on touch screen  112 , an increase in the intensity of contact  5742  (e.g., from an intensity below IT L  to an intensity above IT D ) is detected, as shown in  FIGS. 8S-8U . In response to detection of the increase in intensity of contact  5742 , the size of preview  5737  of item  5736 - 3  is increased to a size larger than the frame size, as shown in  FIG. 8U . 
     While preview  5737  of item  5736 - 3  is displayed at the larger size, the intensity of contact  5742  is decreased (e.g., from an intensity above IT D  to an intensity below IT L ), as shown in  FIG. 8U-8W . In response to detection of the decrease in intensity of contact  5742 , the size of preview  5737  of item  5736 - 3  is decreased back to the earlier size that was limited by the frame size, as shown in  FIG. 8W . 
       FIGS. 9A-9C  are flow diagrams illustrating a method  5800  of previewing content in accordance with some embodiments. The method  5800  is performed at an electronic device (e.g., device  300 ,  FIG. 3 , or portable multifunction device  100 ,  FIG. 1A ) with a display and a touch-sensitive surface. In some embodiments, the display is a touch screen display and the touch-sensitive surface is on the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations in method  5800  are, optionally, combined and/or the order of some operations is, optionally, changed. 
     As described below, the method  5800  provides an intuitive way to preview content. The method reduces the cognitive burden on a user when previewing content, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to preview content faster and more efficiently conserves power and increases the time between battery charges. 
     The device displays ( 5802 ) a frame for previewing content, where the frame corresponds to a plurality of content items (e.g., digital photographs, videos, or other images). In some embodiments, the device displays ( 5804 ) a plurality of frames for previewing content, where each frame of the plurality of frames corresponds to a different plurality of content items (e.g., each frame of the plurality of frames corresponds to an album or event including a plurality of photos or videos). For example,  FIG. 8A  shows frames  5702  displayed in user interface  5700 . Frame  5702 - 1  corresponds to content items  5704 . Frame  5702 - 2  corresponds to content items  5706 . Frame  5702 - 3  corresponds to content items  5708 . Frame  5702 - 4  corresponds to content items  5710 . As another example,  FIG. 8P  shows frames  5732  displayed in user interface  5730 . Frame  5732 - 1  corresponds to content items  5734 . Frame  5732 - 2  corresponds to content items  5736 . Frame  5732 - 3  corresponds to content items  5738 . Frame  5732 - 4  corresponds to content items  5740 . 
     The device detects ( 5806 ) movement of a contact (e.g., a finger contact) across the touch-sensitive surface.  FIGS. 8B-8D , for example, shows movement  5715  and  5717  of contact  5716  detected on touch-sensitive surface  451 .  FIGS. 8Q-8S  shows movement  5744  and  5746  of contact  5742  detected on touch screen  112 . The device moves ( 5808 ) a focus selector (e.g., cursor  5712  in  FIGS. 8A-8O  or contact  5742  in  FIGS. 8P-8W ) across the frame in accordance with the movement of the contact across the touch-sensitive surface. In  FIGS. 8B-8D , in response to movement  5715  and  5717  of contact  5716  on touch-sensitive surface  451 , cursor  5712 , positioned over frame  5702 - 2 , is moved across frame  5702 - 2  in accordance with movement  5715  and  5717 . In  FIGS. 8Q-8S , in response to movement  5744  and  5746  of contact  5742  on touch screen  112 , contact  5742  is detected as moving across frame  5732 - 2  in accordance with movement  5744  and  5746 . In  FIGS. 8P-8Q , the position of contact  5742  on touch screen  112  is an analogue to the position of a cursor on a separate touch-sensitive surface. 
     The device sequentially displays ( 5810 ), in the frame, previews of respective content items in the plurality of content items in accordance with the movement of the focus selector across the frame, wherein a size of the previews is constrained to a size of the frame (e.g., scanning through a chronologically organized set of photos from a beginning of the set to the end of the set where the left edge of the frame is mapped to the beginning of the set and the right side of the frame is mapped to the end of the set). In  FIGS. 8B-8D , previews  5707  of items  5706 - 1 ,  5706 - 2  and  5706 - 3  are displayed in sequence in accordance with movement of cursor  5712  across frame  5702 - 2 , where the sizes of previews  5707  is limited by the size of frame  5702 - 2 . In  FIGS. 8Q-8S , previews  5737  of items  5736 - 1 ,  5736 - 2  and  5736 - 3  are displayed in sequence in accordance with movement of contact  5742  across frame  5732 - 2 , where the sizes of previews  5737  is limited by the size of frame  5732 - 2 . 
     While a respective preview of a respective content item is displayed in the frame at a first size, the device detects ( 5812 ) an increase in intensity of the contact. For example, in  FIGS. 8E-8G , while preview  5707  of item  5706 - 3  is displayed, an increase in the intensity of contact  5716  (e.g., from an intensity below IT L  in  FIG. 8E  to an intensity above IT D  in  FIG. 8G ) is detected. As another example, in  FIG. 8S-8U , while preview  5737  of item  5736 - 3  is displayed, an increase in the intensity of contact  5742  (e.g., from an intensity below IT L  in  FIG. 8S  to an intensity above IT D  in  FIG. 8U ) is detected. 
     In response to detecting the increase in intensity of the contact, the device increases ( 5814 ) the size of the respective preview to a second size larger than the size of the frame.  FIG. 8G , for example, shows preview  5707  of item  5706 - 3  increased to a size larger than the size of frame  5702 - 2  in response to detection of the increase in the intensity of contact  5716  (e.g., from an intensity below IT L  in  FIG. 8E  to an intensity above IT D  in  FIG. 8G ). As another example,  FIG. 8U  shows preview  5737  of item  5736 - 3  increased to a size larger than the size of frame  5732 - 2  in response to detection of the increase in the intensity of contact  5742  (e.g., from an intensity below IT L  in  FIG. 8S  to an intensity above IT D  in  FIG. 8U ). While the frames in  FIGS. 8B-8G  and  FIGS. 8Q-8U  are shown as being substantially smaller than the display, in some situations the frames will be larger (e.g., a size corresponding to half or three quarters of the display) and the respective preview will have a correspondingly larger size that is, in some circumstances, a “full size” of the content—sometimes called a “native resolution” of the content. In such situations, the first size will correspond to a full size of the content, while the second size will correspond to an enlarged or “zoomed in” size of the content that is larger than the “full size” of the content. 
     In some embodiments, increasing the size of the respective preview includes ( 5816 ) displaying an animation of the respective preview increasing in size in accordance with the intensity of the contact (e.g., the respective preview increases in size at a rate based on the intensity of the contact, or the respective preview is enlarged to a size corresponding to the current intensity of the contact). For example, the increase in the size of preview  5707  from  FIG. 8E  through  FIG. 8G  is, optionally, animated, and the animation optionally follows the increase in the intensity of contact  5716 , as shown in  FIGS. 8E-8G . 
     While displaying the respective preview at the second size, the device detects ( 5818 ) a decrease in intensity of the contact. For example,  FIG. 8H  shows detection of a decrease in the intensity of contact  5716  (e.g., from an intensity above IT D  in  FIG. 8H  to an intensity below IT L  in  FIG. 8J ) while preview  5707  of item  5706 - 3  is displayed at the larger size, and  FIG. 8V  shows detection of a decrease in the intensity of contact  5742  (e.g., from an intensity above IT D  in  FIG. 8U  to an intensity below IT L  in  FIG. 8W ) while preview  5737  of item  5736 - 3  is displayed at the larger size. 
     In some embodiments, the contact is ( 5820 ) a single unbroken contact from a point in time when the movement of the contact across the touch-sensitive surface is detected to a point in time when the decrease in intensity of the contact is detected. For example, contact  5716  as depicted in  FIGS. 8B-8H , from detection of movement  5715  to detection of the decrease in the intensity of contact  5716 , is unbroken. Contact  5742  as depicted in  FIGS. 8Q-8V , from detection of movement  5744  to detection of the decrease in the intensity of contact  5742 , is unbroken. 
     In some embodiments, detecting the decrease in intensity of the contact includes ( 5822 ) detecting liftoff of the contact. For example,  FIGS. 8H and 8K-8L  show a liftoff of contact  5716  detected as a decrease in the intensity of contact  5716 , and in response decreasing the size of preview  5707  of item  5706 - 3 . 
     In some embodiments, detecting the decrease in intensity of the contact includes ( 5824 ) detecting a decrease in intensity of the contact while continuing to detect the contact on the touch-sensitive surface.  FIGS. 8H-8J , for example, shows detection of the decrease in the intensity of contact  5716  (e.g., from an intensity above IT D  in  FIG. 8H  to an intensity below IT L  in  FIG. 8J ) while contact  5716  continues to be detected on touch-sensitive surface  451 .  FIGS. 8U-8W  shows detection of the decrease in the intensity of contact  5742  (e.g., from an intensity above IT D  in  FIG. 8U  to an intensity below IT L  in  FIG. 8W ) while contact  5742  continues to be detected on touch screen  112 . 
     In response to detecting the decrease in intensity of the contact, the device reduces ( 5826 ) the size of the respective preview to the first size. For example,  FIG. 8J  shows preview  5707  of item  5706 - 3  reduced back to the size limited by the size of frame  5702 - 2  in response to detection of the decrease in intensity of contact  5716 , and  FIG. 8W  shows preview  5737  of item  5736 - 3  reduced back to the size limited by the size of frame  5732 - 2  in response to detection of the decrease in intensity of contact  5742 . 
     In some embodiments, reducing the size of the respective preview includes ( 5828 ) displaying an animation of the respective preview decreasing in size in accordance with the intensity of the contact (e.g., the respective preview decreases in size at a rate based on the intensity of the contact, or the respective preview shrinks to a size corresponding to the current intensity of the contact). For example, the decrease in the size of preview  5707  from  FIG. 8H  through  FIG. 8J  is, optionally, animated, and the animation optionally follows the decrease in the intensity of contact  5716 . 
     In some embodiments, the device detects ( 5830 ) additional movement of the contact corresponding to lateral movement of the focus selector on the display. For example, while cursor  5712  is positioned over frame  5702 - 2 , contact  5716  optionally moves laterally, as in movement  5717  or  5718 , as shown in  FIGS. 8B-8D, 8M-8N . 
     In response ( 5832 ) to detecting the additional movement of the contact, in accordance with detecting the additional movement while displaying the respective preview at the first size (e.g., while the contact is below a respective intensity threshold), the device ceases ( 5834 ) to display the respective preview and sequentially displays, at the first size, previews of respective content items in the plurality of content items in accordance with the movement of the focus selector across the frame. For example, when cursor  5712  is moved across frame  5702 - 2  while preview  5707  of an item  5706  is displayed at a size limited by the frame size, previews of other items  5706  are displayed sequentially, as in the sequential display of previews of items  5706 - 1 ,  5706 - 2  and  5706 - 3  shown in  FIGS. 8B-8D . 
     In contrast, in accordance with detecting the additional movement while displaying the respective preview at the second size (e.g., while the contact is above a respective intensity threshold), the device maintains ( 5836 ) display of the respective preview on the display. For example, when cursor  5712  is moved across frame  5702 - 2 , in accordance with movement  5718  of contact  5716 , while preview  5707  of item  5706 - 3  is displayed at the larger size ( FIG. 8M ), display of preview  5707  at the larger size is, optionally, maintained, as shown in  FIG. 8N . 
     Alternatively, in accordance with detecting the additional movement while displaying the respective preview at the second size (e.g., while the contact is above a respective intensity threshold), the device ceases ( 5838 ) to display the respective preview and sequentially displays, at the second size, previews of respective content items in the plurality of content items in accordance with the movement of the focus selector across a region of the display corresponding to the frame (e.g., a region of the display that where the focus selector was displayed prior to the respective preview being enlarged to the second size). For example, in accordance with movement  5718  of contact  5716 , preview  5707  of previous or subsequent items in the sequence, such as item  5706 - 2 , is, optionally, displayed at the larger size, as shown in  FIG. 8O . 
     It should be understood that the particular order in which the operations in  FIGS. 9A-9C  have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., those listed in the fifth paragraph of the Description of Embodiments) are also applicable in an analogous manner to method  5800  described above with respect to  FIGS. 9A-9C . For example, the contacts, intensity thresholds, focus selectors, animations described above with reference to method  5800  optionally have one or more of the characteristics of the contacts, intensity thresholds, focus selectors, animations described herein with reference to other methods described herein (e.g., those listed in the fifth paragraph of the Description of Embodiments). For brevity, these details are not repeated here. 
     In accordance with some embodiments,  FIG. 10  shows a functional block diagram of an electronic device  5900  configured in accordance with the principles of the various described embodiments. The functional blocks of the device are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described embodiments. It is understood by persons of skill in the art that the functional blocks described in  FIG. 10  are, optionally, combined or separated into sub-blocks to implement the principles of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG. 10 , an electronic device  5900  includes a display unit  5902  configured to display a frame for previewing content, wherein the frame corresponds to a plurality of content items; a touch-sensitive surface unit  5904  configured to receive contacts; one or more sensor units  5905  configured to detect intensity of contacts with the touch-sensitive surface unit  5904 ; and a processing unit  5906  coupled to the display unit  5902 , the touch-sensitive surface unit  5904 , and the sensor units  5905 . In some embodiments, the processing unit  5906  includes a detecting unit  5908 , a moving unit  5910 , a display enabling unit  5912 , an increasing unit  5914 , a reducing unit  5916 , a ceasing unit  5918 , and a maintaining unit  5920 . 
     The processing unit  5906  is configured to detect movement of a contact across the touch-sensitive surface unit  5904  (e.g., with the detecting unit  5908 ); move a focus selector across the frame in accordance with the movement of the contact across the touch-sensitive surface unit  5904  (e.g., with the moving unit  5910 ); enable sequential display of, in the frame, previews of respective content items in the plurality of content items in accordance with the movement of the focus selector across the frame, wherein a size of the previews is constrained to a size of the frame (e.g., with the display enabling unit  5912 ); while a respective preview of a respective content item is displayed in the frame at a first size, detect an increase in intensity of the contact (e.g., with the detecting unit  5908 ); in response to detecting the increase in intensity of the contact, increase the size of the respective preview to a second size larger than the size of the frame (e.g., with the increasing unit  5914 ); while displaying the respective preview at the second size, detect a decrease in intensity of the contact (e.g., with the detecting unit  5908 ); and in response to detecting the decrease in intensity of the contact, reduce the size of the respective preview to the first size (e.g., with the reducing unit  5916 ). 
     In some embodiments, the contact is a single unbroken contact from a point in time when the movement of the contact across the touch-sensitive surface unit  5904  is detected to a point in time when the decrease in intensity of the contact is detected. 
     In some embodiments, detecting the decrease in intensity of the contact includes detecting liftoff of the contact. 
     In some embodiments, detecting the decrease in intensity of the contact includes detecting a decrease in intensity of the contact while continuing to detect the contact on the touch-sensitive surface unit  5904 . 
     In some embodiments, the processing unit  5906  is configured to enable display of a plurality of frames for previewing content, wherein each frame of the plurality of frames corresponds to a different plurality of content items (e.g., with the display enabling unit  5912 ). 
     In some embodiments, increasing the size of the respective preview includes displaying an animation of the respective preview increasing in size in accordance with the intensity of the contact. 
     In some embodiments, reducing the size of the respective preview includes displaying an animation of the respective preview decreasing in size in accordance with the intensity of the contact. 
     In some embodiments, the processing unit  5906  is configured to: detect additional movement of the contact corresponding to lateral movement of the focus selector on the display unit  5902  (e.g., with the detecting unit  5908 ); and in response to detecting the additional movement of the contact: in accordance with detecting the additional movement while displaying the respective preview at the first size, cease to display the respective preview (e.g., with ceasing unit  5918 ) and enable sequential display of, at the first size, previews of respective content items in the plurality of content items in accordance with the movement of the focus selector across the frame (e.g., with the display enabling unit  5912 ); and in accordance with detecting the additional movement while displaying the respective preview at the second size, maintain display of the respective preview on the display (with the maintaining unit  5920 ). 
     In some embodiments, the processing unit  5906  is configured to: detect additional movement of the contact corresponding to lateral movement of the focus selector on the display unit  5902  (e.g., with the detecting unit  5908 ); and in response to detecting the additional movement of the contact: in accordance with detecting the additional movement while displaying the respective preview at the first size, cease to display the respective preview (e.g., with ceasing unit  5918 ) and enable sequential display of, at the first size, previews of respective content items in the plurality of content items in accordance with the movement of the focus selector across the frame (e.g., with the display enabling unit  5912 ); and in accordance with detecting the additional movement while displaying the respective preview at the second size, cease to display the respective preview (e.g., with ceasing unit  5918 ) and enable sequential display of, at the second size, previews of respective content items in the plurality of content items in accordance with the movement of the focus selector across a region of the display unit  5902  corresponding to the frame (e.g., with the display enabling unit  5912 ). 
     The operations in the information processing methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to  FIGS. 1A and 3 ) or application specific chips. 
     The operations described above with reference to  FIGS. 9A-9C  are, optionally implemented by components depicted in  FIGS. 1A-1B  or  FIG. 10 . For example, detection operations  5806 ,  5812 , and  5818 , moving operation  5808 , displaying operation  5810 , increasing operation  5814 , and reducing operation  5826  are, optionally, implemented by event sorter  170 , event recognizer  180 , and event handler  190 . Event monitor  171  in event sorter  170  detects a contact on touch screen  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 (or whether rotation of the device) corresponds to a predefined event or sub-event, such as selection of an object on a user interface, or rotation of the device from one orientation to another. 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  optionally utilizes or calls 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 . 
     Displaying User Interface Objects Corresponding to an Application 
     At any one time, a user may have multiple windows for any one application opened, and not all of them are displayed. Some of these windows or documents are, optionally, minimized or hidden by other windows. Further, an application may have a recently opened documents history. In some methods, a user keeps track of the multiple windows by looking at a taskbar or opening a task list, both of which are, optionally, hidden at first. To look at a recently opened documents history for an application, the user has to open the application. These methods add additional steps for the user. The embodiments described below improve on these methods by providing a more efficient way to review currently opened windows and a history of recently opened documents. The user moves a focus selector over an application icon corresponding to the desired application and performs a gesture with a contact with an intensity that peaks above a threshold. In response, reduced-scale representations of currently opened windows for the application or of recently opened documents are displayed. Thus, the user is able to get a glance of currently opened windows and recently opened documents. 
       FIGS. 11A-11P  illustrate exemplary user interfaces for displaying user interface objects corresponding to an application in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in  FIGS. 12A-12B .  FIGS. 11A-11P  include intensity diagrams that show the current intensity of the contact on the touch-sensitive surface relative to a plurality of intensity thresholds including a light press intensity threshold (e.g., “IT L ”) and a deep press intensity threshold (e.g., “IT D ”). In some embodiments, operations similar to those described below with reference to “IT D ” are performed with reference to “a different intensity threshold (e.g., “IT L ”). 
       FIG. 11A  illustrates user interface  6000  (e.g., a graphical user interface desktop) displayed on display  450  (e.g., display  340 ) of a device (e.g., device  300 ). User interface  6000  includes one or more application icons  6002  displayed in predefined region  6004  (e.g., an application launch icon tray/dock/springboard) in user interface  6000 . Each of application icons  6002  corresponds to a respective application. For example, application icon  6002 - 2  corresponds to the application “App  2 ,” and application icon  6002 - 1  corresponds to the application “App  1 .” Cursor  6006  (for example, a mouse pointer) is also displayed in user interface  6000 . Cursor  6006  is an example of a focus selector. 
     In  FIG. 11A , a gesture that includes a press input that corresponds to an increase in intensity of contact  6008  from an intensity below a light press intensity threshold (e.g., “IT L ”) to an intensity above the light press intensity threshold (e.g., “IT L ”) is detected on touch-sensitive surface  451  (e.g., touchpad  355 ,  FIG. 3 ) of the device while cursor  6006  is displayed over application icon  6002 - 2 . One or more sensors for detecting the intensity of contacts on touch-sensitive surface  451  determine that the maximum intensity of contact  6008  during the press input is below a deep press intensity threshold (e.g., “IT D ”). The gesture ends with a reduction in intensity of contact  6008  below the light press intensity threshold (e.g., “IT L ”), as shown in  FIG. 11B . In some circumstances, the gesture ends with a liftoff of contact  6008 . 
     In response to the detection of the gesture, and in accordance with contact  6008  having a maximum intensity below the deep press intensity threshold (e.g., “IT D ”), application window  6010  of App  2  is displayed when the end of the gesture is detected, as shown in  FIG. 11B . Application window  6010  corresponds to application App  2 , which corresponds to application icon  6002 - 2 . Application window  6010  is, optionally, a new application window for App  2  (e.g., App  2  had no open windows when the end of the gesture that is performed with contact  6008  is detected, and thus a new application window is opened). 
       FIG. 11C  illustrates application icons  6002 , cursor  6006 , etc. displayed in user interface  6000 , as in  FIG. 11A . A gesture that includes a press input that corresponds to an increase in intensity of contact  6012  from an intensity below a deep press intensity threshold (e.g., “IT D ”) to an intensity above the deep press intensity threshold (e.g., “IT D ”) is detected on touch-sensitive surface  451  while cursor  6006  is displayed over application icon  6002 - 2 . The sensors for detecting the intensity of contacts on touch-sensitive surface  451  determine that the intensity of contact  6012  during the press input goes above the deep press intensity threshold (e.g., “IT D ”). The gesture ends with a reduction in intensity of contact  6012  below the light press intensity threshold (e.g., “IT L ”), as shown in  FIG. 11D . In some circumstances, the gesture ends with a liftoff of contact  6012 . In response to the detection of gesture, and in accordance with contact  6012  having an intensity that goes above the deep press intensity threshold (e.g., “IT D ”) during the gesture, one or more user interface objects corresponding to App  2  are displayed when the end of the gesture is detected. In some embodiments, the user interface objects are reduced-scale representations  6014  (e.g., thumbnails) of currently open (doesn&#39;t have to be currently displayed) application windows for App  2 , as shown in  FIG. 11D . The user optionally moves cursor  6006  to a position over one of these reduced-scale representations  6014  and perform a gesture (for example, a tap gesture) on touch-sensitive surface  451  to select the reduced-scale representation  6014  over which cursor  6006  is positioned. In response to the detection of that gesture corresponding to selection of one of the reduced-scale representations  6014 , the application window corresponding to the selected reduced-scale representation is displayed on display  450 . 
     In some embodiments, the user interface objects that are displayed in accordance with the contact having an intensity that was above the predefined threshold are reduced-scale representations of recently opened documents for the application, instead of reduced-scale representations of currently open application windows such as representations  6014 . As used herein, documents include images, text documents, word processor documents, spreadsheets, presentations, drawings, video clips, audio clips, and so on. Also, in some embodiments, the user interface objects are, optionally, displayed during the gesture, while the contact is still detected on touch-sensitive surface  451 , instead of being displayed when the end of the gesture is detected (with liftoff of the contact or a reduction in intensity of the contact below IT L ), as in  FIG. 11D . For example,  FIG. 11E  illustrates application icons  6002 , cursor  6006 , etc. displayed in user interface  6000 , as in  FIG. 11A .  FIGS. 11E-11H  illustrate detection of a gesture that includes a press input that corresponds to an increase in intensity of contact  6016  from an intensity below a light press intensity threshold (e.g., “IT L ”) in  FIG. 11E  to an intensity above a deep press intensity threshold (e.g., “IT D ”) in  FIG. 11H . The gesture performed with contact  6016  is detected on touch-sensitive surface  451  while cursor  6006  is displayed over application icon  6002 - 2  corresponding to App  2 . The sensors for detecting the intensity of contacts on touch-sensitive surface  451  determine that the intensity of contact  6016  peaked above the deep press intensity threshold (e.g., “IT D ”). Contact  6016  is maintained on touch-sensitive surface  451 . In response to the detection of the gesture, and in accordance with contact  6016  having an intensity that goes above the deep press intensity threshold (e.g., “IT D ”) during the gesture, reduced-scale representations  6018  (e.g., thumbnails) of recently opened documents for App  2  are displayed, as shown in  FIGS. 11F-11H . 
     In some embodiments, the display of representations  6018  includes an animation. For example, initially representation  6018 - 1  is displayed in proximity of application icon  6002 - 2 , as shown in  FIG. 11F . As the animation proceeds, representation  6018 - 1  moves upward and representation  6018 - 2  is displayed in proximity of application icon  6002 - 2 , as shown in  FIG. 11G . Then representations  6018 - 1  moves upward,  6018 - 2  move upward toward representation  6018 - 1 , and representation  6018 - 3  is displayed in proximity of application icon  6002 - 2 , as shown in  FIG. 11H . Representations  6018 - 1  thru  6018 - 3  form an array above icon  6002 - 2 . In some embodiments, the animation progresses in accordance with an intensity of contact  6016 , as shown in  FIGS. 11F-11G , where the representations  6018  appear and move upwards as the intensity of contact  6016  increases toward the deep press intensity threshold (e.g., “IT D ”). 
     The user optionally moves cursor  6006  to a position over one of these reduced-scale representations  6018  and performs a gesture (for example, a tap gesture) on touch-sensitive surface  451  to select the reduced-scale representation  6018  over which cursor  6006  is positioned. In response to that gesture, the document corresponding to the selected representation  6018  is opened and displayed on display  450  in an application window for App  2  (the application corresponding to icon  6002 - 2 ). 
     In some embodiments, user interface objects corresponding to an application, such as reduced-scale representations of application windows or recently opened documents, are, optionally, displayed in predefined region  6004  (e.g., an application launch region such as an application dock).  FIGS. 11I-11L  illustrate detection of a gesture that includes a press input that corresponds to an increase in intensity of contact  6020  from an intensity below a light press intensity threshold (e.g., “IT L ”) in  FIG. 11I  to an intensity above a deep press intensity threshold (e.g., “IT D ”) in  FIG. 11L . The gesture performed with contact  6020  is detected on touch-sensitive surface  451  while cursor  6006  is displayed over application icon  6002 - 2  corresponding to App  2 . The sensors for detecting the intensity of contacts on touch-sensitive surface  451  determine that the intensity of contact  6020  peaked above the deep press intensity threshold (e.g., “IT D ”). Contact  6020  is maintained on touch-sensitive surface  451 . In response to the detection of the gesture, and in accordance with contact  6020  having an intensity that goes above the deep press intensity threshold (e.g., “IT D ”) during the gesture, reduced-scale representations  6022  (e.g., thumbnails) of recently opened documents for App  2  are displayed, as shown in  FIGS. 11J-11L . 
     In some embodiments, the display of representations  6022  includes an animation. For example, icons  6002  are animated in a way that give an illusion of shifting backwards into display  450 . With icons  6002  shifted backward, representation  6022 - 4  is displayed in predefined region  6004  in proximity of application icon  6002 - 2 , as shown in  FIG. 11J . As the animation proceeds, representation  6022 - 4  moves toward the right end of predefined region  6004  and representation  6022 - 3  is displayed in predefined region  6004  in proximity of application icon  6002 - 2 , as shown in  FIG. 11K . Then representations  6022 - 3  moves toward representation  6022 - 4 , and the other representations  6022 - 2  and  6022 - 1  are displayed in predefined region  6004  in a similar manner. The animation ends with representations  6022  displayed in region  6004  in front of application icons  6002 , as shown in  FIG. 11L . In some embodiments, the animation progresses in accordance with an intensity of contact  6020 , as shown in  FIGS. 11I-11L , where the representations  6022  appear and move along the predefined region  6004  as the intensity of contact  6016  increases toward the deep press intensity threshold (e.g., “IT D ”). 
     It should be appreciated that the ways in which the user interface objects are displayed, as described above with reference to  FIGS. 11A-11L , are merely exemplary. The user interface objects are, optionally, displayed in other sizes, positions, and so on. 
       FIGS. 11M-11P  illustrate an example of the user interfaces described above, with reference to  FIGS. 11A-11L , implemented on a device (e.g., device  100 ) with a touch-sensitive display (e.g., touch screen  112 ).  FIG. 11M  illustrates user interface  6030  (e.g., a graphical user interface desktop) displayed on touch screen  112  of a device (e.g., device  100 ). User interface  6030  includes one or more application icons  6032  displayed in predefined region  6034  (e.g., an application launch icon tray/dock/springboard) in user interface  6030 . In some embodiments, each of application icons  6034  corresponds to a respective application. For example, application icon  6032 - 2  corresponds to the application “App  2 ,” and application icon  6032 - 1  corresponds to the application “App  1 .” 
     In  FIG. 11M , a gesture that includes a press input that corresponds to an increase in intensity of contact  6038  from an intensity below a light press intensity threshold (e.g., “IT L ”) to an intensity above the light press intensity threshold (e.g., “IT L ”) is detected on touch-sensitive display  112  of the device at a location corresponding to application icon  6032 - 2 . One or more sensors for detecting the intensity of contacts on touch-sensitive display  112  determine that the maximum intensity of contact  6038  during the press input is below the deep press intensity threshold (e.g., “IT D ”). The gesture ends with a reduction in intensity of contact  6038  below the light press intensity threshold (e.g., “IT L ”), as shown in  FIG. 11N . In some circumstances, the gesture ends with a liftoff of contact  6038 . 
     In response to the detection of the gesture, and in accordance with contact  6038  having a maximum intensity below the deep press intensity threshold (e.g., “IT D ”), application window  6040  of App  2  is displayed when the end of the gesture is detected. Application window  6040  corresponds to application App  2 , which corresponds to application icon  6032 - 2 . Application window  6040  is, optionally, a new application window for App  2  (e.g., App  2  had no open windows when the end of the gesture performed with contact  6038  is detected, and thus a new application window is opened). 
       FIG. 11O  illustrates application icons  6032 , etc. displayed in user interface  6030 , as in  FIG. 11M . A gesture that includes a press input that corresponds to an increase in intensity of contact  6042  from an intensity below a deep press intensity threshold (e.g., “IT D ”) to an intensity above the deep press intensity threshold (e.g., “IT D ”) is detected on touch-sensitive display  112  at a location corresponding to application icon  6032 - 2 . The sensors for detecting the intensity of contacts on touch-sensitive display  112  determine that the intensity of contact  6042  during the press input goes above the deep press intensity threshold (e.g., “IT D ”). The gesture ends with a reduction in intensity of contact  6042  below the light press intensity threshold (e.g., “IT L ”), as shown in  FIG. 11P . In some circumstances, the gesture ends with a liftoff of contact  6042 . 
     In response to the detection of gesture, and in accordance with contact  6042  having an intensity that goes above the deep press intensity threshold (e.g., “IT D ”) during the gesture, one or more user interface objects corresponding to App  2  are displayed when the end of the gesture is detected. In some embodiments, the user interface objects are reduced-scale representations  6044  (e.g., thumbnails) of currently open (doesn&#39;t have to be currently displayed) application windows for App  2 , as shown in  FIG. 11P . The user optionally performs a gesture (e.g., a tap gesture) on touch-sensitive display  112  at a location corresponding to one of these reduced-scale representations  6044  to select the reduced-scale representation  6044  over which the gesture is performed. In response to the detection of that gesture corresponding to selection of one of the reduced-scale representations  6044 , the application window corresponding to the selected reduced-scale representation is displayed on touch-sensitive display  112 . 
       FIGS. 12A-12B  are flow diagrams illustrating a method  6100  of displaying user interface objects corresponding to an application in accordance with some embodiments. The method  6100  is performed at an electronic device (e.g., device  300 ,  FIG. 3 , or portable multifunction device  100 ,  FIG. 1A ) with a display and a touch-sensitive surface. In some embodiments, the display is a touch screen display and the touch-sensitive surface is on the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations in method  6100  are, optionally, combined and/or the order of some operations is, optionally, changed. 
     As described below, the method  6100  provides an intuitive way to display user interface objects corresponding to an application. The method reduces the cognitive burden on a user when displaying user interface objects corresponding to an application, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to display user interface objects corresponding to an application faster and more efficiently conserves power and increases the time between battery charges. 
     The device displays ( 6102 ) a plurality of application icons, where the plurality of application icons includes a respective application icon corresponding to a respective application.  FIGS. 11A-11L  show, for example, application icons  6002  displayed on display  450 . Application icon  6002 - 2  corresponds to application “App  2 .” As another example,  FIGS. 11M-11P  show application icons  6032  displayed on touch-sensitive display  112 . Application icon  6032 - 2  corresponds to application “App  2 .” 
     While a focus selector (e.g., cursor  6006  in  FIG. 11A  or contact  6038  in  FIG. 11M ) is over the respective application icon, the device detects ( 6104 ) a gesture that includes a contact (e.g., a finger contact) on the touch-sensitive surface. As shown in  FIG. 11A , for example, a gesture that includes contact  6008  is detected on touch-sensitive surface  451  while cursor  6006  is over application icon  6002 - 2 . As another example, in  FIG. 11C , a gesture that includes contact  6012  is detected on touch-sensitive surface  451  while cursor  6006  is over application icon  6002 - 2 . In  FIG. 11M , a gesture that includes contact  6038  is detected on touch-sensitive display  112  at a location over application icon  6032 - 2 . 
     In response to detecting the gesture ( 6106 ), in accordance with a determination that the contact had a maximum intensity during the gesture that was below a respective intensity threshold (e.g., “IT D ”), the device displays ( 6108 ) an application window of the respective application. For example, in  FIG. 11A , contact  6008  is determined to have a maximum intensity during the gesture that is below the deep press intensity threshold (e.g., “IT D ”). In accordance with that determination, in response to detecting the gesture performed with contact  6008 , application window  6010  of App  2  is displayed, as shown in  FIG. 11B . In some embodiments, the application window is a new application window that was not displayed on the display prior to detecting the contact (e.g., the new application window was not displayed on the display immediately prior to detecting the contact) ( 6110 ). For example, the new application window is an application window that was created by the application in response to detecting the gesture. For example, when a user opens a web browser, a new browser window is typically opened. Similarly, when a user opens a word processing application, a blank word processing document is typically opened. As another example, when a user requests that an image be opened, a new window including the image is typically opened. For example, application window  6010  ( FIG. 11B ) or  6040  ( FIG. 11N ) is, optionally, new application window if there were no open (displayed or not) windows for App  2  prior to detection of the gesture performed with contact  6008  or  6038 , respectively. 
     In contrast, in accordance with a determination that the contact reached an intensity during the gesture that was above the respective intensity threshold (e.g., “IT D ”), the device displays ( 6112 ) a plurality of user interface objects that correspond to the respective application. In  FIG. 11C , the intensity of contact  6012  is determined to have reached above the deep press intensity threshold (e.g., “IT D ”) during the gesture. In accordance with that determination, in response to detecting the gesture performed with contact  6012 , one or more user interface objects corresponding to App  2  (e.g., reduced-scale representations  6014  of application windows for App  2 ) are displayed, as shown in  FIG. 11D . As another example, reduced-scale representations  6018  ( FIG. 11H ) or  6022  ( FIG. 11L ) of recently opened documents for App  2  are also examples of user interface objects displayed in response to detection of a gesture that includes a contact (e.g., contact  6016 ,  FIG. 11E ; contact  6020 ,  FIG. 11I ) with an intensity that goes above the deep press intensity threshold (e.g., “IT D ”). 
     As another example, in  FIG. 11M , contact  6038  is determined to have a maximum intensity during the gesture that is below deep press intensity threshold (e.g., “IT D ”). In accordance with that determination, in response to detecting the gesture performed with contact  6038 , application window  6040  of App  2  is displayed, as shown in  FIG. 11N . In  FIG. 11O , the intensity of contact  6042  is determined to have reached above the deep press intensity threshold (e.g., “IT D ”) during the gesture. In accordance with that determination, in response to detecting the gesture performed with contact  6042 , one or more user interface objects corresponding to App  2  (e.g., reduced-scale representations  6044  of application windows for App  2 ) are displayed, as shown in  FIG. 11P . 
     In some embodiments, the plurality of user interface objects includes ( 6114 ) reduced-scale representations of currently open application windows for the application. (e.g., thumbnail images of the currently open application windows). For example, the user interface objects displayed in response to the detection of the gesture performed with contact  6012  are reduced-scale representations  6014  of currently open application windows for App  2  ( FIG. 11D ). As another example, the user interface objects displayed in response to the detection of the gesture performed with contact  6042  are reduced-scale representations  6044  of currently open application windows for App  2  ( FIG. 11P ). In some embodiments, the plurality of user interface objects include ( 6116 ) reduced-scale representations of recently opened documents for the respective application. (e.g., thumbnails of the first page or the current page of the recently opened documents). For example, the user interface objects displayed in response to the detection of the gesture performed with contact  6016  are reduced-scale representations  6018  of recently opened documents for App  2  ( FIG. 11H ). 
     In some embodiments, the plurality of application icons are displayed ( 6118 ) in a predefined region of the display (e.g., an application launch icon tray/dock/springboard) prior to detecting the gesture, and the plurality of user interface objects are displayed in the predefined region of the display. Application icons  6002  in  FIGS. 11I-11L , for example, are displayed in predefined region  6004  prior to detection of a contact on touch-sensitive surface  451 , and the user interface objects that correspond to the respective application (for example, representations  6022 ,  FIG. 11L ) are, optionally, displayed in predefined region  6004  as well. In some embodiments, the plurality of user interface objects are displayed ( 6120 ) in front of and at least partially overlapping one or more of the plurality of application icons in the predefined region of the display. For example, reduced-scale representations  6022  that correspond to the respective application (e.g., App  2  in  FIG. 11L ) are displayed in front of and partially overlapping application icons  6002 . 
     In some embodiments, displaying the plurality of user interface objects corresponding to the respective application includes ( 6122 ) displaying an animation of the plurality of application icons shifting backward into the display (e.g., show the plurality of application icons getting smaller with a change in shading and position to provide the illusion that the application icons are moving backward into the display), and displaying the plurality of user interface objects corresponding to the respective application in a location on the display previously occupied by the plurality of application icons (e.g., display the user interface objects in front of the plurality of application icons). For example,  FIGS. 11J-11L  show instances in an animation of application icons  6002  shifting backwards and representations  6022  being displayed in the area that were occupied by application icons  6002 . 
     In some embodiments, displaying the plurality of user interface objects corresponding to the respective application includes ( 6124 ), for a respective user interface object associated with the respective application, initially displaying the respective user interface object at a location proximate to the respective application icon (e.g., the respective user interface object appears near the respective application icon), and after initially displaying the respective user interface object, displaying an animation of the respective user interface object moving from the location proximate to the respective application icon to a location proximate to another user interface object in the plurality of user interface objects (e.g., after appearing near the respective application icon, the respective user interface object moves towards other previously displayed user interface objects). For example, successive thumbnails of recently opened documents appear near the application icon for the application to which they correspond and then move (e.g., fly over) to form an array of thumbnails in a predefined region of the display (e.g., the dock). For example,  FIG. 11K  shows representation  6022 - 3  displayed near application icon  6002 - 2 . Representation  6022 - 3  moves toward representation  6022 - 4  and ends up near representation  6022 - 4 , as shown in  FIG. 11L . 
     In some embodiments, the application window of the respective application is displayed ( 6126 ) when an end of the gesture is detected (e.g., the application window is initially displayed immediately after detecting liftoff of the contact), and the plurality of user interface objects corresponding to the respective application are displayed during the gesture in response to detecting that the intensity of the contact exceeds the respective intensity threshold (e.g., the plurality of objects are initially displayed while still detecting the contact on the touch-sensitive surface). For example, application window  6010  in  FIG. 11B  is, optionally, displayed when contact  6008  is lifted off, and representations  6018  are displayed while contact  6016  is still detected on touch-sensitive surface  451  as shown in  FIG. 11H . 
     In some embodiments, the application window of the respective application is displayed ( 6128 ) when an end of the gesture is detected (e.g., the application window is initially displayed immediately after detecting liftoff of the contact), and the plurality of user interface objects corresponding to the respective application are displayed when the end of the gesture is detected (e.g., the plurality of objects is initially displayed immediately after detecting liftoff of the contact). For example, application window  6010  in  FIG. 11B  is, optionally, displayed when contact  6008  is lifted off, and representations  6014  in  FIG. 11D  are, optionally, displayed when liftoff of contact  6012  is detected. 
     It should be understood that the particular order in which the operations in  FIGS. 12A-12B  have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., those listed in the fifth paragraph of the Description of Embodiments) are also applicable in an analogous manner to method  6100  described above with respect to  FIGS. 12A-12B . For example, the contacts, gestures, user interface objects, intensity thresholds, focus selectors, animations described above with reference to method  6100  optionally has one or more of the characteristics of the contacts, gestures, user interface objects, intensity thresholds, focus selectors, animations described herein with reference to other methods described herein (e.g., those listed in the fifth paragraph of the Description of Embodiments). For brevity, these details are not repeated here. 
     In accordance with some embodiments,  FIG. 13  shows a functional block diagram of an electronic device  6200  configured in accordance with the principles of the various described embodiments. The functional blocks of the device are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described embodiments. It is understood by persons of skill in the art that the functional blocks described in  FIG. 13  are, optionally, combined or separated into sub-blocks to implement the principles of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein. 
     As shown in  FIG. 13 , an electronic device  6200  includes a display unit  6202  configured to display a plurality of application icons, where the plurality of application icons include a respective application icon corresponding to a respective application; a touch-sensitive surface unit  6204  configured to receive gestures including contacts; one or more sensor units  6205  configured to detect intensity of contacts with the touch-sensitive surface unit  6204 ; and a processing unit  6206  coupled to the display unit  6202 , the touch-sensitive surface unit  6204  and the sensor units  6205 . In some embodiments, the processing unit  6206  includes a detecting unit  6208 , and a display enabling unit  6210 . 
     The processing unit  6206  is configured to: while a focus selector is over the respective application icon, detect a gesture that includes a contact on the touch-sensitive surface unit  6204  (e.g., with the detecting unit  6208 ); and in response to detecting the gesture: in accordance with a determination that the contact had a maximum intensity during the gesture that was below a respective intensity threshold, enable display of an application window of the respective application (e.g., with the display enabling unit  6210 ); and in accordance with a determination that the contact reached an intensity during the gesture that was above the respective intensity threshold, enable display of a plurality of user interface objects that correspond to the respective application (e.g., with the display enabling unit  6210 ). 
     In some embodiments, the application window of the respective application is displayed when an end of the gesture is detected; and the plurality of user interface objects corresponding to the respective application are displayed during the gesture in response to detecting that the intensity of the contact exceeds the respective intensity threshold. 
     In some embodiments, the application window of the respective application is displayed when an end of the gesture is detected; and the plurality of user interface objects corresponding to the respective application are displayed when the end of the gesture is detected. 
     In some embodiments, the plurality of user interface objects includes reduced-scale representations of currently open application windows for the application. 
     In some embodiments, the plurality of user interface objects includes reduced-scale representations of recently opened documents for the respective application. 
     In some embodiments, the plurality of application icons are displayed in a predefined region of the display unit  6202  prior to detecting the gesture; and the plurality of user interface objects are displayed in the predefined region of the display unit  6202 . 
     In some embodiments, the plurality of user interface objects are displayed in front of and at least partially overlapping one or more of the plurality of application icons in the predefined region of the display unit  6202 . 
     In some embodiments, enabling display of the plurality of user interface objects corresponding to the respective application includes: enabling display of an animation of the plurality of application icons shifting backward into the display unit  6202  (e.g., with the display enabling unit  6210 ); and enabling display of the plurality of user interface objects corresponding to the respective application in a location on the display unit  6202  previously occupied by the plurality of application icons (e.g., with the display enabling unit  6210 ). 
     In some embodiments, enabling display of the plurality of user interface objects corresponding to the respective application includes, for a respective user interface object associated with the respective application: initially enabling display of the respective user interface object at a location proximate to the respective application icon (e.g., with the display enabling unit  6210 ); and after initially enabling display of the respective user interface object, enabling display of an animation of the respective user interface object moving from the location proximate to the respective application icon to a location proximate to another user interface object in the plurality of user interface objects (e.g., with the display enabling unit  6210 ). 
     In some embodiments, the application window is a new application window that was not displayed on the display unit  6202  prior to detecting the contact. 
     The operations in the information processing methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to  FIGS. 1A and 3 ) or application specific chips. 
     The operations described above with reference to  FIGS. 6A-6B  are, optionally, implemented by components depicted in  FIGS. 1A-1B  or  FIG. 13 . For example, detection operation  6104 , and displaying operations  6108  and  6112  are, optionally, 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 selection of an object 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  optionally utilizes or calls 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 . 
     It should be understood that the particular order in which the operations have been described above is merely exemplary and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that the various processes separately described herein (e.g., those listed in the fifth paragraph of the Description of Embodiments) can be combined with each other in different arrangements. For example, the contacts, user interface objects, tactile sensations, intensity thresholds, and/or focus selectors described above with reference to any one of the various processes separately described herein (e.g., those listed in the fifth paragraph of the Description of Embodiments) optionally have one or more of the characteristics of the contacts, gestures, user interface objects, tactile sensations, intensity thresholds, and focus selectors described herein with reference to one or more of the other methods described herein (e.g., those listed in the fifth paragraph of the Description of Embodiments). For brevity, all of the various possible combinations are not specifically enumerated here, but it should be understood that the claims described above may be combined in any way that is not precluded by mutually exclusive claim features. 
     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 various described embodiments 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 various described embodiments and their practical applications, to thereby enable others skilled in the art to best utilize the various described embodiments with various modifications as are suited to the particular use contemplated.