DEVICE, METHOD, AND GRAPHICAL USER INTERFACE FOR NAVIGATING AMONG USER INTERFACES, DISPLAYING DOCKS, AND DISPLAYING SYSTEM USER INTERFACE ELEMENTS - Patent application

Abstract

To provide a fast and efficient method for navigating between user interfaces, displaying a dock, and displaying a system user interface element.SOLUTION: In an electronic device with a touch-sensitive display, a system user interface element that indicates a position for performing gesture, a first application that currently has a first set of one or more behaviors associated with the system user interface element, and a second application that currently has a second set of one or more behaviors are simultaneously displayed. The system user interface element overlaps the first application and has an appearance determined on the basis of the first set. An input corresponding to a request to resize the second application is detected, the second application is resized, and the appearance is changed on the basis of the second set when the system user interface element overlaps the second application.SELECTED DRAWING: Figure 13A

Description

[Technical field]

[0001] This application relates generally to electronic devices with touch-sensitive surfaces, including, but not limited to, electronic devices with touch-sensitive surfaces for navigating between user interfaces, displaying docks, and displaying system user interface elements (e.g., home affordances). [Background technology]

[0002] The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has grown significantly in recent years. Exemplary touch-sensitive surfaces include touchpads and touchscreen displays. Such surfaces are widely used to manipulate user interfaces on the displays and objects therein. Exemplary user interface objects include digital images, video, text, icons, and control elements such as buttons and other graphics.

[0003] Exemplary operations include adjusting the position and / or size of one or more user interface objects, activating a button or opening a file / application represented by a user interface object, associating metadata with one or more user interface objects, navigating through the user interface, or otherwise manipulating the user interface. Exemplary user interface objects include digital images, video, text, icons, and control elements such as buttons and other graphics. A user may, in some circumstances, need to perform such operations on user interface objects in a file management program (e.g., Finder from Apple Inc. of Cupertino, California), a picture management application (e.g., Aperture, iPhoto, Photos from Apple Inc. of Cupertino, California), a digital content (e.g., video and music) management application (e.g., iTunes® from Apple Inc. of Cupertino, California), a drawing application, a presentation application (e.g., Keynote from Apple Inc. of Cupertino, California), a word processing application (e.g., Pages from Apple Inc. of Cupertino, California), or a spreadsheet application (e.g., Numbers from Apple Inc. of Cupertino, California).

[0004] However, methods of performing these operations are cumbersome and inefficient. For example, using a series of mouse-based inputs to close a first user interface, navigate a multi-page home screen to identify a second user interface, and then select the second user interface for display is tedious and error-prone. In addition, the methods take longer than necessary, thereby wasting energy. The latter problem is particularly acute in battery-operated devices. Summary of the Invention

[0005] Thus, there is a need for electronic devices with faster, more efficient methods and interfaces for navigating among user interfaces, displaying docks, and displaying system user interface elements (e.g., home affordances). Such methods and interfaces, optionally, complement or replace conventional methods for navigating among user interfaces, displaying docks, and displaying system user interface elements (e.g., home affordances). Such methods and interfaces reduce the number, range, and / or type of inputs from a user, creating a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and extend the time between battery charges.

[0006] The above deficiencies and other problems associated with user interfaces for electronic devices having touch-sensitive surfaces are reduced or eliminated by the devices of the present disclosure. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, a tablet computer, or a handheld device). In some embodiments, the device is a personal electronic device (e.g., a wearable electronic device such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a "touch screen" or "touch screen display"). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or sets of instructions stored in the memory for performing a number of functions. In some embodiments, a user interacts with the GUI primarily through stylus and / or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functionality optionally includes image editing, drawing, presenting, word processing, spreadsheet creation, game playing, making phone calls, video conferencing, emailing, instant messaging, training support, digital photography, digital videography, web browsing, digital music playback, note taking, and / or digital video playback, and executable instructions to perform those functionality are optionally contained on a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0007] According to some embodiments, a method is performed on a device having a touch-sensitive display. The method includes displaying a first user interface on the display, the first user interface being separate from a home screen user interface that includes a plurality of application icons corresponding to different applications of a plurality of applications installed on the device. The method also includes detecting a first input by a first contact on a first edge of the display while displaying the first user interface on the display. The method further includes, in response to detecting a first input on an edge of the display, while the first contact continues to be detected on the first edge of the display, displaying a dock having a plurality of application icons at a first location along the first edge of the display in accordance with a determination that the first input satisfies the dock display criteria, and, in accordance with a determination that the first input is detected on a second portion of the first edge of the display different from the first portion of the first edge and the first input satisfies the dock display criteria, displaying the dock at a second location along the first edge of the display selected to include the second portion of the first edge of the display, the second location being different from the first location.

[0008] According to some embodiments, the method is performed in a device with a touch-sensitive surface and a display. The method includes simultaneously displaying a first application user interface on a first portion of the display and a second application user interface on a second portion of the display different from the first portion. The method also includes detecting a first input by a first contact comprising movement in a first direction while simultaneously displaying the first application user interface on the first portion of the display and the second application user interface on the second portion of the display. The method further includes, in response to detecting the first input, replacing the display of the first user interface and the second user interface with a full screen home screen in accordance with a determination that the first input satisfies a first criterion, the first criterion including a requirement that the first input include movement in the first direction less than a first threshold amount for the first criterion to be satisfied; and, in accordance with a determination that the first input satisfies a second criterion, the second criterion including a requirement that the first input include movement in the first direction less than a first threshold amount for the second criterion to be satisfied, the first input corresponding to the first application user interface. and replacing the display of the first user interface with a first replacement user interface while maintaining a display of the second application user interface within a second portion of the display in accordance with a determination that the first input was initiated within a first edge region of the display corresponding to the second application user interface, while maintaining a display of the first application user interface within the first portion of the display in accordance with a determination that the first input satisfied a second criterion.

[0009] According to some embodiments, the method is performed in a device with a touch-sensitive surface and a display. The method includes displaying, on the display, a user interface of a first of a plurality of applications installed on the device. The method includes detecting a gesture on the touch-sensitive surface, where detecting the gesture includes detecting an initial portion of the gesture while displaying the user interface of the first application on the display, and where detecting the gesture further includes simultaneously detecting multiple contacts on the touch-sensitive surface and detecting movement of the multiple contacts. The method further includes, in response to detecting the gesture on the touch-sensitive surface, performing an operation in the first application based on movement of the two simultaneously detected contacts during the gesture in accordance with a determination that the gesture includes two simultaneously detected contacts; switching from displaying a user interface of the first application to displaying a user interface of a second application of the multiple applications separate from the first application in accordance with a determination that the gesture includes more than a predetermined number of simultaneously detected contacts and a determination that the movement of the simultaneously detected contacts during the gesture satisfies a first criterion; and switching from displaying the user interface of the first application to displaying a user interface including respective application icons for opening the multiple applications installed on the device in accordance with a determination that the gesture includes more than the predetermined number of simultaneously detected contacts and a determination that the movement of the simultaneously detected contacts during the gesture satisfies a second criterion, separate from the first criterion.

[0010] According to some embodiments, a method is performed in a device having a touch-sensitive display, the method including: simultaneously displaying a first application and a second application on the touch-sensitive display, both of which are displayed along at least a portion of a respective edge of the touch-sensitive display; detecting a movement of a first edge swipe gesture at a respective location along a respective edge of the touch-sensitive display, including a movement of a contact from the respective location along the respective edge of the touch-sensitive display onto the touch-sensitive display while simultaneously displaying the first application and the second application; and in response to detecting the first edge swipe gesture, determining that the respective locations of the first edge swipe gesture correspond to locations of the first application on the touch-sensitive display; determining that the first applications are simultaneously associated with standard edge swipe gesture criteria; and determining that the first edge swipe gesture satisfies the standard edge swipe gesture criteria. a standard edge swipe gesture including a first set of one or more requirements that must be met for the standard edge swipe gesture criteria to be met; performing a system operation including displaying a system user interface on a portion of the touch-sensitive display previously occupied by at least a portion of the first application and at least a portion of the second application; and performing a system operation in accordance with: determining that a position of each of the first edge swipe gestures corresponds to a position of the second application on the touch-sensitive display; determining that the second application is simultaneously associated with the standard edge swipe gesture criteria; and determining that the first edge swipe gesture satisfies the standard edge swipe gesture criteria;and in accordance with a determination that the first edge swipe gesture satisfies the extended edge swipe gesture criteria, the extended edge swipe gesture including a first set of one or more requirements that must be met for the standard edge swipe gesture criteria to be met and also including a second set of one or more requirements that must be met in addition to the first set of one or more requirements of the extended edge swipe gesture criteria to be met, refraining from performing the system operation; and in accordance with a determination that a respective position of the first edge swipe gesture corresponds to a position of a second application on the touch-sensitive display, a determination that the second application is associated with the extended edge swipe gesture criteria as being simultaneously displayed, and a determination that the first edge swipe gesture does not satisfy the extended edge swipe gesture criteria.

[0011] According to some embodiments, the method is performed on a device having a touch-sensitive display. The method includes: a system user interface element indicating a location for performing a gesture that triggers a system action; a first application currently having a first set of one or more behaviors associated with the system user interface element; and a second application currently having a second set of one or more behaviors associated with the system user interface element that is different from the first set of one or more behaviors, both of which are displayed along at least a portion of respective edges of a touch-sensitive display, the system user interface element overlapping the first application without overlapping the second application, and an appearance of the system user interface element being determined based on the first set of one or more behaviors; detecting an input corresponding to a request to resize the second application while simultaneously displaying the first application, the second application, and the system user interface element; in response to detecting the input, resizing the second application in accordance with the input; and in response to a determination that the system user interface element is overlapped with the second application without overlapping with the first application, changing an appearance of the system user interface element to an appearance based on the second set of one or more behaviors associated with the system user interface element.

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

[0013] Thus, electronic devices having a display, a touch-sensitive surface, optionally one or more sensors that detect intensity of contact with the touch-sensitive surface, optionally one or more tactile output generators, optionally one or more device orientation sensors, and optionally an audio system are provided with improved methods and interfaces for navigating among user interfaces, displaying docks, and displaying system user interface elements (e.g., home affordances), thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can complement or replace conventional methods for navigating among user interfaces, displaying docks, and displaying system user interface elements (e.g., home affordances). [Brief description of the drawings]

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

[0015] [Figure 1A] 1 is a block diagram illustrating a portable multifunction device having a touch-sensitive display in accordance with some embodiments.

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

[0017] [Diagram 2] 1 illustrates a portable multifunction device having a touch screen in accordance with some embodiments.

[0018] [Diagram 3] 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments.

[0019] [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

[0020] [Figure 4B] 1 illustrates an exemplary user interface for a multifunction device having a touch-sensitive surface separate from a display in accordance with some embodiments.

[0021] [Figure 4C] 1 illustrates an example of a dynamic intensity threshold according to some embodiments. [Figure 4D] 1 illustrates an example of a dynamic intensity threshold according to some embodiments. [Figure 4E] 1 illustrates an example of a dynamic intensity threshold according to some embodiments.

[0022] [Figure 5A1] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A2] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A3] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A4] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A5]1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A6] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A7] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A8] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A9] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A10] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A11] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A12] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A13]1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A14] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A15] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A16] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A17] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A18] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A19] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A20] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A21]1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A22] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A23] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A24] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A25] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A26] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A27] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A28] 1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 5A29]1 illustrates an exemplary user interface for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments.

[0023] [Figure 5B1] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B2] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B3] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B4] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B5] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B6] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B7] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B8]1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B9] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B10] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B11] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B12] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B13] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B14] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B15] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B16]1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B17] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B18] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B19] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B20] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B21] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B22] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B23] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B24]1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B25] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B26] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B27] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B28] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B29] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B30] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B31] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B32]1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B33] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B34] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B35] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments. [Figure 5B36] 1A-1C illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode in accordance with some embodiments.

[0024] [Figure 5C1] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C2] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C3] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C4] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C5]1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C6] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C7] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C8] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C9] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C10] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C11] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C12] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C13] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C14] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C15] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C16] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C17] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C18] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C19] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C20] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C21] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C22] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C23] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C24] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C25] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C26]1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C27] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C28] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C29] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C30] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C31] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C32] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C33] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C34] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C35] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C36] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C37] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C38] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C39] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C40] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C41] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C42] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C43] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C44] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C45] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C46] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C47]1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C48] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C49] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C50] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C51] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C52] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C53] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C54] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C55] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C56] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C57] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C58] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments. [Figure 5C59] 1 illustrates an exemplary user interface for navigating between different user interfaces utilizing multi-touch gestures according to some embodiments.

[0025] [Figure 5D1] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D2] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D3] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D4] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D5] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D6] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D7] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D8] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D9] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D10] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D11] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D12] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D13] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D14]1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D15] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D16] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D17] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D18] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D19] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D20] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D21]1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D22] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D23] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D24] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D25] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D26] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D27] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D28]1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D29] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D30] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D31] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D32] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D33] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D34] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D35]1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D36] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D37] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D38] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D39] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D40] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D41] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D42]1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D43] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D44] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D45] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D46] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D47] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D48] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D49]1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D50] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D51] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D52] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D53] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D54] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D55] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D56]1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D57] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D58] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D59] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D60] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D61] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D62] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D63]1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments. [Figure 5D64] 1 illustrates an exemplary user interface for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments.

[0026] [Figure 5D65] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D66] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D67] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D68] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D69]1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D70] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D71] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D72] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D73] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D74] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D75]1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D76] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D77] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D78] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D79] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D80] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D81]1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D82] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D83] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D84] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D85] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D86] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D87]1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D88] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D89] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D90] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D91] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D92] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D93]1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D94] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D95] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D96] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D97] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments. [Figure 5D98] 1 illustrates an exemplary user interface displayed in a split screen display mode in which a system user interface element changes its appearance state based on one or more behaviors of applications underlying the system user interface element, according to some embodiments.

[0027] [Figure 5D99]1 illustrates a system user interface element having an appearance generated according to the appearance of a portion of the content beneath the system user interface element, according to some embodiments.

[0028] [Figure 6A] FIG. 1 is a flow diagram of a process for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 6B] FIG. 1 is a flow diagram of a process for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 6C] FIG. 1 is a flow diagram of a process for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 6D] FIG. 1 is a flow diagram of a process for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 6E] FIG. 1 is a flow diagram of a process for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments. [Figure 6F] FIG. 1 is a flow diagram of a process for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display in accordance with some embodiments.

[0029] [Figure 7A] FIG. 1 is a flow diagram illustrating a process for navigating from a user interface displayed in a split screen display mode to a different user interface in accordance with some embodiments. [Figure 7B]FIG. 1 is a flow diagram illustrating a process for navigating from a user interface displayed in a split screen display mode to a different user interface in accordance with some embodiments. [Figure 7C] FIG. 1 is a flow diagram illustrating a process for navigating from a user interface displayed in a split screen display mode to a different user interface in accordance with some embodiments. [Figure 7D] FIG. 1 is a flow diagram illustrating a process for navigating from a user interface displayed in a split screen display mode to a different user interface in accordance with some embodiments. [Figure 7E] FIG. 1 is a flow diagram illustrating a process for navigating from a user interface displayed in a split screen display mode to a different user interface in accordance with some embodiments. [Figure 7F] FIG. 1 is a flow diagram illustrating a process for navigating from a user interface displayed in a split screen display mode to a different user interface in accordance with some embodiments. [Figure 7G] FIG. 1 is a flow diagram illustrating a process for navigating from a user interface displayed in a split screen display mode to a different user interface in accordance with some embodiments. [Figure 7H] FIG. 1 is a flow diagram illustrating a process for navigating from a user interface displayed in a split screen display mode to a different user interface in accordance with some embodiments. [Figure 7I] FIG. 1 is a flow diagram illustrating a process for navigating from a user interface displayed in a split screen display mode to a different user interface in accordance with some embodiments.

[0030] [Figure 8] FIG. 1 is a flow diagram illustrating a method for navigating between an application user interface, an application switcher user interface, and a home screen user interface according to some embodiments.

[0031] [Figure 9A] 1 illustrates exemplary thresholds for navigating between different user interfaces according to some embodiments. [Figure 9B] 1 illustrates exemplary thresholds for navigating between different user interfaces according to some embodiments. [Figure 9C] 1 illustrates exemplary thresholds for navigating between different user interfaces according to some embodiments.

[0032] [Figure 10A] FIG. 2 is a flow diagram illustrating a method for navigating between user interfaces according to some embodiments. [Figure 10B] FIG. 2 is a flow diagram illustrating a method for navigating between user interfaces according to some embodiments. [Figure 10C] FIG. 2 is a flow diagram illustrating a method for navigating between user interfaces according to some embodiments. [Figure 10D] FIG. 2 is a flow diagram illustrating a method for navigating between user interfaces according to some embodiments.

[0033] [Figure 11A] FIG. 1 is a flow diagram of a process for navigating between user interfaces based on multi-touch gestures according to some embodiments. [Figure 11B] FIG. 1 is a flow diagram of a process for navigating between user interfaces based on multi-touch gestures according to some embodiments. [Figure 11C] FIG. 1 is a flow diagram of a process for navigating between user interfaces based on multi-touch gestures according to some embodiments. [Figure 11D] FIG. 1 is a flow diagram of a process for navigating between user interfaces based on multi-touch gestures according to some embodiments. [Figure 11E] FIG. 1 is a flow diagram of a process for navigating between user interfaces based on multi-touch gestures according to some embodiments. [Figure 11F] FIG. 1 is a flow diagram of a process for navigating between user interfaces based on multi-touch gestures according to some embodiments.

[0034] [Figure 12A] FIG. 2 is a flow diagram of a method for performing a system action (e.g., navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application) according to some embodiments. [Figure 12B] FIG. 2 is a flow diagram of a method for performing a system action (e.g., navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application) according to some embodiments. [Figure 12C] FIG. 2 is a flow diagram of a method for performing a system action (e.g., navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application) according to some embodiments. [Figure 12D] FIG. 2 is a flow diagram of a method for performing a system action (e.g., navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application) according to some embodiments. [Figure 12E] FIG. 2 is a flow diagram of a method for performing a system action (e.g., navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application) according to some embodiments. [Figure 12F] FIG. 2 is a flow diagram of a method for performing a system action (e.g., navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application) according to some embodiments.

[0035] [Figure 13A]FIG. 1 is a flow diagram of a method for displaying a system user interface element (e.g., a home affordance) with different appearance states based on one or more behaviors of an application(s) underlying the system user interface element, according to some embodiments. [Figure 13B] FIG. 1 is a flow diagram of a method for displaying a system user interface element (e.g., a home affordance) with different appearance states based on one or more behaviors of an application(s) underlying the system user interface element, according to some embodiments. [Figure 13C] FIG. 1 is a flow diagram of a method for displaying a system user interface element (e.g., a home affordance) with different appearance states based on one or more behaviors of an application(s) underlying the system user interface element, according to some embodiments. [Figure 13D] FIG. 1 is a flow diagram of a method for displaying a system user interface element (e.g., a home affordance) with different appearance states based on one or more behaviors of an application(s) underlying the system user interface element, according to some embodiments. [Figure 13E] FIG. 1 is a flow diagram of a method for displaying a system user interface element (e.g., a home affordance) with different appearance states based on one or more behaviors of an application(s) underlying the system user interface element, according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0036] Conventional methods of navigating between user interfaces, particularly between application and system user interfaces (e.g., a home screen user interface, or an application switcher user interface), often require multiple separate inputs (e.g., gestures and button presses, etc.) and irreversible, separate user interface transitions. The following embodiments provide a single gesture that dynamically adjusts and prompts navigation to different user interfaces (e.g., recently opened applications, a home screen user interface, and an application switcher user interface) based on different criteria (e.g., different criteria based on the position, timing, and movement parameters of the touch and / or displayed user interface objects). In addition, the following embodiments provide real-time visual feedback to indicate which user interface the user is navigating while performing a single gesture navigation input. This improves the accuracy of user navigation by, for example, allowing the user the opportunity to complete the input before the input is completed to mitigate mistakes by changing the characteristics of the input before lift-off. This in turn avoids undesirable navigation events and saves time and battery life.

