System, method, and user interface for interacting with multiple application windows

Abstract

To provide systems and methods for multitasking using touch-sensitive devices.SOLUTION: A method includes: displaying a first user interface of a first application; receiving a first input corresponding to a request for simultaneously displaying a second application and the first application; simultaneously displaying a second user interface of the second application and the first user interface of the first application; receiving a second input; in accordance with a determination that the second input meets first criteria, replacing display of the second application with display of a third application to simultaneously display the third application and the first application; and in accordance with a determination that the second input meets second criteria, maintaining display of the first application; and ceasing display of the second application without displaying the third application.SELECTED DRAWING: Figure 5A

Description

[Technical Field]

[0001] TECHNICAL FIELD Embodiments herein relate generally to electronic devices, and more particularly to systems and methods for multitasking on electronic devices with display generating components and input devices (e.g., portable multifunction devices with touch-sensitive displays). [Background technology]

[0002] Handheld electronic devices with touch-sensitive displays are ubiquitous. While initially designed for information consumption (e.g., web browsing) and communication (e.g., email), these devices are rapidly replacing desktop and laptop computers as users' primary computing devices. When using a desktop or laptop computer, these users can routinely multitask by accessing and using different running applications (e.g., cutting and pasting text from a document into an email). While the range of new features and applications for handheld electronic devices has greatly expanded, the ability to multitask and swap between applications on handheld electronic devices requires input mechanisms that are quite different from those of desktop or laptop computers.

[0003] Furthermore, because handheld electronic devices have smaller screens than traditional desktop and laptop computers, the need for multitasking is particularly acute on handheld electronic devices. Some traditional handheld electronic devices attempt to address this need by recreating a desktop computer interface on the handheld electronic device. However, these attempted solutions fail to take into account (i) the significant differences in screen size between desktop computers and handheld electronic devices, and (ii) the significant differences between keyboard and mouse interaction on desktop computers and touch and gesture input on handheld electronic devices with touch-sensitive displays. Other attempted solutions require complex input sequences and menu hierarchies that are even less user-friendly than those provided on desktop or laptop computers. Therefore, it is desirable to provide an intuitive and easy-to-use system and method for simultaneously accessing multiple functions or applications on a handheld electronic device. Summary of the Invention

[0004] The embodiments described herein address the need for systems, methods, and graphical user interfaces that provide intuitive and seamless interaction for multitasking on handheld electronic devices, optionally complementing or replacing traditional touch input or gestures.

[0005] According to some embodiments, a method is performed on an electronic device including a display generation component (e.g., a display, a projector, a heads-up display, etc.) and one or more input devices including a touch-sensitive surface (e.g., a touch-sensitive surface coupled to a separate display or a touchscreen display functioning as both a display and a touch-sensitive surface, etc.). The method includes the steps of: displaying, by the display generation component, a first user interface of a first application; receiving, while displaying the first user interface of the first application, a first input corresponding to a request to display the first application and a second application in respective simultaneous display configurations; in response to receiving the first input, displaying a second user interface of the second application and the first user interface of the first application according to respective simultaneous display configurations in which at least a portion of the first user interface of the first application is displayed simultaneously with the second user interface of the second application; and displaying the second application and the first application in respective simultaneous display configurations in which at least a portion of the first user interface of the first application is displayed simultaneously with the second user interface of the second application. receiving a second input, including detecting a first contact at a location on the touch-sensitive surface corresponding to the second application and detecting movement of the first contact across the touch-sensitive surface, while displaying the second application according to the simultaneous display configuration; and, in response to detecting the second input, replacing the display of the second application with the display of the third application in accordance with a determination that the second input satisfies a first criterion and displaying the third application and the first application according to their respective simultaneous display configurations; and, in accordance with a determination that the second input satisfies a second criterion different from the first criterion, maintaining the display of the first application and ceasing the display of the second application without displaying the third application.

[0006] According to some embodiments, a method is performed on an electronic device including a display generation component (e.g., a display, a projector, a heads-up display, etc.) and one or more input devices (e.g., a camera, a remote controller, a pointing device, a touch-sensitive surface coupled to a separate display, or a touchscreen display functioning as both a display and a touch-sensitive surface, etc.). The method includes: displaying, by the display generation component, a dock including a plurality of application icons overlaid on a first user interface of a first application, the plurality of application icons corresponding to different applications installed on the electronic device; detecting a first input while displaying the dock overlaid on the first user interface of the first application, the detecting including detecting a selection of each application icon in the dock; and determining, in response to detecting the first input and in accordance with a determination that the first input satisfies a selection criterion, that each application icon corresponds to a first application and that the first application is associated with a plurality of windows. displaying via a display generation component a representation of each of the plurality of windows of the first application in accordance with a determination that the respective application icon corresponds to the first application and that the first application is currently associated with only a single window; maintaining a display of a first user interface of the first application in accordance with a determination that the respective application icon corresponds to a second application distinct from the first application, replacing the display of the first user interface of the first application with a display of a second user interface of the second application, regardless of the number of windows associated with the second application at the time the first input was detected.

[0007] According to some embodiments, the method is performed on an electronic device that includes a display generating component (e.g., a display, a projector, a heads-up display, etc.) and one or more input devices (e.g., a keyboard, a remote controller, a camera, a touch-sensitive surface coupled to a separate display, or a touchscreen display that functions as both a display and a touch-sensitive surface, etc.). The method includes: displaying, by a display generation component, a first user interface including a selectable representation of first content, the first content being associated with a first application; detecting a first input including detecting an input corresponding to a request to move the selectable representation of the first content across the display to a respective position while displaying the first user interface including the selectable representation of the first content; in response to detecting the first input, resizing the first user interface and displaying a second user interface including the first content adjacent to the first user interface in accordance with a determination that the respective position is a first position; and displaying a third user interface including the first content overlaid on the first user interface in accordance with a determination that the respective position is a second position different from the first position.

[0008] According to some embodiments, a method is performed on an electronic device including a display generating component and one or more input devices. The method includes: displaying, by the display generating component, a first user interface including a selectable user interface object; detecting, while displaying the first user interface including the selectable user interface object, an input corresponding to a request to move the selectable user interface object across the display to a respective location; responsive to detecting the first input, creating a new window of the first application in accordance with a determination that the respective location is within a first predetermined area of ​​the user interface and the selectable user interface object is an application icon of the first application; and responsive to detecting the first input, creating a new window of the first application in accordance with a determination that the respective location is within a second predetermined area of ​​the user interface and the selectable user interface object is an application icon of the first application. and creating a new window for the first application, wherein the second predefined region of the user interface is smaller than the first predefined region of the user interface and the selectable user interface object is a representation of content associated with the first application; and performing an operation corresponding to the selectable user interface object other than creating a new window for the first application in accordance with a determination that the respective location is within a third region of the user interface, the third region of the user interface being smaller than the first predefined region of the user interface and not overlapping with the second predefined region of the user interface, and the selectable user interface object is a representation of content associated with the first application.

[0009] According to some embodiments, the method is performed on an electronic device that includes a display generating component (e.g., a display, a projector, a head-up display, etc.) and one or more input devices (e.g., a camera, a remote controller, a pointing device, a camera, a touch-sensitive surface coupled to a separate display, or a touchscreen display that functions as both a display and a touch-sensitive surface, etc.). The method includes: displaying, by a display generation component, a dock including a plurality of application icons, the plurality of application icons corresponding to different applications, simultaneously with a first user interface of a first application; detecting, while simultaneously displaying the dock with the first user interface of the first application, a first input directed to an application icon in the dock corresponding to a second application, the first input including movement into a first region of the display and subsequent termination of the first input into the first region of the display; in response to detecting the first input, in accordance with a determination that the second application is associated with multiple windows, displaying, via the display generation component, a first representation of a first window of the second application and a second representation of a second window of the second application in the second region of the display simultaneously with the first user interface of the first application; and in accordance with a determination that the second application is associated with only a single window, displaying, via the display generation component, a user interface of the second application simultaneously with the first user interface of the first application, wherein the user interface of the second application is displayed in the second region of the display.

[0010] According to some embodiments, a method is performed on an electronic device including a display generation component (e.g., a display, a projector, a heads-up display, etc.) and one or more input devices (e.g., a camera, a remote controller, a keyboard, a touch-sensitive surface coupled to a separate display, or a touchscreen display functioning as both a display and a touch-sensitive surface, etc.). The method includes simultaneously displaying, by the display generation component, a first application view and a second application view in a first simultaneous display configuration of a plurality of simultaneous display configurations including a first simultaneous display configuration specifying a first arrangement of the simultaneously displayed application views, a second simultaneous display configuration specifying a second arrangement of the simultaneously displayed application views that is different from the first arrangement of the simultaneously displayed application views, and a third simultaneous display configuration specifying a third arrangement of the simultaneously displayed application views that is different from both the first arrangement of the simultaneously displayed application views and the second arrangement of the simultaneously displayed application views; receiving a first input, the first input starting at a position directed toward the first application view in the first arrangement of the simultaneously displayed application views, and a first movement and a second input after the first movement is detected. detecting a first input comprising an end of a pressing force; and in response to detecting the first movement of the first input, moving a representation of the first application view on the display according to the first movement of the first input, displaying, while the representation of the first application view is over a first portion of the display, a first visual indication indicating that the first application view and the second application view will be displayed in a first simultaneous display configuration if the first input is terminated; and displaying, while the representation of the first application view is over a second portion of the display, a second visual indication indicating that the first input is terminated if the first application view and the second application view will be displayed in a second simultaneous display configuration; and while the representation of the first application view is over a third portion of the display.and displaying a third visual indication indicating that the first application view and the second application view will be displayed in a third simultaneous display configuration if the first input is terminated; and in response to detecting the termination of the first input, displaying the first application view and the second application view in the first simultaneous display configuration in accordance with a determination that the first input was terminated while the first application view was over the first portion of the display, displaying the first application view and the second application view in the second simultaneous display configuration in accordance with a determination that the first input was terminated while the first application view was over the second portion of the display, and displaying the first application view and the second application view in the third simultaneous display configuration in accordance with a determination that the first input was terminated while the first application view was over the third portion of the display.

[0011] According to some embodiments, an electronic device includes a display generating component (e.g., a display, a projector, a head-mounted display, etc.), one or more input devices (e.g., a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface, etc.), optionally one or more tactile output generators, one or more processors, and a memory having stored thereon one or more programs, the one or more programs configured to be executed by the one or more processors, the one or more programs including instructions to perform or cause to be performed any of the operations of the methods described herein. According to some embodiments, a computer-readable storage medium has stored therein instructions that, when executed by an electronic device having a display generating component, one or more input devices (e.g., a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface), and optionally one or more tactile output generators, cause the device to perform or cause to be performed any of the operations of the methods described herein. According to some embodiments, a graphical user interface of an electronic device having a display generating component, one or more input devices (e.g., a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface), optionally one or more tactile output generators, a memory, and one or more processors executing one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described herein, and the elements are updated in response to input as described in any of the methods described herein. According to some embodiments, an electronic device includes a display generating component, one or more input devices (e.g., a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface), optionally one or more tactile output generators, and means for performing or causing to be performed the operations of any of the methods described herein.According to some embodiments, an information processing apparatus for use in an electronic device having a display generation component, one or more input devices (e.g., a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface), and optionally one or more tactile output generators, includes means for performing or causing to be performed the operations of any of the methods described herein.

[0012] Thus, an electronic device having a display generating component, one or more input devices (e.g., a touch-sensitive surface and, optionally, one or more sensors that detect the intensity of contact with the touch-sensitive surface), optionally one or more tactile output generators, optionally one or more device orientation sensors, and optionally an audio system, increases the effectiveness, efficiency, and user satisfaction of handheld, portable electronic devices by providing improved methods and interfaces for interacting with multiple windows on such devices. Such methods and interfaces can complement or replace conventional methods for multitasking and interacting with multiple windows.

[0013] It should be noted that the various embodiments described above can be combined with any other embodiment described herein. The features and advantages described herein are not exhaustive, and many additional features and advantages will become apparent to those skilled in the art, particularly in light of the drawings, specification, and claims. Furthermore, it should be noted that the language used in this specification has been selected solely for the purposes of readability and explanation, and not to define or limit the subject matter of the present invention. [Brief explanation of the drawings]

[0014] For a better understanding of the various described embodiments, reference should be made to the following detailed description in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout:

[0015] [Figure 1A]FIG. 1 is a high-level block diagram illustrating a computing device with a touch-sensitive display according to some embodiments.

[0016] [Figure 1B] FIG. 2 is a block diagram illustrating exemplary components for event processing according to some embodiments.

[0017] [Figure 1C] 1 is a schematic diagram of a portable multifunction device having a touch-sensitive display in accordance with some embodiments.

[0018] [Figure 1D] FIG. 1 is a schematic diagram used to illustrate a computing device with a touch-sensitive surface that is separate from the display, according to some embodiments.

[0019] [Figure 2] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface of a menu of an application, according to some embodiments.

[0020] [Figure 3A] FIG. 10 illustrates an example of a dynamic intensity threshold, according to some embodiments. [Figure 3B] FIG. 10 illustrates an example of a dynamic intensity threshold, according to some embodiments. [Figure 3C] FIG. 10 illustrates an example of a dynamic intensity threshold, according to some embodiments.

[0021] [Figure 4A1] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A2] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A3] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A4] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A5] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A6] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A7] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A8] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A9] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A10] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A11] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A12]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A13] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A14] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A15] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A16] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A17] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A18] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A19] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A20] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A21]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A22] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A23] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A24] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A25] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A26] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A27] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A28] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A29] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A30]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A31] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A32] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A33] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A34] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A35] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A36] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A37] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A38] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A39]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A40] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A41] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A42] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A43] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A44] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A45] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A46] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A47] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A48]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A49] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4A50] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B1] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B2] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B3] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B4] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B5] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B6] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B7]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B8] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B9] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B10] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B11] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B12] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B13] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B14] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B15] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B16]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B17] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B18] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B19] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B20] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B21] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B22] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B23] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B24] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B25]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B26] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B27] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B28] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B29] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B30] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B31] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B32] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B33] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B34]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B35] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B36] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B37] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B38] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B39] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B40] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B41] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B42] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B43]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B44] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B45] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B46] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B47] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B48] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B49] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B50] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4B51] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C1]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C2] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C3] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C4] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C5] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C6] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C7] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C8] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C9] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C10]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C11] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C12] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C13] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C14] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C15] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C16] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C17] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C18] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C19]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C20] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C21] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C22] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C23] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C24] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C25] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C26] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C27] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C28]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C29] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C30] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C31] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C32] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C33] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C34] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C35] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C36] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C37]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C38] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C39] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C40] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C41] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C42] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C43] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C44] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C45] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C46]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C47] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4C48] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D1] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D2] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D3] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D4] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D5] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D6] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D7]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D8] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D9] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D10] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D11] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D12] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D13] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D14] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D15] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D16]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D17] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D18] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4D19] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E1] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E2] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E3] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E4] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E5] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E6]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E7] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E8] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E9] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E10] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E11] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E12] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E13] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E14] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E15]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E16] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E17] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E18] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E19] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E20] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E21] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E22] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E23] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E24]FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E25] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E26] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E27] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments. [Figure 4E28] FIG. 1 is a schematic diagram of a touch-sensitive display used to present a user interface for interacting with multiple applications and / or windows, according to some embodiments.

[0022] [Figure 5A] FIG. 1 is a flowchart diagram of a method for interacting with multiple windows in respective simultaneous display configurations (e.g., slide-over display configurations) according to some embodiments. [Figure 5B] FIG. 1 is a flowchart diagram of a method for interacting with multiple windows in respective simultaneous display configurations (e.g., slide-over display configurations) according to some embodiments. [Figure 5C] FIG. 1 is a flowchart diagram of a method for interacting with multiple windows in respective simultaneous display configurations (e.g., slide-over display configurations) according to some embodiments. [Figure 5D] FIG. 1 is a flowchart diagram of a method for interacting with multiple windows in respective simultaneous display configurations (e.g., slide-over display configurations) according to some embodiments. [Figure 5E]FIG. 1 is a flowchart diagram of a method for interacting with multiple windows in respective simultaneous display configurations (e.g., slide-over display configurations) according to some embodiments. [Figure 5F] FIG. 1 is a flowchart diagram of a method for interacting with multiple windows in respective simultaneous display configurations (e.g., slide-over display configurations) according to some embodiments. [Figure 5G] FIG. 1 is a flowchart diagram of a method for interacting with multiple windows in respective simultaneous display configurations (e.g., slide-over display configurations) according to some embodiments. [Figure 5H] FIG. 1 is a flowchart diagram of a method for interacting with multiple windows in respective simultaneous display configurations (e.g., slide-over display configurations) according to some embodiments. [Figure 5I] FIG. 1 is a flowchart diagram of a method for interacting with multiple windows in respective simultaneous display configurations (e.g., slide-over display configurations) according to some embodiments.

[0023] [Figure 6A] FIG. 1 is a flowchart diagram of a method for interacting with an application icon while displaying the application, according to some embodiments. [Figure 6B] FIG. 1 is a flowchart diagram of a method for interacting with an application icon while displaying the application, according to some embodiments. [Figure 6C] FIG. 1 is a flowchart diagram of a method for interacting with an application icon while displaying the application, according to some embodiments. [Figure 6D] FIG. 1 is a flowchart diagram of a method for interacting with an application icon while displaying the application, according to some embodiments. [Figure 6E] FIG. 1 is a flowchart diagram of a method for interacting with an application icon while displaying the application, according to some embodiments.

[0024] [Figure 7A]FIG. 1 is a flowchart diagram of a method for displaying content together with a currently displayed application in respective simultaneous display configurations, according to some embodiments. [Figure 7B] FIG. 1 is a flowchart diagram of a method for displaying content together with a currently displayed application in respective simultaneous display configurations, according to some embodiments. [Figure 7C] FIG. 1 is a flowchart diagram of a method for displaying content together with a currently displayed application in respective simultaneous display configurations, according to some embodiments. [Figure 7D] FIG. 1 is a flowchart diagram of a method for displaying content together with a currently displayed application in respective simultaneous display configurations, according to some embodiments. [Figure 7E] FIG. 1 is a flowchart diagram of a method for displaying content together with a currently displayed application in respective simultaneous display configurations, according to some embodiments. [Figure 7F] FIG. 1 is a flowchart diagram of a method for displaying content together with a currently displayed application in respective simultaneous display configurations, according to some embodiments. [Figure 7G] FIG. 1 is a flowchart diagram of a method for displaying content together with a currently displayed application in respective simultaneous display configurations, according to some embodiments. [Figure 7H] FIG. 1 is a flowchart diagram of a method for displaying content together with a currently displayed application in respective simultaneous display configurations, according to some embodiments.

[0025] [Figure 7I] FIG. 1 is a flowchart diagram of a method for dragging and dropping an object to a corresponding area of ​​a display to open a new window, according to some embodiments.

[0026] [Figure 8A]FIG. 10 is a flow chart diagram of a method for displaying applications together with a currently displayed application in respective simultaneous display configurations according to some embodiments. [Figure 8B] FIG. 10 is a flow chart diagram of a method for displaying applications together with a currently displayed application in respective simultaneous display configurations according to some embodiments. [Figure 8C] FIG. 10 is a flow chart diagram of a method for displaying applications together with a currently displayed application in respective simultaneous display configurations according to some embodiments. [Figure 8D] FIG. 10 is a flow chart diagram of a method for displaying applications together with a currently displayed application in respective simultaneous display configurations according to some embodiments. [Figure 8E] FIG. 10 is a flow chart diagram of a method for displaying applications together with a currently displayed application in respective simultaneous display configurations according to some embodiments.

[0027] [Figure 9A] FIG. 1 is a flowchart diagram of a method for changing window display configurations using fluid gestures, according to some embodiments. [Figure 9B] FIG. 1 is a flowchart diagram of a method for changing window display configurations using fluid gestures, according to some embodiments. [Figure 9C] FIG. 1 is a flowchart diagram of a method for changing window display configurations using fluid gestures, according to some embodiments. [Figure 9D] FIG. 1 is a flowchart diagram of a method for changing window display configurations using fluid gestures, according to some embodiments. [Figure 9E] FIG. 1 is a flowchart diagram of a method for changing window display configurations using fluid gestures, according to some embodiments. [Figure 9F] FIG. 1 is a flowchart diagram of a method for changing window display configurations using fluid gestures, according to some embodiments. [Figure 9G] FIG. 1 is a flowchart diagram of a method for changing window display configurations using fluid gestures, according to some embodiments. [Figure 9H] FIG. 1 is a flowchart diagram of a method for changing window display configurations using fluid gestures, according to some embodiments. [Figure 9I] FIG. 1 is a flowchart diagram of a method for changing window display configurations using fluid gestures, according to some embodiments. [Figure 9J] FIG. 1 is a flowchart diagram of a method for changing window display configurations using fluid gestures, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0028] This disclosure describes various embodiments for facilitating multitasking on portable electronic devices where conventional multi-window interaction and user interface navigation techniques have proven inefficient, cumbersome, error-prone, and time-consuming. Improved user interfaces for interacting with multiple applications, windows, and / or documents are needed for battery-powered devices with small displays.

[0029] In some embodiments, a method is described for switching windows within a subset of windows (e.g., a slide-over application or set of windows) configured to be displayed simultaneously with another full-screen window or application. The subset of windows having the same display configuration (e.g., displayed in slide-over mode) are organized into a stack or carousel and are switchable in response to gestures that meet predetermined criteria. Additionally, an overlay switcher user interface is provided for reviewing and managing the subset of windows displayed in slide-over mode and for providing a consistent way to quickly select a window to overlay on a currently displayed full-screen window or application.

[0030] In some embodiments, application switching requests and window management requests are integrated into the same input (e.g., a tap input on an application icon while displaying a first application). Heuristics are used to determine whether to switch to a second application or display the window switcher for the first application. If the activated application icon corresponds to the displayed application, the input is treated as a request to open the application's window switcher. If the activated application icon corresponds to an application other than the displayed application, the input is treated as a request to switch applications, regardless of the number of windows the first application has open. If the currently displayed application does not have multiple windows, the input is ignored (e.g., optionally with error feedback). Integrating application switching and window switching within an application provides a more efficient interface because the user does not need to keep track of the number of windows currently open for the currently displayed application. Instead, the device automatically provides intuitive responses based on heuristics, thereby improving user interface efficiency and reducing the number of inputs required to achieve a desired result.

[0031] In some embodiments, an object representing content is dragged from a currently displayed window to a predefined region of the display, and the device opens a new window displaying the content along with the currently displayed window in a respective co-display configuration (e.g., a slide-over window or a split-screen window) depending on the location of the input or the location of the dragged object when the end of the input is detected. In some embodiments, the drag-and-drop operation is also integrated with drag-and-drop operations performed on the original window containing the object representing the content or on another co-displayed window. By integrating multiple operations performed on an application window, across two co-displayed windows, in a new window of the first type, or in a new window of the second type, a user can easily perform different operations based on the end location of the input. This helps reduce the complexity of user interface interactions because fewer gestures need to be performed, used, and remembered to achieve these functions, thereby reducing user errors and improving the efficiency of the user interface.

[0032] In some embodiments, when an object is dragged and dropped onto different areas on the display, different actions are performed depending on the end location of the input, including actions that open different types of new windows (e.g., slide-over or split-screen windows), actions within the object's original window, and actions across two simultaneously displayed windows. For some objects, such as application icons, applicable actions within or across existing windows on the display are not common, and therefore it is beneficial to have a larger drop zone for opening a new window by dragging and dropping an application icon compared to the drop zone for opening a new window by dragging and dropping an object representing content. This user interface improvement helps reduce user errors without significantly compromising functionality, thereby improving the efficiency of the user interface.

[0033] In some embodiments, when a request to open an application in a simultaneous display configuration is received, if the application is not associated with multiple windows, the application is displayed in the simultaneous display configuration, and if the application is associated with multiple windows, a window selector user interface is displayed in each simultaneous display configuration. It is intuitive and efficient to allow a user to use the same input (e.g., dragging the application's application icon to a side region of the display) to open the application in the simultaneous display configuration or to open the application's window selector, based on whether the application is associated with multiple windows. This reduces the number and type of user inputs required to achieve a desired result and helps reduce the likelihood of user error.

[0034] In some embodiments, the device responds to input dragging a window to different drop zones defined on the display by providing dynamic visual feedback to indicate the resulting window configuration if the end of the input is detected at the current location. The final state of the user interface is not determined until the end of the input is detected, thus giving the user an opportunity to explore and learn various potential outcomes before ending the input in the appropriate location and ultimately arriving at a single window configuration. This fluid nature of the input and feedback allows multiple results to be achieved using the same gesture, and the likelihood of user error is reduced by the simplicity of the gesture and the continuous visual feedback provided according to the current location of the input.

[0035] The methods and user interface heuristics described herein take into account (i) significant differences in screen size between desktop computers and handheld electronic devices, and (ii) significant differences between keyboard and mouse interaction on desktop computers and touch and gesture input on handheld electronic devices with touch-sensitive displays. Various multitasking functions can be achieved at different levels, such as across multiple applications, across all windows of a given application, across windows of a given type in a given application, when opening new windows or switching between existing windows, when opening content, and when opening applications, without the need for menu navigation or complex sequences of inputs. These methods and user interface heuristics provide an intuitive and easy-to-use system and method for simultaneously accessing multiple functions or applications on a handheld electronic device.

[0036] Figures 1A-1D and 2 provide an illustration of an exemplary device. Figures 3A-3C show examples of dynamic intensity thresholds. Figures 4A1-4A50, 4B1-4B51, 4C1-4C48, 4D1-4D19, and 4E1-4E28 are schematic diagrams of touch-sensitive displays used to show user interfaces for interacting with multiple applications and / or windows, according to some embodiments, and are used to explain the methods / processes shown in Figures 5A-5I, 6A-6E, 7A-7H, 7I, 8A-8E, and 9A-9J. Exemplary Devices

[0037] Reference will now be made in detail to the 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 embodiments being described. However, it will be apparent to those skilled in the art that the various embodiments described 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.

[0038] In this specification, terms such as "first," "second," etc. are used to describe various elements in some examples, but it will be understood that these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first contact can be referred to as a second contact, and similarly, a second contact can be referred to as a first contact, without departing from the scope of the various embodiments being described. Although a first contact and a second contact are both contacts, they are not the same contact.

[0039] The terminology used in the description of various embodiments set forth 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 embodiments set forth and in 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. Also, as used herein, the term "and / or" should be understood to refer to and include 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," as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0040] As used herein, the term "if" is optionally interpreted to mean "when," or "upon," or "in response to determining," or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if [a stated condition or event] is detected" are optionally interpreted 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.

[0041] The disclosures herein relate interchangeably to detecting touch input on, at, over, on top of, or substantially within a particular user interface element or portion of a touch-sensitive display. As used herein, a touch input detected at a particular user interface element may also be detected on, over, on top of, or substantially within the same user interface element, depending on the context. In some embodiments, as discussed in more detail below, the desired sensitivity level for detecting touch input is configured by a user of the electronic device (e.g., the user may determine (and configure the electronic device to operate) that touch input shall be detected only when the touch input is entirely within a user interface element).

[0042] It is understood that use of personally identifiable information should comply with generally recognized privacy policies and practices that meet or exceed industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of permitted uses should be clearly indicated to users.

[0043] 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 communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the IPHONE®, IPOD TOUCH®, and IPAD® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch-sensitive displays and / or touchpads), are also optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer with a touch-sensitive surface (e.g., touch-sensitive displays and / or touchpads).

[0044] In the following discussion, electronic devices are described that include a display and a touch-sensitive surface. However, it should be understood 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.

[0045] The device typically supports a variety of applications such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disc authoring application, a spreadsheet application, a gaming application, a phone application, a video conferencing application, an email application, an instant messaging application, a fitness 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.

[0046] Various applications running on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed for each application and / or within each application. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports various applications with user interfaces that are intuitive and transparent to the user.

