SYSTEM AND METHOD FOR INTERACTING WITH MULTIPLE APPLICATIONS DISPLAYED SIMULTANEOUSLY ON AN ELECTRONIC DEVICE WITH A TOUCH-SENSITIVE DISPLAY - Patent application

Abstract

To provide a systems and method for multitasking using a touch-sensitive device.SOLUTION: A method comprises: displaying a first set of applications within a display area occupying substantially all of a touch-sensitive display; displaying a dock overlaying a first portion of the display area while displaying the first set of applications; detecting a touch on a first affordance associated with a second set of one or more applications displayed within the dock; detecting movement of the touch away from the dock; and displaying i) at least a portion of the first set of applications and (ii) at least a portion of the second set of applications within the display area occupying substantially all of the touch-sensitive display upon detecting lift-off of the touch from the touch-sensitive display while the touch is over a second portion of the display area that is different from the first portion.SELECTED DRAWING: Figure 8A

Description

[Technical field]

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

[0002] Handheld electronic devices with touch-sensitive displays are ubiquitous. Although these devices were originally designed for information consumption (e.g., web browsing) and communication (e.g., email), they 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). Although the range of new functions 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, the need for multitasking is especially acute on handheld electronic devices because handheld electronic devices have smaller screens than traditional desktop and laptop computers. 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 the keyboard and mouse of a desktop computer and the touch and gesture input of a handheld electronic device having a touch-sensitive display. Other attempted solutions require complex input sequences and menu hierarchies that are less user-friendly than those provided on a desktop or laptop computer. It is therefore 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] (A1) According to some embodiments, a method is performed in an electronic device (e.g., portable multifunction device 100, FIG. 1A) with a touch-sensitive display (e.g., touch screen 112, FIG. 1C). The method includes displaying a first set of one or more applications within a display area occupying substantially all of the touch-sensitive display. While displaying the first set of one or more applications, the method also includes (i) displaying a dock overlaying a first portion of the display area, (ii) detecting a contact on the touch-sensitive display on a first affordance displayed within the dock, the first affordance being associated with a second set of one or more applications, and (iii) detecting movement of the contact away from the dock. Upon detecting lift-off of the contact from the touch-sensitive display while the contact is on a second portion of the display area different from the first portion, the method further includes displaying (i) at least a portion of the one or more applications of the first set and (ii) at least a portion of the one or more applications of the second set within the display area occupying substantially all of the touch-sensitive display. In some cases, a user of a computing system must use inefficient and time-consuming interactions to operate two or more applications. By allowing a user to use a single simple gesture (e.g., dragging an affordance from a dock onto a main display area with one finger), the user can easily and efficiently activate a mode in which two or more applications are displayed and operated simultaneously. Enabling a user to easily and efficiently activate this mode improves usability of the device and makes the human-machine interface more efficient (e.g., by allowing a user to activate the mode using a single gesture). Additionally, this allows for sustained interaction with a touch-sensitive display that would not otherwise be possible by having to use multiple gestures to access two or more applications.

[0006] (A1.5) In some embodiments, after the contact moves within a threshold distance from an edge of the touch-sensitive display that contacts at least a portion of the one or more applications in the first set or at least a portion of the one or more applications in the second set prior to detecting lift-off of the contact, resizing the one or more applications in the first set to uncover a second portion of the display area adjacent the resized one or more applications in the first set.

[0007] (A2) In some embodiments of the method according to A1, the method includes resizing the first set of one or more applications to uncover a second portion of the display area adjacent the resized first set of one or more applications after the contact has moved at least a threshold distance away from the dock. In some cases, a user of the computing system may not recognize a change resulting from a particular interaction on the touch-sensitive display. Providing clear visual feedback (e.g., resizing the first set of one or more applications to uncover the second portion of the display area) gives the user an opportunity to preview the changes that will occur after the contact is released (or lifted off). Providing this clear visual feedback improves usability of the device and makes the human-machine interface more efficient (e.g., by allowing the user to understand the changes that will occur and not have to reverse unwanted changes). Additionally, this allows for sustained interaction with the touch-sensitive display that would not otherwise be possible due to the user having to repeatedly undo or reverse undesired changes that they could not have anticipated.

[0008] (A3) In some embodiments of the method of any one of A1.5 or A2, displaying (i) at least a portion of the one or more applications of a first set and (ii) at least a portion of the one or more applications of a second set within a display area occupying substantially all of the touch-sensitive display includes displaying at least a portion of the one or more applications of the second set within a second portion of the display area and displaying at least a portion of the one or more applications of the first set in a remaining portion of the display area adjacent to the second portion of the display area.

[0009] (A4) In some embodiments of the method according to any one of A1 to A3, the method further includes displaying a representation of the affordance in proximity to the contact until the contact moves a threshold distance away from the dock prior to detecting lift-off of the contact, and ceasing to display the representation of the affordance and displaying a thumbnail of content associated with the second application in proximity to the contact pursuant to determining that the contact has moved at least a threshold distance away from the dock. In this way, the user is provided with additional visual feedback to help the user recognize and understand the changes that will occur after the user releases (or lifts off) the contact. Providing this additional visual feedback improves the usability of the device and makes the human-machine interface more efficient (e.g., by allowing the user to better understand the changes that will occur and avoid having to reverse undesired changes). Additionally, it allows for sustained interaction with the touch-sensitive secondary display that would not otherwise be possible by the user having to repeatedly undo or reverse undesired changes that the user could not have anticipated.

[0010] (A5) In some embodiments of the method according to A4, the method further includes resizing the thumbnail to match the display size of the first or second portion when the contact is moved to the top of the first or second portion, respectively. In this way, the user is provided with additional visual feedback that helps the user recognize and understand the changes that will occur after the contact is released (or lifted off). Providing this additional visual feedback improves the usability of the device and makes the human-machine interface more efficient (e.g., by allowing the user to better understand the changes that will occur and avoid the need to reverse undesired changes). Additionally, this allows for sustained interaction with the touch-sensitive secondary display that would not otherwise be possible due to the user having to repeatedly undo or reverse undesired changes that the user could not have anticipated.

[0011] (A6) In some embodiments of the method of any one of claims A1-A5, displaying the dock includes detecting an initial contact on the touch-sensitive display and displaying the dock within a first portion of the touch-sensitive display in response to detecting movement of the initial contact in a direction generally perpendicular to a bottom portion of the touch-sensitive display. Allowing a user to activate the dock using a simple, easy-to-use, repeatable gesture helps ensure that the user interface is operated more efficiently, since the user does not have to waste time searching for application-specific affordances, but can instead quickly access the dock and use the dock to open application-specific affordances. This also helps ensure that the user has a sustained interaction with the electronic device, since the user can smoothly transition from accessing the dock to activating a split-view operating mode (as discussed in more detail below) in which the user can simultaneously interact with two different applications.

[0012] (A6.1) In some embodiments of the method of any one of A1-A4, the method includes displaying a representation of the first affordance proximate to the contact until the contact moves a threshold distance away from the dock before detecting lift-off of the contact, and displaying a user interface object surrounding the representation of the first affordance proximate to the contact pursuant to determining that the contact has moved at least the threshold distance away from the dock.

[0013] (A6.2) In some embodiments of the method described in A6.1, the user interface object has a first shape, and the method further includes modifying the user interface object to have a second shape or a third shape when the contact is moved over a top of the first portion or the second portion, respectively, before detecting lift-off of the contact, and the first shape is distinct from the second and third shapes.

[0014] (A7) In some embodiments of the method according to any one of claims A1-A6, the first set includes one first application, the second set includes one second application, the affordance is associated with the one second application, and upon detecting lift-off of the contact (e.g., while the contact is located within a threshold distance of an edge of the touch-sensitive display that is adjacent to the one first application), the first and second applications are displayed side-by-side in the display area. When the first set includes one first application and the second set includes one second application, a user of the computing system can activate a split-view mode in which the first and second applications are displayed together by simply dragging the affordance corresponding to the second application onto a second portion of the display. Providing clear visual feedback (e.g., clarifying the second portion of the display area after the contact has moved a threshold distance) gives the user an opportunity to preview the changes that will occur after the user releases (or lifts off) the contact. Providing this clear visual feedback improves usability of the device and makes the human-machine interface more efficient (e.g., by allowing the user to understand that releasing contact will activate a split-view mode involving the first and second applications.) Additionally, it allows for sustained interaction with a touch-sensitive display that would not otherwise be possible due to the user having to repeatedly undo or reverse undesired changes that the user could not have anticipated.

[0015] (A7.1) In some embodiments of the method described in A7, upon detecting lift-off of the contact while the contact is located over a first application, a second application is displayed in the display area overlaying the first application.

[0016] (A8) In some embodiments of the method according to any one of A1 to A7, the first set includes at least a first application and a second application, the second set includes one third application, and the affordance is associated with the one third application. When the first set includes the first application and the second application and the second set includes one second application, a user of the computing system can add a new application to a split view mode in which the first application and the second application are displayed together by simply dragging an affordance corresponding to the third application on the display. By providing clear visual feedback (e.g., clarifying the second portion of the display area after the contact has moved a threshold distance), the user is given the opportunity to preview the changes that will occur after the user releases (or lifts off) the contact. Additionally, this allows for sustained interaction with the touch-sensitive display that would not otherwise be possible by the user having to repeatedly undo or reverse undesired changes that the user could not have anticipated.

[0017] (A9) In some embodiments of the method according to A8, the method further includes replacing the second application with a third application on the touch-sensitive display in accordance with determining that lift-off of the contact occurred on the second application. In this manner, the user is provided with the ability to replace the second application with the third application in split view mode, thereby enabling a persistent interaction that the user can quickly and easily substitute in the new application that is viewed simultaneously with the first application.

[0018] (A9.1) In some embodiments of the method described in A9, the method further includes: upon detecting lift-off of the contact while the contact is located over a first application, a second application is displayed overlaying the first application in the display area.

[0019] (A10) In some embodiments of the method according to any one of A1 to A9, the first set includes a first group of at least two pinned applications, the second set includes a second group of at least two pinned applications, and the affordance is associated with the second group of at least two pinned applications. When the first and second sets each include a group of pinned applications, a user of the computing system can add a new group of pinned applications to the split view mode by simply dragging an affordance corresponding to the second group onto the display. By providing clear visual feedback (e.g., clarifying the second portion of the display area after the contact has moved a threshold distance), the user is given the opportunity to preview the changes that will occur after the user releases (or lifts off) the contact. Additionally, this allows for sustained interaction with the touch-sensitive display that would not otherwise be possible by the user having to repeatedly undo or reverse undesired changes that the user could not have anticipated.

[0020] (A11) In some embodiments of the method according to A10, the method further includes replacing the first group of at least two pinned applications with a second group of at least two pinned applications in accordance with a determination that contact lift-off occurred on an application of the first group. In this manner, the user is provided with the ability to quickly switch from the first group of pinned applications to the second group of pinned applications, thereby enabling a persistent interaction on the display that the user can quickly and easily substitute in a new group of pinned applications.

[0021] (A12) In some embodiments of the method according to any one of claims A1-A11, the first set of one or more applications includes an instance of the first application and the second set of one or more applications includes an additional instance of the first application, the instance and the additional instance being separate instances of the first application. If the first and second sets each include different instances of the same first application, a user of the computing system can pin two different instances of a single application next to each other. Enabling both pinning of two different instances provides the user with an improved man-machine interface (e.g., by ensuring that the user can simultaneously interact with different functions of a single application, such as, for example, editing a message in a messaging application while also copying content from different messages in that same messaging application). Additionally, this allows for sustained interaction with the touch-sensitive display that would not otherwise be possible by the user having to repeatedly undo or reverse undesired changes that the user could not have anticipated.

[0022] (A13) In yet another aspect, there is provided an electronic device including a touch-sensitive display, one or more processors, and memory storing one or more programs that, when executed by the one or more processors, cause the electronic device to perform a method described in any one of A1 to A12.

[0023] (A14) In a further aspect, an electronic device is provided, the electronic device including a touch-sensitive display and means for performing a method according to any one of A1-A12.

[0024] (A15) In yet another aspect, there is provided a non-transitory computer-readable storage medium storing executable instructions that, when executed by an electronic device with a touch-sensitive display, cause the electronic device to perform a method as recited in any one of A1-A12.

[0025] (A16) In yet another aspect, there is provided a graphical user interface on an electronic device with a touch-sensitive display, the graphical user interface including a user interface displayed according to a method described in any one of A1-A12.

[0026] (B1) According to some embodiments, a method is performed in an electronic device (e.g., portable multifunction device 100, FIG. 1A) with a touch-sensitive display (e.g., touch screen 112, FIG. 1C). The method includes displaying a first application and a second application within a display area occupying substantially all of the touch-sensitive display. While displaying the first application and the second application within the display area, the method also includes displaying an affordance near an edge of the second application and detecting a contact on the affordance moving in a direction across the touch-sensitive display. In accordance with a determination that the direction is a first direction, the method further includes resizing the first application to occupy substantially all of the display area and displaying the second application overlaying the resized first application. In accordance with a determination that the direction is a second direction substantially perpendicular to the first direction, the method includes moving the second application within the display area. In some cases, a user of a computing system must use inefficient and time-consuming interactions to operate two or more applications. Allowing a user to interact with a handle to either activate Slide Over mode or move a particular application within the display area allows a user to easily and efficiently move applications and switch between parallel view and Slide Over view. Allowing a user to easily and efficiently move applications and switch between different modes of using two or more applications simultaneously improves usability of the device and makes the human-machine interface more efficient (e.g., by allowing a user to select how to interact with two or more applications simultaneously, e.g., using parallel view or using Slide Over / overlay mode).Additionally, this enables persistent interaction with a touch-sensitive display that would not otherwise be possible due to the need to use multiple gestures to customize simultaneous interaction with two or more applications.

[0027] (B2) In some embodiments of the method according to B1, the method further includes detecting a user input in the first application while the second application is overlaid on the resized first application, and responding to the user input via the first application. Allowing the user to interact with the first application allows the user to customize how they want to simultaneously interact with two simultaneously displayed applications, even while the second application is overlaid on top of the first application. Allowing the user to customize the user experience in this way improves usability of the device and makes the human-machine interface more efficient (e.g., their customized selection allows the user to use various features more efficiently without having to make default arrangements). Additionally, this allows for persistent interaction with the touch-sensitive display that would not otherwise be possible, by forcing the user to interact with two or more applications displayed together in a default manner and without user-specific customization.

[0028] (B3) In some embodiments of the method according to B2, the method includes, in response to a request to open a third application separate from the first and second applications, after determining that the orientation is the first orientation, (i) displaying the third application in a portion of the display area previously occupied by the first application, and (ii) displaying the second application overlaying the third application. Allowing the overlaid application to remain displayed after the user opens a new application helps ensure that persistent interaction with functionality of the electronic device (e.g., functionality accessed by the user through the overlaid application that may have to be reopened if the overlaid application does not remain displayed) is maintained. The user may also avoid having to reopen functionality of the overlaid application, improving operability of the device and also making the human-machine interface operate more efficiently.