[0037] Furthermore, when operating larger devices (e.g., tablet computers), the user's hands are often engaged in holding the device (e.g., supporting the device from both sides), making it difficult to perform navigation gestures that must be initiated from a location on the device that is away from the orientation of the user's hands. Operating larger devices with a single hand is similarly difficult because the hand must be engaged in supporting the device. The following embodiments improve user interface navigation on larger devices by providing inputs that allow the display of an application dock as a user-defined location along one or more edges on the device (e.g., an affordance that displays multiple application icons for opening / navigating to a particular application). This allows the user to access the application dock without having to reposition the hand on the device (e.g., in a position proximal to wherever the hand is located on the device). This saves time when operating the device (e.g., by avoiding the need for the user to reposition the hand before invoking and / or interacting with the application dock), which in turn saves battery life on the device.

[0038] Additionally, the following embodiments provide gestures that prompt navigation to different user interfaces (e.g., recently opened applications, a home screen user interface, and an application switcher user interface) within a sub-portion of a split screen user interface or across the entire screen based on different criteria (e.g., different criteria based on contact and / or position, timing, movement parameters of displayed user interface objects), thereby providing easy access to navigation functions of the device without cluttering the user interface with additional displayed controls, reducing the amount of time and number of inputs required to achieve an intended screen configuration, as well as reducing the power usage and improving battery life of the device.

[0039] Additionally, the following embodiments facilitate navigation from an application user interface to another user interface outside of the application, e.g., to a different application or to a system user interface (e.g., a home screen), or perform an action within an application based on a gesture (e.g., a gesture performed with multiple simultaneously detected contacts) initiated from the application user interface. In these embodiments, the outcome of the gesture is that multiple different sets of criteria (e.g., criteria based on the gesture type performed by the contacts, the total number of simultaneously detected contacts, the location, timing, and / or movement parameters of the contacts, and / or the user interface object to be displayed) are satisfied by the gesture (e.g., upon termination of the gesture). When determining the destination state of the device (e.g., which action to perform and / or which user interface to display), the input gesture is continuously evaluated against different sets of criteria. Based on the input detected up to this point, a continuous display is provided to indicate the possible destination state of the device, and dynamic visual feedback provides an opportunity for the user to adjust the input to modify the actual destination state of the device reached after termination of the input. By using a different set of criteria to determine the final destination state of the device (e.g., the final action to be performed and / or the final user interface to be displayed), a user may be able to use fluid gestures to modify intermediate streams to achieve an intended result (e.g., either because the user has decided to make the change they want to achieve, or because the user has realized based on device feedback that the user is providing incorrect input for the intended result).This avoids the need for the user to release the effects of an unintended gesture and then re-initiate the gesture, making the user device's interface more efficient (e.g., by assisting the user in providing the input necessary to achieve the intended result and reducing user errors when operating / interacting with the device), which in turn allows the user to use the device more quickly and efficiently, reducing the device's power usage and improving battery life.

[0040] Further, the following embodiments provide an intuitive way to enable edge protection against inadvertent triggering of a system operation that replaces a split screen user interface displaying two applications with a system user interface, where edge protection is enabled independently on one or both of the applications. Enabling edge protection independently on applications on both sides of the split screen while simultaneously allowing the system user interface to replace the system operation that replaces the entire split screen user interface enhances device usability, makes user-device interaction more efficient (e.g., by providing easy access to navigation features of the device, by helping the user achieve intended results with fewer required inputs, and by using additional displayed controls to provide additional control options without cluttering the user interface), reduces user errors when operating the device (e.g., by selectively using gesture criteria extended to portions of the user interface to avoid inadvertent triggering of a system operation), and further reduces power usage and improves device battery life by allowing the user to use the device more quickly and efficiently.

[0041] Additionally, as described in the following embodiments, a system user interface element that is displayed on a split screen user interface and that overlaps two applications with separate behaviors associated with the system user interface element will have a different appearance depending on the behavior of the application underneath the system user interface element when the applications are resized onto the split screen user interface. The appearance of the system user interface element provides useful visual feedback to help the user provide the appropriate input to achieve a desired result and reduce user errors when operating on the device, thereby creating a more efficient human-machine interface. In battery-operated electronic devices, providing useful visual feedback and reducing user errors when navigating between user interfaces within a split screen display mode and / or in and out of a split screen display mode will conserve power and increase the time between battery charges.

[0042] In the following, Figures 1A, 1B, 2, and 3 provide a description of an exemplary device. Figures 4C-4E show examples of dynamic intensity thresholds. Figures 4A-4B, 5A1-5A29, 5B1-5B36, 5C1-5C59, 5D1-5D99 show exemplary user interfaces for navigating between user interfaces, displaying a dock or performing actions within an application, and showing system user interface elements such as home affordances. Figures 6A-6F show a flow diagram of a method for displaying a dock with multiple application icons at variable positions along one or more edges of a touch-sensitive display. Figures 7A-7I show a flow diagram of a method for navigating to a different user interface from a user interface displayed in a split-screen display mode. Figures 11A-11F show a flow diagram of a process for navigating between user interfaces based on multi-touch gestures. 12A-12F are flow diagrams of a method for performing a system action (e.g., navigating from an application user interface displayed in a split screen display mode to a different user interface external to the application). FIGs. 13A-13E are flow diagrams of a method for displaying a system user interface element (e.g., home affordances) with different appearance states based on one or more behaviors of the application(s) underlying the system user interface element. The user interfaces of FIGs. 5A1-5A29, 5B1-5B36, 5C1-5C59, 5D1-5D99 are used to illustrate the processes of FIGs. 6A-6F, 7A-7I, 11A-11F, 12A-12F, and 13A-13E. FIG. 8 is a flow diagram illustrating various criteria used to navigate between user interfaces, according to some embodiments. FIGs. 9A-9C illustrate example thresholds for navigating between different user interfaces. FIGs. 10A-10D are flow diagrams illustrating various criteria used to navigate between user interfaces, according to some embodiments. Exemplary Devices

[0043] Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments being described. However, it will be apparent to those skilled in the art that the various embodiments described may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

[0044] In this specification, terms such as first, second, etc. are used in some examples 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 unless the context clearly indicates otherwise.

[0045] 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. 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 dictates otherwise. It should also be understood that as used herein, the term "and / or" 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.

[0046] As used herein, the term "if" is optionally interpreted to mean "when," "upon," "in response to determining," or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if [a stated condition or event] is detected" are optionally interpreted to mean "upon determining" or "in response to determining," or "upon detecting [the stated condition or event]" or "in response to detecting [the stated condition or event]," depending on the context.

[0047] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad), are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad).

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

[0049] The device typically supports a variety of applications, such as one or more of note-taking applications, 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, training support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music player applications, and / or digital video player applications.

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

[0051] Attention is now directed to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating a portable multifunction device 100 (shown as device 11 in FIGS. 5D1-5D98) with a touch-sensitive display system 112, according to some embodiments. Touch-sensitive display system 112 may conveniently be referred to as a "touch screen" or simply as a touch-sensitive display. Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input 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 touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

[0052] 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 feels a tactile sensation such as a "down-click" or "up-click" even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user'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 produces the described sensory perception for a typical (or average) user.Using tactile output to provide haptic feedback to the user can improve usability of the device and make the user-device interface more efficient (e.g., by helping the user provide appropriate inputs when operating / interacting with the device and reducing user errors), as well as reducing power usage and improving the device's battery life by allowing the user to use the device more quickly and efficiently.

[0053] In some embodiments, the tactile output pattern specifies characteristics of the tactile output, such as the amplitude of the tactile output, the shape of the movement waveform of the tactile output, the frequency of the tactile output, and / or the duration of the tactile output.

[0054] When tactile outputs having different tactile output patterns are generated by the device (e.g., via one or more tactile output generators that move a movable mass to generate the tactile output), the tactile outputs may cause different tactile sensations when a user holds or touches the device. When the user's sensations are based on the user's perception of the tactile output, most users are able to identify changes in the waveform, frequency, and amplitude of the tactile output generated by the device. Thus, the waveform, frequency, and amplitude can be adjusted to indicate to the user that different actions have been performed. Thus, in some situations, tactile output having a tactile output pattern designed, selected, and / or developed to simulate the properties (e.g., size, material, weight, stiffness, smoothness, etc.), behaviors (e.g., vibration, displacement, acceleration, rotation, expansion, etc.), and / or interactions (e.g., collision, adhesion, repulsion, attraction, friction, etc.) of objects in a given environment (e.g., a user interface including graphical features and objects, a simulated physical environment having virtual boundaries and virtual objects, an actual physical environment having physical boundaries and physical objects, and / or any combination of the above) provides a user with useful feedback that reduces input errors and increases the efficiency of a user's operation of the device. Additionally, the tactile output is optionally generated to correspond to feedback unrelated to simulated physical properties, such as input thresholds or object selection. In some situations, such tactile output provides a user with useful feedback that reduces input errors and increases the efficiency of a user's operation of the device.

[0055] In some embodiments, a tactile output with a suitable tactile output pattern serves as a cue to the appearance of an event of interest behind the scene in a user interface or device. Examples of events of interest include activation of an affordance (e.g., a real button, a virtual button, or a toggle switch) provided on the device or in the user interface, success or failure of a requested action, reaching or crossing a boundary in the user interface, entering a new state, switching input focus between objects, activating a new mode, reaching or crossing an input threshold, detection or recognition of a type of input or gesture, etc. In some embodiments, a tactile output is provided to act as a warning or alert to an impending event or outcome that will occur unless a redirection or interrupt input is detected in a timely manner. Tactile output is also used in other contexts to improve the user experience, improve the accessibility of the device to users with visual or motor impairments or other accessibility needs, and / or improve the efficiency and functionality of the user interface and / or device. The tactile output, optionally accompanied by audio output and / or visible user interface changes, further enhances the user's experience when interacting with the user interface and / or device, facilitates better communication of information about the state of the user interface and / or device, reduces input errors, and increases the efficiency of the user's operation of the device.

[0056] 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, firmware, or a combination thereof, including one or more signal processing circuits and / or application specific integrated circuits.

[0057] Memory 102 optionally includes high-speed random access memory, and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU(s) 120 and peripherals interface 118, is optionally controlled by memory controller 122.

[0058] A peripheral interface 118 may be used to couple input and output peripherals of the device with the CPU(s) 120 and memory 102. The one or more processors 120 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.

[0059] In some embodiments, peripherals interface 118, CPU(s) 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0060] The radio frequency (RF) circuitry 108 transmits and receives RF signals, also referred to as 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, etc. The RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices, by wireless communication. Radio communication options include 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), and code division multiple access (CDMA).Wireless technology such as IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11n, voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE)), instant messaging and presence services (e.g., IEEE 802.11b), instant messaging and presence services (e.g., IEEE 802.11c), instant messaging and presence services (e.g., IEEE 802.11b ... The present invention may use any of a number of communications standards, protocols, and technologies, including, but not limited to, Intermediate System (IS) Intermediate Message Service (IMPS), and / or Short Message Service (SMS), or any other suitable communications protocol, including communications protocols not yet developed as of the filing date of this document.

[0061] 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 electrical signals converted from 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 (e.g., 212, FIG. 2). The headset jack provides an interface between audio circuitry 110 and a detachable audio input / output peripheral such as an output-only headphone or a headset with both an output (e.g., one-ear or binaural headphones) and an input (e.g., a microphone).

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

[0063] Touch-sensitive display system 112 provides an input and output interface between the device and a user. Display controller 156 receives electrical signals from and / or transmits electrical signals to touch-sensitive display system 112. Touch-sensitive display system 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 a user interface object. As used herein, the term "affordance" refers to a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to input directed towards the graphical user interface object). Examples of user-interactive graphical user interface objects include, but are not limited to, a button, a slider, an icon, a selectable menu item, a switch, a hyperlink, or other user interface control.

[0064] Touch-sensitive display system 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and / or tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and / or instruction sets in memory 102) detect contacts (and any movement or breaking of contact) on touch-sensitive display system 112 and translate the detected contacts into interactions with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touch-sensitive display system 112. In some embodiments, the point of contact between touch-sensitive display system 112 and the user corresponds to the user's finger or stylus.

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

[0066] Touch-sensitive display system 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen video resolution exceeds 400 dpi (e.g., 500 dpi, 800 dpi, or higher). A user optionally contacts touch-sensitive display system 112 using any suitable object or accessory, such as a stylus, finger, or the like. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on a touchscreen than that of a stylus. In some embodiments, the device translates the rough finger input into precise pointer / cursor positions or commands to perform the action desired by the user.

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

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

[0069] 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(s) 164 optionally include a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor(s) 164 receive light from the environment, projected through one or more lenses, and convert the light into data representing an image. In conjunction with imaging module 143 (also referred to as a camera module), light sensor(s) 164 optionally captures still images and / or video. In some embodiments, the light sensor is located on the back of device 100, opposite touch-sensitive display system 112 on the front of the device, so that the touch screen can be used as a viewfinder for still and / or video image acquisition. In some embodiments, another light sensor is placed on the front of the device so that an image of the user is captured (e.g., for a selfie, for a video conference while the user views other video conference participants on the touch screen, etc.).

[0070] 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(s) 165 optionally include 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(s) 165 receive 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 touchscreen display system 112, which is located on the front of device 100.

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

[0072] 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. In some embodiments, tactile output generator(s) 167 include 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). Tactile output generator(s) 167 receive tactile feedback generation instructions from haptic feedback module 133 and generate tactile outputs on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed with 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 horizontally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, the at least one tactile output generator sensor is located on the back of device 100, opposite touch-sensitive display system 112, which is located on the front of device 100.

[0073] 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 a touchscreen display in portrait or landscape view based on analysis of data received from the one or more accelerometers. In addition to accelerometer(s) 168, device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information regarding the location and orientation (e.g., portrait or landscape) of device 100.

[0074] In some embodiments, the software components stored in memory 102 include an operating system 126, a communications module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a haptic feedback module (or instruction set) 133, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and applications (or instruction set) 136. Additionally, in some embodiments, as shown in Figures 1A and 3, memory 102 stores device / global internal state 157. Device / global internal state 157 includes one or more of: active application state, which indicates which applications, if any, are currently active; display state, which indicates what applications, views, or other information are occupying various areas of touch-sensitive display system 112; sensor state, which includes information obtained from the device's various sensors and other input or control devices 116; and position and / or location information regarding the device's position and / or orientation.

[0075] Operating system 126 (e.g., an embedded operating system such as iOS™, Darwin, RTXC, LINUX™, UNIX™, OS X™, WINDOWS™, or VxWorks™) includes various software components and / or drivers for controlling and managing overall system tasks (e.g., memory management, storage device control, power management, etc.) and facilitating communication between various hardware and software components.

[0076] The communications module 128 also includes various software components for facilitating communication with other devices via one or more external ports 124 and for processing 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 directly to other devices or indirectly via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors identical to, similar to, and / or compatible with the 30-pin connectors used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. In some embodiments, the external ports are Lightning™ connectors identical to, similar to, and / or compatible with the Lightning™ connectors used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California.

[0077] Contact / motion module 130 optionally detects contact with touch-sensitive display system 112 (in cooperation with display controller 156), and with other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes software components for performing various operations related to detecting contact (e.g., by a finger or stylus), such as determining if contact has occurred (e.g., detecting a finger down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a proxy 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 stylus 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.

[0078] 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 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 one or more finger drag events, followed by a finger up (lift off) event. Similarly, taps, swipes, drags, and other gestures are optionally detected by detecting a particular contact pattern with respect to the stylus with respect to the stylus.

[0079] In some embodiments, detecting a finger tap gesture depends on the length of time between detecting a finger down event and detecting a finger up event, but is not related to the strength of the finger contact between detecting a finger down event and detecting a finger up event. In some embodiments, a tap gesture is detected according to determining that the length of time between a finger down event and a finger up event is less than a predefined value (e.g., less than 0.1, 0.2, 0.3, 0.4, or 0.5 seconds), regardless of whether the strength of the finger contact during the tap meets a given intensity threshold (greater than a nominal contact detection intensity threshold), such as a light or deep pressure intensity threshold. Thus, a finger tap gesture may satisfy certain input criteria that do not require that the characteristic intensity of the contact meet a given intensity threshold in order for the particular input criterion to be met. For clarity, a finger contact in a tap gesture generally needs to meet a nominal contact detection intensity threshold below which the contact is not detected in order to detect a finger down event. A similar analysis applies to detecting a tap gesture or other contact with a stylus. In cases where the device is capable of detecting contact of a finger or stylus hovering over the touch-sensitive surface, the nominal contact-detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch-sensitive surface.

[0080] In a similar manner, the same concepts apply to other types of gestures. For example, swipe gestures, pinch gestures, de-pinch gestures, and / or long press gestures are optionally detected based on meeting criteria that are either unrelated to the intensity of the contacts included in the gesture or do not require the contacts performing the gesture to reach an intensity threshold in order to be recognized. For example, swipe gestures are detected based on the amount of movement of one or more contacts, pinch gestures are detected based on the movement of two or more contacts towards each other, de-pinch gestures are detected based on the movement of two or more contacts away from each other, and long press gestures are detected based on a duration of contact on the touch-sensitive surface that is less than a threshold amount of movement. Thus, a statement that a particular gesture recognition criterion does not require that the intensity of a contact(s) meet a corresponding intensity threshold in order for the particular gesture recognition criterion to be satisfied means that the particular gesture recognition criterion can be satisfied when the contact(s) in the gesture do not reach the corresponding intensity threshold, and can also be satisfied in situations where one or more of the contacts in the gesture reach or exceed the corresponding intensity threshold. In some embodiments, a tap gesture is detected based on a determination that a finger down event and a finger up event are detected within a predetermined time period, regardless of whether the contacts are above or below the respective intensity thresholds during the predetermined time period, and a swipe gesture is detected based on a determination that a movement of the contact is greater than a predetermined magnitude, even if the contacts exceed the respective intensity thresholds at the end of the movement of the contact. Even in implementations in which detection of gestures is affected by the strength of the contact performing the gesture (e.g., the device detects a long press more quickly when the intensity of the contact exceeds an intensity threshold, or the device is slow to detect a tap input when the intensity of the contact is higher), detection of those gestures does not require that the contact reach a particular intensity threshold, so long as the criteria for recognizing the gesture can be met in situations in which the contact does not reach a particular intensity threshold (e.g., even if the amount of time it takes to recognize the gesture varies).

[0081] The contact intensity threshold, duration threshold, and movement threshold are combined in various different combinations in some situations to create heuristics for distinguishing between two or more different gestures directed at the same input element or region, thereby enabling multiple different interactions with the same input element to provide a richer set of user interactions and responses. A statement that a particular set of gesture recognition criteria does not require the intensity of the contact(s) to meet the respective intensity threshold for that particular gesture recognition criterion to be satisfied does not preclude simultaneously evaluating other intensity-dependent gesture recognition criteria to identify other gestures having criteria that are satisfied when the gesture includes a contact having an intensity that exceeds the respective intensity threshold. For example, in some situations, a first gesture recognition criterion for a first gesture that does not require the intensity of the contact(s) to meet the corresponding intensity threshold for the first gesture recognition criterion to be satisfied is in competition with a second gesture recognition criterion for a second gesture that is dependent on the contact(s) reaching the corresponding intensity threshold. In such a competition, a gesture is optionally not recognized as satisfying the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are satisfied first. For example, if the contact reaches the corresponding intensity threshold before it moves the predetermined amount of movement, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves the predetermined amount of movement before it reaches the corresponding intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such a situation, the first gesture recognition criteria for the first gesture still do not require that the intensity of the contact(s) meet the corresponding intensity threshold for the first gesture recognition criteria to be satisfied, because if the contact remains below the corresponding intensity threshold until the end of the gesture (e.g., a swipe gesture with a contact that does not increase in intensity to above the corresponding intensity threshold), the gesture will have been recognized by the first gesture recognition criteria as a swipe gesture.In that way, a particular gesture recognition criterion that does not require that the intensity of the contact(s) meet a corresponding intensity threshold in order for the particular gesture recognition criterion to be satisfied may still be dependent on the intensity of the contact with respect to an intensity threshold in the sense that (A) in some circumstances it may ignore the intensity of the contact with respect to an intensity threshold (e.g., for a tap gesture) and / or (B) in some circumstances the particular gesture recognition criterion (e.g., for a long press gesture) will not function if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognizes an input as corresponding to an intensity-dependent gesture before the particular gesture recognition criterion recognizes a gesture corresponding to the input (e.g., for a long press gesture that competes with a deep press gesture for recognition).

[0082] Graphics module 132 includes various known software components for rendering and displaying graphics on touch-sensitive display system 112 or other display, including components for modifying 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.

[0083] In some embodiments, graphics module 132 stores data representing the graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives one or more codes specifying the graphics to be displayed, including, as appropriate, coordinate data and other graphic characteristic data, from an application or the like, and then generates screen image data for output to display controller 156.

[0084] The haptic feedback module 133 includes various software components that generate instructions (e.g., instructions used by the haptic feedback controller 161) to create tactile outputs at one or more locations on the device 100 using the tactile output generator(s) 167 in response to user interaction with the device 100.

[0085] 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 137, email 140, IM 141, browser 147, and any other application requiring text input).

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