[0047] Attention is now directed to embodiments of portable electronic devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating a portable multifunction device 100 (also referred to interchangeably herein as electronic device 100 or device 100) with a touch-sensitive display 112, according to some embodiments. Touch-sensitive display 112 may conveniently be referred to as a "touchscreen" and may also be known or referred to as a touch-sensitive display system. Device 100 includes memory 102 (optionally including one or more computer-readable storage media), controller 120, one or more processing units (CPU's) 122, 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 light sensors 164. Device 100 optionally includes one or more intensity sensors 165 that detect the intensity of a contact 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 that generate a tactile output on device 100 (e.g., generate a tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or a touchpad of device 100). These components optionally communicate via one or more communication buses or signal lines 103.

[0048] As used herein and in the claims, the term “tactile output” refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a 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 “downclick” or “upclick” of a physical actuator button. In some cases, a user will feel a tactile sensation such as a “downclick” or “upclick” even when no movement of a physical actuator button associated with the touch-sensitive surface has been physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. While such user interpretation of touch depends on the user's personal sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that will produce the described sensory perception for a typical (or average) user.

[0049] It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than those shown, optionally combines two or more components, or optionally has a different configuration or arrangement of its 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 circuits and / or application specific integrated circuits.

[0050] Memory 102 optionally includes high-speed random-access memory (e.g., 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, flash memory devices, or other non-volatile solid-state storage devices. Memory 102 optionally includes one or more storage devices located remotely from processor(s) 122. Access to memory 102 by other components of device 100, such as CPU 122 and peripherals interface 118, is optionally controlled by controller 120.

[0051] A peripheral interface 118 can be used to couple input and output peripherals of the device to the CPU 122 and memory 102. The one or more processors 122 operate or execute various software programs and / or instruction sets stored in the memory 102 to perform various functions and process data for the device 100.

[0052] In some embodiments, peripheral interface 118, CPU 122, and controller 120 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0053] RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to electromagnetic signals and electromagnetic signals to communicate with communication networks and other communication devices via 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, etc. RF circuitry 108 optionally communicates via wireless communication with networks, such as the Internet, also known as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices. Wireless communication optionally uses any of a number of communication 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-HSPA), 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.1la, IEEE 802.1lb, IEEE 802.1lg, and / or IEEE 802.1ln).

[0054] Audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuit 110 receives audio data from peripherals interface 118, converts the audio data into electrical signals, and transmits the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves audible to humans. Audio circuit 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuit 110 converts the electrical signals into audio data and transmits the audio data to peripherals interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to memory 102 and / or RF circuit 108 by peripherals interface 118. In some embodiments, audio circuit 110 further includes a headset jack. The headset jack provides an interface between audio circuitry 110 and a detachable audio input / output peripheral, such as an output-only headphone or a headset with both an output (e.g., mono or binaural headphones) and an input (e.g., a microphone).

[0055] I / O subsystem 106 connects input / output peripherals of device 100, such as touchscreen 112 and other input control devices 116, to peripheral interface 118. I / O subsystem 106 optionally includes one or more input controllers 160 for display controller 156, light sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and other input or control devices. One or more input controllers 160 receive electrical signals from and send electrical signals to other input or control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, input controller 160 is optionally coupled to any or none of a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons optionally include up / down buttons for adjusting the volume of speaker 111 and / or microphone 113. The one or more buttons optionally include a push button.

[0056] Touch-sensitive display 112 provides an input and output interface between the device and a user. Display controller 156 receives and / or sends electrical signals to touchscreen 112. Touchscreen 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output corresponds to user-interface objects.

[0057] Touchscreen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and / or tactile contact. Touchscreen 112 and display controller 156 (along with any associated modules and / or instruction sets in memory 102) detects contacts (and any movement or cessation of contact) on touchscreen 112 and translates the detected contacts into interactions with user interface objects (e.g., one or more softkeys, icons, web pages, or images) displayed on touchscreen 112. In an exemplary embodiment, the point of contact between touchscreen 112 and the user corresponds to the area under the user's finger.

[0058] Touchscreen 112 optionally uses LCD (liquid crystal display), LPD (light emitting polymer display), LED (light emitting diode), or OLED (organic light emitting diode) technology, although other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally detect contact and any movement or disruption thereof using any of a number of now-known or later-developed touch-sensing technologies, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements that determine one or more points of contact with touchscreen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in Apple Inc.'s (Cupertino, California) iPhone®, iPod Touch®, and iPad®.

[0059] Touchscreen 112 optionally has a video resolution greater than 400 dpi. In some embodiments, touchscreen 112 has a video resolution of at least 600 dpi. In other embodiments, touchscreen 112 has a video resolution of at least 1000 dpi. A user optionally contacts touchscreen 112 using any suitable object or digit, such as a stylus or a finger. In some embodiments, the user interface is designed to work primarily with finger-based touches and gestures. In some embodiments, the device translates finger-based input into precise pointer / cursor position or commands that perform the user's desired action.

[0060] In some embodiments, in addition to the touchscreen, device 100 optionally includes a touchpad (not shown) for activating or deactivating certain functions. In some embodiments, the touchpad is a touch-sensitive area of ​​the device that, unlike the touchscreen, does not display visual output. The touchpad is optionally a touch-sensitive surface separate from touchscreen 112 or an extension of the touch-sensitive surface formed by the touchscreen.

[0061] Device 100 also includes a power system 162 that provides power to 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, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with generating, managing, and distributing electrical power within a portable device.

[0062] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 in I / O subsystem 106. Light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. Light sensor 164 optionally works in conjunction with imaging module 143 (also called a camera module) to capture still or video images. In some embodiments, a light sensor is located on the back of device 100, opposite touchscreen 112 on the front of the device, to enable the touch-sensitive display as a viewfinder for still and / or video image acquisition. In some embodiments, another light sensor is located on the front of the device to optionally obtain an image of the user for video conferencing while the user views other video conference participants on the touch-sensitive display.

[0063] Device 100 also optionally 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 juxtaposed with or proximate to the 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 touchscreen 112 located on the front of device 100.

[0064] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is coupled to input controller 160 in I / O subsystem 106. In some embodiments, the proximity sensor turns off and disables touchscreen 112 when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call).

[0065] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows tactile output generators 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 motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates a tactile output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is located on 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 the surface of device 100) or laterally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch-sensitive display 112, which is located on the front of device 100.

[0066] Device 100 also optionally includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I / O subsystem 106. In some embodiments, information is displayed on the touch-sensitive display in portrait or landscape view based on analysis of data received from the one or more accelerometers. In addition to accelerometer(s) 168, device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information regarding the location and orientation (e.g., portrait or landscape) of device 100.

[0067] In some embodiments, software components stored in memory 102 include operating system 126, communications module (or instruction set) 128, touch / motion module (or instruction set) 130, graphics module (or instruction set) 132, text input module (or instruction set) 134, Global Positioning System (GPS) module (or instruction set) 135, and applications (or instruction sets) 136. Additionally, in some embodiments, as shown in FIG. 1A , memory 102 stores device / global internal state 157. Device / global internal state 157 includes one or more of: active application state indicating which applications, if any, are currently active; display state indicating which applications, views, or other information occupy various regions of touch-sensitive display 112; sensor state including information obtained from the device's various sensors and input control devices 116; and location information regarding the device's position and / or attitude (i.e., device orientation). In some embodiments, device / global internal state 157 communicates with multitasking module 180 to track applications activated in multitasking mode (also called shared screen view, shared screen mode, or multitasking mode). In this way, when device 100 is rotated from portrait to landscape display mode, multitasking module 180 can retrieve multitasking state information (e.g., the display area of ​​each application in multitasking mode) from device / global internal state 157 in order to reactivate multitasking mode after switching from portrait to landscape orientation.

[0068] 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 that control and manage common system tasks (e.g., memory management, storage device control, power management, etc.) and facilitate communication between various hardware and software components.

[0069] Communications module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by RF circuitry 108 and / or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE®, etc.) is adapted to couple to other devices directly or indirectly via 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, similar to, and / or compatible with the 30-pin connector used in some embodiments of APPLE Inc.'s IPOD devices. In other embodiments, the external port is a multi-pin (e.g., 8-pin) connector that is the same as, similar to, and / or compatible with the 8-pin connector used in APPLE Inc.'s Lightning connector.

[0070] Contact / motion module 130, optionally in conjunction with display controller 156, detects contact with touch screen 112 and other touch-sensing devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes various software components for performing various operations related to detecting contact, such as determining whether contact occurs (e.g., detecting a finger-down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-drag events), and determining whether the contact has stopped (e.g., detecting a finger-up event or an interruption of the contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact, as represented by the series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact. These actions are optionally applied to a single contact (e.g., a single finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contacts on the touchpad.

[0071] In some embodiments, contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by the user (e.g., whether the user has selected or “clicked” on an affordance). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator, but can be adjusted without changing the physical hardware of device 100). For example, the mouse “click” threshold of a trackpad or touch-sensitive display can be set to any of a wide range of predetermined thresholds without modifying the trackpad or touch-sensitive display hardware. Furthermore, in some implementations, a user of the device is provided with a software setting to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once via a system-level click “intensity” parameter).

[0072] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or intensities of detected contacts). Thus, gestures are optionally detected by detecting particular contact patterns. 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 location (or substantially the same location) as the finger down event (e.g., the location 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 drag events, and in some embodiments, then subsequently detecting a finger up (lift off) event.

[0073] Graphics module 132 includes various known software components that render and display graphics on touchscreen 112 or other display, including components that vary the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including, but not limited to, text, web pages, icons (such as user interface objects, including softkeys), digital images, video, animation, etc.

[0074] 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 one or more codes specifying the graphics to be displayed, including coordinate data and other graphic characteristic data, as needed, from an application or the like, and then generates screen image data to output to display controller 156. In some embodiments, graphics module 132 retrieves graphics stored in multitasking data 176 for each application 136 (FIG. 1B). In some embodiments, multitasking data 176 stores multiple graphics of different sizes to allow applications to be quickly resized while in shared screen mode.

[0075] The tactile feedback module 133 includes various software components for generating instructions used by the tactile output generator 167, which generates tactile outputs at one or more locations on the device 100 in response to a user's interaction with the device 100.

[0076] Text input module 134 is optionally a component of graphics module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts module 137, email client module 140, IM module 141, browser module 147, and any other application requiring text input).

[0077] The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for use in location-based calling, to the camera 143 as photo / video metadata, and to applications that provide location-based services such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0078] Application (“app”) 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: • a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ●Videoconferencing module 139, ● an email client module 140; ● Instant messaging (IM) module 141; ●Fitness module 142, a camera module 143 for still and / or video images, ● Image management module 144; ● Browser module 147, ● Calendar module 148, a widget module 149, optionally including one or more of a weather widget 149-1, a stocks widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6; ● Search module 151, • a video and music player module 152, optionally consisting of a video player module and a music player module; ● Memo module 153, Map module 154, and / or ●Online video module 155.

[0079] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, website creation applications, disk authoring applications, spreadsheet applications, JAVA® enabled applications, encryption, digital rights management, voice recognition, widget creator modules for creating user created widgets 149-6, and voice duplication.

[0080] In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 is optionally used to manage an address book or contact list (e.g., stored in memory 102 or in contacts module 137 in memory 370), including adding name(s) to the address book, removing name(s) from the address book, associating phone number(s), email address(es), physical address(es), or other information with names, associating images with names, categorizing and sorting names, providing phone numbers or email addresses to initiate and / or facilitate communication via telephone module 138, videoconferencing module 139, email client module 140, or IM module 141, etc.

[0081] 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 is optionally used to enter a series of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify an entered telephone number, dial each telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0082] Videoconferencing module 139, along with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, includes executable instructions for initiating, conducting, and terminating a videoconference between a user and one or more other participants according to the user's instructions.

[0083] In cooperation with RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 contains executable instructions for composing, sending, receiving, and managing emails in response to user instructions. In cooperation with image management module 144, email client module 140 greatly facilitates composing and sending emails with still or video images captured by camera module 143.

[0084] Instant messaging module 141, together with RF circuitry 108, touchscreen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, includes executable instructions for entering characters corresponding to instant messages, modifying previously entered characters, sending each instant message (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephone-based instant messaging, or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and displaying received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments, such as those supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0085] In conjunction with the RF circuitry 108, touchscreen 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and video and music player module 146, fitness module 142 includes executable instructions for creating workouts (e.g., in terms of time, distance, and / or calorie burn goals), communicating with workout sensors (such as a watch or sports device such as a pedometer), receiving workout sensor data, calibrating sensors used to monitor workouts, selecting and playing music for workouts, and displaying, storing, and transmitting workout data.

[0086] In cooperation with touch screen 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 contains executable instructions to capture still images or video (including video streams) and store them in memory 102, change the characteristics of the still images or video, or delete the still images or video from memory 102.

[0087] 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 for arranging, modifying (e.g., editing) or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slide show or album), and storing still and / or video images.

[0088] 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 contains executable instructions for browsing the Internet according to user instructions, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0089] In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions for creating, displaying, modifying, and storing calendars and data associated with calendars (e.g., calendar items, to-do lists, etc.) according to user commands.

[0090] In conjunction with RF circuitry 108, touchscreen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 is a mini-application (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) that is optionally downloaded and used by a user, or a mini-application (e.g., user-created widget 149-6) created by a user. 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).

[0091] In conjunction with the RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, a widget creator module (not shown) is optionally used by a user to create widgets (e.g., turn user-specified portions of a web page into widgets).

[0092] In cooperation 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 for searching memory 102 for text, music, sound, images, video, and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

[0093] In conjunction with touchscreen 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 contains executable instructions that enable a user to download and play pre-recorded music or other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions for displaying, presenting, or otherwise playing videos (e.g., on touchscreen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an IPOD® from APPLE Inc.

[0094] In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 contains executable instructions for creating and managing notes, to-do lists, and the like, in accordance with user instructions.

[0095] 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 may optionally be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data about stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.

[0096] Online video module 155, in conjunction with touchscreen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, contains instructions that enable a user to access, browse for, receive (e.g., by streaming and / or downloading), and play (e.g., on the touchscreen or on an external display connected via external port 124) particular online videos, send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141 is used to send links to particular online videos, rather than email client module 140.

[0097] 1A , portable multifunction device 100 also includes multitasking module 180 that manages multitasking operations on device 100 (e.g., communicating with graphics module 132 to determine appropriate display areas for simultaneously displayed applications). Multitasking module 180 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: ● Application Selector 182, ● Compatibility module 184, Picture-in-picture (PIP) / overlay module 186, and ● Multitasking history 188, which stores information about the user's multitasking history (e.g., commonly used applications in multitasking mode, recently displayed areas of applications while in multitasking mode, pinned applications to each other for display in split view / multitasking mode, etc.).

[0098] In cooperation with touch screen 112, display controller 156, contact module 130, graphics module 132, and contact intensity sensor 165, application selector 182 includes executable instructions for displaying affordances corresponding to applications (e.g., one or more of applications 136) and allowing a user of device 100 to select affordances for use in multitasking / split screen mode (e.g., a mode in which two or more applications are displayed and active simultaneously on touch screen 112). In some embodiments, application selector 182 is a dock (e.g., dock 408, described below).

[0099] In cooperation with touch screen 112, display controller 156, contact module 130, graphics module 132, and application selector 182, compatibility module 184 includes executable instructions for determining whether a particular application is compatible with multitasking mode (e.g., by checking a flag, such as a flag stored with multitasking data 176 for each application 136, as shown in FIG. 1B).

[0100] In cooperation with touch screen 112, display controller 156, contact module 130, graphics module 132, and contact intensity sensor(s) 165, PIP / overlay module 186 includes executable instructions for determining a reduced size of an application to be displayed to overlay another application, and for determining an appropriate location on touch screen 112 to display the reduced-size application (e.g., a location that avoids important content in the active application that will be overlaid by the reduced-size application).

[0101] Each of the above-identified modules and applications corresponds to executable instruction sets that perform one or more of the functions described above and methods described in the present application (e.g., computer-implemented methods and other information processing methods described herein). The modules (i.e., instruction sets) need not be implemented as separate software programs, procedures, or modules; thus, various subsets of the modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.

[0102] In some embodiments, device 100 is a device in which operation of a predetermined set of functions on the device is performed solely via a touchscreen and / or touchpad. By using the touchscreen and / or touchpad as the primary input control device for operation of device 100, the number of physical input control devices (push buttons, dials, etc.) on device 100 is optionally reduced.

[0103] The set of predefined functions performed only through the touchscreen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 to a main menu, home menu, or root menu from any user interface displayed on device 100. In such embodiments, a "menu button" is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device rather than a touchpad.

[0104] 1B is a block diagram illustrating exemplary components for event processing, according to some embodiments. In some embodiments, memory 102 (of FIG. 1A) includes event sorter 170 (e.g., of operating system 126) and a corresponding application 136-1 selected from among applications 136 of portable multifunction device 100 (FIG. 1A) (e.g., any of the applications described above stored in memory 102 that comprise application 136).

[0105] Event sorter 170 receives the event information and determines which application 136-1 to deliver the event information to and application view 175 of application 136-1. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192 that indicates the current application view that is displayed on touch-sensitive display 112 when the application is active or running. In some embodiments, device / global internal state 157 is used by event sorter 170 to determine which application is currently active, and application internal state 192 is used by event sorter 170 to determine which application is currently active, and application view 175 to which the event information is delivered.

[0106] In some embodiments, application internal state 192 includes additional information, such as one or more of resume information to use when application 136-1 resumes execution, user interface state information indicating or ready to display information being displayed by application 136-1, state cues that allow the user to return to a previous state or view of application 136-1, and redo / undo cues for previous actions taken by the user. In some embodiments, application internal state 192 is used by multitasking module 180 to help facilitate multitasking operations (e.g., multitasking module 180 obtains resume information from application internal state 192 to redisplay a previously dismissed application).

[0107] In some embodiments, each application 136-1 stores multitasking data 176. In some embodiments, multitasking data 176 includes a compatibility flag (e.g., a flag accessed by compatibility module 184 to determine whether a particular application is compatible with multitasking mode), a list of compatible sizes to display application 136-1 in multitasking mode (e.g., 1 / 4, 1 / 3, 1 / 2, or full screen), and various sized graphics (e.g., a different graphic for each size in the list of compatible sizes).

[0108] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (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 sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (via 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.

[0109] In some embodiments, event monitor 171 sends requests to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receipt of an input above a predetermined noise threshold and / or for more than a predetermined duration).

[0110] In some embodiments, event sorter 170 also includes a hit view determination module 172 and / or an active event recognizer determination module 173 .

[0111] Hit view determination module 172 provides software procedures that determine where a sub-event occurred within one or more views when touch-sensitive display 112 displays more than one view. A view consists of the controls and other elements that a user can see on the display.

[0112] Another aspect of a user interface associated with an application is the set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the respective application) in which the touch is detected optionally corresponds to a programmatic level within the application's programmatic or view hierarchy. For example, the lowest-level view in which the touch is detected is optionally referred to as the hit view, and the set of events that are recognized as appropriate inputs is optionally determined based at least in part on the hit view of the initial touch that initiates the touch gesture.

[0113] Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized hierarchically, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest-level view in which the initiating sub-event occurs (i.e., the first sub-event in a series of sub-events that form an event or potential event). Once a 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.

[0114] Active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive the particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive the particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that contain the physical location of the sub-event are actively participating views, and therefore all actively participating views should receive the particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with one particular view, views higher in the hierarchy still remain actively participating views.

[0115] Event dispatcher module 174 dispatches event information to event recognizers (e.g., event recognizer 178). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information obtained by each event receiver 181 in an event queue.

[0116] In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In still other embodiments, event sorter 170 is a stand-alone module or is part of another module stored in memory 102, such as contact / motion module 130.

[0117] In some embodiments, application 136-1 includes multiple event handlers 177 and one or more application views 175, each containing instructions for processing touch events that occur within a respective view of the application's user interface. Each application view 175 of application 136-1 includes one or more event recognizers 180. Typically, each application view 175 includes multiple 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, the corresponding event handler 177 includes one or more of data updater 177-1, object updater 177-2, GUI updater 177-3, and / or event data 179 received from event sorter 170. Event handler 177 optionally utilizes or invokes data updater 177-1, object updater 177-2, or GUI updater 177-3 to update application internal state 192. Alternatively, one or more of application views 175 includes one or more respective event handlers 177. Also, in some embodiments, one or more of data updater 177-1, object updater 177-2, and GUI updater 177-3 are included in the corresponding application view 175.

[0118] Each event recognizer 178 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 178 includes event receiver 181 and event comparator 183. In some embodiments, event recognizer 178 also includes at least a subset of metadata 189 and event delivery instructions 190 (optionally including sub-event delivery instructions).

[0119] Event receiver 181 receives event information from event sorter 170. The event information includes information about a sub-event, e.g., a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information, such as the position of the sub-event. When the sub-event involves a touch movement, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the device's current orientation (also called the device's attitude).

[0120] Event comparator 183 compares the event information to a predetermined event or sub-event definition and determines the event or sub-event, or determines or updates the state of the event or sub-event, based on the comparison. In some embodiments, event comparator 183 includes event definition 185. Event definition 185 includes a definition of an event (e.g., a sequence of predetermined sub-events), such as Event 1 (187-1) and Event 2 (187-2). In some embodiments, sub-events in Event 187 include, for example, touch start, touch end, touch movement, touch cessation, and multiple touches. In one example, the definition for Event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch (touch start) for a predetermined stage on the displayed object, a first lift-off (touch end) for a predetermined stage, a second touch (touch start) for a predetermined stage on the displayed object, and a second lift-off (touch end) for a predetermined stage. In another example, a definition of event 2 (187-2) is a drag on a displayed object. Drag includes, for example, a touch (or contact) of a predetermined magnitude on a displayed object, movement of the touch across the touch-sensitive display 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information about one or more associated event handlers 177.

[0121] In some embodiments, event definitions 186 include a definition of the event for each user interface object. In some embodiments, event comparator 183 performs a hit test to determine which user interface object is associated with the sub-event. For example, if a touch is detected on touch-sensitive display 112 in an application view in which three user interface objects are displayed on touch-sensitive display 112, event comparator 183 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 177, event comparator 183 uses the results of the hit test to determine which event handler 177 to activate. For example, event comparator 183 selects the event handler associated with the sub-event and object that triggers the hit test.

[0122] In some embodiments, each event 187 definition also includes a delay action that delays delivery of the event information until it is determined whether the sequence of sub-events corresponds to the event type of the event recognizer.

[0123] If the respective event recognizer 178 determines that the sequence of sub-events does not match any of the events in the event definition 185, the respective event recognizer 178 enters an event-disabled, event-failed, or event-ended state and thereafter ignores the next sub-event of the touch-based gesture. In this situation, any other event recognizers that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

[0124] In some embodiments, each event recognizer 178 includes metadata 189 with configurable properties, flags, and / or lists that indicate to actively participating event recognizers how the event delivery system should perform sub-event delivery. In some embodiments, metadata 189 includes configurable properties, flags, and / or lists that indicate how event recognizers interact with each other or how event recognizers are enabled to interact with each other. In some embodiments, metadata 189 includes configurable properties, flags, and / or lists that indicate how sub-events are delivered to various levels in the view or programmatic hierarchy.

[0125] In some embodiments, each event recognizer 178 activates an event handler 177 associated with an event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognizer 178 delivers event information associated with the event to the event handler 177. Activating the event handler 177 is separate from sending (and postponing sending) the sub-events to the respective hit view. In some embodiments, the event recognizer 178 pops a flag associated with the recognized event, and the event handler 177 associated with the flag captures the flag and performs a predetermined process.

[0126] In some embodiments, the event delivery instructions 190 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 the event information to an event handler associated with a set of sub-events or to an actively participating view. The event handler associated with the set of sub-events or the actively participating view receives the event information and performs predetermined processing.

[0127] In some embodiments, data updater 177-1 creates and updates data used by application 136-1. For example, data updater 177-1 updates phone numbers used in contacts module 137 or stores video files used in video and music player module 145. In some embodiments, object updater 177-2 creates and updates objects used by application 136-1. For example, object updater 177-2 creates new user interface objects or updates the positions of user interface objects. GUI updater 177-3 updates the GUI. For example, GUI updater 177-3 prepares display information and sends display information to graphics module 132 for display on the touch-sensitive display. In some embodiments, GUI updater 177-3 communicates with multitasking module 180 to facilitate resizing of various applications displayed in multitasking mode.

[0128] In some embodiments, event handler 177 includes or has access to data updater 177-1, object updater 177-2, and GUI updater 177-3. In some embodiments, data updater 177-1, object updater 177-2, and GUI updater 177-3 are included in a single module of a respective application 136-1 or application view 175. In other embodiments, they are included in two or more software modules.

[0129] It should be understood that the foregoing description of event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 using input devices, not all of which are initiated on the touchscreen. For example, mouse movements and mouse button presses, contact movements such as tapping, dragging, scrolling on a touchpad, optionally coordinated with single or multiple keyboard presses or holds, pen stylus input, device movement, verbal commands, detected eye movement, biometric input, and / or any combination thereof are optionally utilized as inputs corresponding to sub-events that define the event to be recognized.

[0130] 1C is a schematic diagram of a portable multifunction device (e.g., portable multifunction device 100) having a touch-sensitive display (e.g., touch screen 112) according to some embodiments. The touch-sensitive display optionally displays one or more graphics within user interface (UI) 201 a. In some embodiments, as well as other embodiments described below, a user can select one or more of the graphics by making a gesture on the screen, for example, with one or more fingers or one or more styluses. In some embodiments, selection of one or more graphics occurs when the user loses contact with the one or more graphics (e.g., by lifting a finger off the screen). In some embodiments, the gesture optionally includes one or more tap gestures (e.g., a sequence of touches on the screen followed by lift-off), one or more swipe gestures (e.g., successive contacts between gestures along the surface of the screen from left to right, right to left, upward, and / or downward), and / or rolling (e.g., from right to left, left to right, upward, and / or downward) of a finger in contact with device 100. In some implementations or situations, accidental contact with a graphic does not select that graphic. For example, if a gesture for launching an application is a tap gesture, a swipe gesture that sweeps over an application affordance (e.g., an icon) optionally does not launch (e.g., open) the corresponding application.

[0131] Device 100 also optionally includes one or more physical buttons, such as a "home" or menu button 204. As mentioned above, menu button 204 is optionally used to navigate to any application 136 in a set of applications optionally running on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key within a GUI displayed on touchscreen 112.

[0132] In one embodiment, device 100 includes touchscreen 112, menu button 204, pushbutton 206 for powering the device on / off and locking the device, volume control button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external docking / charging port 124. Pushbutton 206 is optionally used to power the device on / off by pressing and holding the button down for a predetermined period of time, to lock the device by pressing and releasing the button before the predetermined time has elapsed, and / or to unlock the device or initiate the unlocking process. In an alternative embodiment, device 100 also accepts verbal input via microphone 113 to activate or deactivate certain functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touchscreen 112 and / or one or more tactile output generators 167 for generating a tactile output for a user of device 100.

[0133] 1D shows a user interface on a device (e.g., device 100 of FIG. 1A ) that includes touch-sensitive surface 195 (e.g., a tablet or touchpad) that is separate from display 194 (e.g., touchscreen 112). In some embodiments, touch-sensitive surface 195 optionally includes one or more contact intensity sensors (e.g., one or more of contact intensity sensors 359) for detecting the intensity of a contact on touch-sensitive surface 195 and / or one or more tactile output generators 357 for generating a tactile output for a user of touch-sensitive surface 195.