[0029] (B4) In some embodiments of the method according to any one of B1-B3, the second application is initially displayed abutting a first edge of the touch-sensitive display, and moving the second application within the display area includes (i) moving the second application in a second direction until the second application abuts a second edge, opposite the first edge, of the touch-sensitive display, and (ii) displaying the first application in a remaining portion of the display area, separate from the portion occupied by the second application, such that the first application abuts the first edge of the touch-sensitive display. Allowing a user to move an application by dragging an affordance (e.g., a handle displayed on the overlaid application) helps to allow a user to customize how the user wishes to simultaneously interact with two simultaneously displayed applications. Allowing users to customize their user experience in this manner improves usability of the device and makes the human-machine interface more efficient (e.g., the user's customized selection of where each application should be displayed allows the user to more efficiently use various features without having to perform default placement operations). In addition, this allows a user to interact with two or more applications displayed together in a default manner and without any user-specific customization, thereby enabling persistent interaction with the touch-sensitive display that would not otherwise be possible.

[0030] (B5) In some embodiments of the method according to B4, a preview of the portion occupied by the second application is made clear next to the first application before moving the second application until it abuts the second edge. In some cases, a user of a computing system may not recognize changes resulting from a particular interaction on a touch-sensitive display. Providing clear visual feedback (e.g., showing a preview of where the second application will be moved to) gives the user an opportunity to preview the changes that will occur after the user releases contact (or lifts off). Providing this clear visual feedback improves usability of the device and makes the human-machine interface more efficient (e.g., by allowing the user to understand the changes that will occur and avoid the need to reverse unnecessary changes). Additionally, it allows for sustained interaction with the touch-sensitive display that would not otherwise be possible by the user having to repeatedly undo or reverse undesired changes that the user could not have anticipated.

[0031] (B6) In some embodiments of the method according to any one of B1-B5, the first direction is a downward direction relative to an edge of the second application, and the second direction is a lateral direction generally perpendicular to the downward direction. Allowing the user to move the handle in different directions helps provide the user with an additional simple way to flexibly customize how the user wants to simultaneously interact with two simultaneously displayed applications. Allowing the user to customize their user experience in this way improves the usability of the device and makes the human-machine interface more efficient (e.g., the user's customized selection of where each application should be displayed allows the user to use various features more efficiently without having to do default placement work). In addition, this allows for persistent interaction with the touch-sensitive display that would not otherwise be possible, by forcing the user to interact with two or more applications displayed together in a default manner and without user-specific customization.

[0032] (B7) In some embodiments of the method of any one of B1-B6, the method includes detecting a user input at an edge of the second application prior to displaying the affordance, and displaying the affordance in response to detecting the user input. In this manner, the user is provided with a simple gesture that is used to activate display of the handle, thereby improving usability of the device (e.g., by ensuring that the handle is only displayed when needed by the user).

[0033] (B8) In some embodiments of the method described in B7, the user input includes contact at an edge of the second application and movement of the contact in a first direction across the touch-sensitive display. As discussed above, this provides the user with a simple gesture that can be used to activate the display of a handle, thereby improving usability of the device (e.g., by ensuring that the handle is only displayed when needed by the user).

[0034] (B8.1) Some embodiments of the method of any one of claims B1-B8 include, after resizing a first application and displaying a second application overlaid on the resized first application, detecting an additional contact on the affordance and movement of the additional contact in a third direction opposite to the first direction, and in response to detecting that the additional contact has moved a threshold distance in the third direction, ceasing to display the second application overlaid on the resized first application, and re-displaying the first application and the second application within a display area occupying substantially all of the touch-sensitive display.

[0035] (B8.2) In some embodiments of the method of any one of claims B1-B8, the method further includes, after resizing the first application and displaying the second application overlaid on the resized first application, detecting an additional contact on the affordance and movement of the additional contact in the first direction, and in response to detecting that the additional contact has moved a second threshold distance across the touch-sensitive display, shrinking content associated with the second application in accordance with the movement of the additional contact until a user interface object having a representation of the affordance corresponding to the second application is displayed.

[0036] (B8.3) In some embodiments of the method described in B8.2, in accordance with a determination that the additional contact has moved over the dock and lifted off the touch-sensitive display, dismissing the second application and displaying the first application occupying substantially all of the touch-sensitive display, and in accordance with a determination that the additional contact has moved within a threshold distance of an edge of the touch-sensitive display and lifted off the touch-sensitive display, re-displaying the first application and the second application within a display area occupying substantially all of the touch-sensitive display.

[0037] (B9) In some embodiments of the methods described in any one of B1 to B8, displaying the first and second applications within the display area includes simultaneously displaying the first and second applications side-by-side within the display area.

[0038] (B10) In yet another aspect, an electronic device is provided that includes a touch-sensitive display, one or more processors, and memory storing one or more programs that, when executed by the one or more processors, cause the electronic device to perform a method described in any one of B1 to B9.

[0039] (B11) In an additional aspect, an electronic device is provided, the electronic device including a touch-sensitive display and means for performing a method according to any one of B1-B9.

[0040] (B12) In yet another aspect, a non-transitory computer-readable storage medium is provided that stores executable instructions that, when executed by an electronic device with a touch-sensitive display, cause the electronic device to perform a method as recited in any one of B1-B9.

[0041] (B13) In another aspect, there is provided a graphical user interface on an electronic device with a touch-sensitive display, the graphical user interface including a user interface displayed according to a method described in any one of B1-B9.

[0042] (C1) According to some embodiments, a method is performed in an electronic device (e.g., portable multifunction device 100, FIG. 1A) having a touch-sensitive display (e.g., touch screen 112, FIG. 1C) and one or more processors. The method includes displaying at least two applications within a display area occupying substantially all of the touch-sensitive display. The method further includes receiving a user input corresponding to a request to display an application switcher user interface. In response to receiving the user input, the method further includes displaying an application switcher user interface on the touch-sensitive display, the application switcher user interface including respective representations of at least some applications recently used on the electronic device, each representation including a representation of a display area having the at least two applications.

[0043] (C2) In some embodiments of the method according to C1, displaying the application switcher user interface includes displaying a dock including a plurality of affordances corresponding to applications available on the electronic device. In some embodiments, the method further includes (i) detecting a contact on one of the plurality of affordances included in the dock and (ii) detecting movement of the contact towards the representation of the display area, and (iii) upon detecting lift-off of the contact on a first application of the at least two applications included in the representation of the display area, the method further includes ceasing to display the first application in the representation of the display area and instead displaying an additional application corresponding to the affordance in the representation of the display area.

[0044] (C3) In some embodiments of the methods described in any one of C1-C2, while displaying the application switcher user interface, the method further includes: (i) detecting additional user input on a first application of the at least two applications included in the representation of the display area; (ii) in response to detecting the additional user input, displaying a dismissal affordance over at least a portion of the first application; and (iii) upon detecting selection of the dismissal affordance, closing the first application and displaying updated representations of the remainder of the at least two applications other than the first application in the application switcher user interface.

[0045] (C4) In some embodiments of the method according to any one of C1 to C3, the method further includes: (i) detecting a contact on a first of the at least two applications included in the representation of the display area; (ii) detecting movement of the contact away from the representation of the display area; and (iii) upon detecting that the contact has moved to a predefined area within the application switcher user interface, ceasing to display the first application within the representation and displaying updated representations of the remaining of the at least two applications other than the first application within the application switcher user interface.

[0046] (C5) In some embodiments of the method described in C4, a dock is displayed overlaying at least a predefined area of ​​the application switcher user interface, the dock including affordances corresponding to multiple applications available on the electronic device.

[0047] (C6) In some embodiments of the methods described in any one of C1 to C5, displaying the application switcher user interface includes gradually reducing a size of the display area until it reaches a default size associated with the representation.

[0048] (C7) In some embodiments of the method of any of the preceding claims, the respective representation includes an additional representation of an additional application associated with the overlaid application, where the additional representation does not indicate the overlaid application.

[0049] (C8) In some embodiments of the method according to any of the preceding claims, displaying at least two applications in the display area comprises simultaneously displaying the at least two applications side-by-side in the display area, and displaying a representation of the display area having the at least two applications comprises simultaneously displaying the at least two applications side-by-side in the representation of the display area.

[0050] (C9) In yet another aspect, an electronic device is provided that includes a touch-sensitive display, one or more processors, and memory storing one or more programs that, when executed by the one or more processors, cause the electronic device to perform a method described in any one of C1 to C8.

[0051] (C10) In a further aspect, an electronic device is provided, the electronic device including a touch-sensitive display and means for performing a method as recited in any one of C1-C8.

[0052] (C11) In yet another aspect, a non-transitory computer-readable storage medium is provided that stores executable instructions that, when executed by an electronic device with a touch-sensitive display, cause the electronic device to perform a method as recited in any one of C1-C8.

[0053] (C12) In yet another aspect, there is provided an information processing apparatus for use in an electronic device with a touch-sensitive display, the information processing apparatus comprising means for performing a method according to any one of C1 to C8.

[0054] (C13) In another aspect, there is provided a graphical user interface on an electronic device with a touch-sensitive display, the graphical user interface including a user interface displayed according to a method described in any one of C1 to C8.

[0055] (D1) A method of activating two or more instances of the same application, according to some embodiments. For example, a first instance of a mail application (e.g., displaying an inbox) is open on one side of a screen, and a second instance of the same mail application (e.g., displaying individual email replies) is open on the other side of the screen. An instance is a distinct single occurrence of an object that typically exists during the execution time of a computer program, e.g., each time a program or application runs, it is an instance of that program. In some embodiments, the method is performed in an electronic device (e.g., portable multifunction device 100, FIG. 1A) that includes a touch-sensitive display (e.g., touch screen 112, FIG. 1C) and one or more processors. In this embodiment, first, a first instance of the application is displayed on substantially all of the touch-sensitive display. A contact is then detected on an affordance displayed in the first instance of the application. A movement of the contact is then detected across the touch-sensitive display. activating a split view operational mode of the electronic device that includes detecting lift-off of the contact after the contact moves across the touch-sensitive display and into a predetermined portion of the touch-sensitive display, simultaneously displaying: (i) a second instance of the application displayed with content associated with the affordance, separate from the first instance, and (ii) at least a portion of the first instance of the application, where the second instance and the portion of the first instance are displayed to occupy substantially all of the touch-sensitive display.

[0056] In some embodiments, the first and second instances of the application are separate executable processes running on one or more processors of the electronic device (e.g., two separate instantiations of the application both running separately on one or more processors of the electronic device). In other words, after detecting lift-off, the second instance of the application is instantiated and then displayed side-by-side with the first instance of the application, thereby allowing a user to easily / conveniently view and use content from the first instance while also interacting with the second instance.

[0057] In some cases, a user of a computing system loses access to certain features of an application after choosing to open other features within the application (e.g., a user may not be able to view a received email after selecting the option to reply to that received email). Opening multiple instances of a single application allows the user to continue viewing and using those certain features. Allowing the user to continue viewing and using those certain features improves usability of the device and makes the human-machine interface more efficient (e.g., by allowing the user to use those certain features without having to provide multiple inputs to reopen those certain features after they have been closed). Additionally, this allows for sustained interaction with a touch-sensitive display that would not otherwise be possible by having to use multiple gestures or inputs to figure out how to reopen or access those certain features after they have been closed or are no longer visible.

[0058] (D2) In some embodiments of the method described in D1, prior to activating the split view mode, the system detects at least one of: (i) the contact has moved at least a threshold distance (e.g., 1-2 centimeters) across the touch-sensitive display; and (ii) the contact has moved to a predefined portion of the touch-sensitive display. In other words, in some embodiments, the system determines whether the contact has moved at least a threshold distance (e.g., 1-2 centimeters) across the touch-sensitive display, while in other embodiments, the system determines whether the contact has moved to a predefined portion of the touch-sensitive display (e.g., the right third to half of the screen). In still other embodiments, the system determines whether either of these movements have occurred, while in other embodiments, the system determines whether both of these movements have occurred. In response to detecting that the contact has moved at least the threshold distance or to the predefined portion of the screen, (i) a first instance of the application is resized to occupy a first portion of the touch-sensitive display, and (ii) a predefined portion of the touch-sensitive display adjacent to the first portion is unmasked. In this manner, a user of the computing system is provided with a preview that uncovers the second portion of the display, providing a visual preview of what the split view mode will look like, thereby improving usability of the device since the user can make a decision regarding whether to activate the split view mode after seeing the preview, thereby ensuring that a user can discover how to activate a split view mode and ensuring that a user can preview such a mode before activating it.

[0059] (D3) In some embodiments of the method according to D2, activating the split-view mode of operation includes displaying a second instance of the application within a predefined portion of the touch-sensitive display.

[0060] (D4) In some embodiments of the method described in D1, a preview of the content associated with the affordance is displayed under the contact prior to detecting movement of the contact across the touch-sensitive display. In some embodiments, the preview is displayed only after the contact remains over the affordance for a predetermined period of time (e.g., 1 or 2 seconds). In other embodiments, the preview is displayed only after the intensity of the contact exceeds an intensity threshold (e.g., a hard or deep press).

[0061] (D5) In some embodiments of the method described in D4, the application is an email application, the affordance is a representation of a message displayed within a first instance of the email application, and the preview is displayed upon detecting that the contact has an intensity of the contact that exceeds a predefined intensity threshold.

[0062] (D6) In some embodiments of the method described in D4, the application is an email application, the affordance is a representation of a message displayed within a first instance of the email application, and the preview is displayed upon detecting that contact remains over the affordance on the touch-sensitive display for more than a predetermined time (e.g., 1, 2, or 3 seconds).

[0063] (D7) In some embodiments of the methods described in D1-D4, the application is an email application and the contact on the affordance is a contact on a link (e.g., a reply, reply all, or compose new message link) displayed within the first instance of the email application.

[0064] (D8) In yet another aspect, an electronic device is provided that includes a touch-sensitive display, one or more processors, and memory storing one or more programs that, when executed by the one or more processors, cause the electronic device to perform a method described in any one of D1 to D7.

[0065] (D9) In an additional aspect, an electronic device is provided that includes a touch-sensitive display and means for performing a method as described in any one of D1-D7.

[0066] (D10) In yet another aspect, a non-transitory computer-readable storage medium is provided that stores executable instructions that, when executed by an electronic device with a touch-sensitive display, cause the electronic device to perform a method as described in any one of D1-D7.

[0067] (D11) In another aspect, there is provided a graphical user interface on an electronic device with a touch-sensitive display, the graphical user interface including a user interface displayed according to a method described in any one of D1-D7.

[0068] (E1) According to some embodiments, a method is performed in an electronic device (e.g., portable multifunction device 100, FIG. 1A) with a touch-sensitive display (touch screen 112, FIG. 1C). The method includes displaying content on the touch-sensitive display and detecting movement of a contact in a direction generally perpendicular to an edge of the touch-sensitive display. The method also includes, upon determining that the movement of the contact satisfies a first movement-based threshold (e.g., the contact has moved beyond a first threshold distance from the edge), displaying a dock overlaying at least a portion of the content, the dock including a plurality of affordances that, when selected, cause the electronic device to open respective applications available on the electronic device. Pursuant to determining that the contact satisfies a second movement-based threshold (e.g., the contact has moved beyond a second threshold distance that is greater than the first threshold distance from the edge) while displaying the dock, the method further includes activating an application switcher user interface including respective selectable representations of at least some of the applications recently used on the electronic device. Providing a single gesture used to activate the dock and then the application switcher user interface improves usability of the device and causes the human-machine interface to operate more efficiently (e.g., because the user can make a single input to activate the dock and the application switch user interface rather than having to use multiple inefficient, time-consuming inputs to separately access the dock and then access the application switcher user interface at some later point in time).

[0069] (E1.5) In some embodiments of the method according to E1, the first and second movement-based thresholds are selected from the group consisting of a distance threshold, a velocity threshold, or an acceleration threshold.

[0070] (E2) In yet another aspect, there is provided an electronic device including a touch-sensitive display, one or more processors, and memory storing one or more programs that, when executed by the one or more processors, cause the electronic device to perform a method described in any one of E1 to E1.5.

[0071] (E3) In an additional aspect, an electronic device is provided, the electronic device including a touch-sensitive display and means for performing a method as recited in any one of E1-E1.5.

[0072] (E4) In yet another aspect, there is provided a non-transitory computer-readable storage medium storing executable instructions that, when executed by an electronic device with a touch-sensitive display, cause the electronic device to perform a method as set forth in any one of E1-E1.5.

[0073] (E5) In another aspect, there is provided a graphical user interface on an electronic device with a touch-sensitive display, the graphical user interface including a user interface displayed according to a method described in any one of E1-E1.5.

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

[0075] 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:

[0076] [Figure 1A] FIG. 1 is a high-level block diagram illustrating a computing device with a touch-sensitive display in accordance with some embodiments.

[0077] [Figure 1B] FIG. 2 is a block diagram of example components for event processing, according to some embodiments.

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

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

[0080] [Diagram 2] 1 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.

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

[0082] [Figure 4A]FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4B] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4C] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4D] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4E] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4F] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4G]FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4H] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4I] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4J] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4K] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4L] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4M]FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4N] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4O] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4P] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4Q] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4R] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4S]FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4T] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4U] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4V] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4W] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4X] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4Y]FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4Z] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AA] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AB] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AC] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4A-D] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AE]FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AF] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4A-G] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AH] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AI] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AJ] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AK]FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AL] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AM] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AN] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AO] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AP] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AQ]FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments. [Figure 4AR] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments.

[0083] [Figure 5A] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments. [Figure 5B] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments. [Figure 5C] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments. [Figure 5D]FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments. [Figure 5E] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments. [Figure 5F] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments. [Figure 5G] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments. [Figure 5H] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments. [Figure 5I]FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments. [Figure 5J] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments. [Figure 5K] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments. [Figure 5L] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments. [Figure 5M] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments. [Figure 5N]FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments. [Figure 5O] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments.

[0084] [Figure 6A] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6B] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6C] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6D] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6E]FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6F] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6G] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6H] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6I] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6J] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6K] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6L]FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6M] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6N] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6O] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6P] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments. [Figure 6Q] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate a sequence of gestures that allow for first activating a dock and then activating an application switcher user interface on the display, according to some embodiments.

[0085] [Figure 7A] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate example user interfaces and gestures for activating two or more instances of the same application. [Figure 7B] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate example user interfaces and gestures for activating two or more instances of the same application. [Figure 7C] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate example user interfaces and gestures for activating two or more instances of the same application. [Figure 7D] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate example user interfaces and gestures for activating two or more instances of the same application. [Figure 7E] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate example user interfaces and gestures for activating two or more instances of the same application. [Figure 7F] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate example user interfaces and gestures for activating two or more instances of the same application. [Figure 7G] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate example user interfaces and gestures for activating two or more instances of the same application. [Figure 7H] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate example user interfaces and gestures for activating two or more instances of the same application. [Figure 7I] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate example user interfaces and gestures for activating two or more instances of the same application. [Figure 7J] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate example user interfaces and gestures for activating two or more instances of the same application. [Figure 7K]FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate example user interfaces and gestures for activating two or more instances of the same application. [Figure 7L] FIG. 1 is a schematic diagram of a touch-sensitive display used to illustrate example user interfaces and gestures for activating two or more instances of the same application.

[0086] [Figure 8A] 1 is a flowchart representation of a method for activating a split view mode (where multiple applications are displayed and usable simultaneously) by dragging out an affordance from a dock, according to some embodiments. [Figure 8B] 1 is a flowchart representation of a method for activating a split view mode (where multiple applications are displayed and usable simultaneously) by dragging out an affordance from a dock, according to some embodiments. [Figure 8C] 1 is a flowchart representation of a method for activating a split view mode (where multiple applications are displayed and usable simultaneously) by dragging out an affordance from a dock, according to some embodiments.

[0087] [Figure 9A] 1 is a flowchart representation of a method of interacting with a single affordance to switch between split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and slide over mode (where one application is displayed overlaying another application on the display), according to some embodiments. [Figure 9B]1 is a flowchart representation of a method of interacting with a single affordance to switch between split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and slide over mode (where one application is displayed overlaying another application on the display), according to some embodiments. [Figure 9C] 1 is a flowchart representation of a method of interacting with a single affordance to switch between split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and slide over mode (where one application is displayed overlaying another application on the display), according to some embodiments.

[0088] [Figure 10A] 1 is a flowchart representation of a method of utilizing an application switcher user interface to display representations of applications pinned together, according to some embodiments. [Figure 10B] 1 is a flowchart representation of a method of utilizing an application switcher user interface to display representations of applications pinned together, according to some embodiments. [Figure 10C] 1 is a flowchart representation of a method of utilizing an application switcher user interface to display representations of applications pinned together, according to some embodiments.

[0089] [Figure 11A] 11 is a flow chart illustrating a method 1100 for activating two or more instances of the same application. [Figure 11B] 11 is a flow chart illustrating a method 1100 for activating two or more instances of the same application.

[0090] [Figure 12]1 is a flowchart representation of a method utilizing a succession gesture that allows for first activating a dock and then activating an application switcher user interface on a display. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0091] 1A-1D and 2 provide an illustration of an exemplary device. FIGS. 3A-3C show an example of a dynamic intensity threshold. FIGS. 4A-4AA are schematic diagrams of a touch-sensitive display used to illustrate a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split view mode in which simultaneous interaction with multiple applications is available), and these figures are used to illustrate the method / process shown in FIGS. 8A-8C. FIGS. 5A-5O are schematic diagrams of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display), and these figures are used to illustrate the method / process of FIGS. 9A-9B. Figures 6A-6Q are schematic diagrams of a touch-sensitive display used to illustrate a sequential gesture that allows for first activating a dock and then activating an application switcher user interface on the display, and these figures are used to illustrate the method / process of Figures 10A-10C and 12. Figures 7A-7L are schematic diagrams of a touch-sensitive display used to illustrate a user interface for simultaneously interacting with multiple instances of a single application (e.g., multiple separate executable instances of a single email application), and these figures are used to illustrate the method / process of Figures 11A-11B. Detailed Description Exemplary Devices

[0092] 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 one of ordinary skill 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.

[0093] In this specification, terms such as first, second, etc. are used in some instances to describe various elements, 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 described. Although a first contact and a second contact are both contacts, they are not the same contact.

[0094] The terminology used in the description of the various embodiments described herein is for the purpose of describing particular embodiments only and is not intended to be limiting. When used in the description of the various embodiments described 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. It should also be understood that the term "and / or" as used herein refers to and includes 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.

[0095] 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 phrase "if it is determined" or "if [a stated condition or event] is detected" is 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.

[0096] 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 that is 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 may configure the electronic device to operate) that touch input shall be detected only when the touch input is entirely within a user interface element).

[0097] 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, 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 a desktop computer with a touch-sensitive surface (e.g., touch-sensitive displays and / or touchpads).

[0098] 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.

[0099] The device typically supports a variety of applications, such as one or more of drawing applications, presentation applications, word processing applications, website creation applications, disc authoring applications, spreadsheet applications, gaming applications, telephony applications, video conferencing applications, email applications, instant messaging applications, fitness applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music playback applications, and / or digital video playback applications.

[0100] The 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 manner, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports a variety of applications with user interfaces that are intuitive and transparent to the user.

[0101] 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 "touch screen" 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 over one or more communication buses or signal lines 103.

[0102] 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 a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in 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 "down-click" or "up-click" of a physical actuator button. In some cases, a user will feel a tactile sensation such as a "down-click" or "up-click" 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 sensed by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. Such user interpretation of touch depends on the user's personal sensory perception, but there are many sensory perceptions of touch that are common to a majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an "up click," a "down click," "roughness"), unless otherwise noted, 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.