[0087] Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: ● a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ● Videoconferencing module 139, ● an email client module 140; ● Instant messaging (IM) module 141; ● Training support 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 price 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; ● a widget creation module 150 for creating 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.

[0088] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA® enabled applications, encryption, digital rights management, voice recognition, and voice duplication.

[0089] Contacts module 137, along with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, includes executable instructions (e.g., stored in memory 102 or in the application internal state 192 of contacts module 137 in memory 370) for managing an address book or contact list, including adding a name(s) to the address book, deleting a name(s) from the address book, associating phone number(s), email address(es), physical address(es), or other information with a name, associating an image with a name, categorizing and sorting names, providing phone numbers and / or email addresses to initiate and / or facilitate communication by telephone 138, video conference 139, email 140, or IM 141, and the like.

[0090] In cooperation with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions for entering a sequence of characters corresponding to a telephone number, accessing one or more telephone numbers in address book 137, modifying an entered telephone number, dialing each telephone number, conducting a conversation, and disconnecting or hanging up when the conversation is completed. As discussed above, the wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0091] In cooperation with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, light sensor(s) 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 to initiate, conduct, and terminate a videoconference between a user and one or more other participants according to the user's commands.

[0092] In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, email client module 140 contains executable instructions for creating, 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.

[0093] In cooperation with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, instant message module 141 includes executable instructions for entering a series of characters corresponding to an instant message, modifying previously entered characters, sending each instant message (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephone-based instant messaging, or using XMPP, SIMPLE, Apple Push Notification Service (APNs), or IMPS for Internet-based instant messaging), receiving instant messages, and viewing 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 messaging (e.g., messages sent using SMS or MMS) and Internet-based messaging (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).

[0094] In cooperation with the RF circuitry 108, the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154, and the video and music player module 152, the training support module 142 includes executable instructions to create workouts (e.g., having time, distance, and / or calorie burn goals), communicate with training sensors (in the sports device and the smart watch), receive training sensor data, calibrate sensors used to monitor the workouts, select and play music for the workouts, and display, store, and transmit training data.

[0095] Camera module 143, along with touch-sensitive display system 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact module 130, graphics module 132, and image management module 144, contain 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, and / or delete still images or videos from memory 102.

[0096] Image management module 144, along with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, contain 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.

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

[0098] Calendar module 148, along with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, contain executable instructions to create, display, modify, and store calendars and data associated with the calendars (e.g., calendar entries, to-do lists, etc.) according to a user's instructions.

[0099] Widget modules 149, along with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, are optionally mini-applications downloaded and used by a user (e.g., weather widget 149-1, stock quotes widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5), or mini-applications created by a user (e.g., user-created widget 149-6). 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! Widgets).

[0100] In cooperation with RF circuitry 108, touch-sensing display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget creation module 150 contains executable instructions for creating widgets (e.g., turning user-specified portions of a web page into widgets).

[0101] In cooperation with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 contains executable instructions to search 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 commands.

[0102] In conjunction with touch-sensitive display system 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 recorded music or other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions to display, present, or otherwise play videos (e.g., on touch-sensitive display system 112 or on an external display connected wirelessly or via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (a trademark of Apple Inc.).

[0103] In cooperation with the touch-sensitive display system 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 according to user commands.

[0104] In conjunction with RF circuitry 108, touch-sensitive display system 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 can be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data about stores and other points of interest at or near a particular location, and other location-based data) in accordance with a user's instructions.

[0105] In conjunction with touch-sensitive display system 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 executable instructions that enable a user to access, view, receive (e.g., by streaming and / or downloading), and play (e.g., on touch screen 112 or on an external display connected wirelessly or via external port 124) online videos in one or more file formats, such as H.264, and send and otherwise manage emails with 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.

[0106] 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 (i.e., 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 above-identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.

[0107] In some embodiments, device 100 is a device in which operation of a predefined set of functions on the device is performed exclusively via 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.

[0108] The set of predefined functions performed only through the touchscreen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 to a main menu, 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.

[0109] 1B is a block diagram illustrating example components for event processing, according to some embodiments. In some embodiments, memory 102 (in FIG. 1A) or 370 (in FIG. 3) includes an event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of applications 136, 137-155, 380-390 described above).

[0110] Event sorter 170 receives the event information and determines which application 136-1 to deliver the event information to and application view 191 of application 136-1. Event sorter 170 includes an event monitor 171 and an 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 system 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 which application view 191 the event information is delivered to.

[0111] In some embodiments, application internal state 192 includes additional information such as one or more of resume information to be used when application 136-1 resumes execution, user interface state information indicating or ready to display information being displayed by application 136-1, state cues that allow a user to return to a previous state or view of application 136-1, and redo / undo cues of previous actions taken by the user.

[0112] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user's touch on touch-sensitive display system 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (via audio circuitry 110). Information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.

[0113] In some embodiments, event monitor 171 sends a request to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or for longer than a predetermined period of time).

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

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

[0116] Another aspect of a user interface associated with an application is the set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the respective application) in which the touch is detected optionally corresponds to a programmatic level within the programmatic or view hierarchy of the application. For example, the lowest level view in which the touch is detected is optionally referred to as a hit view, and the set of events that are 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.

[0117] Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest level view in which the initiating sub-event occurs (i.e., the first sub-event in a series of sub-events that form an event or potential event). Once a hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

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

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

[0120] 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 is part of another module stored in memory 102, such as contact / motion module 130.

[0121] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each including instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, each event handler 190 includes one or more of data updaters 176, object updaters 177, GUI updaters 178, and / or event data 179 received from event sorter 170. Event handlers 190 optionally utilize or call data updaters 176, object updaters 177, or GUI updaters 178 to update application internal state 192. Instead, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in each application view 191.

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

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

[0124] The event comparator 184 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 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a sequence of predefined sub-events), such as event 1 (187-1) and event 2 (187-2). In some embodiments, the sub-events in event 187 include, for example, touch start, touch end, touch movement, 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 predefined stage on the displayed object, a first lift-off (touch end) for a predefined stage, a second touch (touch start) for a predefined stage on the displayed object, and a second lift-off (touch end) for a predefined stage. In another example, a definition of event 2 (187-2) is a drag on a displayed object. Drag includes, for example, a touch (or contact) of a predetermined degree on a displayed object, a movement of the touch across the touch-sensitive display system 112, and a lift-off of the touch (end of the touch). In some embodiments, the event also includes information regarding one or more associated event handlers 190.

[0125] In some embodiments, event definition 187 includes a definition of the event for each user interface object. In some embodiments, event comparator 184 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 system 112, when a touch is detected on touch-sensitive display system 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 to activate. For example, event comparator 184 selects the event handler associated with the sub-event and object that triggers the hit test.

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

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

[0128] In some embodiments, each event recognizer 180 includes metadata 183 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 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact with each other or are enabled to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how sub-events are delivered to various levels in a view or programmatic hierarchy.

[0129] In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more particular sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and postponing sending) the sub-events to the respective hit view. In some embodiments, the event recognizer 180 pops a flag associated with the recognized event, and the event handler 190 associated with the flag catches the flag and performs a predefined process.

[0130] In some embodiments, the event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver 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 a predetermined process.

[0131] In some embodiments, data updater 176 creates and updates data used by application 136-1. For example, data updater 176 updates phone numbers used by contacts module 137 or stores video files used by video and music player module 152. In some embodiments, object updater 177 creates and updates objects used by application 136-1. For example, object updater 177 creates new user interface objects or updates the positions of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on the touch-sensitive display.

[0132] In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0133] 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 input devices, 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.

[0134] FIG. 2 illustrates portable multifunction device 100 having a touch screen (e.g., touch-sensitive display system 112, FIG. 1A ), according to some embodiments. The touch screen optionally displays one or more graphics in user interface (UI) 200. In these embodiments, as well as those described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of the one or more graphics is performed when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upwards and / or downwards), and / or rolling of a finger in contact with device 100 (right to left, left to right, upwards and / or downwards). In some implementations or situations, accidental contact with a graphic does not select that graphic: for example, a swipe gesture sweeping over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

[0135] 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 in a GUI displayed on a touch screen display.

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

[0137] FIG. 3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or commercial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. Device 300 includes input / output (I / O) interfaces 330, including a display 340, which is typically a touchscreen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, as well as a touchpad 355, a tactile output generator 357 for generating tactile output on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A), sensors 359 (e.g., light sensors, acceleration sensors, proximity sensors, touch-sensitive sensors, and / or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, ​​word processing module 384, website creation module 386, disk authoring module 388, and / or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store those modules.

[0138] Each of the above-identified elements in FIG. 3 is optionally stored in one or more of the memory devices mentioned above. Each of the above-identified modules corresponds to an instruction set that performs the functions described above. The above-identified modules or programs (i.e., instruction sets) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of those modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 370 optionally stores additional modules and data structures not described above.

[0139] Attention is now directed to embodiments of a user interface (“UI”) that is optionally implemented on portable multifunction device 100.

[0140] 4A shows an exemplary user interface for a menu of applications on portable multifunction device 100, according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof: signal strength indicator(s) for wireless communication(s), such as cellular and Wi-Fi signals; ●Time, ●Bluetooth (registered trademark) indicator, ● Battery status indicator, Tray 408 with icons of frequently used applications, such as: ○ An icon 416 for the phone module 138, labeled “Phone”, optionally including an indicator 414 of the number of missed calls or voicemail messages; ○ An icon 418 of the email client module 140, labeled “Mail”, optionally including an indicator 410 of the number of unread emails; ○ An icon 420 for the Browser module 147, labeled "Browser"; and ○ An icon 422 of the video and music player module 152 labeled "Music", and ● Icons of other applications, such as: ○ Icon 424 of IM module 141, labeled "Messages"; ○ Icon 426 of the Calendar module 148, labeled "Calendar", ○ Icon 428 of the image management module 144, labeled "Photos"; ○ An icon 430 of the camera module 143, labeled “camera”; ○ Icon 432 of the online video module 155, labeled "Online Video"; Icon 434 of Stock Price Widget 149-2, labeled "Stock Price" ○ Icon 436 of the map module 154, labeled "Map"; ○ Icon 438 of weather widget 149-1, labeled "Weather"; ○ Icon 440 of alarm clock widget 149-4, labeled "Clock"; ○ Icon 442 of Training Support Module 142, labeled "Training Support"; ○ An icon 444 of the Notes module 153, labeled "Notes"; and ○ An icon 446 for a settings application or module that provides access to settings related to the device 100 and its various applications 136.

[0141] 4A are merely examples. For example, other labels are optionally used for the various application icons. In some embodiments, the label for each application icon includes the name of the application that corresponds to the respective application icon. In some embodiments, the label for a particular application icon is different from the name of the application that corresponds to that particular application icon.

[0142] FIG. 4B illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355, FIG. 3) separate from a display 450. Although many of the following examples are given with reference to input on touchscreen display 112 (where the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface separate from the display, as shown in FIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) has a major axis (e.g., 452 in FIG. 4B) that corresponds to a major axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). According to those embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B) at locations that correspond to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this manner, when the touch-sensitive surface is separate from the display, user input (e.g., contacts 460 and 462, and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B ) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B ) of the multifunction device. It is to be understood that similar methods are optionally used for the other user interfaces described herein.