[0134] Although some of the following examples are described with reference to input on touch screen 112 (a combined touch-sensitive surface and display), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, as shown in FIG. 1D . In some embodiments, this touch-sensitive surface (e.g., 195 in FIG. 1D ) has a major axis (e.g., 199 in FIG. 1D ) that corresponds to a major axis (e.g., 198 in FIG. 1D ) on the display (e.g., 194). According to these embodiments, the device detects contact with touch-sensitive surface 195 (e.g., 197-1 and 197-2 in FIG. 1D ) at locations that correspond to respective locations on the display (e.g., in FIG. 1D , 197-1 corresponds to 196-1 and 197-2 corresponds to 196-2). In this manner, when the touch-sensitive surface is separate from the display, user input (e.g., contacts 197-1 and 197-2, and their movement) detected by the device on the touch-sensitive surface (e.g., 195 in FIG. 1D ) is used by the device to operate a user interface on the display (e.g., 194 in FIG. 1D ) of the multifunction device. It should be understood that similar methods are optionally used for the other user interfaces described herein.

[0135] Furthermore, while the following examples are described primarily with reference to finger input (e.g., finger touches, finger tap gestures, finger swipe gestures), it should be understood that in some embodiments, one or more of those finger inputs are replaced with input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of a touch) followed by movement of a cursor along the path of the swipe (e.g., instead of moving a contact). As another example, a tap gesture is optionally replaced by a mouse click (e.g., instead of detecting a contact and then ceasing contact detection) while the cursor is located over the location of the tap gesture. Similarly, when multiple user inputs are detected simultaneously, it will be understood that, optionally, multiple computer mice are being used simultaneously, or, optionally, a mouse and a finger contact are being used simultaneously.

[0136] As used herein, the term “focus selector” refers to an input element that indicates the current portion of a user interface with which a user is interacting. In some implementations involving a cursor or other position marker, when input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touch-sensitive surface 195 of FIG. 1D (in some embodiments, touch-sensitive surface 195 is a touchpad)), the cursor acts as a “focus selector” when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), and the particular user interface element is adjusted according to the detected input. In some implementations involving a touchscreen display (e.g., touch-sensitive display system 112 or touchscreen 112 of FIG. 1A ) that allows direct interaction with user interface elements on the touchscreen display, contact detected on the touchscreen acts as a “focus selector,” such that when input (e.g., a press input by contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface (e.g., by using the tab or arrow keys to move focus from one button to another) without a corresponding cursor movement or contact movement on the touchscreen display. In these implementations, the focus selector moves to follow the movement of focus between various regions of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally a user interface element (or contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface through which the user intends to interact).For example, when a pressure input is detected on a touch-sensitive surface (e.g., a touchpad or touch-sensitive display), the position of the focus selector (e.g., a cursor, contact, or selection box) over a corresponding button indicates that the user intends to activate the corresponding button (rather than other user interface elements shown on the device's display).

[0137] As used herein and in the 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 or a stylus contact) on the touch-sensitive surface, or a 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 (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors under 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., weighted average or sum) to determine an estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure of the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measure). In some implementations, the surrogate measure for the force or pressure of the contact is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure).Using the intensity of contact as an attribute of user input allows a user to access additional device functionality that may not otherwise be easily accessible by the user on devices of reduced size with limited assets for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0138] In some embodiments, contact / motion module 130 uses one or more sets of intensity thresholds to determine whether an action 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 according to software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator and can be adjusted without modifying the physical hardware of portable computing system 100). For example, the mouse “click” threshold of a trackpad or touchscreen display can be set to any of a wide range of pre-defined thresholds without modifying the trackpad or touchscreen display hardware. Furthermore, in some implementations, a user of the device is provided with software settings to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once with a system-level click “intensity” parameter).