[0103] It is 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.

[0104] 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.

[0105] A peripherals 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.

[0106] 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.

[0107] The radio frequency (RF) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. The RF circuitry 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuitry 108 optionally includes well-known circuits for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and the like. The RF circuitry 108 optionally communicates by wireless communication with networks, such as the Internet, also called 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. The 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-HSPADA), 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®, and / or Wireless Fidelity (Wi-Fi)® (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11n).

[0108] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and the device 100. The audio circuit 110 receives audio data from the peripherals interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into sound waves audible to humans. The audio circuit 110 also receives an electrical signal converted from the sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data, and transmits the audio data to the peripherals interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripherals interface 118. In some embodiments, the audio circuit 110 also 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 that has both an output (e.g., one-ear or binaural headphones) and an input (e.g., a microphone).

[0109] The I / O subsystem 106 connects input / output peripherals of the device 100, such as the touch screen 112 and other input control devices 116, to a peripheral interface 118. The I / O subsystem 106 optionally includes one or more input controllers 160 for a display controller 156, a light sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and other input or control devices. The one or more input controllers 160 receive electrical signals from and send electrical signals to the other input or control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some other embodiments, the input controller(s) 160 are optionally coupled to any of (or none of) a keyboard, an infrared port, a 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 the speaker 111 and / or microphone 113. The one or more buttons optionally include a push button.

[0110] The touch-sensitive display 112 provides an input and output interface between the device and a user. The display controller 156 receives and / or transmits electrical signals from and to the touchscreen 112. The 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.

[0111] 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 breaking of contact) on touchscreen 112 and translates the detected contacts into interactions with user interface objects (e.g., one or more soft keys, 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.

[0112] Touch screen 112 optionally uses LCD (liquid crystal display), LPD (light emitting polymer display) or LED (light emitting diode) or OLED (organic light emitting diode) technology, although in other embodiments other display technologies are used. Touch screen 112 and display controller 156 optionally detect contact and any movement or interruption 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 touch screen 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®.

[0113] Touchscreen 112 optionally has a video resolution of 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 contacts 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.

[0114] 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 that is separate from touchscreen 112 or an extension of the touch-sensitive surface formed by the touchscreen.

[0115] 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., batteries, 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 the generation, management, and distribution of power within a portable device.

[0116] 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 images or video. In some embodiments, a light sensor is located on the back of device 100, opposite touch screen 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 videoconferencing while the user views other videoconferencing participants on the touch-sensitive display.

[0117] 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, electrical 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 a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touch screen 112 located on the front of device 100.

[0118] 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, when the multifunction device is placed near a user's ear (e.g., when the user is making a phone call), the proximity sensor is turned off and touch screen 112 is disabled.

[0119] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 in I / O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as 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 disposed on or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and generates a tactile output, optionally 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 disposed on the back of device 100, opposite touch-sensitive display 112, which is disposed on the front of device 100.

[0120] 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) that obtains information regarding the location and orientation (e.g., portrait or landscape) of device 100.

[0121] In some embodiments, the software components stored in memory 102 include operating system 126, communication 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 set) 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 the following: active application state, indicating which applications, if any, are currently active; display state, indicating which applications, views, or other information are occupying 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 (e.g., the device's orientation). In some embodiments, device / global internal state 157 communicates with multitasking module 180 to track applications activated in multitasking mode (also referred to as shared screen view, shared screen mode, or multitasking mode). In this manner, when device 100 is rotated from portrait to landscape display mode, multitasking module 180 can obtain multitasking state information (e.g., 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. Additional embodiments of stateful application operation in multitasking mode are described below with reference to FIGS. 43A-45C below.

[0122] Operating system 126 (e.g., an embedded operating system such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or 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.

[0123] The communications module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components that process data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE®, etc.) are adapted to couple to other devices directly or indirectly via a network (e.g., Internet, wireless LAN, etc.). In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors that are the same as, similar to, and / or compatible with the 30-pin connectors used in some embodiments of APPLE Inc.'s IPOD devices. In other embodiments, the external ports are multi-pin (e.g., 8-pin) connectors that are the same as, similar to, and / or compatible with the 8-pin connectors used in APPLE Inc.'s Lightning connectors.

[0124] Contact / motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensing devices (e.g., a touchpad or a physical click wheel). Contact / motion module 130 includes various software components that perform various operations related to detecting contact, such as determining if contact has occurred (e.g., detecting a finger down event), determining the strength of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining if 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 set 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., one 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 a touchpad.

[0125] In some embodiments, contact / motion module 130 uses a set of one or more intensity thresholds for determining whether an action has been performed by a user (e.g., for determining whether a 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 thresholds 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 hardware of the trackpad or touch-sensitive display. 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 "strength" parameter).

[0126] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or strength of detected contacts). Thus, gestures are optionally detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger down event, followed by detecting a finger up (lift off) event at the same location (or substantially the same location) as the finger down event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on a touch-sensitive surface includes detecting a finger down event, followed by detecting one or more finger drag events, and in some embodiments, then followed by detecting a finger up (lift off) event.

[0127] 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 soft keys), digital images, videos, and animations.

[0128] 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, such as from an application, along with coordinate data and other graphic characteristic data, as appropriate, and then generates screen image data for 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 so that applications can be quickly resized while in shared screen mode (resizing applications is discussed in more detail below with reference to FIGS. 6A-6J, 37A-37G, and 40A-40D).

[0129] The tactile feedback module 133 includes various software components that generate instructions used by the tactile output generator(s) 167 to generate tactile outputs at one or more locations on the device 100 in response to user interaction with the device 100.

[0130] 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).

[0131] 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 a weather widget, a local yellow pages widget, and a maps / navigation widget).

[0132] Application ("app") 136 optionally includes the following modules (or instruction sets), or a subset or superset thereof: ● a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ●Video conferencing 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 stock 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.

[0133] 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, a widget creator module for creating user created widgets 149-6, and voice duplication.

[0134] 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 a name(s) to the address book, deleting a name(s) from the address book, associating phone number(s), email address(es), address(es), or other information with a name, associating a picture with a name, 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, and the like.

[0135] Telephone module 138, 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, 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 previously mentioned, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0136] In conjunction 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, videoconferencing module 139 contains executable instructions for initiating, conducting, and terminating a videoconference between a user and one or more other participants in accordance with the user's instructions.

[0137] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact 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 conjunction with image management module 144, email client module 140 greatly facilitates the creation and sending of emails with still or video images captured by camera module 143.

[0138] In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for inputting character strings corresponding to an instant message, modifying previously inputted characters, sending the corresponding 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).

[0139] In conjunction with the RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and video and music player module 146, the 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 the workout, selecting and playing music for the workout, and displaying, storing, and transmitting workout data.

[0140] Camera module 143, in conjunction 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, contains executable instructions to capture still images or videos (including video streams) and store them in memory 102, change characteristics of the still images or videos, or delete still images or videos from memory 102.

[0141] 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 contains 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.

[0142] Browser module 147, in conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, contains executable instructions for browsing the Internet in accordance with a user's instructions, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0143] Calendar module 148, 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, contains executable instructions for creating, displaying, modifying, and storing calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with a user's instructions.

[0144] In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget 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) that is created by a user. In some embodiments, a widget includes a Hypertext Markup Language (HTML) file, a Cascading Style Sheets (CSS) file, and a JavaScript file. In some embodiments, a widget includes an Extensible Markup Language (XML) file and a JavaScript file (e.g., Yahoo! Widget).

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

[0146] In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 contains executable instructions for searching for text, music, sound, images, video, and / or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with a user's instructions.

[0147] 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 APPLE Inc. IPOD®.

[0148] 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 a user's instructions.

[0149] 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 is optionally 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 a user's instructions.

[0150] 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, online video module 155 contains instructions that enable a user to access, browse, 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) online videos in one or more file formats, such as H.264, and send and otherwise manage emails containing links to particular online videos. In some embodiments, instant messaging module 141 is used to send links to particular online videos, rather than email client module 140.

[0151] 1A , portable multifunction device 100 also includes a 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, recent display areas for applications while in multitasking mode, applications pinned to each other for display in split view / multitasking mode, etc.).

[0152] In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and contact intensity sensor(s) 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 a multitasking / split view mode (e.g., a mode in which two or more applications are displayed and active on touch screen 112 at the same time). In some embodiments, application selector 182 is a dock (e.g., dock 408 described below).

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

[0154] In conjunction 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 reduction in the 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-sized application (e.g., a location that avoids important content in the active application that will be overlaid by the reduced-sized application).

[0155] Each of the above identified modules and applications corresponds to an executable instruction set that performs one or more of the functions described above, as well as the methods described in this application (e.g., computer-implemented methods and other information processing methods described herein). The modules (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules, and 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 modules and data structures identified above. Additionally, memory 102 optionally stores additional modules and data structures not described above.

[0156] In some embodiments, device 100 is a device in which operation of a given set of functions is performed exclusively through a touchscreen and / or touchpad. Using the touchscreen and / or touchpad as the primary input control device for operation of device 100 optionally reduces the number of physical input control devices (push buttons, dials, etc.) on device 100.

[0157] The set of predetermined functions performed solely 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, a home menu, or a 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.

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

[0159] Event sorter 170 receives the event information and determines application 136-1 and application view 175 of application 136-1 to which the event information is to be delivered. 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(s) that are 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(s) is currently active, and application internal state 192 is used by event sorter 170 to determine application view 175 to which the event information is to be delivered.

[0160] In some embodiments, application internal state 192 includes additional information such as one or more of resume information used when application 136-1 resumes execution, user interface state information indicating information being displayed or ready to be displayed by application 136-1, a state queue that allows a user to return to a previous state or view of application 136-1, and a redo / undo queue of 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).

[0161] 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).

[0162] Event monitor 171 receives event information from peripherals interface 118. The event information includes information of sub-events (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information received 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.

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

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

[0165] 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.

[0166] Another aspect of a user interface associated with an application is a 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 programmatic or view hierarchy of the application. For example, the lowest view in which the touch is detected is optionally referred to as the hit view, and the set of events recognized as suitable inputs is optionally determined based at least in part on the hit view of the initial touch that initiates the touch gesture.

[0167] Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchical manner, 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 an initiating sub-event occurs (e.g., the first sub-event in a sub-event sequence that forms 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.

[0168] Active event recognizer determination module 173 determines which view or views 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-events 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.

[0169] Event dispatcher module 174 dispatches the 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 the event information obtained by each event receiver 181 in an event queue.

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

[0171] In some embodiments, application 136-1 includes one or more application views 175 and multiple event handlers 177, each including instructions for handling 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 the 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 a data updater 177-1, an object updater 177-2, a 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 include 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.

[0172] 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 an event receiver 181 and an 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).

[0173] The event receiver 181 receives event information from the event sorter 170. The event information includes information about a sub-event, e.g., information about a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information, such as a position of the sub-event. If the sub-event relates to a movement of a touch, the event information also optionally includes a speed and a 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 current orientation of the device (also called the device's attitude).

[0174] The event comparator 183 compares the event information to predefined event or sub-event definitions 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, the event comparator 183 includes an event definition 185. The event definition 185 includes definitions of events (e.g., sequences of predefined sub-events), such as, for example, event 1 (187-1) and event 2 (187-2). In some embodiments, sub-events in the event 187 include, for example, touch start, touch end, touch move, touch stop, 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 given stage on the displayed object, a first lift off (touch end) for a given stage, a second touch (touch start) for a given stage on the displayed object, and a second lift off (touch end) for a given stage. In another example, the definition for event 2 (187-2) is a drag on the displayed object. A drag includes, for example, a touch (or contact) for a given step on a displayed object, movement of the touch across the touch-sensitive display 112, and lift-off of the touch (end of touch). In some embodiments, the event also includes information regarding one or more associated event handlers 177.

[0175] In some embodiments, event definition 186 includes 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, in an application view in which three user interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 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 corresponding event handler 177, event comparator 183 uses the results of the hit test to determine which event handler 177 should be activated. For example, event comparator 183 selects the event handler associated with the sub-event and object that triggers the hit test.

[0176] 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.

[0177] If the respective event recognizer 178 determines that the sequence of sub-events does not match any event in the event definition 185, the respective event recognizer 178 enters an event disabled, event failed, or event finished state and thereafter ignores subsequent sub-events 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.

[0178] In some embodiments, corresponding event recognizers 178 include 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 or 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 a view or programmatic hierarchy.

[0179] In some embodiments, each event recognizer 178 activates an event handler 177 associated with an event when one or more particular 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 catches the flag and performs predefined processing.

[0180] In some embodiments, 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 the specified processing.

[0181] 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 by contacts module 137 or stores video files used by 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.

[0182] In some embodiments, event handler(s) 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.

[0183] 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 with an input device, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses, contact movements such as tapping, dragging, scrolling on a touchpad, optionally coordinated with single or multiple presses or holds of a keyboard, pen stylus input, device movement, verbal commands, detected eye movements, biometric input, and / or any combination thereof, are optionally utilized as inputs corresponding to sub-events that define the event to be recognized.

[0184] 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) in accordance with some embodiments. The touch-sensitive display optionally displays one or more graphics in user interface (UI) 201a. 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 the 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 a 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, upwards, and / or downwards), and / or rolling (e.g., from right to left, left to right, upwards, and / or downwards) 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 to launch 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.

[0185] 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 touch screen 112. Further details and alternative configurations of home button 204 are also provided below with reference to FIG. 5J below.

[0186] In one embodiment, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on / off and locking the device, volume control button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and external docking / charging port 124. Push button 206 is optionally used to power the device on / off by pressing the button and holding it down for a predefined period of time, to lock the device by pressing the button and releasing it before the predefined period of time has elapsed, and / or to unlock the device or initiate an unlocking process. In an alternative embodiment, device 100 also accepts voice input via microphone 113 for activating or deactivating some features. Device 100 also optionally includes one or more contact intensity sensors 165 that detect the intensity of a contact on touch screen 112 and / or one or more tactile output generators 167 that generate a tactile output to a user of device 100.

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

[0188] Although some of the following examples are described with reference to input on touch screen 112 (when the touch-sensitive surface and display are combined), 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, the 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 is to be understood that similar methods are optionally used for the other user interfaces described herein.

[0189] Furthermore, while the following examples are described primarily with reference to finger input (e.g., finger contacts, 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 with a mouse click (e.g., instead of a contact), optionally followed by movement of a cursor along the path of the swipe (e.g., instead of a contact movement). As another example, a tap gesture is optionally replaced with a mouse click (e.g., instead of a contact, optionally followed by cessation of detection of the contact) 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.

[0190] 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 an 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 of FIG. 1A, or touch screen 112) that allows direct interaction with user interface elements on the touchscreen display, a contact detected on the touchscreen acts as a "focus selector" such that when an 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 without a corresponding cursor movement or contact movement on the touchscreen display (e.g., by using a tab key or arrow keys to move focus from one button to another), and in these implementations, the focus selector moves to follow the movement of focus between different regions of the user interface. Regardless of the particular form taken by the focus selector, 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 which element of the user interface the user intends to interact with).For example, when a press 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).

[0191] 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 ​​including at least four distinct values, and more typically including 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 the 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 a 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 proxy for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the proxy measure for the force or pressure of the contact is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units that correspond to the proxy measure). In some implementations, the proxy 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 has been 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 enables users to access additional device functionality on reduced-size devices 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) that may not otherwise be readily accessible to the user.

[0192] In some embodiments, the contact / motion module 130 uses a set of one or more 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 thresholds of a particular physical actuator and can be adjusted without modifying the physical hardware of the 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 predefined thresholds without modifying the hardware of the trackpad or touchscreen display. 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 “strength” parameter).

[0193] 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 predefined number of intensity samples, i.e., a set of intensity samples collected during a predefined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) for a predefined event (e.g., after detecting a contact, before detecting lift-off of the contact, before or after detecting the start of movement of the contact, 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 a contact is optionally based on one or more of a maximum intensity of the contact, a median intensity of the contact, an average intensity of the contact, a top 10 percentile of the intensity of the contact, half the maximum intensity of the contact, 90 percentile 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 operation 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 operation, a contact having a characteristic intensity that exceeds the first intensity threshold but not exceeding the second intensity threshold would be a second operation, and a contact having a characteristic intensity that exceeds the second intensity threshold would be a third operation. In some embodiments, the comparison of the characteristic intensity to the one or more intensity thresholds is not used to determine whether to perform the first operation or the second operation, but rather to determine whether to perform one or more operations (e.g., to perform a respective option or to refrain from performing a respective operation).

[0194] 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 prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate small increases or decreases in the intensity of the swipe contact for purposes of determining the characteristic intensity.

[0195] In some embodiments, one or more predefined intensity thresholds are used to determine whether a particular input satisfies 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, IT D and I D refers to the same deep pressure intensity threshold, IT H and I Hrefers to the same intensity threshold. In some embodiments, the light pressure intensity threshold corresponds to an intensity at which the device performs an action normally 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 the action normally 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 ITO 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 among the various sets of user interface diagrams.

[0196] In some embodiments, the device's response to an input detected by the device depends on a criterion based on the contact intensity 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 a criterion that includes both the contact intensity during the input and a time-based criterion. 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 time the first intensity threshold is met. During the time period of decreased sensitivity, the second intensity threshold is increased. This temporary increase in the second intensity threshold also serves 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.

[0197] In some embodiments, one or more of the input intensity thresholds and / or corresponding outputs 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 Nos. 14 / 399,606 and 14 / 624,296, which are incorporated herein by reference in their entireties.

[0198] 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. The dynamic intensity threshold 380 is the sum of two components: a first component 374 that decays over time after a predefined 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 the 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. The 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).

[0199] FIG. 3B illustrates another dynamic intensity threshold 386 (e.g., intensity threshold I D ) is shown in FIG. 3B. Two other intensity thresholds, a first intensity threshold I H and a second intensity threshold I L In FIG. 3B, the touch input 384 crosses the first intensity threshold I before time p2. H and a second intensity threshold I L 3B, the dynamic intensity threshold 386 decays over time, with the decay occurring after a predefined delay p1 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 Immediately after or simultaneously with triggering a response associated with a lower intensity threshold, such as D This reduces the accidental triggering of responses associated with