[0143] The term "focus selector" as used herein 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 location marker, the cursor functions as a "focus selector" such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations involving a touchscreen display (e.g., touch-sensitive display system 112 in FIG. 1A or touchscreen in FIG. 4A) that enables direct interaction with user interface elements on the touchscreen display, a contact detected on the touchscreen functions as a "focus selector" such that when an input (e.g., a press input by contact) is detected on the touchscreen display at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface (e.g., by using the tab or arrow keys to move focus from one button to another) without a corresponding cursor movement or contact movement on the touchscreen display. In these implementations, the focus selector moves to follow the movement of focus between various regions of the user interface. Regardless of the specific form taken by the focus selector, the focus selector is generally a user interface element (or a 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, positioning of a focus selector (e.g., a cursor, touch, or selection box) over a corresponding button while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user intends to activate that corresponding button (and not another user interface element shown on the device's display).

[0144] In some embodiments, the device's response to an input detected by the device depends on criteria 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 criteria including both the contact intensity during the input and time-based criteria. For example, for some "deep press" inputs, the intensity of the contact during the input that exceeds a second intensity threshold that is greater than the first intensity threshold for a light press triggers a second response only if a delay time has elapsed between meeting the first intensity threshold and meeting the second intensity threshold. This delay time is typically less than 200 ms (milliseconds) in time (e.g., 40 ms, 100 ms, or 120 ms 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 recognition of a deep press input. 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.

[0145] 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 Publication Nos. 14 / 399,606 and 14 / 624,296, which are incorporated herein by reference in their entireties.

[0146] For example, FIG. 4C illustrates a dynamic intensity threshold 480 that varies over time based in part on the intensity of touch input 476 over time. The dynamic intensity threshold 480 is the sum of two components, a first component 474 that decays over time after a predefined delay time p1 from when touch input 476 is first detected, and a second component 478 that tracks the intensity of touch input 476 over time. The initial high intensity threshold of the first component 474 reduces accidental triggering of a "deep press" response while still allowing an immediate "deep press" response if touch input 476 provides sufficient intensity. The second component 478 reduces unintended 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 476 meets the dynamic intensity threshold 480 (e.g., at point 481 in FIG. 4C). In some embodiments, when the touch input 476 meets a dynamic intensity threshold 480 (eg, at point 481 in FIG. 4C), a "deep press" response is triggered.

[0147] FIG. 4D illustrates another dynamic intensity threshold 486 (e.g., intensity threshold I D ) is shown in FIG. 4D. Two other intensity thresholds are shown: the first intensity threshold I H and the second intensity threshold II L In FIG. 4D, the touch input 484 crosses the first intensity threshold I before time p2. H and a second intensity threshold I L4D, the dynamic intensity threshold 486 decays over time, with the decay occurring after a predefined delay p1 from time 482 (the second intensity threshold I L This type of dynamic intensity threshold begins at time 488 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 Reduce accidental triggering of associated responses.

[0148] FIG. 4E illustrates yet another dynamic intensity threshold 492 (e.g., intensity threshold I D In FIG. 4E, the intensity threshold I L The response associated with the intensity threshold I is triggered after a delay time p2 from when the touch input 490 is first detected. At the same time, the dynamic intensity threshold 492 decays after a predefined delay time p1 from when the touch input 490 is first detected. Thus, the intensity threshold I is triggered after a delay time p1 from when the touch input 490 is first detected. L The decrease in the intensity of the touch input 490 after triggering a response associated with the touch input 490 may occur when the intensity of the touch input 490 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. User Interface and Related Processes

[0149] Attention is now directed to embodiments of user interfaces ("UI") and associated processes that may be implemented on an electronic device, such as portable multifunction device 100 or device 300, that includes a display, a touch-sensitive surface, (optionally) one or more tactile output generators for generating tactile output, and (optionally) one or more sensors for detecting the intensity of contact with the touch-sensitive surface.

[0150] 5A1-5A29 illustrate exemplary user interfaces for displaying a dock with multiple application icons, e.g., at variable positions along one or more edges of a touch-sensitive display. For example, according to some embodiments, a user may be able to summon and interact with a dock in a location close to a current hand position (e.g., without having to significantly shift the current hand position). The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 6A-6C. For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device having touch-sensitive display system 112. In such embodiments, the focus selector is optionally a respective finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., an enantiomeric center of the respective contact or a point associated with the respective contact), or an enantiomeric center of two or more contacts detected on touch-sensitive display system 112. However, similar operations, along with a focus selector, are optionally performed on a device having display 450 and separate touch-sensitive surface 451 in response to detecting contacts on touch-sensitive surface 451 while displaying the user interface shown in the figures on display 450.

[0151] For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device that does not have a home button, and gestures that meet predefined criteria are used to trigger dismissal of the currently displayed user interface and display of a home screen user interface. Although optionally shown in FIGS. 5A1-5A29, in some embodiments, a home button (e.g., a mechanical button, a solid-state button, or a virtual button) is included on the device and is used to trigger dismissal of the currently displayed user interface and display of a home screen user interface (e.g., in response to a single press input) and / or display of a multitasking user interface (e.g., in response to a double press input).

[0152] The home screen user interface includes a number of application icons corresponding to different applications installed on the device. Each of the application icons, when activated by the user (e.g., by a tap input), causes the device to bring up the corresponding application and display the application's user interface (e.g., a default initial user interface or a last displayed user interface) on the display. The dock is a user interface object that includes a subset of application icons selected from the home screen user interface to provide quick access to a small number of frequently used applications. The application icons included in the dock are optionally selected by the user (e.g., via a settings user interface) or automatically selected by the device based on various criteria (e.g., frequency of use or time since last use). In some embodiments, the dock is displayed as part of the home screen user interface (e.g., overlaying the bottom of the home screen user interface, as shown in FIG. 4A). In some embodiments, the dock is displayed over a portion of another user interface (e.g., an application user interface) independent of the home screen user interface in response to a user request (e.g., a gesture that meets the dock display criteria). The application switcher user interface displays representations of multiple recently opened applications (e.g., arranged in order based on when the applications were last displayed), each of which (e.g., a snapshot of the last displayed user interface of each recently opened application) when selected (e.g., by a tap input) causes the device to re-display the last displayed user interface of each recently opened application on the screen.

[0153] 5A1-5A5 illustrate an example embodiment in which an electronic device displays a dock at different locations along an edge of the device depending on the location of a call input (e.g., an edge long press). FIG. 5A1 illustrates an interactive map user interface displayed in a full-screen display mode. A long press gesture (e.g., contact 4202) detected at a location on the left side of the bottom edge of the display remains in a unique location (e.g., touch-down location) for at least a threshold amount of time TT 1 A long press gesture detected at a position to the right of the display's bottom edge (e.g., by contact 4206) causes the display of dock 4204 at a corresponding location along the left side of the device's bottom edge (e.g., bottom centered contact 4202) as shown in FIGS. 5A1-5A2. The dock remains displayed after liftoff of contact 4202 in FIG. 5A3 because the contact did not substantially move (e.g., remained substantially stationary) during input. In contrast, a long press gesture detected at a position to the right of the display's bottom edge (e.g., by contact 4206) causes the display of dock 4204 at a corresponding location along the right side of the device's bottom edge (e.g., bottom centered contact 4206) as shown in FIGS. 5A4-5A5. The dock appears on the right side of the bottom edge of the display in FIG. 5A5, as opposed to the left side of the bottom edge as in FIG. 5A2, because the long press input that invokes the dock is located on the right side of the bottom edge, thereby allowing the user to interact with the dock in a location that is easily and conveniently accessible to the user (e.g., without requiring the user to move their hand on the device to a pre-set location on the device). In some embodiments, invoking the dock requires a long press gesture within an edge region of the touchscreen (e.g., contact is present for at least a threshold amount of time TT). 1Alternatively, the device may respond to a light press gesture within an edge region of the touchscreen that invokes the dock (e.g., requiring the intensity of the contact to be maintained in a fixed position for a certain period of time, and optionally maintaining an intensity below a first threshold intensity greater than the contact-detection intensity threshold, and optionally maintaining an intensity below a first threshold intensity greater than the contact-detection intensity threshold, and optionally maintaining the contact for at least a threshold amount of time TT 1 (not required to be maintained in a fixed position for a period of time).

[0154] 5A4-5A8 illustrate an exemplary embodiment in which a single input (e.g., a multi-part input with continuously held contact 4206) causes the display of a dock and then navigation to an application user interface associated with an application icon displayed within the dock. FIG. 5A4 illustrates an interactive map user interface displayed in a full-screen display mode. As shown in FIGS. 5A4-5A5, a long press gesture with contact 4206 at a location on the right side of the bottom edge of the display causes the dock 4204 to appear in a corresponding location (e.g., contact 4206 centered below) along the right side of the bottom edge of the device, as shown in FIGS. 5A4-5A5. Movement of contact 4206 over email application icon 218 within dock 4204 selects the icon that appears larger in FIG. 5A6 as a result of being selected. Lifting off of contact 4206 while email application icon 218 is selected causes navigation to an email user interface, as shown in FIGS. 5A7-5A8. As shown in FIGS. 5A7-5A8, the display of the email user interface animates and appears to move out of the selected email application icon 218 overlaying the interactive map user interface. After navigation to the email user interface, in FIGS. 5A7-5A8, the dock disappears due to an input that invokes and moves the dock, causing a navigation event. If no lift-off of contact 4206 is detected when contact 4206 moves over email application icon 218, the movement of contact 4206 continues to a position corresponding to phone application icon 216 in the dock such that the email application icon is no longer selected and the phone application icon is selected. If lift-off of contact 4206 is detected when contact 4206 moves off of dock 4204, the device optionally ceases displaying the dock while maintaining the display of the interactive map user interface.

[0155] 5A9-5A10 illustrate an example embodiment in which a long press input on a different edge of the device also causes a dock to appear at a location near the input. FIG. 5A9 illustrates an example email user interface. A long press gesture (e.g., by contact 4208) detected at a location on the lower half of the left edge of the device causes a dock 4204 to appear at a corresponding location along the lower half of the left edge of the device (e.g., contact 4206 centered below), as shown in FIGS. 5A9-5A10. The dock appears on a different edge of the device in FIG. 5A10 because the display invocation of the long press input is located on a different edge, as compared to FIGS. 5A2 and 5A5. The dock also appears in a different orientation, as it appears along a vertical edge of the device instead of a horizontal edge, as compared to FIGS. 5A2 and 5A5.

[0156] 5A9-5A12 show an example embodiment in which the display of the dock is cancelled by lift-off of the calling contact 4208 even though no navigation event occurred as a result of the input. FIG. 5A9 shows an example email user interface. A long press gesture on the lower half of the left edge of the device, including contact 4208 over the MobileFinder email header in FIG. 5A9, causes the display of the dock 4204 along the lower half of the left edge of the device, below contact 4206 in FIG. 5A10. The dock disappears after lift-off of the contact in FIG. 5A12. This is because the contact moves away from the dock in FIGS. 5A10-5A11, e.g., the contact was not positioned over the dock when lift-off occurred.

[0157] 5A13-5A14 illustrate an example embodiment in which a gesture (e.g., a tap or light press) detected within an edge region of a touch screen results in an action within a displayed application user interface rather than causing the display of a dock because the gesture did not meet the long press criteria (e.g., contact lift-off was detected before the contact was maintained for at least a threshold amount of time without substantial movement). FIG. 5A13 illustrates an example email user interface. A tap gesture or light press gesture on the bottom half of the left edge of the device, including contact 4209 over a MobileFinder email header in FIG. 5A13, results in the selection / display of a MobileFinder email in FIG. 5A14 rather than the display of a dock as in FIG. 5A12. It is important to note that the time threshold (e.g., TT 0) required to invoke a system-wide dock display action (and preempt a corresponding email application-specific email selection / display action) is not met. 1 ) was not filled prior to contact lift-off.

[0158] 5A15-5A18 show an example embodiment in which a swipe down hides the dock. FIG. 5A15 shows an interactive map user interface displayed in a full screen display mode. A long press gesture on the right side of the bottom edge of the display, including contact 4212 in FIG. 5A15, causes the display of dock 4204 along the right side of the bottom edge of the device, under contact 4212 in FIG. 5A13. A downward movement of the contact causes the dock to slide off the bottom edge of the display in FIG. 5A17. The dock disappears after lift-off of the contact in FIG. 5A18 because the contact pushes the dock off the display in FIG. 5A16-5A17. In FIG. 5A16, the dock appears in a position below contact 4212, but not centered under contact 4212, because the location of the contact is close to an adjacent vertical edge of the display (e.g., the right edge of the display). In this case, the dock appears adjacent to the adjacent vertical edge of the display.

[0159] 5A19-5A21 show an example embodiment in which a lift-off of a contact causes the dock to expand and move to a predefined position on the display. FIG. 5A19 shows an interactive map user interface displayed in full screen display mode. A long press gesture on the left side of the bottom edge of the display, including contact 4216 in FIG. 5A19, causes the display of the dock 4204 along the left side of the bottom edge of the device, under contact 4216 in FIG. 5A20. After lift-off of contact 4216, the dock moves from position 4204-a in FIG. 5A20 to a predefined position 4204-b in the center of the bottom edge of the display in FIG. 5A21. The dock also expands when displayed in the predefined position compared to displaying at a position defined by the call input.

[0160] 5A22-5A23 show an example embodiment in which the dock is displayed in a default position when a long press gesture is located too close to the edge of the display's edge. FIG. 5A22 shows an interactive map user interface displayed in full screen display mode. A long press gesture on the right side of the bottom edge of the display, including contact 4218 in FIG. 5A22, causes the dock 4204 to be displayed in a default position near the right edge of the bottom edge of the display, and is not centered on contact 4218 in FIG. 5A23, but all of the dock would not be shown on the display if it were centered on contact 4218 (e.g., if the right hand portion of the dock is off to the right of the display).

[0161] 5A22-5A27 show an example embodiment in which a single gesture initiated from the edge of the display causes the display of an application in a split-screen display mode. FIG. 5A22 shows an interactive map user interface displayed in a full-screen display mode. A long press gesture on the right side of the bottom edge of the display, including contact 4218 in FIG. 5A22, causes the dock 4204 to appear in a default position near the right edge of the bottom edge of the display, below but not centered on contact 4218 in FIG. 5A23. Movement of the contact on the email application icon 218 selects the icon, which appears larger in FIG. 5A24 as a result of being selected. Movement of the contact in an upward direction away from the edge of the display while the email application icon is selected moves the icon out of the dock, which appears larger in FIG. 5A25 as a result of the icon being moved out of the dock, indicating that the corresponding application is launched upon lift-off of contact 4218. In FIG. 5A26, further movement of the contact through boundary 4223 (e.g., an invisible boundary or a boundary that is temporarily displayed in response to detecting upward and rightward movement outside the dock of icon 218) transitions the icon into view of the email user interface, indicating that the email application will be launched in split-screen display mode (e.g., displayed side-by-side with the interactive map user interface) upon contact lift-off. Lift-off of contact 4218 in FIG. 5A27 causes the device to switch from full-screen display mode to split-screen display mode, displaying a user interface for the email application on the right portion of the display and displaying the interactive map user interface on the left portion of the display. The email application user interface is displayed in split-screen mode because the icon was dragged out of the dock prior to contact lift-off, in contrast to FIG. 5A8, where the email user interface is displayed in full-screen display mode because contact lift-off occurred while the email icon was selected in the dock in FIGS. 5A6-5A7.

[0162] 5A28-5A29 show an example embodiment in which a gesture initiated at an edge of the display results in navigation to a transition navigation state rather than display of a dock because the contact moves away from the edge of the display before meeting the time requirements for a long press gesture. FIG. 5A28 shows an interactive map user interface displayed in a full screen display mode. The user interface selection process is activated by movement of contact 5222 upward from the bottom edge of the display in FIG. 5A29 because the contact moves a sufficient amount before meeting the long press criterion. In contrast, the dock was displayed in FIG. 5A23 because the long press criterion was met before contact 4218 began substantial movement. In FIG. 5A29, the interactive map user interface is replaced (e.g., transitioned) by a card 4014 representing the interactive map user interface. For example, as shown in FIG. 5A29, after a user interface selection process is activated, the device selects between multiple possible target user interfaces (e.g., a user interface of a previously displayed application, an application switcher user interface, or a home screen user interface) depending on which user interface state is the currently selected target user interface state at the time that lift-off of the contact is detected. The target user interfaces dynamically facilitate selecting and navigating to different user interfaces (e.g., a recently opened application, a home screen user interface, and an application switcher user interface) based on different criteria (e.g., different criteria based on the position, timing, movement parameters of the contact and / or the displayed user interface object). In addition, real-time visual feedback is provided to indicate where the user is navigating while the user is moving the contact on the touch screen. Respective criteria for navigating to different user interfaces are described, for example, with respect to FIG. 8.

[0163] In some embodiments, when a currently displayed user interface is displayed in a full-screen display mode (e.g., as shown in FIGS. 5A28-5A29), the device follows a first set of criteria for navigating to a different user interface in the full-screen display mode; when a currently displayed user interface is displayed in a split-screen display mode, the device follows a second set of criteria for navigating to a different user interface in the split-screen display mode (e.g., navigating to a recently opened application user interface, or an application switcher user interface within a sub-portion of the split-screen), or for navigating to a different user interface in the full-screen display mode (e.g., an application switcher user interface that includes the split-screen user interface as a single selectable user interface, an application switcher user interface that includes application user interfaces within the split-screen user interface as separate selectable user interfaces, or a home screen user interface). More details regarding navigation to different user interfaces (e.g., including different full-screen user interfaces, and different user interface configurations of split-screen user interfaces (e.g., different combinations of user interfaces of split-screen user interfaces)) are provided below, for example, with respect to Figures 5B1-5B36 and flowcharts Figures 7A-7I.

[0164] 5B1-5B36 illustrate example user interfaces for navigating to a different user interface from a user interface displayed in a split screen display mode according to some embodiments.

[0165] The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 7A-7I. For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device having touch-sensitive display system 112. In such embodiments, the focus selector is optionally a respective finger or stylus contact, a representative point corresponding to the finger or stylus contact (e.g., the face center of the respective contact or a point associated with the respective contact), or the face center of two or more contacts detected on touch-sensitive display system 112. However, similar operations are optionally performed on a device having display 450 and separate touch-sensitive surface 451 in response to detecting a contact on touch-sensitive surface 451 while displaying the user interface shown in the figures on display 450, along with a focus selector.

[0166] For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device that does not have a home button, and gestures that meet predefined criteria are used to trigger dismissal of the currently displayed user interface and display of a home screen user interface. Although optionally shown in Figures 5B1-5B36, in some embodiments, a home button (e.g., a mechanical button, a solid-state button, or a virtual button) is included on the device and is used to trigger dismissal of the currently displayed user interface and display of a home screen user interface (e.g., in response to a single press input) and / or display of a multitasking user interface (e.g., in response to a double press input).

[0167] 5B1-5B36 illustrate a method for efficiently navigating between multiple user interfaces, e.g., quickly switching between different applications and system user interfaces in a split-screen display mode on an electronic device, according to some embodiments. An exemplary user interface for user interface selection processing includes an application switcher user interface that includes representations of multiple user interfaces for applications associated with the electronic device (e.g., recently opened applications, currently displayed applications, and optionally a system control panel) displayed as a virtual stack (e.g., "stack") of cards, with each card in the stack representing a user interface for a different application. The cards are also referred to herein as "application view" when they correspond to a user interface for a recently opened application, or "control panel view" when they correspond to a user interface for a control panel. User input (e.g., touch, swipe / drag gestures, flick gestures, etc.) detected on the touch screen 112 (e.g., touch-sensitive surface) is used to display an application dock that is superimposed on the currently displayed user interface and navigate between user interfaces that can be selected for display on the screen. In some embodiments, the home screen user interface is optionally displayed as a "card" in a virtual stack of cards. In some embodiments, the home screen user interface is displayed in a display layer beneath the stack of cards.

[0168] While the device is displaying any interface (e.g., an application's user interface), a gesture that begins at the bottom of the screen (e.g., within a predefined region of the device proximate to the edge of the display (e.g., an edge region that includes a predefined portion of the display (e.g., 20 pixels wide) that is close to the bottom edge of the device)) triggers a user interface selection process (e.g., displays a transition navigation user interface) and directs navigation between multiple user interfaces based on the speed and direction of the input, and optionally based on movement parameters and characteristics of the currently displayed user interface object (e.g., a card). The device replaces the display of the current user interface with a card representing the user interface (e.g., in some embodiments, the user interface appears to shrink into a card following the input movement). The user has the option, in some embodiments, to use various gestures to (i) navigate to a full-screen home screen, (ii) navigate to an application that was displayed on the screen immediately prior to the user interface that was displayed when the user interface selection process was invoked (e.g., on any portion of a split-screen display), (iii) navigate to a split-screen application switcher user interface that allows the user to select from applications that were previously displayed on the screen (e.g., for display on a portion of a display operating in split-screen mode), (iv) navigate to a full-screen application switcher user interface that allows the user to select from applications that were previously displayed on the screen (e.g., for display in either full-screen or split-screen display mode), or (v) navigate back to the user interface that was displayed when the user interface selection process was invoked (e.g., in split-screen display mode).During input, the device provides dynamic visual feedback indicating which navigational choice will be made once input is completed, facilitating efficient user navigation between multiple choices. In some embodiments, the visual feedback and user interface response is fluid and reversible. In some embodiments, the user also has the option to navigate to a control panel user interface using gestures. In other embodiments, a different input (e.g., starting from a different edge of the display) is required to navigate to the control panel user interface. In some embodiments, the user also has the option to display a dock with multiple application icons on the displayed user interface.

[0169] 5B1-5B9 show exemplary split screen user interfaces in which the user interface on one portion of the display can be changed via an application switcher user interface displayed in a split screen display mode. FIG. 5B1 shows an interactive map user interface displayed on a left portion of a display operating in a split screen display mode, and an email user interface displayed simultaneously on a right portion of the display. Home affordances 4400 are displayed on both portions of the display and are overlaid on the corresponding user interfaces to indicate that an input that can guide navigation on either portion of the display is to be initiated (e.g., for navigation only within that portion of the display, or for navigation to a full screen user interface). In FIG. 5B2, after activating a user interface selection process by moving contact 4402 from the left side of the bottom edge of the display upwards, the interactive map user interface is replaced (e.g., transitioned) by a card 4014 representing the interactive map user interface. However, because the transition navigation state was initiated only on the left portion of the display, the display of the email user interface is maintained on the right portion of the display. When contact 4402 moves upward beyond a threshold position on the screen, a second card 406 representing a web browser user interface is also partially displayed on the left portion of the display (e.g., slid off the left edge of the display) to indicate that if the contact is lifted off at that time, navigation will proceed to the split screen application switcher user interface. The criteria for navigating to the split screen application switcher user interface on the left portion of the display is, optionally, dynamically determined based on the movement parameters (e.g., position, velocity, path, etc., or a combination thereof) and the movement history of the contact 4402. Upon lift-off of contact 4402 in FIG. 5B3, the device navigates to the application switcher user interface in the left portion of the display in FIG. 5B4.The device animates the transition by appearing to slide a card representing a previously displayed user interface out from the left side of the display, forming a stack of previously displayed user interfaces. A swipe gesture beginning in FIG. 5B5 navigates the stack of cards, revealing web browsing card 4406 in FIGS. 5B6 and 5B7. Selection of web browsing card 4406 using a tap gesture in FIG. 5B8 results in the display of a user interface for a web browsing application on the left side of the display in FIG. 5B9. The email user interface remains displayed in the right portion of the display in FIG. 5B9 because navigation actions only operate on user interfaces displayed in the left portion of the display.

[0170] 5B1-5B12 show exemplary split screen user interfaces in which navigation occurs within one portion of a split screen display (e.g., instead of another portion of the display, or instead of within the full display). This is because the transition navigation gesture is initiated from the bottom edge of that portion of the display (e.g., instead of starting from the bottom edge of the other portion of the display). FIG. 5B1 shows an interactive map user interface displayed on the left portion of a display operating in a split screen display mode, and an email user interface displayed simultaneously on the right portion of the display. As shown in FIG. 5B1, when an upward swipe gesture is initiated from the bottom edge of the left portion of the display, a user interface selection process is activated on the left portion of the screen, as indicated by the transition navigation user interface displayed on the left portion of the display in FIG. 5B2. In contrast, when an upward swipe gesture is initiated from the bottom edge of the right portion of the display, as indicated in FIG. 5B10, a user interface selection process is activated on the right portion of the screen, as indicated by the transition navigation user interface displayed on the right portion of the display in FIG. 5B11. In both examples, the user interface displayed on the opposite portion of the display is maintained while navigation occurs on the portion of the display where the gesture was initiated (e.g., an email user interface remains displayed on the right portion of the display when navigation to an application switcher user interface occurs on the left portion of the display in FIGS. 5B2-5B9, and then a web browsing user interface occurs on the left portion of the display in FIGS. 5B10-5B12, and similarly, the web browsing user interface remains displayed on the left portion of the display when navigation to the application switcher user interface occurs on the right portion of the display in FIGS. 5B10-5B12.

[0171] In the examples shown in FIGS. 5B1-5B12, an edge swipe gesture initiated on either side of the split screen met the criteria for navigating to a split screen application switcher user interface on each side of the split screen, but did not meet the criteria for navigating to a full screen application switcher user interface.

[0172] 5B13-5B17 illustrate an exemplary process in which a device navigates from a user interface displayed in a split-screen display mode to a full-screen application switcher user interface (e.g., instead of a split-screen application switcher user interface). The reason for navigating is that the criteria for navigating to the full-screen application switcher user interface are met by the input (e.g., because the transition navigation gesture has moved further from the edge of the display). FIG. 5B13 illustrates an interactive map user interface displayed on the left portion of a display operating in a split-screen display mode, and an email user interface displayed simultaneously on the right portion of the display. When an upward swipe gesture starts from the bottom edge of the left portion of the display, as shown in FIG. 5B13, a user interface selection process is activated on the left portion of the screen, as illustrated by the transition navigation user interface displayed on the left portion of the display in FIG. 5B14. As the contact continues to move away from the bottom edge of the display, the email user interface displayed on the right portion of the display is replaced (e.g., transitioned) by card 4015 representing the email user interface, indicating to the user in FIG. 5B15 that the device will switch to full-screen display mode upon lift-off of the contact (unless, for example, the user changes the gesture to direct navigation back to split-screen display mode). Additionally, when contact lift-off is detected at the point shown in FIG. 5B15, the application switcher user interface displayed in the full-screen display mode includes cards 4014 and 4015 as separately selectable user interfaces within the application switcher user interface. When one of the cards displayed in the full-screen application switcher user interface is selected by the user, the device displays the user interface corresponding to the selected card in the full-screen display mode.In other words, the device transitions out of split screen mode as a result of a navigation gesture by contact 4424 when lift-off of contact 4424 is detected in the state shown in FIG. 5B15 (e.g., visual feedback indicates that the criteria for navigating to the full-screen application switcher user interface have been met).

[0173] As shown in FIG. 5B16, the contact 4424 continues to move upwards, and the cards from the previously displayed interactive map user interface and email user interface animate and merge into a single card 4017 representing a split-screen display state in which user interfaces for the interactive map application and the email application are displayed simultaneously. The presence of a second card 4406 representing a web browsing user interface on the device indicates that the device will navigate to a full-screen application switcher user interface in a different configuration upon lift-off of the contact. The display of a full-screen transition user interface (e.g., including cards associated with two applications) indicates that the application switcher user interface will be displayed in a full-screen display mode. This is in contrast to the display of a split-screen transition user interface (e.g., as shown in FIGS. 5B2 and 5B11, including only cards associated with a single application), which indicates that upon termination of the gesture, the application switcher user interface will be displayed in a split-screen mode (e.g., as shown in FIGS. 5B4 and 5B12). The device then displays the full-screen application switcher user interface after lift-off of the contact in FIG. 5B17. Selection of card 4015 causes the device to re-display the split-screen user interface, which includes an interactive map user interface and an email user interface.

[0174] 5B18-5B21 illustrate an exemplary process in which a device navigates from a user interface displayed in a split-screen display mode to a full-screen home screen (e.g., a split-screen application switcher user interface or instead of a full-screen application switcher user interface). The reason for navigating is that the criteria for navigating to a full-screen home screen user interface are met by the input (e.g., because the transition navigation gesture has moved further from the edge of the display than that shown in FIG. 5B16). FIG. 5B18 illustrates an interactive map user interface displayed on the left portion of a display operating in a split-screen display mode, and an email user interface displayed simultaneously on the right portion of the display. When an upward swipe gesture starts from the bottom edge of the left portion of the display and moves sufficiently far from the bottom edge of the display, as shown in FIG. 5B18, a full-screen user interface selection process is activated. As illustrated by the full-screen transition user interface displayed on the display in FIG. 5B19, it includes cards 4017 associated with both the interactive map application and the email application. The presence of the second card 4406 representing the web browsing user interface in Fig. 5B19 indicates to the device that the device will navigate to an application switcher user interface upon lift-off of the contact. As the contact continues to move away from the bottom edge of the display, the web browsing card disappears in Fig. 5B20 and the home screen user interface begins to come into focus behind the transition navigation user interface, indicating that the device will navigate to the home screen upon lift-off of the contact (unless, for example, the user changes the gesture to indicate navigation to a different user interface). The device then displays the full screen home screen after lift-off of the contact in Fig. 5B21.

[0175] 5B22-5B24 show exemplary split screen user interfaces in which the device navigates to a previously displayed user interface on one portion of the display (e.g., not an application switcher user interface or home screen) while maintaining display of a user interface on the other portion of the display. The reason for navigating is that the criteria for navigating to the previously displayed user interface are met by an input (e.g., the input moves substantially horizontally relative to the bottom edge of the display (e.g., the input is an arc swipe that starts from the bottom edge of one portion of the display). FIG. 5B22 shows a web browser user interface displayed on the left portion of a display operating in a split screen display mode, and an email user interface displayed simultaneously on the right portion of the display. As shown in FIG. 5B22, when a substantially horizontal swipe gesture starts from the bottom edge of the left portion of the display, a user interface selection process is activated on the left portion of the screen, as shown by the transition navigation user interface displayed on the left portion of the display in FIG. 5B23. The arc swipe 5B23, a web browsing user interface (e.g., application view 406 of the web browsing user interface) appears to be dragged from a first portion of the display to the right, while simultaneously pulling an interactive maps user interface (e.g., application view 4014 of the interactive maps user interface) onto the display from the left side. Cards appear to move over the home screen and are blurred in the background. The display of the email user interface in the right portion of the display is not affected by the gesture because the gesture started within the left portion of the display and did not invoke a full-screen display mode (e.g., as in FIGS. 5B15 and 5B19). Upon lift-off of the contact, the interactive maps user interface is displayed in the left portion of the split-screen display in FIG. 5B24.

[0176] 5B25-5B36 show an exemplary split screen interface in which the device navigates a previously displayed user interface in a card stack in one portion of the display and then activates a full screen display mode in response to a serial arc swipe gesture because no other previously displayed user interface is available in the card stack. FIG. 5B25 shows an interactive map user interface displayed in the left portion of the display operating in a split screen display mode, and an email user interface displayed simultaneously in the right portion of the display. When a substantially sideways swipe gesture starts from the bottom edge of the right portion of the display as shown in FIG. 5B25, a user interface selection process is activated on the right portion of the screen, as shown by the transition navigation user interface displayed on the left portion of the display in FIG. 5B23 (e.g., in contrast, when an arc swipe starts from the bottom edge of the left portion of the display as shown in FIG. 5B23, the left portion of the display). The arc swipe gesture pushes the email user interface off the display to the right while dragging a web browsing user interface (e.g., application view 4406 of the web browsing user interface) onto the right portion of the display (e.g., as seen from below an interactive map user interface displayed on the right portion of the display), as shown in FIG. 5B27. The web browsing user interface is the first previously displayed user interface navigated onto the right portion of the display because it was the last user interface navigated off of the display. According to some embodiments, the web browsing user interface was previously displayed on the left portion of the display, but it is still the first previously displayed user interface navigated onto the right portion of the display because the two portions of the display share a single stack of previously displayed cards.

[0177] As shown in FIGS. 5B28-5B29, a first subsequent arc swipe in the right portion of the display results in navigation back to the email user interface in FIG. 5B30 because the previously displayed card stack was reset before the gesture was initiated, as indicated by the redisplay of home affordance 4400-2 when input was initiated, as shown in FIG. 5B28. In contrast, as shown in FIGS. 5B31-5B33, a second subsequent arc swipe in the right portion of the display navigates to the older, previously displayed user interface for the messaging application in FIG. 5B33 (as opposed to navigation back to the web browsing user interface that was displayed on the right side of the display immediately prior to the display of the email user interface), as indicated by the lack of a home affordance displayed in FIG. 5B31. Finally, in FIGS. 5B34-5B35, a third subsequent arc swipe in the right portion of the display, initiated before the reset of the previously displayed card stack, results in navigation to a full-screen display of the interactive map user interface, previously displayed in the left portion of the display, as shown in FIG. 5B36, because there was no previously displayed user interface available in the card stack. The split-screen display mode has two home affordances 4400 displayed (e.g., one displayed above each of the application user interfaces displayed in the right and left portions of the display, as in FIG. 5B25, indicating that separate navigation is possible within either portion of the display), as compared to FIG. 5B36, in which there is only one home affordance displayed above the full-screen interactive map user interface.

[0178] 5C1-5C59 show example user interfaces for navigating between different user interfaces using multi-touch gestures, for example, taking into account translation and movement of contacts relative to one another as a group (e.g., pinch and de-pinch keycap actions) and providing dynamic feedback during the gesture to indicate which user interface will be navigated to upon completion of the gesture, which according to some embodiments allows a user to change characteristic properties of the gesture upon completion of the gesture to avoid unintended navigation and / or consideration for changes in intended navigation during the gesture.

[0179] The user interfaces in these figures are used to illustrate processes described below, including the processes in Figures 11A-11F. For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device having touch-sensitive display system 112. In such embodiments, the focus selector is optionally a respective finger or stylus contact, a representative point corresponding to the finger or stylus contact (e.g., the face center of the respective contact or a point associated with the respective contact), or the face center of two or more contacts detected on touch-sensitive display system 112. However, similar operations are optionally performed on a device having display 450 and separate touch-sensitive surface 451 in response to detecting a contact on touch-sensitive surface 451 while displaying the user interface shown in the figures on display 450, along with a focus selector.

[0180] For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device that does not have a home button, and gestures that meet predefined criteria are used to trigger dismissal of the currently displayed user interface and display of a home screen user interface. Although optionally shown in FIGS. 5C1-5C59, in some embodiments, a home button (e.g., a mechanical button, a solid-state button, or a virtual button) is included on the device and is used to trigger dismissal of the currently displayed user interface and display of a home screen user interface (e.g., in response to a single press input) and / or display of a multitasking user interface (e.g., in response to a double press input).

[0181] Exemplary user interfaces shown in Figures 5C1-5C59 relate to a method for efficiently navigating between multiple user interfaces, e.g., quickly switching between different applications and a system user interface, according to some embodiments. Exemplary user interfaces shown in Figures 5C1-5C59 include, for example, a home screen user interface including multiple application launch icons, as described in conjunction with Figures 5A1-5A29, a full screen application switcher user interface including representations of multiple user interfaces for applications associated with the electronic device (e.g., recently opened applications, currently displayed applications, and, optionally, a system control panel) displayed as cards each processed on a virtual plane (as opposed to cards displayed in a virtual stack, as described in conjunction with Figures 5B1-5B36). The cards are also referred to herein as "application view" when they correspond to a user interface for recently opened applications, or "control panel view" when they correspond to a user interface for a control panel. In some embodiments, the application view displays a snapshot of a recent or live state of the application corresponding to the application view, which is in contrast to the application launch icons displayed on the home user interface, which display a predefined design independent of the recent or live state of the application.

[0182] While displaying a user interface (e.g., a user interface for an application such as an application switcher user interface or a system user interface), the device may detect a gesture initiated anywhere on the screen involving at least three contacts (e.g., 3, 4, 5, or more contacts) and involving at least a threshold amount of movement within a predetermined time period, and may invoke a user interface selection process (e.g., display a transition navigation user interface) to direct navigation between multiple user interfaces based on the speed and direction of the input, and optionally based on movement parameters and characteristics of a currently displayed user interface object (e.g., a card). The device replaces the display of the current user interface with a card representing the user interface (e.g., in some embodiments, the user interface appears to shrink into a card following the movement of the input).A user may, according to some embodiments, (i) navigate to a full screen home screen, (ii) navigate to an application displayed on the screen (e.g., the user of the user interface displayed when the user interface selection process was invoked may, according to some embodiments, (i) navigate to a full screen home screen, (ii) navigate to an application that was displayed on the screen immediately preceding the user interface displayed when the user interface selection process was invoked (e.g., on any portion of a split screen display), (iii) navigate to a split screen application switcher user interface that allows the user to select from applications that were previously displayed on the screen (e.g., for display on a portion of a display operating in split screen mode), or (iv) navigate to a full screen application switcher user interface that allows the user to select from applications that were previously displayed on the screen (e.g., for display on a portion of a display operating in split screen mode). The user has the option to use transitions and pinch / de-pinch gestures to (v) navigate back to the user interface that was displayed when the user interface selection process was invoked (e.g., in split-screen display mode). During input, the device provides dynamic visual feedback indicating which navigational selection will be made once input is completed, facilitating efficient user navigation between multiple selections. In some embodiments, the visual feedback and user interface response is fluid and reversible. In some embodiments, the user also has the option to navigate to a control panel user interface using gestures. In other embodiments, a different input (e.g., starting from a different edge of the display) is required to navigate to the control panel user interface. In some embodiments, the user also has the option to display a dock with multiple application launch icons on the displayed user interface.

[0183] Figures 5C1-5C3, 5C4-5C6, and 5C7-5C9 show example embodiments in which a gesture involving two contacts (e.g., a two-finger touch) performs an application-specific action rather than, for example, a system-wide user interface selection (e.g., UI navigation) operation. Figures 5C1-5C3 and 5C4-5C6 show a swipe gesture that causes a translation of the interactive map, and Figures 5C7-5C9 show a pinch gesture that causes a resize of the interactive map.

[0184] FIG. 5C1 shows an interactive map user interface displayed in a full-screen display mode. As shown in FIG. 5C2, a two-contact swipe gesture including movement 4504 and 4508 of contacts 4502 and 4506 to the right from positions 4502-a and 4506-a to positions 4502-b and 4506-b as shown in FIG. 5C1, respectively, results in a horizontal translation of the interactive map to the right (e.g., to reveal Eastern Oregon) because the gesture met application-specific translation criteria (e.g., including translation of contacts in a gesture including less than three total contacts) rather than criteria that invoke a user interface selection process (e.g., including translation of contacts in a gesture including at least three contacts). Upon lift-off of the contacts, as shown in FIG. 5C3, the interactive map application user interface remains displayed because the gesture met application-specific criteria rather than system-wide user interface navigation criteria.

[0185] FIG. 5C4 illustrates an interactive map user interface displayed in a full-screen display mode. As shown in FIG. 5C4, a two-contact swipe gesture including movement 4664 and 4668 of contacts 4662 and 4666 in an upward direction from positions 4662-a and 4666-a to positions 4662-b and 4666-b, respectively, results in a horizontal translation of the interactive map upward (e.g., hiding southern Montana), as shown in FIG. 5C5, because the gesture met application-specific translation criteria (e.g., including translation of contacts in a gesture including less than three total contacts) rather than criteria for invoking a user interface selection process (e.g., including translation of contacts in a gesture including at least three contacts). Upon contact liftoff, as shown in FIG. 5C6, the interactive map application user interface remains displayed because the gesture met application-specific criteria rather than system-wide user interface navigation criteria.

[0186] FIG. 5C7 illustrates an interactive map user interface displayed in a full-screen display mode. As shown in FIG. 5C7, a two-touch pinch gesture involving movement 4596 and 4600 of contacts 4594 and 4598 toward each other from positions 4594-a and 4598-a to positions 4594-b and 4598-b, respectively, results in the contraction of the interactive map (e.g., revealing both Eastern Oregon and Western Illinois), as shown in FIG. 5C8, because the gesture met application-specific resizing criteria (e.g., including pinch movement of contacts in a gesture involving less than three total contacts) rather than criteria that would invoke a user interface selection process (e.g., including pinch movement of contacts in a gesture involving at least three contacts). Upon lift-off of the contacts, as shown in FIG. 5C9, the interactive map application user interface remains displayed because the gesture met application-specific criteria rather than system-wide user interface navigation criteria.

[0187] 5C10-5C12, 5C13-5C16, 5C17-5C19, and 5C20-5C22 illustrate example embodiments in which a swipe gesture involving at least three contacts (e.g., three, four, or five finger touches) performs, for example, a system-wide user interface selection (e.g., UI navigation) operation rather than an application-specific operation. The user interface navigated in response to the gesture in each series of figures depends on the characteristics of the gesture. The device provides dynamic visual feedback during the gesture to indicate which user interface is navigated upon termination of the gesture (e.g., lift-off of all contacts).

[0188] 5C10-5C12 illustrate a horizontal swipe gesture including four contacts that results in navigation to a previously displayed application user interface. FIG. 5C10 illustrates an interactive map user interface displayed in a full screen display mode. A four contact swipe gesture including contact movement 4512, 4516, 4520, and 4524 upward from locations 4510-a, 4514-a, 4518-a, and 4522-a, as shown in FIG. 5C10, to locations 4510-b, 4514-b, 4518-b, and 4522-b, as shown in FIG. 5C11, invokes a user interface selection process because the gesture meets system-wide user interface navigation criteria (e.g., includes translational movement of contacts within a gesture including at least three contacts, and is selected within a threshold time (e.g., TT) after the device first detects the contacts). 1 ) that occurs within a threshold amount of time (TT) after the device first detects the contact, which may be application-specific translation criteria (e.g., including translational movement of contacts in gestures that include three or fewer total contacts (e.g., as shown in Figures 5C1-5C3) and where the translational movement of contacts occurs within a threshold amount of time (TT) after the device first detects the contact). 15C11 ). The device replaces the display of the interactive map user interface with a display of an interactive map user interface (e.g., card) 4526 and begins to slide the card from the right side of the screen (e.g., following the movement of the contact to the right), dragging the previously displayed email user interface display (e.g., card) 4528 onto the screen from the left, as shown in FIG. 5C11 . As shown by the display of the email user interface after lift-off of the contact in FIG. 5C12 , the cards 4526 and 4528 remain large during the gesture, indicating that the device will navigate to the next / previously displayed application upon the end of the gesture (e.g., because the device assigns the next / previously displayed application as the current target state when the input / application view characteristics meet the "next / previous app" criteria (100x4) and / or the "vertical swipe for next / previous app" criteria (100x5), as shown in FIGS. 10A-10B ).

[0189] 5C13-5C16 show a vertical swipe gesture including four contacts resulting in navigation to a homescreen user interface. FIG. 5C13 shows an email user interface displayed in a full screen display mode. A four contact swipe gesture including movement of contacts 4532, 4536, 4540, and 4544 upward from locations 4530-a, 4534-a, 4538-a, and 4542-a, as shown in FIG. 5C13C, to locations 4530-b, 4534-b, 4538-b, and 4542-b, as shown in FIG. 5C14, invokes a user interface selection process because the gesture meets system-wide user interface navigation criteria (e.g., includes translational movement of contacts within a gesture including at least three contacts, and is selected within a threshold time (e.g., TT) after the device first detects the contacts). 1) that occurs within a threshold amount of time (TT) after the device first detects the contact, which may be application-specific translation criteria (e.g., including translational movement of contacts in gestures that include three or fewer total contacts (e.g., as shown in Figures 5C4-5C6) and where the translational movement of contacts occurs within a threshold amount of time (TT) after the device first detects the contact). 1 ). The device replaces the display of the email user interface with an email user interface representation (e.g., card) 4528 and begins to both shrink and translate the card 4528 upward (e.g., in accordance with the upward movement of the contact). The previously displayed interactive map user interface representation (e.g., card) 4526 is also displayed with a similar size and vertical translation as the email card 4528, indicating that at the end of the gesture the device will navigate to an application switcher user interface. As shown in FIG. 5C15, as the contact moves upward to positions 4530-c, 4534-c, 4538-c, and 4542-c, the email card 4528 shrinks and continues to move upward, the interactive map card 4526 disappears and begins to come into focus behind the email card 4528, and the home screen user interface indicates that the device navigates to the home screen user interface upon completion of the gesture (e.g., because the device assigns the home screen as the current target state when the input / application view characteristics meet the "quick resize / translate to home" criteria (100x2) and / or the "large resize / translate to home" criteria (100x3), as shown in FIG. 10A-B). In FIG. 5C16, a display of the home screen user interface after liftoff of the contact is shown.

[0190] 5C17-5C19 illustrate a vertical swipe gesture including four contacts that results in navigation to an application switcher user interface. FIG. 5C17 illustrates an email user interface displayed in a full screen display mode. A four contact swipe gesture including contact movement 4548, 4552, 4556, and 4560 upward from locations 4546-a, 4550-a, 4554-a, and 4558-a, as shown in FIG. 5C17, to locations 4546-b, 4550-b, 4554-b, and 4558-b, as shown in FIG. 5C18, invokes a user interface selection process because the gesture meets system-wide user interface navigation criteria (e.g., includes translational movement of contacts within a gesture including at least three contacts, and occurs within a threshold time (e.g., TT) after the device first detects the contacts). 1 ) that occurs within a threshold amount of time (TT) after the device first detects the contact. It is not limited to application-specific translation criteria (e.g., including translational movement of contacts in gestures that include three or fewer total contacts, where the movement threshold amount occurs within a threshold amount of time (TT) after the device first detects the contact). 15C19 ). The device replaces the display of the email user interface with a representation (e.g., card) 4528 of the email user interface and begins to both contract and translate the card 4528 upward (e.g., in accordance with the upward movement of the contact). The previously displayed representation (e.g., card) 4526 of the interactive map user interface is also displayed with a size and vertical movement similar to that of the email card 4528, as shown in FIG. 5C19 , the display of the application switcher user interface after lift-off of the contact, indicating that the device will navigate to the application switcher user interface at the end of the gesture (e.g., because the device assigns the application switcher as the current target state, as shown in FIGS. 10A-10B , when the input / application view characteristics meet the “pause for application switcher” criteria (100×6) and / or the “short, slow move to application switcher” criteria (100×8). Because the gesture met the application switcher navigation criteria, but not the home screen navigation criteria, in FIG. 5C19, rather than the home screen user interface, the device navigates to the application switcher user interface (e.g., navigated within FIGS. 5C13-5C16). The upward movement of the contact meets a second vertical translation and / or second vertical velocity threshold corresponding to navigation to the application switcher user interface).

[0191] 5C20-5C22 show a horizontal swipe gesture including four contacts that results in navigation back to the same application user interface. FIG. 5C20 shows an interactive map user interface displayed in a full screen display mode. A four contact swipe gesture including upward movement 4564, 4568, 4572, and 4576 to contacts 4562, 4566, 4570, 4574 from locations 4562-a, 4566-a, 4570-a, and 4574-a, as shown in FIG. 5C20, to locations 4562-b, 4566-b, 4570-b, and 4574-b, as shown in FIG. 5C21, invokes a user interface selection process because the gesture meets system-wide user interface navigation criteria (e.g., includes translational movement of contacts within a gesture including at least three contacts, and within a threshold time (e.g., TT) after the device first detects the contacts). 1 ) that occurs within a threshold amount of time (TT) after the device first detects the contact, which may be application-specific translation criteria (e.g., including translational movement of contacts in gestures that include three or fewer total contacts (e.g., as shown in Figures 5C1-5C3) and where the translational movement of contacts occurs within a threshold amount of time (TT) after the device first detects the contact). 15C21 )). The device replaces the display of the interactive map user interface with a display of an interactive map user interface (e.g., a card) 4526 and begins to slide the card from the right side of the screen (e.g., following the movement of the contact to the right), dragging the previously displayed display of an email user interface (e.g., a card) 4528 onto the screen from the left, as shown in FIG. 5C21 . However, while cards 4526 and 4528 remain large during the gesture, the card slides quite far to the right, indicating that the device will navigate to the interactive map-using interface at the end of the gesture (e.g., because the device assigns the current application as the current target state when the input / application view characteristics meet the "resize / translate cancel" criteria (100x7) as shown in FIGS. 10A-10B , as indicated by the display of the interactive map-using interface after lift-off of the contact in FIG. 5C22 ).