[0139] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples, i.e., a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a predetermined event (e.g., after detecting the contact, before detecting lift-off of the contact, before or after detecting the start of contact movement, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of the contact is optionally based on one or more of the maximum intensity of the contact, the median intensity of the contact, the average intensity of the contact, the top 10 percent of the intensity of the contact, half the maximum intensity of the contact, 90 percent of the maximum intensity of the contact, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is performed by the user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity that does not exceed the first threshold would be a first action, a contact having a characteristic intensity that exceeds the first intensity threshold but not exceeding a second intensity threshold would be a second action, and a contact having a characteristic intensity that exceeds the second intensity threshold would be a third action. In some embodiments, the comparison between the characteristic intensity and one or more intensity thresholds is not used to determine whether to perform the first action or the second action, but rather to determine whether to perform one or more actions (e.g., perform a respective option or refrain from performing a respective action).

[0140] In some embodiments, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact (e.g., a drag gesture) that transitions from a start position to an end position, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end position may be based on only a portion of the continuous swipe contact (e.g., only the portion of the swipe contact at the end position) rather than the entire swipe contact. In some embodiments, a smoothing algorithm may be applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some situations, these smoothing algorithms eliminate narrow spikes or dips in the swipe contact intensity for purposes of determining the characteristic intensity.

[0141] In some embodiments, one or more predefined intensity thresholds are used to determine whether a particular input meets the intensity-based criteria. For example, the one or more predefined intensity thresholds may include: (i) a touch-detection intensity threshold IT0; (ii) a light pressure intensity threshold IT10; L , (iii) (e.g., at least initially I L Higher) deep pressure intensity threshold IT D , and / or (iv) one or more other intensity thresholds (e.g., I L Lower Intensity Threshold I H As used herein, IT L and I L refers to the same light pressure intensity threshold, and IT D and I D refers to the same deep pressure intensity threshold, IT H and I Hrefer to the same intensity threshold. In some embodiments, the light pressure intensity threshold corresponds to an intensity at which the device performs an action typically associated with clicking a physical mouse button or trackpad. In some embodiments, the deep pressure intensity threshold corresponds to an intensity at which the device performs an action different from an action typically associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below the light pressure intensity threshold (e.g., above a nominal contact-detection intensity threshold IT0 below which contact is no longer detected), the device moves the focus selector according to the movement of the contact on the touch-sensitive surface without performing an action associated with the light pressure intensity threshold or the deep pressure intensity threshold. In general, unless otherwise specified, these intensity thresholds are consistent across various sets of values ​​for a user interface.

[0142] In some embodiments, the device's response to an input detected by the device depends on criteria based on the intensity of the contact during the input. For example, for some "light press" inputs, the intensity of the contact during the input that exceeds a first intensity threshold triggers a first response. In some embodiments, the device's response to an input detected by the device depends on criteria that include both the intensity of the contact during the input and time-based criteria. For example, for some "deep press" inputs, the intensity of the contact during the input that exceeds a second intensity threshold that is greater than the first intensity threshold for a light press triggers a second response only if a delay time has elapsed between meeting the first intensity threshold and meeting the second intensity threshold. This delay time is typically less than 200 milliseconds in duration (e.g., 40 milliseconds, 100 milliseconds, or 120 milliseconds, depending on the magnitude of the second intensity threshold, with the delay time increasing as the second intensity threshold increases). This delay time helps to avoid accidental deep press inputs. As another example, for some "deep press" inputs, there is a period of reduced sensitivity that occurs after the first intensity threshold is met. During the period of decreased sensitivity, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep pressure inputs. For other deep pressure inputs, the response to the detection of a deep pressure input does not depend on a time-based criterion.

[0143] In some embodiments, one or more of the input intensity threshold and / or corresponding output vary based on one or more factors, such as user settings, contact movement, input timing, running application, rate at which intensity is applied, number of simultaneous inputs, user history, environmental factors (e.g., ambient noise), position of focus selector, etc. Exemplary factors are described in U.S. Patent Application Publication Nos. 14 / 399,606 and 14 / 624,296, which are incorporated herein by reference in their entireties.

[0144] For example, FIG. 3A illustrates a dynamic intensity threshold 380 that varies over time based in part on the intensity of touch input 376 over time. Dynamic intensity threshold 380 is the sum of two components: a first component 374 that decays over time after a predetermined delay time p1 from when touch input 376 is first detected, and a second component 378 that tracks the intensity of touch input 376 over time. The initial, high intensity threshold of first component 374 reduces accidental triggering of a "deep press" response while still allowing an immediate "deep press" response if touch input 376 provides sufficient intensity. Second component 378 reduces unintentional triggering of a "deep press" response due to gradual intensity variations of the touch input. In some embodiments, a "deep press" response is triggered when touch input 376 meets dynamic intensity threshold 380 (e.g., at point 381 in FIG. 3A ).

[0145] FIG. 3B illustrates another dynamic intensity threshold 386 (e.g., intensity threshold I D ) is shown in Figure 3B. Two other intensity thresholds, the first intensity threshold I H and a second intensity threshold I L 3B, the touch input 384 reaches the first intensity threshold I before time p2. H and a second intensity threshold I L , but no response is provided until a delay time p2 has elapsed at time 382. Also in FIG. 3B, the dynamic intensity threshold 386 decays over time, and the decay occurs after a predetermined delay time p1 has elapsed from time 382 (the second intensity threshold I L This type of dynamic intensity threshold begins at time 388 (when the response associated with the first intensity threshold I H or the second intensity threshold I L A dynamic intensity threshold I is triggered immediately or simultaneously with triggering a response associated with a lower intensity threshold, such as D Reduce accidental triggering of responses associated with

[0146] FIG. 3C illustrates yet another dynamic intensity threshold 392 (e.g., intensity threshold I D ) is shown in Figure 3C. LThe response associated with the intensity threshold I is triggered after a delay time p2 from when the touch input 390 is first detected. At the same time, the dynamic intensity threshold 392 decays after a predetermined delay time p1 from when the touch input 390 is first detected. Therefore, the intensity threshold I is increased by a predetermined delay time p1 from when the touch input 390 is first detected, without the touch input 390 being released. L The decrease in intensity of touch input 390 after triggering a response associated with the touch input 390 may occur when the intensity of touch input 390 exceeds another intensity threshold, e.g., intensity threshold I L Even when the intensity threshold I D A response associated with the

[0147] Light pressure intensity threshold IT L From an intensity below the threshold IT L and deep pressure intensity threshold IT D The increase in the characteristic intensity of contact to an intensity between is sometimes referred to as a "light press" input. D From an intensity below the threshold IT D An increase in the characteristic intensity of a touch from an intensity below the touch detection intensity threshold IT0 to an intensity above the touch detection intensity threshold IT0 and a light pressure intensity threshold IT L An increase in the characteristic intensity of the contact to an intensity between ITO and ITO may be referred to as detecting a contact on the touch surface. A decrease in the characteristic intensity of the contact from an intensity above the contact-detection intensity threshold IT0 to an intensity below the contact-detection intensity threshold IT0 may be referred to as detecting lift-off of the contact from the touch surface. In some embodiments, IT0 is zero. In some embodiments, IT0 is greater than zero. In some examples, shaded circles or ellipses are used to represent the intensity of the contacts on the touch-sensitive surface. In some examples, unshaded circles or ellipses are used to represent each contact on the touch-sensitive surface without specifying the intensity of each contact.

[0148] In some embodiments described herein, one or more actions are performed including upon detecting a gesture including the respective pressure input, or including upon detecting a respective pressure input performed on the respective contact(s), where the respective pressure inputs are detected based at least in part on detecting an increase in intensity of the contact(s) above a pressure input intensity threshold. In some embodiments, the respective actions are performed including upon detecting an increase in intensity of the respective contact(s) above a pressure input intensity threshold (e.g., the respective actions are performed on the “downstroke” of the respective pressure input). In some embodiments, the pressure inputs include an increase in intensity of the respective contact(s) above a pressure input intensity threshold and a subsequent decrease in intensity of the contact(s) below the pressure input intensity threshold, where the respective actions are performed including upon detecting a subsequent decrease in intensity of the respective contact(s) below the pressure input threshold (e.g., the respective actions are performed on the “upstroke” of the respective pressure input).

[0149] In some embodiments, the device employs intensity hysteresis to avoid accidental input, sometimes referred to as “jitter,” and the device defines or selects a hysteresis intensity threshold that has a predetermined relationship to the press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Thus, in some embodiments, the press input includes an increase in the intensity of each contact above the press input intensity threshold and a subsequent decrease in the intensity of the contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and respective actions are performed in response to detecting the subsequent decrease in intensity of each contact below the hysteresis intensity threshold (e.g., the respective actions are performed on the “upstroke” of the respective press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and a respective action is performed in response to detecting the press input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, as the case may be).

[0150] For ease of explanation, descriptions of operations performed in response to a press input associated with a press input intensity threshold or in response to a gesture including a press input are, optionally, triggered in response to detecting an increase in the intensity of the contact above the press input intensity threshold, an increase in the intensity of the contact from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, a decrease in the intensity of the contact below the press input intensity threshold, or a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold. Further, in examples where an operation is described as being performed in response to detecting a decrease in the intensity of the contact below a press input intensity threshold, the operation is optionally performed in response to detecting a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to and lower than the press input intensity threshold. As noted above, in some embodiments, the triggering of these responses also depends on time-based criteria being met (e.g., a delay time elapsed between the first intensity threshold being met and the second intensity threshold being met). Exemplary User Interface and Associated Processes

[0151] Attention is now directed to embodiments of a user interface ("UI") and associated processes that may be implemented on an electronic device having a display generating component and one or more input devices, such as device 100 having a touch-sensitive display or a device having a separate display and touch-sensitive surface.

[0152] 2 is a schematic diagram of a touch-sensitive display used to present a user interface for a menu of an application, according to some embodiments. Optionally, a similar user interface is implemented on device 100 (FIG. 1A). In some embodiments, user interface 201a includes the following elements, or a subset or superset thereof: signal strength indicators 202 for wireless communications such as cellular and Wi-Fi signals; ●Time, ●Bluetooth indicator 205, ● Battery status indicator 206, Tray 203 with icons of frequently used applications, such as: An icon 216 for the phone module 138, labeled "Phone," optionally including an indicator 214 of the number of missed calls or voicemail messages; An icon 218 for the email client module 140, labeled "Mail," optionally including an indicator 210 of the number of unread emails; ○ An icon 220 for the browser module 147, labeled "Browser"; and ○ An icon 222 of the video and music player module 152 (also referred to herein as a video or video browsing application), also referred to as the IPOD (registered trademark of APPLE Inc.) module 152, labeled "iPoD", and ● Icons of other applications, such as: ○ Icon 224 of IM module 141, labeled "Messages" icon 226 of the calendar module 148, labeled "Calendar"; ○ Icon 228 of the image management module 144, labeled "Photos" ○ An icon 230 of the camera module 143, labeled "camera"; ○ Icon 232 of the online video module 155, labeled "Online Video"; Icon 234 of Stocks widget 149-2, labeled "Stocks" ○ Icon 236 of the map module 154, labeled "Map" ○ Icon 238 of weather widget 149-1, labeled "Weather" ○ Icon 240 of alarm clock widget 149-4, labeled "Clock" ○ An icon 242 for the fitness module 142, labeled "Fitness" ○ Icon 244 of the Notes module 153, labeled "Notes" A settings application or module icon 246 that provides access to settings related to the device 100 and its various applications; and Other icons for additional applications, such as App Store, iTunes®, Voice Memos, and Utilities.

[0153] Note that the icon labels shown in FIG. 2 are merely exemplary. Other labels are optionally used for various application icons. For example, the icon 242 for the fitness module 142 is alternatively labeled “Fitness Support,” “Workout,” “Workout Support,” “Exercise,” “Exercise Support,” or “Health.” In some embodiments, the label for each application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label for a particular application icon differs from the name of the application corresponding to that particular application icon.

[0154] In some embodiments, the home screen includes two areas: a tray 203 and an icon area 201. As shown in Figure 2, the icon area 201 is displayed on the tray 203. However, the icon area 201 and the tray 203 (also called the "dock") are optionally displayed in positions other than those described herein.

[0155] Tray 203 optionally contains icons of the user's favorite applications on computing device 100. Initially, tray 203 may contain a set of default icons. A user can customize tray 203 to include icons other than the default icons. In some embodiments, a user customizes tray 203 by selecting an icon from icon area 201 and dragging and dropping the selected icon into tray 203 to add the icon to tray 203. To remove an icon from tray 203, a user selects an icon that has been displayed in the favorites area for a threshold time, thereby causing computing device 100 to display a control for removing the icon. User selection of the control causes computing device 100 to remove the icon from tray 203. In some embodiments, tray 203 is replaced by dock 4006 (as described in more detail below); therefore, the details described above with respect to tray 203 may also apply to dock 4006 and can complement the description of dock 4006 provided below.

[0156] In this disclosure, references to a "split screen mode" refer to a mode in which at least two applications are displayed simultaneously on the display 112 side by side, allowing both applications to be interacted with (e.g., an email application and an instant messaging application are displayed in the split screen mode of FIG. 4E1). The split screen mode is also referred to as a "side-by-side" display configuration or a "split screen display" configuration. In some embodiments, at least two applications displayed simultaneously in the split screen mode may also be "pinned" to each other, which refers to an association (stored in the memory of the device 100) between the at least two applications that causes the two applications to be displayed together when either of the at least two applications reappears on the display. In some embodiments, affordances (e.g., drag handles displayed near the top edge of the application windows) may not be used to pin the applications, but instead, one of the at least two applications may be displayed to overlay the other; this overlay display mode is referred to as a slide over display mode (e.g., in FIG. 5E2, the email application and the instant messaging application are displayed in slide over mode). The slide over mode is also referred to as a "slide over" display configuration or a "slide over view." A Slide Over window may also be referred to as a background full-screen window or an "overlay" of a pair of split-screen windows. In some embodiments, at least two applications displayed simultaneously in Slide Over mode are not "pinned" to each other, so that when one of the at least two applications is displayed, the other application is optionally not simultaneously displayed, and optionally simultaneously displayed with another application. In some embodiments, affordances (e.g., drag handles displayed near the top edge of the application windows) may be used to pin the applications to each other and display them in split-screen mode.A user may further use a boundary affordance displayed within the boundary running between at least two applications while displayed in split-screen mode to unpin or dismiss one of the at least two applications (e.g., by reaching an edge of the display 112 bordering a first of the at least two applications and then dragging the boundary affordance until the first application is dismissed and the at least two applications are no longer pinned). The use of a boundary affordance (or a gesture at the boundary between two applications) to dismiss a pinned application is described in commonly owned U.S. patent application Ser. No. 14 / 732,618 (e.g., at Figures 37H-37M and related descriptive paragraphs), the entirety of which is incorporated herein by reference. While many examples provided herein refer to different applications displayed in split-screen mode and slide-over mode, many of these examples are also valid when windows of different applications are replaced with different windows of the same application displayed in split-screen mode or slide-over mode, unless otherwise noted.

[0157] 4A1-4A50, 4B1-4B51, 4C1-4C48, 4D1-4D19, and 4E1-4E28 are schematic diagrams of touch-sensitive displays used to present user interfaces for interacting with multiple applications and / or windows, according to some embodiments.

[0158] 4A1-4A50 illustrate user interface behavior of application windows displayed in slide over mode, according to some embodiments. Interaction with an overlay switcher user interface for simultaneously displaying multiple slide over windows corresponding to different applications is also described. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 5A-5I. For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device having touch-sensitive display system 112. In such embodiments, the focus selector is optionally a respective finger or stylus contact, a representative point corresponding to the finger or stylus contact (e.g., the face center of each contact or a point associated with each contact), or the face center of two or more contacts detected on touch-sensitive display system 112. However, similar operations, along with a focus selector, are optionally performed on a device having display 450 and a separate touch-sensitive surface 451 in response to detecting contacts on touch-sensitive surface 451 while displaying the user interface shown in the figures on display 450.

[0159] As background for the following description, in some embodiments, a home screen user interface includes multiple application icons corresponding to different applications installed on the device. Each application icon, when activated by a user (e.g., by a tap input), causes the device to launch the corresponding application and display the application's user interface (e.g., a default initial user interface or a last-displayed user interface) on the display. A dock is a container user interface object that includes a subset of application icons selected from the home screen user interface to provide quick access to a few frequently used applications. The application icons included in the dock are, optionally, selected by the user (e.g., via a settings user interface) or automatically selected by the device based on various criteria (e.g., frequency of use or time since last use). In some embodiments, the dock is displayed as part of the home screen user interface (e.g., overlaying the bottom of the home screen user interface). In some embodiments, the dock is displayed over a portion of another user interface (e.g., an application user interface) independent of the home screen user interface in response to a user request (e.g., a gesture that meets dock display criteria (e.g., an upward swipe gesture starting from the bottom edge of the touchscreen)). The application switcher user interface displays representations of multiple recently opened applications (e.g., arranged in order based on when the applications were last displayed), each of which, when selected (e.g., by a tap input), causes the device to re-display the last displayed user interface of each recently opened application on the screen.In some embodiments, the application switcher user interface displays windows in different display configurations (e.g., full-screen windows, slide-over and split-screen windows, minimized windows, and / or draft windows) that may correspond to the same application or different applications.

[0160] As shown in FIG. 4A1 , a first application window of a first application (e.g., window 4002 of a map application) is displayed on touch screen 112 in a standalone display configuration (e.g., a full-screen display configuration) without being displayed concurrently with another application window of the same or a different application. First application window 4002 displays a portion of a first user interface of the first application (e.g., a searchable map interface). As shown in FIGS. 4A1-4A2 , an input (e.g., an upward edge swipe input with contact 4004) that meets dock display criteria is detected on touch screen 112 (e.g., near the bottom edge of touch screen 112). In response to detecting the input that meets the dock display criteria, dock 4006 is displayed to overlay the first application window (e.g., window 4002) of the first application. The dock 4006 includes multiple application icons corresponding to different applications (e.g., icon 216 for a phone application, icon 218 for an email application, icon 220 for a browser application, and icon 232 for an online video application). In some embodiments, the dock includes application icons for the currently displayed application (e.g., a maps application) and one or more most recently displayed applications. In some embodiments, the dock is temporarily removed from the display in response to an input that meets dock rejection criteria (e.g., a downward swipe gesture on the dock moving toward the bottom edge of the touchscreen).

[0161] 4A4-4A7, in some embodiments, a second application window (e.g., window 4010 in FIG. 4A7) of a second application (e.g., an online video application) is displayed to overlay a first application window (e.g., window 4002) of a first application in a slide-over display configuration. The second application window of the second application displays a portion of a second user interface of the second application (e.g., a media player user interface of the online video application). As shown in FIG. 4A4, while first window 4002 of the first application (e.g., a maps application) is displayed, an input meeting a selection criterion (e.g., a stationary touch-and-hold input or a light press input by contact 4008) is detected on application icon 232 of the online video application, allowing subsequent movement of the input (e.g., movement from the touch-down position of contact 4008) to initiate a drag action on application icon 232. 4A5 and 4A6, a representation of a second application (e.g., representation 4012) is dragged across the touchscreen in accordance with movement of the input (e.g., movement of contact 4008). As shown in FIG. 4A5, when contact 4008 is over a portion of the touchscreen that displays a first user interface of a first application (e.g., a map application) and is within a threshold distance from a predetermined side edge (e.g., the right edge and / or the left edge) of the touchscreen (e.g., outside a first predefined portion of the touchscreen (e.g., predefined region 4014 (also referred to as predefined region 4308 in FIG. 4D3 and zone F in FIG. 4E8)), representation 4012 of the second application being dragged by contact 4008 has a first appearance (e.g., the same appearance as original application icon 232) that indicates that if the input ends at the current position (e.g., if lift-off of contact 4008 is detected), the drag action is canceled and the display state shown before the detection of the input is restored.When contact 4008 moves over a portion of the touchscreen that is within a first predefined portion of the touchscreen (e.g., predefined area 4014), the electronic device displays visual feedback (e.g., representation 4012 of the second application is elongated) indicating that if the input terminates at the current location within the first predefined portion of the touchscreen, the window of the second application will be displayed together with the first window of the first application in their respective simultaneous display configurations (e.g., a slide-over display configuration in which the window of the second application overlays a portion of the first window of the first application), as shown in FIG. 4A6. In some embodiments, other visual feedback is provided, such as reducing the display size of the first window 4002 of the first application on the touchscreen (e.g., clarifying the background behind the perimeter of the reduced first window) and / or changing the visual clarity of the first window 4002 of the first application (e.g., blurring and / or darkening the window 4002) to indicate that the second application (e.g., an online video application) will be opened in a slide-over display configuration along with the currently open application (e.g., a maps application). As shown in FIG. 4A7 , after the input ends while contact 4008 is over the first predefined portion 4014 of the touchscreen, the device opens the window of the second application (e.g., window 4010 of the online video application) to overlay a portion of the first window of the first application (e.g., window 4002 of the maps application) and at least a portion of the first predefined portion 4014 of the touchscreen. In some embodiments, if the second application has no windows open or only one window open at the time contact 4008 is detected, window 4002 is displayed in the configuration shown in FIG. 4A7.In some embodiments, if the second application has multiple windows open, representations of the second application's multiple windows are displayed (e.g., in a window selector user interface of the second application), and the user selects one of the multiple windows (e.g., by tapping the representation of the desired window of the second application in the window selector user interface) to display in a slide-over configuration with the first application. Further details regarding behavior regarding multiple windows of the second application are described, for example, in connection with Figures 4D1-4D19.

[0162] 4A8-4A11, another input by contact 4016 selects a third application (e.g., a touch-and-hold input or a light press input on application icon 220 for a browser application) in a manner similar to that shown in FIGS. 4A4-4A7 for a second application (e.g., an online video application) and drags a representation of the third application (e.g., representation 4018) across the touchscreen, following the movement of the input (e.g., an initial resting portion of the input by contact 4016 followed by the movement of contact 4016). As shown in FIG. 4A10, when contact 4016 is within predefined region 4014 near a side edge of the touchscreen, representation 4018 of the third application is elongated and expanded horizontally to indicate that if the input were to end in its current position, the window of the third application (e.g., the browser application) would be displayed in a slide-over display configuration with first window 4002 of the first application (e.g., a maps application). 4A11, in response to detecting the end of input by contact 4016 (e.g., in response to detecting lift-off of contact 4016), the device displays browser application window 4020 so as to overlay a portion of map application window 4002. As shown in FIG. 4A11, browser application window 4020 either completely obscures window 4010 or replaces window 4010 so as to overlay map application window 4002 as a currently displayed slide-over window.

[0163] 4A1-4A11 result in the addition of multiple slide-over windows (e.g., window 4010 and window 4020) to a series of zero or more slide-over windows stored in the device's memory. Figures 4A12-4A50 illustrate various interactions with the series of slide-over windows starting from the state shown in Figure 4A12, such as, for example, interactions with a slide-over window of one application that is displayed to overlay a portion of a full-screen window of another application (e.g., the same application as the application corresponding to the slide-over window or a different application).

[0164] 4A12, multiple inputs (e.g., multiple swipe inputs) are represented on the touchscreen (e.g., by different contacts 4021, 4022, 4023, 4024, 4025, 4026, 4027, and 4066) corresponding to inputs at different locations and / or different movement directions. In some embodiments, these inputs are distinct inputs detected on the screen at different times when the screen is displaying window 4020 and window 4002 in slide over mode. In some embodiments, the device detects a single input, determines characteristics of the input based on a position and / or direction of movement of the input, and performs different actions, such as those described in connection with Figures 4A13-4A50, according to the position and / or direction of movement of the input (e.g., system-level actions (such as navigating between applications, switching between slide-over windows, converting between display configurations, opening documents across multiple applications, etc.) or application-level actions (such as activating a user interface element within a user interface of a displayed application, scrolling a user interface within a displayed application, etc.)).

[0165] 4A13-4A14, which follow FIG. 4A12, contact 4024 input is detected at a location corresponding to a drag handle region of slide-over window 4020 (e.g., near the top edge of window 4020), and the input includes movement of contact 4024 in a first direction (e.g., substantially horizontally to the left) toward the side edge of the display opposite the side occupied by window 4020. As shown in FIG. 4A13, slide-over window 4020 is dragged across the display to overlay a portion of window 4002. In FIG. 4A13, even though window 4020 is dragged away from its original position on the right side of the display, previously displayed slide-over window 4010 is not uncovered or displayed in its original position on the right side of the display after window 4020 has been moved by the drag input of contact 4024. In FIG. 4A14, after input by contact 4024 ends near the left edge of the display (e.g., after liftoff of contact 4024 is detected within a first threshold distance from the left edge of the display and within a second threshold distance from the top edge of the display, such as in zone H or zone B of FIG. 4E8), the device displays window 4020 overlaying a portion of window 4002 on the left side of the display (e.g., in a modified simultaneous display configuration from the previous one (e.g., swapped sides but remaining in slide-over mode)).

[0166] In FIG. 4A15, which follows FIG. 4A12, input by contact 4025 is detected at a location corresponding to a drag handle region of slide-over window 4020 (e.g., near the top edge of window 4020), and the input includes movement of contact 4025 in a second direction (e.g., slightly downward and to the right) toward a side edge of the display (e.g., the side edge occupied by window 4020) and terminating in zone E shown in FIG. 4E8. As shown in FIG. 4A15, in response to the input terminating within zone E (FIG. 4E8), slide-over window 4020 is converted to parallel window 4028, and full-screen window 4002 is converted to parallel window 4030. Window 4028 and window 4030 are displayed in a side-by-side display configuration (or split-screen mode). In this scenario, window 4028 and window 4030 are pinned to each other and will appear together in a split-screen configuration when either window later reappears on the display. Additionally, slide over window 4020 is removed from the set of slide over windows stored in memory and will not reappear on the display as a slide over window.

[0167] 4A12, in Figures 4A16-4A18, which follow Figure 4A12, input by contact 4021 is detected at a location within a bottom edge region of the touchscreen, the input including movement of contact 4021 in a third direction (e.g., upward) toward the top edge of the touchscreen. As shown in Figures 4A16-4A18, pursuant to a determination that the input meets the application switcher display criteria (e.g., the velocity and / or distance of the input meets a predetermined velocity and / or distance threshold for navigating to the application switcher user interface), an animated sequence is displayed illustrating a transition from the current display state of the screen (e.g., Figure 4A12) to the display of application switcher user interface 4032 (e.g., also referred to as a multitasking user interface) (e.g., Figure 4A18). In the animated sequence, full-screen window 4002 is reduced in size and moves upward in conjunction with the movement of contact 4021. Slide-over window 4020 is reduced in size and moved away from the representation of window 4002 so as not to overlap in transition user interface 4032' shown in Figure 4A16. In Figure 4A17, other windows stored in the device's memory (e.g., recently opened windows with states stored in memory) are made apparent in transition user interface 4032', including full-screen windows, split-screen windows, and slide-over windows that are currently on the device and can be redisplayed on the display in their stored display states.FIG. 4A18 shows an application switcher user interface 4032 that includes representations of full-screen windows (e.g., representation 4002' of window 4002, representation 4034' of full-screen email window 4034), representations of pairs of windows displayed in split-screen mode (e.g., representation 4036' of window 4030 and window 4028 displayed in split-screen mode, and representation 4038' of a browser window and an email window displayed in split-screen mode), and representations of slide-over windows (e.g., representation 4020' of window 4020, representation 4010' of window 4010, representation 4040' of an email slide-over window, and representation 4042' of a photo slide-over window).

[0168] In some embodiments, windows having different display configurations are displayed in groups in different areas of application switcher user interface 4032, and within each group, the windows are ordered according to their respective timestamps of when they were last displayed. For example, in the area containing representations of slide-over windows, window 4020 is the most recently displayed slide-over window, and its corresponding representation 4020' is displayed in the leftmost position in the row, next to which is displayed representation 4010' of slide-over window 4010. The slide-over windows represented by representations 4040' and 4042' were displayed at a time before window 4010 was last displayed.

[0169] In some embodiments, each representation of an application window in the application switcher user interface 4032 is displayed with an identifier for that window's application (e.g., the application name and application icon) and an identifier for that application's window (e.g., a window name that is automatically generated based on the window's contents).

[0170] In some embodiments, each representation of a window within the application switcher user interface, when activated (e.g., by a tap input), causes the device to re-display that window on the display. If the activated representation corresponds to a full-screen window (e.g., window 4002 or window 4034), that window is re-displayed on the screen in a full-screen, standalone display configuration without another application simultaneously displayed on the screen. In some embodiments, even if the full-screen window was last displayed at the same time as another slide-over window on top, when the full-screen window is re-displayed on the screen from the application switcher user interface 4032, the full-screen window is displayed without the topmost slide-over window. In some embodiments, when a representation of a slide-over window (e.g., window 4020, window 4040, or window 4042 of window 4010) is activated within the application switcher user interface 4032, the slide-over window is re-displayed on the display with another full-screen or split-screen window behind it (e.g., window 4002, window 4034, or a pair of windows in a split-screen configuration). In some embodiments, the window behind the slide over window is a full-screen window or a pair of split-screen windows that was on the display immediately prior to the display of application switcher user interface 4032. In some embodiments, the window behind the slide over window is the last window displayed simultaneously with the slide over window. In some embodiments, when a representation of the pair of split-screen windows (e.g., representation 4036′ or representation 4038′) is activated in application switcher user interface 4032, the pair of split-screen windows reappears on the display together in split-screen mode.

[0171] In FIGS. 4A19-4A21, which follow FIG. 4A12, input by contact 4022 is detected at a position within the bottom edge region of slide-over window 4020, and this input includes movement of contact 4022 in a fourth direction (e.g., a substantially horizontal direction) toward the edge of the screen on which slide-over window 4020 is displayed (e.g., the right edge of the screen). In response to the input by contact 4022, slide-over window 4020 is dragged toward the right edge of the screen and is removed from the screen after the input terminates. During the movement of contact 4022 and window 4020, other windows in the stack of slide-over windows stored in the device's memory are represented on the display. For example, as shown in FIGS. 4A19 and 4A20, representations of windows 4010, 4040, and 4042 emerge from below window 4020. The order of windows 4020, 4010, 4040, and 4042 corresponds to the order in which these windows were last displayed on the screen. In some embodiments, windows 4020, 4010, 4040, and 4042 are displayed at different depths perpendicular to the surface of the screen (e.g., decreasing in size and transparency as the distance from the surface increases). This differs from the scenarios of FIGS. 4A13-4A14, in which there was no indication that other windows were below window 4020 as window 4020 was dragged toward the other side of the screen (e.g., no other windows emerged from below window 4020). In FIGS. 4A19 and 4A20, as window 4020 is dragged toward the right edge of the screen with input directed toward the bottom edge of window 4020, the next window in the stack of slide-over windows (e.g., window 4010) gradually appears, eventually becoming the topmost window displayed overlaying full-screen window 4002 (as shown in FIG. 4A21).

[0172] 4A22-4A25, which follow FIG. 4A21, an input by contact 4046 is detected at a position within the bottom edge region of slide-over window 4010, and this input includes movement of contact 4046 in a fourth direction (e.g., a substantially horizontal direction) toward the edge of the screen on which slide-over window 4010 is displayed (e.g., the right edge of the screen). In response to the input by contact 4046, slide-over window 4010 is dragged toward the right edge of the screen and is removed from the screen after the input terminates. During the movement of contact 4046 and window 4010, other windows in the stack of slide-over windows stored in the device's memory are represented on the display. For example, as shown in FIG. 4A23, representations of windows 4040, 4042, and 4020 emerge from below window 4010. In general, if input by contact 4046 is detected within a threshold time after input by contact 4022, the original top window 4020 is shuffled to the bottom of the stack (e.g., as shown in FIG. 4A23), even if window 4020 is the most recently displayed window other than window 4010. If input by contact 4046 is detected after window 4010 has been displayed as the top window for more than the threshold time, the stack is sorted based on the order in which the windows were last displayed, and window 4020 is inserted between window 4010 and window 4040 in the stack shown in FIG. 4A23. In some embodiments, the slide-over stack of windows is only re-sorted based on the time the windows were last displayed (e.g., as shown in FIGS. 4A28-4A29) once the entire stack of slide-over windows is removed from the display. In FIG. 4A24, after input by contact 4046 has ended, window 4040 is displayed as a slide-over window overlaying full-screen window 4002.

[0173] 4A25-4A27, which follow FIG. 4A24, an input by contact 4048 is detected at a location within the bottom edge region of slide-over window 4040, and the input includes movement of contact 4048 in a fifth direction (e.g., a substantially horizontal direction) away from the edge of the screen on which slide-over window 4040 is displayed (e.g., the right edge of the screen). In response to the input by contact 4048, slide-over window 4010, which was just removed from the display, is dragged back onto the screen so as to overlay window 4040. During the movement of contact 4048 and window 4010, other windows in the stack of slide-over windows stored in the device's memory are represented on the display. For example, as shown in FIG. 4A26, representations of windows 4040, 4042, and 4020 emerge from below window 4010. In some embodiments, the windows in the stack of slide-over windows are arranged in a circular carousel with the bottom card and the top card positioned adjacent to each other. Swiping in one direction scrolls the window in that direction within the circular carousel, and swiping in the opposite direction scrolls the window in the opposite direction. After the end of the input by contact 4048 is detected, window 4010 is displayed as a slide-over window overlaying full-screen window 4002, as shown in FIG. 4A27. This is also in contrast to the scenario of dragging the top-most slide-over window to the other side of the screen with input directed at the top edge region of the top-most slide-over window, where no other windows appear below or are added above the top-most slide-over window as the input is moved.In this scenario, when the top slide-over window (e.g., window 4040) is flicked or dragged from the right edge of the screen toward the left, another window (e.g., window 4010) appears above the dragged window (e.g., window 4040), and at least one window (e.g., window 4042 and window 4020) appears below the dragged window (e.g., window 4010).

[0174] 4A28-4A29, which follow FIG. 4A12, input by contact 4027 is detected at a location near the left edge of slide-over window 4020, and the input includes movement of contact 4027 in a sixth direction (e.g., a substantially horizontal direction) toward the edge of the screen on which slide-over window 4020 is displayed (e.g., the right edge of the screen). In some embodiments, the device requires that the input be detected on or within a threshold distance of the left edge of window 4020 to trigger an action to remove the stack of slide-over windows from the display. In some embodiments, as shown in FIG. 4A28, during movement of contact 4027 toward the right edge of the display, window 4020 is gradually dragged out of the display, and visual indications of other windows in the stack of slide-over windows are shown to follow the movement of window 4020. After the end of input by contact 4027 is detected, window 4020 is removed from the display, and no other slide-over windows are displayed on the display simultaneously with background window 4002. Window 4002 is displayed as a full-screen window in a standalone display configuration, rather than as a full-screen background window of a slide-over window in a slide-over display configuration. This contrasts with the scenario shown in FIG. 4A50, which follows FIG. 5A12, in which input by contact 4026 detected outside slide-over window 4020 and including movement in a sixth direction (e.g., a substantially horizontal direction toward the right edge of the display) shifts the user interface within window 4002 to the right in accordance with the movement of contact 4026, without moving slide-over window 4020. This also contrasts with the scenario shown in FIG. 4A19-4A21, which follows FIG. 4A12, in which a rightward swipe input by contact 4022 slides window 4020 out of the display, causing underlying window 4010 to become a slide-over window overlaying background window 4002 after the input is terminated.

[0175] 4A29, in Figures 4A30-4A32, input by contact 4052 is detected on a side edge of the display (e.g., the side of the screen that previously displayed a slide over window (e.g., window 4020)), and the input includes movement in a seventh direction (e.g., a substantially horizontal direction) from the side edge of contact 4052 onto the display. In response to detecting the input by contact 4052, the last-displayed slide over window (e.g., window 4020) is dragged back onto the display to overlay the currently-displayed full-screen window (e.g., window 5004), as shown in Figure 4A32. In some embodiments, if a window on the display has been switched to another full-screen window in a standalone display configuration (e.g., a full-screen window displayed in response to tapping an application icon in a dock, selecting an application from a set of windows that opened after the application icon was tapped, or an application switching gesture (e.g., a horizontal swipe along the bottom edge of the currently displayed standalone window)), then in response to detecting a contact input detected on a side edge of the display that includes horizontal movement of the contact from the side edge onto the screen, the last-displayed slide-over window (e.g., window 4020) is dragged back onto the display to overlay the currently displayed full-screen window (e.g., a full-screen window other than window 4002). In FIG. 4A31 , as window 4020 is dragged back onto the display with leftward movement of contact 4052, representations of the other windows in the stack of slide-over windows are displayed below window 4020.

[0176] In some embodiments, in contrast to the scenario shown in FIGS. 4A30-4A32, which follow FIG. 4A12, a contact input is detected within an area a threshold distance from a side edge of the display (e.g., a side edge of a screen that previously displayed a slide-over window (e.g., window 4020)), and the input includes movement of contact 4052 from the side edge onto the display in a seventh direction (e.g., a substantially horizontal direction). In response to detecting this contact input, the last-displayed slide-over window (e.g., window 4020) is not dragged back onto the display. Instead, the input causes an action within an application (e.g., a maps application) corresponding to the input to be performed, such as shifting a searchable map user interface displayed in window 4002 relative to the display in response to the movement of the contact.

[0177] 4A33-4A34, which follow FIG. 4A12, input by contact 4023 is detected on a bottom edge of a slide-over window (e.g., window 4020), the input including movement of contact 4023 in an eighth direction (e.g., upward) across the display. In response to detecting the input by contact 4023 and following a determination that the movement of contact 4023 meets predetermined criteria (e.g., exceeds a threshold amount of movement in the eighth direction or exceeds a threshold amount of velocity in the eighth direction), the device displays transition user interface 4053 including a representation (e.g., representation 4020′) of slide-over window 4020 that moves in accordance with the movement of contact 4023. In some embodiments, a background window (e.g., window 4002) is visually obscured (e.g., blurred or darkened) beneath the representation of the slide-over window in transition user interface 4053. In some embodiments, representations of other slide-over windows in the stack of slide-over windows (e.g., representations 4010′, 4040′, and 4042′) are displayed below the representation of the topmost slide-over window (e.g., representation 4020′) as the representation of the topmost slide-over window is dragged within the display in accordance with movement of contact 4023. In some embodiments, the representations of the slide-over windows are dynamically updated (e.g., resized) according to the current position of the representations (and contact 4023) on the display. In FIG. 4A34 , lift-off of contact 4023 has been detected, and the device displays a slide-over window switcher user interface or overlay switcher user interface 4054 for only those slide-over windows currently stored in the stack of slide-over windows stored in memory. In some embodiments, representations of the slide-over windows in the stack of slide-over windows are displayed and individually selectable within overlay switcher user interface 4054.The behavior of the overlay switcher user interface 4054 is similar to the application switcher user interface (e.g., application switcher user interface 4032 of FIG. 4A18) in that tapping on a representation of a slide-over window in the overlay switcher user interface 4054 causes the slide-over window to be displayed. As shown in FIG. 4A34, in some embodiments, the representations of slide-over windows in the stack of stored slide-over windows are spread out on a background without overlapping each other. In some embodiments, the representations of the slide-over windows are reduced-scale images of the slide-over windows. In some embodiments, some of the representations of the slide-over windows are not displayed due to constraints on the display size and the total number of slide-over windows in the stack. For example, in FIG. 4A34, there are a total of four slide-over windows in the stack, and the representation of one of those windows (e.g., representation 4042′) is initially only partially visible in the overlay switcher user interface 4054. If there are additional slide-over windows in the stack, the representations of those additional slide-over windows are initially not visible in the overlay switcher user interface 4054. In some embodiments, instead of displaying the representations of the slide-over windows in the overlay switcher user interface in a fully expanded configuration, the representations are displayed in a stack with the underlying representations offset by a different amount than the topmost slide-over window representation.

[0178] 4A35 displays an overlay switcher user interface 4054 that includes a representation of a slide-over window that is currently in a stack of slide-over windows. Several inputs (e.g., tap inputs and swipe inputs) are represented on the touch screen (e.g., by different contacts 4056, 4058, 4059, 4060, 4062, and 4064) corresponding to different positions, input types, and / or different movement directions. In some embodiments, these inputs are distinct inputs detected on the screen at different times when the screen is displaying the overlay switcher user interface 4054. In some embodiments, the device detects a single input, determines characteristics of the input based on the input's location, input type, and / or movement direction, and performs different actions as described in connection with Figures 4A36-4A42 depending on the input's location, input type, and / or movement direction (e.g., different system-level actions such as navigating or browsing within the overlay switcher user interface, exiting the overlay switcher user interface to display a previously displayed or selected window, closing a window in a stack of slide-over windows, etc.).

[0179] 4A36-4A37, which follow FIG. 4A35, an input by contact 4056 is detected on one of the displayed representations (e.g., representation 4010′), the input including movement of contact 4056 in a ninth direction across the display (e.g., horizontally (e.g., to the right)). In response to detecting the input by contact 4056 and following a determination that the input meets preset criteria (e.g., the location of contact 4056 is on a representation of a slide over window and the direction of movement of contact 4056 is horizontal), the device scrolls overlay switcher user interface 4054 to reveal representations of the slide over window that are not currently displayed or are not fully displayed within the overlay switcher user interface. In some embodiments, as shown in FIGS. 4A35 and 4A36, following the movement of contact 4056, representations displayed near one side of the display (e.g., representation 4020′) gradually disappear outside the display, and representations on the other side of the display gradually appear on the display. 4A37, the representation that is moved off the display is added to the end of a stack (e.g., a stack with a tail and a head connected to each other, similar to a circular carousel) and reappears on the other side of the display as contact 4056 continues to move in the same direction. In some embodiments, the device does not require contact 4056 to be detected on a representation of a slide-over window in overlay switcher user interface 4054; scrolling of overlay switcher user interface 4054 occurs as long as the input includes movement that exceeds a threshold amount in the horizontal direction. In some embodiments, the direction of scrolling is determined according to the direction of movement of the contact across the display.

[0180] In FIGS. 4A38-4A39, which follow FIG. 4A35, input by contact 4058 is detected on one of the displayed representations (e.g., representation 4010′), the input including movement of contact 4058 in a tenth direction (e.g., vertically (e.g., upward)) across the display. In response to detecting input by contact 4058, the representation is removed from overlay switcher user interface 4054, and the slide-over window represented by the removed representation is removed from the stack of stored slide-over windows in memory. In other words, the slide-over window corresponding to the removed representation is “closed.” In FIG. 4A39, representations of the other windows that are not closed (e.g., representations 4042′, 4040′, and 4020′) remain displayed in overlay switcher user interface 4054.

[0181] In FIG. 4A40, which follows FIG. 4A35, a tap input by contact 4059 is detected on representation 4010′ of window 4010, and in response to detecting the tap input by contact 4059, the device stops displaying the overlay switcher user interface and displays slide over window 4010 in slide over mode along with the full screen background window. In some embodiments, the full screen background window is the full screen window last displayed (e.g., window 4002), regardless of whether the full screen window was last displayed along with the selected slide over window. In some embodiments, the full screen background window is the full screen window last displayed along with the selected slide over window (e.g., window 4002).

[0182] 4A35, in FIG. 4A41, a tap input by contact 4060 is detected on representation 4040′ of window 4040, and in response to detecting the tap input by contact 4060, the device stops displaying overlay switcher user interface 4054 and displays slide over window 4040 in slide over mode with a full-screen background window. In some embodiments, the full-screen background window is the full-screen window last displayed (e.g., window 4002), regardless of whether the full-screen window was last displayed with the selected slide over window. In some embodiments, the full-screen background window is the full-screen window last displayed with the selected slide over window (e.g., window 4002 or another window different from window 4002).

[0183] In FIG. 4A42, which follows FIG. 4A35, a tap input with contact 4062 is detected on representation 4020′ of window 4020, and in response to detecting the tap input with contact 4062, the device stops displaying overlay switcher user interface 4054 and displays slide over window 4020 in slide over mode along with a full-screen background window. In some embodiments, the full-screen background window is the full-screen window last displayed (e.g., window 4002), regardless of whether the full-screen window was last displayed along with the selected slide over window. In some embodiments, the full-screen background window is the full-screen window last displayed along with the selected slide over window (e.g., window 4002).

[0184] 4A42 is also displayed in response to a tap input by contact 4064 detected on a portion of overlay switcher user interface 4054 that is not occupied by any representation of a slide-over window. In some embodiments, overlay switcher user interface 4054 includes a close affordance, and a tap input detected on the close affordance also causes the device to stop displaying overlay switcher user interface 4054 and re-display the last displayed user interface state (e.g., window 4020 overlaying window 4002 in slide-over mode).

[0185] 4A42, subsequent Figures 4A43-4A46 illustrate that a swipe input by contact 4066 is detected within a bottom edge region of the display, and that the movement of contact 4066 is substantially horizontal (e.g., includes no vertical movement or includes a small amount of vertical movement relative to the horizontal movement). In response to the edge swipe input, and in accordance with a determination that the edge swipe input meets the application switching criteria (e.g., meets the distance and velocity criteria of the application switching criteria), window 4002 is dragged off the screen and replaced with window 4034, which was the last full-screen window displayed before window 4002. As shown in Figures 4A43-4A45, while the background full-screen window is being changed, slide over window 4020 is unaffected by the input by contact 4066. After the input by contact 4066 ends, slide over window 4020 is overlaid on window 4034 in slide over mode, as shown in Figure 4A46. 4A43-4A46 may also begin with the user interface shown in FIG. 4A12. In some embodiments, the user interface shown in FIG. 4A12 does not include the dock (e.g., after it has been removed by a downward swipe on the dock). In some embodiments, window 4034 is a full-screen window of another application (e.g., an email application) that is different from the full-screen window of the application (e.g., a maps application) that was originally displayed below slide-over window 4020. In some embodiments, window 4034 is a full-screen window of the same application as the full-screen window that was originally displayed below slide-over window 4020.

[0186] 4A46, another input by contact 4068 is detected on a document (e.g., an email message of a series of email messages in an email application) displayed in window 4034. If the initial portion of the input by contact 4068 meets the criteria for initiating a drag action on the document (e.g., the input is a tap-and-hold input that remains substantially stationary for at least a threshold time after touchdown of the contact on the document, or the input is a light press input where the intensity of the contact exceeds a nominal contact detection intensity threshold), the document is selected (e.g., as indicated by a visual highlighting of the document).

[0187] In Figure 4A47, representation 4070 of the document is dragged across the display following the movement of contact 4068. In Figure 4A48, when contact 4068 is within a predefined area of ​​the display (e.g., predefined area 4014 for opening a Slide Over window by dropping an application icon onto it, or a reduced-size version of predefined area 4014), the representation of the document is transformed (e.g., to representation 4044') to show a preview of the new Slide Over window that displays the document in the document's native application.

[0188] In FIG. 4A49, after the input ends (e.g., after liftoff of contact 4068 is detected within default area 4014 or a reduced-size version of default area 4014), the document is opened within a slide-over window of the document's native application (e.g., a slide-over window of an email application), and slide-over window 4044 displaying the document becomes the topmost slide-over window overlaying background fullscreen window 4034.

[0189] In some embodiments, if the input ends elsewhere on the display, other actions may be performed. For example, in some embodiments, if the input ends within an area of ​​the display that corresponds to opening a new window in split view mode, the document is opened in a new window displayed side-by-side with a resized version (e.g., a reduced-width version) of the email application window 4034. In some embodiments, if the input ends within an area of ​​the display that is above the Slide Over window but outside the default area for opening a new window for the document, and the Slide Over window presents an acceptable drop location for the document, the document is inserted at this drop location within the Slide Over window (e.g., inserted into another document, or message, or storage location displayed within the Slide Over window). In some embodiments, if the input ends outside the Slide Over window, the document is dropped within window 4034 at an acceptable drop location (if available) that corresponds to the input's ending location, or is returned to its original location if an acceptable drop location is not available.

[0190] In FIG. 4A50, which follows FIG. 4A12, input by contact 4026 is detected outside of slide-over window 4020, including movement of contact 4026 in each direction. In response to the movement of contact, the device performs an action within the application corresponding to background fullscreen window 4002, such as shifting a map in accordance with the movement of contact 4026. Because the starting position of contact 4026 is outside of slide-over window 4020, an application-level action is initiated and continues as the contact subsequently moves over the area where slide-over window 4020 is displayed.

[0191] 4B1-4B51 illustrate user interface behavior in response to a user request to switch applications by selecting an application icon, according to some embodiments. The request to switch applications is integrated into the same gesture with a request to view the application's window switcher user interface. The device automatically determines whether to switch applications or display the currently displayed application's window switcher user interface based on whether the currently displayed application currently has two or more windows. User interaction with a window switcher user interface that simultaneously displays multiple windows corresponding to respective applications is also described according to some embodiments. The user interfaces in these figures are used to illustrate processes described below, including those in FIGS. 6A-6E. For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device having touch-sensitive display system 112. In such embodiments, the focus selector is optionally a respective finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., an encenter of each contact or a point associated with each contact), or an encenter of two or more contacts detected on touch-sensitive display system 112. However, a similar operation is optionally performed on a device having display 450 and separate touch-sensitive surface 451 in response to detecting a contact on touch-sensitive surface 451 while displaying the user interface shown in the figure on display 450, along with a focus selector.

[0192] 4B1-4B4 show interactions in which a user selects an application icon to open the corresponding application while the corresponding application is currently displayed.

[0193] As shown in FIG. 4B1 , a full-screen window 4102 of an email application is displayed on touch screen 112. In this example, full-screen window 4102 is displayed in a full-screen, standalone display configuration, with no other windows simultaneously displayed on the screen. In some embodiments, the device has the same response, described below, regardless of whether full-screen window 4102 is displayed in a standalone configuration or in slide-over mode as a background window of a slide-over window (e.g., of the same or a different application). In FIG. 4B1 , an input by contact 4104 is detected at a location on the screen corresponding to a first application icon (e.g., application icon 218 for an email application) in dock 4006 overlaid on full-screen window 4102. In response to detecting the input and following a determination that the input meets selection criteria (e.g., the input meets criteria (e.g., location and time criteria) for detecting a tap input on an application icon), the device determines whether the selected icon corresponds to the application of the currently displayed window. In this scenario, the currently displayed window (e.g., window 4102) and the selected application icon (e.g., application icon 218) both correspond to an email application. In response to determining that the currently displayed window (e.g., window 4102) and the selected application icon (e.g., application icon 218) both correspond to an email application, the device determines whether the application is associated with multiple windows (e.g., whether multiple open windows are stored in memory as "open" windows that can be redisplayed on the screen in their saved last display states).In this scenario, pursuant to a determination that the email application currently has two or more open windows, the device displays a window switcher user interface 4018 (FIG. 4B4) that simultaneously displays representations of the multiple open windows associated with the email application. This is in contrast to a scenario in which the application icon for the email application is activated by input that meets the selection criteria when the email application is not the currently displayed application (e.g., when another application is the currently displayed application or when a system user interface (e.g., a home screen user interface) is currently displayed).

[0194] In Figures 4B2-4B3, in response to a determination that the input by contact 4104 meets the selection criteria, that the currently displayed window and the selected application icon correspond to the same application, and that the application is associated with multiple windows, an animated transition is displayed. The animated transition illustrates that the currently displayed full-screen window 4102 is reduced in size to become a representation (e.g., a reduced-scale image) 4102' of window 4102, and that representations of other windows (e.g., representation 4016' of slide-over email window 4106 and representations 4110' of the email and photo windows shown in split-screen mode in Figure 4B4) appear on the screen to overlay the background of window switcher user interface 4108. In Figure 4B4, after the input by contact 4104 ends and the animated transition is completed, window switcher user interface 4108 is displayed, replacing the email application full-screen window 4102 on the screen. In this scenario, the window switcher user interface 4108 displays representations of all saved windows associated with the email application, including representations of all full-screen windows (e.g., representation 4102' of full-screen window 4102), all slide-over windows (e.g., representation 4106' of slide-over window 4106), and all windows displayed in split-screen mode (e.g., representation 4102' of an email window displayed with a photo window in split-screen mode), overlaid on a background (e.g., a blurred or darkened image of full-screen window 4102).Each representation in the window switcher user interface 4108, when activated by an input (e.g., a tap input) that meets the selection criteria, causes the device to stop displaying the window switcher user interface, display the window corresponding to the selected representation, and perform the task of either returning to the previously displayed window (e.g., if a representation of the originally displayed window was selected), or switching to a different window of the same application (e.g., if a representation of a window other than the originally displayed window was selected).

[0195] 4B4, a close affordance 4114 is provided within the window switcher user interface 4108. When activated by input (e.g., a tap input) that meets the selection criteria, the close affordance causes the device to stop displaying the window switcher user interface 4108 and redisplay the full-screen window 4102. A new window affordance 4112 is also provided within the window switcher user interface 4108. When activated by input (e.g., a tap input) that meets the selection criteria, the new window affordance 4112 causes the device to stop displaying the window switcher user interface 4108 and display a new window of the email application (e.g., a default window (e.g., an email inbox user interface, a draft email user interface, a new message user interface, etc.)).

[0196] In Figure 4B4, input by contact 4118 is detected on representation 4102' of originally displayed full-screen window 4102. In response to detecting input by contact 4118 and in accordance with a determination that the input meets a first criterion (e.g., the input is a tap input), the device stops displaying window switcher user interface 4108 and displays full-screen window 4102, as shown in Figure 4B5.

[0197] FIG. 4B5 illustrates that while full-screen window 4102 of an email application is displayed, input by contact 4120 is detected on application icon 224 for a messages application. In response to a determination that the input by contact 4120 meets a first criterion (e.g., the input is a tap input), the device determines whether application icon 224 and currently displayed window 4102 correspond to the same application. In response to a determination that application icon 224 and currently displayed window 4102 do not correspond to the same application, the device stops displaying full-screen window 4102 and displays full-screen window 4122 corresponding to the messages application (e.g., a default window of the messages application (e.g., the last-displayed full-screen window of the messages application)), as shown in FIG. 4B6. In the exemplary scenario illustrated in FIGS. 4B5-4B6, the user's request to switch applications is fulfilled regardless of whether the messages application is currently associated with multiple windows or whether the email application is currently associated with multiple windows because the user selected an application icon for a different application than the currently displayed application.

[0198] 4B7-4B8 illustrate a scenario that contrasts with the scenarios illustrated in FIGS. 4B1-4B4. In the exemplary scenario illustrated in FIGS. 4B7-4B8, a full-screen window 4122 of a message application is displayed on touch screen 112. In some embodiments, the device has the same response, described below, regardless of whether full-screen window 4102 is displayed in a standalone configuration or in slide-over mode as a background window of a slide-over window (e.g., of the same or a different application). In FIG. 4B7, an input by contact 4124 is detected on the screen at a location corresponding to application icon 224 for the message application in dock 4006 overlaid on full-screen window 4122 of message window 4122. In response to detecting the input and following a determination that the input meets the selection criteria, the device determines whether the selected application icon corresponds to the application of the currently displayed window. In this scenario, both the currently displayed window (e.g., window 4122) and the selected application icon (e.g., application icon 224) correspond to the message application. In response to determining that the currently displayed window (e.g., window 4122) and the activated application (e.g., application icon 224) both correspond to a messaging application, the device determines whether the application is associated with multiple windows (e.g., whether multiple open windows are stored in memory as "open" windows that can be redisplayed on the screen in their saved last display state).In this scenario, pursuant to a determination that the messages application does not currently have more than one open window, the device provides one or more outputs (e.g., corresponding to visual, auditory, and / or haptic feedback) to indicate that neither an application switching operation nor a window switcher display operation will be initiated in response to input by contacts 4124. In Figure 4B8, application icon 224 vibrates in response to input by contacts 4124, optionally in conjunction with an auditory or haptic alert, to indicate that the currently displayed window and the selected application icon correspond to the same application, that the application is not associated with multiple windows, and that neither an application switching nor a window switcher display operation will be performed.

[0199] Figures 4B9-4B13, which follow Figure 4B8, illustrate a process in which additional windows are opened in the Messages application such that at the end of the process there are two or more windows associated with the Messages application. There are other ways to open additional windows in the Messages application, and the process illustrated in Figures 4B9-4B13 is just one of many ways for opening additional windows in an application.

[0200] As shown in FIG. 4B9, contact 4128 input is detected at a location on full-screen window 4122 that corresponds to representation 4130 of a conversation with Greg Kane. In response to detecting contact 4128 input and following a determination that an initial portion of the input meets object movement criteria (e.g., time or intensity criteria for detecting a tap-and-hold input or a light press input to initiate a drag action on an object (e.g., a document, a user interface object, a content item, etc.)), the device displays representation 4130 in a highlighted state. In FIGS. 4B10-4B11, following movement of contact 4128 detected after the object movement criteria are met by the initial portion of contact 4128 input, another representation 4132 of a conversation with Greg Kane (e.g., a copy of representation 4130) is dragged across the display. In FIG. 4B12, when representation 4132 is dragged into predefined region 4308 near the right edge of the display to open content in the application's slide-over window (e.g., as also shown in FIG. 4C28, predefined region 4308 is a reduced-width version of predefined region 4014 of FIG. 4A6, zone F in FIG. 4E8), the device provides visual feedback (e.g., full-screen window 4122 is reduced in size and converted to a reduced-scale representation 4122′ of window 4122, the background beneath reduced-scale representation 4122′ is revealed, representation 4132 is elongated and expanded horizontally, etc.) to indicate that if typing were to finish at this point, the slide-over window of the messages application would be displayed overlaying full-screen window 4122 on the right side of the screen. In some embodiments, the visual feedback also includes visually obscuring the resized full-screen window and displaying an application icon corresponding to the full-screen window on the visually obscured window. In some embodiments, an application icon for the messages application is displayed on representation 4132.4B13, slide-over window 4136 of the messages application is opened and displayed on the right side of the display so as to overlay a portion of full-screen window 4122 of the messages application. A conversation with Greg Kane is displayed inside slide-over window 4136. In other words, a content object (e.g., a conversation with Greg Kane) that was dragged to the right side of the screen (e.g., into default area 4308 for opening content in a slide-over window) is opened in a slide-over window (e.g., a slide-over message window) of the application corresponding to the content object. After completion of input by contact 4128, there are two or more windows associated with the messages application, including full-screen window 4122 and slide-over window 4136.

[0201] In FIGS. 4B14-4B17, which follow FIG. 4B13, another input by contact 4138 is detected on application icon 228 in dock 4006, which causes a slide over window to open in the photos application. There are many ways to open a new window in an application, and the process illustrated in FIGS. 4B14-4B17 is just one of many ways to open a new window. In this example, the new window is the first window opened in the photos application. As shown in FIG. 4B14, while full screen window 4122 and slide over window 4136 of the messages application are displayed in slide over mode, input by contact 4138 is detected at a location on the display corresponding to application icon 228 of the photos application. In FIGS. 4B15-4B16, after an initial portion of the input satisfies the object movement criteria for initiating a drag action on the application icon, a representation 4140 of the photos application is dragged across the display in accordance with the movement of contact 4138 detected after the object movement criteria are satisfied by this initial portion. In Figure 4B16, when contact 4138 drags representation 4140 of the photos application into default region 4014 to open a slide-over window on the right side of the display (e.g., region 4014 for opening a slide-over application window by dropping the application icon is wider than region 4308 of Figure 4B12 used to open content in a new slide-over window), representation 4140 elongates and expands horizontally to indicate reaching the drop zone for opening the slide-over window of the dragged application. In Figure 4B17, after input ends within default region 4014 (e.g., after contact 4138 lifts off within default region 4014), slide-over window 4142 of the photos application appears as the topmost slide-over window overlaying full-screen window 4122.

[0202] 4B18-4B19 show a scenario similar to that shown in FIGS. 4B1-4B4, and in contrast to the scenarios shown in FIGS. 4B5-4B6 and 4B7-4B8.

[0203] In the exemplary scenario shown in FIGS. 4B18-4B19, full-screen window 4122 of a messages application is displayed on touch screen 112 along with slide-over window 4142 of a photos application. In some embodiments, the device has the same response, described below, regardless of whether full-screen window 4122 is displayed in a standalone display configuration or as a background window of a slide-over window (e.g., of the same or a different application) in slide-over mode. In FIG. 4B18, input by contact 4144 is detected at a location on the screen corresponding to application icon 224 for the messages application in dock 4006 overlaid on full-screen window 4122. In response to detecting the input and following a determination that the input meets a first criterion, the device determines whether the selected icon corresponds to the application of the currently displayed window. In this scenario, the currently displayed window (e.g., window 4122) and the selected application icon (e.g., application icon 224) both correspond to the messages application. In response to determining that the currently displayed window (e.g., window 4122) and the activated application icon (e.g., application icon 224) both correspond to the messages application, the device determines whether the messages application is associated with multiple windows (e.g., whether multiple open windows are saved in memory as "open" windows that can be redisplayed on the screen in their saved last-display states). In this scenario, following a determination that the messages application currently has more than one open window (e.g., because window 4136 is also open in FIG. 4B15), the device displays window switcher user interface 4018, which simultaneously displays representations of the multiple open windows associated with the messages application.This contrasts with a scenario in which an application icon for a messaging application is activated by input that meets the selection criteria, but the messaging application is not the currently displayed application, and an application switch operation is immediately performed in response to the input (e.g., as shown in Figures 4B5-4B6). This also contrasts with a scenario in which the application corresponding to the activated application icon is the currently displayed application, but only a single window is open, and neither application switching nor display of the window switcher occurs (e.g., as shown in Figures 4B7-4B8).

[0204] 4B19, after input via contact 4144 is terminated, window switcher user interface 4108 is displayed, replacing full-screen window 4122 of the messages application and slide-over window 4142 of the photos application. In this scenario, window switcher user interface 4108 displays representations of all saved windows associated with the messages application overlaid on a background (e.g., a blurred or darkened image of full-screen window 4122), including representations of all full-screen windows (e.g., representation 4122′ of full-screen window 4122), all slide-over windows (e.g., representation 4136′ of slide-over window 4136), and representations of all windows displayed in split-screen mode (e.g., not present at this time). Each representation in the window switcher user interface 4108, when activated by input (e.g., a tap input) that meets the selection criteria, causes the device to stop displaying the window switcher user interface, display the window corresponding to the selected representation, and perform the tasks of returning to the previously displayed window (or, optionally, a simultaneously displayed window), or switching to a different window of the same application (e.g., window 4136′). The window switcher user interface 4108 displays the same new window affordance 4112 and close affordance 4114. The new window affordance 4112, when activated, causes the device to open a new window of the Messages application. The close affordance 4114, when activated, causes the device to stop displaying the window switcher user interface 4108 and redisplay the fullscreen window 4122 and slide-over window 4142. In some embodiments, each application has its own copy of the window switcher user interface, with customizations (e.g., user interface objects, functionality, and appearance) configured within the application.In some embodiments, the window switcher user interface is a system user interface that is displayed in a different state corresponding to each application from which the window switcher user interface is invoked.

[0205] 4B20-4B21 illustrate interaction with new window affordance 4112 within window switcher user interface 4108. In FIG. 4B20, input by contact 4146 is detected at a location corresponding to new window affordance 4112. In response to the input, and following a determination that the input meets the selection criteria (e.g., the input is a tap input), the device displays a new window of a messages application. In embodiments, the new window is the default window of the messages application (e.g., window 4148 displaying a set of existing conversations and a new message template for composing a new message with a new recipient).

[0206] 4B22-4B23 illustrate navigating to another user interface within full-screen window 4148 without opening a new window. In FIG. 4B22, input by contact 4152 is detected at a location corresponding to representation 4150 of a conversation with Mary Ford. In response to the input and in accordance with a determination that the input meets a first criterion (e.g., the input is a tap input), the user interface within window 4148 is transformed, and the new message template within the window is replaced with a conversation with Mary Ford, as shown in FIG. 4B23. For purposes of further clarity, window 4148 is relabeled as window 4154 to indicate that the window content has changed, but a new window is not opened in the Messages application. Alternatively, a navigation action within the Messages application closes window 4148 and opens window 4154 within the Messages application.

[0207] 4B24-4B27 illustrate a process of opening a window in a photos application in split-screen mode and simultaneously converting a full-screen window in a messages application to a split-screen window, according to some embodiments, where the window in the photos application is a newly opened window, but the window in the messages application is a resized existing window rather than a newly opened window.

[0208] As shown in FIG. 4B24, while displaying a full-screen window 4154 of a messaging application, an input by contact 4156 is detected at a location corresponding to an application icon 228 of a photo application. In response to detecting the input and in accordance with a determination that an initial portion of the input satisfies a second criterion (e.g., a criterion for initiating a drag operation on an object at the location of the input), the device highlights the application icon 228 to indicate that the criterion for initiating a drag operation has been met. In FIG. 4B25, a representation 4158 of the photo application is dragged in accordance with the movement of contact 4156, which was detected after the second criterion was met by the initial portion of the input. In FIG. 4B26, the representation 4158 of the photo application is dragged to a predetermined region 4162 near the left edge of the display (e.g., also referred to as zone A in FIG. 4E8) to open the window in split-screen mode. In some embodiments, the distance between the predetermined region 4162 for opening a window in split-screen mode and the left edge of the display is shorter than the distance between the predetermined region 4014 (e.g., for opening a window in slide-over mode) and the right edge of the display. In response to determining that contact 4156 is within predefined area 4162 for opening application windows in split-screen mode, the device provides visual feedback to indicate that if input were to end at this point, the window of the dragged application would be opened in split-screen mode. In some embodiments, the visual feedback includes, for example, resizing full-screen window 4154 horizontally to obscure the background on the side of the display on which the new window appears. In some embodiments, when full-screen window 4154 is resized, the contents of the full-screen window are visually obscured (e.g., blurred or darkened), and an application icon for the corresponding application is displayed on the visually obscured window.In some embodiments, the visual feedback includes, for example, stretching representation 4158 of the application and reducing the horizontal width of representation 4158 so that representation 4158 does not overlap reduced-width representation 4154' of window 4154 of the messages application. In FIG. 4B27, after the end of input by contact 4156 is detected, a new window 4166 of the photos application is opened on the left side of the display in split-screen mode. In addition, full-screen window 4154 of the messages application is resized and displayed simultaneously with new window 4166 of the photos application in split-screen mode. For purposes of clarity, window 4154 is relabeled as 4164 to indicate that it has been resized and converted from a full-screen window to a split-screen window, but no new window is opened in the messages application. In some embodiments, the above-described window resize operation in the messages application is achieved by closing full-screen window 4154 and opening split-screen window 4164 in the messages application. Window 4166 and window 4164 are associated (e.g., pinned) as a pair of split-screen windows and are represented together by a single representation in the application switcher user interface (e.g., application switcher user interface 4032). Additionally, in some embodiments, each window of the pair of split-screen windows also counts as an open window of the respective corresponding application in the window switcher user interface corresponding to the respective application. In some embodiments, the pair of split-screen windows are represented in the window switcher user interface by a single representation. In some embodiments, when a single representation of the pair of split-screen windows is selected (e.g., by a tap input), the pair of split-screen windows reappears together on the display from the application switcher user interface and / or the window switcher user interface.

[0209] 4B28-4B31 illustrate window switching operations using a window switcher user interface, according to some embodiments. As shown in FIG. 4B28, window 4166 of a photo application and window 4164 of a message application are displayed side-by-side in split-screen mode. Input by contact 4168 is detected on application icon 224 corresponding to the message application. In accordance with a determination that the input meets selection criteria (e.g., the input is a tap input), in accordance with a determination that one of the currently displayed windows (e.g., window 4166 and window 4164) and the activated application icon correspond to the same application (e.g., window 4164 and application icon 224 both correspond to the message application), and in accordance with a determination that the application of the activated application icon (e.g., the message application) is associated with multiple windows, the device displays window switcher user interface 4108 in a state corresponding to the message application (e.g., displaying representations of the multiple windows now associated with the message application), as shown in FIG. In Figure 4B29, representation 4122' is displayed for full-screen window 4122, representation 4136' is displayed for slide-over window 4136, and representation 4168' is displayed for split-screen window 4164 (e.g., for a photos application, the same representation is used for split-screen window 4166 in the window switcher user interface). In Figure 4B30, input by contact 4170 is detected on representation 4122' in window switcher user interface 4108 of a messages application.In response to the input, and pursuant to a determination that the input meets the selection criteria (e.g., the input is a tap input), the device stops displaying the window switcher user interface 4108 of the messages application and re-displays the full-screen window 4122 of the messages application on the screen in a standalone display configuration, as shown in Figure 4B31. At this point, the window switching operation from split-screen window 4164 to full-screen window 4122 shown in Figure 4B28 is accomplished via the window switcher user interface 4108.

[0210] 4B32-4B33 illustrate a scenario similar to that shown in FIGS. 4B5-4B6 in which, in some embodiments, an application switch operation from a first application to a second application is performed in response to selection of an application icon for the second application, regardless of how many windows are associated with the second application.

[0211] FIG. 4B32 illustrates that while full-screen window 4122 of a messages application is displayed, input by contact 4172 is detected on application icon 218 for an email application. Following a determination that input by contact 4172 meets the selection criteria (e.g., the input is a tap input), the device determines whether application icon 218 and currently displayed window 4122 correspond to the same application. Following a determination that application icon 218 and currently displayed window 4122 do not correspond to the same application, the device stops displaying full-screen window 4122 and displays full-screen window 4102 corresponding to the email application (e.g., a default window of the email application (e.g., the last-displayed full-screen window of the email application)), as shown in FIG. 4B33. In the exemplary scenario illustrated in FIGS. 4B32-4B33, the user's request to switch applications is satisfied regardless of whether the email application is currently associated with multiple windows or whether the messages application is currently associated with multiple windows because the user activated an application icon for a different application than the currently displayed application.

[0212] Figures 4B34-4B35, following Figure 4B33, illustrate an exemplary scenario similar to that shown in Figures 4B1-4B5 in which an application switcher user interface is displayed in response to activation of the application icon of a currently displayed application via a tap input. In Figure 4B34, while window 4102 of an email application is displayed on the screen, an input via contact 4174 is detected on application icon 218 for the email application. Following a determination that the input meets selection criteria (e.g., the input is a tap input), following a determination that the activated application icon and the currently displayed window correspond to the same application, and following a determination that the application has two or more windows, the device displays window switcher user interface 4108 for that application (e.g., an email application), as shown in Figure 4B35. In Figure 4B35, all windows currently associated with the email application are displayed within window switcher user interface 4108. Each representation of a window is displayed with a unique name for the window that is automatically generated based on the application icon and the window's content to distinguish between windows with similar or identical content.

[0213] 4B32-4B35 illustrate that a double tap (e.g., two consecutive inputs that both meet the selection criteria and are optionally separated by less than a threshold time) causes the device to perform the operation of switching from a display of a first application to a display of a second application and displaying a window switcher user interface for the second application. In some embodiments, an intermediate state displaying the second application is not displayed, and the device proceeds directly from a display of the first application to a display of the window switcher user interface for the second application in response to the double tap input, and then proceeds from a display of the window switcher user interface for the second application to a display of the window of the second application in response to an input that selects a window from this or an existing window switcher user interface (e.g., by tapping outside the representation of the window, by selecting the close or new window affordance).

[0214] 4B36-4B37 illustrate an exemplary process in which an input by contact 4176 is detected on an application icon 228 in a dock 4006 overlaid on a window switcher user interface 4108. In some embodiments, the dock 4006 is initially hidden when the window switcher user interface 4108 is displayed and is redisplayed on the screen by an input that meets the dock display criteria (e.g., the input is an upward swipe gesture starting from the bottom edge of the touchscreen). In response to detecting the input and following a determination that the input meets the selection criteria (e.g., the input is a tap input), the device ceases displaying the window switcher user interface 4108 and displays a window 4178 of the application (e.g., a photo application) that corresponds to the activated application icon 228, as shown in FIG.

[0215] 4B38-4B42 show an exemplary process for switching from a first window (e.g., a full-screen window (e.g., window 4178)) to a second window (e.g., a slide-over window (e.g., window 4142)) of an application (e.g., a photo application) using the application's window switcher user interface 4108, in some embodiments.

[0216] As shown in FIG. 4B38, while full-screen window 4178 of the photos application is displayed, input by contact 4180 is detected on application icon 228 of the photos application. In response to input by contact 4180, the device displays window switcher user interface 4108 in a state corresponding to the photos application, including representations of multiple windows currently associated with the photos application (e.g., representation 4168' for full-screen window 4168, representation 4142' for slide-over window 4142, and representation 4178' for full-screen window 4178). In FIG. 4B40, input by contact 4182 is detected on representation 4142' for slide-over window 4142. In response to detecting the input and following a determination that the input meets the selection criteria (e.g., the input is a tap input), the device stops displaying window switcher user interface 4108 and displays slide-over window 4142, as shown in FIG. 4B41 or 4B42. In Figure 4B41, in some embodiments, slide-over window 4142 is displayed simultaneously with the same background window (e.g., a full-screen window, or a pair of split-screen windows) that was last previously displayed with slide-over window 4142 (e.g., in Figure 4B18, window 4122 was last displayed with slide-over window 4142). In Figure 4B42, in some embodiments, slide-over window 4142 is displayed simultaneously with a full-screen window (e.g., a full-screen window or a pair of split-screen windows) that was last displayed immediately before the display of window switcher user interface 4108 (e.g., window 4178 was the last full-screen window displayed immediately before the display of window switcher user interface 4108).

[0217] 4B43-4B43 illustrate another exemplary process for invoking an application's window switcher user interface 4108, according to some embodiments. While the example shown in Figures 4B43-4B43 illustrates invoking the photo application's window switcher user interface 4108 due to an input detected while the photo application is displayed, this exemplary process functions to invoke an application's window switcher user interface 4108 regardless of whether the application is the currently displayed application (e.g., another application or system user interface may be displayed when the input is first detected).

[0218] As shown in FIG. 4B43, while displaying an application (e.g., a photos application or another application different from the photos application) and dock 6004, an input by contact 4183 is detected on an application icon in the dock (e.g., application icon 228 of the photos application). In response to detecting the input and in accordance with a determination that the input meets the menu display criteria (e.g., the input is a tap-and-hold input or a light press input), the application icon 228 is highlighted to indicate that the menu criteria have been met by the input. In FIG. 4B44, in response to detecting an end of the input (e.g., in response to detecting lift-off of contact 4183), a menu 4182 of selectable options 4184 for window management of the application corresponding to the selected application icon (e.g., the photos application) is displayed. As shown in FIG. 4B44, the selectable options include a first option for displaying all windows associated with the photos application in a window switcher user interface, a second option for opening a new window (e.g., a new default window) in the photos application, and a third option for closing all windows associated with the photos application. In Figure 4B45, input by contact 4186 is detected on a first selectable option to display all windows. In response to detecting the input and following a determination that the input meets the selection criteria (e.g., the input is a tap input), the device displays a window switcher user interface 4108 including representations of all windows associated with the photos application, as shown in Figure 4B46.

[0219] 4B4, 4B19, 4B29, 4B35, and 4B40, a new window affordance 4112 is displayed that, when activated (e.g., by a tap input), initiates the process of opening a new window for the application corresponding to the currently displayed window switcher user interface. In some embodiments, the newly opened window is the default new window for the application. In some embodiments, a second version of the window switcher user interface 4108 is displayed with two different new window affordances, one for opening a new document in a new window and the other for opening an existing document in a new window. In some embodiments, the device selects which version of the window switcher user interface 4108 depending on whether the corresponding application of the window switcher user interface is a document editor application (e.g., a word processing application, a spreadsheet application, a presentation editor application, a drawing application, a PDF document creation application, a content publishing application, etc.) or is not a document creation application (e.g., a browser application, an email application, an instant messaging application, a photo application, etc.). 4B47-4B50 show two different versions of the new window affordance in the second version of the window switcher user interface 4108, according to some embodiments.

[0220] As shown in FIG. 4B47, a full-screen window 4188 of the notes application is displayed. The notes application functions as a document editor application because a user frequently creates and edits documents and can reopen previously created and edited documents for further editing. As shown in FIG. 4B47, while the notes application window 4188 is displayed, an input by contact 4190 is detected on the application icon 244 of the notes application in the dock 6004. In response to detecting the input and following a determination that the input meets selection criteria, the device displays a window switcher user interface 4108 corresponding to the notes application, as shown in FIG. 4B48. In FIG. 4B48, the version of the window switcher user interface 4108 displayed for the notes application includes representations of windows associated with the notes application (e.g., representation 4188' of full-screen window 4188 and representation 4192' of the slide-over window of the notes application). In addition to representing an open window of the notes application, the window switcher user interface also includes an "Open" affordance 4194 for opening an existing document in a new window of the notes application, and a "New" affordance 4196 for opening a new document in a new window of the notes application. Input by contact 4198 and input by contact 4200 are shown on the window switcher user interface 4108 shown in FIG. 4B48.

[0221] 4B49, in response to detecting input by contact 4200 on “new” affordance 4196 and following a determination that the input meets a first criterion (e.g., the input is a tap input), the device stops displaying a window switcher user interface and displays a new window 4202 displaying a new note document (e.g., a new document created based on a default note template in a notes application, opened for editing with a keyboard overlaying the document). In some embodiments, instead of opening a new document directly based on the default new document template, the device displays a document creation user interface including selectable options corresponding to different new document formats and / or different new document templates. When the user selects each new document format and / or new document template, the device creates a new document according to the selected document format and / or document template and opens it in a new window in the application.

[0222] In FIG. 4B50 , in response to detecting input by contact 4198 on “open” affordance 4194 and following a determination that the input meets a first criterion (e.g., the input is a tap input), the device stops displaying window switcher user interface 4108 and displays a new window 4204 in a document picker user interface for a notes application. In some embodiments, the document picker user interface includes selectable options corresponding to different existing folders and documents that can be opened within the application (e.g., the notes application). For example, as shown in FIG. 4B50 , a series of existing notes are displayed within the document picker user interface of the notes application. When a user selects each of the existing notes, the device opens the selected document (e.g., a previously created selected note) in a new window of the application (e.g., the notes application). In some embodiments, the application is a document management application and is configured to open documents corresponding to different applications. In such a scenario, the document picker of the document management application optionally displays representations of documents corresponding to different applications within its document picker user interface and, in response to the user's selection input, opens the selected document by invoking the different application corresponding to the selected document.

[0223] FIG. 4B51 illustrates a home screen user interface 4205 that includes multiple application icons corresponding to different applications installed on the device. In response to an input that meets menu display criteria (e.g., a tap-and-hold input or a light press input followed by a contact lift-off, a long touch-and-hold input without a contact lift-off, or a deep press input without a contact lift-off), a quick action menu 4206 is displayed. The quick action menu 4206 displays selectable options corresponding to actions within the application (e.g., view recent photos, view favorites folder, search for photos, etc.) simultaneously with the selectable options shown in menu 4182 (FIG. 4B44), including a first option for displaying all windows associated with the Photos application in a window switcher user interface, a second option for opening a new window (e.g., a new default window) within the Photos application, and a third option for closing all windows associated with the Photos application.

[0224] 4C1-4C48 show a process for dragging and dropping an object (e.g., a user interface object representing a content item or an application icon) at different positions (e.g., side regions) on a display according to some embodiments. In some embodiments, dropping an object corresponding to a content item into different regions on the display optionally causes the device to perform different actions according to various position-based criteria (e.g., based on a comparison of the end position of the drag input, the position of the object at the time the drag input ended, or a predicted final position of the object based on past movement of the input relative to different predefined regions on the display). In some embodiments, the actions performed in response to dropping an object corresponding to a content item in a different region on the display include (1) displaying the content item or a representation thereof at a different location within the same window (e.g., to perform an object move or object copy operation in the same application window); (2) displaying the content item or a representation thereof at a location within a different window that is displayed simultaneously with the object's original window (e.g., to perform an object move or object copy operation between two simultaneously displayed windows (e.g., of the same application or two different applications)); (3) opening and displaying the content item in a new window in a first simultaneous display configuration with the object's original window (e.g., to display the content item in a new slide-over window of the native application corresponding to the content item so that it overlays the object's original window); (4) opening and displaying the content item in a new window in a second simultaneous display configuration with the object's original window (e.g., to resize the object's original window and display the content item in a new split-screen window of the native application corresponding to the content item in a side-by-side display with the object's resized original window); (5) opening and displaying the content item in a new window in a second simultaneous display configuration with the object's original window (e.g., to resize the object's original window and display the content item in a new split-screen window of the native application corresponding to the content item in a side-by-side display with the object's resized original window);(5) displaying the content item in a new window together with the object's original window in a third simultaneous display configuration (e.g., to display the content item in a draft window so as to overlay the center of the object's original window, optionally visually obscuring the object's original window); (6) opening and displaying the content item in a new window together with the object's original window in a fourth simultaneous display configuration (e.g., to display the content item in a minimized window that can be viewed simultaneously with the content item's original window); and / or (7) opening and displaying the content item in a new full-screen window according to the position or predicted position of the dragged object at the time of the drag input or the end of the drag input (e.g., to open the content item in a new full-screen window, replacing the object's original window on the display (and replacing any other windows simultaneously displayed on the display)). In some embodiments, the default area on a display for determining whether a new window (e.g., a slide-over window or a split-screen window) should open for an application when an application icon is dragged and dropped on the display (e.g., area 4308 and area 4310 in FIGS. 4B12 and 4C28) is smaller than the default area for determining whether a new window should open for a content item when an object representing a content item is dragged and dropped on the display (e.g., area 4014 in FIG. 4B16 and area 4162 in FIG. 4B26). For example, in some embodiments, the default area for dropping an application icon to create a slide-over window for an application is larger than the default area for dropping an object representing a content item to create a slide-over window in which to display the content item. Similarly, in some embodiments, the default area for dropping an application icon to create a split-screen window for an application is larger than the default area for dropping an object representing a content item.7A-7H and 7I. For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device having touch-sensitive display system 112. In such embodiments, the focus selector is optionally a respective finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., the face center of each contact or a point associated with each contact), or the face center of two or more contacts detected on touch-sensitive display system 112. However, similar operations, along with a focus selector, are optionally performed on a device having display 450 and separate touch-sensitive surface 451 in response to detecting contacts on touch-sensitive surface 451 while displaying the user interface shown in the figures on display 450.

[0225] 4C1-4C5 illustrate a process for opening a content item in a slide-over window via a drag-and-drop operation, according to some embodiments. In FIGS. 4C1-4C5, an object representing a content item is dragged from a first window displayed on the display and dropped into a first predefined area near a side edge of the display (e.g., predefined area 4308 shown in FIG. 4C3), resulting in the content item being opened in a new slide-over window of the application corresponding to the content item. This first predefined area for dropping the content item is smaller in size (e.g., narrower in width and / or closer in distance from the corresponding side edge of the display) than the predefined area used for dropping an application icon and opening the slide-over window of the application corresponding to the application icon (e.g., predefined area 4014 shown in FIGS. 4A5-4B16). This makes more area available for performing actions on the content item in the first window and, optionally, in a second window displayed simultaneously with the first window.

[0226] 4C1 , full-screen window 4122 of a messaging application is displayed (e.g., in a standalone configuration). Input by contact 4302 is detected at a location corresponding to object 4304 representing a first content item (e.g., a conversation with Greg Kane). An initial portion of the input by contact 4302 meets the object movement criteria for initiating a drag operation on object 4304 or a copy of object 4304 representing the first content item (e.g., the initial portion of the input by contact 4302 meets the touch hold time threshold or the light pressure input intensity threshold), and the device highlights object 4304 to indicate that the criteria for initiating a drag operation on the object have been met.

[0227] 4C2, representation 4306 of the first content item (e.g., a copy of object 4304) is dragged across the display according to the movement of contact 4302 detected after the second criterion is met. In some embodiments, representation 4306 has a first appearance that indicates that no allowable drop locations are available for the object in the portion of window 4122 that is outside first predefined region 4308, and that no object move or object copy operation will be performed with respect to the first content item in window 4122 if input terminates at this point.

[0228] 4C3 , following movement of contact 4302 after the object movement criteria have been met, representation 4306 of the first content item is dragged to a position within first predefined region 4308. In some embodiments, representation 4306 takes on a second appearance (e.g., the representation is elongated and horizontally expanded) indicating that if input were to end at this point, the first content item would be displayed in a new slide-over window in the application corresponding to the first content item (e.g., a messaging application). In FIG. 4C4 , in some embodiments, in addition to changing the appearance of representation 4306 of the first content item, as the representation is dragged to a position within first predefined region 4308, the device provides further visual feedback to indicate that the input and / or the current position of representation 4306 meets the position criteria for opening the first content item in a slide-over window. In some embodiments, the further visual feedback includes reducing the overall size of the first window 4122 to display a representation 4122' of the first window 4122 and clarifying the background 4134 below the representation 4122'.

[0229] In FIG. 4C5, upon detecting the end of input by contact 4302 (e.g., detecting lift-off of contact 4302), the first content item is displayed in a new slide-over window 4136 of the message application so as to overlay the first window 4122.

[0230] 4C4, Figures 4C6-4C7 illustrate that the input by contact 4302 is continuously evaluated for satisfying position criteria corresponding to different predefined regions on the display for different actions to be performed after the input terminates (e.g., moving the object in the same window, moving the object to a different window, opening the content in a new slide-over window, opening the content in a new split-screen window, etc.), and that the visual feedback is dynamically updated to indicate the corresponding expected outcome if the input terminates at the current location. In Figures 4C6-4C7, before the end of the input by contact 4302 is detected, movement of contact 4302 drags representation 4306 of the first content object from first predefined region 4308 to a position in the center of the display outside first predefined region 4308, and as a result, the visual feedback is dynamically updated to indicate that the position criteria for opening the first content item in a slide-over window are no longer satisfied and that neither the object move nor the object copy action will be performed if the input terminates at this point (e.g., the point shown in Figure 4C7).

[0231] 4C8-4C11 illustrate a process for opening a content item in a split-screen window via a drag-and-drop operation, according to some embodiments. In FIGS. 4C8-4C11, an object representing the content item is dragged from a first window displayed on the display and dropped into a second predefined area near a side edge of the display (e.g., predefined area 4310 shown in FIG. 4C10), resulting in the content item being opened in a new split-screen window of the application corresponding to the content item. This second predefined area 4310 for dropping the content item is smaller in size (e.g., narrower in width and / or closer in distance from the corresponding side edge of the display) than the predefined area used for dropping an application icon and opening the split-screen window of the application corresponding to the application icon (e.g., predefined area 4162, such as in FIG. 4B26). The second predefined area and the first predefined area on the same side of the display are optionally adjacent to each other and share a common boundary between them. For example, the second predetermined region is defined by a side edge of the display and a first boundary line that is a first distance from the side edge of the display, and the first predetermined region is defined by the first boundary line and a second boundary line that is a second distance (greater than the first distance) from the side edge of the display. In some embodiments, a third predetermined region outside the first predetermined region (and the second predetermined region) is used to determine whether to perform an action on the first content item in the first window rather than opening a new window for the first content item.

[0232] As shown in FIG. 4C8, full-screen window 4122 of a messaging application is displayed (e.g., in a standalone configuration). Contact 4312 input is detected at a location corresponding to object 4304 representing a first content item (e.g., a conversation with Greg Kane). An initial portion of contact 4312 input meets the object movement criteria for initiating a drag operation on object 4304 or a copy of object 4304 representing the first content item (e.g., the initial portion of contact 4312 input meets the touch hold time threshold or the light pressure input intensity threshold), and the device highlights object 4304 to indicate that the criteria for initiating a drag operation on the object have been met. In some embodiments, contact 4312 may be the same as contact 4302, and the contact input can trigger different actions (e.g., actions described in FIGS. 4C1-4C7 or actions described in FIGS. 4C8-4C15) depending on the location of the input at its final termination. In some embodiments, contact 4312 and contact 4302 are different contacts corresponding to two different inputs detected at different times on the same window displaying the same user interface state.

[0233] 4C9, representation 4306 of the first content item (e.g., a copy of object 4304) is dragged across the display according to the movement of contact 4312 detected after the second criterion is met. In some embodiments, representation 4306 has a first appearance that indicates that no allowable drop locations are available for the object in the portion of window 4122 that is outside first predefined area 4308 (and second predefined area 4310), and that no object move or object copy operation will be performed with respect to the first content item in window 4122 if input terminates at this point.

[0234] 4C10, following movement of contact 4312 after the second criterion is met, representation 4306 of the first content item is dragged to a position within second predefined region 4310. In some embodiments, representation 4306 takes on a third appearance (e.g., the representation becomes more elongated and horizontally shortened) indicating that if input were to terminate at this point, the first content item would be displayed in a new split-screen window of the application corresponding to the first content item (e.g., a messages application), with the split-screen window of the messages application converted from full-screen window 4122. In FIG. 4C10, in some embodiments, in addition to changing the appearance of representation 4306 of the first content item, as the representation is dragged to a position within second predefined region 4310, the device provides further visual feedback to indicate that the input and / or the current position of representation 4306 meets the position criteria for opening the first content item in a split-screen window. In some embodiments, the further visual feedback includes reducing the width of the first window 4122 to display a representation 4122' of the first window 4122 and clarifying the background 4134 below the representation 4122' on the side on which the display representation 4306 is currently displayed.

[0235] In FIG. 4C11, upon detecting the end of input by contact 4312 (e.g., detecting lift-off of contact 4312), the first content item is displayed in a new split-screen window 4316 of the messages application, side-by-side with another split-screen window 4314 converted from first window 4122.

[0236] In Figure 4C12, while a pair of split-screen windows 4314 and 4316 are displayed, an input by contact 4320 is detected on close affordance 4318 of split-screen window 4316. In response to detecting the input by contact 4320 and following a determination that the input meets the selection criteria (e.g., the input is a tap input), split-screen window 4316 is closed and split-screen window 4314 is returned to standalone full-screen window 4122, as shown in Figure 4C13.

[0237] 4C10, Figures 4C14-4C15 illustrate that the input by contact 4312 is continuously evaluated for satisfying position criteria corresponding to different predefined regions on the display for different actions to be performed after the input terminates (e.g., moving the object in the same window, moving the object to a different window, opening the content in a new slide-over window, opening the content in a new split-screen window, etc.), and that the visual feedback is dynamically updated to indicate the corresponding expected outcome if the input terminates at the current location. In Figures 4C14-4C15, before the end of the input by contact 4312 is detected, the movement of contact 4312 drags representation 4306 of the first content object from second predefined region 4310 to a position in the center of the display outside first predefined region 4308, and as a result, the visual feedback is dynamically updated to indicate that the position criteria for opening the first content item in a split-screen window are no longer satisfied and that neither the object move nor the object copy action will be performed if the input terminates at this point (e.g., the point shown in Figure 4C15). 4C2, 4C3, 4C4, 4C6, 4C7, 4C9, 4C10, 4C14, and 4C15 may be displayed and repeated in any order and any number of times based on the current location of the contact, as long as the end of the input is not detected. Additionally, the final states of the screens shown in Figures 4C5, 4C11, and 4C13 are displayed depending on whether the final end location of the input is within first predefined region 4308, second predefined region 4310, or a third predefined region outside the first and second predefined regions (and any other predefined regions for opening new windows in various display modes (e.g., full-screen draft mode, minimized mode, slide-over windows on different sides of the display, split screen on different sides of the display, etc.)).

[0238] 4C16-4C17 illustrate input by contact 4322 at a location corresponding to object 4304 representing a first content item (e.g., a conversation from Greg Kane) in window 4122. In response to detecting input by contact 4322 and following a determination that the input meets the selection criteria (e.g., the input is a tap input), the device navigates to another user interface within the messages application without opening a new window. For clarity of explanation, the window displaying the new user interface is labeled as window 4324 as shown in FIG. 4C17. In some embodiments, an operation corresponding to user interface navigation within the application is implemented by closing the current window displaying the current user interface and opening a new window with the new user interface. In some embodiments, contact 4322 may be the same as contact 4302 and / or 4312, and the contact input may trigger different actions (e.g., actions described in Figures 4C1-4C7 and / or actions described in Figures 4C8-4C15) depending on the location of the input at the final termination of the input and the type of input (e.g., drag input or tap input). In some embodiments, contact 4322, contact 4312, and contact 4302 are different contacts corresponding to different inputs detected at different times on the same window displaying the same user interface state.

[0239] Figures 4C18-4C23 illustrate an example process similar to that shown in Figures 4C1-4C17 for a content item associated with a different application (e.g., an email application). Many of the aspects described with respect to the example shown in Figures 4C1-4C17 can be applied to the example shown in Figures 4C18-4C23.

[0240] 4C18-4C21 illustrate a process for opening another content item in a split-screen window using a drag-and-drop operation, according to some embodiments. In FIGURES 4C18-4C21, an object representing the content item is dragged from a first window displayed on the display and dropped into a second predefined area (e.g., predefined area 4310 shown in FIGURE 4C20) near a side edge (e.g., the right edge) of the display, resulting in the content item being opened in a new split-screen window of the application corresponding to the content item.

[0241] As shown in FIG. 4C18, full-screen window 4102 of an email application is displayed (e.g., in a standalone configuration). Input by contact 4328 is detected at a location corresponding to object 4326 representing a second content item (e.g., an email message from MobileFind). An initial portion of the input by contact 4328 meets the object movement criteria for initiating a drag operation on object 4326 or a copy of object 4326 representing the second content item (e.g., the initial portion of the input by contact 4328 meets the touch hold time threshold or the light pressure input intensity threshold), and the device highlights object 4326 to indicate that the criteria for initiating a drag operation on the object have been met.

[0242] 4C19, representation 4330 of the second content item (e.g., a copy of object 4326) is dragged across the display according to the movement of contact 4328 detected after the second criterion is met. In some embodiments, representation 4330 has a first appearance that indicates that no permissible drop locations are available for the object in the portion of window 4102 that is outside first predefined area 4308 (and second predefined area 4310), and that if input were to terminate at this point, no object move or object copy operation would be performed with respect to the first content item in window 4102.

[0243] 4C20, following movement of contact 4328 after the second criterion is met, representation 4330 of the second content item is dragged to a position within second predefined region 4310. In some embodiments, representation 4330 takes on a second appearance (e.g., the representation is elongated) indicating that if input were to terminate at this point, the second content item would be displayed in a new split-screen window of the application corresponding to the second content item (e.g., an email application), with the split-screen window of the email application converted from full-screen window 4102. In FIG. 4C20, in some embodiments, in addition to changing the appearance of representation 4330 of the second content item, as the representation is dragged to a position within second predefined region 4310, the device provides further visual feedback to indicate that the input and / or the current position of representation 4330 meets the position criteria for opening the second content item in a split-screen window. In some embodiments, further visual feedback includes reducing the width of the full-screen window 4102 to display a representation 4102' of the window 4102 and clarifying the background 4134 below the representation 4102' on the side of the display on which the representation 4330 is currently displayed.

[0244] In FIG. 4C21, upon detecting the end of input by contact 4330 (e.g., detecting lift-off of contact 4330), the second content item is displayed in a new split-screen window 4334 of the email application, alongside another split-screen window 4332 converted from window 4102.

[0245] 4C22 and 4C23 continue from any of FIGS. 4C18, 4C19, and 4C20 and illustrate an exemplary scenario in which a second content item is opened in a new slide-over window 4336 of an email application to overlay full-screen window 4102. As shown in FIG. 4C22, movement of contact 4328 after the object movement criteria is met causes representation 4330 of the second content item to be dragged to a position within first predefined region 4308. In some embodiments, representation 4330 takes on a third appearance (e.g., elongated and horizontally expanded, although not as thin as the representation shown in FIG. 4C20) indicating that the second content item would be displayed in a new slide-over window of the application corresponding to the second content item (e.g., the email application) if input were to end at this point. 4C22, in some embodiments, in addition to changing the appearance of representation 4330 of the second content item, as the representation is dragged to a position within first predefined area 4308, the device provides further visual feedback to indicate that the current position of input and / or representation 4330 meets the position criteria for opening the second content item in a slide-over window. In some embodiments, the further visual feedback includes reducing the overall size of window 4102 to display representation 4102′ of window 4102 and clarifying background 4134 below representation 4102′.

[0246] In FIG. 4C23, in response to detecting the end of input by contact 4328 (e.g., detecting lift-off of contact 4328), the second content item is displayed in a new slide-over window 4336 of the email application so as to overlay window 4102.

[0247] 4C23-4C24 illustrate that input by contact 4338 is detected on affordance 4340 to create a new draft email in an email application. In response to detecting input by contact 4338 and following a determination that the input meets the selection criteria (e.g., the input is a tap input), the device opens a new draft window containing the new draft email (such as a new reply email to the email displayed in slide-over window 4336 (e.g., because affordance 4340 is part of slide-over window 4336)), as shown in FIG. 4C24. In some embodiments, new draft window 4342 may be displayed in the configuration shown in FIG. 4C24 by other user interaction processes (e.g., opening an existing draft email in a slide-over or split-screen window and displaying it in draft mode by dragging the window to the center of the display).

[0248] 4C24-4C26, input by contact 4344 is detected on drag handle 4346 of drafting window 4342, the input including movement of contact 4344 toward a side edge (e.g., the right edge) of the display. In response to detecting the input and following a determination that the current position of contact 4346 is within first predefined region 4308, representation 4348 of drafting window 4342 is displayed with an appearance (e.g., an elongated application icon that is also extended horizontally) indicating that if the input ends at the current position, drafting window 4342 will be converted into a slide-over window that overlays the original background window 4102. In some embodiments, the visual feedback also includes reducing the overall size of background window 4102 to representation 4102′ and clarifying background 4134 below representation 4102′. In FIG. 4C26, after an end of input is detected while contact 4344 and expression 4348 are within predefined region 4014 (or zone F in FIG. 4E8), draft window 4342 is transformed into slide-over window 4348 that overlays background window 4102. Slide-over window 4348 displays the draft email reply to John. Other related examples of dragging currently displayed windows and transforming windows of one display configuration into windows of another display configuration are described in more detail with respect to FIGS. 4E1-4E28, according to some embodiments.

[0249] 4C27-4C40 show various examples in which after a drag operation is initiated on a content object, the final result of the input (e.g., after the end of the input is detected) is determined based on the position of the contact or the position of the dragged object at the time the input ends.

[0250] 4C27, the display is divided into several regions, including a first predefined region 4308, a second predefined region 4310, a third predefined region 4354, a fourth predefined region within the region of window 4102 that is outside the first, second, and third predefined regions and outside the search input field 4355, and a fifth predefined region within window 4102 that corresponds to the search input field 4355. In this example, the region of window 4102 outside the search input field 4335 does not correspond to any action that may be performed on the dragged content item in response to the end of the drag input. However, in some embodiments, window 4102 includes sub-areas in which actions can be performed on the dragged content item (e.g., move the dragged item within the dragged item sub-area, copy the dragged item to a folder within the sub-area, send the dragged item to another user (e.g., by dropping the content item onto a "Send" button), delete the dragged item (e.g., by dropping the content item onto a virtual trash can within the window), print the dragged item (e.g., by dropping the content item onto a printer icon displayed within the window), etc.).

[0251] 4C27, input by contact 4350 is detected at a location corresponding to object 4352 representing a document (e.g., the image "Attachment 1"). In response to detecting the first portion of the input that satisfies the object movement criteria (e.g., a tap-and-hold input or a light press input without contact liftoff), the device displays visual feedback (e.g., highlighting object 4352) indicating that the first portion of the input satisfies the criteria for initiating a drag action relative to the document.

[0252] 4C28, a first movement of contact 4350 is detected after the object movement criteria are satisfied by the first portion of the input, and representation 4356 of the document is dragged across the display in accordance with the movement of contact 4350. When contact 4356 is over a portion of window 4102 that is outside first predefined region 4308, second predefined region 4310, and third predefined region 4354, the appearance of representation 4356 indicates that no acceptable drop location is available at this location and that no action will be taken on the document if the input ends at the current location. In some embodiments, if an acceptable drop location is available at the current location, the device provides visual feedback to indicate the action to be taken on the document if the input ends at the current location (e.g., changes the appearance of representation 4356 to indicate a particular action to be taken if the end of the input is detected at this location).

[0253] 4C29, a second movement of contact 4350 is detected after the second criterion is met by the first portion of the input, and representation 4356 of the document is dragged across the display following the movement of contact 4350 into search input field 4355. The appearance of representation 4356 changes (e.g., from an icon to a filename) to indicate that an acceptable drop position is available at this location and that a search will be performed based on the document's filename if the input ends at the current location.

[0254] 4C30, a third movement of contact 4350 is detected after the second criterion is met by the first portion of the input, and representation 4356 of the document is dragged across the display following the movement of contact 4350 to third predefined area 4354 in slide-over window 4348. The appearance of representation 4356 changes (e.g., is reduced in size, and a preview of the document (e.g., image 4358) is displayed in slide-over window 4348) to indicate that an acceptable drop location is available at this location and that the contents of the document will be inserted into the draft email if input ends at the current location.

[0255] In Figure 4C31, the end of input is detected while contact and expression 4356 is within third predefined region 4354. As a result, the document (e.g., image 4358) is inserted at the insertion point in the draft email displayed in slide-over window 4348.

[0256] In Figure 4C32, a fourth movement of contact 4350 is detected after the object movement criteria are satisfied by the first portion of the input, and representation 4356 of the document is dragged across the display following the movement of contact 4350 to first predefined area 4308 within slide-over window 4348. The appearance of representation 4356 changes (e.g., becomes elongated and expanded horizontally compared to the appearance shown in Figure 4C28) to indicate that the document will be opened in a new slide-over window if the input ends in its current location.

[0257] In Figure 4C33, the end of input is detected while contact and expression 4356 is within first predefined region 4354. As a result, the document (e.g., image 4358) is opened in a new slide-over window 4360 of a photo application (e.g., the image document's native application) to overlay full-screen window 4102 of the email application.

[0258] In some embodiments, a fifth movement of contact 4350 is detected after the second criterion is satisfied by the first portion of the input, and representation 4356 of the document is dragged across the display following the movement of contact 4350 to second predefined area 4310 within slide-over window 4348. The appearance of representation 4356 changes (e.g., becomes more elongated and horizontally shorter compared to the appearance shown in FIG. 4C32) to indicate that the document will be opened in a new split-screen window if the input ends in its current location. If the end of the input is detected while contact and representation 4356 are within second predefined area 4310, the document (e.g., image 4358) is opened in a new split-screen window of a photo application (e.g., the image document's native application) alongside the split-screen window converted from full-screen window 4102 of the email application.

[0259] In some embodiments, the position of the touched and dragged object is continuously evaluated, and the visual feedback is dynamically updated according to a comparison between the position of the touched / dragged object and the different predefined regions described above (e.g., with respect to Figures 4C27, 4C28, 4C29, 4C30, and 4C32). The display states shown in Figures 4C27-4C30 and 4C32 can be repeated any number of times and in any order based on the current position of the input before the end of the input is detected.

[0260] 4C34-4C40 illustrate actions performed with respect to a content object in response to the end of a drag action performed on the content object, according to some embodiments.

[0261] In Figure 4C34, slide-over window 4348 is displayed overlaying full-screen window 4102. Input by contact 4366 is detected at a location corresponding to object 4364 (e.g., a hyperlink) representing a web page. The initial portion of the input by contact 4366 meets the object movement criteria, and the device highlights object 4364 to indicate that the criteria for initiating a drop action on object 4364 have been met.

[0262] In Figure 4C35, in response to a first movement of contact 4366 detected after the object movement criteria are met, representation 4368 is dragged across the display in accordance with the movement of contact 4366. As shown in Figure 4C35, while contact and representation 4368 are over a portion of the display that does not represent an acceptable drop location for an object representing a web page (e.g., within an area outside first predefined area 4308, second predefined area 4310, third predefined area 4354, and search input field 4355), representation 4368 has a first appearance that indicates that no object move or object copy operation will be performed with respect to the object within the email application if input ends at this point.

[0263] 4C36, a second movement of contact 4366 is detected after the object criteria is satisfied by the first portion of the input, and representation 4368 of the web page is dragged across the display following the movement of contact 4366 into search input field 4355. The appearance of representation 4368 changes (e.g., from an icon to a web address (e.g., URL) or web page title) to indicate that an acceptable drop location is available at this location and that a search will be performed based on the web page's URL or title if the input ends at the current location.

[0264] 4C37 , a third movement of contact 4336 is detected after the object movement criteria are satisfied by the first portion of the input, and representation 4368 of the web page is dragged across the display following the movement of contact 4336 to third predefined area 4354 within slide-over window 4348. The appearance of representation 4368 changes to indicate that an acceptable drop location is available at this location and that the web address or contents of the web page will be inserted into the draft email if input ends at the current location (e.g., it is reduced in s...

Claims

1. 1. A method comprising: In an electronic device including a display generating component and one or more input devices including a touch-sensitive surface, displaying, by the display generation component, a first user interface of a first application; receiving a first input corresponding to a request to display a second application together with the first application in a respective simultaneous display configuration while displaying the first user interface of the first application; in response to receiving the first input, displaying a second user interface of the second application and the first user interface of the first application according to the respective simultaneous display configurations, in which at least a portion of the first user interface of the first application is displayed simultaneously with the second user interface of the second application; receiving a second input including detecting a first contact at a location on the touch-sensitive surface corresponding to the second application and detecting movement of the first contact across the touch-sensitive surface while displaying the second application and the first application according to the respective simultaneous display configurations; In response to detecting the second input, replacing a display of the second application with a display of a third application in accordance with a determination that the second input satisfies a first criterion, and displaying the third application and the first application according to their respective simultaneous display configurations; in response to a determination that the second input satisfies a second criterion different from the first criterion; maintaining a display of the first application; stopping the display of the second application without displaying the third application; A method comprising:

2. 2. The method of claim 1, wherein the respective simultaneous display configurations are first simultaneous display configurations, and the second user interface of the second application is displayed to overlay a portion of the first user interface of the first application in accordance with the first simultaneous display configuration.

3. 3. The method of claim 2, wherein in accordance with a determination that the first criterion is satisfied by the second input, a third user interface of the third application is displayed to overlay the portion of the first user interface of the first application in accordance with the respective simultaneous display configurations.

4. the second input satisfies the first criterion and the display of the third application replaces the display of the second application in the respective simultaneous display configurations; The method comprises: detecting a third input while displaying the third application and the first application according to the respective simultaneous display configurations after the first criterion is satisfied by the second input, the third input including detecting a second contact and detecting movement of the second contact across the touch-sensitive surface; In response to detecting the third input, replacing a display of the third application with a display of a fourth application in accordance with a determination that the third input satisfies the first criterion, and displaying the fourth application and the first application according to their respective simultaneous display configurations; The method according to any one of claims 1 to 3, comprising:

5. 5. The method of claim 1, further comprising: displaying an indication of one or more application views displayable in the respective simultaneous display configurations in response to detecting a respective input that satisfies the first criterion.

6. 6. The method of claim 1, wherein the first and second criteria have a first movement criterion that requires that the movement of the first contact across the touch-sensitive surface corresponds to movement in a first predetermined direction relative to a currently displayed user interface of the second application, the first criterion has a first starting position criterion that requires the movement of the first contact to begin at a position within a threshold distance of a side edge of the second user interface of the second application, and the second criterion has a second starting position criterion that requires the movement of the first contact to begin at a position within a threshold distance of a bottom edge of the second user interface of the second application.

7. 6. The method of claim 1, wherein the first criteria has a first movement criterion that requires that the movement of the first contact across the touch-sensitive surface corresponds to movement in a first predetermined direction relative to a currently displayed user interface of the second application, and the second criteria has a second movement criterion that requires that the movement of the first contact across the touch-sensitive surface corresponds to movement in a second predetermined direction different from the first predetermined direction relative to the currently displayed user interface of the second application.

8. In response to detecting the second input, 8. The method of claim 1, further comprising: simultaneously displaying, in accordance with a determination that the second input satisfies a third criterion, a representation of each of a plurality of application views recently displayed in the respective simultaneous display configurations together with another application, the representation of the application view corresponding to the second application and a representation of an application view corresponding to the third application.

9. 9. The method of claim 8, wherein the representation of the application view corresponding to the second application includes an identifier of the second application and an identifier of the application window corresponding to the second application, and the representation of the application view corresponding to the third application includes an identifier of the third application and an identifier of the application window corresponding to the third application.

10. 10. The method of claim 8 or 9, wherein the third criteria include a respective start position criterion requiring that movement of the first contact start within a threshold range of a first edge of the second application, and a respective movement criterion requiring that the movement of the first contact satisfy a first movement condition in order to satisfy the third criterion.

11. 11. The method of claim 8, wherein the respective representations of the plurality of application views do not include a representation of an application view of the first application among the respective representations of the plurality of application views that have recently been displayed in the respective simultaneous display configurations with another application.

12. detecting a fourth input satisfying a fourth criterion while displaying the respective representations of the plurality of application views recently displayed in the respective simultaneous display configurations with another application, the representations of the application view corresponding to the second application and the representations of the application view corresponding to the third application; In response to detecting the fourth input, ceasing display of the representation of the application view corresponding to the second application in accordance with determining that the fourth input is directed to the representation of the second application; ceasing display of the representation of the application view corresponding to the third application in accordance with determining that the fourth input is directed to the representation of the third application; The method of any one of claims 8 to 11, comprising:

13. detecting a fifth input satisfying a fifth criterion while displaying the respective representations of the plurality of application views recently displayed in the respective simultaneous display configurations with another application, the representations of the application view corresponding to the second application and the representations of the application view corresponding to the third application; in response to detecting the fifth input, changing a relative display emphasis of the first application view and the second application view according to the fifth input; 13. The method of any one of claims 8 to 12, comprising:

14. detecting a sixth input satisfying a sixth criterion while displaying the respective representations of the plurality of application views recently displayed in the respective simultaneous display configurations with another application; In response to detecting the sixth input, ceasing to display the respective representations of the plurality of application views; and displaying a respective application view selected from the plurality of application views in the respective co-display configuration with the first application, the respective application view being selected based on a position of the sixth input; 14. The method of any one of claims 8 to 13, comprising:

15. In response to detecting the second input, 15. The method of claim 8, further comprising: visually obscuring a displayed portion of the first user interface of the first application relative to the respective representations of the plurality of application views that were recently displayed in the respective simultaneous display configurations with another application in accordance with a determination that the second input satisfies the third criterion.

16. 16. The method of claim 1, wherein the first criterion is satisfied by a horizontal swipe gesture detected near a bottom edge of each application displayed in the respective simultaneous display configuration along with the first application.

17. detecting a seventh input while displaying the first application after the second criterion was satisfied by a previous input and the respective application was removed from simultaneous display in the respective simultaneous display configuration with the first application, the seventh input including detecting a third contact and detecting movement of the third contact across the touch-sensitive surface; In response to detecting the seventh input, in accordance with a determination that the seventh input satisfies a seventh criterion, restoring the display of the respective application to re-display the respective application and the first application according to the respective simultaneous display configurations; 17. The method of any one of claims 1 to 16, comprising:

18. In response to detecting the seventh input, 20. The method of claim 17, comprising displaying an indication of one or more application views displayable in the respective simultaneous display configurations in accordance with a determination that the seventh input satisfies the seventh criterion.

19. detecting an eighth input while displaying the respective application and the first application according to the respective simultaneous display configurations, the eighth input including detecting a fourth contact, detecting movement of the fourth contact across the touch-sensitive surface, and detecting lift-off of the fourth contact after the movement of the fourth contact; In response to detecting the eighth input, in accordance with a determination that the eighth input satisfies an eighth criterion requiring that the fourth contact is detected at a location on the touch-sensitive surface corresponding to first content represented in the first user interface of the first application and that the movement of the fourth contact across the touch-sensitive surface corresponds to movement from a location of the first content to a location above the respective application, displaying the application corresponding to the first content together with the first application in accordance with the respective simultaneous display configurations by replacing a display of the respective application with a display of the first content in the application corresponding to the first content; 19. The method of any one of claims 1 to 18, comprising:

20. detecting a ninth input while displaying each application and the first application according to the respective simultaneous display configurations, the ninth input including detecting a fifth contact, detecting movement of the fifth contact across the touch-sensitive surface, and detecting lift-off of the fifth contact after the movement of the fifth contact; In response to detecting the ninth input, in accordance with a determination that the fifth contact is detected at a location on the touch-sensitive surface corresponding to a first application icon in a dock displayed simultaneously with the first application and the ninth input satisfies a ninth criterion requiring that the fifth contact corresponds to movement across the touch-sensitive surface from a location of the first application icon to a location above the respective application, displaying the application corresponding to the first application icon together with the first application in accordance with the respective simultaneous display configuration by replacing a display of the respective application with a display of the application corresponding to the first application icon; 20. The method of any one of claims 1 to 19, comprising:

21. In response to detecting the second input, In response to a determination that the second input satisfies a tenth criterion, moving the second application relative to the first application in accordance with the movement of the first contact; maintaining a display of the second application along with the first application in the respective simultaneous display configuration; 21. The method of any one of claims 1 to 20, comprising:

22. Each of the simultaneous display configurations is a first simultaneous display configuration in which the second application is displayed so as to overlay a portion of the first application, and the method further comprises: In response to detecting the second input, 22. The method of claim 1, comprising: switching from displaying the second application and the first application in the first simultaneous display configuration to displaying the second application and the first application in the second simultaneous display configuration, the second application and the first application, wherein the first application and the second application are displayed side-by-side in a second simultaneous display configuration, in accordance with a determination that the second input satisfies an eleventh criterion.

23. detecting, while displaying the first application after receiving the second input, a twelfth input corresponding to a request to display an application switcher user interface including a representation of a plurality of recently opened applications; in response to detecting the twelfth input, replacing the display of the first application with a display of the application switcher user interface including a representation of a plurality of application views corresponding to the plurality of recently opened applications, the application switcher user interface including one or more first application views that are full screen windows and one or more second application views that are slide-over windows displayed with another application view, the application switcher user interface including any of the first application views; 23. The method of any one of claims 1 to 22, comprising:

24. 1. A method comprising:

1. An electronic device including a display generating component and one or more input devices, comprising: displaying, by the display generation component, a dock including a plurality of application icons overlaid on a first user interface of a first application, the plurality of application icons corresponding to different applications installed on the electronic device; detecting a first input while displaying the dock overlaid on the first user interface of the first application, the first input including detecting a selection of a respective application icon in the dock; in response to detecting the first input and in accordance with a determination that the first input satisfies a selection criterion; displaying, via the display generation component, a representation of each of the plurality of windows of the first application in accordance with a determination that the respective application icon corresponds to the first application and that the first application is associated with a plurality of windows; maintaining a display of the first user interface of the first application in accordance with a determination that the respective application icon corresponds to the first application and that the first application is currently associated with only a single window; pursuant to a determination that the respective application icon corresponds to a second application distinct from the first application, replacing a display of the first user interface of the first application with a display of a second user interface of the second application, regardless of a number of windows associated with the second application at the time the first input was detected; A method comprising:

25. Replacing a display of the first user interface of the first application with a display of the second user interface of the second application includes: replacing a display of the first user interface of the first application with a display of the single window associated with the second application in accordance with a determination that the second application was associated with a single window at the time the first input was detected; replacing a display of the first user interface of the first application with a display of a most recently displayed user interface of the second application in the plurality of windows in accordance with a determination that the second application was associated with a plurality of windows at the time the first input was detected; 25. The method of claim 24, comprising:

26. detecting a second input while displaying each of the plurality of windows associated with the second application after detecting the first input, the second input including detecting a selection of an application icon in the dock corresponding to the second application; In response to detecting the second input, displaying, via the display generation component, a representation of each of the plurality of windows of the second application in accordance with a determination that the second input satisfies the selection criteria and the second application was associated with a plurality of windows at the time the second input was detected; and 26. The method of claim 25, comprising:

27. Replacing a display of the first user interface of the first application with a display of the second user interface of the second application includes:

27. The method of claim 24, further comprising: replacing a display of the first user interface of the first application with a display of a default window associated with the second application in accordance with a determination that the second application was not associated with any window at the time the first input was detected.

28. Displaying the respective representations of the plurality of windows of the first application includes: displaying a representation of each of one or more first windows of the first application being a full screen window; displaying respective representations of one or more second windows of the first application, the second windows being slide-over windows or split-screen windows, in respective simultaneous display configurations with another application; 28. The method of any one of claims 24 to 27, comprising:

29. 30. The method of claim 28, wherein the one or more second windows comprise respective slide-over windows of the first application that are displayed over a portion of the application currently displayed according to a first simultaneous display configuration.

30. detecting an input activating the respective representations of the respective slide-over windows of the first application while displaying the respective representations of the plurality of windows of the first application, the respective representations of the respective slide-over windows of the first application; in response to detecting the input activating the respective representation of the respective slide-over window of the first application, displaying the respective slide-over window of the first application so as to overlay a portion of a user interface of the application last displayed with the respective slide-over window of the first application in the first simultaneous display configuration; 30. The method of claim 29, comprising:

31. 31. The method of any one of claims 28 to 30, wherein the one or more second windows include a respective split screen window of the first application displayed adjacent to another window that is paired with the respective split screen window of the first application in a second simultaneous display configuration.

32. in response to detecting the first input and in accordance with the determination that the first input satisfies the selection criterion; 32. The method of claim 24, further comprising: displaying, via the display generating component, a first user interface object that, when activated, causes a user interface for opening a document in the first application to be displayed in accordance with a determination that the respective application icon corresponds to the first application and that the first application is associated with a plurality of windows.

33. in response to detecting the first input and in accordance with the determination that the first input satisfies the selection criterion; 33. The method of any one of claims 24 to 32, comprising displaying, via the display generation component, a second user interface object that, when activated, causes a user interface corresponding to a new document in the first application to be displayed in accordance with a determination that the respective application icon corresponds to the first application and that the first application is associated with a plurality of windows.

34. in response to detecting the first input and in accordance with the determination that the first input satisfies the selection criterion; 34. The method of claim 24, further comprising: reducing a size of a window displaying the first user interface of the first application in accordance with a determination that the respective application icon corresponds to the first application and that the first application is associated with multiple windows.

35. displaying, in response to detecting the first input and according to a determination that the first input satisfies menu display criteria distinct from the selection criteria, one or more selectable options for performing operations within the application corresponding to the respective application icon, including displaying a first selectable option for displaying all windows associated with the application corresponding to the respective application icon; detecting an input activating a first selectable option while displaying the one or more selectable options for performing an action within the first application; in response to detecting the input activating the first selectable option, displaying, via the display generation component, a representation of each of all windows of the first application; 35. The method of any one of claims 24 to 34, comprising:

36. 36. The method of any one of claims 24 to 35, comprising maintaining a display of the dock simultaneously with the respective representations of the plurality of windows of the first application.

37. detecting a third input at a location corresponding to the respective application icon corresponding to the first application while displaying the respective application icon corresponding to the first application on a home screen user interface including a plurality of application icons corresponding to different applications installed on the device; in response to detecting the third input and in accordance with a determination that the third input satisfies a menu display criterion distinct from the selection criterion, displaying a plurality of selectable options including at least a first selectable option for performing an action within the first application and a second selectable option for displaying all windows associated with the first application; detecting a fourth input while displaying the plurality of selectable options, the fourth input activating the second selectable option; and in response to detecting the fourth input activating the second selectable option, displaying via the display generation component, a representation of each of all windows of the first application; 37. The method of any one of claims 24 to 36, comprising:

38. 38. The method of claim 24, wherein the respective representations of the plurality of windows of the first application include an identifier of the first application and a respective identifier of each of the plurality of windows of the first application.

39. 1. A method comprising:

1. An electronic device including a display generating component and one or more input devices, comprising: displaying, by the display generation component, a first user interface including a selectable representation of a first content, the first content being associated with a first application; detecting a first input while displaying the first user interface including the selectable representation of the first content, the first input including detecting an input corresponding to a request to move the selectable representation of the first content across the display to a respective position; In response to detecting the first input, resizing the first user interface in accordance with a determination that the respective location is a first location and displaying a second user interface adjacent to the first user interface, the second user interface including the first content; displaying a third user interface including the first content overlaid on the first user interface in accordance with a determination that the respective location is a second location different from the first location; A method comprising:

40. in response to detecting the first input and prior to detecting an end of the first input, 40. The method of claim 39, comprising: reducing a size of the first user interface in accordance with a determination that a current location of the selectable representation is the first location.

41. in response to detecting the first input and prior to detecting an end of the first input, 41. The method of claim 39 or 40, comprising reducing a size of the first user interface by a first amount in accordance with a determination that the current position of the selectable representation is the second position.

42. in response to detecting the first input and prior to detecting an end of the first input, 42. The method of claim 41, further comprising: reducing the size of the first user interface by a second amount greater than the first amount in accordance with a determination that the current position of the selectable representation is the first position, the size of the first user interface being reduced by different amounts on two opposing sides of the first user interface.

43. in response to detecting the first input and prior to detecting an end of the first input, modifying an appearance of the selectable representation of the first content according to a current position of the selectable representation; displaying the selectable representation of the first content in a first appearance in accordance with a determination that the current location of the selectable representation is the first location; displaying the selectable representation of the first content in a second appearance different from the first appearance in accordance with a determination that the current location of the selectable representation is the second location; 43. The method of any one of claims 39 to 42, comprising:

44. in response to detecting the first input and prior to detecting an end of the first input, 44. A method according to any one of claims 39 to 43, comprising, in accordance with a determination that the current position of the selectable representation is at the first position or the second position, clarifying a portion of the background behind the first user interface to indicate that if an end of the first input is detected, a new user interface including the first content will be displayed simultaneously with the first user interface.

45. in response to detecting the first input and prior to detecting an end of the first input, in response to a determination that the current position of the selectable representation is at the first position or the second position, displaying a first application identifier of an application for opening the first content contemporaneously with the selectable representation of the first content; visually obscuring the selectable representation of the first content without visually obscuring the first application identifier; and 45. The method of any one of claims 39 to 44, comprising:

46. in response to detecting the first input and prior to detecting an end of the first input, 46. ​​The method of claim 39, further comprising: resizing the selectable representation of the first content such that the selectable representation of the first content at least partially overlaps the first user interface in accordance with a determination that the current location of the selectable representation is at the second location.

47. in response to detecting the first input and prior to detecting an end of the first input, 47. The method of any one of claims 39 to 46, comprising: resizing the selectable representation of the first content such that a gap exists between the selectable representation of the first content and the resized first user interface in accordance with a determination that a current position of the selectable representation is at the first position.

48. in response to detecting the first input and prior to detecting an end of the first input, 48. The method of claim 39, comprising: visually obscuring the selectable representation of the first content without visually obscuring the first user interface in accordance with a determination that the current location of the selectable representation is at the second location.

49. in response to detecting the first input and prior to detecting an end of the first input, displaying a first visual feedback in accordance with determining that a current location of the selectable representation is at the first location or the second location to indicate that if an end of the first input is detected at a current time, the first content will be displayed in a window simultaneously with the first user interface; in accordance with a determination that the current location of the selectable representation is not at the first location or the second location, ceasing to display the first visual feedback to indicate that the first content will not be displayed in a window concurrently with the first user interface if an end of the first input is detected at the current time; 49. The method of any one of claims 39 to 48, comprising:

50. detecting a second input while displaying the first user interface including the selectable representation of the first content, the second input including detecting an input that satisfies an activation criterion; in response to detecting the second input, replacing a display of the first user interface with a display of a fourth user interface including the first content; 50. The method of any one of claims 39 to 49, comprising:

51. Detecting the first input comprises: detecting a tap-and-hold input enabling a drag operation to be performed on the selectable representation in the first user interface; detecting a drag input subsequent to the tap and hold input, moving the selectable representation, or a copy thereof, from an original location of the selectable representation in the first user interface to a predetermined side of the display; 51. The method of any one of claims 39 to 50, comprising:

52. In response to detecting the first input, 52. The method of claim 39, further comprising: maintaining display of the first user interface without displaying the first content in accordance with a determination that the respective location is a third location different from both the first location and the second location.

53. 53. The method of any one of claims 39 to 52, wherein the first user interface is a user interface of an email application and the first content is an email message.

54. 53. The method of any one of claims 39 to 52, wherein the first user interface is a user interface of an email application and the first content is an attachment to an email message.

55. 53. The method of any one of claims 39 to 52, wherein the first user interface includes a simultaneous display of a file list of a file management application and a user interface of a second application, and the first content is a document listed in the file list of the file management application.

56. detecting a third input while displaying the first user interface including the selectable representation of the first content, the third input including detecting an input that satisfies a menu display criterion; in response to detecting the third input, displaying one or more selectable options for performing an action on the first content, including a first selectable option that, when activated, causes the device to display the first content in a new window along with the first user interface; and 56. The method of any one of claims 39 to 55, comprising:

57. 57. The method of any one of claims 39 to 56, wherein the first user interface, the second user interface, and the third user interface are all user interfaces of the first application.

58. 57. The method of any one of claims 39 to 56, wherein the first user interface is a user interface of an application separate from the first application.

59. detecting a fourth input, the fourth input including detecting an input corresponding to a request to move the third user interface across the display while displaying the third user interface as an overlay on a portion of the first user interface; in response to detecting the fourth input and in accordance with a determination that the fourth input satisfies a window close criterion, ceasing display of the third user interface while maintaining display of the first user interface; 59. The method of any one of claims 39 to 58, comprising:

60. the first user interface includes, prior to detecting the first input, a first region including a series of content items including the first content, and a second region including a second content of the series of content items; The method comprises:

60. The method of claim 39, comprising ceasing display of the first region in the first user interface while expanding the second region in the first user interface in response to detecting the first input and in accordance with a determination that the third user interface is displayed adjacent to the first user interface.

61. the second region of the first user interface includes a navigation affordance that, when activated, navigates up a hierarchy within the set of content items; the second user interface does not include the navigation affordance when displayed adjacent to the first user interface; the second user interface includes a drag handle for moving the second user interface relative to the first user interface; The method comprises: detecting a fifth input corresponding to a request to drag the second user interface relative to the first user interface; in response to detecting that the fifth input satisfies a swap criterion (e.g., a drag handle is moved horizontally toward a side of the first user interface by more than a threshold amount), swapping positions of the first user interface and the second user interface and displaying the navigation affordance in the second user interface instead of the first user interface; 61. The method of claim 60, comprising:

62. In response to detecting the first input, 62. The method of any one of claims 39 to 61, comprising: displaying, in accordance with a determination that the respective position is the first position, a close affordance simultaneously with the second user interface, the close affordance, when activated, closing the second user interface and restoring the first user interface to a size prior to displaying the second user interface.

63. In response to detecting the first input, 63. The method of any one of claims 39 to 62, comprising: displaying a send affordance simultaneously with the second user interface in accordance with a determination that the respective location is the first location, the send affordance, which, when activated, closes the second user interface and displays a user interface for sending the first content to a recipient.

64. In response to detecting the first input, 64. The method of any one of claims 39 to 63, comprising performing an action corresponding to the first content in the first application in accordance with a determination that the respective location is a third location.

65. In response to detecting the first input, 65. The method of any one of claims 39 to 64, comprising performing an action corresponding to the first content in the second application in accordance with a determination that the respective location is a fourth location.

66. 1. A method comprising:

1. An electronic device including a display generating component and one or more input devices, comprising: displaying, by the display generation component, a first user interface including a selectable user interface; detecting a first input while displaying the first user interface including the selectable user interface object, the first input including detecting an input corresponding to a request to move the selectable user interface object across the display to a respective position; In response to detecting the first input, creating a new window of the first application in accordance with a determination that the respective locations are within a first predefined area of ​​the user interface and that the selectable user interface objects are application icons of a first application; creating a new window of the first application in accordance with a determination that the respective locations are within a second predefined area of ​​the user interface, the second predefined area of ​​the user interface being smaller than the first predefined area of ​​the user interface and the selectable user interface objects being within a second predefined area of ​​the user interface that is a representation of content associated with the first application; performing an operation corresponding to the selectable user interface object other than creating a new window of the first application in accordance with a determination that the respective location is within a third region of the user interface, the third region of the user interface being smaller than the first predefined region of the user interface and not overlapping with the second predefined region of the user interface, the selectable user interface object being a representation of content associated with the first application; A method comprising:

67. The new window that is created when the respective location is within the first predefined area of ​​the user interface is a first type window, and the method further comprises: In response to detecting the first input, creating a new window of the first application of a second type different from the first type in accordance with a determination that the respective locations are within a fourth predefined area of ​​the user interface that does not overlap with the first predefined area of ​​the user interface and that the selectable user interface objects are application icons of a first application; creating a new window of the first application of the second type in accordance with a determination that the respective locations are within a fifth predefined area of ​​the user interface, the fifth predefined area of ​​the user interface being smaller than the fourth predefined area of ​​the user interface, and the selectable user interface objects are within a fifth predefined area of ​​the user interface that is a representation of content associated with the first application; performing an operation corresponding to the selectable user interface object other than creating a new window for the first application in accordance with a determination that the respective location is within a sixth region of the user interface, the sixth region of the user interface being smaller than the fourth predefined region of the user interface and not overlapping with the fifth predefined region of the user interface, and the selectable user interface object being a representation of content associated with the first application; 67. The method of claim 66, comprising:

68. 1. A method comprising:

1. An electronic device including a display generating component and one or more input devices, comprising: displaying, by the display generation component, a dock including a plurality of application icons simultaneously with a first user interface of a first application, the plurality of application icons corresponding to different applications; detecting a first input directed to an application icon in the dock corresponding to a second application while simultaneously displaying the dock with the first user interface of the first application, the first input including a movement into a first region of the display and a subsequent termination of the first input into the first region of the display; In response to detecting the first input, displaying, via the display generation component, a first representation of a first window of the second application and a second representation of a second window of the second application concurrently with the first user interface of the first application within a second region of the display in accordance with a determination that the second application is associated with a plurality of windows; pursuant to determining that the second application is associated with only a single window, displaying, via the display generation component, a user interface of the second application simultaneously with the first user interface of the first application, the user interface of the second application being displayed within the second region of the display; A method comprising:

69. 69. The method of claim 68, wherein the second region is a predefined region of the display.

70. displaying a first affordance for opening a document in the second application simultaneously with the first representation of the first window and the second representation of the second window of the second application; Detecting an input that activates the first affordance for opening a document in the second application while displaying the first affordance; in response to detecting the input that activates the first affordance, displaying a user interface for selecting a document for display in a new window in the second region of the display; 70. The method of claim 68 or 69, comprising:

71. displaying a second affordance for creating a new document in the second application simultaneously with the first representation of the first window and the second representation of the second window of the second application; detecting an input activating the second affordance for creating a new document in the second application while displaying the second affordance; in response to detecting the input that activates the second affordance; displaying a new window of the second application in the second area of ​​the display; 71. The method of any one of claims 68 to 70, comprising:

72. detecting a second input directed to the second region of the display including a movement across the second region of the display and a subsequent termination of the second input while displaying the first representation of the first window and the second representation of the second window of the second application; In response to detecting the second input, ceasing to display the first representation of the first window while maintaining a display of the second representation of the second window of the second application in accordance with a determination that the second input meets a rejection criterion and a position of the second input corresponds to the first representation of the first window of the second application; and ceasing to display the second representation of the second window while maintaining a display of the first representation of the first window of the second application in accordance with a determination that the second input meets the rejection criterion and a position of the second input corresponds to the second representation of the second window of the second application; and 72. The method of any one of claims 68 to 71, comprising:

73. 73. The method of any one of claims 68 to 72, wherein displaying the user interface of the second application simultaneously with the first user interface of the first application comprises displaying the user interface of the second application adjacent to the first user interface of the first application.

74. 73. The method of any one of claims 68 to 72, wherein displaying the user interface of the second application simultaneously with the first user interface of the first application comprises displaying the user interface of the second application so as to overlay a portion of the first user interface of the first application.

75. detecting a third input directed toward the second region of the display between the first representation of the first window and the second representation of the second window of the second application; In response to detecting the third input, in response to a determination that the third input satisfies a rejection criterion for closing the first window of the second application; ceasing to display the first representation in the first window while maintaining the display of the second representation in the second window of the second application; in response to a determination that the second representation of the second window of the second application is a representation of only one window of the second application; ceasing to display the second representation in the second window; and displaying the second window within the second region of the display; 75. The method of any one of claims 68 to 74, comprising:

76. detecting a third input directed toward the second region of the display between the first representation of the first window and the second representation of the second window of the second application; In response to detecting the third input, in response to a determination that the third input satisfies a rejection criterion for closing the first window of the second application, ceasing to display the first representation in the first window while maintaining the display of the second representation in the second window of the second application; maintaining a display of the second representation of the second window of the second application in the second region of the display in accordance with a determination that the second representation of the second window of the second application is a representation of only one window of the second application; 75. The method of any one of claims 68 to 74, comprising:

77. displaying an affordance for opening a new window of the second application simultaneously with the first representation of the first window and the second representation of the second window of the second application; Detecting a plurality of inputs directed to the second region of the display; In response to detecting the plurality of inputs, in response to a determination that the plurality of inputs meets a rejection criterion for closing the first window and the second window of the second application, ceasing to display the first representation of the first window and the second representation of the second window of the second application; maintaining the display of the affordance for opening a new window of the second application within the second region of the display in accordance with a determination that a window of the second application is not represented within the second region; and 75. The method of any one of claims 68 to 74, comprising:

78. 1. A method comprising:

1. An electronic device including a display generating component and one or more input devices, comprising: simultaneously displaying, by the display generation component, the first application view and the second application view in a first simultaneous display configuration of a plurality of simultaneous display configurations including a first simultaneous display configuration specifying a first arrangement of simultaneously displayed application views, a second simultaneous display configuration specifying a second arrangement of simultaneously displayed application views that differs from the first arrangement of simultaneously displayed application views, and a third simultaneous display configuration specifying a third arrangement of simultaneously displayed application views that differs from both the first arrangement of simultaneously displayed application views and the second arrangement of simultaneously displayed application views; detecting a first input beginning at a location directed toward the first application view in the first array of simultaneously displayed application views and including a first movement and a termination of the first input after the first movement is detected; in response to detecting the first movement of the first input, moving a representation of the first application view on the display according to the first movement of the first input; displaying, while the representation of the first application view is on a first portion of the display, a first visual indication indicating that when the first input is terminated, the first application view and the second application view will be displayed in the first simultaneous display configuration; displaying, while the representation of the first application view is on a second portion of the display, a second visual indication indicating that when the first input is terminated, the first application view and the second application view will be displayed in the second simultaneous display configuration; displaying, while the representation of the first application view is on a third portion of the display, a third visual indication indicating that when the first input is terminated, the first application view and the second application view will be displayed in the third simultaneous display configuration; and in response to detecting the end of the first input, displaying the first application view and the second application view in the first simultaneous display configuration in accordance with a determination that the first input ended while the first application view was over the first portion of the display; displaying the first application view and the second application view in the second simultaneous display configuration in accordance with a determination that the first input ended while the first application view was on the second portion of the display; displaying the first application view and the second application view in the third simultaneous display configuration in accordance with a determination that the first input ended while the first application view was on the third portion of the display; A method comprising:

79. 80. The method of claim 78, wherein the first arrangement of simultaneously displayed application views differs from the second arrangement of simultaneously displayed application views in terms of relative display positions along a first direction of at least the first application view and the second application view defined by the display generation component.

80. 80. The method of claim 79, wherein the first application view is displayed to overlay different portions of the second application view in the first array of simultaneously displayed application views and in the second array of simultaneously displayed application views.

81. 81. The method of claim 80, wherein the first application view is a slide-over window that overlays a first side of the second application view in the first array of simultaneously displayed application views and is a slide-over window that overlays a second side of the second application view in the second array of simultaneously displayed application views.

82. 81. The method of claim 80, wherein the first application view is displayed adjacent to a first side of the second application view in the first array of simultaneously displayed application views and adjacent to a second side of the second application view in the second array of simultaneously displayed application views.

83. 81. The method of claim 80, wherein the first application view is displayed so as to overlay a periphery of the second application view in the first array of simultaneously displayed application views and so as to overlay a center portion of the second application view in the second array of simultaneously displayed application views.

84. 81. The method of claim 80, wherein the first application view is displayed so as to overlay a central portion of the second application view in the first array of simultaneously displayed application views and so as to overlay a peripheral portion of the second application view in the second array of simultaneously displayed application views.

85. 81. The method of claim 80, wherein the first application view is displayed so as to overlay a central portion of the second application view in the first array of simultaneously displayed application views and is displayed in a minimized state so as to overlay a peripheral portion of the second application view in the second array of simultaneously displayed application views.

86. 81. The method of claim 80, wherein the first application view is displayed in a minimized state so as to overlay or be adjacent to a periphery of the second application view in the first array of simultaneously displayed application views, and is displayed so as to overlay a central portion of the second application view in the second array of simultaneously displayed application views.

87. 81. The method of claim 80, wherein the first application view is displayed adjacent to a side of the second application view in the first array of simultaneously displayed application views and is displayed in a minimized state overlaying or adjacent to a periphery of the second application view in the second array of simultaneously displayed application views.

88. 81. The method of claim 80, wherein the first application view is displayed in a minimized state overlaying or adjacent to a periphery of the second application view in the first array of simultaneously displayed application views and overlaying a side of the second application view in the second array of simultaneously displayed application views.

89. 80. The method of claim 78, wherein the first arrangement of simultaneously displayed application views differs from the second arrangement of simultaneously displayed application views in terms of relative display layers of at least the first and second application views defined by the display generation component.

90. 90. The method of claim 89, wherein the first application view is a slide-over window that overlays a first side of the second application view in the first array of simultaneously displayed application views and is displayed adjacent to a second side of the second application view in the second array of simultaneously displayed application views.

91. 90. The method of claim 89, wherein the first application view is displayed adjacent to a first side of the second application view in the first array of simultaneously displayed application views and overlaid on a second side of the second application view in the second array of simultaneously displayed application views.

92. 90. The method of claim 89, wherein the first application view is displayed adjacent to a periphery of the second application view in the first array of simultaneously displayed application views and overlaying a center portion of the second application view in the second array of simultaneously displayed application views.

93. 90. The method of claim 89, wherein the first application view is displayed so as to overlay a central portion of the second application view in the first array of simultaneously displayed application views and adjacent to a peripheral portion of the second application view in the second array of simultaneously displayed application views.

94. 94. The method of any one of claims 79 to 93, wherein the third arrangement of simultaneously displayed application views differs from the first arrangement of simultaneously displayed application views in at least a relative display position between the first application view and the second application view or a relative display layer of the first application view and the second application view.

95. 95. The method of any one of claims 78 to 94, wherein the first visual indication is different from the second visual indication and the third visual indication, and the second visual indication is different from the third visual indication.

96. 96. The method of claim 78, comprising visually obscuring content of the second application view during the first movement of the first input in accordance with a current position of the first application view and a determination that the second application view is resized to a respective simultaneous display configuration corresponding to the current position of the first application view.

97. 97. The method of claim 78, further comprising: displaying the second application view without visually obscuring content of the second application view in accordance with a current position of the first application view and a determination that the second application view will not be resized to a respective simultaneous display configuration corresponding to the current position of the first application view during the first movement of the first input.

98. detecting, while simultaneously displaying the first application view and the second application view in the first simultaneous display configuration of the multiple simultaneous display configurations by the display generation component after detecting the termination of the first input, a second input beginning at a position directed toward the second application view in the first array of simultaneously displayed application views and including a second movement and a termination of the second input after the second movement is detected; in response to detecting the second movement of the second input, moving the representation of the second application view on the display according to the second movement of the second input; displaying, while the representation of the second application view is on a fourth portion of the display, a fourth visual indication indicating that when the second input is terminated, the first application view and the second application view will be displayed in the first simultaneous display configuration; displaying, while the representation of the second application view is on a fifth portion of the display, a fifth visual indication indicating that when the second input is terminated, the first application view and the second application view will be displayed in the second simultaneous display configuration; displaying, while the representation of the second application view is on a sixth portion of the display, a sixth visual indication indicating that when the second input is terminated, the first application view and the second application view will be displayed in the third simultaneous display configuration; and in response to detecting the end of the second input, displaying the first application view and the second application view in the first simultaneous display configuration in accordance with a determination that the second input ended while the second application view was on the fourth portion of the display; displaying the first application view and the second application view in the second simultaneous display configuration in accordance with a determination that the second input ended while the second application view was on the fifth portion of the display; displaying the first application view and the second application view in the third simultaneous display configuration in accordance with a determination that the second input ended while the second application view was on the sixth portion of the display; 98. The method of any one of claims 78 to 97, comprising:

99. Moving the representation of the first application view on the display in accordance with the first movement of the first input comprises: displaying, while the representation of the first application view is on a seventh portion of the display, a seventh visual indication indicating that when the first input is terminated, the first application view and the second application view are displayed in a fourth simultaneous display configuration of the multiple simultaneous display configurations, the fourth simultaneous display configuration being different from the first, second, and third simultaneous display configurations; The method comprises: in response to detecting the end of the first input, 99. The method of any one of claims 78 to 98, further comprising: displaying the first application view and the second application view in the fourth simultaneous display configuration in accordance with a determination that the first input ended while the first application view was on the seventh portion of the display.

100. In response to detecting the first movement of the first input, moving the representation of the first application view on the display according to the first movement of the first input comprises: while the representation of the first application view is on an eighth portion of the display.

100. The method of claim 78, further comprising: in accordance with a determination that the eighth portion of the display corresponds to the position of the first application view at the start of the first input, redisplaying the first application view and the second application view in the first simultaneous display configuration as an indication that the first application view and the second application view will be redisplayed in the first simultaneous display configuration if the first input ends within the eighth region.

101. detecting, while simultaneously displaying the first application view and the second application view in the first simultaneous display configuration of the multiple simultaneous display configurations by the display generation component after detecting the termination of the first input, a third input beginning at a location directed toward the first application view in the first array of simultaneously displayed application views and including a third movement and a termination of the third input after the third movement is detected; in response to detecting the third movement of the third input, moving the representation of the first application view on the display according to the third movement of the second input; displaying, while the representation of the first application view is on a respective one of the first, second, and third portions of the display, a respective visual indication indicating that if the third input is terminated, the first application view and the second application view will be displayed in a respective one of the first, second, and third simultaneous display configurations corresponding to the respective one of the first, second, and third portions of the display; displaying, while the representation of the first application view is on a ninth portion of the display, an eighth visual indication indicating that if the third input is terminated, the first application view will be displayed in a standalone display configuration without being displayed simultaneously with the second application view; in response to detecting the end of the second input, pursuant to a determination that the second input was terminated while the first application view was over the respective one of the first, second, and third portions of the display, displaying the first application view and the second application view in the respective one of the first, second, and third simultaneous display configurations corresponding to the respective one of the first, second, and third portions of the display; displaying the first application view in a standalone display configuration in accordance with a determination that the third input was terminated while the first application view was on the ninth portion of the display; and 101. The method of any one of claims 78 to 100, comprising:

102. while the first application view and the second application view are displayed in their respective simultaneous display configurations on the display, displaying a first drag handle on the first application view and a second drag handle on the second application view, wherein displaying the first drag handle and the second drag handle comprises: displaying the first drag handle in a first appearance state and displaying the second drag handle in a second appearance state different from the first appearance state in accordance with a determination that the first application view currently has input focus; displaying the first drag handle in the second appearance state and displaying the second drag handle in the first appearance state in accordance with a determination that the second application view currently has input focus; 102. The method of any one of claims 78 to 101, comprising:

103. 1. A computer system comprising: a display generation component; an input device including a touch-sensitive surface; one or more processors; A memory storing one or more programs, the one or more programs including instructions for causing the computer system to perform operations, the operations including: displaying, by the display generation component, a first user interface of a first application; receiving a first input corresponding to a request to display the first application and a second application in respective simultaneous display configurations while displaying the first user interface of the first application; in response to receiving the first input, displaying a second user interface of the second application and the first user interface of the first application according to the respective simultaneous display configurations, in which at least a portion of the first user interface of the first application is displayed simultaneously with the second user interface of the second application; receiving a second input including detecting a first contact at a location on the touch-sensitive surface corresponding to the second application and detecting movement of the first contact across the touch-sensitive surface while displaying the second application and the first application according to the respective simultaneous display configurations; In response to detecting the second input, replacing a display of the second application with a display of a third application in accordance with a determination that the second input satisfies a first criterion, and displaying the third application and the first application according to their respective simultaneous display configurations; in response to a determination that the second input satisfies a second criterion different from the first criterion; maintaining a display of the first application; stopping the display of the second application without displaying the third application; a memory including: A computer system comprising:

104. 104. A computer system according to claim 103, wherein the one or more programs comprise instructions that cause the computer system to perform a method according to any one of claims 2 to 23.

105. A non-transitory computer-readable storage medium storing one or more programs, which, when executed by a computer system having a display generating component, cause an input device including a touch-sensitive surface to: causing the display generation component to display a first user interface of a first application; receiving a first input corresponding to a request to display the first application and a second application in respective simultaneous display configurations while displaying the first user interface of the first application; in response to receiving the first input, displaying a second user interface of the second application and the first user interface of the first application according to the respective simultaneous display configurations, wherein at least a portion of the first user interface of the first application is displayed simultaneously with the second user interface of the second application; receiving a second input including detecting a first contact at a location on the touch-sensitive surface corresponding to the second application and detecting movement of the first contact across the touch-sensitive surface while displaying the second application and the first application according to the respective simultaneous display configurations; In response to detecting the second input, responsive to a determination that the second input satisfies a first criterion, replacing a display of the second application with a display of a third application to cause the third application and the first application to be displayed according to their respective simultaneous display configurations; in response to a determination that the second input satisfies a second criterion different from the first criterion; maintaining the display of the first application; halting display of the second application without displaying the third application.

106. 106. The computer readable storage medium of claim 105, wherein the one or more programs include instructions that, when executed by the computer system, cause the computer system to perform the method of any one of claims 2 to 23.

107. 24. A non-transitory computer-readable storage medium storing executable instructions that, when executed by an electronic device having one or more processors and a touch-sensitive display, cause the electronic device to perform the method of any one of claims 1 to 23.

108. 1. An electronic device comprising: one or more processors; A touch-sensitive display; A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of any one of claims 1 to 23; An electronic device comprising:

109. 1. An electronic device comprising one or more processors and a touch-sensitive display, Means for carrying out the method according to any one of claims 1 to 23. An electronic device comprising:

110. 1. An information processing device for use in an electronic device comprising one or more processors and a touch-sensitive display, comprising: Means for carrying out the method according to any one of claims 1 to 23. An information processing device comprising:

111. A graphical user interface displayed on a touch-sensitive display of an electronic device comprising one or more processors, the graphical user interface comprising a user interface displayed according to a method according to any one of claims 1 to 23.

112. 1. A computer system comprising: a display generation component; one or more input devices; one or more processors; A memory storing one or more programs, the one or more programs including instructions for causing the computer system to perform operations, the operations including: displaying, by the display generation component, a dock including a plurality of application icons overlaid on a first user interface of a first application, the plurality of application icons corresponding to different applications installed on the electronic device; detecting a first input while displaying the dock overlaid on the first user interface of the first application, the first input including detecting a selection of a respective application icon in the dock; in response to detecting the first input and in accordance with a determination that the first input satisfies a selection criterion; displaying, via the display generation component, a representation of each of the plurality of windows of the first application in accordance with a determination that the respective application icon corresponds to the first application and that the first application is associated with a plurality of windows; maintaining a display of the first user interface of the first application in accordance with a determination that the respective application icon corresponds to the first application and that the first application is currently associated with only a single window; pursuant to a determination that the respective application icon corresponds to a second application distinct from the first application, replacing a display of the first user interface of the first application with a display of a second user interface of the second application, regardless of a number of windows associated with the second application at the time the first input was detected; a memory including: A computer system comprising:

113. 113. A computer system according to claim 112, wherein the one or more programs comprise instructions that cause the computer system to perform a method according to any one of claims 25 to 38.

114. A non-transitory computer-readable storage medium storing one or more programs, which, when executed by a computer system having a display generating component, cause an input device including a touch-sensitive surface to: causing the display generation component to display a dock including a plurality of application icons overlaid on a first user interface of a first application, the plurality of application icons corresponding to different applications installed on the electronic device; detecting a first input while displaying the dock overlaid on the first user interface of the first application, the first input including detecting a selection of a respective application icon in the dock; in response to detecting the first input and in accordance with a determination that the first input satisfies a selection criterion; in response to a determination that the respective application icon corresponds to the first application and that the first application is associated with a plurality of windows, causing a representation of each of the plurality of windows of the first application to be displayed via the display generation component; maintaining a display of the first user interface of the first application in accordance with a determination that the respective application icon corresponds to the first application and that the first application is currently associated with only a single window; a non-transitory computer-readable storage medium that, in accordance with a determination that the respective application icon corresponds to a second application distinct from the first application, causes a display of the first user interface of the first application to be replaced with a display of a second user interface of the second application, regardless of a number of windows associated with the second application at the time the first input was detected.

115. 115. The computer readable storage medium of claim 114, wherein the one or more programs include instructions that, when executed by the computer system, cause the computer system to perform the method of any one of claims 25 to 38.

116. 1. An electronic device comprising: one or more processors; A touch-sensitive display; 39. An electronic device comprising: a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing a method according to any one of claims 24 to 38.

117. 1. An electronic device comprising one or more processors and a touch-sensitive display, Means for carrying out the method according to any one of claims 24 to 38. An electronic device comprising:

118. 1. An information processing device for use in an electronic device comprising one or more processors and a touch-sensitive display, comprising: Means for carrying out the method according to any one of claims 24 to 38. An information processing device comprising:

119. 39. A graphical user interface displayed on a touch-sensitive display of an electronic device comprising one or more processors, the graphical user interface comprising a user interface displayed according to a method according to any one of claims 24 to 38.

120. 1. A computer system comprising: a display generation component; one or more input devices; one or more processors; A memory storing one or more programs, the one or more programs including instructions for causing the computer system to perform operations, the operations including: displaying, by the display generation component, a first user interface including a selectable representation of the first content, the first content being associated with a first application; detecting a first input while displaying the first user interface including the selectable representation of the first content, the first input including detecting an input corresponding to a request to move the selectable representation of the first content across the display to a respective position; In response to detecting the first input, resizing the first user interface in accordance with a determination that the respective location is a first location and displaying a second user interface adjacent to the first user interface, the second user interface including the first content; displaying a third user interface including the first content overlaid on the first user interface in accordance with a determination that the respective location is a second location different from the first location; a memory including: A computer system comprising:

121. 121. A computer system according to claim 120, wherein the one or more programs comprise instructions that cause the computer system to perform a method according to any one of claims 40 to 65.

122. A non-transitory computer-readable storage medium storing one or more programs, which, when executed by a computer system having a display generating component, cause an input device including a touch-sensitive surface to: a display generating component that displays a first user interface including a first content associated with a first application and a selectable representation of the first content; detecting a first input while displaying the first user interface including the selectable representation of the first content, the first input including detecting an input corresponding to a request to move the selectable representation of the first content across the display to a respective position; In response to detecting the first input, pursuant to determining that the respective location is a first location, resizing the first user interface to display a second user interface adjacent to the first user interface, the second user interface including the first content; and displaying a third user interface including the first content overlaid on the first user interface in accordance with a determination that the respective location is a second location different from the first location.

123. 123. The computer readable storage medium of claim 122, wherein the one or more programs include instructions that, when executed by the computer system, cause the computer system to perform the method of any one of claims 40 to 65.

124. 66. A non-transitory computer-readable storage medium storing executable instructions that, when executed by an electronic device having one or more processors and a touch-sensitive display, cause the electronic device to perform the method of any one of claims 39 to 65.

125. 1. An electronic device comprising: one or more processors; A touch-sensitive display; 66. An electronic device comprising: a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing a method according to any one of claims 39 to 65.

126. 66. An electronic device comprising one or more processors and a touch-sensitive display, the electronic device comprising means for performing the method of any one of claims 39 to 65.

127. 66. An information processing apparatus for use in an electronic device having one or more processors and a touch-sensitive display, the information processing apparatus comprising means for carrying out a method according to any one of claims 39 to 65.

128. 66. A graphical user interface displayed on a touch-sensitive display of an electronic device comprising one or more processors, the graphical user interface comprising a user interface displayed according to a method of any one of claims 39 to 65.

129. 1. A computer system comprising: a display generation component; one or more input devices; one or more processors; A memory storing one or more programs, the one or more programs including instructions for causing the computer system to perform operations, the operations including: displaying, by the display generation component, a first user interface including a selectable user interface; detecting a first input while displaying the first user interface including the selectable user interface object, the first input including detecting an input corresponding to a request to move the selectable user interface object across the display to a respective position; In response to detecting the first input, creating a new window of the first application in accordance with a determination that the respective locations are within a first predefined area of ​​the user interface and that the selectable user interface objects are application icons of a first application; creating a new window of the first application in accordance with a determination that the respective locations are within a second predefined area of ​​the user interface, the second predefined area of ​​the user interface being smaller than the first predefined area of ​​the user interface and the selectable user interface objects being within a second predefined area of ​​the user interface that is a representation of content associated with the first application; performing an operation corresponding to the selectable user interface object other than creating a new window of the first application in accordance with a determination that the respective location is within a third region of the user interface, the third region of the user interface being smaller than the first predefined region of the user interface and not overlapping with the second predefined region of the user interface, the selectable user interface object being a representation of content associated with the first application; a memory including: A computer system comprising:

130. 130. The computer system of claim 129, wherein the one or more programs include instructions that cause the computer system to perform the method of claim 67.

131. A non-transitory computer-readable storage medium storing one or more programs, which, when executed by a computer system having a display generating component, cause an input device including a touch-sensitive surface to: causing the display generation component to display a first user interface including a selectable user interface; detecting a first input while displaying the first user interface including the selectable user interface object, the first input including detecting an input corresponding to a request to move the selectable user interface object across the display to a respective position; In response to detecting the first input, creating a new window of the first application in response to a determination that the respective locations are within a first predefined area of ​​the user interface and that the selectable user interface objects are application icons of a first application; creating a new window of the first application in accordance with a determination that the respective locations are within a second predefined area of ​​the user interface, the second predefined area of ​​the user interface being smaller than the first predefined area of ​​the user interface and the selectable user interface objects being within a second predefined area that is a representation of content associated with the first application; a first window for the first application in response to a determination that the respective locations are within a third region of the user interface, the third region of the user interface being smaller than the first predefined region of the user interface and not overlapping with the second predefined region of the user interface, and the selectable user interface objects being a representation of content associated with the first application, the first window for the first application being displayed ...

132. 132. The computer readable storage medium of claim 131, wherein the one or more programs include instructions that, when executed by the computer system, cause the computer system to perform the method of claim 67.

133. 68. A non-transitory computer-readable storage medium storing executable instructions that, when executed by an electronic device having one or more processors and a touch-sensitive display, cause the electronic device to perform the method of claim 66 or 67.

134. 1. An electronic device comprising: one or more processors; A touch-sensitive display; a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of claim 66 or 67; An electronic device comprising:

135. 1. An electronic device comprising one or more processors and a touch-sensitive display, 68. An electronic device comprising means for carrying out the method of claim 66 or 67.

136. 1. An information processing device for use in an electronic device comprising one or more processors and a touch-sensitive display, comprising:

68. An information processing device comprising means for carrying out the method according to claim 66 or 67.

137. 68. A graphical user interface displayed on a touch-sensitive display of an electronic device comprising one or more processors, the graphical user interface comprising a user interface displayed according to the method of claim 66 or 67.

138. 1. A computer system comprising: a display generation component; one or more input devices; one or more processors; A memory storing one or more programs, the one or more programs including instructions for causing the computer system to perform operations, the operations including: displaying, by the display generation component, a dock including a plurality of application icons simultaneously with a first user interface of a first application, the plurality of application icons corresponding to different applications; detecting a first input directed to an application icon in the dock corresponding to a second application while simultaneously displaying the dock with the first user interface of the first application, the first input including a movement into a first region of the display and a subsequent termination of the first input into the first region of the display; In response to detecting the first input, displaying, via the display generation component, a first representation of a first window of the second application and a second representation of a second window of the second application concurrently with the first user interface of the first application within a second region of the display in accordance with a determination that the second application is associated with a plurality of windows; pursuant to determining that the second application is associated with only a single window, displaying, via the display generation component, a user interface of the second application simultaneously with the first user interface of the first application, the user interface of the second application being displayed within the second region of the display; a memory including: A computer system comprising:

139. 139. A computer system according to claim 138, wherein the one or more programs comprise instructions that cause the computer system to perform a method according to any one of claims 69 to 77.

140. A non-transitory computer-readable storage medium storing one or more programs, which, when executed by a computer system having a display generating component, cause an input device including a touch-sensitive surface to: causing the display generation component to simultaneously display a dock including a plurality of application icons with a first user interface of a first application, the plurality of application icons corresponding to different applications; detect, while simultaneously displaying the dock with the first user interface of the first application, a first input directed to an application icon in the dock corresponding to a second application, the first input including a movement into a first region of the display and a subsequent termination of the first input into the first region of the display; In response to detecting the first input, pursuant to determining that the second application is associated with a plurality of windows, causing, via the display generation component, a first representation of a first window of the second application and a second representation of a second window of the second application within a second region of the display concurrently with the first user interface of the first application; A non-transitory computer-readable storage medium that, in accordance with a determination that the second application is associated with only a single window, causes, via the display generation component, a user interface of the second application to be displayed simultaneously with the first user interface of the first application, the user interface of the second application being displayed within the second area of ​​the display.

141. 141. The computer readable storage medium of claim 140, wherein the one or more programs include instructions that, when executed by the computer system, cause the computer system to perform the method of any one of claims 69 to 77.

142. 80. A non-transitory computer-readable storage medium storing executable instructions that, when executed by an electronic device having one or more processors and a touch-sensitive display, cause the electronic device to perform the method of any one of claims 68 to 77.

143. 1. An electronic device comprising: one or more processors; A touch-sensitive display; a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing a method according to any one of claims 68 to 77; An electronic device comprising:

144. 80. An electronic device comprising one or more processors and a touch-sensitive display, the electronic device comprising means for performing the method of any one of claims 68 to 77.

145. 80. An information processing apparatus for use in an electronic device having one or more processors and a touch-sensitive display, the information processing apparatus comprising means for carrying out a method according to any one of claims 68 to 77.

146. 78. A graphical user interface displayed on a touch-sensitive display of an electronic device comprising one or more processors, the graphical user interface comprising a user interface displayed according to the method of any one of claims 68 to 77.

147. 1. A computer system comprising: a display generation component; one or more input devices; one or more processors; A memory storing one or more programs, the one or more programs including instructions for causing the computer system to perform operations, the operations including: simultaneously displaying, by the display generation component, the first application view and the second application view in a first simultaneous display configuration of a plurality of simultaneous display configurations including a first simultaneous display configuration specifying a first arrangement of simultaneously displayed application views, a second simultaneous display configuration specifying a second arrangement of simultaneously displayed application views that differs from the first arrangement of simultaneously displayed application views, and a third simultaneous display configuration specifying a third arrangement of simultaneously displayed application views that differs from both the first arrangement of simultaneously displayed application views and the second arrangement of simultaneously displayed application views; detecting a first input beginning at a location directed toward the first application view in the first array of simultaneously displayed application views and including a first movement and a termination of the first input after the first movement is detected; in response to detecting the first movement of the first input, moving a representation of the first application view on the display according to the first movement of the first input; displaying, while the representation of the first application view is on a first portion of the display, a first visual indication indicating that when the first input is terminated, the first application view and the second application view will be displayed in the first simultaneous display configuration; displaying, while the representation of the first application view is on a second portion of the display, a second visual indication indicating that when the first input is terminated, the first application view and the second application view will be displayed in the second simultaneous display configuration; displaying, while the representation of the first application view is on a third portion of the display, a third visual indication indicating that when the first input is terminated, the first application view and the second application view will be displayed in the third simultaneous display configuration; and in response to detecting the end of the first input, displaying the first application view and the second application view in the first simultaneous display configuration in accordance with a determination that the first input ended while the first application view was over the first portion of the display; displaying the first application view and the second application view in the second simultaneous display configuration in accordance with a determination that the first input ended while the first application view was on the second portion of the display; displaying the first application view and the second application view in the third simultaneous display configuration in accordance with a determination that the first input ended while the first application view was on the third portion of the display; a memory including: A computer system comprising:

148. 148. A computer system according to claim 147, wherein the one or more programs comprise instructions that cause the computer system to perform a method according to any one of claims 79 to 102.

149. A non-transitory computer-readable storage medium storing one or more programs, which, when executed by a computer system having a display generating component, cause an input device including a touch-sensitive surface to: causing the display generation component to simultaneously display the first application view and the second application view in a first simultaneous display configuration of a plurality of simultaneous display configurations including a first simultaneous display configuration specifying a first arrangement of simultaneously displayed application views, a second simultaneous display configuration specifying a second arrangement of simultaneously displayed application views that differs from the first arrangement of simultaneously displayed application views, and a third simultaneous display configuration specifying a third arrangement of simultaneously displayed application views that differs from both the first arrangement of simultaneously displayed application views and the second arrangement of simultaneously displayed application views; detecting a first input beginning at a location directed toward the first application view in the first array of simultaneously displayed application views and including a first movement and a termination of the first input after the first movement is detected; in response to detecting the first movement of the first input; displaying, while the representation of the first application view is on a first portion of the display, a first visual indication indicating that when the first input is terminated, the first application view and the second application view will be displayed in the first simultaneous display configuration; displaying, while the representation of the first application view is on a second portion of the display, a second visual indication indicating that when the first input is terminated, the first application view and the second application view will be displayed in the second simultaneous display configuration; displaying, while the representation of the first application view is on a third portion of the display, a third visual indication indicating that when the first input is terminated, the first application view and the second application view will be displayed in the third simultaneous display configuration; moving the representation of the first application view on the display in accordance with the first movement of the first input; in response to detecting the end of the first input, pursuant to a determination that the first input ended while the first application view was over the first portion of the display, causing the first application view and the second application view to be displayed in the first simultaneous display configuration; pursuant to a determination that the first input ended while the first application view was on the second portion of the display, causing the first application view and the second application view to be displayed in the second simultaneous display configuration; a first application view and a second application view that are displayed in the third simultaneous display configuration in accordance with a determination that the first input ended while the first application view was on the third portion of the display;

150. 150. The computer readable storage medium of claim 149, wherein the one or more programs include instructions that, when executed by the computer system, cause the computer system to perform the method of any one of claims 79 to 102.

151. 103. A non-transitory computer-readable storage medium storing executable instructions that, when executed by an electronic device having one or more processors and a touch-sensitive display, cause the electronic device to perform the method of any one of claims 78 to 102.

152. 1. An electronic device comprising: one or more processors; A touch-sensitive display; a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing a method according to any one of claims 78 to 102; An electronic device comprising:

153. 103. An electronic device comprising one or more processors and a touch-sensitive display, the electronic device comprising means for performing the method of any one of claims 78 to 102.

154. 103. An information processing apparatus for use in an electronic device comprising one or more processors and a touch-sensitive display, the information processing apparatus comprising means for carrying out a method according to any one of claims 78 to 102.

155. 103. A graphical user interface displayed on a touch-sensitive display of an electronic device comprising one or more processors, the graphical user interface comprising a user interface displayed according to the method of any one of claims 78 to 102.

Images