[0200] FIG. 3C illustrates yet another dynamic intensity threshold 392 (e.g., intensity threshold I D In FIG. 3C, the intensity threshold I 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 predefined delay time p1 from when the touch input 390 is first detected. Thus, the intensity threshold I is triggered after a delay time p1 from when the touch input 390 is first detected. L The decrease in the intensity of the touch input 390 after triggering the response associated with the touch input 390 may occur when the intensity of the 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 event may be triggered.

[0201] Light pressure intensity threshold IT L From a strength below the light pressure strength threshold IT L and deep pressure intensity threshold IT D An increase in the characteristic intensity of a 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 to an intensity above the touch detection intensity threshold IT0 is sometimes referred to as a "deep press" input. L An increase in the characteristic intensity of the contact to an intensity between may be referred to as detection of 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 detection of 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.

[0202] In some embodiments described herein, one or more actions are performed in response to detecting a gesture including a respective press input or in response to detecting a respective press input performed on a respective contact (or contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some embodiments, the respective actions are performed in response to detecting an increase in intensity of the respective contact above a press input intensity threshold (e.g., the respective actions are performed on a "downstroke" of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold and a subsequent decrease in intensity of the contact below the press input intensity threshold, where the respective actions are performed in response to detecting a subsequent decrease in intensity of the respective contact below the press input threshold (e.g., the respective actions are performed on an "upstroke" of the respective press input).

[0203] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as "jitter," and the device defines or selects a hysteresis intensity threshold that has a predefined relationship to the pressure input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the pressure input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the pressure input intensity threshold). Thus, in some embodiments, the pressure input includes an increase in the intensity of each contact above the pressure input intensity threshold, followed by a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the pressure input intensity threshold, and a respective action is performed in response to detecting a subsequent decrease in the intensity of each contact below the hysteresis intensity threshold (e.g., the respective action is performed on the "upstroke" of the respective pressure input). Similarly, in some embodiments, a pressure 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 pressure 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 pressure 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).

[0204] For ease of explanation, the description of the 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 is 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. Furthermore, 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 discussed above, in some embodiments, the triggering of these responses also depends on a time-based criterion being met (e.g., a delay time has elapsed between the first intensity threshold being met and the second intensity threshold being met). User Interface and Associated Processes

[0205] Attention is now directed to embodiments of user interfaces ("UI") and associated processes that may be implemented in an electronic device with a display and a touch-sensitive surface, such as device 100.

[0206] 2 is a schematic diagram of a touch-sensitive display used to present a user interface for a menu of applications, 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 indicator(s) 202 for wireless communication(s), such as cellular and Wi-Fi signals; ●Time, ●Bluetooth indicator 205, ● Battery status indicator 206, ● A tray 203 having icons of frequently used applications, such as: o An icon 216 for the phone module 138, labeled "Phone", that optionally includes an indicator 214 showing the number of missed calls or voicemail messages; An icon 218 of the email client module 140, labeled "Mail", optionally including an indicator 210 showing 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 "Stock Prices" ○ An icon 236 for 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"; ○ Icon 242 of the fitness module 142, labeled "Fitness"; ○ Icon 244 of the Notes module 153, labeled "Notes"; ○ A settings application or module icon 246, which 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.

[0207] 2 are merely exemplary. Other labels are optionally used for the various application icons. For example, icon 242 for fitness module 142 is alternatively labeled "Fitness Support," "Workout," "Workout Support," "Exercise," "Exercise Support," or "Health." In some embodiments, the label of each application icon includes the name of the application that corresponds to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application that corresponds to that particular application icon.

[0208] 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 are optionally displayed in positions other than those described herein.

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

[0210] In this disclosure, references to a "split view mode" refer to a mode in which at least two applications are displayed simultaneously side-by-side on the display 112 and both applications can be interacted with (e.g., application 1 and a video browsing application are displayed in the split view mode of FIG. 4I). At least two applications can also be pinned to one another, referring to an association (stored in the memory of the device 100) between at least two applications that causes the two applications to open together when either of the at least two applications is launched. In some embodiments, an affordance (e.g., affordance 506, FIG. 5B) may not pin an application, but instead be used to display one of the at least two applications overlaying the other, and this overlay display mode is referred to as a slice-over display mode (e.g., the video browsing application is displayed overlaying application 1 in the slide-over mode shown in FIG. 5C). The user may further use a boundary affordance displayed within the boundary running between the at least two applications while displayed in split view mode to unpin or dismiss one of the at least two applications (e.g., by dragging the boundary affordance until it reaches an edge of the display 112 that borders a first of the at least two applications and then 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-M and related descriptive paragraphs), the entirety of which is incorporated herein by reference.

[0211] 4A-4AA are schematic diagrams of a touch-sensitive display used to illustrate an example of a user interface for interacting with multiple applications simultaneously (and gestures used to activate a split-view mode in which simultaneous interaction with multiple applications is available), according to some embodiments.

[0212] In some embodiments, an application is displayed on the touch-sensitive display, such as the exemplary map application displayed on touch-sensitive display 112 of FIG. 4A that includes a map of the United States and a search box that allows for searching for various locations using the map application. While the map application is displayed, gesture 450 is detected near an edge of touch-sensitive display 112 (e.g., the bottom edge of the touch-sensitive display relative to the viewer).

[0213] 4B, in response to detecting that gesture 450 has moved away from an edge and beyond a threshold distance (e.g., approximately one centimeter or more, but which may depend on the size of touch-sensitive display 112), dock 408 is manifested on the touch-sensitive display overlaying the map application. As used herein, a dock is a user interface element that includes affordances (e.g., system selected (based on how recently the respective affordances have been used)) or user selected affordances (selected by the user for inclusion in the dock) that, when activated, launch a corresponding function or application. As gesture 450 moves toward the opposite edge of the touch-sensitive display (e.g., upward), more of dock 408 is manifested and displayed overlaying the map application. Once gesture 450 moves at least a second threshold distance away from the edge of the touch-sensitive display (e.g., 2-4 centimeters, but may depend on the size of touch-sensitive display 112), dock 408 is presented within a predefined area of ​​the touch-sensitive display and no longer follows the movement of gesture 450. For example, as shown in FIG. 4C, after the gesture moves at least the second threshold distance away from the edge of the touch-sensitive display, dock 408 is displayed within the predefined area. In some embodiments, after gesture 450 ends (e.g., after contact is released or lifted off the touch-sensitive display and the end of gesture 450), dock 408 remains displayed within the predefined area and stationary.

[0214] 4E, application-specific affordances displayed within the dock 408 may be selected to open a respective application (e.g., an application corresponding to any application-specific affordance is selected), and application-specific affordances may also be dragged out of the dock 408 using a gesture (e.g., gesture 452, FIG. 4E). For example, in some embodiments, a simple tap on the affordance 232 launches the application associated with the affordance and displays it below the dock. Also, in some embodiments, a contact followed by a drag movement away from the dock, as shown by gesture 452, launches the application associated with the affordance and displays it below the dock.

[0215] Further, in some embodiments, as shown in FIG. 4F, using gesture 452, application-specific affordance 232 is dragged out of the dock or toward a predefined region 454 of the touch-sensitive display. In some embodiments, predefined region 454 is an area of ​​the touch-sensitive display reserved for pinning an application next to a currently displayed application (e.g., application 1, FIG. 4F). In some embodiments, pinning an application includes creating an association between at least two different applications so that the applications are then launched together. For example, when launched, one of the pinned applications is displayed within predefined region 454. As described in more detail below, dragging each application-specific affordance toward predefined region 454 launches the associated application, first displaying the application in a preview while the application-specific affordance is being dragged, and then displaying the associated application (upon lift-off of contact) within predefined region 454 while simultaneously displaying application 1. In some embodiments, displaying the associated application within the default area 454 causes Application 1 to be resized or scaled to accommodate the display of the associated application within the default area 454.

[0216] Returning to FIG. 4F, gesture 452 continues to move across touch-sensitive display 112 of FIG. 4G and moves beyond the boundaries of dock 408 (e.g., the contact associated with gesture 452 moves outside the boundaries of dock 408). In some embodiments, upon detecting that gesture 452 has moved beyond the boundaries of dock 408, application-specific affordances 232 no longer move and appear with gesture 452, but instead a preview 456 of content associated with the application associated with application-specific affordance 232 (e.g., a video browsing application and content) is displayed following gesture 452. Additionally, in some embodiments, default region 454 is articulated adjacent to the currently displayed application (e.g., Application 1, FIG. 4G).

[0217] In some embodiments, instead of displaying preview 456, user interface objects containing application-specific affordances (e.g., affordance 232) are displayed when the gesture moves beyond the boundaries of dock 408. Examples of these user interface objects are shown in Figures 4AC-AE (e.g., user interface objects 473-A and 473-B) and are described in more detail below.

[0218] As gesture 452 continues to move, as shown in Figure 4H, preview 456 and more of default area 454 are made visible adjacent to application 1. Along with making default area 454 visible, application 1 is also resized (as shown in Figures 4G-H) to occupy the remainder of touch-sensitive display 112 outside of default area 454.

[0219] FIG. 4I shows that upon detecting the end of gesture 452 (e.g., contact for the gesture is lifted off the touch-sensitive display), the video browsing application is displayed to occupy default region 454 and is now pinned next to application 1 (e.g., the two applications are now associated and will open together when either application is launched). Boundary affordance 460 is also shown in FIG. 4I and, in some embodiments, allows the user to resize the pinned application (e.g., in response to detecting contact on boundary affordance 460 and movement of the contact in a substantially right-to-left direction across the touch-sensitive display (such as gesture 464 in FIGS. 4L-4M), application 1 is reduced or scaled in size and the video application is increased or scaled in size (as shown in FIGS. 4L-4M ). Further details regarding using border affordances (or dragging borders) to resize and / or dismiss pinned applications are also provided in commonly owned U.S. patent application Ser. No. 14 / 732,618, particularly in Figures 37H-M and the related descriptive paragraphs, the entire contents of which are incorporated by reference in their entirety.

[0220] In some embodiments, the default region 454 is not articulated until the gesture (e.g., gesture 452) moves beyond a threshold located on either the left-hand or right-hand portion of the touch-sensitive display 112 (e.g., thresholds 464 and 465, FIGS. 4AB-4AE). In this manner, the user can decide whether to end the gesture on the currently displayed application (e.g., lifting gesture 481 off the currently displayed application 1, FIG. 4AH) to initiate a slide-over mode in which an overlaid application is displayed over the currently displayed application, or continue moving the gesture toward one of the thresholds 464, 465 to initiate a split-view mode in which a pinned application is displayed (e.g., as shown in FIGS. 4AE-4AF, gesture 472 moves toward left-hand threshold 465, then upon detecting lift-off of the contact associated with gesture 472, the two applications shown in FIG. 4AF are pinned next to each other). Further details regarding these features of particular embodiments are provided below with reference to Figures 4AB-4AI.

[0221] Figure 4I also shows gesture 461, which includes an initial contact near the top edge (relative to a user's perspective looking down on display 112) of display 112, followed by movement of the contact in a substantially downward direction across the touch-sensitive display. In response to detecting that the gesture has moved at least a threshold distance (e.g., one to two centimeters) in a substantially downward direction, affordance 462 (Figure 4J) is displayed overlaying the application in which gesture 461 was detected (e.g., the video application shown in Figures 4I and 4J).

[0222] 4J-4L also show gesture 471 used to move dock 408 from the touch-sensitive display while at least two applications are currently displayed side-by-side on display 112 (e.g., at least two applications are pinned / displayed next to each other in a split view mode) (gesture 471 may include an initial contact near dock 408 followed by movement of the contact in a substantially downward direction). In this manner, dock 408 may be hidden so that a user may choose to interact only with applications displayed behind dock 408. Similar to gestures used to activate the dock while a single application is displayed on display 112 (e.g., gesture 450 of FIGS. 4A-4C), gesture 450 may also be used to activate the dock while more than one application is displayed on display 112 (e.g., while application 1 is pinned next to a video application as shown in FIGS. 4N-4P).

[0223] 4Q, while multiple applications are simultaneously displayed on the touch-sensitive display 112, a gesture 466 is detected over one of the application-specific affordances displayed in the dock 408. For example, the gesture 466 includes an initial contact over the affordance 220 corresponding to a web browsing application, followed by movement of the initial contact across the touch-sensitive display 112. The gesture 466 continues to move in FIG. 4R, and the application-specific affordances move to follow the movement of the gesture 466 until the gesture 466 crosses beyond the boundary of the dock 408. In some embodiments, once it is detected that the gesture 466 has moved beyond the boundary of the dock 408, the application-specific affordances are no longer displayed beneath the gesture 466, and a preview 498 of the content associated with the web browsing application is displayed in its place (FIG. 4S).

[0224] As also shown in FIG. 4S, in some embodiments, when gesture 466 moves beyond the boundaries of dock 408, new affordances are added to the dock (e.g., affordance 492 corresponding to the pinned state of the map application and video application are displayed in the position in dock 408 previously occupied by the affordance for the web browsing application). In some other embodiments, new affordances are not added to dock 408 until the end of gesture 466 is detected (in other words, affordance 492 is not added to dock 408 until lift-off of gesture 466 is detected between FIGS. 4T-4U). In some embodiments, the user may choose to move the affordance back to the dock instead of continuing the drag gesture (or may end the gesture before reaching predefined region 454 or move the gesture away from the predefined region). In this way, the user is provided with an improved man-machine interface and the ability to engage in a sustained interaction with the device that would not otherwise be possible if an unintended action needs to be reversed.

[0225] Returning to the description of the exemplary gesture 466, in some embodiments, the preview 498 is resized depending on the application over which the gesture is currently moving. For example, as shown in FIG. 4S, while the gesture 466 is over application 1, the preview 498 has a first display size, and as shown in FIG. 4T, while the gesture 466 is over a video application, the preview 498 is resized to have a second display size different from the first display size. As shown in FIG. 4S-4T, the first display size is wider (compared to the second display size) to match the dimensions of application 1, and the second display size is narrower (compared to the first display size) to match the dimensions of the video application.

[0226] Upon detecting the end of gesture 466 (e.g., lift-off of the gesture from the touch-sensitive display while gesture 466 is on the video application), the web browsing application is then displayed within the area of ​​touch-sensitive display 112 previously occupied by the video application (FIG. 4U).

[0227] In some embodiments, while already displaying multiple applications (e.g., two pinned applications, such as application 1 and a web browsing application, FIG. 4V), a gesture (e.g., gesture 468 in FIG. 4V) may be used to drag an affordance corresponding to a pinned application out of dock 408 and onto touch-sensitive display 112. When gesture 468 crosses the boundary of dock 408, a preview of the content corresponding to the affordance is displayed (FIG. 4W), and then upon detecting liftoff of gesture 468 from touch-sensitive display 112 (FIG. 4X), the content is displayed. In some embodiments, the content is displayed to occupy substantially all of touch-sensitive display 112, and the previously displayed multiple applications are no longer displayed. In other embodiments, both the content and the multiple applications are displayed (e.g., the content is displayed above the multiple applications, thereby allowing the user to simultaneously interact with more than one set of pinned applications). In some embodiments, this feature is only available on devices with larger displays (eg, displays with a diagonal dimension of at least 9.7 inches).

[0228] In some embodiments, multiple instances of a single application may also be pinned to each other, and affordances corresponding to multiple instances of a single application (e.g., affordance 404) may also be dragged out of dock 408 using gesture 470 (Figures 4Y-4AA).

[0229] Although not depicted in FIGS. 4A-4AA, some embodiments also allow a user to drag an affordance from a dock onto a currently undisplayed overlaid application (e.g., to drag the affordance toward an edge of the touch-sensitive display to temporarily display a hidden overlaid application (an overlaid application that the user has swiped off the display)) and then drop the affordance onto the temporarily displayed overlaid application. For example, a user may drag an application-specific affordance 244 corresponding to a notes application from the dock 408 shown in FIG. 4AN toward the right-most edge of the touch-sensitive display 112, and upon reaching a threshold distance from the right-most edge, a hidden overlaid video application (hidden using gesture 485 in FIGS. 4AL-4AM) may be temporarily uncovered, and the user may then drop the dragged affordance on top of the hidden overlaid application, thereby replacing the video application with the notes application. In this manner, a user may use a simple drag gesture to replace an overlaid application that is currently not visible.

[0230] 4AB, example thresholds 464 and 465 are illustrated near the rightmost and leftmost edges of touch-sensitive display 112. In some embodiments, the thresholds are located approximately one to two centimeters away from the respective edges of display 112, and these thresholds are utilized to help determine when to uncover predefined regions of display 454 that provide an indication to the user that an application may be pinned within the predefined region. For example, as shown in FIGS. 4AB-4AF, gesture 472 is detected on application-specific affordance 232 corresponding to a video browsing application. Gesture 472 then moves beyond the boundary of dock 408 of FIG. 4A, and in response to detecting that gesture 472 has moved beyond the boundary of the dock, application-specific affordance 232 is no longer displayed beneath the contact corresponding to gesture 472, and instead, user interface object 473-A is displayed beneath the contact.

[0231] In some embodiments, user interface object 473-A has a first shape (e.g., a substantially elliptical shape with a representation of an application-specific affordance located therein), while the contact corresponding to gesture 472 does not cross beyond thresholds 464, 465 (FIG. 4AC). In some embodiments, in response to detecting that gesture 472 crosses beyond one of thresholds 464, 465 (and the contact remains beyond the threshold), predefined region 454 is uncovered and user interface object 473-B is displayed under the contact in place of user interface object 473-A (FIGS. 4AD and 4AE). In some embodiments, user interface object 473-B has a second shape (e.g., a substantially rectangular shape with a representation of an application-specific affordance located therein) that is different from the first shape of user interface object 473-A. By uncovering predefined region 454 and changing the shape of user interface object 473, a clear visual indication is provided that the user may now pin an application / activate split view mode on display 112. Providing these clear visual cues improves the man-machine interface by ensuring that new features are discoverable, and allows for sustained interaction with the display 112 that would not otherwise be possible because the user does not have to continually undo unanticipated actions.

[0232] As shown in Figures 4AE-4AF, the user can decide to end the gesture (e.g., by lifting off the contact corresponding to gesture 472 from display 112), and in response, the application corresponding to the application-specific affordance being dragged during gesture 472 (e.g., a video browsing application) is then pinned next to Application 1 on display 112 (Figure 4AF).

[0233] FIG. 4AF also illustrates an example of a gesture (e.g., gesture 477) that may be used to dismiss an application after it has been pinned. As illustrated, the example gesture 477 includes a contact followed by movement of the contact to an edge (e.g., the left-most edge of the display 112 for a user looking down on the display 112). In response to detecting that the gesture 477 has moved within a predetermined distance of the edge (e.g., within 1-2 centimeters of the edge), the pinned application is dismissed as illustrated in FIG. 4AG (and, in some embodiments, the memory of the device 100 is updated to reflect that the video application and application 1 are no longer pinned to each other). Further details regarding dismissing pinned applications using gestures are provided in co-owned U.S. Patent Application Serial No. 14 / 732,618 (e.g., FIGS. 37K-37M and associated paragraphs describing these figures). In other embodiments, detecting gesture 477 moving beyond a predetermined speed or acceleration towards an edge will reject the pinned application.

[0234] Figure 4AG also illustrates gesture 478, which may be used to activate a slide-over mode in which an application overlaying another application is displayed. For example, a contact associated with gesture 478 is initially detected on application-specific affordance 220 corresponding to a web browsing application, and in response to detecting movement of the contact beyond the boundary of dock 408, UI object 473-A is displayed with application-specific affordance 220. In Figure 4AH, lift-off of the contact from touch-sensitive display 112 is also detected on application 1 (without the contact crossing either of thresholds 464 or 465), and in response, the web browsing application overlaying application 1 is displayed (as shown in Figure 4AI).

[0235] FIG. 4AI also illustrates an embodiment in which gesture 482 is displayed moving in a substantially downward direction toward the bottom edge of display 112, and in response to detecting that the gesture has moved a predetermined distance (e.g., 1-2 centimeters) in the downward direction, then a web browsing application is pinned next to application 1 (as shown in FIG. 4AJ). In some embodiments, this downward swipe gesture for pinning an overlaid application is available in addition to gesture 518, described below with reference to FIGS. 5D-5F (while in other embodiments, the downward swipe gesture is an alternative to the upward swipe gesture of FIGS. 5D-5F ). ​​In some embodiments, the gesture must be initiated at or near the top of the overlaid application (e.g., on a displayed affordance 462 that is near the top of the overlaid application).

[0236] As shown in Figures 4AJ-4AL, in some embodiments, the user can also overlay an application on top of two pinned applications. For example, in response to detecting the end of gesture 484 covering the boundary between two pinned applications (Figure 4AK), an application overlaying the two pinned applications is displayed (e.g., a video browsing application overlaying a pinned web browsing application next to application 1 is displayed, Figure 4AL). Furthermore, in some embodiments where picture-in-picture video is available, the user can also have picture-in-picture video content displayed on top of the overlaid application on top of the two pinned applications. In other words, the picture-in-picture video is always the top layer. Picture-in-picture video features are described in more detail in commonly owned U.S. Patent Application Serial No. 14 / 732,618 (e.g., in Figures 48A-52D and the associated paragraphs describing these figures), which are incorporated by reference above in their entirety.

[0237] To allow users efficient space, in some embodiments, the user can also temporarily hide the overlaid application. For example, as shown in FIGS. 4AL-4AN, a gesture (e.g., gesture 485) can be used to swipe in on the overlaid application in a substantially left-to-right direction across touch-sensitive display 112 to temporarily hide the overlaid application. The user can then unhide the overlaid application using another gesture (e.g., gesture 486) that moves in the opposite direction to the gesture used to hide the overlaid application (e.g., gesture 486 moves in a substantially right-to-left direction across touch-sensitive display 112). FIG. 4AO shows an example of an overlaid application being unhide in response to gesture 486.

[0238] To allow a user to easily pin a currently overlaid application and efficiently and easily adjust its workspace on display 112 (which may result in an improved man-machine interface and allow a user to engage in persistent interaction with an application displayed on display 112), gestures may be provided that allow a user to easily switch an application from an overlaid state to a pinned state. For example, a contact on affordance 506 displayed with an overlaid application may be detected, which contact may then be moved in a substantially downward direction across the touch-sensitive display toward a bottom edge of touch-sensitive display 112 (e.g., gesture 487 of FIG. 4AO). In response to detecting that gesture 488 has moved at least a predetermined distance (e.g., 4-5 centimeters) across the touch-sensitive display, the overlaid application is no longer displayed, and instead, UI object 473-B is displayed below the contact associated with gesture 488. In some embodiments, a gradual shrinking of the content corresponding to the overlaid application is shown until the content is no longer displayed and only UI object 473-A remains on display 112.

[0239] In some embodiments, the predetermined distance used to determine when to display UI object 473-B is greater than the predetermined distance used to determine when to switch from an overlaid state to a pinned state in response to a downward swipe gesture. In some embodiments, a velocity or acceleration based threshold may be utilized instead of a distance based threshold, as also described below with reference to method 1200. In these embodiments, the velocity or acceleration threshold used to determine when to display UI object 473-B corresponds to a faster velocity (e.g., 8 centimeters / second) or acceleration used to determine when to switch from an overlaid state to a pinned state in response to a downward swipe gesture (e.g., 4 centimeters / second).

[0240] In some embodiments, gesture 488 then continues with the user dragging UI object 473-B across touch-sensitive display 112. As shown in FIGS. 4AP-4AQ, gesture 488 moves over application 1 and in response, the shape of UI object 473-B may then change to provide an indication to the user that the video browsing application will replace application 1 on display 112 upon contact lift-off (such that UI object 473-B becomes UI object 473-C, which has a shape distinct from the shapes of UI object 473-B and UI object 473-A discussed above).

[0241] As shown in Figures 4AP and 4AQ, when gesture 488 moves over the web browsing application and then over application 1, the content corresponding to each of these applications is blurred (as indicated by the darkening of each of the content corresponding to each of these applications in Figures 4AP and 4AQ), providing the user with another visual indication that dropping the UI object on either application will cause a change (in addition to changing the shape of UI object 473).

[0242] In some embodiments, upon detecting the end of gesture 488 (e.g., lift-off of the contact associated with gesture 488 occurs on application 1), the video browsing application replaces application 1 on display 112 and is pinned next to the web browsing application (the memory of device 100 may also be updated to reflect that the web browsing application and application 1 are no longer pinned to each other, and that the web browsing application and the video browsing application are pinned to each other). An example of this is shown in FIG. 4AR, where the video browsing application is pinned next to the web browsing application on display 112.

[0243] Allowing a user to easily pin a currently overlaid application, thereby efficiently and easily adjusting the workspace on the display 112, ensures that the man-machine interface is improved (e.g., by ensuring a consistent user experience between dragging an application from the dock and dragging an overlaid application to switch it to a pinned state) and also enables a user to engage in persistent interaction with applications displayed on the display 112 (e.g., by ensuring that the content of the pinned application is not completely obscured during the drag gesture to switch between an overlay state and a pinned state).

[0244] In some embodiments, to dismiss the video browsing application during the above-described gesture 488, the user can terminate the gesture 488 on the dock 408. In these embodiments, upon detecting the termination of the gesture 488 on the dock 408 (e.g., a lift-off of the contact associated with the gesture 488 on the dock), the overlaid video browsing application is dismissed and the split view mode including application 1 and the web browsing application remains displayed on the display 112.

[0245] In some embodiments, each of the applications installed on the device 100 (as shown in the device's memory in FIG. 1A ) may be associated with an indication as to whether they are compatible with the split view display mode. Pursuant to a determination that a particular application is not compatible with the split view display mode (e.g., by checking an indication associated with the particular application and indicating that the particular application is not compatible), no display changes are made while the application-specific affordance corresponding to the particular application is being dragged from the dock 408. Instead, dragging the application-specific affordance corresponding to the particular application and then dropping it on top of the application (or on top of a single application) displayed in the split view mode causes the particular application to occupy all of the touch-sensitive display (instead of having the particular application displayed in the split view mode or overlaying any of the applications). In some embodiments, application-specific affordances corresponding to incompatible applications (such as the particular applications used as examples herein) may not be dragged from the dock 408 at all (instead, these applications may be tapped to inform the user that these applications are not available for use in conjunction with the split view mode or the slide-over display mode).

[0246] Further discussion regarding FIGS. 4A-4AR is provided below with reference to method 800.

[0247] 5A-5O are schematic diagrams of a touch-sensitive display used to illustrate a user interface for switching between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed overlaying another application on the display) in accordance with some embodiments.

[0248] In FIG. 5A, two applications are displayed in split view mode on touch-sensitive display 112, and gesture 508 is detected near an edge of display 112, where the edge contacts a first of the two applications displayed in split view mode. The gesture may first move from a bezel surrounding display 112, across the edge of display 112, and then continue to move in a substantially downward direction (relative to a user looking down on display 112). In response to detecting that gesture 508 has moved at least a threshold distance (e.g., one to two centimeters) in a substantially downward direction, affordance 506 is displayed overlaying the first application (e.g., affordance 506 overlays a video application in FIG. 5B). The video application is also referred to interchangeably herein as a video browsing application.

[0249] As shown in FIG. 5B, gesture 509 may be performed on affordance 506, which allows a user to toggle between split-view mode and slide-over mode (which allows a user to pin and unpin an application). Gesture 509 may include an initial contact on affordance 506, followed by movement of the initial contact in a substantially downward direction over a first application (e.g., the video browsing application shown in FIG. 5B). As shown in FIG. 5C, after gesture 509 has moved at least a threshold distance (e.g., 1-2 centimeters) in a substantially downward direction, split-view mode is exited and instead slide-over mode is entered, where the first application is displayed overlaying another application (e.g., the video browsing application is displayed overlaying application 1 in FIG. 5C). In conjunction with the existing split view mode, the first application may also be unpinned from application 1 (e.g., the memory of device 100 may be updated to remove the association between the first application and application 1).

[0250] While the applications are displayed in Slide Over mode, Application 1 remains available and can respond to user input (even while a video browsing application is overlaying Application 1). For example, in response to detecting contact 510 on link 504 in Application 1, contact 510 is processed and Application 1 responds by accessing and displaying content associated with link 504 (FIG. 5D).

[0251] FIG. 5D also illustrates that gesture 511 may be used to return to split view mode and exit slide over mode. Gesture 511 may include an initial contact on affordance 506 followed by movement of the contact in a substantially upward direction toward the top edge of touch-sensitive display 112. In response to detecting that gesture 511 has moved at least a threshold distance (e.g., one to two centimeters) in a substantially upward direction, the video application is again displayed in split view mode adjacent to application 1 on touch-sensitive display 112 (as shown in FIG. 5F). The memory of device 100 may also be updated to again include an association between the video browsing application and application 1 indicating that the two applications are pinned to each other. In some embodiments, while gesture 511 is detected and moving in a substantially upward direction, a default region is articulated on the touch-sensitive display (e.g., default region 591 in FIG. 5E), the default region being the region in which the video browsing application is displayed after detecting the end of gesture 511.

[0252] FIG. 5F further illustrates that gesture 512 may be used to move the pinned video browsing application to a different location on touch-sensitive display 112. Gesture 512 may include an initial contact on affordance 506 followed by movement of the contact in a substantially lateral direction substantially parallel (e.g., within + / - 5° of parallel) toward the top edge of touch-sensitive display 112. FIG. 5G illustrates that as gesture 512 continues to move substantially lateral, the video browsing application moves in accordance with gesture 512 across the touch-sensitive display until it reaches a position opposite application 1 (e.g., as shown in FIG. 5H, the video browsing application is displayed to the left of application 1 upon detecting lift-off of gesture 512. The association between the two applications may also be updated to reflect that the video browsing application is pinned to the left of application 1.

[0253] FIG. 5H illustrates that gesture 509 can be used to switch from split view mode to slide over mode while video browsing is pinned to the left of application 1. For example, after detecting that gesture 509 has moved at least a threshold distance in a substantially downward direction (e.g., 1-2 centimeters in a substantially downward direction), split view mode is exited and the video browsing application is displayed overlaying application 1 (FIG. 5I). As also shown in FIG. 5I, gesture 517 (similar to gesture 512 described above) can be used to drag the overlaid video browsing application to a different position on touch-sensitive display 112 (as shown in FIG. 5J).

[0254] FIG. 5J also shows contact 527 on the home button 204 (either a physical hardware button that moves when pressed, a solid-state button that does not move when pressed but simulates movement by providing haptic feedback, or a button displayed on the touch-sensitive display 112 that can simulate movement by providing haptic feedback). In response to detecting contact 527 on the home button 204, the home screen is displayed (FIG. 5K). While the home screen is displayed, contact 516 (FIG. 5K) is detected on an affordance corresponding to a camera application, and in response, the camera application is opened with a video browsing application overlaid on top (FIG. 5L). In this manner, the user can have overlaid applications displayed with applications launched (from the home screen or application switcher user interface) such that they can have a sustained and uninterrupted interaction with the overlaid applications while also changing the application displayed behind them.

[0255] FIG. 5L also shows that the gesture 518 used to drag an affordance from the dock 408 can be used to switch what application is overlaid (e.g., while the gesture 518 is on an overlaid video browsing application, to switch from the video browsing application to a web browsing application after the gesture 518 ends (FIGS. 5M-5O)).

[0256] Further discussion regarding FIGS. 5A-5O is provided below with reference to method 900.

[0257] Attention is now directed to Figures 6A-6Q, which are schematic diagrams of a touch-sensitive display used to illustrate a successive gesture that allows for first activating a dock and then activating an application switcher user interface on the display, in accordance with some embodiments.

[0258] As shown in FIG. 6A, a first application (e.g., application 1) is displayed adjacent to (or, in other words, in side-by-side / split view mode) a second application (e.g., application 2 or a video application). Application 1 and the video application are displayed within display area 601a that occupies substantially all available display area of ​​touchscreen 112 of portable multifunction device 100. While displaying the side-by-side views, device 100 receives a user input, e.g., a substantially upward drag, swipe, or sliding gesture 602, on touchscreen 112 of portable multifunction device 100. In response to receiving user input 602, the device gradually displays dock 408 from the bottom edge of touchscreen 112, as shown in FIG. 6B. In some embodiments, the dock 408, which overlays a portion of the display area 601a, includes affordances corresponding to applications available on the device 100, such as a phone affordance corresponding to a phone application, a mail affordance corresponding to a mail application, a browser affordance corresponding to a web browsing application, and a note affordance corresponding to a note application available on the device 100. In some embodiments, after the gesture 602 moves a first threshold distance (e.g., 1-2 centimeters) across the display 112, the dock 408 begins to follow the gesture 602 as it moves across the display 112. Then, in some embodiments, after the gesture 602 moves a second threshold distance (e.g., 2-4 centimeters in total, or another 1-2 centimeters beyond the first threshold distance), the dock 408 remains in a static position and no longer follows the gesture 602 (FIG. 6C). If gesture 602 continues to move beyond a second threshold distance, the currently displayed application (e.g., a split view mode between application 1 and a video application) begins to scale down in size and an application switcher user interface is displayed (Figure 6D).In some embodiments, once the gesture has traveled at least a third threshold distance (e.g., a total of 3-6 centimeters, or an additional 1-2 centimeters beyond the second threshold distance), the application switcher user interface is displayed with the representations 604 displayed in their respective chronological order (as discussed in more detail below) (FIG. 6E). In some embodiments, movement between these threshold distances occurs without interrupting contact with the surface of the screen, e.g., without any lift-off or release of contact.

[0259] 6D illustrates an application switcher user interface that is displayed on touch screen 112 in response to receiving user input 602. In some embodiments, the application switcher user interface displays representations of at least some of the applications that were recently used on portable multifunction device 100, such as application 3 (606), application 4 (608), application 5 (610), and application 6 (612). In some embodiments, the application switcher user interface also includes a representation 604 of display area 601a shown in FIG.

[0260] In some embodiments, as shown in FIG. 6D, the display area 601a previously shown in FIG. 6A is animated to gradually decrease in size or scale to fit within the displayed representation 604. Representation 604 includes a scaled-down side-by-side view of application 1 and a video application. In some embodiments, the representations of the most recently used applications 606-612 are chronologically ordered. For example, application 3 (606) was used more recently than application 4 (608) and is therefore displayed to the right of application 4 (608). Similarly, application 5 (610) was used more recently than application 6 (612) and is therefore displayed above application 6. In some embodiments, the application switcher user interface also includes a control center 614 that includes commonly used system controls such as volume control, brightness control, etc.

[0261] Figure 6E shows that the shrinking or scaling of representation 604 continues until representation 604 reaches a predetermined size, e.g., the same size as representations 606-612. Figure 6E further shows that representations of recently used applications 606-612 may be rearranged to make room for representation 604, e.g., by moving representations 606-612 to the left and / or to a different row. Representations 604 representing application 1 and application 2 (video applications) are positioned in front of representations 606-612 because application 1 and application 2 are the most recently used applications.

[0262] 6F-6G illustrate switching between applications displayed in an application switcher interface, according to some embodiments. While displaying an application switcher interface including a dock 408 and representations 604 corresponding to application 1 and application 2, device 100 detects contact 603 on a web browsing affordance in dock 408, followed by gesture 603 (e.g., a continuous movement of the contact on touch screen 112 to representation 604 displayed in the display area). In some embodiments, the gesture is performed without detecting a release or lift-off between detecting the contact and the movement. Gesture 603 ends when the user lifts off the contact on application 2 in representation 604. Upon detecting the lift-off, device 100 replaces application 2 in representation 604 with a representation of the web browsing application, as shown in FIG. 6G. Replacement representation 616 includes a representation of application 1 and a representation of the web browsing application in a side-by-side view. In some embodiments, these two applications are pinned to each other until they are rejected from the pinned relationship, as described below.

[0263] 6H-6M illustrate dismissing an application from within an application switcher user interface, according to some embodiments. In some embodiments, while displaying the application switcher user interface, device 100 detects user input, e.g., contact 618a on application 2 in representation 604, as shown in FIG.

[0264] In some embodiments, as shown in FIG. 6I, the system determines whether the input is of a predefined type, such as a non-tap selection 618b, e.g., a press and sustained contact that lasts longer than a predefined length of time, or a contact having an intensity above a threshold intensity (e.g., a deep / hard press as described in more detail above). In response to detecting the predefined type of input 618b, the device 100 displays a dismiss affordance 620 over application 2 in the representation 604. Thereafter, upon detecting a selection 622 of the dismiss affordance 620 (e.g., upon tapping the dismiss affordance 620), as shown in FIG. 6J, the device 100 closes application 2 and updates the representation 604 to no longer include application 2, as shown in FIG. 6K. In some embodiments, representations of more than two applications pinned to each other may also be interacted with to dismiss and / or replace more than two applications.

[0265] In another embodiment, the input is a drag gesture 618c, as shown in FIGURE 6L. The drag gesture 626 includes a contact on application 2 in the representation 604, followed by movement of the contact away from the representation 604. In some embodiments, the drag gesture 626 includes an initial contact that lasts longer than a predefined length of time (e.g., press and hold). In some embodiments, the initial contact is substantially stationary. In response to detecting the contact 626 moving into a predefined area (e.g., dock 408) or moving beyond a predefined distance from the representation 604, the device 100 closes application 2 and updates the representation 604 to no longer include application 2, as shown in FIGURE 6M.

[0266] 6N-6Q show gestures for activating an application switcher user interface received via a slide over display mode in some embodiments, where a representation of the slide over display mode is not included within the application switcher user interface.

[0267] In FIG. 6N, application 1 is displayed in display area 601b while application 2 is displayed as an overlay in display area 601b. In some embodiments, the overlaid display of application 2 includes a handle, e.g., affordance 628, near the top edge of application 2. Display area 601b occupies substantially all of the available display area of ​​touchscreen 112. FIG. 6O illustrates that while displaying the overlaid view, device 100 receives user input on touchscreen 112 of portable multifunction device 100, e.g., a substantially drag, swipe, or sliding gesture 602 (e.g., an upward drag) away from the edge of the screen. In response to receiving user input 602, the device gradually displays dock 408 from the bottom edge of touchscreen 112, which overlays display area 601b (e.g., at the bottom edge of touchscreen 112). When positioned, the dock 408 no longer moves even if the gesture continues, and the dock remains in a stationary position. However, if the continuous gesture 602 continues to move further off the edge (e.g., upwards) after the dock 408 has stopped moving, an application switcher interface is displayed, as shown in FIG. 6P.

[0268] As the gesture continues, the display area 601b shown in FIG. 6N is gradually reduced in size or scale to fit within the representation 634. Representation 634 includes a representation of application 1 but does not include the overlaid representation of application 2. FIG. 6Q shows that the shrinking of representation 634 continues until it is the same size as the representations of recently used applications 636-642, which may be repositioned to make room for representation 634. In some embodiments, three different threshold distances (e.g., the first, second, and third threshold distances described above with reference to FIGS. 6A-6E) are used to determine when to begin unfolding the dock 408, when the dock 408 should be placed in its resting position, and when the application switcher user interface should be displayed.

[0269] Further discussion regarding FIGS. 6A-6Q is provided below with reference to methods 1000 and 1200.

[0270] 7A-7L are schematic diagrams of touch-sensitive displays used to illustrate exemplary user interfaces and gestures for activating two or more instances of the same application. An instance is a single occurrence of a distinct object that typically exists during the execution of a computer program, e.g., each time a program or application that is an instance of that program is executed.

[0271] In some embodiments, the method for activating two or more instances of the same application is performed on an electronic device (e.g., portable multifunction device 100, FIG. 1A) with a touch-sensitive display (e.g., touch screen 112) and one or more processors (122, FIG. 1A). For example, FIG. 7A illustrates a first instance of an application 702a executing on electronic device 100 with touch-sensitive display 112 and one or more processors (122, FIG. 1A). As shown, the first instance of the application is displayed on substantially all of touch-sensitive display 112.

[0272] In this example, application 702a is an email, e-mail, or mail application, but in other embodiments, the application can be any application that is capable of running more than one instance on electronic device 100 and displaying more than one instance of the application on touch screen 112 (e.g., any of the applications described above with reference to FIGS. 1A and 2).

[0273] 7A, the inbox of a first instance of a mail application is displayed on touch screen 112. In this example, the displayed inbox includes a left panel and a right panel. The left panel lists individual emails received by the mail application, and the right panel shows one of the received emails in more detail.

[0274] 7B shows a user input (e.g., a contact such as a tap or press) 704 on touch screen 112. Here, the user input or contact 704 is on or above an arrow affordance used to reply, forward, or print the opened email shown in the right panel. Upon contact with touch screen 112 (also referred to herein as a touch-sensitive display or touch-sensitive display screen) at the arrow affordance, a system including touch screen 112 and a processor (122 in FIG. 1A) determines that the user selected the arrow affordance and displays affordances for replying to the email, forwarding the email, or printing the email. In this example, these affordances are displayed in a pop-up window that overlays the opened email, as shown in FIG. 7B.

[0275] 7C illustrates another user input (e.g., touch or gesture) 706 on touch screen 112. Here, the user input (e.g., touch or gesture) 706 is on or above a reply affordance used to reply to an opened email. In some embodiments, the user input (e.g., touch or gesture) 706 is not a simple tap or touch, but instead is a deep or strong press (e.g., a press with a contact that exceeds a predetermined contact force or intensity - see the discussion associated with Figures 3A-3C) or a press and sustain for longer than a predetermined length of time (e.g., 1 second).

[0276] For example, a system including touch screen 112, a processor (122 in FIG. 1A), a contact intensity sensor (165 in FIG. 1), and / or an intensity sensor controller (159 in FIG. 1) determines whether the user input (e.g., a contact or gesture) 706 is of a predefined type (e.g., a deep press or a press and hold) on the reply affordance. Upon determining that the user input 706 is of a predefined type on the reply affordance, touch screen 112 displays a preview 763 of a new email that replies to the previous email, as shown in FIG. 7D. In this example, the preview 763 of the new email that replies to the previous email is displayed in a pop-up window that overlays the previous email.

[0277] FIG. 7E continues with the example shown in FIG. 7D. Here, after detecting that user input 706 is of a predetermined type (e.g., a deep press or a press and hold), without detecting lift-off of the input or contact with a reply affordance, touch screen 112 and processor (122 in FIG. 1A) detect a gesture of a predetermined type 706. In some embodiments, the gesture of a predetermined type is movement of the contact up to (or greater than) a particular distance (e.g., 1-2 centimeters). In other embodiments, the gesture of a predetermined type is movement of the contact to a predefined second portion of the touch screen (e.g., from the right third to the half of the screen). This gesture or movement of contact 706 is indicated by an arrow extending from contact 706 in FIG. 7D.

[0278] Upon detecting that the gesture 706 is of a predetermined type, the first instance of the application is resized to a first portion of the touchscreen display, as shown in FIG. 7E. In this example shown in FIG. 7E, the first portion is the left half of the touchscreen. At the same time, the remainder of the touchscreen (e.g., the entire touchscreen area minus the first portion) becomes emptied of content other than the preview 763, providing an indication to the user that if the user were to release contact with the screen or lift off, the area is where a new email is replying to a previous email (as indicated by the preview 763). In some embodiments, this remainder of the touchscreen is the second portion 762 described above.

[0279] If the user does not want to open a new email replying to the previous email, for example in split view mode next to the first instance of the mail application, the user can move the contact back over the reply affordance and lift off or release the contact from the surface of the touchscreen. However, if the user lifts off or releases contact with the touchscreen after a certain type of gesture or contact (see FIG. 7D above), the new email replying to the previous email is displayed in the second portion 762 of the touchscreen, as shown in FIG. 7F or FIG. 7G. In some embodiments, upon detecting the lift off or release of the contact, the preview 763 (FIG. 7E) expands to occupy the entire second portion 762 (FIG. 7E). In some embodiments, this expansion is animated.

[0280] In some embodiments, when the preview 763 (FIG. 7E) is expanded to occupy the entire second portion 762, a first instance of a mail application is displayed in the first portion, as shown in FIG. 7F. In other embodiments, when the preview 763 (FIG. 7E) is expanded to occupy the entire second portion 762, a previous email (to which the new email displayed in the second portion is replied) is displayed in the first portion, as shown in FIG. 7G. In some embodiments associated with FIG. 7G, the preview 763 (FIG. 7E) is expanded to occupy the entire second portion 762, but the first instance of the mail application slides off the screen (e.g., to the left) while the previous email slides into the first portion (e.g., from the right) in an animated sequence.

[0281] 7H illustrates another example of a user interface and gestures for activating two or more instances of the same application, here a mail application. Similar to FIG. 7A, a first instance of the application is displayed occupying substantially all of the viewable area of ​​the touch screen. As shown, user input or contact 712 is detected at a selectable affordance, here an individual email in a list of received emails displayed in an inbox.

[0282] For example, a system including a touch screen 112, a processor (122 in FIG. 1A), a contact intensity sensor (165 in FIG. 1), and / or an intensity sensor controller (159 in FIG. 1) may determine whether a user input (e.g., a touch or gesture) 712 corresponds to a predetermined type (e.g., a deep press, or a press and hold; see the discussion incorporated herein above) on a reply affordance. If the user input 712 is of a predetermined type on the affordance, the touch screen 112 displays a preview 765 of the new instance of the application (here, an email replying to the selected email in the inbox), as shown in FIG. 7I. In this example, the preview 765 is displayed in a pop-up window overlaying the first instance of the application (e.g., a mail application).

[0283] As shown in FIG. 7I, after not detecting lift-off of the input or contact 712 and detecting that the user input 712 is of a predetermined type, a system including, for example, touch screen 112 and a processor (122 in FIG. 1A) detects a gesture 712 of a predetermined type. In some embodiments, the gesture of a predetermined type is a movement of the contact up to (or greater than) a certain distance (e.g., 1-2 centimeters). In other embodiments, the gesture of a predetermined type is a movement to a predefined second portion of the touch screen (e.g., the right 1 / 3 of the screen). This gesture or movement of the contact 706 is indicated by an arrow in FIG. 7I.

[0284] Upon detecting that the gesture 712 is of a predetermined type, a first instance of the application (e.g., a mail application displaying an inbox) is resized into a first portion of the touchscreen display, as shown in FIG. 7J. In this example shown in FIG. 7J, the first portion is the left half of the touchscreen. At the same time, the remainder of the touchscreen (e.g., the entire touchscreen area minus the first portion) is emptied of content other than the preview 765, providing the user with a visual indication of the area that will be completely occupied by the new reply email (as shown by the preview 765) if the user lifts off contact with the screen. In some embodiments, this remainder of the touchscreen is the second portion 764 described above.

[0285] If the user does not have the new reply email open in split view mode next to the first instance of the mail application, the user can move the contact back to where the contact originated and lift off or release the contact from the surface of the touchscreen. However, if the user lifts off or releases contact with the touchscreen after a certain type of gesture or contact (see FIG. 7I above), a new email replying to the previous email is displayed in the second portion 762 of the touchscreen, as shown in FIG. 7K. In some embodiments, upon detecting the lift off or release of the contact, the preview 765 (FIG. 7J) expands to occupy the entire second portion 764 (FIG. 7J). In some embodiments, this expansion is animated.

[0286] In some embodiments, when the preview 765 (FIG. 7J) is expanded to occupy the entire second portion 764, a first instance of a mail application is displayed in the first portion, as shown in FIG. 7K. In other embodiments, when the preview 765 (FIG. 7J) is expanded to occupy the entire second portion 764, the previous email (to which the new email shown in the first portion is replied) is displayed in the first portion, as shown in FIG. 7L. In some embodiments associated with FIG. 7L, while the preview 765 (FIG. 7J) is expanded to occupy the entire second portion 764, the first instance of the mail application is slid off the screen (e.g., to the left) while the previous email is slid into the first portion (e.g., from the right) in an animated sequence.

[0287] 7A-7G and 7H-7K, a second instance of an application (e.g., an email reply in a mail application) can be opened adjacent to a first instance of the same application (e.g., displaying the inbox of a mail application) side-by-side on the touch screen in split screen mode. Further embodiments display multiple applications with multiple instances of the same application side-by-side in split view mode, although other embodiments are used to display more than two instances of an application side-by-side in split view mode.

[0288] In some embodiments, all displayed combinations of applications, instances of applications, or combinations of applications and multiple instances of applications are displayed such that they occupy substantially the entire viewable area of ​​the touchscreen.

[0289] In some embodiments, as shown in Figures 7F, 7G, 7K, and 7L, a boundary affordance 710 is displayed between two displayed instances of an application, e.g., between a first portion and a second portion. This boundary affordance can be used to drag the boundary between the two instances, e.g., to the left or right. Dragging the boundary affordance 710 resizes each instance of the application, and when lift-off occurs, lift-off maintains each instance at its respective size. Further details can be found in co-owned U.S. Patent Application Serial No. 14 / 732,618 (e.g., in Figures 37H-M and associated paragraphs describing these figures).

[0290] In some embodiments, the first and second instances of the application are separate executable processes executing in separate executable processes executing on one or more processors (122 in FIG. 1A) of the electronic device (e.g., two separate instantiations of the application running separately on one or more processors of the electronic device).

[0291] In some instances, a user of a computing system loses access to certain features of an application after selecting to open other features within the application (e.g., a user may be unable to view a received email after selecting an option to reply to that received email). Opening multiple instances of a single application allows the user to continue to view and use these particular features. Allowing a user to continue to view and use these particular features improves usability of the device and makes the human-machine interface more efficient (e.g., by allowing a user to use these particular features without having to provide multiple inputs to reopen these particular features after they have been closed). Furthermore, this allows persistent interaction with a touch-sensitive display that would not otherwise be possible by having to use multiple gestures or inputs to understand how to reopen or access these particular features after they have been closed and are no longer displayed.

[0292] Further discussion regarding FIGS. 7A-7L is provided below with reference to method 1100.

[0293] 8A-8C are flow chart diagrams of a method for activating a split view mode (where multiple applications are displayed and available for use simultaneously) by dragging an affordance out of a dock, according to some embodiments. FIGS. 4A-4AA are used to illustrate the methods and / or processes of FIGS. 8A-8C. Although some of the examples below are described with reference to input on a touch-sensitive display (combining a touch-sensitive surface and display), in some embodiments, the device detects input on a touch-sensitive surface 195 that is separate from display 194, as shown in FIG. 1D.

[0294] In some embodiments, method 800 is performed by an electronic device (e.g., portable multifunction device 100, FIG. 1A, and / or one or more components of the electronic device (e.g., I / O subsystem 106, operating system 126, etc.). In some embodiments, method 800 is governed by instructions stored on a non-transitory computer-readable storage medium and executed by one or more processors of the device, such as one or more processors 122 of device 100 (FIG. 1A). For ease of explanation, method 800 is described below as being performed by device 100. In some embodiments, with reference to FIG. 1A, the operations of method 800 are performed at least in part by or use a multitasking module (e.g., multitasking module 180) and its components, a contact / motion module (e.g., contact / motion module 130), a graphics module (e.g., graphics module 132), and a touch-sensitive display (e.g., touch-sensitive display system 112). Some operations of method 2200 are optionally combined and / or the order of some operations is optionally changed.

[0295] As described below, method 800 provides an intuitive way to activate a split view mode using gestures at a dock and then interact with applications displayed in split view mode on a touch-sensitive display. This method reduces the number of inputs required from a user to activate a split view mode (e.g., a user need only make a simple drag gesture instead of performing multiple inputs), thereby ensuring extended battery life of an electronic device implementing method 800 since less power is required to process a smaller number of inputs (and this savings is realized over time as users become increasingly accustomed to this more intuitive and simple gesture). As described in more detail below, the operations of method 800 help to ensure that users engage in sustained interactions (e.g., the operations of method 800 do not require frequent undo behaviors that interrupt their interactions with their devices), and the operations of method 800 help to create a more efficient human-machine interface.

[0296] In some embodiments, a device configured to perform method 800 first displays (802) a first set of one or more applications in a display area that occupies substantially all of a touch-sensitive display. For example, the first set of one or more applications may include a single application (e.g., a maps application as shown in FIG. 4A) that occupies substantially all of touch-sensitive display 112, or, as shown in FIG. 4I, the first set of one or more applications may include two or more applications (e.g., application 1 on the left portion of display 112 and a video browsing application on the right portion of display 112, where these two applications are displayed together in a split view mode in FIG. 4I such that the combination of the two applications occupies substantially all of the touch-sensitive display).

[0297] While displaying the first set of one or more applications (804), the device displays a dock (e.g., dock 408, FIG. 4A) overlaying a first portion of the display area (806). Displaying the dock may include displaying the dock within the first portion of the touch-sensitive display in response to detecting an initial contact on the touch-sensitive display and detecting movement of the initial contact in a direction approximately perpendicular (e.g., within + / - 5 degrees of the perpendicular) to a bottom edge of the touch-sensitive display (808). In other words, the dock is activated by dragging in a substantially upward direction, as shown in gesture 450 in FIGS. 4A-4C and described in more detail below with reference to method 1000.

[0298] In some embodiments, a dock (e.g., dock 408, FIG. 4A) is a user interface object that includes multiple affordances, each corresponding to a respective set of one or more applications. The respective set of one or more applications may include a single application (e.g., affordance 220, FIG. 4C, corresponding to a web browsing application) or multiple applications (e.g., multiple applications displayed / pinned to each other in a split view mode, such as affordance 492 shown in FIG. 4S, corresponding to a maps application pinned next to a video browsing application). In some embodiments, the dock includes two different sets of affordances, a first set being default affordances (e.g., affordances corresponding to phone and mail applications to the left of a divider displayed within the dock) and a second set being recently used affordances (e.g., affordances corresponding to web browsing and a video browsing application to the right of the divider). In some embodiments, the dock includes a predetermined number (eg, 2, 3, 4, or 5) of recently used applications in the second set of recently used affordances.

[0299] The device then detects (810) a contact on the touch-sensitive display over a first affordance displayed in the dock (distinct from the initial contact used to activate the dock), and the first affordance is associated with a second set of one or more applications. For example, as shown in FIG. 4E, an exemplary contact associated with gesture 452 is received over affordance 232, which corresponds to a video browsing application. As another example, as shown in FIG. 4V, another exemplary contact associated with gesture 468 is received over affordance 468, which is associated with a split view mode, where a maps application is displayed adjacent to a messaging application and a web browsing application is displayed in a side-by-side view occupying substantially all of the touch-sensitive display.

[0300] Movement of the contact away from the dock is then detected 812. In some embodiments, the movement is continuous movement that is detected without detecting lift-off of the contact from the touch-sensitive display.

[0301] In some embodiments, representations of the affordances are displayed (814) in close proximity to the contacts until the contacts move a threshold distance away from the dock (e.g., 1-2 centimeters) before detecting any lift-off of the contacts. For example, representations of the affordances are displayed within very close proximity (e.g., 1px or 2px) of the contact or directly underneath the contact so that the user can see the representations of the affordances moving across the touch-sensitive display while moving the contact (as shown in FIGS. 4E-4F, affordances 232 are shown to follow the contacts associated with gesture 452 as gesture 452 moves away from dock 408).

[0302] Pursuant to determining that the contact has moved at least a threshold distance away from the dock, the device ceases displaying the representation of the affordance and displays a thumbnail of the content associated with the second application in proximity to the contact (e.g., when the contact moves beyond the threshold distance away from the boundary surrounding the dock, a preview / thumbnail 456 is shown beneath the contact). The thumbnail of the content corresponds to a miniaturized preview of the content associated with the second application, the miniaturized preview being displayed within the second application when the second application is opened, and the miniaturized preview includes the content displayed at approximately 1 / 5-1 / 10 of its size when the second application is opened. In this manner, the user is provided with additional visual feedback to aid in recognizing and understanding the changes that occur after the contact is released (or lifted off). Providing this additional visual feedback enhances usability of the device (e.g., by allowing the user to better understand the changes that occur and avoid having to reverse unnecessary changes) and makes the human-machine interface more efficient. In addition, this allows for sustained interaction with the touch-sensitive secondary display that would not be possible except by repeatedly undoing or reversing undesirable changes that the user could not have anticipated.

[0303] In some embodiments, the device also resizes the thumbnail to match the display size of the portion of the touch-sensitive display on which the contact is located. For example, preview 498 (FIG. 4S) may have a first display size while the contact associated with gesture 466 is over a first portion of display 112 on which application 1 is displayed. And preview 498 may have a second display size, different from the first display size, while the contact associated with gesture 466 is over a second portion of display 112 on which a video browsing application is displayed. In this manner, the user is provided with additional visual feedback to help them recognize and understand the changes that occur after the contact is released (or lifted off). Providing this additional visual feedback improves the usability of the device (e.g., by allowing the user to better understand the changes that occur and avoid having to reverse unnecessary changes) and makes the human-machine interface more efficient. Additionally, this allows for sustained interaction with the touch-sensitive secondary display that would not be possible otherwise than by repeatedly undoing or undoing undesired changes that the user could not have anticipated.

[0304] In some embodiments, instead of providing a thumbnail of the content, a user interface object (e.g., UI objects 473-A, 473-B, and / or 473-C) is displayed that contains a representation of the application-specific affordance being dragged. The features discussed above with respect to the use of these thumbnails also apply to embodiments in which user interface objects are provided instead of thumbnails. Examples of the use of user interface objects are shown in Figures 4AB-AE, 4AG-AH, 4AJ-AK, and 4AO-AQ, and descriptions of these examples are also provided above.

[0305] Thus, in some embodiments, method operation 814 may be replaced (or a new method operation may be added as an alternative to method operation 814) by an operation including displaying a representation of the first affordance proximate to the contact until the contact moves a threshold distance away from the dock, and displaying a user interface object surrounding the representation of the first affordance proximate to the contact pursuant to determining that the contact has moved at least a threshold distance away from the dock. For example, in Figures 4AB-4AC, video browsing affordance 232 is surrounded by user interface object 473-A (whose shape may change as the contact moves over the first and second portions, such that the UI object then has a shape substantially similar to that shown for UI objects 473-B and 473-C in Figures 4AP and 4AQ, respectively).

[0306] Upon detecting a lift-off of the contact from the touch-sensitive display while the contact is on a second portion of the display area that is different from the first portion (e.g., a lift-off of the contact associated with gesture 452 during FIGS. 4H-4I or a lift-off of the contact associated with gesture 466 during FIGS. 4T-4U), then the device (simultaneously) displays (818) (i) at least a portion of the one or more applications of the first set and (ii) at least a portion of the one or more applications of the second set within a display area occupying substantially all of the touch-sensitive display. In some embodiments, the first portion of the display area is a portion used to display one or more applications of the first set (e.g., application 1 of FIG. 4E), and the second portion of the display area is a portion of the display area that is available for displaying one or more affordances of the second set (e.g., default area 454, FIG. 4F is available for displaying one or more applications of the second set upon detecting a lift-off of the contact).

[0307] In some examples, a user of a computing system must use inefficient and time-consuming interactions to operate two or more applications. By allowing a user to use a single and simple gesture (e.g., using a single finger to drag an affordance from a dock onto a main display area, as detailed above with respect to at least operations 804-812 and 818 of method 800), the user is able to easily and efficiently activate a mode in which two or more applications are displayed and operated simultaneously. By allowing a user to easily and efficiently activate this mode, the usability of the device is improved (e.g., by allowing a user to activate the mode using a single gesture) and the human-machine interface is made more efficient. Additionally, this allows for sustained interaction with a touch-sensitive display that would not be possible otherwise by using multiple gestures to access two or more applications.

[0308] 8B, in some embodiments, before detecting any lift-off of the contact from the touch-sensitive display and after the contact has moved at least a threshold distance away from the dock, the device resizes the one or more applications of the first set to uncover a second portion of the display area adjacent to the resized one or more applications of the first set (820). In some embodiments, the one or more applications of the first set are resized to occupy a predetermined percentage of the display area (e.g., approximately 75% or 66% of the display area), and the second portion (e.g., predetermined area 454 or a portion of the display area used to display pinned applications, such as the portion used to display the video browsing application of FIG. 4T) occupies a predetermined remaining percentage of the display area (e.g., approximately 25% or 34% of the display area).

[0309] As a specific example, as shown in FIGS. 4E-4H, when one or more applications in the first set correspond to a single application (e.g., application 1 in FIG. 4E), the single application is reduced in size to make way for one or more affordances of the second set to be displayed adjacent to the resized single application (e.g., a preview of the default area is presented, and in some embodiments, the preview includes temporarily showing a wallpaper associated with the home screen).

[0310] If the one or more applications in the first set correspond to a plurality of applications (e.g., a first pinned application 1 and a second pinned video browsing application as shown in FIG. 4N), then one of the plurality of applications may no longer be displayed (FIG. 4T), thereby making way for displaying the preview in the default area 454 (which may include displaying a wallpaper associated with the device's home screen). In some other embodiments, if the one or more applications in the first set correspond to a plurality of applications, both of the plurality of applications remain displayed (e.g., as shown in FIG. 4W), and one of the plurality of applications is removed from the display only following liftoff of the contact associated with the gesture (e.g., gesture 468, FIG. 4W).

[0311] In some examples, a user of an electronic device may not recognize changes resulting from constant interaction on a touch-sensitive display. Providing clear visual feedback (e.g., resizing one or more applications of the first set to reveal a second portion of the display area) gives the user an opportunity to preview changes that will occur after releasing contact (or lifting off). Providing this clear visual feedback improves usability of the device (e.g., by allowing the user to understand the changes that will occur and avoid being forced to reverse unnecessary changes) and makes the human-machine interface more efficient. Additionally, it allows for sustained interaction with the touch-sensitive display that would not be possible otherwise than by repeatedly undoing or reversing undesired changes that the user could not have anticipated.

[0312] In some embodiments, prior to detecting lift-off of the contact and after the contact moves within a threshold distance (e.g., one to two centimeters, as in thresholds 464, 465 of FIG. 4AB) from an edge of the touch-sensitive display that contacts at least a portion of the one or more applications in the first set or at least a portion of the one or more applications in the second set, the method includes resizing the one or more applications in the first set to uncover a second portion of the display area adjacent the resized one or more applications in the first set (e.g., as shown in FIGs. 4AD and 4AE).

[0313] In one particular exemplary embodiment, when the first set of one or more applications corresponds to a single application (e.g., Application 1, FIG. 4AB), the single application is simply reduced in size to make room for clarifying the preview of the default region upon determining that a gesture (e.g., gesture 472, FIG. 4AB) dragging an application-specific affordance outside of the dock 408 crosses beyond a threshold, such as threshold 464 or 465 in FIG. 4AB. Examples are shown in FIGS. 4AB-4AF and described in more detail above.

[0314] In some embodiments (such as one particular exemplary embodiment described above), when the one or more applications in the first set correspond to multiple applications, the multiple applications may not be resized to display a preview in the default area 454. Instead, the user may drag an application-specific affordance over a boundary between the multiple applications to overlay another application on top of the multiple applications (as shown in FIGS. 4AJ-4AL), or drag an application-specific affordance over a particular application of the multiple applications to replace the particular application with a new application that corresponds to the application-specific affordance (as shown in FIGS. 4AP-4AR). Examples of such embodiments are given in more detail above with reference to FIGS. 4AJ-4AL and 4AP-4AR.

[0315] 8B, in some embodiments, displaying (i) at least a portion of one or more applications of a first set and (ii) at least a portion of one or more applications of a second set within a display area occupying substantially all of the touch-sensitive display includes displaying at least a portion of the one or more applications of the second set in a second portion of the display area (e.g., displaying a web browsing application in a default portion, as shown in FIG. 4U) and displaying at least a portion of the one or more applications of the first set in a remainder of the display area adjacent to the second portion of the display area (e.g., displaying application 1 in the default portion adjacent to the second portion / default area) (822 and 822A). In some embodiments, the second portion of the display area is separated from the remainder of the display area by a draggable border extending along a length of the second portion and the remainder. In some embodiments, contact over a draggable boundary (e.g., over boundary affordance 460 in FIG. 4R) enables the user to resize the portions of the display area allocated to one or more applications in the first and second sets (as also described above with reference to FIGS. 4L-4M).

[0316] 8C, in various embodiments or situations, the first and second sets may include one or more applications where contact lift-off may cause different exchange behaviors. Additional examples are provided below with reference to methods 824-830.

[0317] For example, at 824, the first set includes one first application, the second set includes one second application, an affordance is associated with the one second application, and upon detecting lift-off of the contact, the first and second applications are displayed side-by-side within the display area. An example of this is shown in FIGS. 4E-4I. In some embodiments, lift-off of the contact is detected while the contact is located within a threshold distance of an edge of the touch-sensitive display that bounds the one first application (e.g., while the contact is located beyond one of thresholds 464, 465 shown in FIGS. 4AB-4AE, and described above). When the first set includes one first application and the second set includes one second application, a user of the computing system can activate a split view mode in which both the first application and the second application are displayed by simply dragging the affordance corresponding to the second application over a second portion of the display. Providing clear visual feedback (e.g., revealing a second portion of the display area after contact has moved a threshold distance) gives the user an opportunity to preview changes that will occur after contact is released (or lifted off). Providing this clear visual feedback improves usability of the device (e.g., by allowing the user to understand that releasing contact activates a split view mode that includes the first and second applications) and makes the human-machine interface more efficient. Additionally, it allows for sustained interaction with the touch-sensitive display that would not be possible without repeatedly undoing or reversing undesired changes that the user could not have anticipated.

[0318] In some embodiments, if a contact lift-off is instead detected while the contact is located over one of the first applications (and while the contact is not located within a threshold distance of an edge of the display 112, such as one of thresholds 464, 465), the second application is displayed in an overlay mode instead of side-by-side with the first application. For example, upon detecting a contact lift-off while the contact is located over one of the first applications (825) (e.g., the lift-off occurs over the first application, as shown in FIG. 4AH), the second application is displayed overlaying the first application in the display area (as shown in FIG. 4AI).

[0319] As another example, at 826, the first set includes at least a first application and a second application, the second set includes one third application, and the affordance is associated with the one third application (e.g., as shown in Figures 4Q-4U). When the first set includes a first application and a second application and the second set includes one second application, a user of the computing system can add a new application to a split view mode in which the first application and the second application are both displayed by simply dragging an affordance corresponding to the third application on the display. Providing visual feedback (e.g., clearing a second portion of the display area after the contact has moved a threshold distance) gives the user an opportunity to preview changes that will occur after the contact is released (or lifted off). Additionally, this allows for sustained interaction with the touch-sensitive display that would not have been possible otherwise than by repeatedly undoing or reversing undesired changes that the user could not have anticipated.

[0320] In this example, pursuant to determining at 826 that contact lift-off occurs on the second application, the device replaces the second application with a third application on the touch-sensitive display. An example of this is shown in Figures 4Q-4U. In this manner, the user is provided with the ability to replace the second application with a third application in a split view mode, thereby enabling a persistent interaction in which the user can quickly and easily substitute in a new application that is viewed simultaneously with the first application.

[0321] In some embodiments, when contact lift-off occurs at a boundary between a first application and a second application, instead of replacing one of the pinned applications, a third application instead overlays one of the first or second applications. For example, as shown in FIGS. 4AJ-4AK, contact lift-off associated with gesture 484 occurs on a boundary between application 1 and a video browsing application, and pursuant to determining that contact lift-off occurs on this boundary, the device displays (827) one third application (e.g., the video browsing application of FIG. 4AL) overlaying the first or second application on the touch-sensitive display (e.g., the video browsing application overlaying the web browsing application in FIG. 4AL). In some embodiments, the third application always overlays the right-most application after it is determined that lift-off occurred on a boundary between the first and second applications.

[0322] Another example is described at 828, where a first set includes at least two pinned applications of a first group, a second set includes at least two pinned applications of a second group, and an affordance is associated with at least two pinned applications of the second group (e.g., as shown in Figures 4V-4X). When the first and second sets each include a group of pinned applications, a user of the computing system can add a new group of pinned applications to the split-view mode by simply dragging the affordance corresponding to the second group on the display. Providing clear visual feedback (e.g., clearing the second portion of the display area after the contact has moved a threshold distance) gives the user an opportunity to preview changes that will occur after the contact is released (or lifted off). In addition, this allows for sustained interaction with the touch-sensitive display that would not have been possible otherwise than by repeatedly undoing or reversing undesired changes that the user could not have anticipated.

[0323] In this example, pursuant to determining that contact lift-off occurred on the first group of applications at 828, the device replaces at least two pinned applications of the first group with at least two pinned applications of the second group (e.g., as shown in FIG. 4X). In this manner, the user is provided with the ability to quickly switch between the first group of pinned applications and the second group of pinned applications, thereby enabling a persistent interaction that allows the user to quickly and easily replace the new group of pinned applications on the display.

[0324] A final example is at 830, where the first set of one or more applications includes an instance of the first application and the second set of one or more applications includes an additional instance of the first application, the instance and the additional instance being separate instances of the first application. If the first and second sets each include different instances of the same first application, a user of the computing system can pin two different instances of a single application next to each other. Allowing two different instances to be pinned to each other provides an improved man-machine interface for the user (e.g., by ensuring that different features of a single application can be simultaneously interacted with, e.g., editing a message in a messaging application while also copying content from a different message in the same messaging application). Additionally, this allows for sustained interaction with the touch-sensitive display that would not have been possible otherwise than by repeatedly undoing or reversing undesired changes that the user could not have anticipated.

[0325] In some embodiments, as described in more detail below with reference to method 900, the second application is displayed with a handle (e.g., affordance 462, FIG. 4J) that can be used to activate a slide-over mode or to drag the second application to be displayed on a different portion of the touch-sensitive display. Accordingly, aspects / operations of methods 800 and 900 may be interchanged, substituted, and / or added between these methods. For the sake of brevity, these details will not be repeated here.

[0326] Additionally, in some embodiments, the representations shown in the application switcher user interface include representations in a split view mode, as described in more detail below with reference to method 1000. Accordingly, aspects / operations of methods 800 and 1000 may also be interchanged, substituted, and / or added between these methods, and for the sake of brevity, these details will not be repeated here.

[0327] Additionally, in some embodiments, as described in more detail below with reference to method 1100, the first set of one or more applications may include two different instances of the same application. Accordingly, aspects / operations of methods 800 and 1100 may be interchanged, substituted, and / or added between these methods. For the sake of brevity, these details will not be repeated here.

[0328] 9A-9B are flow chart diagrams of methods of interacting with a single affordance to switch between a split view mode (where two applications are pinned to each other and displayed side-by-side on the display) and a slide over mode (where one application is displayed on the display overlaying another application), according to some embodiments. FIGS. 5A-5O are used to illustrate the methods and / or processes of FIGS. 9A-9B. Although some of the examples below are described with reference to input on a touch-sensitive display (combining a touch-sensitive surface and display), in some embodiments the device detects input on a touch-sensitive surface 195 that is separate from display 194, as shown in FIG. 1D.

[0329] In some embodiments, method 900 is performed by an electronic device (e.g., portable multifunction device 100, FIG. 1A, and / or one or more components of the electronic device (e.g., I / O subsystem 106, operating system 126, etc.). In some embodiments, method 800 is governed by instructions stored on a non-transitory computer-readable storage medium and executed by one or more processors of the device, such as one or more processors 122 of device 100 (FIG. 1A). For ease of explanation, method 900 is described below as being performed by device 100. In some embodiments, with reference to FIG. 1A, the operations of method 800 are performed at least in part by or use a multitasking module (e.g., multitasking module 180) and its components, a contact / motion module (e.g., contact / motion module 130), a graphics module (e.g., graphics module 132), and a touch-sensitive display (e.g., touch-sensitive display system 112). Some operations of method 900 are optionally combined and / or the order of some operations is optionally changed.

[0330] As described below, the method 900 provides an intuitive way to switch between split view and slide over modes, as well as to manipulate the location at which multiple applications are displayed simultaneously. This method reduces the number of inputs required from the user to switch between these modes (e.g., the user need only make a simple gesture instead of performing multiple inputs), thereby ensuring an extended battery life for the electronic device implementing the method 900, as less power is required to process the fewer number of inputs (and this savings is realized over time as users become increasingly accustomed to the more intuitive and simple gestures). As described in more detail below, the operations of the method 900 help to ensure that users engage in sustained interactions (e.g., the operations of the method 900 do not require frequent undo behaviors that interrupt their interactions with their devices), and the operations of the method 900 help to create a more efficient human-machine interface.

[0331] In some embodiments, a device performing method 900 first displays (902) a first application and a second application within a display area occupying substantially all of a touch-sensitive display. In some embodiments, the first application is a primary application (e.g., application 1 displayed to occupy the right side of display 112 in FIG. 5A ) that is displayed to occupy approximately 2 / 3 (approximately 66%) of the available display area of ​​display 112, and the second application is a side application (e.g., a video browsing application displayed to occupy the left side of display 112 and pinned next to application 1 in split view mode) that is displayed to occupy the remaining 1 / 3 (approximately 33%) of the available display area of ​​display 112.

[0332] In some embodiments, displaying the first and second applications within the display area includes simultaneously displaying the first and second applications side-by-side within the display area (903).

[0333] While displaying the first application and the second application within the display area (904), the device may perform operations 906, 908, and 910. At operation 906, the device displays an affordance near an edge of the second application. For example, the affordance is a user interface object (e.g., handle 506, FIG. 5B) displayed near a top portion of the second application, which handle is displayed in response to an activation gesture (as described with reference to operation 908). At 908, in some embodiments, before displaying the affordance, the device detects a user input (e.g., a contact associated with gesture 508 in FIG. 5A) at an edge of the second application and displays the affordance in response to detecting the user input (FIG. 5B). In this manner, the user is provided with a simple gesture that is used to activate the display of the handle, thereby enhancing usability of the device (e.g., by ensuring that the handle is only displayed when needed by the user).

[0334] In some embodiments, also in operation 908, the user input can include an initial contact (e.g., associated with gesture 508) at an edge of the second application and movement of the initial contact in a first direction across the touch-sensitive display. In some embodiments, the device detects that the contact has moved at least a threshold distance away from the edge, such as one or two centimeters, before displaying the affordance. As discussed above, this provides the user with a simple gesture that can be used to activate the display of a handle, thereby improving usability of the device (e.g., by ensuring that the handle is only displayed when needed by the user).

[0335] At 910 (also performed while displaying the first and second applications within the display area), the device detects (910) a contact (different from the initial contact described above, such as the contact associated with gesture 509 of FIG. 5B ) over an affordance that moves in a direction across the touch-sensitive display. Pursuant to a determination that the direction is a first direction (912) (e.g., the contact associated with gesture 509 is shown as moving in a substantially downward direction relative to the top edge of the second application in FIG. 5B ), the device performs operations 914 and 916. Operation 914 includes resizing the first application to occupy substantially all of the display area (e.g., as shown in FIG. 5C , where application 1 occupies substantially all of the display area of ​​touch-sensitive display 112), and operation 916 includes displaying the second application overlaying the resized first application (e.g., as also shown in FIG. 5C , the video browsing application is now displayed overlaying the resized application 1).

[0336] The method 900 checks whether the direction is a second direction instead of the first direction described above, and if so, the method proceeds to move the application in which the affordance 506 is displayed (instead of switching between split view and slide over modes). Specifically, pursuant to a determination that the direction is a second direction that is substantially perpendicular to the first direction (e.g., within + / - 5 degrees of perpendicular from the first direction), the device moves (918) the second application within the display area. For example, the contact associated with the gesture 512 is shown in Figures 5F-5G as moving in a second direction (e.g., a substantially left-to-right direction across the touch-sensitive display), and the second application is then moved laterally within the display area (e.g., from a right-most position in Figure 5F to a left-most position in Figure 5H). In some examples, a user of a computing system must use inefficient and time-consuming interactions to operate two or more applications. Enabling a user to interact with affordances (such as handles, in connection with at least actions 902, 904, 906, 910, 912, 914, 916, and 918) to activate a slide over mode or move a particular application within the display area allows the user to easily and efficiently move applications around and switch between parallel views or slide over views. Enabling a user to easily and efficiently move applications around and switch between different modes using two or more applications simultaneously improves usability of the device and makes the human-machine interface more efficient (e.g., by allowing the user to select how to interact with two or more applications simultaneously, e.g., using parallel views or slide over / overlay modes). Additionally, this allows for persistent interaction with a touch-sensitive display that would not be possible otherwise by using multiple gestures to customize simultaneous interaction with two or more applications.

[0337] As briefly discussed above, in some embodiments, the first direction is a downward direction relative to the edge of the second application (e.g., the direction moved by gesture 508 in FIG. 5A ), and the second direction is a sideways direction that is approximately perpendicular to the downward direction (e.g., the direction moved by gesture 512 in FIGS. 5F-5G ). Allowing the user to move the handle in different directions helps provide the user with an additional and simple way to flexibly customize how they want to interact with two simultaneously displayed applications at the same time. Allowing users to customize their user experience in this way improves the usability of the device and makes the human-machine interface more efficient (e.g., allowing users to use various functions more efficiently instead of having to go through default arrangements due to their customized selection of where each application should be displayed). In addition, this allows for persistent interaction with the touch-sensitive display that would not be possible otherwise than by forcing the user to interact with two or more applications that are displayed together in a default manner and without any user-specific customization.

[0338] 9B, before performing operation 918, the device detects (922) a user input in the resized first application while the second application is overlaying the resized first application (e.g., receives contact 510 over link 504, FIG. 5C). The device then responds to the user input via the first application (924) (e.g., content associated with link 504 is opened, FIG. 5D). In other words, the first application is still usable while the second application is overlaying it (e.g., the first application is still usable because the features of the first application are still functional even during the overlay / slideover mode). In some embodiments, both the first application and the second application are usable simultaneously, allowing the user to simultaneously interact with various functions of each of the two applications even when the second application is overlaying the first application. Enabling a user to interact with a first application, even while the second application is overlaid on top of the first application, allows the user to customize how they want to interact with two simultaneously displayed applications. Allowing users to customize their user experience in this manner improves usability of the device and makes the human-machine interface more efficient (e.g., allowing users to use various features more efficiently instead of having to work with default arrangements because of their customized selections). Additionally, this allows for persistent interaction with the touch-sensitive display that would not be possible without the user being forced to interact with two or more applications displayed together in a default manner and without any user-specific customization.

[0339] In some embodiments, after performing operations 922 and 924 (or alternatively, before performing these operations), the device, in response to a request to open a third application separate from the first and second applications (e.g., contact 516 on the camera application in FIG. 5K), displays (926) (i) the third application within a portion of the display area previously occupied by the first application, and (ii) the second application overlaying the third application. For example, as shown in FIGS. 5K-5L, a user requests to open a third application by activating a home screen and clicking an affordance corresponding to the third application. In response to the request, the third application is then displayed in a portion of the display area previously occupied by the first application, and the second application is displayed overlaying the third application. In other words, the overlaying application (e.g., the second application) remains even after the user switches to open a new application. Enabling the overlaid application to remain visible after the user opens a new application helps ensure that persistent interactions are maintained with features of the electronic device (e.g., features accessed by the user through the overlaid application that may have to be reopened if the overlaid application does not remain visible). The user can also avoid being forced to reopen features of the overlaid application, thereby improving usability of the device and also causing the human-machine interface to operate more efficiently.

[0340] Returning to the description of operation 918, in which the direction (of contact moving over the affordance) is determined to be the second direction, additional operations shown at 928 are also performed. First, the second application is initially displayed adjacent to a first edge of the touch-sensitive display (e.g., the video browsing application shown in FIG. 5F is shown adjacent to the right-most edge of touch-sensitive display 112). Moving the second application within the display area also includes moving the second application in the second direction until the second application abuts a second edge opposite the first edge of the touch-sensitive display (e.g., the video browsing application follows gesture 512 as it moves across touch-sensitive display 112, as shown in FIG. 5G, and then the video browsing application stops moving when it reaches the second edge). In these embodiments, moving the second application within the display area may also include displaying the first application in a remainder of the display area separate from the portion occupied by the second application, such that the first application abuts a first edge of the touch-sensitive display (as shown in FIG. 5H). Allowing the user to move the application around by dragging affordance 506 helps to allow the user to customize how they want to interact with two simultaneously displayed applications. Allowing users to customize their user experience in this way improves the usability of the device and makes the human-machine interface more efficient (e.g., allowing users to use various features more efficiently instead of having to go through default arrangements, with their customized selection of where each application should be displayed). Additionally, this allows for persistent interaction with the touch-sensitive display that would not be possible otherwise than by the user being forced to interact with two or more applications displayed together in a default manner and without any user-specific customization.

[0341] In the embodiment described above with reference to 928, a preview of the portion occupied by the second application is made clear next to the first application before the second application is moved until it touches the second edge (930). In some examples, a user of a computing system may not recognize changes resulting from constant interaction on a touch-sensitive display. Providing clear visual feedback (e.g., showing a preview of where the second application will move) gives the user an opportunity to preview changes that will occur after releasing contact (or lifting off). Providing this clear visual feedback improves usability of the device (e.g., by allowing the user to understand the changes that will occur and avoid being forced to reverse undesired changes) and makes the human-machine interface more efficient. Additionally, it allows for sustained interaction with the touch-sensitive display that would not be possible otherwise than by repeatedly undoing or reversing undesired changes that the user could not have anticipated.

[0342] 9C, additional interactions available after the overlaid applications are displayed are shown at acts 932, 934, and 936. For example, after resizing a first application and displaying a second application overlaying the resized first application in act 932 (e.g., as shown in FIG. 4AI, a web browsing application overlays application 1), the device detects an additional contact above the affordance (e.g., the contact associated with gesture 482 in FIG. 4AI) and movement of the additional contact in a third direction opposite the first direction (e.g., a substantially upward direction as shown in FIG. 4AI). In response to detecting that the additional contact has moved a threshold distance (e.g., one to two centimeters) in a third direction, the device stops displaying the second application overlaying the resized first application and re-displays the first application and the second application within a display area that occupies substantially all of the touch-sensitive display (e.g., as shown in FIG. 4AJ, where the web browsing application is pinned next to application 1 so that the two applications occupy substantially all of the touch-sensitive display and are displayed in a side-by-side / split view format).

[0343] 9C , in some embodiments, after resizing a first application and displaying a second application overlaying the resized first application (e.g., as shown in FIG. 4AI, a web browsing application overlays application 1), the device detects an additional contact on the affordance and movement of the additional contact in a first direction (e.g., the contact associated with gesture 487 in FIG. 4AO is over affordance 467 and moves in the first direction) (934). Although the example in FIG. 4AO shows two applications displayed side-by-side with another application overlaying the two applications, gesture 487 may also be available when the overlaid application is displayed over a single application (e.g., gesture 487 may be similarly performed over affordance 467 in FIG. 4AI). In response to detecting that the additional contact has moved a second threshold distance across the touch-sensitive display (e.g., one to two centimeters), the device scales the content associated with the second application in accordance with the movement of the additional contact until a user interface object having a representation of an affordance corresponding to the second application is displayed (e.g., as shown in FIG. 4AP, the content is scaled down until it is no longer displayed and instead UI object 473-B is displayed).

[0344] In some embodiments, the user can then move UI object 473-B to dismiss the second application entirely or to pin the second application next to the first application. For example, pursuant to a determination that an additional contact moves over the dock and is lifted off the touch-sensitive display (e.g., a contact associated with gesture 488 of FIGS. 4AO-4AQ is dragged over dock 408 and then lifted off (not shown)), the device may dismiss the second application and display the first application occupying substantially all of the touch-sensitive display (e.g., the user interface shown in FIG. 4AG is displayed in which application 1 occupies substantially all of the touch-sensitive display, and pursuant to a determination that an additional contact moves within a threshold distance of an edge of the touch-sensitive display (e.g., within one of thresholds 464, 465 shown in FIGS. 4AB-4AE) and is lifted off the touch-sensitive display, the device may re-display the first application and the second application within a display area occupying substantially all of the touch-sensitive display (e.g., displays the user interface shown in FIG. 4AJ in which application 1 is displayed side-by-side in split view mode with the web browsing application).

[0345] Although the examples provided above generally refer to overlaying a second application on top of a currently displayed first application, in some embodiments an application may be overlaid on top of two pinned applications in a side-by-side display format. Examples of this are shown in Figures 4AJ-4AR and described above. Aspects of these examples may complement and / or replace certain operations described above with respect to method 900.

[0346] It should be understood that the particular order described for the operations in Figures 9A-9B is merely an example, and that the described order is not intended to indicate that the operations are the only order in which they may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. Additionally, method 900 may be supplemented (or various operations reordered) to incorporate aspects of method 800 relating to, for example, using a dock to activate a split view mode. For the sake of brevity, these details will not be repeated here.

[0347] Figures 10A-10C are flow chart diagrams of method 1000 according to some embodiments. Figures 6A-6Q are used to illustrate the methods and / or processes of Figures 10A-10C. Although some of the examples below are described with reference to input on a touch-sensitive display (combining the touch-sensitive surface and display), in some embodiments, the device detects input on a touch-sensitive surface 195 that is separate from display 194, as shown in Figure 1D.

[0348] In some embodiments, method 1000 is performed by an electronic device (e.g., portable multifunction device 100, FIG. 1A ), and / or one or more components of the electronic device (e.g., I / O subsystem 106, operating system 126, etc.). In some embodiments, method 1000 is governed by instructions stored on a non-transitory computer-readable storage medium and executed by one or more processors of the device, such as one or more processors 122 of device 100 ( FIG. 1A ). For ease of explanation, method 1000 is described below as being performed by device 100. In some embodiments, with reference to FIG. 1A , the operations of method 1000 are performed at least in part by or use a multitasking module (e.g., multitasking module 180) and its components, a contact / motion module (e.g., contact / motion module 130), a graphics module (e.g., graphics module 132), and a touch-sensitive display (e.g., touch-sensitive display system 112). Some operations of method 1000 are optionally combined and / or the order of some operations is optionally changed.

[0349] As described below, the method 1000 provides an intuitive and seamless interaction for multitasking on a handheld electronic device. The method 1000 reduces the number of inputs from a user to display multiple applications and switch between different applications on the device, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, providing an interaction for multitasking conserves power (e.g., by saving time and energy-draining operations when a user must close one application to open another) and increases the time between battery charges.

[0350] 10A, in performing method 1000, a device simultaneously displays (1002) at least two applications within a display area that occupies substantially all of the touch-sensitive display. For example, in FIG. 6A, a first application (Application 1) is displayed adjacent / side-by-side with a second application (Application 2 or a video application), and the two applications are displayed within display area 601a that occupies substantially all of touch screen 112.

[0351] The device receives (1004) user input corresponding to a request to display an application switcher user interface. In some embodiments, the application switcher user interface may refer to a user interface in which representations of recently used applications (e.g., applications that have been opened and used in the foreground of the electronic device and have not yet been closed by a user of the device) are displayed. In some embodiments, the user input may correspond to a double-tap input on a physical or solid-state home button of the electronic device, or may correspond to a continuous upward gesture across a touch-sensitive display (e.g., gesture 602 of FIGS. 6A-6D and 6O-6P). For example, in some embodiments, a gesture a first threshold distance (e.g., 1-2 centimeters) from the edge of the screen displays a dock that begins to follow the gesture as it moves across the display; after the gesture moves a second threshold distance (e.g., 2-4 centimeters in total, or an additional 1-2 centimeters beyond the first threshold distance), the dock remains in a static position and no longer follows the gesture; when the gesture 602 continues to move beyond the second threshold distance, the currently displayed application begins to reduce in size and an application switcher user interface is displayed, and when the gesture moves at least a third threshold distance (e.g., 3-6 centimeters in total, or an additional 1-2 centimeters beyond the second threshold distance), the application switcher user interface is displayed.

[0352] In response to receiving the user input, the device displays (1006) an application switcher user interface (e.g., application switcher user interface, FIGS. 6D-6M, and 6P-6Q) on the touch-sensitive display. In some embodiments, displaying the application switcher user interface includes gradually decreasing the size of the display area or shrinking the display area until it reaches a predefined size associated with the representation (1008). For example, in FIGS. 6D-6E, the size of the display area 601a shown in FIG. 6A gradually decreases until the miniaturized view of the display 601a reaches a predefined size associated with the representation. In this manner, the user is provided with a clear visual indication as to where the pinned applications the user was looking at are located within the application switcher user interface, which helps to improve usability of the device (e.g., by ensuring that the user easily locate the pinned applications without having to waste time trying to locate their placement within the application switcher UI and within this UI).

[0353] In some embodiments, the application switcher user interface includes (1010) a representation of at least some of the applications recently used on the electronic device, each representation including a representation of a display area having at least two applications. For example, in Figures 6P and 6Q, representation 638 includes a representation of a display area having two applications, application 4 and application 5. In some embodiments, each representation shows an active state (e.g., the last display screen for a particular application) for at least some of the applications recently used on the electronic device. In some embodiments, the representation of the display area having at least two applications is a miniaturized view of the display area previously occupying substantially all of the touch-sensitive display. For example, in Figure 6E, representation 604 includes a miniaturized view of display area 601a shown in Figure 6A, which shows a side-by-side display of application 1 and a video application.

[0354] In some embodiments, each representation includes an additional representation of an additional application associated with the overlaid application (1012), where the additional representation does not show the overlaid application. For example, as shown in FIG. 6N, the additional applications are application 1 and application 2, where a video application is overlaid on top of application 1. Application 1 is displayed in display area 601b that occupies substantially all of touch-sensitive display 112. In FIGS. 6P-6Q, the additional representation 634 does not show the overlaid video application. In this way, the human-machine interface is made more efficient by presenting only representations of pinned applications (which may be directly interacted with in the application switcher user interface) and not presenting representations of overlaid applications. To avoid clustering of the application switcher user interface, the additional representation representing application 1 in some embodiments does not show the overlaid second application.

[0355] In some embodiments, displaying at least two applications within the display area includes simultaneously displaying at least two applications side-by-side within the display area (e.g., application 1 of FIG. 6A and a video application) (1014), and displaying a representation of the display area with the at least two applications includes simultaneously displaying at least two applications side-by-side within the representation of the display area (e.g., representation 604 is a miniaturized view in a split view mode showing application 1 and a video application of FIGS. 6D-6F).

[0356] In some embodiments, displaying the application switcher user interface includes displaying a dock including a plurality of affordances corresponding to applications available on the electronic device, e.g., dock 408 of Figures 6B-6M and 6O-6Q including a plurality of affordances (1016). In such an embodiment, referring to Figure 10B, the device further detects a contact (e.g., contact 603, Figure 6F) over one of the plurality of affordances included in the dock (e.g., contact 603 over a browser affordance in dock 408, Figure 6F) (1018) and detects movement of the contact toward the representation in the display area (e.g., movement of contact 603 away from dock 408 and orientation of representation 604, Figure 6F) without detecting lift-off during detection of the contact and movement (1020). In some embodiments, upon detecting a lift-off of the contact on a first application of at least two applications included in the representation of the display area, the device stops displaying (1022) the first application in the representation of the display area and instead displays a further application that corresponds to an affordance in the representation of the display area. For example, in Figures 6F-6G, after detecting a lift-off of the contact, representation 604 is updated to indicate that the web browsing application is now displayed side-by-side with application 1 (and the memory of device 100 may be updated to reflect that these applications are pinned to each other). In the updated representation 616, the video application is dismissed from representation 604 and replaced by the web browsing application.

[0357] As described above, allowing a user to see a representation within the application switcher user interface showing the applications displayed in split view mode allows the user to easily and efficiently identify pinned applications. Allowing a user to interact with pinned applications directly from the application switcher user interface improves device usability and causes the human-machine interface to operate more efficiently (e.g., interacting directly with pinned applications from within the application switcher user interface ensures that the user avoids being forced to exit the application switcher user interface to perform those interactions). Additionally, this allows for persistent interaction with the touch-sensitive display that would not be possible otherwise by using multiple gestures to leave the application switcher user interface and then initiating an interaction with the pinned application (or dismissing / replacing it).

[0358] In some embodiments, while displaying the application switcher user interface, the device detects (1024) additional user input over a first application of the at least two applications included in the representation of the display area (e.g., a non-tap selection 618b (long press), such as a contact that lasts longer than a predefined time, or a contact having an intensity that increases above a threshold intensity (e.g., a deep / hard press), as shown in FIG. 6I). In response to detecting the additional user input, in some embodiments, the device displays (1026) a dismiss affordance over at least a portion of the first application (e.g., the dismiss affordance 620 corresponds to an "x" displayed over a portion of the first application, as shown in FIGS. 6I and 6J). Upon detecting a selection of the dismiss affordance (e.g., upon detecting user input 622 in FIG. 6J), the device closes (1028) the first application and displays an updated representation of the remaining at least two applications other than the first a...

Claims

1. 1. An electronic device having a touch-sensitive display and one or more processors, Displaying a first application and a second application within a display area occupying substantially all of a touch-sensitive display; While the first application and the second application are displayed in the display area, Displaying an affordance near an edge of the second application; and Detecting a contact on the affordance that moves across the touch-sensitive display; upon determining that the direction is a first direction that includes downward movement relative to a top edge of the touch-sensitive display, resizing the first application to occupy substantially all of the display area; displaying the second application overlaying the resized first application; moving the second application within the display area in accordance with a determination that the direction is a second direction substantially parallel to the top edge of the touch-sensitive display; A method comprising:

2. Detecting a user input in the first application while the second application overlays the resized first application; Responding to the user input via the first application; The method of claim 1 further comprising:

3. after said determining that said direction is said first direction, in response to a request to open a third application separate from the first and second applications, (i) displaying the third application within a portion of the display area previously occupied by the first application, and (ii) displaying the second application overlaying the third application; The method of claim 2 further comprising:

4. the second application is initially displayed adjacent a first edge of the touch-sensitive display; Moving the second application within the display area moving the second application in the second direction until the second application contacts a second edge of the touch-sensitive display opposite the first edge; displaying the first application in a remaining portion of the display area separate from a portion occupied by the second application such that the first application abuts the first edge of the touch-sensitive display; The method of claim 1 , comprising:

5. 5. The method of claim 4, wherein a preview of the portion occupied by the second application is made clear next to the first application before the second application is moved until the second application contacts the second edge.

6. Before displaying the affordance, Detecting a user input at the edge of the second application and displaying the affordance in response to detecting the user input. The method of claim 1 further comprising:

7. The method of claim 6 , wherein the user input comprises a contact at the edge of the second application and a movement of the contact in the first direction across the touch-sensitive display.

8. after resizing the first application and displaying the second application overlaying the resized first application; Detecting an additional contact on the affordance and movement of the additional contact in a third direction opposite to the second direction; in response to detecting that the additional contact has moved a first threshold distance in the third direction, ceasing to display the second application overlaying the resized first application and redisplaying the first application and the second application within the display area occupying substantially all of the touch-sensitive display; The method of claim 1 further comprising:

9. after resizing the first application and displaying the second application overlaying the resized first application; Detecting an additional contact on the affordance and movement of the additional contact in the first direction; in response to detecting that the additional contact has moved a second threshold distance across the touch-sensitive display, shrinking content associated with the second application in accordance with movement of the additional contact until a user interface object having a representation of an affordance corresponding to the second application is displayed; The method of claim 1 further comprising: re-displaying the first application and the second application within the display area occupying substantially all of the touch-sensitive display pursuant to a determination that the additional contact has moved within a third threshold distance of an edge of the touch-sensitive display and lifted off of the touch-sensitive display; The method of claim 9 further comprising:

11. 8. The method of claim 1, wherein displaying the first and second applications within the display area comprises simultaneously displaying the first and second applications side-by-side within the display area.

12. 1. An electronic device comprising: A display and An input element; one or more processors; a memory storing one or more programs; the one or more programs are configured to be executed by the one or more processors, the one or more programs comprising: Displaying a first application and a second application within a display area occupying substantially all of a touch-sensitive display; While the first application and the second application are displayed in the display area, Displaying an affordance near an edge of the second application; and Detecting a contact on the affordance that moves across the touch-sensitive display; upon determining that the direction is a first direction that includes downward movement relative to a top edge of the touch-sensitive display, resizing the first application to occupy substantially all of the display area; displaying the second application overlaying the resized first application; moving the second application within the display area in accordance with a determination that the direction is a second direction substantially parallel to the top edge of the touch-sensitive display; An electronic device that contains instructions for executing the

13. 13. The electronic device of claim 12, wherein the one or more programs comprise instructions for carrying out the method of any one of claims 2 to 11.

14. A program including instructions that, when executed by an electronic device having a display and input elements, cause the electronic device to: Displaying a first application and a second application within a display area occupying substantially all of a touch-sensitive display; While the first application and the second application are displayed in the display area, Displaying an affordance near an edge of the second application; Detecting a contact on the affordance that moves across the touch-sensitive display; upon determining that the direction is a first direction that includes downward movement relative to a top edge of the touch-sensitive display, resizing the first application to occupy substantially all of the display area; displaying the second application overlaying the resized first application; moving the second application within the display area in accordance with a determination that the direction is a second direction substantially parallel to the top edge of the touch-sensitive display; A program to execute.

15. A program according to claim 14, comprising instructions for carrying out the method according to any one of claims 2 to 11.

Images