[0192] 5C23-5C26 illustrate example embodiments in which a swipe gesture including at least four contacts (e.g., four or five finger touches) performs an application-specific action rather than a system-wide user interface selection (e.g., UI navigation) action when a threshold amount of movement does not occur within a threshold amount of time. FIG. 5C23 illustrates an interactive map user interface displayed in a full screen display mode. As shown in FIG. 5C24, four contact inputs including contacts 4578, 4582, 4586, and 4590 are detected. However, contact movement does not occur until a threshold amount of time (e.g., TT) has elapsed after the first detection of the contacts, as shown in FIG. 5C24. 1) has elapsed. Movement 4580, 4584, 4588, and 4592 to the right from contacts 4578, 4582, 4586, and 4590, as shown in FIG. 5C24, to locations 4578-b, 4582-b, 4586-b, and 4590-b, as shown in FIG. 5C25, results in a horizontal translation of the interactive map to the right (e.g., to reveal Eastern Oregon), and is not, for example, a criterion for invoking a user interface selection process (e.g., a threshold time TT 1 (including movements over a threshold amount within a certain time frame) after the device first detects a touch, but rather, an application-specific translation criterion (a time threshold amount (TT 1 5C26), the interactive map application user interface remains displayed because the gesture satisfies application-specific criteria rather than system-wide user interface navigation criteria.

[0193] 5C27-5C29, 5C30-5C32, 5C33-5C36, and 5C37-5C42 illustrate example embodiments in which a pinch gesture involving at least three contacts (e.g., three, four, or five finger touches) performs a system-wide user interface selection (e.g., UI navigation) action rather than an application-specific operation, for example. The user interface navigated in response to the gesture in each series of figures depends on the characteristics of the gesture and, in some embodiments, includes a translational motion instead of and / or in addition to a pinch / pinch action. The device provides dynamic visual feedback during the gesture to indicate which user interface is navigated to upon termination of the gesture (e.g., lift-off of all contacts).

[0194] Figures 5C27-5C29 show a pinch gesture including five contacts resulting in navigation to a home screen user interface. Figure 5C27 shows an interactive map user interface displayed in a full screen display mode. A five contact pinch gesture, including movement of contacts 4604, 4608, 4612, 4616, and 4620 from locations 4602-a, 4606-a, 4610-a, 4614-a, and 4618-a toward one another to locations 4602-b, 4606-b, 4610-b, 4614-b, 4618-b, as shown in FIG. 5C28, invokes a user interface selection process because the gesture meets system-wide user interface navigation criteria (e.g., includes a pinch movement of contacts in a gesture that includes at least three contacts and is selected within a threshold time (e.g., TT) after the device first detects the contacts). 1 ) that occurs within a threshold amount of time (TT) after the device first detects the contact, which is not subject to any application-specific resizing criteria (e.g., pinch / de-pinch movement of contacts in gestures that include three or fewer total contacts (e.g., as shown in Figures 5C7-5C9) and where the movement threshold amount occurs within a threshold amount of time (TT 15C). The device replaces the display of the interactive map user interface with a representation (e.g., card) 4526 of the interactive map user interface and begins to contract and translate (e.g., following the pinch movement of the contacts) the card 4526 towards the location between each of the contacts. The small size of the interactive map card 4526 and the appearance of the home screen user interface behind the interactive map card 4526 indicate that the device navigates to the home screen user interface at the end of the gesture (e.g., because the device assigns the home screen as the current target state when the input / application view characteristics meet the "quick resize / translate to home" criteria (100x2) and / or the "big resize / translate to home" criteria (100x3), as shown in FIG. 10A-B). Shown in FIG. 5C29 is a display of the home screen user interface after lift-off of the contacts.

[0195] Figures 5C30-5C32 show a pinch gesture including five contacts, which results in navigation to an application switcher user interface. Figure 5C30 shows an interactive map user interface displayed in a full screen display mode. A five contact pinch gesture, including movement of contacts 4644, 4648, 4652, 4656, and 4660 from locations 4642-a, 4646-a, 4650-a, 4654-a, and 4658-a toward one another, as shown in FIG. 5C30, to locations 4642-b, 4646-b, 4650-b, 4654-b, 4658-b, as shown in FIG. 5C31, invokes a user interface selection process because the gesture meets system-wide user interface navigation criteria (e.g., includes a pinch movement of contacts in a gesture that includes at least three contacts, and is selected within a threshold time (e.g., TT) after the device first detects the contacts). 1) that occurs within a threshold amount of time (TT) after the device first detects the contact, which is not subject to any application-specific resizing criteria (e.g., pinch / de-pinch movement of contacts in gestures that include three or fewer total contacts (e.g., as shown in Figures 5C7-5C9) and where the movement threshold amount occurs within a threshold amount of time (TT 1 5C32 )). The device replaces the display of the interactive map user interface with a representation (e.g., card) 4526 of the interactive map user interface and begins contracting and translating the interactive map card 4526 toward the location between each of the contacts (e.g., following the pinch movement of the contacts). A previously displayed representation (e.g., card) 4528 of the email user interface is also displayed with a similar size and vertical movement as the interactive map card 4526, as shown in FIG. 5C32 in the display of the application switcher user interface after lift-off of the contacts, indicating that the device will navigate to the application switcher user interface at the end of the gesture (e.g., because the device assigns the application switcher as the current target state, as shown in FIGS. 10A-10B , when the input / application view characteristics meet the “pause for application switcher” criteria (100×6) and / or the “short, slow move to application switcher” criteria (100×8). Rather than the home screen user interface, in FIG. 5C32 the device navigates to the application switcher user interface (e.g., navigates within FIGS. 5C27-5C29) because the gesture met the application switcher navigation criteria but not the home screen navigation criteria (e.g., the pinch upward movement of the contact meets a first pinch translation and / or first vertical velocity threshold corresponding to navigation to the application switcher user interface).

[0196] 5C33-5C36, 5C37-5C42, and 5C43-5C47 illustrate example embodiments in which navigation of a user interface is controlled by a combination of translation and pinch movements in gestures that include at least three contacts (e.g., three, four, or five finger touches). The user interface navigated in response to the gesture in each series of figures depends on the characteristics of the gesture before it is terminated (e.g., the last set of measured characteristics of the gesture). The device provides dynamic visual feedback during the gesture to indicate which user interface is navigated to upon termination of the gesture (e.g., lift-off of all contacts).

[0197] Figures 5C33-5C36 show an example embodiment in which a pinch movement of a gesture including five contacts triggers a user interface selection process, and a translational movement of the gesture just before the end of the gesture results in navigation to a previously displayed application user interface. Figures 5C33-5C36 also show an example embodiment in which after the user interface selection process is invoked, user interface navigation continues after liftoff of some, but not all, of the contacts. A five contact pinch motion, including movements 4624, 4628, 4632, 4636 and 4640 of contacts 4622, 4626, 4630, 4634 and 4638 from positions 4622-a, 4626-a, 4630-a, 4634-a, and 4638-a, as shown in Figure 5C33, to positions 4622-b, 4626-b, 4630-b, 4634-b, and 4638-b, as shown in Figure 5C34, invokes a user interface selection process. The device replaces the display of the interactive map user interface with an interactive map user interface representation (e.g., card) 4526 and begins contracting and translating interactive map card 4526 (e.g., following the pinch movements of the contacts) toward positions between each of the contacts. A previously displayed representation (e.g., card) 4528 of the email user interface is also displayed with a size and vertical movement similar to that of the interactive map card 4526, to indicate that the device will navigate to the application switcher user interface upon completion of the gesture (e.g., because when the input / application view characteristics meet the "pause for application switcher" criteria (100x6) and / or the "short, slow move to application switcher" criteria (100x8), the device assigns the application switcher as the current target state, as shown in Figures 10A-10B). The user interface selection process continues after contacts 4622 and 4626 are lifted off, as shown in Figure 5C35.As shown by the display of the email user interface after lift-off of the contacts in FIG. 5C36, horizontal translation of remaining contacts 4630, 4634, and 4638 from positions 4630-b, 4634-b, and 4638-b shown in FIG. 5C34 to positions 4630-c, 4634-c, and 4638-c as shown in FIG. 5C35 pushes interactive map card 4526 off the display to the right while also dragging email card 4528 from the left onto the display, indicating that the device will navigate to the next / previously displayed application upon completion of the gesture (because, for example, as shown in FIGS. 10A-10B, when the input / application view properties meet the "next / previous app" criteria (100x4) and / or the "vertical swipe for next / previous app" criteria (100x5), the device assigns the next / previously displayed application as the current target state).

[0198] 5C37-5C42 illustrate an example embodiment in which a navigation gesture including a pinch motion is reversed by a de-pinch motion. A five contact pinch movement, including movements 4672, 4676, 4680, 4684, and 4688 of contacts 4670, 4674, 4678, 4682, and 4686 toward one another from positions 4670-a, 4674-a, 4678-a, 4682-a, and 4686-a, as shown in FIG. 5C37, to positions 4670-b, 4674-b, 4678-b, 4682-b, and 4686-b, as shown in FIG. 5C38, invokes a user interface selection process. The device replaces the display of the interactive map user interface with an interactive map user interface representation (e.g., card) 4526 and begins contracting and translating the interactive map card 4526 (e.g., following the pinch movement of the contacts) toward the location between each of the contacts. A previously displayed representation (e.g., card) 4528 of an email user interface is also displayed with a size and vertical movement similar to the interactive map card 4526 to indicate that the device will navigate to the application switcher user interface at the end of the gesture (e.g., because when the input / application view characteristics meet the "pause for application switcher" criteria (100x6) and / or the "short, slow move to application switcher" criteria (100x8), the device assigns the application switcher as the current target state, as shown in FIGS. 10A-10B).As shown in FIG. 5C39, as the contacts continue to pinch together to positions 4670-c, 4674-c, 4678-c, 4682-c, and 4686-c, the interactive map card 4526 shrinks and continues to move into the virtual palm gesture, the email card 4528 disappears, and the home screen user interface begins to come into focus behind the interactive map card 4526, indicating that the device will navigate to the home screen user interface at the end of the gesture (e.g., because the device assigns the home screen as the current target state when the characteristics of the input / application view meet the "fast resize / translate to home" criteria (100x2) and / or the "large resize / translate to home" criteria (100x3), as shown in FIG. 10A-B). As shown in FIG. 5C40, reversing the pinch motion (e.g., de-pinch motion) of contacts at locations 4670-d, 4674-d, 4678-d, 4682-d, and 4686-d expands the interactive map card 4526 and causes the email card 4538 to reappear, indicating that the device will navigate to the application switcher user interface at the end of the gesture (e.g., because when the characteristics of the input / application view meet the "pause for application switcher" criteria (100x6) and / or the "short, slow move to application switcher" criteria (100x8), the device assigns the application switcher as the current target state, as shown in FIGs. 10A-10B).As shown in FIG. 5C42 by the display of the email user interface after lift-off of the contact, horizontal translation of the contact to the right after the de-pinch motion to locations 4670-e, 4674-e, 4678-e, 4682-e, and 4686-e as shown in FIG. 5C41 pushes interactive map card 4526 off the display to the right while also dragging email card 4528 from the left onto the display, indicating that the device will navigate to the next / previously displayed application upon completion of the gesture (because, e.g., as shown in FIGS. 10A-10B, when the input / application view properties meet the "next / previous app" criteria (100x4) and / or the "vertical swipe for next / previous app" criteria (100x5), the device assigns the next / previously displayed application as the current target state).

[0199] 5C43-5C47 illustrate an example embodiment in which an upward swipe motion and a pinch motion both contribute to a gesture that results in navigation to a home screen user interface. FIG. 5C43 illustrates an interactive map user interface displayed in a full screen display mode. A four contact swipe including movement 4692, 4696, 4700, and 4704 of contacts 4690, 4694, 4698, and 4702 to the right from positions 4690-a, 4694-a, 4698-a, and 4702-a as shown in FIG. 5C43 to positions 4690-b, 4694-b, 4698-b, and 4702-b as shown in FIG. 5C44 invokes a user interface selection process. The device replaces the interactive map user interface display with an interactive map user interface display (e.g., card) 4526 and begins sliding the card from the right side of the screen (e.g., following the contact's movement to the right), dragging the previously displayed email user interface display (e.g., card) 4528 onto the screen from the left, as shown in FIG. 5C43. In FIG. 5C44, cards 4526 and 4528 remain large, indicating that the device will navigate to the next / previously displayed application upon completion of the gesture (e.g., because the device assigns the next / previously displayed application as the current target state when the input / application view properties meet the "next / previous app" criteria (100x4) and / or the "vertical swipe for next / previous app" criteria (100x5), as shown in FIGS. 10A-10B).As shown in FIG. 5C45, upward movement of the contact to positions 4690-c, 4694-c, 4698-c, and 4702-c causes the cards to contract and move upward (e.g., in accordance with the upward movement of the contact), indicating that the device will navigate to the application switcher user interface at the end of the gesture (e.g., because when the characteristics of the input / application view meet the “pause for application switcher” criteria (100x6) and / or the “short, slow move to application switcher” criteria (100x8), the device assigns the application switcher as the current target state, as shown in FIGs. 10A-10B). As the contact begins to pinch together to positions 4690-d, 4694-d, 4698-d, and 4702-d, as shown in FIG. 5C46, the interactive map card 4526 continues to shrink and begins to move downward toward the virtual palm gesture, the email card 4528 disappears, and the home screen user interface begins to focus behind the interactive map card 4526, indicating that the device navigates to the home screen user interface at the end of the gesture (e.g., because the device assigns the home screen as the current target state when the input / application view characteristics meet the "quick resize / translate to home" criteria (100x2) and / or the "large resize / translate to home" criteria (100x3), as shown in FIG. 10A-B). In FIG. 5C47, a display of the home screen user interface after liftoff of the contact is shown. Despite the card moving downward in response to the pinch action in FIG. 5C46 (as opposed to, e.g., an upward movement in response to an upward swipe in FIGS. 5C13-5C16), the predicted navigation state is the home screen user interface because both the upward movement of the contact and the pinch are associated with such navigation (e.g., both the upward swipe and the pinch contribute to an increase in the "simulated Y-position" and / or a contraction of the card, either or both of which correspond to navigation to an application switcher user interface).

[0200] 5C48-5C50 show example embodiments in which an upward swipe with at least three contacts (e.g., three, four, or five finger touches) on a homescreen user interface that is not the default homescreen user interface (e.g., a second or subsequent page of application launching icons) causes navigation to the default homescreen user interface. FIG. 5C48 shows a second homescreen user interface that includes application launching icons for multiple applications (e.g., a clock, an app store, a voice memo, a calculator, and a memo). A four contact swipe gesture including movement 4712, 4716, 4720 and 4724 of contacts 4710, 4714, 4718 and 4722 upward from locations 4710-a, 4714-a, 4718-a and 4722-a to locations 4710-b, 4714-b, 4718-b and 4722-b as shown in Figure 5C48, causes the device to navigate to the primary (e.g., default) home screen user interface as shown in Figure 5C50, as shown in Figure 5C49. In some embodiments, an animation is displayed showing the primary home screen user interface sliding (e.g., from the left side of the display) and pushing the secondary home screen user interface off the display (e.g., to the right). In some embodiments, a four contact pinch gesture involving moving contacts 4710, 4714, 4718, and 4722 towards each other causes the device to navigate to a primary (eg, default) home screen user interface.

[0201] 5C51-5C54 show example embodiments in which an upward swipe gesture involving at least three contacts (e.g., three, four, or five finger touches) on an application switcher user interface causes navigation to a home screen user interface. A four-contact swipe gesture involving movement 4728, 4732, 4736, and 4740 of contacts 4726, 4730, 4734, and 4738 upward from positions 4726-a, 4730-a, 4734-a, and 4738-a, as shown in FIG. 5C52, to positions 4726-b, 4730-b, 4734-b, and 4738-b, as shown in FIG. 5C51, causes the device to navigate to the home screen user interface, as shown in FIG. 5C54. In some embodiments, an animation is displayed to slide the application switcher user interface upward with the movement of the contact to reveal the home screen user interface below the application switcher user interface. In some embodiments, representations of recently used applications are displayed in parallel in response to an initial portion of a multi-touch swipe up gesture (e.g., as shown in FIG. 5C52), and when the criteria for navigating to the home screen are met (e.g., the same as the criteria for navigating from an application user interface to a home screen user interface, as described in FIGS. 9A-9C and 10A-10D), the device displays only representations of recently used applications on the display as visual feedback to indicate the current target state of the user interface navigation before lift-off of the contact (e.g., as shown in FIG. 5C23), and displays the home screen user interface after the gesture ends (e.g., as shown in FIG. 5C54).

[0202] Figures 5C55-5C59 show an example embodiment in which the user interface for the user interface selection process is dynamic and reversible. A five contact pinch movement, including movements 4744, 4748, 4752, 4756 and 4760 of contacts 4742, 4746, 4750, 4754 and 4758 towards each other from positions 4742-a, 4746-a, 4750-a, 4754-a and 4758-a as shown in Figure 5C55 to positions 4742-b, 4746-b, 4750-b, 4754-b and 4758-b as shown in Figure 5C56, invokes the user interface selection process. The device replaces the display of the interactive map user interface with an interactive map user interface representation (e.g., card) 4526 and begins contracting and translating the interactive map card 4526 (e.g., following the pinch movement of the contacts) toward the location between each of the contacts. A previously displayed representation (e.g., card) 4528 of an email user interface is also displayed with a size and vertical movement similar to the interactive map card 4526 to indicate that the device will navigate to the application switcher user interface at the end of the gesture (e.g., because when the input / application view characteristics meet the "pause for application switcher" criteria (100x6) and / or the "short, slow move to application switcher" criteria (100x8), the device assigns the application switcher as the current target state, as shown in FIGS. 10A-10B). As shown in FIG. 5C57, translational movement of the contact diagonally to the upper right (e.g., a movement that includes horizontal and vertical components) to locations 4742-c, 4746-c, 4750-c, 4754-c, and 4758-c causes the card to contract and move upward and to the right (e.g., in accordance with the vertical component of the contact movement).As shown in FIG. 5C58, downward movement of the contact to locations 4742-d, 4746-d, 4750-d, 4754-d, and 4758-d increases the size of the interactive map card 4526 and pushes the email card 4528 to the left off the display, indicating that the device will navigate to the interactive map user interface at the end of the gesture, as shown in FIG. 5C59 by the display of the interactive map user interface after lift-off of the contact (e.g., because the device assigns the current application as the current target state when the input / application view characteristics meet the “resize / translate cancel” criterion (100×7), as shown in FIG. 10A-10B).

[0203] 5D1-5D64 illustrate example user interfaces for navigating from an application user interface displayed in a split-screen display mode to a different user interface outside the application according to some embodiments.

[0204] In FIGS. 5D1-5D14, two applications (e.g., a map application and a game application) are displayed side-by-side on touch screen 112 in a split-screen display mode. Neither of the two applications requires edge protection (e.g., implemented with extended edge swipe gesture criteria) in their current state. In some embodiments, edge protection is implemented with standard edge swipe gesture criteria (e.g., gesture starts anywhere along the bottom edge), plus gesture repetition requirements (e.g., two consecutive standard edge swipe gestures required), and / or extended position requirements (e.g., one or both edge swipes start on a home affordance). When an application does not require edge protection, it is associated with standard edge swipe gesture criteria, and an upward edge swipe gesture that meets the standard edge swipe gesture criteria causes the execution of a system action, including, for example, navigation from an application user interface displayed in split screen mode to a user interface external to the application, including a system user interface (e.g., a home screen user interface or an application switcher user interface) or a user interface of another application (e.g., the contact moves up and sideways, or starts on an edge and moves sideways without initially moving up).

[0205] As shown in FIG. 5D1 (and also in FIG. 5D9), on touch screen 112, user interface 4806-1 of a map application is displayed side-by-side with user interface 4808-1 of a game application. User interface 4801-1 and user interface 4808-1 are separated by a divider 4804, which may be dragged in a direction along the bottom edge of touch screen 112 to resize the user interfaces of the two simultaneously displayed applications (e.g., by adjusting the ratio of the widths of the two parallel applications). In some embodiments, the relative sizes of the parallel applications are one of a set of predetermined discrete values ​​(e.g., 1:2, 1:1, 2:1).

[0206] In FIG. 5D1 (and also in FIG. 5D9), neither of user interfaces 4806-1 and 4808-1 is in an edge-protected state (e.g., extended edge swipe gesture criteria are not active for applications on either side of the split screen). A system user interface element (e.g., home affordance 4802-1) is displayed in a first appearance state (e.g., opaque, or standard visibility) to indicate that the application(s) underlying the system user interface element are associated with standard edge swipe gesture criteria, as opposed to extended edge swipe gesture criteria. In some embodiments, the appearance of home affordance 4802-1 is generated according to the portion of the content underlying home affordance 4802-1 (e.g., having the display characteristics shown in FIG. 5D99) using a first set of rules.

[0207] In FIGS. 5D1-5D8, because map application user interface 4806-1 is not in an edge-protected state (e.g., the extended edge swipe gesture criteria are not active), and when an upward swipe with contact 4828 is detected on the side of the screen displaying the map application (e.g., at a starting position on the lower or bottom edge of screen 112 and optionally outside the area occupied by home affordance 4801-1), the upward swipe gesture with contact 4828 meets the standard edge swipe gesture criteria, a system navigation process is initiated, and transition user interface 4822-1 replaces the split-screen user interface displayed on the screen at the start of the gesture. 5D2, at the beginning of the system navigation process, a dock 4826 is gradually dragged onto the screen following the upward movement of contact 4828, and the split screen user interface (e.g., including user interfaces 4806-1 and 4808-1) is transformed into a card 4818 in a transition user interface 4822-1 (e.g., a snapshot representation of the split screen user interface at the time contact 4828 was detected). The dock 4826 includes a subset of application icons (e.g., frequently used apps, user selected apps, or recommended app icons) selected from the application icons shown on the home screen user interface 4814. The dock 4826 overlays a portion (less than all) of the currently displayed user interface and may be displayed in multiple contexts (e.g., overlaid on a home screen user interface, an application user interface, a transition user interface, or an application switcher user interface).

[0208] In Figures 5D1-5D8, as contact 4828 moves upward on touch screen 112, card 4818 is displayed next to another card 4820 representing a previously used application in a set of recently used applications, as shown in Figures 5D2 and 5D3. The representations of user interfaces 4818 and 4820 are continuously and dynamically dragged and resized (e.g., as shown in Figures 5D2-5D3) in accordance with the movement of contact 4828 on the touch screen. As contact 4828 continues to move upward, card 4820 moves off the display, leaving card 4818 as a single card in transition user interface 4822-2, as shown in Figure 5D5. If contact 4828 moves to the side after initially moving up (e.g., in an arc swipe gesture in the side swipe for next / previous app 100x4 of FIG. 10A), cards 4818 and 4820 are dragged to the side by contact 4828, as shown in FIG. 5D7. When lift-off of contact 4828 is detected, contact 4828 determines a final navigation state of the user interface based on one or more characteristic parameters of the gesture according to various navigation criteria. As shown in FIG. 5D4, for example, if lift-off of contact 4828 is detected while transition user interface 4822-1 is in the state shown in FIG. 5D3, application switcher user interface 4812 is displayed (e.g., a split screen user interface representation 4824 shown in a grid or stack of recently used application presentations (e.g., arranged based on recency of last use of the application)). As shown in FIG. 5D6, if lift-off of contact 4828 is detected while transition user interface 4822-2 is in the state shown in FIG. 5D5, home screen user interface 4814 is displayed (e.g., with application icons representing applications installed on the device displayed in a pre-arranged grid, regardless of whether the applications were last used).As shown in FIG. 5D8, if lift-off of contact 4828 is detected (e.g., after an arc swipe (at transition user interface 4822-3 in the state shown in FIG. 5D7), the user interface of the previously used application (e.g., the application represented by card 4820) is displayed. In some embodiments, the criteria for navigating to a different user interface are described with respect to the processes shown in FIGS. 9A-9C and 10A-10D.

[0209] In some embodiments, if a gesture by contact does not meet the criteria for navigating between user interfaces (e.g., the gesture is initiated outside the responsive area indicated by home affordances 4802-1), the gesture is passed to the underlying application and used as input for an action within the application. For example, a tap input by contact within an area within user interface 4806-1 (e.g., a touch input that does not meet edge swipe gesture criteria, e.g., because it does not include movement over a threshold amount) causes a location within the map corresponding to the location of the contact to be selected. A swipe input by contact within an area within user interface 4806-1 (e.g., a swipe that does not meet edge swipe gesture criteria, e.g., because it does not start at a predefined edge of the device, such as an edge where a home affordance is displayed) scrolls a map shown within the user interface of a map application.

[0210] 5D1-5D8, the standard edge swipe gesture criteria does not require that the contact begin above or below the home affordance, and a standard edge swipe gesture for a contact (e.g., contact 4828) detected anywhere along the bottom edge of the screen (e.g., on home affordance 4802-1 or otherwise) on the side of the map application can result in system-level navigation to a user interface outside of the currently displayed application (e.g., the map application displayed in split screen mode). In addition, navigation applies to the entire split screen user interface, including the user interfaces of both applications displayed simultaneously.

[0211] 5D9-5D14 show that both applications (e.g., a map application and a gaming application) displayed side-by-side on a split screen user interface are associated with standard edge swipe gesture criteria (e.g., a non-edge protected state), but home affordance 4802-1, which overlays the user interfaces of both applications (e.g., 4806-1 and 4808-1), is displayed in a first appearance state (e.g., opaque and standard visibility). An edge swipe gesture with contact 4830 detected on the side of the gaming application on screen 112 that meets standard edge swipe gesture criteria (e.g., detected outside of home affordance 4802-1) causes navigation from the currently displayed split screen user interface to application switcher user interface 4812 (e.g., as shown in FIGS. 5D9-5D12) or home screen user interface 4814 (e.g., as shown in FIGS. 5D9-5D10 and 5D13-5D14) according to the criteria for navigating to different user interfaces described with respect to the process shown in FIGS. 9A-9C and 10A-10D. The navigation process shown in FIGS. 5D9-5D14 is similar to that of FIGS. 5D1-5D6 and will not be repeated here for brevity.

[0212] In Figures 5D15-5D49, two applications (e.g., a map application and a game application) are displayed side-by-side on the touch screen 112 in a split-screen display mode. In contrast to the scenarios shown in Figures 5D1-5D14 (e.g., neither of the two applications require edge protection), one of the two applications shown in Figures 5D15-5D49 is currently associated with an extended edge swipe gesture criteria and is in an edge protection state. According to some embodiments, the home affordance 4802-2, which overlaps at least a portion of both applications on the split screen, is displayed in a second appearance state (e.g., semi-transparent or with reduced visibility, as shown in Figures 5D15, 25, - 5D32, 5D37, 5D44, 5D47) compared to the affordances in the first appearance state (e.g., as shown in Figures 5D1 and 5D9). Indicates that at least one of the two applications under the Home affordance is currently associated with the extended edge swipe gesture criteria.

[0213] In the scenarios shown in Figures 5D15-5D24, the application displayed on the right side of the split screen (e.g., a gaming application) is currently associated with standard edge swipe gesture criteria, and the application displayed on the left side of the split screen (e.g., a map application) is currently associated with extended edge swipe gesture criteria. In the scenarios shown in Figures 5D25-5D31, the application displayed on the left side of the split screen (e.g., a map application) is currently associated with standard edge swipe gesture criteria, and the application displayed on the right side of the split screen (e.g., a gaming application) is currently associated with extended edge swipe gesture criteria. In these examples, the extended edge swipe gesture criteria require two edge swipe gestures to be detected to trigger a system action to navigate to another user interface outside of the currently displayed application. In addition, the extended edge swipe gesture criteria ensure that at least the first of two consecutive edge swipe gestures meets extended position requirements (e.g., must start above or below home affordance 4802-2) and temporarily disables edge protection, allowing the second edge swipe gesture to meet the criteria of standard edge swipe gestures and trigger a system-level navigation action (e.g., navigating to the home screen, an application switcher user interface, or another application not currently displayed on a split screen).

[0214] In the exemplary scenario illustrated in FIG. 5D15-FIG. 5D24, as shown in FIG. 5D15, the map application is in a guided navigation mode that requires edge protection. In the guided navigation mode, user interaction with the map user interface 4806-2 is given priority over system-level navigation because accidental triggering of system-level navigation during use of the guided navigation mode (e.g., while driving) is disadvantageous. Contact 4832 is detected (e.g., on the user interface 4806-2) at a location on the home affordance 4802-2 on the side of the map application. The home affordance 4802-2 is displayed in a second appearance state (e.g., semi-transparent with reduced visibility). An upward movement of contact 4832 (e.g., meeting the standard edge swipe gesture criteria and the extended position requirements of the extended edge swipe gesture criteria (e.g., applicable to the first swipe of two consecutive edge swipes), but not meeting the gesture repetition requirements of the extended edge swipe gesture criteria) causes edge protection to be temporarily disabled, as indicated by a change in appearance state of home affordance 4802 from a second appearance state (e.g., as shown in FIG. 5D15) to a first appearance state (e.g., as shown in FIG. 5D16). In some embodiments, because it does not meet the extended edge swipe gesture criteria associated with the map application, the upward movement of contact 4832 is optionally provided as input to the map application. In this example, the upward movement of contact 4832 causes a menu displayed at the starting location of contact 4832 to be dragged upward within user interface 4806-2. No system-level operations are performed to replace or modify the split screen user interface as a whole. A standard edge swipe gesture by contact 4832 does not result in a transition user interface being displayed 4832.

[0215] 5D17-5D24, a second upward edge swipe gesture with contact 4832 is detected (e.g., at a starting location outside of home affordance 4802-1 in the first appearance state). The second upward edge swipe gesture with contact 4834 meets the gesture criteria for a standard edge swipe gesture by itself and, in combination with the first edge swipe gesture with contact 4832, meets the extended edge swipe gesture criteria (e.g., the gesture with contact 4834 is detected within a threshold amount of time after the gesture with contact 4836). An upward edge swipe gesture by contact 4832 may transition, for example, from an application user interface (e.g., user interfaces 4806-2 and 4808-1) displayed in a split-screen mode (e.g., as shown in FIG. 5D17) to a user interface external to the application, for example, a system user interface (e.g., initially transition user interface 4822-1 (e.g., as shown in FIG. 5D17) according to various navigation criteria (e.g., criteria described with respect to the processes illustrated in FIGS. 9A-9C and 10A-10D). 8) or 4822-2 (e.g., FIG. 5D20), 4822-3 (e.g., FIG. 5D23), and ultimately to a home screen user interface (e.g., in FIG. 5D21) or an application switcher user interface (e.g., in FIG. 5D19), or to another application's user interface (e.g., in FIG. 5D24). The navigation process illustrated in 5D15-5D24 is similar to that in FIGS. 5D1-5D8 and will not be repeated here for brevity.

[0216] In the example shown in FIG. 5D25-5D31, the application displayed on the left side of the split screen (e.g., a map application) is currently associated with standard edge swipe gesture criteria, and the application displayed on the right side of the split screen (e.g., a game application) is currently associated with extended edge swipe gesture criteria. In FIG. 5D25, the game application is in a game play mode (e.g., piano keyboard play mode) that requires edge protection. In the game play mode, user interaction with the game user interface 4808-2 is given priority over system level navigation because accidental triggering of system level navigation during use of the game play mode (e.g., during an active game) is inconvenient. Contact 4838 is detected (e.g., on user interface 4808-2) at a location on home affordance 4802-2 beside the game application. Home affordance 4802-2 is displayed in a second appearance state (e.g., semi-transparent with reduced visibility). An upward movement of contact 4838 (e.g., meeting the standard edge swipe gesture criteria and the extended position requirements of the extended edge swipe gesture criteria (e.g., applicable to the first swipe of two consecutive edge swipes), but not meeting the gesture repetition requirements of the extended edge swipe gesture criteria) causes edge protection to be temporarily disabled, as indicated by a change in appearance state of home affordance 4802 from a second appearance state (e.g., as shown in FIG. 5D25) to a first appearance state (e.g., as shown in FIG. 5D26). In some embodiments, the upward movement of contact 4838 is optionally provided as input to the gaming application because it does not meet the extended edge swipe gesture criteria associated with the gaming application. In this example, the upward movement of contact 4838 causes a piano key (key "C") to be displayed at the start of contact 4838 being pressed within user interface 4808-2. No system level actions are performed to replace or modify the split screen user interface as a whole.A standard edge swipe gesture by contact 4838 does not result in a transition user interface being displayed 4838.

[0217] 5D27-5D31, a second upward edge swipe gesture by contact 4840 is detected (e.g., at a start location outside of home affordance 4802-1 in the first appearance state). The second upward edge swipe gesture by contact 4840 meets the gesture criteria for a standard edge swipe gesture by itself and in combination with the first edge swipe gesture by contact 4832 meets the extended edge swipe gesture criteria (e.g., the gesture by contact 4840 is detected within a threshold amount of time after the gesture by contact 4838). An upward edge swipe gesture by contact 4840 triggers the execution of a system action, including, for example, navigation from an application user interface (e.g., user interfaces 4806-1 and 4808-2) displayed in a split-screen mode (e.g., as shown in FIG. 5D27) to a user interface external to the application, for example, a system user interface (e.g., first to transition user interface 4822-1 (e.g., FIG. 5D28) or 4822-2 (e.g., FIG. 5D30), and eventually to a home screen user interface (e.g., in FIG. 5D31) or an application switcher user interface (e.g., in FIG. 5D29)) according to various navigation criteria (e.g., criteria described with respect to the processes shown in FIGS. 9A-9C and 10A-10D). The navigation process shown in FIGS. 5D27-5D31 is similar to that of FIGS. 5D1-5D6 and will not be repeated herein for brevity.

[0218] As shown in the two exemplary scenarios of Figures 5D15-5D24 and 5D25-5D31, when one of two simultaneously displayed applications is associated with the extended edge swipe gesture criteria, a gesture detected on the edge-protected application side must meet the extended edge swipe gesture criteria in order to execute a system action (e.g., navigation to a user interface outside the currently displayed application). A gesture detected on the edge-protected application side that meets the extended edge swipe gesture criteria (e.g., when combined with an earlier gesture that meets the extended position requirement) intercepts the gesture and prevents the gesture from being passed to the underlying application. In contrast, a gesture detected on the edge-protected application side that does not meet the extended edge swipe gesture criteria is optionally passed to the application as an input and does not execute a system action (e.g., navigation to a user interface outside the currently displayed application).

[0219] In contrast to the example scenarios shown in Figures 5D15-5D24 and 5D25-5D31, 5D32-5D36, and 5D37-5D43, two example scenarios are shown in which an upward edge swipe gesture that meets the standard edge swipe gesture criteria is detected on a side of a split screen that displays an application associated with the standard edge swipe gesture criteria. In these example scenarios, an upward Ecker gesture that meets the standard edge swipe gesture criteria (e.g., no extended position requirement or gesture repetition requirement needs to be met) causes the system to perform an action (e.g., navigating to a user interface outside of the currently displayed application) regardless of the fact that the other side of the split screen displays an application associated with the extended edge swipe gesture criteria.

[0220] As shown in FIG. 5D32, the map application on the left side of the split screen (e.g., with user interface 4806-2) is edge protected (e.g., in a guided navigation mode) and the gaming application on the right side of the split screen (e.g., with user interface 4808-1) is not edge protected. Home affordance 4802-2 is displayed in a second appearance state (e.g., semi-transparent with reduced visibility) to indicate that at least one of the applications under the home affordance is currently associated with an extended edge swipe gesture criteria. Contact 4842 is detected in a location proximate to the bottom edge of the screen on the side of the gaming application, as shown in FIG. An upward edge swipe gesture by contact 4842 satisfies standard edge swipe gesture criteria associated with a gaming application and causes the execution of a system action, including, for example, navigation from an application user interface (e.g., user interfaces 4806-2 and 4808-1) displayed in a split screen mode (e.g., as shown in FIG. 5D32) to a user interface external to the application, such as a system user interface (e.g., first to transition user interface 4822-1 (e.g., FIG. 5D33) or 4822-2 (e.g., FIG. 5D35), and eventually to a home screen user interface (e.g., in FIG. 5D36) or an application switcher user interface (e.g., in FIG. 5D34)) according to various navigation criteria (e.g., criteria described with respect to the processes shown in FIGS. 9A-9C and 10A-10D). The navigation process shown in FIGS. 5D32-5D36 is similar to that of FIGS. 5D1-5D6 and will not be repeated herein for brevity.

[0221] As shown in FIG. 5D37, the map application on the left side of the split screen (e.g., with user interface 4806-1) is not edge protected, and the game application on the right side of the split screen (e.g., with user interface 4808-2) is edge protected (e.g., in game play mode). Home affordance 4802-2 is displayed in a second appearance state (e.g., semi-transparent with reduced visibility) to indicate that at least one of the applications under the home affordance is currently associated with an extended edge swipe gesture criteria. Contact 4844 is detected in a location proximate to the bottom edge of the screen on the side of the map application, as shown in FIG. 5D37. The upward swipe gesture by contact 4844 satisfies standard edge swipe gesture criteria associated with the map application and causes the execution of a system action including, for example, navigation from an application user interface (e.g., user interfaces 4806-1 and 4808-2) displayed in a split screen mode (e.g., as shown in FIG. 5D37) to a user interface external to the application, for example, a system user interface (e.g., first to transition user interfaces 4822-1 (e.g., FIG. 5D38), 4822-2 (e.g., FIG. 5D40) or 4822-3 (e.g., FIG. 5D42), and ultimately to a home screen user interface (e.g., in FIG. 5D41), an application switcher user interface (e.g., FIG. 5D39)), or a user interface of another application (e.g., FIG. 5D43), in accordance with various navigation criteria (e.g., criteria described with respect to the processes shown in FIGS. 9A-9C and 10A-10D). The navigation process shown in Figures 5D37-5D43 is similar to that of Figures 5D1-5D8 and will not be repeated here for the sake of brevity.

[0222] In contrast to the exemplary scenarios shown in Figures 5D15-5D24 and 5D25-5D31 and the exemplary scenarios shown in Figures 5D32-5D36 and 5D37-5D43, 5D44-5D49, two exemplary scenarios are shown in which an upward edge swipe gesture that meets the standard edge swipe gesture criteria is detected on the side of a split screen that displays an application associated with the extended edge swipe gesture criteria. In these exemplary scenarios, an upward Ecker gesture that meets the standard edge swipe gesture criteria (e.g., the extended position requirement or gesture repetition requirement does not need to be met) does not temporarily disable edge protection for the underlying application (e.g., because the extended position requirement applicable to the initial swipe is not met) and does not cause the execution of a system action (e.g., because the enhanced position requirement and gesture repetition criteria of the gesture criteria of the extended edge swipe gesture associated with the underlying application are not met). Instead of navigating to a user interface outside the currently displayed application, the gesture is passed as input to the underlying application, optionally causing an action to be performed within the application.

[0223] As shown in FIG. 5D44, the map application on the left side of the split screen (e.g., with user interface 4806-2) is edge protected (e.g., in a guided navigation mode), and the game application on the right side of the split screen (e.g., with user interface 4808-1) is not edge protected. Home affordance 4802-2 is displayed in a second appearance state (e.g., semi-transparent with reduced visibility) to indicate that at least one of the applications under the home affordance is currently associated with the extended edge swipe gesture criteria. Contact 4848 is detected in a location proximate to the bottom edge of the screen on the side of the map application, as shown in FIG. 5D44. The upward swipe gesture by contact 4848 meets the standard edge swipe gesture criteria associated with the map application, but does not meet the extended edge swipe gesture criteria. The upward swipe gesture also does not satisfy the extended position requirement of temporarily disabling edge protection for subsequent edge swipes, resulting in the home affordances continuing to be displayed in the second appearance state (e.g., semi-transparent with reduced visibility) and no system action is performed, e.g., no navigation from the application user interface (e.g., user interfaces 4806-2 and 4808-1) displayed in split screen mode (e.g., as shown in FIG. 5D44) to a user interface outside the application. Instead, the gesture input from contact 4848 is provided to the underlying application (e.g., a map application) and action within the application is performed according to the screen gesture input (e.g., a piano key below contact 4848 is pressed following the movement of contact 4848, as shown in FIG. 5D45). Upon ceasing to detect contact 4848, the map application's user interface 4806-2 is restored, e.g., the menu is retracted and removed from the display, as shown in FIG. 5D46.

[0224] As shown in FIG. 5D47, the map application on the left side of the split screen (e.g., with user interface 4806-1) is not edge protected, and the game application on the right side of the split screen (e.g., with user interface 4808-2) is edge protected (e.g., in game play mode). The home affordance 4802-2 is displayed in a second appearance state (e.g., semi-transparent with reduced visibility) to indicate that at least one of the applications under the home affordance is currently associated with the extended edge swipe gesture criteria. A contact 4850 is detected in a location proximate to the bottom edge of the screen on the side of the game application, as shown in FIG. 5D47. The upward swipe gesture by contact 4850 meets the standard edge swipe gesture criteria associated with the game application, but does not meet the extended edge swipe gesture criteria. The upward swipe gesture also does not satisfy the extended position requirement of temporarily disabling edge protection for subsequent edge swipes, resulting in the home affordances continuing to be displayed in the second appearance state (e.g., semi-transparent with reduced visibility) and no system action is performed, e.g., no navigation from the application user interface (e.g., user interfaces 4806-2 and 4808-1) displayed in split screen mode (e.g., as shown in FIG. 5D48) to a user interface outside the application. Instead, the gesture input from contact 4848 is provided to the underlying application (e.g., a gaming application) and actions within the application are performed as the gesture input (e.g., a piano key beneath contact 4850) is pressed as contact 4850 moves, as shown in FIG. 5D48. When contact 4850 is no longer detected, the gaming application's user interface 4808-2 is restored, e.g., the pressed piano key is restored, as shown in FIG. 5D50.

[0225] In the exemplary scenario illustrated in FIG. 5D50-FIG. 5D56, applications on both sides of the split screen are edge protected. In order to use an edge swipe gesture to trigger navigation to a user interface outside the application, extended edge swipe criteria must be met. First, an edge swipe gesture that meets the standard edge swipe gesture criteria and the application of enhanced position requirements for the first of two consecutive edge swipes is detected, which temporarily disables edge protection for both applications. Subsequently, a second edge swipe gesture that meets the standard edge swipe gesture criteria (detected anywhere along the bottom edge of either side of the split screen) is detected, which triggers the execution of a system action.

[0226] As shown in Figure 5D50, a map application (e.g., in user interface 4806-2) and a gaming application (e.g., in user interface 4808-2) are displayed side-by-side on the touch screen with home affordance 4802-2 displayed in a second appearance state (e.g., semi-transparent with reduced visibility), overlaying both applications. A first edge swipe gesture with contact 4852 is detected on home affordance 4802, causing the home affordance to change appearance state from the second appearance state (e.g., semi-transparent with reduced visibility) to the first appearance state (e.g., opaque with normal visibility), indicating that edge protection is temporarily disabled for both applications, as shown in Figure 5D51. In Figures 5D52-5D56, a second edge swipe gesture by contact 4854 is detected while edge protection is temporarily disabled for both applications (e.g., as indicated by the first appearance state of home affordance 4802-1 in Figure 5D52). The second edge swipe gesture meets standard edge swipe gesture criteria (e.g., various types of navigation criteria described corresponding to Figures 9A-9C and 10A-10D) and, in some embodiments, does not need to meet the extended location requirements imposed on the first of two consecutive edge swipes required to meet the extended location requirements.The second edge swipe gesture by contact 4854, in combination with the previous gesture by contact 4852, satisfies the extended edge swipe gesture criteria associated with the two underlying applications and causes the execution of a system action including, for example, navigation from an application user interface (e.g., user interfaces 4806-2 and 4808-2) displayed in a split screen mode (e.g., as shown in FIG. 5D52) to a user interface external to the application, for example, a system user interface (e.g., first to transition user interfaces 4822-1 (e.g., FIG. 5D53), 4822-2 (e.g., FIG. 5D55) or 4822-3 (e.g., FIG. 5D57), and eventually to a home screen user interface (e.g., in FIG. 5D56), an application switcher user interface (e.g., FIG. 5D54)), or a user interface of another application (e.g., FIG. 5D58), according to various navigation criteria (e.g., criteria described with respect to the processes shown in FIGS. 9A-9C and 10A-10D). The navigation process shown in Figures 5D52-5D58 is similar to that of Figures 5D1-5D8 and will not be repeated here for the sake of brevity.

[0227] 5D59-5D60 and 5D60-5D61 show two example scenarios where both sides of a split screen are occupied by applications associated with the enhanced edge swipe gesture criteria and are edge protected. In contrast to the example scenarios shown in 5D50-5D58, 5D59-5D60, and 5D60-61, two example scenarios are shown where an upward edge swipe gesture that meets the standard edge swipe gesture criteria is detected on the side of the split screen and not on the home affordance. Thus, the edge swipe gesture does not meet the enhanced position requirement or gesture repetition requirement of the gesture criteria of the improved edge swipe gesture associated with both applications. As a result, the edge swipe gesture (e.g., by contact 4856 or contact 4858) does not temporarily disable edge protection for the underlying application (e.g., because the extended position requirements applicable to the initial swipe are not met) and does not cause the execution of a system action (e.g., because the enhanced position requirements and gesture repetition criteria of the gesture criteria for the extended edge swipe gesture associated with the underlying application are not met.) Instead of navigating to a user interface outside the currently displayed application, the gesture is passed as input to the application underlying the gesture, and optionally causes an action to be performed within the application.

[0228] As shown in FIGS. 5D59-5D60, an upward swipe gesture by contact 4856 is detected near the bottom edge of the touchscreen at the side of the gaming application. The swipe gesture meets the gesture criteria of a standard edge swipe gesture but does not override edge protection or cause navigation to a different user interface outside of the application. In some embodiments, the gesture is passed to the underlying gaming application and piano keys in user interface 4804-2 are pressed in accordance with the gesture by contact 4856. Similarly, as shown in FIGS. 5D61-5D62, an upward swipe gesture by contact 4858 is detected near the bottom edge of the touchscreen at the side of the map application. The swipe gesture meets the gesture criteria of a standard edge swipe gesture but does not override edge protection or cause navigation to a different user interface outside of the application. In some embodiments, the gesture is passed to the underlying map application, causing a menu in user interface 4806-2 to be dragged around the screen following the gesture made by contact 4858.

[0229] Figures 5D63-5D64 illustrate that when at least one or both sides of a split screen are occupied by an edge protection application (e.g., as shown in Figure 5D63 with the home affordance in a second application state), if a virtual keyboard (e.g., virtual keyboard 4860) is invoked (e.g., in response to a tap gesture by contact 4859 within a text input field of user interface 4806-1), overlaid on the touch screen (e.g., spanning both the first and second applications on the split screen), the edge protection is temporarily disabled for both applications under the virtual keyboard. As shown in Figure 5D64, the home affordance 4802-1 is displayed in a first appearance state (e.g., opaque with standard visibility), and when an edge swipe gesture that meets the standard edge swipe gesture criteria is detected, for example, in accordance with various navigation criteria (e.g., the criteria described with respect to the processes shown in Figures 9A-9C and 10A-10D), it causes the execution of system operations including navigation from an application user interface (e.g., user interfaces 4806-2 and 4808-2) (e.g., as shown in Figure 5D64) displayed in split screen mode to a user interface external to the application, such as a system user interface (e.g., initially a transition user interface 4822-1, 4822-2, or 4822-3, and ultimately the home screen user interface, application switcher user interface), or a user interface of another application. The navigation process is similar to that of Figures 5D1-5D8 and is not repeated herein for brevity.

[0230] Figures 5D65-5D98 illustrate exemplary user interfaces displayed in split screen display mode in accordance with some embodiments, where system user interface elements change their appearance state based on one or more behaviors of an application under the system user interface element.

[0231] In the exemplary scenario shown in FIGS. 5D65-5D67, applications displayed on both sides of the split screen (e.g., with a map application displayed on the left and a game application displayed on the right) are associated with standard edge swipe gesture gesture criteria (as opposed to the extended edge swipe gesture criteria) and are not edge protected. Neither of the two applications displayed on the split screen has requested automatic display of home affordance 4802-1. When a request to resize the applications (e.g., to expand the left application and shrink the right application) is received (e.g., a drag input by contact 4862 on divider 4804 is detected), the map application on the left side of the split screen is expanded from one third of the screen width (e.g., as shown in FIG. 5D65) to half the width of the screen (e.g., as shown in FIG. 5D66), and then to two thirds of the width of the screen (e.g., as shown in FIG. 5D67). The home affordance 4802-1 is fully displayed above the gaming application on the right side of the split screen when the gaming application occupies two-thirds of the screen width, as shown in FIG. 5D65. The home affordance is displayed in a first appearance state (e.g., opaque and with normal visibility) to indicate that the underlying application (e.g., gaming application) is associated with standard edge swipe gesture criteria, as shown in FIG. 5D65. When the map application occupies one half of the split screen and the gaming application occupies one half of the split screen, the home affordance 4802-1 overlaps a portion of the map application and a portion of the gaming application, as shown in FIG. 5D66. The home affordance remains displayed in the first appearance state, and both underlying applications indicate standard edge swipe gesture gesture criteria (e.g., no edge protection enabled in either application), as shown in FIG. 5D66.When the map application occupies two-half of the screen width, the Home affordance is displayed completely on top of the map application, as shown in FIG. 5D67. The Home affordance remains displayed in a first appearance state, indicating that the underlying map application is associated with standard edge swipe gesture gesture criteria. When a split screen is shown in the configuration of FIGS. 5D65-5D67, an edge swipe gesture that meets the standard edge swipe gesture criteria will cause the system to perform an action, including, for example, navigating to a user interface outside of the currently displayed application, regardless of which side of the split screen the edge swipe gesture is detected on or whether the edge swipe gesture is detected on the Home affordance 4802-1. In these examples, because both applications have the same behavior (e.g., neither is edge protected and neither is required to automatically hide the Home affordance), the appearance state of the Home affordance is determined based on the behavior of either or both of the applications.

[0232] In the exemplary scenario shown in FIGS. 5D68-5D70, the applications displayed on the two sides of the split screen are associated with different behaviors that affect the appearance state of the home affordance 4802. For example, as shown in FIG. 5D68, the map application displayed on the left side of the split screen is associated with the standard edge swipe gesture criteria. The game application displayed on the right side of the split screen is associated with the extended edge swipe gesture criteria. Neither of the two applications displayed on the split screen has requested that the home affordance 4802 be automatically displayed. When a request to resize the applications (e.g., to expand the left appli...

Claims

1. In an electronic device having a touch-sensitive display, on the touch-sensitive display; a system user interface element indicating a location for performing a gesture that triggers a system action; a first application currently having a first set of one or more behaviors associated with the system user interface element; a second application currently having a second set of one or more behaviors associated with the system user interface element that is different from the first set of one or more behaviors; the first application and the second application are both displayed along at least a portion of a respective edge of the touch-sensitive display; the system user interface element overlaps the first application without overlapping the second application; simultaneously displaying the appearance of the system user interface element based on the first set of one or more behaviors; detecting an input corresponding to a request to resize the second application while simultaneously displaying the first application, the second application, and the system user interface element; In response to detecting the input, resizing the second application according to the input; pursuant to a determination that the system user interface element overlaps the second application without overlapping the first application, changing the appearance of the system user interface element to an appearance based on the second set of one or more behaviors associated with the system user interface element; A method comprising:

2. the first set of one or more behaviors includes extended edge swipe gesture criteria for the gesture that triggers the system action; The method of claim 1 , wherein the second set of one or more behaviors includes a standard edge swipe gesture criteria for the gesture that triggers the system action.

3. the first set of one or more behaviors includes a request to hide the system user interface element when a predetermined criterion is met; The method of any one of claims 1 to 2, wherein the second set of one or more behaviors does not include a request to hide the system user interface element when the predetermined criteria is met.

4. 4. The method of claim 1, further comprising: determining, in response to detecting the input, the appearance of the system user interface element based on a combination of the first set of one or more behaviors associated with the system user interface element and the second set of one or more behaviors associated with the system user interface element in accordance with a determination that the system user interface element overlaps the second application and the first application.

5. In response to detecting the input, determining the appearance of the system user interface element based on the first set of one or more behaviors associated with the system user interface element in accordance with determining that the system user interface element overlaps both the second application and the first application and determining that the first set of one or more behaviors includes a behavior having a higher priority than the second set of one or more behaviors; 5. The method of claim 1, further comprising: determining the appearance of the system user interface element based on the second set of one or more behaviors associated with the system user interface element in accordance with a determination that the system user interface element overlaps with both the second application and the first application, and a determination that the second set of one or more behaviors includes a behavior having a higher priority than the first set of one or more behaviors.

6. the first set of behaviors requires that extended edge swipe gesture criteria be met for an edge swipe gesture detected at a location occupied by the first application to execute the system action; the second set of behaviors requires that standard edge swipe gesture criteria be met in order for an edge swipe gesture detected at a location occupied by the first application to execute the system action; In response to detecting the input, the method further comprises: displaying the system user interface element having a first appearance in accordance with a determination that the system user interface element overlaps the first application without overlapping the second application; displaying the system user interface element having the first appearance in accordance with a determination that the system user interface element overlaps both the first application and the second application; 5. The method of claim 1, further comprising: displaying the system user interface element having a second appearance in accordance with a determination that the system user interface element overlaps the second application without overlapping the first application.

7. the first set of behaviors requires that extended edge swipe gesture criteria be met for an edge swipe gesture detected at a location occupied by the first application to execute the system action; the second set of behaviors requires that standard edge swipe gesture criteria be met in order for an edge swipe gesture detected at a location occupied by the first application to execute the system action; In response to detecting the input, the method further comprises: displaying the system user interface element having a first appearance in accordance with a determination that the system user interface element overlaps the first application without overlapping the second application; displaying the system user interface element having a second appearance in accordance with a determination that the system user interface element overlaps both the first application and the second application; 5. The method of claim 1, further comprising displaying the system user interface element having the second appearance in accordance with a determination that the system user interface element overlaps the second application without overlapping the first application.

8. the first set of one or more behaviors includes requesting a reduction in visual distinction of the system user interface element relative to a remainder of a user interface displayed on the display when a second predetermined criterion is met; the second set of one or more behaviors does not include requiring a reduction in the visual distinction of the system user interface element relative to a remainder of the user interface displayed on the display when the second predetermined criterion is met; In response to determining that the second predetermined criterion is satisfied for the first application, the method further comprises: reducing the visual distinction of the system user interface element relative to a remainder of the user interface displayed on the display in accordance with a determination that the system user interface element overlaps the first application without overlapping the second application; reducing the visual distinction of the system user interface element relative to a remainder of the user interface displayed on the display in accordance with a determination that the system user interface element overlaps both the first application and the second application; 8. The method of claim 1, further comprising forgoing the reduction in the visual distinction of the system user interface element relative to a remainder of the user interface displayed on the display in accordance with a determination that the system user interface element overlaps the second application without overlapping the first application.

9. the first set of one or more behaviors includes requesting a reduction in visual distinction of the system user interface element relative to a remainder of a user interface displayed on the display when a second predetermined criterion is met; the second set of one or more behaviors does not include requiring a reduction in the visual distinction of the system user interface element relative to a remainder of the user interface displayed on the display when the second predetermined criterion is met; In response to determining that the second predetermined criterion is satisfied for the first application, the method further comprises: reducing the visual distinction of the system user interface element relative to a remainder of the user interface displayed on the display in accordance with a determination that the system user interface element overlaps the first application without overlapping the second application; pursuant to determining that the system user interface element overlaps both the first application and the second application, refraining from reducing the visual distinction of the system user interface element relative to a remainder of the user interface displayed on the display; 8. The method of claim 1, further comprising forgoing the reduction in the visual distinction of the system user interface element relative to a remainder of the user interface displayed on the display in accordance with a determination that the system user interface element overlaps the second application without overlapping the first application.

10. the first application is associated with extended edge swipe gesture criteria, detecting an edge swipe input at a location corresponding to the system user interface element while the system user interface element is overlapped by the first application; 10. The method of claim 1, comprising changing an appearance of the system user interface element from a first appearance to a second appearance in response to detecting the edge swipe input.

11. The method of any one of claims 1 to 10, wherein the first application is associated with extended edge swipe gesture criteria and the second application is associated with standard edge swipe gesture criteria.

12. A method according to any preceding claim, wherein the appearance of the system user interface elements is influenced by underlying content of a user interface displayed on the display.

13. The method of any one of claims 1 to 12, wherein the system action is selected from a plurality of different system actions based on one or more parameters of the gesture.

14. A touch-sensitive display; one or more processors; and a memory storing one or more programs, the one or more programs being configured to be executed by the one or more processors, the one or more programs comprising: on the touch-sensitive display; a system user interface element indicating a location for performing a gesture that triggers a system action; a first application currently having a first set of one or more behaviors associated with the system user interface element; a second application currently having a second set of one or more behaviors associated with the system user interface element that is different from the first set of one or more behaviors; the first application and the second application are both displayed along at least a portion of a respective edge of the touch-sensitive display; the system user interface element overlaps the first application without overlapping the second application; simultaneously displaying the appearance of the system user interface element based on the first set of one or more behaviors; detecting an input corresponding to a request to resize the second application while simultaneously displaying the first application, the second application, and the system user interface element; In response to detecting the input, resizing the second application according to the input; pursuant to a determination that the system user interface element overlaps the second application without overlapping the first application, changing the appearance of the system user interface element to an appearance based on the second set of one or more behaviors associated with the system user interface element. An electronic device that contains instructions.

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

16. 1. A program comprising instructions that, when executed by an electronic device having a touch-sensitive display, cause the device to: on the touch-sensitive display; a system user interface element indicating a location for performing a gesture that triggers a system action; a first application currently having a first set of one or more behaviors associated with the system user interface element; a second application currently having a second set of one or more behaviors associated with the system user interface element that is different from the first set of one or more behaviors; the first application and the second application are both displayed along at least a portion of a respective edge of the touch-sensitive display; the system user interface element overlaps the first application without overlapping the second application; simultaneously displaying the appearance of the system user interface element based on the first set of one or more behaviors; detecting an input corresponding to a request to resize the second application while simultaneously displaying the first application, the second application, and the system user interface element; In response to detecting the input, resizing the second application according to the input; pursuant to a determination that the system user interface element overlaps the second application without overlapping the first application, changing the appearance of the system user interface element to an appearance based on the second set of one or more behaviors associated with the system user interface element. This causes the program.

17. A program according to claim 16, comprising instructions which, when executed by the electronic device, cause the electronic device to carry out the method according to any one of claims 2 to 13.

Images