Device, method, and graphical user interface for navigating between user interfaces, displaying dock, and displaying system user interface element

By employing edge swipe gestures and real-time visual feedback on touch-sensitive displays, the method addresses the inefficiencies in navigating user interfaces and managing system elements on electronic devices, enhancing user interaction and energy conservation.

JP2025087681APending Publication Date: 2025-06-10APPLE INC
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2025015033
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2018-10-29
Filing Date
2025-01-31
Publication Date
2025-06-10

AI Technical Summary

Technical Problem

Existing methods for navigating between user interfaces, displaying docks, and displaying system user interface elements on electronic devices with touch-sensitive surfaces are cumbersome, inefficient, and energy-intensive, particularly in battery-operated devices.

Method used

The implementation of a method that utilizes edge swipe gestures on a touch-sensitive display to dynamically navigate between user interfaces, display docks at user-defined positions, and manage system user interface elements, while providing real-time visual feedback and edge protection to enhance user interaction and efficiency.

Benefits of technology

This solution reduces the number and complexity of user inputs, improves navigation efficiency, conserves energy, and extends battery life by allowing for intuitive and quick access to various user interfaces and system elements on electronic devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025087681000001_ABST
    Figure 2025087681000001_ABST
Patent Text Reader

Abstract

To provide a faster and more efficient method, an interface, and an electronic device equipped therewith for displaying a user interface.SOLUTION: An electronic device with a touch-sensitive display displays a first user interface that is distinct from a home screen. The device detects a first input on a first edge of the display. In response, while a first contact continues to be detected on the first edge, the device, when the first input was detected on a first portion of the first edge and the first input meets dock-display criteria, displays a dock with a plurality of application icons at a first location along the first edge and, when the first input was detected on a second portion of the first edge that is distinct from the first portion and the first input meets the dock-display criteria, displays the dock at a second location along the first edge that is selected to include the second potion of the first edge, the second location being different from the first location.SELECTED DRAWING: Figure 1A
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application generally relates to electronic devices having a touch-sensitive surface and includes, but is not limited to, electronic devices having a touch-sensitive surface for navigation between user interfaces, display of docks, and display of system user interface elements (e.g., home affordances).

Background Art

[0002] The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Exemplary touch-sensitive surfaces include touch pads and touch screen displays. Such surfaces are widely used to manipulate user interfaces and objects therein. Exemplary user interface objects include digital images, videos, 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 buttons, or opening files / applications represented by user interface objects, associating metadata with one or more user interface objects, navigating between user interfaces, or otherwise manipulating the user interface. Exemplary user interface objects include digital images, videos, text, icons, and control elements such as buttons and other graphics. In some situations, the user may need to perform such operations on user interface objects in a file management program (e.g., Finder from Apple Inc., Cupertino, California), an image management application (e.g., Aperture, iPhoto, Photos from Apple Inc., Cupertino, California), a digital content (e.g., video and music) management application (e.g., iTunes® from Apple Inc., Cupertino, California), a drawing application, a presentation application (e.g., Keynote from Apple Inc., Cupertino, California), a word processing application (e.g., Pages from Apple Inc., Cupertino, California), or a spreadsheet application (e.g., Numbers from Apple Inc., Cupertino, California).

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

Summary of the Invention

[0005] Accordingly, there is a need for a faster and more efficient method and interface for navigation between user interfaces, display of a dock, and display of system user interface elements (e.g., home affordances), and an electronic device with such an interface. Such a method and interface optionally complements or replaces conventional methods for navigation between user interfaces, display of a dock, and display of system user interface elements (e.g., home affordances). Such a method and interface reduces the number, scope, and / or type of inputs from the user and generates a more efficient human-machine interface. For battery-operated devices, such a method and interface saves power and extends the time between battery charges.

[0006] The above-mentioned defects and other problems associated with the user interface for an electronic device having a touch-sensing surface 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-sensing 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 plurality of functions. In some embodiments, the user interacts with the GUI primarily through a stylus and / or finger contact and gestures on the touch-sensing surface. In some embodiments, the functions optionally include image editing, drawing, presenting, word processing, spreadsheet creation, game play, making a phone call, video conferencing, sending an email, instant messaging, training support, digital photography, digital video recording, web browsing, playing digital music, taking notes, and / or playing digital video. The executable instructions for performing those functions are optionally included in 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, the method is executed 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 the first user interface is being displayed on the display. The method further includes, in response to detecting the first input on the edge of the display, while the first contact continues to be detected at the first edge of the display, the first input is detected on a first portion of the first edge of the display, and according to a determination that the first input meets the dock display criteria, displaying a dock having a plurality of application icons at a first position along the first edge of the display, the first input is detected on a second portion of the first edge of the display that is different from the first portion of the first edge, and according to a determination that the first input meets the dock display criteria, displaying a dock at a second position along the first edge of the display that includes the second portion of the first edge of the display and is selected such that the second position is different from the first position.

[0008] According to some embodiments, the method is performed on a device having a touch sensing 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 including 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, according to a determination that the first input meets a first criterion, the first criterion including a requirement for movement exceeding a first threshold amount in the first direction for the first criterion to be met, replacing the display of the first user interface and the second user interface with a full screen home screen; according to a determination that the first input meets a second criterion, the second criterion including a requirement that the first input includes movement less than the first threshold amount in the first direction for the second criterion to be met, according to a determination that the first input is initiated within a first edge region of the display corresponding to the first application user interface, replacing the display of the first user interface with a first replacement user interface while maintaining the display of the second application user interface within the second portion of the display, according to a determination that the first input meets the second criterion, according to a determination that the first input is initiated within a second edge region corresponding to the second application user interface, replacing the display of the second user interface with a second replacement user interface while maintaining the display of the first application user interface within the first portion of the display.

[0009] According to some embodiments, the method is performed in a device having a touch sensing surface and a display. The method includes displaying, on the display, a user interface of a first application of a plurality of applications installed on the device. The method detects a gesture on the touch sensing surface, and detecting the gesture includes detecting an initial portion of the gesture while the user interface of the first application is being displayed on the display, and detecting the gesture further includes simultaneously detecting a plurality of contacts on the touch sensing surface and detecting a movement of the plurality of contacts. The method further, in response to detecting the gesture on the touch sensing surface, in accordance with a determination that the gesture includes two simultaneously detected contacts, performs an operation in the first application based on a movement of the two simultaneously detected contacts between the gestures, and in accordance with a determination that the gesture includes more than two simultaneously detected contacts exceeding a predetermined number and a determination that a movement of the simultaneously detected contacts between the gestures meets a first criterion, switches from displaying the user interface of the first application to displaying a user interface of a second application of a plurality of applications separate from the first application, and in accordance with a determination that the gesture includes more than two simultaneously detected contacts exceeding a predetermined number and a determination that a movement of the simultaneously detected contacts between the gestures meets a second criterion separate from the first criterion, switches from displaying the user interface of the first application to displaying a user interface including respective application icons for opening a plurality of applications installed on the device.

[0010] According to some embodiments, the method is executed on a device having a touch-sensitive display. The method includes simultaneously displaying a first application and a second application on the touch-sensitive display, where both the first application and the second application are displayed along at least a portion of respective edges of the touch-sensitive display. While simultaneously displaying the first application and the second application, detecting movement of a first edge swipe gesture at respective positions along each edge of the touch-sensitive display, including movement of contact from respective positions along each edge of the touch-sensitive display onto the touch-sensitive display. In response to detecting the first edge swipe gesture, performing system operations according to a determination that respective positions of the first edge swipe gesture correspond to a position of the first application on the touch-sensitive display, a determination that the first application is simultaneously associated with standard edge swipe gesture criteria, and a determination that the first edge swipe gesture meets the standard edge swipe gesture criteria, where the standard edge swipe gesture includes a first set of one or more requirements that must be met for the standard edge swipe gesture criteria to be satisfied, 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. Performing system operations according to a determination that respective positions of the first edge swipe gesture correspond to a position of the second application on the touch-sensitive display, a determination that the second application is simultaneously associated with standard edge swipe gesture criteria, and a determination that the first edge swipe gesture meets the standard edge swipe gesture criteria. Performing system operations according to a determination that respective positions of the first edge swipe gesture correspond to a position of the first application on the touch-sensitive display, a determination that the first application is simultaneously associated with extended edge swipe gesture criteria,And in accordance with the determination that the first edge swipe gesture meets the extended edge swipe gesture criteria, the extended edge swipe gesture includes a first set of one or more requirements that must be met for the standard edge swipe gesture criteria to be met, and also includes 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, stopping the execution of the system operation, determining that each position of the first edge swipe gesture corresponds to the position of a second application on the touch-sensitive display, determining that the second application is associated with the extended edge swipe gesture criteria as being simultaneously displayed, and stopping the execution of the system operation in accordance with the determination that the first edge swipe gesture does not meet the extended edge swipe gesture criteria.

[0011] According to some embodiments, the method is executed on a device having a touch-sensitive display. The method includes a system user interface element indicating a position for performing a gesture that triggers system operation, 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, the second set of one or more behaviors being different from the first set of one or more behaviors, wherein both the first application and the second application are displayed along at least a portion of each edge of the touch-sensitive display, the system user interface element overlaps the first application without overlapping the second application, the appearance of the system user interface element is 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, resizing the second application according to the input in response to detecting the input, and changing the appearance of the system user interface element to an appearance based on a second set of one or more behaviors associated with the system user interface element according to a determination that the system user interface element overlaps the second application without overlapping the first application.

[0012] According to some embodiments, an electronic device includes a display, a touch sensing surface, optionally one or more sensors for detecting the intensity of contact with the touch sensing surface, optionally one or more haptic output generators, 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 and 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 stores instructions therein, and when the instructions are executed by an electronic device having a display, a touch sensing surface, optionally one or more sensors for detecting the intensity of contact with the touch sensing surface, and optionally one or more haptic output generators, the instructions 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 sensing surface, optionally one or more sensors for detecting the intensity of contact with the touch sensing surface, optionally one or more haptic output generators, a memory, and one or more processors for executing the one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described herein, and the elements are updated in response to input as described in any of the methods described herein. According to some embodiments, an electronic device includes a display, a touch sensing surface, optionally one or more sensors for detecting the intensity of contact with the touch sensing surface, optionally one or more haptic 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 sensing surface, optionally one or more sensors for detecting the intensity of contact with the touch sensing surface, and optionally one or more haptic output generators includes means for performing or causing to be performed any of the operations of the methods described herein.

[0013] Thus, an electronic device having a display, a touch sensing surface, optionally one or more sensors for detecting the intensity of contact with the touch sensing surface, optionally one or more haptic output generators, optionally one or more device orientation sensors, and optionally an audio system provides an improved method and interface for navigating between user interfaces, displaying a dock, and also displaying system user interface elements (e.g., home affordances), thereby enhancing the effectiveness, efficiency, and user satisfaction of such a device. Such methods and interfaces can complement or replace conventional methods for navigation between user interfaces, display of a dock, and display of system user interface elements (e.g., home affordances).

Brief Description of the Drawings

[0014] To better understand the various embodiments described, the following "Detailed Description of the Invention" should be referred to in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout the following figures.

[0015]

Figure 1A

[0016]

Figure 1B

[0017]

Figure 2

[0018]

Figure 3

[0019]

Figure 4A

[0020]

Figure 4B

[0021]

Figure 4C

Figure 4D

Figure 4E

[0022]

Figure 5A1

Figure 5A2

Figure 5A3

Figure 5A4

Figure 5A5

Figure 5A6

Figure 5A7

Figure 5A8

Figure 5A9

Figure 5A10

Figure 5A11

Figure 5A12

Figure 5A13

Figure 5A14

Figure 5A15

Figure 5A16

Figure 5A17

Figure 5A18

Figure 5A19

Figure 5A20

Figure 5A21

Figure 5A22

Figure 5A23

Figure 5A24

Figure 5A25

Figure 5A26

Figure 5A27

Figure 5A28

Figure 5A29

[0023]

Figure 5B1

Figure 5B2

Figure 5B3

Figure 5B4

Figure 5B5

Figure 5B6

Figure 5B7

Figure 5B8

Figure 5B9

Figure 5B10

Figure 5B11

Figure 5B12

Figure 5B13

Figure 5B14

Figure 5B15

Figure 5B16

Figure 5B17

Figure 5B18

Figure 5B19

Figure 5B20

Figure 5B21

Figure 5B22

Figure 5B23

Figure 5B24

Figure 5B25

Figure 5B26

Figure 5B27

Figure 5B28

Figure 5B29

Figure 5B30

Figure 5B31

Figure 5B32

Figure 5B33

Figure 5B34

Figure 5B35

Figure 5B36

[0024]

Figure 5C1

Figure 5C2

Figure 5C3

Figure 5C4

Figure 5C5

Figure 5C6

Figure 5C7

Figure 5C8

Figure 5C9

Figure 5C10

Figure 5C11

Figure 5C12

Figure 5C13

Figure 5C14

Figure 5C15

Figure 5C16

Figure 5C17

Figure 5C18

Figure 5C19

Figure 5C20

Figure 5C21

Figure 5C22

Figure 5C23

Figure 5C24

Figure 5C25

Figure 5C26

Figure 5C27

Figure 5C28

Figure 5C29

Figure 5C30

Figure 5C31

Figure 5C32

Figure 5C33

Figure 5C34

Figure 5C35

Figure 5C36

Figure 5C37

Figure 5C38

Figure 5C39

Figure 5C40

Figure 5C41

Figure 5C42

Figure 5C43

Figure 5C44

Figure 5C45

Figure 5C46

Figure 5C47

Figure 5C48

Figure 5C49

Figure 5C50

Figure 5C51

Figure 5C52

Figure 5C53

Figure 5C54

Figure 5C55

Figure 5C56

Figure 5C57

Figure 5C58

Figure 5C59

[0025]

Figure 5D1

Figure 5D2

Figure 5D3

Figure 5D4

Figure 5D5

Figure 5D6

Figure 5D7

Figure 5D8

Figure 5D9

Figure 5D10

Figure 5D11

Figure 5D12

Figure 5D13

Figure 5D14

Figure 5D15

Figure 5D16

Figure 5D17

Figure 5D18

Figure 5D19

Figure 5D20

Figure 5D21

Figure 5D22

Figure 5D23

Figure 5D24

Figure 5D25

Figure 5D26

Figure 5D27

Figure 5D28

Figure 5D29

Figure 5D30

Figure 5D31

Figure 5D32

Figure 5D33

Figure 5D34

Figure 5D35

Figure 5D36

Figure 5D37

Figure 5D38

Figure 5D39

Figure 5D40

Figure 5D41

Figure 5D42

Figure 5D43

Figure 5D44

Figure 5D45

Figure 5D46

Figure 5D47

Figure 5D48

Figure 5D49

Figure 5D50

Figure 5D51

Figure 5D52

Figure 5D53

Figure 5D54

Figure 5D55

Figure 5D56

Figure 5D57

Figure 5D58

Figure 5D59

Figure 5D60

Figure 5D61

Figure 5D62

Figure 5D63

Figure 5D64

[0026]

Figure 5D65

Figure 5D66

Figure 5D67

Figure 5D68

Figure 5D69

Figure 5D70

Figure 5D71

Figure 5D72

Figure 5D73

Figure 5D74

Figure 5D75

Figure 5D76

Figure 5D77

Figure 5D78

Figure 5D79

Figure 5D80

Figure 5D81

Figure 5D82

Figure 5D83

Figure 5D84

Figure 5D85

Figure 5D86

Figure 5D87

Figure 5D88

Figure 5D89

Figure 5D90

Figure 5D91

Figure 5D92

Figure 5D93

Figure 5D94

Figure 5D95

Figure 5D96

Figure 5D97

Figure 5D98

[0027]

Figure 5D99

[0028]

Figure 6A

Figure 6B

Figure 6C

Figure 6D

Figure 6E

Figure 6F

[0029]

Figure 7A

Figure 7B

Figure 7C

Figure 7D

Figure 7E

Figure 7F

Figure 7G

Figure 7H

Figure 7I

[0030]

Figure 8

[0031]

Figure 9A

Figure 9B

Figure 9C

[0032]

Figure 10A

Figure 10B

Figure 10C

Figure 10D

[0033]

Figure 11A

Figure 11B

Figure 11C

Figure 11D

Figure 11E

Figure 11F

[0034]

Figure 12A

Figure 12B

Figure 12C

Figure 12D

Figure 12E

Figure 12F

[0035]

Figure 13A

Figure 13B

Figure 13C

Figure 13D

Figure 13E

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

[0037] Furthermore, when operating a larger device (e.g., a tablet computer), 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 start from positions on the device that are away from the orientation of the user's hands. Since the hands must be engaged in supporting the device, it is similarly difficult to operate a larger device with a single hand. The following embodiments provide an input that enables the display of an application dock as a user-defined position along one or more edges of the device (e.g., an affordance that displays multiple application icons for opening / navigating to specific applications), thereby improving user interface navigation on larger devices. This allows the user to access the application dock without having to reposition their hand on the device (e.g., to a proximal position regardless of where that hand is located on the device). This saves time when operating the device (e.g., by avoiding the need for the user to reposition their hand before calling and / or interacting with the application dock), and in turn saves the device's battery life.

[0038] Furthermore, the following embodiments provide gestures that prompt navigation to different user interfaces (e.g., recently opened applications, home screen user interface, and application switcher user interface) within a secondary 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 the position, timing, movement parameters of the displayed user interface objects). This provides easy access to the device's navigation functions without cluttering the user interface with additional displayed controls, reduces the amount and number of input times required to achieve the intended screen configuration, and in addition, reduces the device's power consumption and improves battery life.

[0039] Furthermore, the following embodiments facilitate navigation from an application user interface to another user interface external to the application, for example, to a different application or a system user interface (e.g., a home screen), or execute an operation within the application based on a gesture initiated from the application user interface (e.g., a gesture executed with multiple simultaneously detected contacts). In these embodiments, the result of the gesture is that a plurality of different sets of criteria (e.g., criteria based on the gesture type executed by the contact, the total number of simultaneously detected contacts, the position, timing, and / or movement parameters of the contacts, and / or the user interface objects being displayed) are satisfied by the gesture (e.g., at the time the gesture ends). When determining the destination state of the device (e.g., which operation to execute 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 possible destination state of the device is continuously displayed to indicate, and the dynamic visual feedback gives the user an opportunity to adjust the input to correct the actual destination state of the device reached after the input has ended. By using different sets of criteria to determine the final destination state of the device (e.g., the last operation executed and / or the final user interface displayed), the user can use fluid gestures and may modify the intermediate stream to achieve the intended result (e.g., because the user has decided to change what they want to achieve or based on device feedback that the user has provided an inaccurate input for the intended result).This eliminates the impact of unintended gestures by the user, subsequently avoiding the need to restart the gesture, making the interface of the user device more efficient (e.g., by assisting in providing the input necessary to achieve the result intended by the user and reducing user errors during device operation / interaction), thereby further enabling the user to use the device more quickly and efficiently, reducing power consumption of the device and improving battery life.

[0040] Furthermore, the following embodiments provide an intuitive way to enable edge protection against inadvertent triggers of system operation that replace the split-screen user interface that displays two applications in the system user interface, where the edge protection is enabled independently for one or both of the applications. Enabling edge protection independently for the applications on both sides of the split screen while at the same time enabling the replacement of the system operation that replaces the entire split-screen user interface with the system user interface enhances the operability of the device, makes the user-device interaction more efficient (e.g., by providing easy access to the device's navigation function, by assisting the user to achieve the intended result with fewer required inputs, and by providing additional control options without disturbing the user interface using additional displayed controls), reduces user errors when operating the device (e.g., by selectively using gesture criteria extended to a part of the user interface to avoid inadvertent triggers of system operation), and further enables the user to use the device more quickly and efficiently, reducing power consumption and improving the battery life of the device.

[0041] Furthermore, as described in the following embodiments, a system user interface element that overlays two applications related to distinct behaviors associated with system user interface elements and that is displayed on a split screen user interface obtains different appearances depending on the behavior of the application below the system user interface element when the application is resized on the split screen user interface. The appearance of the system user interface element provides useful visual feedback to assist in providing appropriate input for the user to achieve a desired result, reducing user errors when operating on the device, and thereby creating a more efficient human-machine interface. In a battery-operated electronic device, providing useful visual feedback and reducing user errors when navigating between user interfaces within a split screen display mode and / or inside and outside of a split screen display mode conserves power and increases the time between battery charges.

[0042] The following, FIGS. 1A, 1B, 2, and 3 provide an illustration of an exemplary device. FIGS. 4C - 4E show examples of dynamic intensity thresholds. FIGS. 4A - 4B, 5A1 - 5A29, 5B1 - 5B36, 5C1 - 5C59, 5D1 - 5D99 show exemplary user interfaces for navigating between user interfaces, displaying a dock, or performing operations within an application, and showing system user interface elements such as home affordances. FIGS. 6A - 6F show a flowchart of a method for displaying a dock with a plurality of application icons at variable positions along one or more edges of a touch - sensitive display. FIGS. 7A - 7I show a flowchart of a method for navigating from a user interface displayed in a split - screen display mode to a different user interface. FIGS. 11A - 11F are flowcharts of a process for navigating between user interfaces based on multi - touch gestures. FIGS. 12A - 12F are flowcharts of a method for performing system operations (e.g., navigating from an application user interface displayed in a split - screen display mode to a different user interface outside the application). FIGS. 13A - 13E are flowcharts of a method for displaying system user interface elements (e.g., home affordances) having different appearance states based on one or more behaviors of one or more applications (singular or plural) under 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 flowchart showing various criteria used for navigating between user interfaces according to some embodiments. FIGS. 9A - 9C show exemplary thresholds for navigating between different user interfaces. FIGS. 10A - 10D are flowcharts showing various criteria used for navigating between user interfaces according to some embodiments. Exemplary device

[0043] Reference will now be made in detail to embodiments 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 described. However, it will be apparent to one of ordinary skill in the art that the various embodiments described may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

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

[0045] The terms used in the description of the various embodiments described herein are for the purpose of describing particular embodiments only and are not intended to be limiting. In the description of the various embodiments and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural as well, unless the context clearly dictates otherwise. Also, 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 should be understood that the terms "includes", "including", "comprises", and / or "comprising", when used herein, specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

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

[0047] Embodiments of electronic devices, user interfaces for such devices, and related 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 functionality and / or music player functionality. Exemplary embodiments of portable multifunctional devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc., Cupertino, California. Other portable electronic devices, such as laptop or tablet computers having a touch-sensitive surface (e.g., a touch screen display and / or a touch pad), may optionally be used. It is 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 touch screen display and / or a touch pad).

[0048] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it is understood that the electronic device may optionally include one or more other physical user interface devices, such as a physical keyboard, a mouse, and / or a joystick.

[0049] The device generally supports various applications, such as one or more of a note-taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a game application, a telephone application, a video conferencing application, an email application, an instant messaging application, a training support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.

[0050] 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 functions of the touch-sensitive surface, as well as the corresponding information displayed on the device, are optionally adjusted and / or changed for each application and / or within each respective application. Thus, the common physical architecture of the device (such as a touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and transparent to the user.

[0051] Attention is now directed to an embodiment of a portable device having a touch-sensitive display. FIG. 1A is a block diagram showing a portable multifunctional device 100 (shown as device 11 in FIGS. 5D1-5D98) having a touch-sensitive display system 112, according to some embodiments. The touch-sensitive display system 112 may be referred to as a "touch screen" for convenience, or simply as a touch-sensitive display. Device 100 includes a memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input or control devices 116, and an external port 124. Device 100 optionally includes one or more light sensors 164. Device 100 optionally includes one or more intensity sensors 165 for detecting the intensity of contact on a touch-sensitive surface of device 100 (such as the touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more haptic output generators 167 for generating haptic output on device 100 (such as on a touch-sensitive surface like the touch-sensitive display system 112 of device 100 or the touch pad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0052] As used in this specification and the claims, the term "haptic output" refers to a physical displacement of the device relative to its previous position, a physical displacement of a component of the device (e.g., a touch-sensing surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device that will be detected by the user's sense of touch. For example, in a situation where the device or a component of the device is in contact with a touch-sensitive surface of the user (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or the component of the device. For example, the movement of a touch-sensing surface (e.g., a touch-sensing display or a trackpad) may optionally be interpreted by the user as a "down click" or "up click" of a physical actuator button. In some cases, the user may feel a tactile sensation such as a "down click" or "up click" even when there is no movement of the physical actuator button associated with the touch-sensing surface that has been physically pushed (e.g., displaced) by the user's action. As another example, the movement of a touch-sensing surface may optionally be interpreted or perceived by the user as the "roughness" of the touch-sensing surface even if there is no change in the smoothness of the touch-sensing surface. Such an interpretation of touch by the user depends on the user's individual sensory perception, but there are many sensory perceptions of touch that are common to the majority of users. Therefore, when a haptic output is described as corresponding to a particular sensory perception of the user (e.g., "up click", "down click", "roughness"), unless otherwise specified, the generated haptic output corresponds to a physical displacement of the device or a component of the device that produces the described sensory perception of a typical (or average) user.By providing haptic feedback to a user using tactile output, the operability of a device is improved, the user-device interface becomes more efficient (e.g., by assisting the user in providing appropriate input and reducing user errors when operating / interacting with the device), and in addition, by enabling the user to use the device more quickly and efficiently, power usage is reduced and the battery life of the device is improved.

[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 haptic outputs having different haptic output patterns are generated by a device (e.g., via one or more haptic output generators that move a movable mass to generate the haptic output), the haptic outputs can cause different tactile sensations when a user holds or touches the device. When the user's sensation is based on the user's perception of the haptic output, most users are able to distinguish changes in the waveform, frequency, and amplitude of the haptic output generated by the device. Thus, the waveform, frequency, and amplitude can be adjusted to indicate to the user that different operations have been performed. Thus, in some situations, haptic outputs having haptic output patterns designed, selected, and / or developed to simulate the properties (e.g., size, material, weight, stiffness, smoothness, etc.), behavior (e.g., vibration, displacement, acceleration, rotation, expansion, etc.), and / or interactions (e.g., collision, adhesion, repulsion, attraction, friction, etc.) of an object 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) provide useful feedback to the user that reduces input errors and increases the efficiency of the user's operation of the device. Additionally, the haptic output is optionally generated to correspond to feedback unrelated to simulated physical characteristics such as input thresholds or object selections. In some situations, such haptic outputs provide useful feedback to the user that reduces input errors and increases the efficiency of the user's operation of the device.

[0055] In some embodiments, haptic output having a suitable haptic output pattern serves as a cue for the occurrence of a target event behind a scene within a user interface or within a device. Examples of target events include activation of affordances (e.g., physical buttons, virtual buttons, or toggle switches) provided on the device or within the user interface, success or failure of a requested operation, reaching or exceeding a boundary within the user interface, entering a new state, switching the input focus between objects, activating a new mode, reaching or exceeding an input threshold, detecting or recognizing the type of an input or gesture, and the like. In some embodiments, the haptic output is provided to serve as a warning or alert for an upcoming event or result that occurs in the near future, provided that no redirection or interrupt input is detected in a timely manner. The haptic output may also be 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 the device. The haptic output optionally includes an audio output and / or a change in the visual user interface, further enhancing the user's experience when interacting with the user interface and / or the device, facilitating better communication of information regarding the state of the user interface and / or the device, reducing input errors, and increasing the efficiency of the user's actions on the device.

[0056] Device 100 is merely an example of a portable multifunctional device, and it should be understood that Device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of those 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 a high-speed random access memory and also 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 peripheral interface 118, is optional and is controlled by memory controller 122.

[0058] Peripheral interface 118 can be used to couple the input and output peripheral devices of the device to CPU(s) 120 and memory 102. One or more processors 120 operate or execute various software programs and / or instruction sets stored in memory 102 to perform various functions for device 100 and process data.

[0059] In some embodiments, peripheral 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 RF (radio frequency) circuit 108 transmits and receives RF signals, also called electromagnetic signals. The RF circuit 108 converts electrical signals into electromagnetic signals or vice versa and communicates with a communication network and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes well-known circuits for performing these functions, such as, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and the like. The RF circuit 108 optionally communicates wirelessly with networks such as the Internet, also called the World Wide Web, an intranet, and / or a wireless network such as a cellular telephone network, a wireless local area network (LAN), and / or a metropolitan area network (MAN), and with other devices. The wireless communication is optionally Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code divisionAny one of a plurality of communication standards, communication protocols, and communication technologies is used, including, but not limited to, multiple access (e.g., code division multiple access (CDMA)), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., 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 Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of the present document.

[0061] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts this audio data into an electrical signal, and transmits this electrical signal to the speaker 111. The speaker 111 converts the electrical signal into human audible sound waves. Also, the audio circuit 110 receives the electrical signal converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data and transmits this audio data to the peripheral device interface 118 for processing. The audio data is optionally obtained from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripheral device interface 118. In some embodiments, the audio circuit 110 further includes a headset jack (e.g., 212, FIG. 2). The headset jack provides an interface between the audio circuit 110 and a detachable audio input / output peripheral device such as an output-only headset or a headset with both output (e.g., mono or stereo headphones) and input (e.g., microphone).

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

[0063] The touch-sensing display system 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from, and / or transmits electrical signals to, the touch-sensing display system 112. The touch-sensing display system 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term "affordance" refers to a user-interactive form of graphical user interface object (e.g., a graphical user interface object configured to respond to input directed towards the graphical user interface object). Examples of user-interactive forms of graphical user interface objects include, but are not limited to, buttons, sliders, icons, selectable menu items, switches, hyperlinks, or other user interface controls.

[0064] The touch-sensing display system 112 has a touch-sensing surface, sensor, or set of sensors that receives input from the user based on tactile and / or haptic contact. The touch-sensing display system 112 and the display controller 156 (along with any associated modules and / or instruction sets in the memory 102) detect contact (and any movement or interruption of the contact) on the touch-sensing display system 112 and translate the detected contact into an interaction with a user interface object (e.g., one or more soft keys, icons, web page, or image) displayed on the touch-sensing display system 112. In some embodiments, the point of contact between the touch-sensing display system 112 and the user corresponds to the user's finger or stylus.

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

[0066] The touch-sensing display system 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the video resolution of the touch screen is greater than 400 dpi (e.g., 500 dpi, 800 dpi, or higher). The user optionally uses any suitable object or appendage, such as a stylus, finger, etc., to contact the touch-sensing display system 112. In some embodiments, the user interface is designed to function with finger-based contact and gestures, which may be less accurate than stylus-based input due to the larger contact area of the finger on the touch screen compared to the contact area of the stylus. In some embodiments, the device converts rough input by the finger into an accurate pointer / cursor position or command for performing the action desired by the user.

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

[0068] Device 100 also includes a power system 162 that supplies power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharge system, a power outage detection circuit, a power converter or inverter, a power status indicator (e.g., light-emitting diode (LED)), and any other components associated with the generation, management, and distribution of power within a portable device.

[0069] In addition, device 100 optionally includes one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to an optical sensor controller 158 within I / O subsystem 106. The optical sensor(s) 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. The optical sensor(s) 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. In cooperation with imaging module 143 (also referred to as a camera module), the optical sensor(s) 164 optionally captures still images and / or video. In some embodiments, the optical sensor is disposed on the back surface of device 100, opposite touch-sensing display system 112 on the front surface of the device, so that the touch screen can be used as a viewfinder for acquiring still images and / or video images. In some embodiments, another optical sensor is disposed on the front surface of the device so that an image of the user is acquired (e.g., for selfies, for video conferencing while the user is looking at other video conferencing 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 an intensity sensor controller 159 within I / O subsystem 106. The contact intensity sensor(s) 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric force sensors, optical force sensors, capacitive touch sensing surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of contact on a touch sensing surface). The contact intensity sensor(s) 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed with, or proximate to, a touch sensing surface (e.g., touch sensing display system 112). In some embodiments, at least one contact intensity sensor is disposed on the back surface of device 100, opposite a touch screen display system 112 located on the front surface of device 100.

[0071] Also, device 100 optionally includes one or more proximity sensors 166. FIG. 1A shows a proximity sensor 166 coupled to a peripheral device interface 118. Alternatively, the proximity sensor 166 is coupled to an input controller 160 within I / O subsystem 106. In some embodiments, when a multifunctional device is placed near a user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch sensing display system 112.

[0072] Device 100 also optionally includes one or more haptic output generators 167. FIG. 1A shows a haptic output generator coupled to a haptic feedback controller 161 within I / O subsystem 106. In some embodiments, the haptic 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 movement, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components that convert an electrical signal into a haptic output) on the device. The haptic output generator(s) 167 receive haptic feedback generation instructions from the haptic feedback module 133 and generate haptic output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed with, or proximate to, a touch sensing surface (e.g., touch sensing display system 112), and optionally generates haptic output by moving the touch sensing surface in a vertical direction (e.g., in / out of the surface of device 100) or a horizontal direction (e.g., back and forth within the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is disposed on the back surface of device 100, opposite a touch sensing display system 112 located on the front surface of device 100.

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

[0074] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or set of instructions) 128, a touch / motion module (or set of instructions) 130, a graphics module (or set of instructions) 132, a haptic feedback module (or set of instructions) 133, a text input module (or set of instructions) 134, a Global Positioning System (GPS) module (or set of instructions) 135, and an application (or set of instructions) 136. Further, in some embodiments, as shown in FIGS. 1A and 3, memory 102 stores a device / global internal state 157. The device / global internal state 157 includes one or more of an active application state indicating which application is active if there is a currently active application, a display state indicating which application, view, or other information occupies various regions of the touch-sensitive display system 112, a sensor state including information obtained from various sensors of the device and other input or control devices 116, and position and / or orientation information regarding the position and / or orientation of the device.

[0075] The operating system 126 (e.g., an embedded operating system such as iOS (trademark), Darwin, RTXC, LINUX (trademark), UNIX (registered trademark), OS X (registered trademark), WINDOWS (registered trademark), or VxWorks (trademark)) 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 facilitates communication between various hardware components and software components.

[0076] The communication module 128 also includes various software components for facilitating communication with other devices via one or more external ports 124 and processing data received by the RF circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FIREWIRE (registered trademark), etc.) is adapted to couple directly or indirectly via a network (e.g., the Internet, a wireless LAN, etc.) to other devices. In some embodiments, the external port is the same as, similar to, and / or compatible with a 30-pin connector used in some iPhone (registered trademark), iPod Touch (registered trademark), and iPad (registered trademark) devices from Apple Inc. of Cupertino, California. In some embodiments, the external port is the same as, similar to, and / or compatible with a Lightning (trademark) connector used in some iPhone (registered trademark), iPod Touch (registered trademark), and iPad (registered trademark) devices from Apple Inc. of Cupertino, California.

[0077] The contact / motion module 130 optionally detects contact with the touch sensing display system 112 (in cooperation with the display controller 156) and contact with other touch sensing devices (e.g., a touch pad or a physical click wheel). The contact / motion module 130 includes software components for performing various operations related to the detection of contact (e.g., by a finger or a stylus), such as determining whether 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 something that substitutes for the force or pressure of the contact), determining whether there is movement of the contact, and tracking movement across the touch sensing surface (e.g., detecting a drag event of one or more fingers), and determining whether the contact has stopped (e.g., detecting a finger up event or an interruption of the contact). The contact / motion module 130 receives contact data from the touch sensing surface. Determining the movement of the contact point, represented by a series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These operations are optionally applied to a single contact (e.g., contact by one finger or a stylus) or multiple simultaneous contacts (e.g., "multi-touch" / contact by multiple fingers). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the touch pad.

[0078] The contact / motion module 130 optionally detects gesture inputs by a user. Different gestures on the touch sensing surface have different contact patterns (e.g., the detected contact movement, timing, and / or intensity are different). Thus, gestures are optionally detected by detecting a specific contact pattern. For example, detecting a finger tap gesture includes detecting a finger down event and subsequently detecting a finger up (lift off) event at the same position (or substantially the same position) as the finger down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch sensing surface includes detecting a finger down event, subsequently detecting one or more finger drag events, and then detecting a finger up (lift off) event. Similarly, taps, swipes, drags, and other gestures are optionally detected for a stylus by detecting a specific contact pattern for 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, and is not related to the intensity of finger contact between detecting the finger down event and detecting the finger up event. In some embodiments, a tap gesture is detected according to a determination that the length of time between the finger down event and the finger up event is shorter than a predetermined value (e.g., shorter than 0.1, 0.2, 0.3, 0.4, or 0.5 seconds), regardless of whether the intensity of finger contact during the tap meets a given intensity threshold such as a light press or a deep press intensity threshold (greater than a nominal contact detection intensity threshold). Thus, a finger tap gesture can meet a specific input criterion that does not require the characteristic intensity of the contact to meet a given intensity threshold for a particular input criterion to be met. For clarity, finger contact in a tap gesture generally needs to meet a nominal contact detection intensity threshold below which 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 sensing surface, the nominal contact detection intensity threshold is optional and does not correspond to physical contact between the finger or stylus and the touch sensing surface.

[0080] In a similar manner, the same concept is applied to other types of gestures. For example, a swipe gesture, pinch gesture, pinch-out gesture, and / or long-press gesture are optionally detected based on meeting criteria that are either not related to the intensity of the contact included in the gesture or do not require the contact making the gesture to reach an intensity threshold for recognition. For example, a swipe gesture is detected based on the amount of movement of one or more contacts, a pinch gesture is detected based on the movement of two or more contacts towards each other, a pinch-out gesture is detected based on the movement of two or more contacts away from each other, and a long-press gesture is detected based on the duration of contact on the touch-sensitive surface that is less than a threshold amount of movement. Thus, the statement that a particular gesture recognition criterion does not require the intensity of the contact(s) to meet a corresponding intensity threshold for the particular gesture recognition criterion to be met means that it is possible for a particular gesture recognition criterion to be met when the contact(s) in the gesture do not reach the corresponding intensity threshold, and it is also possible for it to be met 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 contact exceeds or falls below its respective intensity threshold during the predetermined time period, and a swipe gesture is detected based on a determination that the movement of the contact is greater than a predetermined magnitude, even if the contact exceeds its respective intensity threshold at the end of the movement of the contact. Even in embodiments where the detection of the gesture is affected by the intensity of the contact making the gesture (e.g., the device detects a long press faster when the intensity of the contact exceeds the intensity threshold, or the device is slower to detect a tap input when the intensity of the contact is higher), as long as the criteria for recognizing the gesture can be met in situations where the contact does not reach a particular intensity threshold (e.g., even if the amount of time required to recognize the gesture changes), the detection of those gestures does not require the contact to reach a particular intensity threshold.

[0081] The contact intensity threshold, the duration threshold, and the movement threshold are combined in various different combinations in order to create heuristics for distinguishing between two or more different gestures that are directed at the same input element or region in some situations, thereby enabling a richer set of user interactions and responses with the same input element. A description that a particular set of gesture recognition criteria does not require the intensity of the contact(s) to meet their respective intensity thresholds in order for that particular gesture recognition criteria to be satisfied does not preclude simultaneously evaluating other intensity-dependent gesture recognition criteria for identifying other gestures that have criteria that are satisfied when the gesture includes contacts having intensities that exceed their respective intensity thresholds. For example, in some situations, a first gesture recognition criteria for a first gesture that does not require the intensity of the contact(s) to meet the corresponding intensity threshold in order for the first gesture recognition criteria to be satisfied is in a competing relationship with a second gesture recognition criteria for a second gesture that depends on the contact(s) reaching the corresponding intensity threshold. In such a competition, the 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 is satisfied first. For example, if the contact reaches the corresponding intensity threshold before the contact moves a predetermined amount of movement, a deep press gesture rather than a swipe gesture is detected. Conversely, if the contact moves a predetermined amount of movement before the contact reaches the corresponding intensity threshold, a swipe gesture rather than a deep press gesture is detected. Even in such situations, the first gesture recognition criteria for the first gesture still does not require the intensity of the contact(s) to meet the corresponding intensity threshold in order 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 having a contact that does not increase to an intensity exceeding the corresponding intensity threshold), the gesture is recognized by the first gesture recognition criteria as a swipe gesture.In this way, certain gesture recognition criteria that do not require the intensity of the contact(s) to meet a corresponding intensity threshold for the satisfaction of the certain gesture recognition criteria are such that, in some situations, they ignore the intensity of the contact with respect to the intensity threshold (e.g., for a tap gesture), and / or, in some situations, they still depend on the intensity of the contact with respect to the intensity threshold in the sense that, if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognizes the input as corresponding to an intensity-dependent gesture before the certain gesture recognition criteria (e.g., for a long press gesture) recognizes a gesture (e.g., a long press gesture that competes with the deep press gesture for recognition) corresponding to the input, the certain gesture recognition criteria (e.g., for a long press gesture) does not function.

[0082] The graphic module 132 includes various known software components for rendering and displaying graphics on a touch-sensitive display system 112 or other display, including components for changing visual effects (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, the graphic module 132 stores data representing the graphics that will be used. Optionally, a corresponding code is assigned to each graphic. The graphic module 132 receives, from an application or the like, as needed, one or more codes specifying the graphics to be displayed, along with coordinate data and other graphic characteristic data, and then generates image data for the screen to be output to the display controller 156.

[0084] The tactile feedback module 133 includes various software components that generate instructions (e.g., instructions used by the tactile 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] The text input module 134 is optionally a component of the graphic 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 that requires 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 location-based calling, to the camera 143 as metadata for photos / videos, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map / navigation widgets).

[0087] The application 136 optionally includes the following modules (or sets of instructions) or subsets or supersets thereof. ● Contacts module 137 (sometimes referred to as an address book or contacts list), ● Phone module 138, ● Video conferencing module 139, ● Email client module 140, ● Instant messaging (IM) module 141, ● Training support module 142, ● Camera module 143 for still and / or video images, ● Image management module 144, ● Browser module 147, ● Calendar module 148, ● The widget module 149 optionally includes 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 a user-created widget 149-6. ● A widget creation module 150 for creating a user-created widget 149-6. ● A search module 151. ● A video and music player module 152 optionally composed of a video player module and a music player module. ● A memo module 153. ● A map module 154, and / or ● An online video module 155.

[0088] Examples of other applications 136 optionally stored in the memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA (registered trademark)-compatible applications, encryption, digital rights management, speech recognition, and speech replication.

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

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

[0091] In cooperation with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch sensing display system 112, the display controller 156, the optical sensor(s) 164, the optical sensor controller 158, the contact module 130, the graphic module 132, the text input module 134, the contact list 137, and the phone module 138, the video conferencing module 139 includes executable instructions to start, conduct, and end a video conference between the user and one or more other participants according to the user's commands.

[0092] In cooperation with the RF circuit 108, the touch sensing display system 112, the display controller 156, the contact module 130, the graphic module 132, and the text input module 134, the email client module 140 includes executable instructions to create, send, receive, and manage emails in response to the user's instructions. In cooperation with the image management module 144, the email client module 140 greatly facilitates the creation and sending of emails with still or video images captured by the camera module 143.

[0093] In cooperation with RF circuit 108, touch sensing display system 112, display controller 156, contact module 130, graphic 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, and sending each instant message (e.g., using the Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for phone-based instant messages, or using XMPP, SIMPLE, Apple Push Notification Service (APNs), or IMPS for Internet-based instant messages), receiving instant messages, and viewing received instant messages. In some embodiments, the instant messages sent and / or received optionally include graphics, photos, audio files, video files, and / or other attached files, such as those supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant message" refers to both phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).

[0094] In cooperation with the RF circuit 108, the touch sensing display system 112, the display controller 156, the contact module 130, the graphic 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 creates a training (e.g., having time, distance, and / or calorie consumption goals), communicates with training sensors (within the sports device and smartwatch), receives training sensor data, calibrates sensors used to monitor the training, selects and plays music for the training, and displays, stores, and transmits training data, including executable instructions.

[0095] In conjunction with the touch sensing display system 112, the display controller 156, the light sensor(s) 164, the light sensor controller 158, the contact module 130, the graphic module 132, and the image management module 144, the camera module 143 captures still images or videos (including video streams), stores them in the memory 102, modifies the characteristics of the still images or videos, and / or deletes still images or videos from the memory 102, including executable instructions.

[0096] In cooperation with the touch sensing display system 112, the display controller 156, the contact module 130, the graphic module 132, the text input module 134, and the camera module 143, the image management module 144 arranges, modifies (e.g., edits) still images and / or video images, or otherwise operates on them, labels, deletes, presents (e.g., in a digital slide show or album), and stores them, including executable instructions.

[0097] Together with the RF circuit 108, touch sensing display system 112, display system controller 156, contact module 130, graphic module 132, and text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with user commands, including searching for, linking to, receiving, and displaying web pages or portions thereof, as well as attached files and other files linked to the web pages.

[0098] Together with the RF circuit 108, touch sensing display system 112, display system controller 156, contact module 130, graphic module 132, text input module 134, email client module 140, and browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying, and storing a calendar and data associated with the calendar (e.g., calendar items, to-do lists, etc.) in accordance with user commands.

[0099] Together with RF circuit 108, touch sensing display system 112, display system controller 156, contact module 130, graphic module 132, text input module 134, and browser module 147, widget module 149 is, optionally, a mini-application (e.g., weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) downloaded and used by a user, or a mini-application created by the user (e.g., user-created widget 149-6). In some embodiments, the widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript (trademark) file. In some embodiments, the widget includes an XML (Extensible Markup Language) file and a JavaScript (trademark) file (e.g., Yahoo! Widget (registered trademark)).

[0100] In conjunction with RF circuit 108, touch sensing display system 112, display system controller 156, contact module 130, graphic module 132, text input module 134, and browser module 147, widget creation module 150 includes executable instructions for creating a widget (e.g., changing a user-specified portion of a web page into a widget).

[0101] In cooperation with the touch sensing display system 112, the display system controller 156, the contact module 130, the graphic module 132, and the text input module 134, the search module 151 includes executable instructions that, in accordance with a user's command, search for text, music, sound, images, video, and / or other files in the memory 102 that match one or more search criteria (e.g., one or more user-specified search phrases).

[0102] In cooperation with the touch sensing display system 112, the display system controller 156, the contact module 130, the graphic module 132, the audio circuit 110, the speaker 111, the RF circuit 108, and the browser module 147, the video and music player module 152 includes 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, and executable instructions to display, present, or otherwise play video (e.g., on the touch sensing display system 112 or on an external display connected wirelessly or via the external port 124). In some embodiments, the 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 sensing display system 112, the display controller 156, the contact module 130, the graphic module 132, and the text input module 134, the memo module 153 includes executable instructions that, in accordance with a user's command, create and manage memos, lists of things to do, and the like.

[0104] In cooperation with the RF circuit 108, touch sensing display system 112, display system controller 156, contact module 130, graphic module 132, text input module 134, GPS module 135, and browser module 147, the map module 154 can be used to receive, display, modify, and store maps and data associated with the maps (e.g., driving directions, data about stores and other points of interest at or near a particular location, and other location-based data) according to user commands.

[0105] In cooperation with the touch sensing display system 112, display system controller 156, contact module 130, graphic module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, the online video module 155 includes executable instructions that enable a user to access, view, receive (e.g., by streaming and / or downloading), play (e.g., on the touch screen 112 or on an external display connected wirelessly or via the external port 124), send an email having a link to a particular online video, and manage in other ways. In some embodiments, instead of the email client module 140, the instant messaging module 141 is used to send a link to a particular online video.

[0106] Each of the specifically identified modules and applications corresponds to a set of executable instructions that perform one or more of the functions described above, as well as the methods described in this application (e.g., methods executed by a computer and other information processing methods described herein). Those modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus, various subsets of those modules may optionally be combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Further, memory 102 optionally stores additional modules and data structures not described above.

[0107] In some embodiments, device 100 is a device in which the operation of a set of default functions in the device is performed only via a touch screen and / or a touch pad. By using the touch screen and / or the touch pad as the main input control device for device 100 to operate, optionally, the number of physical input control devices (push buttons, dials, etc.) on device 100 is reduced.

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

[0109] FIG. 1B is a block diagram showing exemplary 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., within operating system 126) and respective applications 136-1 (e.g., any of the applications 136, 137-155, 380-390 described above).

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

[0111] In some embodiments, application internal state 192 includes additional information such as 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, a state queue enabling the user to return to a previous state or view of application 136-1, and a redo / undo queue of previous actions performed by the user.

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

[0113] In some embodiments, the event monitor 171 transmits requests to the peripheral device interface 118 at predetermined intervals. In response, the peripheral device interface 118 transmits event information. In other embodiments, the peripheral device interface 118 transmits event information only when a significant event (e.g., receiving an input that exceeds a predetermined noise threshold and / or is longer than a predetermined period) exists.

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

[0115] The hit view determination module 172 provides software procedures for determining where within one or more views a sub-event has occurred when the touch-sensitive display system 112 displays two or more views. A view is composed of control devices and other elements that a user can view on the display.

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

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

[0118] The active event recognition unit determination module 173 determines which view(s) within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognition unit determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognition unit determination module 173 determines that all views including the physical location of the sub-event are views actively involved, and thus determines that all views actively involved should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely limited to an area associated with one particular view, the upper-level views within the hierarchy continue to be views actively involved.

[0119] The event dispatcher module 174 dispatches event information to an event recognition unit (e.g., event recognition unit 180). In embodiments including the active event recognition unit determination module 173, the event dispatcher module 174 dispatches event information to the event recognition unit determined by the active event recognition unit determination module 173. In some embodiments, the event dispatcher module 174 stores the event information obtained by each event receiving unit module 182 in an event queue.

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

[0121] In some embodiments, application 136-1 includes a plurality of event processing units 190 and one or more application views 191, each including instructions for processing touch events that occur within respective views of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognition units 180. Typically, each application view 191 includes a plurality of event recognition units 180. In other embodiments, one or more of the event recognition units 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 characteristics. In some embodiments, each event processing unit 190 includes one or more of event data 179 received from data update unit 176, object update unit 177, GUI update unit 178, and / or event sorter 170. Optionally, event processing unit 190 utilizes, or calls, data update unit 176, object update unit 177, or GUI update unit 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event processing units 190. Also, in some embodiments, one or more of data update unit 176, object update unit 177, and GUI update unit 178 are included in respective application views 191.

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

[0123] The event receiving unit 182 receives event information from the event sorter 170. The event information includes sub-events, for example, information about a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information such as the position of the sub-event. When the sub-event relates to the 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 posture of the device).

[0124] The event comparison unit 184 compares event information with the definitions of defined events or sub-events, and based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, the event comparison unit 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a sequence of predefined sub-events) such as, for example, event 1 (187-1) and event 2 (187-2). In some embodiments, the sub-events in event 187 include, for example, the start of a touch, the end of a touch, the movement of a touch, the cancellation of a touch, 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 (start of touch) at a predefined stage on the displayed object, a first lift-off (end of touch) at a predefined stage, a second touch (start of touch) at a predefined stage on the displayed object, and a second lift-off (end of touch) at a predefined stage. In another example, the definition of event 2 (187-2) is a drag on a displayed object. The drag includes, for example, a touch (or contact) at a predefined stage on the displayed object, a movement of the touch across the touch-sensing display system 112, and a lift-off of the touch (end of touch). In some embodiments, an event also includes information regarding one or more associated event processing units 190.

[0125] In some embodiments, the event definition 187 includes the definition of events for each user interface object. In some embodiments, the event comparison unit 184 performs a hit test to determine which user interface object is associated with the sub - event. For example, in an application view where three user interface objects are displayed on the touch - sensitive display system 112, when a touch is detected on the touch - sensitive display system 112, the event comparison unit 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub - event). If each of the displayed objects is associated with a respective event processing unit 190, the event comparison unit uses the result of the hit test to determine which event processing unit 190 should be activated. For example, the event comparison unit 184 selects the event processing unit associated with the sub - event and object that triggered the hit test.

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

[0127] If each event recognition unit 180 determines that a series of sub - events does not match any of the events of the event definition 186, each event recognition unit 180 enters a state of event impossible, event failure, or event end, and then ignores the next sub - event of the touch - based gesture. In this situation, if there are other event recognition units that remain active for the hit view, that event recognition unit continues to track and process the sub - events of the ongoing touch - based gesture.

[0128] In some embodiments, each event recognition unit 180 includes metadata 183 having configurable properties, flags, and / or lists indicating how the event distribution system should actively participate in executing sub-event distribution for the event recognition unit. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists indicating how the event recognition units interact with each other or how they can interact with each other. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists indicating whether sub-events are distributed at various levels in the view hierarchy or program hierarchy.

[0129] In some embodiments, each event recognition unit 180 activates the event processing unit 190 associated with the event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognition unit 180 distributes event information associated with the event to the event processing unit 190. Activating the event processing unit 190 is separate from sending (and deferring sending) sub-events to each hit view. In some embodiments, the event recognition unit 180 sets a flag associated with the recognized event, and the event processing unit 190 associated with the flag catches the flag and executes a predefined process.

[0130] In some embodiments, the event distribution command 188 includes a sub-event distribution command that distributes event information about sub-events without activating the event processing unit. Instead, the sub-event distribution command distributes the event information to the event processing unit associated with a series of sub-events or to the view actively participating in the event. The event processing unit associated with a series of sub-events or the view actively participating in the event receives the event information and executes a predetermined process.

[0131] In some embodiments, the data update unit 176 creates and updates data used in the application 136-1. For example, the data update unit 176 updates a phone number used in the contact module 137 or stores a video file used in the video and music player module 152. In some embodiments, the object update unit 177 creates and updates objects used in the application 136-1. For example, the object update unit 177 creates a new user interface object or updates the position of a user interface object. The GUI update unit 178 updates the GUI. For example, the GUI update unit 178 prepares display information and sends the display information to the graphic module 132 for display on the touch-sensitive display.

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

[0133] The foregoing description regarding event processing of a user's touch on the touch-sensitive display also applies to other forms of user input for operating the multifunctional device 100 using an input device, but it should be understood that not all of them are initiated on the touch screen. For example, movement of a mouse and pressing of a mouse button, movement of a contact such as a tap, drag, or scroll on a touch pad, pen stylus input, movement of the device, spoken commands, detected eye movements, biometric input, and / or any combination thereof, optionally in association with a single or multiple presses or holds of a keyboard, are utilized as input corresponding to sub-events that define events to be optionally recognized.

[0134] FIG. 2 shows a portable multifunctional device 100 having a touch screen (e.g., touch sensing display system 112, FIG. 1A) according to some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In these embodiments, as well as in the embodiments described below, the user can select one or more of the graphics by performing gestures on the graphics using, for example, one or more fingers 202 (not drawn to an exact scale in the figure) or one or more styli 203 (not drawn to an exact scale in the figure). In some embodiments, the selection of one or more graphics is performed when the user interrupts contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, from right to left, upward and / or downward), and / or rolling of a finger in contact with the device 100 (from right to left, from left to right, upward and / or downward). In some implementations or situations, an unexpected contact with a graphic does not select that graphic. For example, if the gesture corresponding to selection is a tap, a swipe gesture that sweeps over an application icon does not optionally select the corresponding application.

[0135] Device 100 optionally also includes one or more physical buttons such as a "home" or menu button 204. As described above, the menu button 204 is optionally used to navigate to any application 136 in a set of applications that are optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key within a GUI displayed on the touch screen display.

[0136] In some embodiments, device 100 includes a touch screen display, a menu button 204 (which may be referred to as a home button 204), a push button 206 for turning the device on / off and locking the device, volume control button(s) 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and holding it down for a predetermined period, to lock the device by pressing the button and releasing it before a predetermined time has elapsed, and / or to unlock the device or initiate an unlock process. In some embodiments, device 100 also accepts verbal input through microphone 113 to activate or deactivate some functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contact on touch sensing display system 112 and / or one or more haptic output generators 167 for generating haptic output to the user of device 100.

[0137] FIG. 3 is a block diagram of an exemplary multifunctional device having a display and a touch sensing surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a child's learning toy), game system, or control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more networks 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 called a chipset) for interconnecting and controlling communications between system components. Device 300 includes an input / output (I / O) interface 330 that typically includes a display 340 which is a touch screen display. I / O interface 330 optionally also includes a keyboard and / or mouse (or other pointing device) 350, a touch pad 355, a tactile output generator 357 for generating tactile outputs on device 300 (similar to the tactile output generator(s) 167 described above with reference to FIG. 1A), and sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch sensing sensors, and / or contact intensity sensors similar to the 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 the CPU(s) 310.In some embodiments, the memory 370 stores programs, modules, and data structures similar to, or subsets of, the programs, modules, and data structures stored in the memory 102 of the portable multifunctional device 100 (FIG. 1A). Further, the memory 370 optionally stores additional programs, modules, and data structures not present in the memory 102 of the portable multifunctional device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a presentation module 382, a word processing module 384, a website creation module 386, a disk authoring module 388, and / or a spreadsheet module 390, while the memory 102 of the portable multifunctional device 100 (FIG. 1A) optionally does not store those modules.

[0138] Each of the elements in FIG. 3 identified above is optionally stored in one or more of the previously mentioned memory devices. Each of the modules identified above corresponds to a set of instructions that perform the functions described above. The modules or programs (i.e., sets of instructions) identified above 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, the memory 370 optionally stores a subset of the modules and data structures identified above. Further, the memory 370 optionally stores additional modules and data structures not described above.

[0139] Now, attention is directed to embodiments of a user interface (``UI'') optionally implemented on the portable multifunctional device 100.

[0140] FIG. 4A shows an exemplary user interface for a menu of applications on a portable multifunctional 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® indicator, ● Battery status indicator, ● Tray 408 having icons for frequently used applications, such as ○ Icon 416 of phone module 138, labeled "Phone", optionally including an indicator 414 of the number of missed calls or voicemail messages, ○ Icon 418 of email client module 140, labeled "Mail", optionally including an indicator 410 of the number of unread emails, ○ Icon 420 of browser module 147, labeled "Browser", and ○ Icon 422 of video and music player module 152, labeled "Music", and ● Icons for other applications, such as ○ Icon 424 of IM module 141, labeled "Message", ○ Icon 426 of calendar module 148, labeled "Calendar", ○ Icon 428 of image management module 144, labeled "Photos", ○ Icon 430 of camera module 143, labeled "Camera", ○ Icon 432 of online video module 155, labeled "Online Video", ○ Icon 434 of stock widget 149-2, labeled "Stock Price", ○ An icon 436 of the map module 154 labeled with "Map", ○ An icon 438 of the weather widget 149-1 labeled with "Weather", ○ An icon 440 of the alarm clock widget 149-4 labeled with "Clock", ○ An icon 442 of the training support module 142 labeled with "Training Support", ○ An icon 444 of the memo module 153 labeled with "Memo", 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] Note that the labels of the icons shown in FIG. 4A are merely examples. For example, other labels may optionally be used for the various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to that application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to that particular application icon.

[0142] FIG. 4B shows an exemplary user interface on a device (e.g., device 300, FIG. 3) having a touch sensing surface 451 (e.g., a tablet or touch pad 355, FIG. 3) separated from a display 450. Many of the following examples are given with reference to inputs on a touch screen display 112 (when the touch sensing surface and the display are combined), but in some embodiments, the device detects inputs on a touch sensing surface separated from the display, as shown in FIG. 4B. In some embodiments, the touch sensing surface (e.g., 451 in FIG. 4B) has a major axis (e.g., 452 in FIG. 4B) corresponding to a major axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). According to those embodiments, the device detects contact (e.g., 460 and 462 in FIG. 4B) with the touch sensing surface 451 at positions (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470) corresponding to respective positions on the display. Thus, when the touch sensing surface is separated from the display, user inputs (e.g., contacts 460 and 462, and their movement) detected by the device on the touch sensing surface (e.g., 451 in FIG. 4B) are used by the device to operate the user interface on the display (e.g., 450 in FIG. 4B) of the multifunctional device. It should be understood that a similar method is optionally used for other user interfaces described herein.

[0143] As used herein, the term "focus selector" refers to an input element that indicates the current part of the user interface with which the user is interacting. In some implementations, including 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., the touchpad 355 in FIG. 3 or the 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, including a touch screen display (e.g., the touch-sensitive display system 112 in FIG. 1A or the touch screen in FIG. 4A) that enables direct interaction with user interface elements on the touch screen display, a contact detected on the touch screen functions as a "focus selector" such that when an input (e.g., a press input by the contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted according to the detected input. In some implementations, the focus is moved from one area of the user interface to another area of the user interface (e.g., by moving the focus from one button to another button using the tab key or arrow keys) without moving the corresponding cursor or the contact on the touch screen display. In these implementations, the focus selector moves according to the movement of the focus between various areas 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 the touch screen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user intends to interact).For example, while a press input is detected on a touch sensing surface (e.g., a touch pad or a touch screen), the position of a focus selector (e.g., a cursor, a contact, or a selection box) over the corresponding button indicates that the user intends to activate that corresponding button (as opposed to other user interface elements shown on the device's display).

[0144] In some embodiments, the device's response to an input detected by the device depends on a criterion based on the contact intensity during the input. For example, in the case of some "light press" inputs, a contact intensity exceeding a first intensity threshold during the input triggers a first response. In some embodiments, the device's response to an input detected by the device depends on a criterion that includes both the contact intensity and a time-based criterion during the input. For example, in the case of some "deep press" inputs, a contact intensity exceeding a second intensity threshold during the input that is greater than the first intensity threshold for light presses triggers a second response only if a delay time has elapsed between satisfying the first intensity threshold and satisfying the second intensity threshold. This delay time is typically shorter than 200 ms (milliseconds) (e.g., 40 ms, 100 ms, or 120 ms depending on the magnitude of the second intensity threshold, and the delay time increases as the second intensity threshold increases). This delay time helps to avoid accidental recognition of deep press inputs. As another example, in the case of some "deep press" inputs, there is a time period of reduced sensitivity that occurs after the time when the first intensity threshold is satisfied. During the time period of reduced sensitivity, the second intensity threshold increases. This temporary increase in the second intensity threshold also helps to avoid accidental deep press inputs. In the case of other deep press inputs, the response to the detection of a deep press input does not depend on a time-based criterion.

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

[0146] For example, FIG. 4C shows a dynamic intensity threshold 480 that varies over time, based in part on the intensity of a 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 predetermined delay time p1 from when the touch input 476 is first detected, and a second component 478 that follows the trace of the intensity of the touch input 476 over time. The initial high intensity threshold of the first component 474 reduces the accidental triggering of a "deep press" response while enabling an immediate "deep press" response if the touch input 476 provides sufficient intensity. The second component 478 reduces the unintended triggering of a "deep press" response due to the gradual intensity variations of the touch input. In some embodiments, when the touch input 476 meets the dynamic intensity threshold 480 (e.g., at point 481 in FIG. 4C), a "deep press" response is triggered. In some embodiments, when the touch input 476 meets the dynamic intensity threshold 480 (e.g., at point 481 in FIG. 4C), a "deep press" response is triggered.

[0147] FIG. 4D shows another dynamic intensity threshold 486 (e.g., intensity threshold I D ). FIG. 4D also shows two other intensity thresholds: a first intensity threshold I H and a second intensity threshold II L . In FIG. 4D, the touch input 484 is below the first intensity threshold I H and the second intensity threshold I Lis satisfied, but no response is provided until the delay time p2 has elapsed at time 482. Also, in FIG. 4D, the dynamic intensity threshold 486 decays over time, and the decay starts at time 488 after the predetermined delay time p1 has elapsed from time 482 (when the response associated with the second intensity threshold I L has been triggered). This type of dynamic intensity threshold reduces spurious triggering of the response associated with the dynamic 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 the first intensity threshold I D .

[0148] FIG. 4E shows yet another dynamic intensity threshold 492 (e.g., intensity threshold I D ). In FIG. 4E, the response associated with the intensity threshold I L is triggered after the delay time p2 has elapsed from when the touch input 490 was first detected. At the same time, the dynamic intensity threshold 492 decays after the predetermined delay time p1 has elapsed from when the touch input 490 was first detected. Thus, without releasing the touch input 490, a decrease in the intensity of the touch input 490 after triggering the response associated with the intensity threshold I L that is followed by an increase in the intensity of the touch input 490 can trigger the response associated with the intensity threshold I L even when the intensity of the touch input 490 falls below another intensity threshold, e.g., intensity threshold I D at (e.g., time 494). User Interface and Related Processes

[0149] Attention is directed to embodiments of a user interface ("UI") and related processes that may be implemented on an electronic device such as a portable multifunctional device 100 or device 300, comprising a display, a touch sensing surface, (optionally) one or more haptic output generators for generating haptic output, and (optionally) one or more sensors for detecting the intensity of contact with the touch sensing surface.

[0150] Figures 5A1-5A29 illustrate exemplary user interfaces for displaying a dock having a plurality of application icons at variable positions along one or more edges of, for example, a touch-sensitive display. For example, according to some embodiments, the user is enabled to call and interact with a dock that is in a location near the 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 purposes of explanation, some embodiments are discussed with reference to operations that are performed on a device having a touch-sensitive display system 112. In such embodiments, the focus selector is optionally any contact of a respective finger or stylus, a representative point corresponding to the contact of the finger or stylus (e.g., the centroid of each contact or a point associated with each contact), or the centroid of two or more contacts detected on the touch-sensitive display system 112. However, similar operations are optionally performed on a device having a display 450 and a separate touch-sensitive surface 451 in response to detecting a contact on the touch-sensitive surface 451 while displaying the user interface shown in the figures on the display 450, together with the focus selector.

[0151] For purposes of explanation, some embodiments are discussed with reference to operations that are performed on a device that does not have a home button, and gestures that meet a predefined criterion are used to cause dismissal of the currently displayed user interface and display of the 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 in the device and is used to cause dismissal of the currently displayed user interface and display of the home screen user interface (e.g., in response to a single press input), and / or to cause display of a multitask user interface (e.g., in response to a double press input).

[0152] The home screen user interface includes a plurality of application icons corresponding to different applications installed on the device. When each of the application icons is activated by a user (e.g., by a tap input), the device launches the corresponding application and displays the user interface of the application (e.g., the default initial user interface or the last displayed user interface) on the display. The dock is a user interface object that includes a subset of the application icons selected from the home screen user interface to provide quick access to a few frequently used applications. The application icons included in the dock are optionally selected by the user (e.g., via a settings user interface) or automatically selected by the device based on various criteria (e.g., usage frequency 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 on a portion of a separate 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 a plurality of recently opened applications (e.g., arranged in order based on the time when the applications were last displayed). When the representation of each recently opened application (e.g., a snapshot of the last displayed user interface of each recently opened application) is selected (e.g., by a tap input), the device redisplay the last displayed user interface of each recently opened application on the screen.

[0153] Figures 5A1 - 5A5 illustrate exemplary embodiments in which an electronic device displays a dock at different positions along an edge of the device depending on the location of a call input (e.g., edge long - press). Figure 5A1 shows an interactive map user interface displayed in full - screen mode. A long - press gesture (e.g., contact 4202 is maintained for at least a threshold amount of time TT at a specific location (e.g., touch - down location) with less than a threshold amount of movement) detected at a position on the left side of the bottom edge of the display (e.g., the bottom edge is defined with respect to the current orientation of the interactive map user interface) causes the display of dock 4204 at a corresponding position along the left side of the bottom edge of the device (e.g., contact 4202 centered downward). Since the contact did not move substantially during the input (e.g., remained substantially stationary), the dock remains displayed after the lift - off of contact 4202 in Figure 5A3. In contrast, as shown in Figures 5A4 - 5A5, a long - press gesture detected at a position on the right side of the bottom edge of the display (e.g., by contact 4206) causes dock 4204 to be displayed at a corresponding position along the right side of the bottom edge of the device (e.g., contact 4206 centered downward). The dock is displayed on the right side of the bottom edge of the display in Figure 5A5, in contrast to the left side of the bottom edge as in Figure 5A2, because the long - press input that calls the dock is positioned on the right side of the bottom edge, thereby enabling the user to interact with the dock at a position that is easily and conveniently accessible to the user (e.g., without the need for the user to move their hand on the device to a pre - set position on the device). In some embodiments, a long - press gesture within an edge region of the touch - screen that calls the dock is required (e.g., the contact is maintained for at least a threshold amount of time TT 1 below a threshold amount of movement). (e.g., the bottom edge is defined with respect to the current orientation of the interactive map user interface) causes the display of dock 4204 at a corresponding position along the left side of the bottom edge of the device (e.g., contact 4202 centered downward). Since the contact did not move substantially during the input (e.g., remained substantially stationary), the dock remains displayed after the lift - off of contact 4202 in Figure 5A3. In contrast, as shown in Figures 5A4 - 5A5, a long - press gesture detected at a position on the right side of the bottom edge of the display (e.g., by contact 4206) causes dock 4204 to be displayed at a corresponding position along the right side of the bottom edge of the device (e.g., contact 4206 centered downward). The dock is displayed on the right side of the bottom edge of the display in Figure 5A5, in contrast to the left side of the bottom edge as in Figure 5A2, because the long - press input that calls the dock is positioned on the right side of the bottom edge, thereby enabling the user to interact with the dock at a position that is easily and conveniently accessible to the user (e.g., without the need for the user to move their hand on the device to a pre - set position on the device). In some embodiments, a long - press gesture within an edge region of the touch - screen that calls the dock is required (e.g., the contact is maintained for at least a threshold amount of time TT 1Rather than being required to be maintained in a fixed position (optionally maintaining an intensity below a first threshold intensity greater than the contact detection intensity threshold), the device requires a light press gesture within the edge region of the touch screen that invokes the dock (e.g., the intensity of the contact requires a first threshold intensity greater than the contact detection intensity threshold and optionally the contact is maintained in a fixed position for at least a threshold amount of time TT 1 without being required to be maintained in a fixed position).

[0154] Figures 5A4 - 5A8 illustrate exemplary embodiments in which a single input (e.g., a multi - part input by a continuously maintained contact 4206) causes a dock to be displayed, and then causes navigation to an application user interface associated with an application icon displayed within the dock. Figure 5A4 shows an interactive map user interface displayed in full - screen display mode. As shown in Figures 5A4 - 5A5, a long - press gesture by contact 4206 at a position on the right side of the bottom edge of the display causes the dock 4204 to be displayed at a corresponding position along the right side of the bottom edge of the device (e.g., contact 4206 centered downward). Movement of contact 4206 over the email application icon 218 within the dock 4204 selects the icon that is displayed larger in Figure 5A6 as a selected result. Lift - off of contact 4206 while the email application icon 218 is selected causes navigation to the email user interface, as shown in Figures 5A7 - 5A8. As shown in Figures 5A7 - 5A8, the display of the email user interface is animated and appears to emerge from the selected email application icon 218 that covers the interactive map user interface. After navigation to the email user interface, in Figures 5A7 - 5A8, the dock disappears for the input that calls and moves the dock to cause a navigation event. If lift - off of contact 4206 is not detected when contact 4206 moves beyond the email application icon 218, the movement of contact 4206 continues to the position corresponding to the phone application icon 216 within the dock, the email application icon is deselected, and the phone application icon is selected. If lift - off of contact 4206 is detected when contact 4206 moves out of the dock 4204, the device optionally aborts displaying the dock while maintaining the display of the interactive map user interface.

[0155] Figures 5A9 - 5A10 illustrate exemplary embodiments where long - press inputs on different edges of the device also cause a dock to be displayed at a location near the input. Figure 5A9 shows an exemplary email user interface. A long - press gesture detected at a location in the lower half of the left edge of the device (e.g., by contact 4208) causes the dock 4204 to be displayed at a corresponding location along the lower half of the left edge of the device (e.g., contact 4206 centered downward) as shown in Figures 5A9 - 5A10. Compared with Figures 5A2 and 5A5, since the display invocation of the long - press input is located on a different edge, the dock is displayed on a different edge of the device in Figure 5A10. Also, since the dock is displayed along a vertical edge rather than a horizontal edge of the device compared with Figures 5A2 and 5A5, it is displayed in a different orientation.

[0156] Figures 5A9 - 5A12 illustrate exemplary embodiments where the display of the dock is canceled by the lift - off of the call - out contact 4208 even though no navigation event occurred as a result of the input. Figure 5A9 shows an exemplary email user interface. A long - press gesture in the lower half of the left edge of the device, including contact 4208 above the MobileFinder email header in Figure 5A9, causes the display of the dock 4204 along the lower half of the left edge of the device, below contact 4206 in Figure 5A10. The dock disappears after the lift - off of the contact in Figure 5A12. This is because the contact moves away from the dock in Figures 5A10 - 5A11, for example, the contact was not positioned over the dock when the lift - off occurred.

[0157] Figures 5A13 - 5A14 illustrate an exemplary embodiment in which a gesture (e.g., a tap or a light press) detected within an edge region of a touch screen does not cause a dock display but instead causes an action within the displayed application user interface because the gesture did not meet the long - press criterion (e.g., lift - off of the contact was detected before the contact was maintained for at least a threshold amount of time without substantial movement). Figure 5A13 shows an exemplary email user interface. A tap gesture or a light press gesture on the lower - half of the left end of the device, including contact 4209 above the MobileFinder email header in Figure 5A13, causes selection / display of the MobileFinder email in Figure 5A14 rather than a dock display as in Figure 5A12. This is because the time threshold (e.g., TT 1 ) required to invoke the system - wide dock display operation (and preempt the corresponding email - application - specific email selection / display operation) was not met before lift - off of the contact.

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

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

[0160] Figures 5A22 - 5A23 show exemplary embodiments where the dock is displayed in its default position when a long-press gesture is located too close to the edge of the display. Figure 5A22 shows an interactive map user interface displayed in full-screen mode. A long-press gesture on the right side of the bottom edge of the display, including contact 4218 in Figure 5A22, causes dock 4204 to be displayed in its default position near the right end of the bottom edge of the display. Although not centered on contact 4218 in Figure 5A23, if all of the dock is centered over contact 4218 (e.g., the right hand portion of the dock extends off the display to the right), not all of the dock will be shown on the display.

[0161] Figures 5A22 - 5A27 illustrate exemplary embodiments in which a single gesture starting from the edge of a display causes the display of an application in split - screen mode. Figure 5A22 shows an interactive map user interface displayed in full - screen mode. A long - press gesture on the right side of the bottom edge of the display, including contact 4218 in Figure 5A22, causes the dock 4204 to be displayed at a default position near the right end of the bottom edge of the display, not at the center of contact 4218 but below it as shown in Figure 5A23. Movement of the contact on the email application icon 218 selects an icon that is displayed larger in Figure 5A24 as a selected result. While the email application icon is selected, upward movement of the contact away from the edge of the display indicates, in Figure 5A25, that the icon is moved out of the dock, is displayed larger as a result of moving out of the dock, and the corresponding application is launched upon lift - off of contact 4218. Further movement of the contact passing through the boundary 4223 in Figure 5A26 (e.g., a boundary that may be invisible or temporarily displayed in response to detecting upward and right - direction movement outside the dock of icon 218) causes the icon to transition to a view of the email user interface that indicates that the email application is launched in split - screen mode upon lift - off of the contact (e.g., displayed in parallel with the interactive map user interface). Lift - off of contact 4218 in Figure 5A27 causes the device to switch from full - screen mode to split - screen mode, display a user interface for the email application on the right - hand portion of the display, and display an interactive map user interface on the left - hand portion of the display. The email application user interface is displayed in split - screen mode because the icon was dragged from the dock before lift - off of the contact, in contrast to Figure 5A8. The email user interface is displayed in full - screen mode in Figures 5A6 - 5A7 because lift - off of the contact occurred while the email icon was selected within the dock.

[0162] Figures 5A28 - 5A29 show an exemplary embodiment where a gesture starting at the edge of the display results in navigation to a transition navigation state rather than a dock display because the contact moves away from the edge of the display before the gesture meets the temporal requirements for a long - press gesture. Figure 5A28 shows an interactive map user interface displayed in full - screen mode. The user interface selection process is activated by the upward movement of contact 5222 from the bottom edge of the display in Figure 5A29 because the contact moves a sufficient amount before meeting the long - press criteria. In contrast, the dock is displayed in Figure 5A23 because the long - press criteria are met before contact 4218 starts a substantial movement. In Figure 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 Figure 5A29, after the user interface selection process is activated, depending on which user interface state is the currently selected target user interface state at the time when the lift - off of the contact is detected, the device selects among multiple possible target user interfaces (e.g., the user interface of a previously displayed application, the application switcher user interface, or the home screen user interface). The target user interface selects and dynamically facilitates navigation to different user interfaces (e.g., the most recently opened application, the home screen user interface, and the 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 objects). In addition, real - time visual feedback is provided to indicate whether the user is navigating while the user is moving the contact on the touch screen. The respective criteria for navigating to different user interfaces are described, for example, with respect to Figure 8.

[0163] In some embodiments, when the currently displayed user interface is in full-screen display mode (e.g., as shown in FIGS. 5A28-5A29), the device follows a first set of criteria for navigating to different user interfaces in full-screen display mode; when the currently displayed user interface is in split-screen display mode, the device navigates to a different user interface in split-screen display mode (e.g., navigate to the most recently opened application user interface, or the application switcher user interface within the secondary portion of the split screen), or follows a second set of criteria for navigating to different user interfaces in 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 the application user interfaces within the split-screen user interface as separate selectable user interfaces, or the 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 with respect to, for example, FIGS. 5B1-5B36 and flowcharts FIGS. 7A-7I.

[0164] FIGS. 5B1-5B36 are diagrams showing exemplary user interfaces for navigating from a user interface displayed in split-screen display mode to different user interfaces, according to some embodiments.

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

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

[0167] The exemplary user interfaces shown in FIGS. 5B1 - 5B36 relate to methods for efficiently navigating between multiple user interfaces in some embodiments, e.g., methods for quickly switching between different applications and system user interfaces in a split - screen display mode on an electronic device. Exemplary user interfaces for user interface selection processing include an application switcher user interface that includes representations of multiple user interfaces for applications (e.g., recently opened applications, currently displayed applications, and optionally a system control panel) associated with an electronic device, which are displayed as a virtual stack of cards (e.g., a "stack"). Each card in the stack represents a user interface for a different application. The cards are also referred to herein as "application views" when corresponding to a user interface for a recently opened application or "control panel views" when corresponding to a user interface for a control panel. User input (e.g., contact, swipe / drag gesture, flick gesture, etc.) detected on a touch screen 112 (e.g., a touch - sensitive surface) is used to display an application dock superimposed on the currently displayed user interface and to 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 that is below the stack of cards.

[0168] While the device displays any interface (e.g., the user interface of an application), a gesture that starts at the bottom of the screen (e.g., within a predefined area of the device near the edge of the display (e.g., an edge area including a predefined portion (e.g., 20 pixels wide) of the display near the bottom edge of the device)) causes a user interface selection process (e.g., to display a transition navigation user interface) and, optionally, based on the speed and direction of the input and, optionally, based on the movement parameters and the characteristics of the currently displayed user interface object (e.g., a card), instructs navigation between multiple user interfaces. 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 the card following the movement of the input). The user, in some embodiments, has the option to use various gestures to (i) navigate to the full-screen home screen, (ii) navigate to the application that was displayed on the screen immediately preceding the user interface that was displayed when the user interface selection process was invoked (e.g., on any part of a split-screen display), (iii) navigate to a split-screen application switcher user interface that enables the user to select from applications 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 enables the user to select from applications previously displayed on the screen (e.g., for display in either full-screen display mode 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 navigation selection will be made when the input is complete, facilitating efficient user navigation among multiple selections. In some embodiments, the visual feedback and user interface response are fluid and reversible. In some embodiments, the user also has the option to use gestures to navigate to the control panel user interface. In other embodiments, different inputs (e.g., starting from different edges of the display) are required to navigate to the control panel user interface. In some embodiments, the user also has the option to display a dock having a plurality of application icons on the displayed user interface.

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

[0170] Figures 5B1 through 5B12 illustrate exemplary split screen user interfaces in which navigation occurs within one portion of a split screen display (e.g., instead of in another portion of the display or instead of within a full display). The transition navigation gesture begins at the bottom edge of that portion of the display (e.g., instead of beginning at the bottom edge of another portion of the display). FIG. 5B1 shows an interactive map user interface displayed in the left portion of a display operating in split screen display mode and an email user interface simultaneously displayed in the right portion of the display. As shown in FIG. 5B1, when an upward swipe gesture begins at the bottom edge of the left portion of the display, the 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 of FIG. 5B2. In contrast, as shown in FIG. 5B10, when an upward swipe gesture begins at the bottom edge of the right portion of the display, the user interface selection process is activated on the right portion of the screen as shown by the transition navigation user interface displayed on the right portion of the display of 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 began (e.g., the email user interface remains displayed on the right portion of the display during navigation to the application switcher user interface and then the web browsing user interface occurs on the left portion of the display in FIGS. 5B2 through 5B9 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 through 5B12).

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

[0172] Figures 5B13 - 5B17 illustrate an exemplary process by which a device navigates from a user interface displayed in 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 the navigation is that the criteria for navigating to the full - screen application switcher user interface are met by the input (e.g., because a transition navigation gesture has moved further from the edge of the display). Figure 5B13 shows an interactive map user interface displayed in the left portion of a display operating in split - screen display mode, and an email user interface simultaneously displayed in the right portion of the display. As shown in Figure 5B13, when an upward swipe gesture starts from the lower end of the left portion of the display, the user - interface selection process is activated on the left portion of the screen as indicated by a transition navigation user interface displayed on the left portion of the display in Figure 5B14. As the contact continues to move away from the bottom edge of the display, the email user interface displayed in the right portion of the display is replaced (e.g., transitions) by a card 4015 representing the email user interface, and in Figure 5B15, the device indicates to the user that it will switch to full - screen display mode upon lift - off of the contact (e.g., unless the user changes the gesture to navigate back to split - screen display mode). Further, if lift - off of the contact is detected at the point shown in Figure 5B15, the application switcher user interface displayed in 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 within the full - screen application switcher user interface is selected by the user, the device displays the user interface corresponding to the selected card in full - screen display mode.In other words, the device transitions from the split screen mode as a result of a navigation gesture by contact 4424 when lift-off of the contact 4424 is detected in the state shown in FIG. 5B15 (e.g., visual feedback indicates that criteria for navigating to the full screen application switcher user interface are met).

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

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

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

[0176] Figures 5B25 - 5B36 illustrate an exemplary split - screen interface where the device navigates a previously - displayed user interface within a card stack in one portion of the display and then activates the full - screen display mode as other previously - displayed user interfaces are made unavailable within the card stack in response to a serial arc - swipe gesture. Figure 5B25 shows an interactive map user interface displayed in the left portion of a display operating in split - screen mode and an email user interface simultaneously displayed in the right portion of the display. As shown in Figure 5B25, when a substantially lateral swipe gesture starts from the bottom edge of the right portion of the display, the user - interface selection process is activated on the right portion of the screen as indicated by the transition navigation user interface displayed on the left - hand portion of the display of Figure 5B23 (for example, in contrast, when an arc - swipe is initiated from the bottom edge of the left portion of the display as shown in Figure 5B23, it is the left - hand portion of the display). The arc - swipe gesture, as shown in Figure 5B27, pushes the email user interface off the display to the right while dragging a web - browsing user interface (for example, the application view 4406 of the web - browsing user interface) onto the right portion of the display (visible, for example, below the interactive map user interface displayed in the right portion of the display). Since the web - browsing user interface is the last user interface navigated from the display, it is the first previously - displayed user interface to be navigated on the right portion of the display. According to some embodiments, since the two portions of the display share a single stack of previously - displayed cards, the web - browsing user interface was previously displayed in the left portion of the display, but it is still the first previously - displayed user interface to be navigated to the right portion of the display.

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

[0178] Figures 5C1 - 5C59 illustrate exemplary user interfaces for navigating between different user interfaces using multi - touch gestures. For example, considering translation as a group of touches and movement of touches relative to each other (e.g., pinch and spread key - cap gestures), dynamic feedback is provided during the gesture to indicate which user interface will be navigated to upon completion of the gesture. Thereby, according to some embodiments, it becomes possible for the user to change the characteristic properties of the gesture upon completion of the gesture, avoiding unintended navigation and / or consideration due to changes in the intended navigation during the gesture.

[0179] The user interfaces in these figures are used to illustrate processes described later, including the processes in FIGS. 11A - 11F. For convenience of explanation, some embodiments are discussed with reference to operations executed on a device having a touch - sensing display system 112. In such embodiments, the focus selector is optionally one of each finger or stylus contact, a representative point corresponding to each finger or stylus contact (e.g., the centroid of each contact or a point associated with each contact), or the centroid of two or more contacts detected on the touch - sensing display system 112. However, similar operations are optionally executed on a device having a display 450 and a separate touch - sensing surface 451 in response to detecting a contact on the touch - sensing surface 451 while displaying the user interface shown in the figure on the display 450, together with the focus selector.

[0180] For purposes 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 a predefined criterion are used to cause dismissal of the currently displayed user interface and display of the 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 in the device and is used to cause dismissal of the currently displayed user interface and display of the home screen user interface, (e.g., in response to a single press input), and / or to cause display of a multitask user interface (e.g., in response to a double press input).

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

[0182] While the device is displaying a user interface (e.g., a user interface for an application such as an application switcher user interface or a system user interface), a gesture that includes at least three contacts (e.g., 3, 4, 5, or more contacts) and that starts anywhere on the screen, and that includes at least a threshold amount of movement within a predetermined period, calls a user interface selection process (e.g., displays a transition navigation user interface), and optionally, based on the speed and direction of the input and optionally based on the movement parameters and characteristics of the currently displayed user interface object (e.g., a card), instructs navigation between multiple user interfaces. 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 to the card as the input moves).The user has the option of using transitions and pinch / depinch gestures to: (i) navigate to the full-screen home screen, (ii) navigate to an application displayed on the screen (e.g., for a user of a user interface displayed when a user interface selection process is invoked, in some embodiments, (i) navigate to the full-screen home screen, (ii) navigate to an application displayed on the screen immediately preceding the user interface displayed when the user interface selection process is invoked (e.g., on any part of a split-screen display), (iii) navigate to a split-screen application switcher user interface that enables the user to select from previously displayed applications 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 enables the user to select from previously displayed applications on the screen (e.g., for display in either full-screen or split-screen display mode), or (v) navigate back to the user interface displayed when the user interface selection process is invoked (e.g., in split-screen display mode). During input, the device provides dynamic visual feedback indicating which navigation selection will be made when the input ends, facilitating efficient user navigation among multiple selections. In some embodiments, the visual feedback and user interface response are fluid and reversible. In some embodiments, the user also has the option of using gestures to navigate to a control panel user interface. In other embodiments, different inputs (e.g., starting from different edges of the display) are required to navigate to the control panel user interface. In some embodiments, the user also has the option of displaying a dock having multiple application launch icons on the displayed user interface.

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

[0184] Figure 5C1 shows an interactive map user interface displayed in full - screen mode. As shown in Figure 5C2, the two - contact swipe gesture including the movement 4504 and 4508 of the contacts 4502 and 4506 from the positions 4502 - a and 4506 - a to the positions 4502 - b and 4506 - b as shown in Figure 5C1 each results in a horizontal translation of the interactive map to the right (e.g., to indicate eastern Oregon). This is because the gesture meets an application - specific translation criterion (e.g., including the translational movement of contacts within a gesture that includes less than three total contacts) rather than a criterion for invoking a user interface selection process (e.g., including the translational movement of contacts in a gesture that includes at least three contacts). At the lift - off of the contacts, as shown in Figure 5C3, the interactive map application user interface remains displayed, which is because the gesture meets an application - specific criterion rather than a system - wide user interface navigation criterion.

[0185] Figure 5C4 shows an interactive map user interface displayed in full-screen mode. As shown in Figure 5C4, two-touch swipe gestures including the upward movement 4664 and 4668 of contacts 4662 and 4666 from positions 4662-a and 4666-a to positions 4662-b and 4666-b each result in a horizontal translation of the interactive map upward (e.g., hiding southern Montana). This is because the gesture meets an application-specific translation criterion (e.g., including the translational movement of contacts within a gesture including less than three total contacts) rather than a criterion for invoking a user interface selection process (e.g., including the translational movement of contacts in a gesture including at least three contacts). At the lift-off of the contacts, as shown in Figure 5C6, the interactive map application user interface remains displayed because the gesture meets an application-specific criterion rather than a system-wide user interface navigation criterion.

[0186] Figure 5C7 shows an interactive map user interface displayed in full-screen mode. As shown in Figure 5C7, two-touch pinch gestures including the 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 each result in a contraction of the interactive map (e.g., showing both eastern Oregon and western Illinois). This is because the gesture meets an application-specific resizing criterion (e.g., including the pinching movement of contacts within a gesture including less than three total contacts) rather than a criterion for invoking a user interface selection process (e.g., including the pinching movement of contacts in a gesture including at least three contacts). At the lift-off of the contacts, as shown in Figure 5C9, the interactive map application user interface remains displayed because the gesture meets an application-specific criterion rather than a system-wide user interface navigation criterion.

[0187] Figures 5C10 - 5C12, 5C13 - 5C16, 5C17 - 5C19, and 5C20 - 5C22 illustrate exemplary embodiments where a swipe gesture that includes at least three contacts (e.g., three, four, or five finger touches) performs 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 set of figures depends on the characteristics of the gesture. The device provides dynamic visual feedback during the gesture to indicate which user interface will be navigated to at the end of the gesture (e.g., lift-off of all contacts).

[0188] Figures 5C10 - 5C12 show a horizontal swipe gesture that includes four contacts, which results in navigation to a previously displayed application user interface. Figure 5C10 shows an interactive map user interface displayed in full-screen mode. A four-contact swipe gesture that includes upward movement 4512, 4516, 4520, and 4524 of contacts 4510, 4514, 4518, and 4522 from positions 4510-a, 4514-a, 4518-a, and 4522-a as shown in Figure 5C10 to positions 4510-b, 4514-b, 4518-b, and 4522-b as shown in Figure 5C11 calls the user interface selection process because the gesture meets the system-wide user interface navigation criteria (e.g., includes translational movement of contacts within a gesture that includes at least three contacts, and after the device first detects a contact, at least a threshold amount of movement occurs within a threshold time (e.g., TT 1 )). It does not meet the application-specific translational criteria (e.g., not within a threshold amount of time after the device first detects a contact (e.g., includes translational movement of contacts in a gesture that includes three or fewer total (e.g., as shown in Figures 5C1 - 5C3) contacts, and the movement threshold amount is not within a threshold amount of time after the device first detects a contact (TT 1) does not occur). The device replaces the display of the interactive map user interface with the display of the 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), starting to slide the right side of the card, and drags the previously displayed display of the email user interface (e.g., a card) 4528 onto the screen from the left as shown in FIG. 5C11. In FIG. 5C12, as shown by the display of the email user interface after the contact is lifted off, cards 4526 and 4528 remain large during the gesture, indicating that the device navigates to the next / previously displayed application at the end of the gesture (e.g., as shown in FIGS. 10A-10B, when the characteristics of the input / application view meet the "next / previous app criterion (100×4) and / or the "vertical swipe for next / previous app" criterion (100×5), the device assigns the next / previous displayed application as the current target state).

[0189] FIGS. 5C13-5C16 show a vertical swipe gesture including four contacts that results in navigation to the home screen user interface. FIG. 5C13 shows the email user interface displayed in full screen display mode. A four-contact swipe gesture including upward movement of contacts 4532, 4536, 4540, and 4544 of contacts 4530, 4534, 4538, and 4542 from positions 4530-a, 4534-a, 4538-a, and 4542-a as shown in FIG. 5C13C to positions 4530-b, 4534-b, 4538-b, and 4542-b as shown in FIG. 5C14 calls the user interface selection process because the gesture meets the system-wide user interface navigation criteria (e.g., including translational movement of contacts within a gesture including at least three contacts, and after the device first detects a contact, within a threshold time (e.g., TT 1) at least a threshold amount of movement occurs). It is an application-specific translation criterion (e.g., not at a threshold amount of time after the device first detects contact (e.g., a total of three or less (e.g., as shown in FIGS. 5C4 to 5C6) including translational movement of contacts in a gesture), and the movement threshold amount is within a threshold amount of time after the device first detects contact (TT 1 ) does not occur). The device replaces the display of the email user interface with an email user interface representation (e.g., a card) 4528 and starts both contracting and translating the card 4528 upward (e.g., following the upward movement of the contact). The previously displayed interactive map user interface representation (e.g., a card) 4526 is also displayed with the same size and vertical translation as the email card 4528, indicating that the device navigates to the application switcher user interface at the end of the gesture. As shown in FIG. 5C15, the contact moves upward to positions 4530-c, 4534-c, 4538-c, and 4542-c, the email card 4528 contracts and continues to move upward, the interactive map card 4526 disappears, and behind the email card 4528, starting to focus, the home screen user interface indicates that the device navigates to the home screen user interface at the end of the gesture (e.g., the reason is that 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" criterion (100×2) and / or the "large resize / translate to home" criterion (100×3) as shown in FIGS. 10A to 10B). FIG. 5C16 shows the display of the home screen user interface after the lift-off of the contact.

[0190] Figures 5C17 to 5C19 show a vertical swipe gesture that includes four contacts, which results in navigation to the application switcher user interface. Figure 5C17 shows an email user interface displayed in full screen mode. A four-contact swipe gesture that includes upward movement of contacts 4548, 4552, 4556, and 4560 from positions 4546-a, 4550-a, 4554-a, and 4558-a as shown in Figure 5C17 to positions 4546-b, 4550-b, 4554-b, and 4558-b as shown in Figure 5C18 calls the user interface selection process because the gesture meets the system-wide user interface navigation criteria (e.g., includes translational movement of contacts within a gesture that includes at least three contacts, and after the device first detects a contact, at least a threshold amount of movement occurs within a threshold time (e.g., TT 1 ))). It is application-specific translational criteria (e.g., not a threshold amount of time after the device first detects a contact (e.g., includes translational movement of contacts in a gesture that includes three or fewer total contacts, and the movement threshold amount is within a threshold amount of time after the device first detects a contact (TT 1) does not occur). The device replaces the display of the email user interface with a representation of the email user interface (e.g., a card) 4528 and begins both shrinking and translating the card 4528 upward (e.g., in accordance with upward movement of the contact). The previously displayed representation of the interactive map user interface (e.g., a card) 4526 is also displayed with a size and vertical movement similar to that of the email card 4528, as shown in FIG. 5C19 in the display of the application switcher user interface after lift-off of the contact, indicating that the device navigates to the application switcher user interface at the end of the gesture (e.g., when the input / application view characteristics meet the "pause for application switcher" criterion (100×6) and / or the "move to short, slow application switcher" criterion (100×8), the device assigns the application switcher as the current target state as shown in FIGS. 10A - 10B). Since the gesture meets the application switcher navigation criterion rather than the home screen navigation criterion, the device navigates to the application switcher user interface in FIG. 5C19 rather than the home screen user interface (e.g., navigated within FIGS. 5C13 - 5C16). The upward movement of the contact meets a second vertical translation and / or a second vertical speed threshold corresponding to navigation to the application switcher user interface).

[0191] Figures 5C20 to 5C22 show a horizontal swipe gesture including four contacts, which results in navigation back to the same application user interface. Figure 5C20 shows an interactive map user interface displayed in full screen display mode. From positions 4562-a, 4566-a, 4570-a, and 4574-a as shown in Figure 5C20 to positions 4562-b, 4566-b, 4570-b, and 4574-b as shown in Figure 5C21, the four-contact swipe gesture including upward movements 4564, 4568, 4572, and 4576 of contacts 4562, 4566, 4570, 4574 calls the user interface selection process because the gesture meets the system-wide user interface navigation criteria (e.g., including translational movement of contacts within a gesture including at least three contacts, and after the device first detects a contact, at least a threshold amount of movement occurs within a threshold time (e.g., TT 1 ))). It is an application-specific translational criterion (e.g., not a threshold amount of time after the device first detects a contact (e.g., including translational movement of contacts in a gesture including three or fewer total contacts (e.g., as shown in Figures 5C1 to 5C3)), and the movement threshold amount is within a threshold amount of time after the device first detects a contact (TT 1) does not occur). The device replaces the display of the interactive map user interface with the display of the interactive map user interface (e.g., a card) 4526 and starts sliding the card from the right side of the screen (e.g., following the movement of the contact to the right). The right side of the card starts to slide, and as shown in FIG. 5C21, the previously displayed display of the email user interface (e.g., a card) 4528 is dragged onto the screen from the left. However, cards 4526 and 4528 remain large during the gesture, but the card slides quite far to the right, indicating that the device navigates to the interactive map usage interface at the end of the gesture (e.g., as shown in FIGS. 10A - 10B, the device assigns the current application to the current target state when the characteristics of the input / application view meet the "resize / translation cancel" criterion (100×7), so in FIG. 5C22, it is shown by the display of the interactive map usage interface after the lift-off of the contact).

[0192] FIGS. 5C23 - 5C26 show exemplary embodiments in which a swipe gesture including at least four contacts (e.g., four or five finger touches) performs an application-specific operation rather than a system-wide user interface selection (e.g., UI navigation) operation when a threshold amount of movement does not occur within a threshold amount of time. FIG. 5C23 shows an interactive map user interface displayed in full-screen display mode. As shown in FIG. 5C24, four contact inputs including contacts 4578, 4582, 4586, and 4590 are detected. However, the movement of the contacts, as shown in FIG. 5C24, after the first detection of the contacts, within a threshold amount of time (e.g., TT 1It is not performed until ) elapses. From positions 4578-a, 4582-a, 4586-a, and 4590-a as shown in FIG. 5C24 to positions 4578-b, 4582-b, 4586-b, and 4590-b as shown in FIG. 5C25, the rightward movement 4580, 4584, 4588, and 4592 of contacts 4578, 4582, 4586, and 4590 results in a rightward horizontal translation of the interactive map (e.g., indicating eastern Oregon), and is not, for example, a criterion for invoking a user interface selection process (e.g., after the device first detects a contact (e.g., as shown in FIGS. 5C10-5C12)). Because after the device first detects a contact (e.g., as shown in FIGS. 5C10-5C12), it does not meet the criterion for invoking a user interface selection process (e.g., including movement exceeding a threshold amount within threshold time TT 1 ), but rather meets application-specific translation criteria (including being less than the threshold of movement within the time threshold amount (TT 1 ) after the device first detects a contact. At the lift-off of the contact, as shown in FIG. 5C26, the interactive map application user interface remains displayed, because the gesture meets application-specific criteria rather than system-wide user interface navigation criteria.

[0193] FIGS. 5C27-5C29, 5C30-5C32, 5C33-5C36, and 5C37-5C42 show exemplary 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) 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 and, in some embodiments, includes translational movement instead of and / or in addition to the pinch / pinch action. The device provides dynamic visual feedback during the gesture to indicate which user interface will be navigated at the end of the gesture (e.g., lift-off of all contacts).

[0194] Figures 5C27 to 5C29 show a pinch gesture including five contacts that results in navigation to the home screen user interface. Figure 5C27 shows an interactive map user interface displayed in full screen display mode. From positions 4602-a, 4606-a, 4610-a, 4614-a, and 4618-a as shown in Figure 5C27 to positions 4602-b, 4606-b, 4610-b, 4614-b, 4618-b as shown in Figure 5C28, the five-contact pinch gesture including the mutual movement 4604, 4608, 4612, 4616, and 4620 of contacts 4602, 4606, 4610, 4614, and 4618 calls the user interface selection process because the gesture meets the user interface navigation criteria of the entire system (e.g., including the pinch movement of contacts within a gesture including at least three contacts, after the device first detects a contact, within a threshold time (e.g., TT 1 ) at least a threshold amount of movement occurs). It is application-specific resize criteria (e.g., not within a threshold amount of time after the device first detects a contact (e.g., including the pinch / depinch movement of contacts in a gesture including a total of three or less contacts (e.g., as shown in Figures 5C7 to 5C9)), the movement threshold amount is within a threshold amount of time after the device first detects a contact (TT 1) does not occur). The device replaces the display of the interactive map user interface with the representation (e.g., card) 4526 of the interactive map user interface and begins to shrink and translate the card 4526 towards the position between each of the contacts (e.g., in accordance with the pinch movement 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 will navigate to the home screen user interface at the end of the gesture (e.g., the reason is that the device, as shown in FIGS. 10A-10B, assigns the home screen as the current target state when the characteristics of the input / application view meet the "fast resize / translate to home" criterion (100×2) and / or the "large resize / translate to home" criterion (100×3)). FIG. 5C29 shows the display of the home screen user interface after the lift-off of the contact.

[0195] FIGS. 5C30-5C32 show a pinch gesture including five contacts, which results in navigation to the application switcher user interface. FIG. 5C30 shows the interactive map user interface displayed in full-screen display mode. A five-contact pinch gesture including the movements 4644, 4648, 4652, 4656, and 4660 of the contacts 4642, 4646, 4650, 4654, and 4658 from the positions 4642-a, 4646-a, 4650-a, 4654-a, and 4658-a as shown in FIG. 5C30 to the positions 4642-b, 4646-b, 4650-b, 4654-b, 4658-b as shown in FIG. 5C31 calls the user interface selection process because the gesture meets the system-wide user interface navigation criteria (e.g., including the pinch movement of the contacts within a gesture including at least three contacts, and after the device first detects the contact, within a threshold time (e.g., TT 1) at least a threshold amount of movement occurs). It is an application-specific resizing criterion (e.g., not at a threshold amount of time after the device first detects contact (e.g., a total of three or less (e.g., as shown in FIGS. 5C7 - 5C9)) including pinch / depinch movement of contacts in a gesture, and the movement threshold amount occurs within a threshold amount of time after the device first detects contact (TT 1 ) does not occur). The device replaces the display of the interactive map user interface with an interactive map user interface representation (e.g., a card) 4526 and begins to shrink and translate the interactive map card 4526 towards the position between each of the contacts (e.g., according to the pinch movement of the contacts). The previously displayed electronic mail user interface representation (e.g., a card) 4528 is also displayed in the same 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 contact, indicating that the device navigates to the application switcher user interface at the end of the gesture (e.g., when the input / application view characteristics meet the "pause for application switcher" criterion (100×6) and / or the "move to short, slow application switcher" criterion (100×8), the device assigns the application switcher as the current target state, as shown in FIGS. 10A - 10B). Since the gesture meets the application switcher navigation criterion instead of the home screen navigation criterion, in FIG. 5C32 instead of the home screen user interface, the device navigates to the application switcher user interface (e.g., navigated within FIGS. 5C27 - 5C29) (e.g., upward movement by pinch of the contact corresponds to a first pinch translation and / or meets a first vertical speed threshold for navigation to the application switcher user interface).

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

[0197] Figures 5C33-5C36 illustrate an exemplary 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 immediately before the end of the gesture results in navigation to a previously displayed application user interface. Figures 5C33-5C36 also illustrate an exemplary embodiment in which user interface navigation continues after lift-off of some, but not all, contacts after the user interface selection process has been invoked. As shown in Figure 5C33, a five-contact pinch operation 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 to positions 4622-b, 4626-b, 4630-b, 4634-b, and 4638-b as shown in Figure 5C34 triggers a user interface selection process. The device begins to replace the display of the interactive map user interface with a representation (e.g., a card) 4526 of the interactive map user interface and shrink and translate the interactive map card 4526 toward the position between each of the contacts (e.g., in accordance with the pinch movement of the contacts). A representation (e.g., a card) 4528 of the previously displayed email user interface is also displayed with a size and vertical movement similar to that of the interactive map card 4526, indicating that the device navigates to the application switcher user interface at the end of the gesture (e.g., as shown in Figures 5C30-5C32, because when the input / application view characteristics meet the "pause for application switcher" criterion (100x6) and / or the "move to short, slow application switcher" criterion (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 contact in FIG. 5C36, the horizontal translation of the remaining contacts 4630, 4634, and 4638 from the positions 4630-b, 4634-b, and 4638-b shown in FIG. 5C34 to the positions 4630-c, 4634-c, and 4638-c as shown in FIG. 5C35 pushes the interactive map card 4526 to the right from the display, while at the same time dragging the email card 4528 from the left onto the display, which indicates that the device navigates to the next / previously displayed application at the end of the gesture (e.g., as shown in FIGS. 10A - 10B, when the properties of the input / application view meet the criteria of the next / previous app "criterion (100×4) and / or the vertical swipe criterion for the next / previous app (100×5)", the device assigns the next / previously displayed application as the current target state).

[0198] Figures 5C37 to 5C42 illustrate an exemplary embodiment in which a navigation gesture including a pinch gesture is reversed by a de-pinch gesture. Five contact pinch movements, including movements 4672, 4676, 4680, 4684, and 4688 of contacts 4670, 4674, 4678, 4682, and 4686 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, which are towards each other, call a user interface selection process. The device replaces the display of the interactive map user interface with a representation (e.g., a card) 4526 of the interactive map user interface and begins to contract and translate the interactive map card 4526 towards the position between each of the contacts (e.g., in accordance with the pinch movement of the contacts). A previously displayed representation (e.g., a 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, indicating that the device navigates to the application switcher user interface at the end of the gesture (e.g., when the characteristics of the input / application view meet the "pause for application switcher" criterion (100×6) and / or the "movement to short, slow application switcher" criterion (100×8), the device assigns the application switcher as the current target state as shown in FIGS. 10A to 10B).As shown in FIG. 5C39, as the contacts continue to pinch towards each other to positions 4670-c, 4674-c, 4678-c, 4682-c, and 4686-c, the interactive map card 4526 shrinks and continues to move to 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 will navigate to the home screen at the end of the gesture (e.g., the reason is that, as shown in FIGS. 10A - 10B, the device assigns the home screen as the current target state when the characteristics of the input / application view meet the "quick resize / translate to home" criterion (100×2) and / or the "large resize / translate to home" criterion (100×3)). As shown in FIG. 5C40, the reversal of the pinch operation of the contacts to positions 4670-d, 4674-d, 4678-d, 4682-d, and 4686-d (e.g., the de-pinch operation) expands the interactive map card 4526, reappears the email card 4538, and indicates that the device will navigate to the application switcher user interface at the end of the gesture (e.g., when the characteristics of the input / application view meet the "pause for application switcher" criterion (100×6) and / or the "move to short, slow application switcher" criterion (100×8), the device assigns the application switcher as the current target state, as shown in FIGS. 10A - 10B).In Figure 5C42, as shown by the display of the email user interface after contact lift-off, the horizontal translation of the right contact after the de-pinch operation to positions 4670-e, 4674-e, 4678-e, 4682-e, and 4686-e as shown in Figure 5C41 pushes the interactive map card 4526 to the right from the display, while at the same time further dragging the email card 4528 from the left onto the display, which indicates that the device navigates to the next / previously displayed application at the end of the gesture (e.g., as shown in Figures 10A - 10B, when the properties of the input / application view satisfy the next / previous app criteria (100×4) and / or the vertical swipe criteria for the next / previous app (100×5), the device assigns the next / previous displayed application as the current target state).

[0199] Figures 5C43 to 5C47 illustrate exemplary embodiments that contribute to gestures in which both an upward swipe operation and a pinch operation result in navigation to a home screen user interface. Figure 5C43 shows an interactive map user interface displayed in full screen display mode. From positions 4690-a, 4694-a, 4698-a, and 4702-a as shown in Figure 5C43 to positions 4690-b, 4694-b, 4698-b, and 4702-b as shown in Figure 5C44, four contact swipes including movements 4692, 4696, 4700, and 4704 of contacts 4690, 4694, 4698, and 4702 towards the right call a user interface selection process. 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 rightward contact), and drags the display (e.g., a card) 4528 of the previously displayed email user interface onto the screen from the left as shown in Figure 5C43. In Figure 5C44, cards 4526 and 4528 remain large, indicating that the device navigates to the next / previously displayed application at the end of the gesture (e.g., as shown in Figures 10A to 10B, when the properties of the input / application view meet the "next / previous app criteria (100 x 4) and / or the "vertical swipe for next / previous app" criteria (100 x 5), the device assigns the next / previous displayed application as the current target state).As shown in FIG. 5C45, upward movement of the contacts to positions 4690-c, 4694-c, 4698-c, and 4702-c contracts the card, moves it upward (e.g., in accordance with the upward movement of the contacts), and indicates that the device navigates 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” criterion (100×6) and / or the “move to short, slow application switcher” criterion (100×8), the device assigns the application switcher as the current target state, as shown in FIGS. 10A-10B). As shown in FIG. 5C46, when the contacts pinch together to positions 4690-d, 4694-d, 4698-d, and 4702-d, the interactive map card 4526 continues to contract and begins to move downward toward the palm gesture of the virtual hand, the email card 4528 disappears, the home screen user interface begins to focus behind the interactive map card 4526, and indicates 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 characteristics of the input / application view meet the “quick resize / translate to home” criterion (100×2) and / or the “large resize / translate to home” criterion (100×3), as shown in FIGS. 10A-10B). FIG. 5C47 shows the display of the home screen user interface after lift-off of the contacts. Despite the downward movement of the card in response to the pinch gesture in FIG. 5C46 (e.g., in contrast to the upward movement in response to the upward swipe in FIGS. 5C13-5C16), the predicted navigation state is the home screen user interface. This is because both upward movement of the contacts and pinching are associated with such navigation (e.g., both upward swiping and pinching contribute to an increase in the “simulated Y-position” and / or contraction of the card, and any one or both of these correspond to navigation to the application switcher user interface).

[0200] Figures 5C48 - 5C50 illustrate exemplary embodiments where an upward swipe including at least three contacts (e.g., 3, 4, or 5 finger touches) on a home screen user interface that is not the default home screen user interface (e.g., the second page or subsequent pages of application launch icons) causes navigation to the default home screen user interface. Figure 5C48 shows a second home screen user interface including application launch icons for a plurality of applications (e.g., clock, app store, voice memo, calculator, and memo). A four - contact swipe gesture including the movement 4712, 4716, 4720, and 4724 of the upward contacts 4710, 4714, 4718, and 4722 from positions 4710 - a, 4714 - a, 4718 - a, and 4722 - a to positions 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 5C49 and as shown in Figure 5C50. 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 including the movement of contacts 4710, 4714, 4718, and 4722 towards each other causes the device to navigate to the primary (e.g., default) home screen user interface.

[0201] Figures 5C51 - 5C54 illustrate exemplary embodiments where an upward swipe gesture including at least three contacts (e.g., three, four, or five finger touches) on an application switcher user interface causes navigation to the home screen user interface. A four - contact swipe gesture including the 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 Figure 5C52 to positions 4726 - b, 4730 - b, 4734 - b, and 4738 - b as shown in Figure 5C51 causes the device to navigate to the home screen user interface as shown in Figure 5C54. In some embodiments, an animation is displayed to slide the application switcher user interface upward with the movement of the contacts, revealing 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 the initial portion of the multi - contact upward swipe gesture (e.g., as shown in Figure 5C52), and when the criteria for navigating to the home screen are met (e.g., the same criteria as described for navigating from the application user interface to the home screen user interface as shown in Figures 9A - 9C and 10A - 10D), the device displays only the representation of the recently used application as visual feedback indicating the current target state of the user interface navigation before lift - off of the contacts (e.g., as shown in Figure 5C23), and displays the home screen user interface after the gesture ends (e.g., as shown in Figure 5C54).

[0202] Figures 5C55 - 5C59 illustrate exemplary embodiments where the user interface for the user interface selection process is dynamic and reversible. Five contact pinch movements, including the movements 4744, 4748, 4752, 4756, and 4760 of contacts 4742, 4746, 4750, 4754, and 4758 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, call the user interface selection process. The device begins to replace the display of the interactive map user interface with a representation (e.g., a card) 4526 of the interactive map user interface and shrink and translate the interactive map card 4526 towards the position between each of the contacts (e.g., according to the pinch movement of the contacts). The previously displayed representation (e.g., a card) 4528 of the email user interface is also displayed with a size and vertical movement similar to the interactive map card 4526, indicating that the device navigates to the application switcher user interface at the end of the gesture (e.g., when the characteristics of the input / application view meet the "pause for application switcher" criterion (100×6) and / or the "move to short, slow application switcher" criterion (100×8), the device assigns the application switcher as the current target state as shown in Figures 10A - 10B). As shown in Figure 5C57, the translational movement of the contacts in a diagonal upward direction (e.g., a movement including horizontal and vertical components) to positions 4742 - c, 4746 - c, 4750 - c, 4754 - c, and 4758 - c shrinks the card and moves it upward and to the right (e.g., according to the vertical component of the contact movement).As shown in FIG. 5C58, the downward movement of the contacts to positions 4742-d, 4746-d, 4750-d, 4754-d, and 4758-d increases the size of the interactive map card 4526, pushes the email card 4528 to the left from the display, and, as shown by the display of the interactive map user interface after the contact lift-off in FIG. 5C59, indicates that the device navigates to the interactive map user interface at the end of the gesture (e.g., the device assigns the current application as the current target state when the characteristics of the input / application view meet the "resize / translation cancel" criterion (100×7) as shown in FIGS. 10A-10B).

[0203] FIGS. 5D1 - 5D64 show exemplary user interfaces for navigating from an application user interface displayed in a split screen display mode to different user interfaces external to the application, according to some embodiments.

[0204] In FIGS. 5D1 to 5D14, two applications (e.g., a map application and a game application) are displayed in parallel on the touch screen 112 in a split screen display mode. Neither of the two applications requires edge protection (e.g., implemented based on an extended edge swipe gesture criterion) in their current state. In some embodiments, edge protection is implemented with a gesture repetition requirement (e.g., two consecutive standard edge swipe gestures required) and / or an extended position requirement (e.g., one or both edge swipes start on a home affordance) in addition to a standard edge swipe gesture criterion (e.g., the gesture starts from any position along the bottom edge). When an application does not require edge protection, this is associated with the standard edge swipe gesture criterion, and an upward edge swipe gesture that meets the standard edge swipe gesture criterion causes the execution of system operations, which includes, for example, navigation from the application user interface displayed in split screen mode to the user interface outside the application, including the system user interface (e.g., home screen user interface or application switcher user interface) or the user interface of another application (e.g., the contact moves up and sideways, or starts on the edge and moves sideways without an initial upward movement).

[0205] As shown in FIG. 5D1 (and also in FIG. 5D9), on the touch screen 112, the user interface 4806-1 of the map application is displayed alongside the user interface 4808-1 of the game application. The user interfaces 4801-1 and 4808-1 are separated by a divider 4804, and the divider 4804 can be dragged in a direction along the bottom edge of the 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 side-by-side applications). In some embodiments, the relative sizes of the side-by-side 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 the user interfaces 4806-1 and 4808-1 is in an edge protection state (e.g., the extended edge swipe gesture criteria are not active for the applications on either side of the split screen). System user interface elements (e.g., the home affordance 4802-1) are displayed in a first appearance state (e.g., opaque, or standard visibility), indicating that the application(s) below the system user interface element are associated with standard edge swipe gesture criteria, as opposed to the extended edge swipe gesture criteria. In some embodiments, the appearance of the home affordance 4802-1 is generated according to a portion of the content below the 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, since the user interface 4806-1 of the map application is not in an edge protection state (e.g., the extended edge swipe gesture criteria are not active), and when an upward swipe by contact 4828 is detected on the side of the screen displaying the map application (e.g., at the start position of the lower or bottom edge of screen 112 and optionally outside the area occupied by the home affordance 4801-1), the upward swipe gesture by contact 4828 meets the standard edge swipe gesture criteria, the system navigation process is initiated, and the transition user interface 4822-1 replaces the split screen user interface displayed on the screen at the start of the gesture. As shown in FIG. 5D2, at the start of the system navigation process, the 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 converted into a card 4818 within the transition user interface 4822-1 (e.g., a snapshot representation of the split screen user interface at the time when contact 4828 is detected). The dock 4826 includes a subset of application icons (e.g., icons of frequently used apps, apps selected by the user, or recommended apps) selected from the application icons shown on the home screen user interface 4814. The dock 4826 can overlay a portion (less than all) of the currently displayed user interface and be displayed in multiple contexts (e.g., overlaid on the home screen user interface, application user interface, transition user interface, or application switcher user interface).

[0208] In FIGS. 5D1 to 5D8, when contact 4828 moves upward on touch screen 112, card 4818 is displayed next to another card 4820 representing a previously used application within the set of most recently used applications, as shown in FIGS. 5D2 and 5D3. The representations of user interfaces 4818 and 4820 are continuously and dynamically dragged and resized following the movement of contact 4828 on the touch screen (e.g., as shown in FIGS. 5D2 - 5D3). As contact 4828 continues to move upward, card 4820 moves off the display, leaving card 4818 as a single card within transition user interface 4822 - 2, as shown in FIG. 5D5. If contact 4828 moves laterally after first moving upward within an arc swipe gesture (e.g., within the side swipe for the 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, the final navigation state of the user interface is determined by contact 4828 according to various navigation criteria and based on one or more characteristic parameters of the gesture. 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., the split - screen user interface representation 4824 shown in the grid or stack of presentation of most recently used applications (e.g., arranged based on the recency of the 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 the applications installed on the device displayed within a pre - arranged grid, regardless of whether the application was last used).As shown in FIG. 5D8, if the lift-off of contact 4828 is detected (e.g., after an arc swipe (in the transition user interface 4822-3 as 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 different user interfaces are described with respect to the processes shown in FIGS. 9A-9C and FIGS. 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 starts outside the reaction area indicated by the home affordance 4802-1), the gesture is passed to the underlying application and used as an input for an operation within the application. For example, a tap input by contact within an area within the user interface 4806-1 (e.g., a touch input that does not include movement exceeding a threshold amount, and thus does not meet the edge swipe gesture criteria) causes a position within the map corresponding to the position of the contact to be selected. A swipe input entered by contact within an area within the user interface 4806-1 (e.g., a swipe that does not start from a predefined edge of the device such as the edge where the home affordance is displayed, and thus does not meet the edge swipe gesture criteria) scrolls the map shown within the user interface of the map application.

[0210] In FIGS. 5D1 to 5D8, the standard edge swipe gesture criteria do not require that the contact start 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 on the side of the map application (e.g., above or otherwise on home affordance 4802-1) can result in system-level navigation to the user interface outside the currently displayed application (e.g., a map application displayed in split-screen mode). Additionally, the navigation applies to the entire split-screen user interface, including the user interfaces of both applications displayed simultaneously.

[0211] FIGS. 5D9 to 5D14 show that both applications (e.g., a map application and a game application) displayed in parallel on the split-screen user interface are associated with the standard edge swipe gesture criteria (e.g., non-edge protected state), and that the home affordance 4802-1 that 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 by contact 4830 detected on the side of the game application on screen 112 that meets the standard edge swipe gesture criteria (e.g., detected outside home affordance 4802-1) causes navigation from the currently displayed split-screen user interface to the application switcher user interface 4812 (e.g., as shown in FIGS. 5D9 to 5D12), or to the home screen user interface 4814 (e.g., as shown in FIGS. 5D9 to 5D10 and FIGS. 5D13 to 5D14), according to criteria for navigating to different user interfaces described with respect to the processes shown in FIGS. 9A to 9C and 10A to 10D. The navigation processes shown in 5D9 to 5D14 are similar to those in FIGS. 5D1 to 5D6 and are not repeated herein for brevity.

[0212] In FIGS. 5D15 to 5D49, two applications (for example, a map application and a game application) are displayed in parallel on the touch screen 112 in a split screen display mode. In contrast to the scenarios shown in FIGS. 5D1 to 5D14 (for example, neither of the two applications requires edge protection), one of the two applications shown in FIGS. 5D15 to 5D49 is currently associated with an extended edge swipe gesture criterion and is in an edge protection state. According to some embodiments, the home affordance 4802-2 that overlaps at least a portion of both applications on the split screen is displayed in a second appearance state (for example, as shown in FIGS. 5D15, 25, ~ FIGS. 5D32, 5D37, 5D44, 5D47, translucent or with reduced visibility) compared to the affordance in the first appearance state (for example, as shown in FIGS. 5D1 and 5D9). It indicates that at least one of the two applications under the home affordance is currently associated with an extended edge swipe gesture criterion.

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

[0214] In an exemplary scenario as shown in FIG. 5D15 through FIG. 5D24, such as that shown in FIG. 5D15, the map application is in an induced navigation mode that requires edge protection. In the induced navigation mode, since accidental triggers of system-level navigation during the use of the induced navigation mode (e.g., while driving) are disadvantageous, user interaction with the map user interface 4806-2 is given priority over system-level navigation. Contact 4832 is detected at a position on the home affordance 4802-2 on the side of the map application (e.g., on the user interface 4806-2). 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 requirement 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 requirement of the extended edge swipe gesture criteria) temporarily disables edge protection, as indicated by a change in the appearance state of the home affordance 4802 from the second appearance state (e.g., as shown in FIG. 5D15) to the first appearance state (e.g., as shown in FIG. 5D16). In some embodiments, since the upward movement of contact 4832 does not meet the extended edge swipe gesture criteria associated with the map application, it is optionally provided as an input to the map application. In this example, an upward movement of contact 4832 drags the menu displayed at the start position of contact 4832 upward within the user interface 4806-2. No system-level operations are performed to replace or modify the split-screen user interface as a whole. The transition user interface is not displayed as a result of the standard edge swipe gesture by contact 4832.

[0215] In FIGS. 5D17-5D24, a second upward edge swipe gesture by contact 4832 is detected (e.g., at a starting position outside the home affordance 4802-1 in the first appearance state). The second upward edge swipe gesture by contact 4834 meets the gesture criteria of 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 4834 is detected within a threshold amount of time after the gesture by contact 4836). The upward edge swipe gesture by contact 4832 causes the execution of system operations according to various navigation criteria (e.g., the criteria described with respect to the processes shown in FIGS. 9A-9C and FIGS. 10A-10D), for example, from an application user interface (e.g., user interfaces 4806-2 and 4808-1) (e.g., as shown in FIG. 5D17) displayed in split screen mode to a user interface outside the application, such as a system user interface (e.g., first transition user interface 4822-1 (e.g., FIG. 5D18) or 4822-2 (e.g., FIG. 5D20), 4822-3 (e.g., FIG. 5D23), and finally the home screen user interface (e.g., in FIG. 5D21) or the application switcher user interface (e.g., in FIG. 5D19), or the user interface of another application (e.g., in FIG. 5D24)). The navigation process shown in 5D15-5D24 is similar to that of FIGS. 5D1-5D8 and is not repeated herein for brevity.

[0216] In the example shown in FIGS. 5D25 - 5D31, the application (e.g., a map application) displayed on the left side of the split screen is currently associated with standard edge - swipe gesture criteria, and the application (e.g., a game application) displayed on the right side of the split screen is currently associated with extended edge - swipe gesture criteria. In FIG. 5D25, the game application is in a game - playing mode (e.g., a piano - keyboard playing mode) that requires edge protection. In the game - playing mode, user interaction with the game user interface 4808 - 2 is given priority over system - level navigation because accidental triggers of system - level navigation (e.g., during an active game) are inconvenient. Contact 4838 is detected at a position on the home affordance 4802 - 2 on the game - application side (e.g., on the user interface 4808 - 2). The 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 requirement 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 requirement of the extended edge - swipe gesture criteria) temporarily disables edge protection, as indicated by a change in the appearance state of the home affordance 4802 from the second appearance state (e.g., as shown in FIG. 5D25) to the first appearance state (e.g., as shown in FIG. 5D26). In some embodiments, since the upward movement of contact 4838 does not meet the extended edge - swipe gesture criteria associated with the game application, it is optionally provided as an input to the game application. In this example, the upward movement of contact 4838 causes the display of a piano key (key "C") at the starting position of contact 4838 being pressed within the user interface 4808 - 2. No system - level operations are performed to replace or modify the split - screen user interface as a whole.As a result of a standard edge swipe gesture by contact 4838, the transition user interface is not displayed 4838.

[0217] In FIGS. 5D27-5D31, a second upward edge swipe gesture by contact 4840 is detected (e.g., at a starting position outside the home affordance 4802-1 in the first appearance state). The second upward edge swipe gesture by contact 4840 itself meets the gesture criteria of a standard edge swipe gesture 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). The upward edge swipe gesture by contact 4840 causes the execution of system operations, including navigation from an application user interface (e.g., user interfaces 4806-1 and 4808-2) (e.g., as shown in FIG. 5D27) displayed in split screen mode, for example, to a user interface external to the application, such as a system user interface (e.g., first the transition user interface 4822-1 (e.g., FIG. 5D28) or 4822-2 (e.g., FIG. 5D30), and finally the home screen user interface (e.g., in FIG. 5D31) or the application switcher user interface (e.g., in FIG. 5D29)), according to various navigation criteria (e.g., the criteria described with respect to the processes shown in FIGS. 9A-9C and 10A-10D). The navigation process shown in 5D27-5D31 is similar to that of FIGS. 5D1-5D6 and is not repeated herein for brevity.

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

[0219] In contrast to the exemplary scenarios shown in FIGS. 5D15 - 5D24, FIGS. 5D25 - 5D31, FIGS. 5D32 - 5D36, and FIGS. 5D37 - 5D43, two exemplary scenarios are shown where an upward edge swipe gesture that meets the standard edge swipe gesture criterion is detected on the side of a split - screen that displays an application associated with the standard edge swipe gesture criterion. In these exemplary scenarios, an upward edge gesture that meets the standard edge swipe gesture criterion (e.g., where extended position requirements or gesture repetition requirements need not be met) causes the execution of system operations (e.g., navigating to a user interface outside 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 criterion.

[0220] As shown in FIG. 5D32, a map application (e.g., using user interface 4806-2) on the left side of the split screen is edge protected (e.g., in a guided navigation mode), and a game application (e.g., using user interface 4808-1) on the right side of the split screen is not edge protected. The home affordance 4802-2 is displayed within a second appearance state (e.g., semi-transparent with reduced visibility) to indicate that at least one of the applications below the home affordance is currently associated with an extended edge swipe gesture criterion. Contact 4842 is detected at a position close to the bottom edge of the screen on the side of the game application, as shown in FIG. 5D32. An upward edge swipe gesture by contact 4842 meets the standard edge swipe gesture criterion associated with the game application and causes the execution of system operations, including navigation from the application user interfaces (e.g., user interfaces 4806-2 and 4808-1) (e.g., as shown in FIG. 5D32) displayed in the split screen mode to a user interface external to the application, e.g., a system user interface (e.g., initially the transition user interface 4822-1 (e.g., FIG. 5D33) or 4822-2 (e.g., FIG. 5D35), and ultimately the home screen user interface (e.g., in FIG. 5D36) or the application switcher user interface (e.g., in FIG. 5D34)), according to various navigation criteria (e.g., the 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, a map application (e.g., using user interface 4806-1) on the left side of the split screen is not edge-protected, and a game application (e.g., using user interface 4808-2) on the right side of the split screen is edge-protected (e.g., in game play mode). The home affordance 4802-2 is displayed within a second appearance state (e.g., semi-transparent with reduced visibility) to indicate that at least one of the applications below the home affordance is currently associated with an extended edge swipe gesture criterion. Contact 4844 is detected at a position close to the bottom edge of the screen on the side of the map application, as shown in FIG. 5D37. An upward swipe gesture by contact 4844 meets the standard edge swipe gesture criterion associated with the map application and, according to various navigation criteria (e.g., the criteria described with respect to the processes shown in FIGS. 9A-9C and 10A-10D), causes the execution of system operations, including navigation from the application user interfaces (e.g., user interfaces 4806-1 and 4808-2) (e.g., as shown in FIG. 5D37) displayed in split screen mode to an external user interface of the application, such as a system user interface (e.g., initially the transition user interface 4822-1 (e.g., FIG. 5D38), 4822-2 (e.g., FIG. 5D40) or 4822-3 (e.g., FIG. 5D42), and finally the home screen user interface (e.g., in FIG. 5D41), the application switcher user interface (e.g., FIG. 5D39)), or a user interface of another application (e.g., FIG. 5D43). The navigation process shown in FIGS. 5D37-5D43 is similar to that of FIGS. 5D1-5D8 and will not be repeated here for the sake of brevity.

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

[0223] As shown in FIG. 5D44, a map application (e.g., using user interface 4806-2) on the left side of the split screen is edge protected (e.g., in guided navigation mode), and a game application (e.g., using user interface 4808-1) on the right side of the split screen is not edge protected. The home affordance 4802-2 is displayed within a second appearance state (e.g., semi-transparent with reduced visibility) to indicate that at least one of the applications below the home affordance is currently associated with an extended edge swipe gesture criterion. Contact 4848 is detected at a position close to the bottom edge of the screen on the side of the map application, as shown in FIG. 5D44. An upward swipe gesture by contact 4848 meets the standard edge swipe gesture criterion associated with the map application but does not meet the extended edge swipe gesture criterion. The upward swipe gesture also does not meet an extended position requirement that temporarily disables edge protection for subsequent edge swipes, and as a result, the home affordance continues to be displayed in the second appearance state (e.g., semi-transparent with reduced visibility), and no system operations are performed. For example, navigation from the application user interfaces (e.g., user interfaces 4806-2 and 4808-1) displayed in split screen mode (e.g., as shown in FIG. 5D44) to an external user interface of the application is not performed. Instead, the gesture input by contact 4848 is provided to the underlying application (e.g., the map application), and operations within the application are performed according to the gesture input on the screen (e.g., as shown in FIG. 5D45, as contact 4848 moves, the piano keys below contact 4848 are pressed). When stopping detecting contact 4848, as shown in FIG. 5D46, the user interface 4806-2 of the map application is restored, e.g., the menu retreats and is removed from the display.

[0224] As shown in FIG. 5D47, a map application (e.g., using user interface 4806-1) on the left side of the split screen is not edge-protected, while a game application (e.g., using user interface 4808-2) on the right side of the split screen is edge-protected (e.g., in game play mode). The home affordance 4802-2 is displayed within 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 criterion. Contact 4850 is detected at a position close to the bottom edge of the screen on the game application side, as shown in FIG. 5D47. An upward swipe gesture by contact 4850 meets the standard edge swipe gesture criterion associated with the game application but does not meet the extended edge swipe gesture criterion. The upward swipe gesture also does not meet an extended position requirement that temporarily disables edge protection for subsequent edge swipes, and as a result, the home affordance continues to be displayed in the second appearance state (e.g., semi-transparent with reduced visibility), and no system operations are performed. For example, navigation from the application user interfaces (e.g., user interfaces 4806-2 and 4808-1) displayed in split screen mode (e.g., as shown in FIG. 5D48) to the user interface outside the application is not performed. Instead, the gesture input by contact 4848 is provided to the underlying application (e.g., the game application), and operations within the application are performed following the movement of contact 4850, as shown in FIG. 5D48, following the pressing of the gesture input (e.g., the piano keys under contact 4850). When contact 4850 is no longer detected, the user interface 4808-2 of the game application is restored, and for example, as shown in FIG. 5D50, the pressed piano keys are restored.

[0225] In the exemplary scenarios shown in FIGS. 5D50 - 5D56, the applications on both sides of the split screen are edge protected. To trigger navigation to the user interface outside the application using an edge swipe gesture, an extended edge swipe criterion must be met. First, an edge swipe gesture that meets the standard edge swipe gesture criterion and the application of an improved position requirement for the first swipe of two consecutive edge swipes is detected, thereby temporarily disabling edge protection for both applications. Subsequently, a second edge swipe gesture that meets the standard edge swipe gesture criterion (detected anywhere along the bottom edge on either side of the split screen) is detected, causing the execution of system operations.

[0226] As shown in FIG. 5D50, a map application (e.g., at user interface 4806-2) and a game application (e.g., at user interface 4808-2) are arranged side by side on the touch screen, and the home affordance 4802-2 is displayed in a second appearance state (e.g., semi-transparent with reduced visibility), overlapping both applications. A first edge swipe gesture by contact 4852 is detected on the home affordance 4802, and as shown in FIG. 5D51, the home affordance changes its appearance state from a second appearance state (e.g., semi-transparent with reduced visibility) to a first appearance state (e.g., opaque with standard visibility), indicating that edge protection is temporarily disabled for both applications. In FIGS. 5D52 to 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 the home affordance 4802-1 in FIG. 5D52). The second edge swipe gesture meets standard edge swipe gesture criteria (e.g., various types of navigation criteria described in correspondence with FIGS. 9A to 9C and FIGS. 10A to 10D), and in some embodiments, it is not necessary to meet the extended position requirements imposed on the first swipe of two consecutive edge swipes required to meet the extended position requirements.The second edge swipe gesture by contact 4854, in combination with the previous gesture by contact 4852, meets the extended edge swipe gesture criteria associated with two lower applications and, according to various navigation criteria (e.g., the criteria described with respect to the processes shown in FIGS. 9A-9C and 10A-10D), 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 FIG. 5D52) displayed in split screen mode to an external user interface of the application, such as a system user interface (e.g., initially the transition user interface 4822-1 (e.g., FIG. 5D53), 4822-2 (e.g., FIG. 5D55) or 4822-3 (e.g., FIG. 5D57), and finally the home screen user interface (e.g., in FIG. 5D56), the application switcher user interface (e.g., FIG. 5D54)), or a user interface of another application (e.g., FIG. 5D58). The navigation processes shown in 5D52-5D58 are similar to those in FIGS. 5D1-5D8 and are not repeated herein for brevity.

[0227] Figures 5D59 - 5D60 and 5D60 - 5D61 show two exemplary scenarios where both sides of a split screen are associated with an extended edge - swipe gesture criterion and are occupied by an edge - protected application. In contrast to the exemplary scenarios shown in FIGS. 5D50 - 5D58, 5D59 - 5D60, and 5D60 - 61, two exemplary scenarios are shown where an upward edge - swipe gesture that meets the standard edge - swipe gesture criterion is detected on the side of the split screen but not on the home affordance. Thus, the edge - swipe gesture does not meet the improved position requirements or gesture - repetition requirements of the improved edge - swipe gesture criterion associated with both applications. As a result, the edge - swipe gesture (e.g., by contact 4856 or contact 4858) does not temporarily disable the 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 system operations (e.g., because the improved position requirements and gesture - repetition criteria of the extended edge - swipe gesture criterion associated with the underlying application are not met). Instead of navigating to an external user interface of the currently displayed application, the gesture is passed as input to the application underlying the gesture and, optionally, causes an operation to be executed 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 touch screen on the side of the game application. The swipe gesture meets the gesture criteria of a standard edge swipe gesture, but does not disable edge protection or cause navigation to a different user interface outside the application. In some embodiments, the gesture is passed to the underlying game application, and the piano keys within the user interface 4804 - 2 are pressed according to 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 touch screen on the side of the map application. The swipe gesture meets the gesture criteria of a standard edge swipe gesture, but does not disable edge protection or cause navigation to a different user interface outside the application. In some embodiments, the gesture is passed to the underlying map application, and the menu within the user interface 4806 - 2 is dragged onto the screen according to the gesture by contact 4858.

[0229] Figures 5D63-5D64 show that when a...

Claims

1. In a device having a touch-sensitive display, displaying a first user interface on the display, the first user interface being separate from a home screen user interface including a plurality of application icons corresponding to different applications of a plurality of applications installed on the device; detecting a first input by a first contact on a first edge of the display while displaying the first user interface on the display; in response to detecting the first input on the edge of the display, while the first contact continues to be detected on the first edge of the display. the first input is detected on a first portion of the first edge of the display, and in accordance with a determination that the first input satisfies a dock display criterion, displaying a dock having a plurality of application icons at a first location along the first edge of the display; pursuant to determining 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 that 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; A method comprising:

2. The method of claim 1 , wherein the first location along the first edge of the display does not include the second portion of the first edge of the display.

3. The method of claim 1 or 2, wherein the second location along the first edge of the display does not include the first portion of the first edge of the display.

4. while displaying the first user interface without displaying the dock on the display; detecting a second input by a second contact on a second edge of the display different from the first edge of the display; The method of any one of claims 1 to 3, further comprising displaying the plurality of application icons in the dock at a third location along the second edge of the display.

5. while displaying the first user interface without displaying the dock on the display; detecting a third input by a third contact on a third edge of the display, the third input being distinct from the first edge of the display and the second edge of the display; The method of claim 4 , further comprising displaying the plurality of application icons in the dock at a fourth location along the third edge of the display.

6. displaying the dock at the first position along the first edge of the display while the first contact continues to be detected on the display; Detecting a lift-off of the first contact from the display; 6. The method of claim 1, further comprising: in response to detecting lift-off of the first contact, maintaining display of the dock on the first user interface on the display after the lift-off of the first contact in accordance with a determination that the first contact moved less than a threshold amount while displaying the dock.

7. in response to detecting a lift-off of the first contact, increasing a size of the dock displayed on the first user interface after the lift-off of the first contact in accordance with a determination that the first contact moved less than the threshold amount while displaying the dock. The method of claim 6 further comprising:

8. 8. The method of claim 6 or 7, further comprising: in response to detecting lift-off of the first contact, moving a display of the dock from the first position along the first edge of the display to a third predetermined position along the first edge of the display in accordance with the determination that the first contact moved less than the threshold amount while displaying the dock.

9. while displaying the dock at the first position along the first edge of the display; Detecting a first movement of the first contact along the dock; responsive to detecting the first movement of the first contact, selecting a respective application icon in the dock according to a current location of the first contact; detecting a lift-off of the first contact from the display after detecting a first movement of the first contact along the first edge; in response to detecting the lift-off of the first contact, in accordance with a determination that a first application icon is currently selected within the dock when the lift-off of the first contact is detected; opening a first application corresponding to the first application icon in the dock; replacing a display of the first user interface with a display of a second user interface for the first application; The method of any one of claims 1 to 8, further comprising:

10. While displaying the dock in the first position along the first edge of the display, Detecting movement of the first contact on the display; 10. The method of claim 1, further comprising: selecting a first application icon in response to detecting that the contact is at a location on the display that corresponds to the display of a first application icon in the dock.

11. While the first application icon is selected, Detecting movement of the first contact on the display away from the first edge of the display; 11. The method of claim 10, further comprising: in response to detecting the movement of the first contact on the display away from the first edge of the display, in accordance with a determination that the first contact was detected at a location that does not correspond to the display of the dock, displaying the first application icon or a representation thereof at a location on the display that corresponds to a location of the first contact that does not correspond to the display of the dock.

12. while displaying the first application icon or the representation thereof at a location on the display corresponding to a location of the first contact that does not correspond to the display of the dock. Detecting lift-off of the first contact; in response to detecting a lift-off of the first contact while the first application icon is displayed on the display at a location corresponding to a location of the first contact that does not correspond to the display of the dock. replacing the display of the first user interface within a first portion of the display with a display of a second user interface corresponding to an application associated with the first application icon; The method of claim 11 , further comprising maintaining a display of the first user interface on a second portion of the display that does not overlap the first portion of the display.

13. while displaying the dock at the first position along the first edge of the display; Detecting movement of the first contact towards the first edge of the display; in response to detecting the movement of the first contact toward a first edge of the display, ceasing display of the dock in accordance with a determination that the dock removal criteria is satisfied by the movement of the first contact toward the first edge of the display. The method of any one of claims 1 to 12, further comprising:

14. 14. The method of claim 1, wherein the first portion of the first edge of the display is within a first predefined sub-range of the first edge of the display, and the first position is a first predetermined position within the first predefined sub-range of the first edge.

15. the second position of the first edge of the display is within a second predefined sub-range of the first edge of the display; the dock displayed at the second location is centered on the location of the first contact when the first contact is at least a threshold distance away from a first adjacent edge of the first edge proximate to the first contact; 15. The method of claim 1, wherein the dock displayed at the second location is displayed abutting a first adjacent edge of the first edge when the first contact is less than the threshold distance away from the first adjacent edge of the first edge.

16. A method according to any preceding claim, wherein the size of the dock is larger when the dock is displayed in the first position than the size of the dock when the dock is displayed in the second position.

17. in response to detecting the first input on the edge of the display, while the first contact continues to be detected at the first edge of the display. pursuant to determining that the first input satisfies navigation gesture criteria, the navigation gesture criteria including a requirement that a threshold amount of movement across the display by the first contact in a direction away from the first edge of the display be detected for the navigation gesture criteria to be satisfied; 17. The method of any one of claims 1 to 16, further comprising entering a transitional user interface mode in which a plurality of different user interface states are available to be selected based on a comparison of a set of one or more properties of the first input to a corresponding set of one or more thresholds.

18. 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: displaying a first user interface on the display, the first user interface being separate from a home screen user interface including a plurality of application icons corresponding to different applications of a plurality of applications installed on the device; detecting a first input by a first contact on a first edge of the display while displaying the first user interface on the display; in response to detecting the first input on the 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 a dock display criterion, the first input being detected on a first portion of the first edge of the display; pursuant to determining that the first input is detected on a second portion of the first edge of the display that is different from the first portion of the first edge, and that the first input satisfies the dock display criteria, display 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. The electronic device includes a memory containing instructions to

19. 1. A computer-readable storage medium having stored thereon one or more programs that, when executed by an electronic device having a touch-sensitive display, cause the device to: displaying a first user interface on the display, the first user interface being separate from a home screen user interface including a plurality of application icons corresponding to different applications of a plurality of applications installed on the device; detecting a first input by a first contact on a first edge of the display while displaying the first user interface on the display; in response to detecting the first input on the 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 portion of the display in accordance with a determination that the first input satisfies a dock display criterion, the first input being detected on a first portion of the first edge of the display; pursuant to determining that the first input is detected on a second portion of the first edge of the display that is different from the first portion of the first edge and that 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. A computer-readable storage medium.

20. 1. A graphical user interface on an electronic device having a touch-sensitive display, a memory, and one or more processors executing one or more programs stored in the memory, the graphical user interface comprising: A rendering from a first application that is separate from a rendering of a home screen that includes a plurality of application icons corresponding to different applications of a plurality of applications installed on the device. Including, a first input is detected by a first contact on a first edge of the display while displaying the first user interface on the display; in response to detecting the first input on the edge of the display, while the first contact continues to be detected on the first edge of the display. the first input is detected on a first portion of the first edge of the display, and in accordance with a determination that the first input satisfies a dock display criterion, a dock having a plurality of application icons is displayed at a first location along the first portion of the display; a first input detected on a second portion of the first edge of the display that is different from the first portion of the first edge, and in accordance with a determination that the first input satisfies the dock display criterion, the dock is displayed 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.

21. 1. An electronic device comprising: A touch-sensitive display; means for displaying a first user interface on the display, the first user interface being separate from a home screen user interface including a plurality of application icons corresponding to different applications of a plurality of applications installed on the device; means for detecting a first input by a first contact on a first edge of the display while displaying the first user interface on the display; in response to detecting the first input on the edge of the display, and while the first contact continues to be detected at 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 is detected on a first portion of the first edge of the display in accordance with a determination that the first input satisfies a dock display criterion; means for 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 pursuant to a determination that the first input is detected on a second portion of the first edge different from the first portion of the first edge and the first input satisfies the dock display criteria, the second location being different from the first location. Electronic devices.

22. 1. An information processing apparatus for use in an electronic device having a touch-sensitive display, comprising: means for displaying a first user interface on the display, the first user interface being separate from a home screen user interface including a plurality of application icons corresponding to different applications of a plurality of applications installed on the device; means for detecting a first input by a first contact on a first edge of the display while displaying the first user interface on the display; in response to detecting the first input on the edge of the display, and while the first contact continues to be detected at 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 response to a determination that the first input is detected on a first portion of the first edge of the display and in response to a determination that the first input satisfies a dock display criterion; means for 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 pursuant to a determination that the first input is detected on a second portion of the first edge different from the first portion of the first edge and the first input satisfies the dock display criteria, the second location being different from the first location. Information processing device.

23. 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 containing instructions for performing the method of any one of claims 1 to 17.

24. 18. A computer readable storage medium having stored thereon one or more programs, the one or more programs comprising instructions that, when executed by an electronic device having a touch-sensitive display, cause the device to perform any one of the methods of claims 1 to 17.

25. A graphical user interface on an electronic device having a touch-sensitive display, a memory, and one or more processors executing one or more programs stored in the memory, the graphical user interface comprising a user interface displayed in accordance with any one of the methods of claims 1 to 17.

26. 1. An electronic device comprising: A touch-sensitive display; 18. An electronic device comprising means for carrying out any one of the methods according to claims 1 to 17.

27. 1. An information processing apparatus for use in an electronic device having a touch-sensitive display, comprising:

18. An electronic device comprising means for carrying out any one of the methods according to claims 1 to 17.

28. In a device having a touch-sensitive surface and a display, 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; 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; In response to detecting the first input, replacing a display of the first user interface and the second user interface with a full screen home screen in response to a determination that the first input satisfies first criteria, the first criteria including a requirement of movement in the first direction exceeding a first threshold amount for the first criteria to be satisfied; pursuant to a determination that the first input satisfies the second criteria, the second criteria including a requirement that the first input include movement in the first direction less than the first threshold amount for the second criteria to be satisfied, and pursuant to a determination that the first input was initiated within a first edge region of the display corresponding to the first application user interface, 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 the second portion of the display; and replacing the display of the second application user interface with a second replacement 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 satisfies the second criterion and in accordance with a determination that the first input was initiated within a second edge region corresponding to the second application user interface. A method comprising:

29. the second criteria includes an application switcher interface navigation criterion, the application switcher interface navigation criterion requiring that the first input include movement of the first contact at a magnitude of a movement parameter in a direction away from a respective edge region of the display, the first input being initiated such that the application switcher interface navigation criterion is satisfied; 30. The method of claim 28, wherein the replacement user interface is an application switcher user interface including respective representations of applications for selectively activating one of a plurality of applications currently represented in the application switcher user interface.

30. while displaying the application switcher user interface on either the first portion of the display or the second portion of the display; Detecting a selection of a first representation within the respective representations of applications to selectively activate one of the applications currently represented within the application switcher user interface; In response to detecting a selection of the first representation, displaying a user interface for an application associated with the first representation in the first portion of the display while maintaining a display of the second application user interface in the second portion of the display when the application switcher user interface is displayed in the first portion of the display when selection of the first representation is detected; displaying the user interface for the application associated with the first representation in the second portion of the display while maintaining the display of the first application user interface in the first portion of the display when the application switcher user interface is displayed in the second portion of the display when selection of the first representation is detected.

30. The method of claim 29, comprising:

31. The application switcher user interface is displayed on the first portion of the display, and the method further comprises: detecting a second input by a second contact within a second edge region of the display corresponding to the second application user interface while displaying the first representation within the first portion of the display and the user interface for the application associated with the second application user interface within the second portion of the display; in response to detecting the second input, replacing the display of the application switcher user interface with the second application user interface in the second portion of the display while maintaining the display of the user interface for the application associated with the first representation in the first portion of the display in accordance with a determination that the second input satisfies the application switcher interface navigation criteria; The application switcher user interface in the second portion of the display includes a representation of the first application associated with the first application user interface previously displayed on the first portion of the display.

31. The method of claim 30, comprising:

32. the second criteria include a last application switcher interface navigation criterion, the last application switcher interface navigation criterion requiring that the first input include movement of the first contact at a magnitude of a movement parameter in a direction substantially parallel to a respective edge region of the display, the first input being initiated; A method according to any one of claims 28 to 31, wherein the replacement user interface is a first previously displayed application user interface that is different from the respective application user interface it is replacing.

33. after replacing the display of the first application user interface with a first replacement user interface, the first replacement application user interface being a previously displayed application user interface, and within a first temporal threshold from liftoff of the first contact; detect a second input by a second contact including movement of the second contact beginning at the first edge region and having a magnitude of a movement parameter in a direction substantially parallel to the first edge region of the display that satisfies the last application interface navigation criterion; In response to detecting the second input, pursuant to a determination that a second previously-displayed application user interface is available to be navigated to, replacing a display of the first previously-displayed application user interface with the second previously-displayed application user interface; displaying the second previously displayed application user interface in a full screen display mode in accordance with a determination that the second previously displayed application user interface cannot be navigated; 33. The method of claim 32, comprising:

34. in response to detecting the first input, in accordance with a determination that the first input satisfies a third criterion, the third criterion requiring that the first input include movement in the first direction less than the first threshold amount but include movement in the first direction greater than a second threshold amount to satisfy the third criterion, and displaying a full screen application switcher user interface. The method according to any one of claims 28 to 33, comprising:

35. while simultaneously displaying the first application user interface and the second application user interface on the first portion of the display and prior to detecting the first input; displaying a first affordance over a portion of the first application user interface, a location of the first affordance indicating a responsive area for initiating a predefined gesture input on the first portion of the display; 35. The method of any one of claims 28 to 34, comprising displaying a second affordance over a portion of the second application user interface, a location of the second affordance indicating a responsive area for initiating the default gesture input on the second portion of the display.

36. a size of the first affordance is proportional to a size of the first portion of the display; a size of the second affordance is proportional to a size of the second portion of the display; while displaying the first affordance on the portion of the first application user interface and while displaying the second affordance on the portion of the second application user interface. Detecting user input that satisfies split-screen resize criteria; in response to detecting a user input that satisfies the split screen resizing criteria, resizing the first portion of the display from a first size to a second size and resizing the presentation of the first application user interface and the presentation of the first affordance proportional to the second size of the first portion of the display; 36. The method of claim 35, comprising resizing the second portion of the display from a third size to a fourth size and displaying the second application user interface and a second affordance proportional to the fourth size of the second portion of the display.

37. 37. The method of any one of claims 28 to 36, further comprising: displaying a third affordance on a portion of a third application user interface while displaying the third application user interface in a full screen display mode, the location of the third affordance indicating a responsive area on the display for initiating a predefined gesture input.

38. the first criterion and the second criterion each require liftoff of the first input, and the method further comprises: in response to detecting the movement of the first input in the first direction across the display, prior to detecting lift-off of the first input. pursuant to a determination that the first input commenced at the first edge region of the display corresponding to the first application user interface, replacing the display of the first application user interface with a transitional user interface including a first application view corresponding to the first application user interface, the size of the first application view dynamically changing with the movement of the first input across the display while maintaining the display of the second application user interface in the second portion of the display; 38. The method of claim 28, further comprising: replacing display of the second application user interface with a transitional user interface including a second application corresponding to the second application user interface in accordance with a determination that the first input has commenced in the second edge region of the display corresponding to the second application user interface; and, while maintaining display of the first application user interface in the first portion of the display, the size of the second application view dynamically changes with the movement of the first input across the display.

39. 40. The method of claim 38, comprising monitoring a position and velocity of the first contact while displaying the transition user interface and providing corresponding visual feedback to indicate how a device would be navigated if lift-off of the first contact is detected at the current moment.

40. While displaying the transitional user interface on either the first portion of the display or the second portion of the display, display of two or more application views within the transitional user interface is suppressed when, upon lift-off of the first contact, the device: pursuant to a determination that the first input has been initiated at the first edge region, displaying an application switcher user interface including a plurality of representations of applications that selectively activate one of a plurality of applications represented in the application switcher user interface in the first portion of the display while maintaining display of the second application user interface in the second portion of the display.

40. The method of claim 39, comprising displaying the application switcher user interface including a plurality of representations of applications that selectively activate one of a plurality of applications represented in an application switcher user interface in the second portion of the display pursuant to a determination that the first input has been initiated in the second edge region, and maintaining display of the first application user interface in the first portion of the display.

41. while displaying the transitional user interface on either the first portion of the display or the second portion of the display; Detecting a first characteristic of the first input that satisfies the first criterion upon lift-off of the first contact; in response to detecting the first movement of the first contact, pursuant to determining that the first input initiated in the first edge region has begun, ceasing to display the second application user interface within the second portion of the display and expanding display of the transition user interface from the first portion of the display to the entire display; 41. The method of claim 39 or 40, comprising ceasing to display the first application user interface within the first portion of the display and expanding display of the transition user interface to fill the entire display in accordance with a determination that the first input has commenced in the second edge region.

42. ceasing to display the first application user interface or the second application user interface; responsive to determining that the first input has been initiated at the first edge region, replacing a display of the first application user interface with a display of the first application user interface view, wherein display characteristics of the application view of the first application user interface dynamically change in response to movement of the first input; In response to a determination that a first input has been initiated in the second edge region, replacing a display of the second application user interface with a display of an application view of the second application user interface, wherein display characteristics of the application view of the second application user interface are dynamically changed in response to movement of the first input.

42. The method of claim 41 , comprising:

43. 43. The method of claim 41 or 42, wherein while displaying the full screen transition user interface, display of two or more applications in the transition user interface, upon lift-off of the first contact, the device displays an application switcher user interface including a plurality of representations of applications that selectively activates one of the plurality of applications represented in the full screen application switcher user interface.

44. 44. The method of any one of claims 41 to 43, wherein displaying only one application view in the transition user interface while displaying the full screen transition user interface indicates that the device will display the full screen home screen upon lift-off of the first contact.

45. while displaying application views of the first application user interface and the second application user interface within the full-screen transition user interface. detecting a gesture comprising movement of the first contact in a second direction toward the first edge region or a second edge region of the display; in response to detecting the gesture including moving the first contact in the second direction, restore presentation of the second application user interface on the second portion of the display in accordance with a determination that the first input was initiated in the first edge region; 45. The method of claim 42, comprising restoring a display of the first application user interface within the first portion of the display in accordance with a determination that the first input has been initiated within the second edge region.

46. a plurality of representations of applications for selectively activating one of the plurality of applications represented in the application switcher user interface while displaying the full screen application switcher user interface includes a first representation associated with at least two applications that are simultaneously activated upon selection of the first representation; 46. ​​The method of claim 41, wherein while displaying the application switcher user interface on either the first portion of the display or the second portion of the display, the multiple representations of applications that selectively activate one of the multiple applications represented in the application switcher user interface do not include representations associated with at least two applications that are activated simultaneously upon selection.

47. 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 and prior to detecting the first input by the first contact; Detecting a first touch input on a first edge of the display that satisfies a dock display criterion; in response to detecting the first touch input on the first edge of the display, while the first touch input 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 response to determining that the first touch input is detected on a first portion of the first edge of the display; 47. The method of any one of claims 28 to 46, comprising: 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 in accordance with a determination that the first touch input is detected on a second portion of the first edge of the display, the second location being different from the first location.

48. 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: 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; 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; In response to detecting the first input, replacing a display of the first user interface and the second user interface with a full screen home screen in response to a determination that the first input satisfies first criteria, the first criteria including a requirement of movement in the first direction exceeding a first threshold amount for the first criteria to be satisfied; pursuant to a determination that the first input satisfies the second criteria, the second criteria including a requirement that the first input include movement in the first direction less than the first threshold amount for the second criteria to be satisfied, and pursuant to a determination that the first input was initiated within a first edge region of the display corresponding to the first application user interface, 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 the second portion of the display; in accordance with a determination that the first input satisfies the second criterion, in accordance with a determination that the first input was initiated within a second edge region corresponding to the second application user interface, replacing the display of the second user interface with a second replacement user interface while maintaining the display of the first application user interface within the first portion of the display; The electronic device includes instructions for:

49. 1. A computer-readable storage medium having stored thereon one or more programs that, when executed by an electronic device having a touch-sensitive display, cause the device to: 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; 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; In response to detecting the first input, replacing a display of the first user interface and the second user interface with a full screen home screen in response to a determination that the first input satisfies first criteria, the first criteria including a requirement of movement in the first direction exceeding a first threshold amount for the first criteria to be satisfied; pursuant to a determination that the first input satisfies the second criteria, the second criteria including a requirement that the first input include movement in the first direction less than the first threshold amount for the second criteria to be satisfied, and pursuant to a determination that the first input was initiated within a first edge region of the display corresponding to the first application user interface, 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 the second portion of the display; a storage medium including instructions for causing, in accordance with a determination that the first input satisfies a second criterion, to replace a display of the second user interface with a second replacement 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 was initiated within a second edge region corresponding to the second application user interface.

50. 1. A graphical user interface on an electronic device having a touch-sensitive display, a memory, and one or more processors executing one or more programs stored in the memory, the graphical user interface comprising: simultaneous rendering of a first application on a first portion of the display and a second application on a second portion of the display different from the first portion; Including, 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; In response to detecting the first input, replacing a display of the first user interface and the second user interface with a full screen home screen in response to a determination that the first input satisfies first criteria, the first criteria including a requirement of movement in the first direction exceeding a first threshold amount for the first criteria to be satisfied; pursuant to a determination that the first input satisfies the second criteria, the second criteria including a requirement that the first input include movement in the first direction less than the first threshold amount for the second criteria to be satisfied, and pursuant to a determination that the first input was initiated within a first edge region of the display corresponding to the first application user interface, 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 the second portion of the display; a graphical user interface that causes a display of the second user interface to be replaced with a second replacement 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 satisfies a second criterion and in accordance with a determination that the first input was initiated within a second edge region corresponding to the second application user interface.

51. 1. An electronic device comprising: A touch-sensitive display; means for 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; means for detecting a first input by a first contact comprising a 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; and In response to detecting the first input, replacing a display of the first user interface and the second user interface with a full screen home screen in response to a determination that the first input satisfies first criteria, the first criteria including a requirement of movement in the first direction exceeding a first threshold amount for the first criteria to be satisfied; pursuant to a determination that the first input satisfies the second criteria, the second criteria including a requirement that the first input include movement in the first direction less than the first threshold amount for the second criteria to be satisfied, and pursuant to a determination that the first input was initiated within a first edge region of the display corresponding to the first application user interface, 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 the second portion of the display; means for replacing a display of the second application user interface with a second replacement 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 satisfies the second criterion and in accordance with a determination that the first input was initiated within a second edge region corresponding to the second application user interface; 2. An electronic device comprising:

52. 1. An information processing apparatus for use in an electronic device having a touch-sensitive display, comprising: means for 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; means for detecting a first input by a first contact comprising a 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; and In response to detecting the first input, replacing a display of the first user interface and the second user interface with a full screen home screen in response to a determination that the first input satisfies first criteria, the first criteria including a requirement of movement in the first direction exceeding a first threshold amount for the first criteria to be satisfied; pursuant to a determination that the first input satisfies the second criteria, the second criteria including a requirement that the first input include movement in the first direction less than the first threshold amount for the second criteria to be satisfied, and pursuant to a determination that the first input was initiated within a first edge region of the display corresponding to the first application user interface, 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 the second portion of the display; means for replacing a display of the second application user interface with a second replacement 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 satisfies the second criterion and in accordance with a determination that the first input was initiated within a second edge region corresponding to the second application user interface; An information processing device comprising:

53. 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 containing instructions for performing a method according to any one of claims 28 to 47.

54. 48. A computer readable storage medium having stored thereon one or more programs comprising instructions that, when executed by an electronic device having a touch-sensitive display, cause the device to perform any one of the methods of claims 28 to 47.

55. A graphical user interface on an electronic device having a touch-sensitive display, a memory, and one or more processors executing one or more programs stored in the memory, the graphical user interface comprising a user interface displayed in accordance with any one of the methods of claims 28 to 47.

56. 1. An electronic device comprising: A touch-sensitive display; An electronic device comprising means for carrying out any one of the methods according to claims 28 to 47.

57. 1. An information processing apparatus for use in an electronic device having a touch-sensitive display, comprising: Means for carrying out any one of the methods according to claims 28 to 47, An information processing device comprising:

58. In an electronic device having a display and a touch-sensitive surface, displaying, on the display, a user interface of a first application of a plurality of applications installed on the device; 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 detecting the gesture includes simultaneously detecting multiple contacts on the touch-sensitive surface and detecting movement of the multiple contacts; in response to detecting a gesture on the touch-sensitive surface, pursuant to a determination that the gesture includes two simultaneously detected contacts, performing an action in the first application based on the movement of the two simultaneously detected contacts during the gesture; switch from displaying the user interface of the first application to displaying a user interface of a second application of the plurality of applications that is distinct from the first application in accordance with a determination that the gesture includes more than a predetermined number of simultaneously detected contacts that are greater than two and a determination that the movement of the simultaneously detected contacts during the gesture satisfies a first criterion; switching from displaying the user interface of the first application to displaying a user interface including respective application icons for opening the plurality of 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 distinct from the first criterion; A method comprising:

59. 60. The method of claim 58, wherein the first criterion requires that the gesture include movement in a first direction that exceeds a first threshold amount for the first criterion to be met.

60. A method according to any one of claims 58 to 59, wherein the second criterion requires that the gesture include movement in a second direction exceeding a second threshold amount for the second criterion to apply.

61. 61. The method of any one of claims 58 to 60, wherein the second criterion requires that the gesture include movement of the simultaneously detected contacts towards each other exceeding a third threshold amount for the second criterion.

62. in response to detecting a gesture on the touch-sensitive surface, switching from displaying the user interface of the first application to displaying a user interface including a representation of each of a plurality of recently active applications 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 third criterion. The method of any one of claims 58 to 61, comprising:

63. 63. The method of claim 62, wherein the third criterion requires that the input include movement in a second direction that is greater than a fourth threshold amount and less than a fifth threshold amount for the third criterion to be met.

64. 64. The method of any one of claims 62-63, wherein the third criterion requires that the inputs include movement of the simultaneously detected contacts towards each other of less than a sixth threshold amount for the third criterion to be met.

65. in response to detecting a gesture on the touch-sensitive surface, maintaining a display of the first application on the display in accordance with a determination that the gesture includes more than the predetermined number of simultaneously detected contacts and a determination that movement of the simultaneously detected contacts during the gesture satisfies a fourth criterion. The method of any one of claims 58 to 64, comprising:

66. 66. The method of claim 65, wherein, to be satisfied, the fourth criterion requires that the input include movement by the simultaneously detected contacts less than a seventh threshold amount.

67. in response to detecting a gesture on the touch-sensitive surface, performing an action within the first application in accordance with the gesture in accordance with a determination that the gesture includes more than the predetermined number of simultaneously detected contacts and in accordance with a determination that the movement of the simultaneously detected contacts across the touch-sensitive surface begins at least a threshold amount of time after an initial detection of the multiple contacts on the touch-sensitive surface. The method of any one of claims 58 to 66, comprising:

68. Detecting relative movement of the simultaneously detected contacts toward one another across the touch-sensitive surface during the gesture; resizing a representation of a user interface of the first application according to relative movement of the simultaneously detected contacts toward one another. The method of any one of claims 58 to 67, comprising:

69. detecting movement of the simultaneously detected contacts across the touch-sensitive surface in respective directions corresponding to movement across the display toward a predetermined edge of the display; resizing a representation of the user interface of the first application in accordance with movement of the simultaneously detected contacts in the respective directions. The method of any one of claims 58 to 68, comprising:

70. simultaneously detecting first movements of the simultaneously detected contacts in respective directions across the touch-sensitive surface and second movements of the simultaneously detected contacts toward one another; moving a representation of the user interface of the first application across the display in accordance with the first movements of the simultaneously detected contacts in the respective directions; resizing the representation of the user interface of the first application on the display in accordance with the second movement of the simultaneously detected contacts toward one another.

70. The method of any one of claims 58 to 69, comprising:

71. 71. The method of any one of claims 58 to 70, comprising detecting a change in a total number of simultaneously detected contacts during the gesture, and wherein the first criterion or the second criterion does not require that the total number of simultaneously detected contacts remain constant during the gesture for the first or second criterion to be satisfied.

72. 72. The method of claim 71 , further comprising detecting additional movement of remaining contacts on the touch-sensitive surface after detecting a change in the total number of simultaneously detected contacts, wherein the first or second criterion is satisfied after detecting the additional movement of the remaining contacts.

73. Detecting the gesture includes: Detecting a first portion of the gesture; detecting a second portion of the gesture subsequent to the first portion of the gesture; the first portion of the gesture includes synchronous movement in respective directions of at least the predetermined number of simultaneously detected contacts; the second portion of the gesture includes movement of at least the predetermined number of simultaneously detected contacts toward one another; At least one of the first criterion and the second criterion is satisfied after detecting the first and second portions of the gesture.

73. The method according to any one of claims 58 to 72.

74. Detecting the gesture includes: Detecting a third portion of the gesture; and detecting a fourth portion of the gesture subsequent to the third portion of the gesture. the third portion of the gesture includes movement of at least the predetermined number of simultaneously detected contacts toward one another; the fourth portion of the gesture includes synchronous movement in each direction of at least the predetermined number of simultaneously detected contacts; at least one of the first criterion and the second criterion is satisfied after detecting the third and fourth portions of the gesture.

74. The method according to any one of claims 58 to 73.

75. The method of any one of claims 58 to 74, wherein the initial portion of the gesture is detected in a central portion of the touch-sensitive surface, away from any edges of the touch-sensitive surface.

76. 76. The method of any one of claims 58 to 75, wherein each one of the first criterion and the second criterion does not require that lift-off of the plurality of contacts be detected in order for each one of the first criterion and the second criterion to be satisfied.

77. A touch-sensitive display; one or more processors; An electronic device comprising: 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: displaying, on the display, a user interface of a first application of a plurality of applications installed on the device; 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 includes simultaneously detecting multiple contacts on the touch-sensitive surface and detecting movement of the multiple contacts; in response to detecting a gesture on the touch-sensitive surface, pursuant to a determination that the gesture includes two simultaneously detected contacts, performing an action in the first application based on the movement of the two simultaneously detected contacts during the gesture; switch from displaying the user interface of the first application to displaying a user interface of a second application of the plurality of applications that is distinct from the first application in accordance with a determination that the gesture includes more than a predetermined number of simultaneously detected contacts that are greater than two and a determination that the movement of the simultaneously detected contacts during the gesture satisfies a first criterion; switching from displaying the user interface of the first application to displaying a user interface including respective application icons for opening the plurality of 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 distinct from the first criterion; The electronic device includes instructions for:

78. 1. A computer-readable storage medium having stored thereon one or more programs that, when executed by an electronic device having a touch-sensitive display, cause the device to: displaying, on the display, a user interface of a first application of a plurality of applications installed on the device; 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 includes simultaneously detecting multiple contacts on the touch-sensitive surface and detecting movement of the multiple contacts; in response to detecting a gesture on the touch-sensitive surface, pursuant to determining that the gesture includes the two simultaneously detected contacts, performing an action in a first application based on the movement of the two simultaneously detected contacts during the gesture; switch from displaying the user interface of the first application to displaying a user interface of a second application of the plurality of applications that is distinct from the first application in accordance with a determination that the gesture includes more than a predetermined number of simultaneously detected contacts that are greater than two and a determination that the movement of the simultaneously detected contacts during the gesture satisfies a first criterion; A computer-readable storage medium comprising instructions for causing a switch from displaying a user interface of a first application to displaying a user interface including respective application icons for opening a plurality of applications installed on the device in accordance with a determination that the gesture includes more than a predetermined number of simultaneously detected contacts and a determination that movement of the simultaneously detected contacts during the gesture satisfies a second criterion, separate from the first criterion.

79. 1. A graphical user interface on an electronic device having a touch-sensitive display, a memory, and one or more processors executing one or more programs stored in the memory, the graphical user interface comprising: Rendering a user interface of a first application of a plurality of applications installed on the device; the device detects 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 detecting the gesture includes detecting multiple contacts on the touch-sensitive surface simultaneously and detecting movement of the multiple contacts; in response to detecting a gesture on the touch-sensitive surface, In accordance with determining that the gesture includes the two simultaneously detected contacts, the device performs an action in a first application based on the movement of the two simultaneously detected contacts during the gesture; in accordance with a determination that the gesture includes more than a predetermined number of simultaneously detected contacts that are greater than two and a determination that the movement of the simultaneously detected contacts during the gesture satisfies a first criterion, switching the device from displaying the user interface of the first application to displaying a user interface of a second application of the plurality of applications that is distinct from the first application; a graphical user interface including instructions that cause the device to switch from displaying the user interface of the first application to displaying a user interface including respective application icons for opening the plurality of 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 distinct from the first criterion.

80. 1. An electronic device comprising: A touch-sensitive display; means for displaying, on the display, a user interface of a first application of a plurality of applications installed on the device; detecting a gesture on the touch-sensitive surface, the detecting the gesture including detecting an initial portion of the gesture while displaying the user interface of the first application on the display, the detecting the gesture including means for simultaneously detecting multiple contacts on the touch-sensitive surface and detecting movement of the multiple contacts; and in response to detecting a gesture on the touch-sensitive surface, pursuant to a determination that the gesture includes two simultaneously detected contacts, performing an action in the first application based on the movement of the two simultaneously detected contacts during the gesture; switch from displaying the user interface of the first application to displaying a user interface of a second application of the plurality of applications that is distinct from the first application in accordance with a determination that the gesture includes more than a predetermined number of simultaneously detected contacts that are greater than two and a determination that the movement of the simultaneously detected contacts during the gesture satisfies a first criterion; means for switching from displaying the user interface of the first application to displaying a user interface including respective application icons for opening the plurality of 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 distinct from the first criterion; 2. An electronic device comprising:

81. 1. An information processing apparatus for use in an electronic device having a touch-sensitive display, comprising: means for displaying, on the display, a user interface of a first application of a plurality of applications installed on the device; detecting a gesture on the touch-sensitive surface, the detecting the gesture including detecting an initial portion of the gesture while displaying the user interface of the first application on the display, the detecting the gesture including means for simultaneously detecting multiple contacts on the touch-sensitive surface and detecting movement of the multiple contacts; and in response to detecting a gesture on the touch-sensitive surface, pursuant to a determination that the gesture includes two simultaneously detected contacts, performing an action in the first application based on the movement of the two simultaneously detected contacts during the gesture; switch from displaying the user interface of the first application to displaying a user interface of a second application of the plurality of applications that is distinct from the first application in accordance with a determination that the gesture includes more than a predetermined number of simultaneously detected contacts that are greater than two and a determination that the movement of the simultaneously detected contacts during the gesture satisfies a first criterion; means for switching from displaying the user interface of the first application to displaying a user interface including respective application icons for opening the plurality of 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 distinct from the first criterion; An information processing device comprising:

82. 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 containing instructions for performing a method according to any one of claims 58 to 76.

83. 77. A computer readable storage medium having stored thereon one or more programs comprising instructions that, when executed by an electronic device having a touch-sensitive display, cause the device to perform any one of the methods of claims 58 to 76.

84. A graphical user interface on an electronic device having a touch-sensitive display, a memory, and one or more processors executing one or more programs stored in the memory, the graphical user interface comprising a user interface displayed according to any of the methods of claims 58 to 76.

85. 1. An electronic device comprising: A touch-sensitive display; Means for carrying out any one of the methods according to claims 58 to 76; An electronic device comprising:

86. 1. An information processing apparatus for use in an electronic device having a touch-sensitive display, comprising: Means for carrying out any one of the methods according to claims 58 to 76, An information processing device comprising:

87. In an electronic device having a touch-sensitive display, simultaneously displaying a first application and a second application on the touch-sensitive display, both of the first application and the second application being displayed along at least a portion of a respective edge of the touch-sensitive display; detect movement of a first edge swipe gesture at a respective location along the respective edge of the touch-sensitive display, including movement of a contact onto the touch-sensitive display from the respective location along the respective edge of the touch-sensitive display while simultaneously displaying the first application and the second application; In response to detecting the first edge swipe gesture, performing a system operation in accordance with determining that the respective positions of the first edge swipe gestures correspond to positions of the first application on the touch-sensitive display, determining that the first application is simultaneously associated with standard edge swipe gesture criteria, and determining that the first edge swipe gesture satisfies the standard edge swipe gesture criteria, the standard edge swipe gesture including a first set of one or more requirements that must be satisfied in order for the standard edge swipe gesture criteria to be satisfied, and 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; performing the system operation in accordance with determining that the respective positions of the first edge swipe gestures correspond to positions 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; in accordance with determining that the respective positions of the first edge swipe gesture correspond to a position of the first application on the touch-sensitive display, determining that the first application is simultaneously associated with extended edge swipe gesture criteria, and determining that the first edge swipe gesture satisfies the extended edge swipe gesture criteria, the extended edge swipe gesture including the 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, ceasing to perform the system operation; refraining from performing the system operation in accordance with a determination that the respective position of the first edge swipe gesture corresponds to a position of the 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. A method comprising:

88. 88. The method of claim 87, wherein the first set of one or more requirements includes a movement requirement that is met when a first movement parameter of the first edge swipe gesture meets a first threshold.

89. 89. The method of any one of claims 87 to 88, wherein the second set of one or more requirements includes a requirement that two edge swipe gestures that satisfy the standard edge swipe gesture criteria are detected at respective positions along respective edges of the touch-sensitive display that correspond to positions of the respective applications that are simultaneously associated with the extended edge swipe gesture criteria.

90. detecting a second edge swipe gesture after detecting the first edge swipe gesture, the respective positions of the first edge swipe gesture corresponding to respective application positions of the first and second applications concurrently associated with the extended edge swipe gesture criteria, and canceling performance of the system operation in accordance with the determination that the first edge swipe gesture did not satisfy the extended edge swipe gesture criteria; in response to detecting the second edge swipe gesture after detecting the first edge swipe gesture, 90. The method of claim 87, comprising: performing the system operation in accordance with determining that a position of each of the second edge swipe gestures corresponds to a position of the respective application of the first and second applications simultaneously associated with the extended edge swipe gesture criteria and determining that the second edge swipe gesture also satisfies the standard edge swipe gesture criteria.

91. A first user interface element is displayed within an area proximate to the respective edge of the touch-sensitive display, and the second set of one or more requirements includes a requirement that a currently detected edge swipe gesture that meets standard edge swipe gesture criteria be detected at the respective position of the first user interface element displayed along the respective edge of the touch-sensitive display, the requirement being an extended position of a previous edge swipe gesture immediately prior to the currently detected edge swipe gesture that meets standard edge swipe gesture criteria. The method according to any one of claims 87 to 90, comprising:

92. In response to detecting the first edge swipe gesture, performing the system operation in accordance with a determination that the respective positions of previous edge swipe gestures detected before the first edge swipe gesture correspond to a respective one of the first and second applications currently associated with the extended edge swipe gesture criteria, a determination that both the previous edge swipe gesture and the first edge swipe gesture satisfy the standard edge swipe gesture criteria, and a determination that the previous edge swipe gestures have been detected at respective positions on the first user interface element displayed on the respective edges of the touch-sensitive display.

92. The method of claim 91, comprising:

93. performing the system operations, ceasing to simultaneously display the first application and the second application; displaying a home screen user interface including a plurality of application launch icons representing a plurality of applications installed on the electronic device, each application launch icon of the plurality of application launch icons, when activated, causing the electronic device to launch a corresponding application of the respective application launch icon; The method according to any one of claims 87 to 92, comprising:

94. performing the system operations, ceasing to simultaneously display the first application and the second application; displaying an application switcher user interface including a plurality of representations of the application corresponding respectively to a plurality of recently used applications; The method according to any one of claims 87 to 92, comprising:

95. performing the system operations, selectively displaying one of a plurality of system user interfaces in accordance with one or more characteristic parameters of the first edge swipe gesture; displaying a home screen user interface including a plurality of application launch icons representing a plurality of applications installed on the electronic device in accordance with a determination that the one or more characteristic parameters of the first edge swipe gesture satisfy a first criterion, wherein, when each application launch icon of the plurality of application launch icons is activated, causing the electronic device to launch a corresponding application of the respective application launch icon and to cease simultaneously displaying the first application and the second application; displaying an application switcher user interface including a plurality of representations of applications corresponding respectively to a plurality of recently used applications in accordance with a determination that the one or more characteristic parameters of the first edge swipe gesture satisfy a second criterion; The method of any one of claims 87 to 92, comprising:

96. 96. The method of claim 87, comprising displaying user interface elements across at least a portion of the first user interface of the first application and at least a portion of the second user interface of the second application, the positions of each of the user interface elements indicating a responsive area on the touch-sensitive display where a gesture that meets the standard edge swipe gesture criteria may be initiated.

97. displaying the first user interface elements with respective appearances corresponding to whether edge protection is currently enabled for at least one of the first application and the second application while simultaneously displaying the first user interface of the first application and the second user interface of the second application; while simultaneously displaying the first user interface of the first application and the second user interface of the second application. displaying the first user interface element having a first appearance characteristic in accordance with a determination that at least one of the first application and the second application is currently associated with the extended edge swipe gesture criteria; and 97. The method of claim 96, further comprising: displaying the first user interface element having a second appearance characteristic that is different from the first appearance characteristic in accordance with a determination that neither the first application nor the second application is currently associated with the extended edge swipe gesture criteria.

98. while displaying, for at least one of the first application and the second application, the first user interface element having a respective appearance corresponding to whether edge protection is currently enabled, following a determination that at least one of the first application and the second application is associated with the extended edge swipe gesture criteria while displaying the first user interface element with the first appearance characteristic; 98. The method of claim 97, comprising, in response to detecting the first edge swipe gesture, replacing display of the first user interface element with the first user interface element having the first appearance characteristic and the first user interface element having the second appearance characteristic.

99. while displaying the first user interface element overlying at least a portion of the first application and at least a portion of the second application, detecting a request from the first application to stop displaying at least a portion of the first user interface element; 99. A method according to any one of claims 96 to 98, comprising ceasing to display at least a portion of the first user interface element on the first application and a portion of the first user interface element on the second application in response to receiving the request to cease displaying at least a portion of the first user interface element.

100. while displaying the first user interface element overlying at least a portion of the first application and at least a portion of the second application, detecting a request from the first application to stop displaying at least a portion of the first user interface element; in response to receiving the request to cease displaying the first user interface element; ceasing display of the first user interface element in response to a determination that a request to cease displaying at least a portion of the first user interface element has also been received from the second application; 99. A method according to any one of claims 96 to 98, comprising maintaining display of the first user interface element after the threshold amount of time in accordance with a determination that a request to cease displaying at least a portion of the first user interface element has not been received from the second application.

101. detecting a user input to resize the first application and the second application on the touch-sensitive display while displaying the first user interface element overlaying at least a portion of the first application and at least a portion of the second application; in response to detecting the user input resizing the first application and the second application on the touch-sensitive display, updating from a portion of a respective user interface of one of the first and second applications to a portion of a respective user interface of the other of the first and second applications; 101. The method of any one of claims 96 to 100, comprising maintaining a position of the first user interface element on the touch-sensitive display without regard to the updates to portions of content underlying the first user interface element.

102. 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: simultaneously displaying a first application and a second application on the touch-sensitive display, both of the first application and the second application being displayed along at least a portion of a respective edge of the touch-sensitive display; detect movement of a first edge swipe gesture at a respective location along the respective edge of the touch-sensitive display, including movement of a contact onto the touch-sensitive display from the respective location along the respective edge of the touch-sensitive display while simultaneously displaying the first application and the second application; In response to detecting the first edge swipe gesture, performing a system operation in accordance with determining that the respective positions of the first edge swipe gestures correspond to positions of the first application on the touch-sensitive display, determining that the first application is simultaneously associated with standard edge swipe gesture criteria, and determining that the first edge swipe gesture satisfies the standard edge swipe gesture criteria, the standard edge swipe gesture including a first set of one or more requirements that must be satisfied in order for the standard edge swipe gesture criteria to be satisfied, and 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; performing a system operation in accordance with determining that a respective position of the first edge swipe gesture corresponds to a position of a second application on the touch-sensitive display, determining that the second application is simultaneously associated with standard edge swipe gesture criteria, and determining that the first edge swipe gesture satisfies the standard edge swipe gesture criteria; in accordance with determining that the respective positions of the first edge swipe gesture correspond to a position of the first application on the touch-sensitive display, determining that the first application is simultaneously associated with extended edge swipe gesture criteria, and determining that the first edge swipe gesture satisfies the extended edge swipe gesture criteria, the extended edge swipe gesture including the 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, ceasing to perform the system operation; 11. The method of claim 10, further comprising: instructions for ceasing to perform the system operation in accordance with a determination that the respective position of the first edge swipe gesture corresponds to a position of the 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.

103. 1. A computer-readable storage medium having stored thereon one or more programs that, when executed by an electronic device having a touch-sensitive display, cause the device to: simultaneously displaying a first application and a second application on the touch-sensitive display, both of the first application and the second application being displayed along at least a portion of a respective edge of the touch-sensitive display; detect movement of a first edge swipe gesture at a respective location along the respective edge of the touch-sensitive display, including movement of a contact onto the touch-sensitive display from the respective location along the respective edge of the touch-sensitive display while simultaneously displaying the first application and the second application; In response to detecting the first edge swipe gesture, performing a system operation in accordance with determining that the respective positions of the first edge swipe gestures correspond to positions of the first application on the touch-sensitive display, determining that the first application is simultaneously associated with standard edge swipe gesture criteria, and determining that the first edge swipe gesture satisfies the standard edge swipe gesture criteria, the standard edge swipe gesture including a first set of one or more requirements that must be satisfied in order for the standard edge swipe gesture criteria to be satisfied, and 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; performing the system operation in accordance with a determination that the respective positions of the first edge swipe gesture correspond to a position of the second application on the touch-sensitive display, a determination that the second application is simultaneously associated with the standard edge swipe gesture criteria, and a determination that the first edge swipe gesture satisfies the standard edge swipe gesture criteria. in accordance with determining that the respective positions of the first edge swipe gesture correspond to a position of the first application on the touch-sensitive display, determining that the first application is simultaneously associated with extended edge swipe gesture criteria, and determining that the first edge swipe gesture satisfies the extended edge swipe gesture criteria, the extended edge swipe gesture including the 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, ceasing to perform the system operation; 11. A computer-readable storage medium comprising: instructions for causing a system to discontinue performing the system operation in accordance with a determination that the respective position of the first edge swipe gesture corresponds to a position of the 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.

104. 1. An electronic device comprising: A touch-sensitive display; means for simultaneously displaying a first application and a second application on the touch-sensitive display, the first application and the second application being simultaneously displayed on the first and second touch-sensitive displays, the first application and the second application both being displayed along at least a portion of a respective edge of the touch-sensitive display; means for detecting movement of a first edge swipe gesture at a respective location along the respective edge of the touch-sensitive display, the movement including movement of a contact onto the touch-sensitive display from the respective location along the respective edge of the touch-sensitive display while simultaneously displaying the first application and the second application; and means enabled in response to detecting the first edge swipe gesture, the means including: means for 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, the standard edge swipe gesture being enabled pursuant to a determination that the respective positions of the first edge swipe gesture correspond to a position of the first application on the touch-sensitive display, a determination that the first application is simultaneously associated with a standard edge swipe gesture criterion, and a determination that the first edge swipe gesture satisfies the standard edge swipe gesture criterion, the standard edge swipe gesture including a first set of one or more requirements that must be satisfied for the standard edge swipe gesture criterion to be satisfied; and means for performing the system operation in accordance with a determination that the respective positions of the first edge swipe gestures correspond to positions of the second application on the touch-sensitive display, a determination that the second application is simultaneously associated with the standard edge swipe gesture criteria, and a determination that the first edge swipe gesture satisfies the standard edge swipe gesture criteria; means for enabling the extended edge swipe gesture according to a determination that the respective positions of the first edge swipe gesture correspond to a position of the first application on the touch-sensitive display, a determination that the first application is simultaneously associated with extended edge swipe gesture criteria, and a determination that the first edge swipe gesture satisfies the extended edge swipe gesture criteria, the extended edge swipe gesture including the 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, and for ceasing to perform the system operation; and means for withdrawing from performing the system operation that is enabled in accordance with a determination that the respective position of the first edge swipe gesture corresponds to a position of the 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; 2. An electronic device comprising:

105. 1. An information processing apparatus for use in an electronic device having a touch-sensitive display, comprising: means for simultaneously displaying a first application and a second application on the touch-sensitive display, the first application and the second application being simultaneously displayed on the first and second touch-sensitive displays, the first application and the second application both being displayed along at least a portion of a respective edge of the touch-sensitive display; means for detecting movement of a first edge swipe gesture at a respective location along the respective edge of the touch-sensitive display, the movement including movement of a contact onto the touch-sensitive display from the respective location along the respective edge of the touch-sensitive display while simultaneously displaying the first application and the second application; and means enabled in response to detecting the first edge swipe gesture, the means including: means for 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, the standard edge swipe gesture being enabled pursuant to a determination that the respective positions of the first edge swipe gesture correspond to a position of the first application on the touch-sensitive display, a determination that the first application is simultaneously associated with a standard edge swipe gesture criterion, and a determination that the first edge swipe gesture satisfies the standard edge swipe gesture criterion, the standard edge swipe gesture including a first set of one or more requirements that must be satisfied for the standard edge swipe gesture criterion to be satisfied; and means for performing the system operation in accordance with a determination that the respective positions of the first edge swipe gestures correspond to positions of the second application on the touch-sensitive display, a determination that the second application is simultaneously associated with the standard edge swipe gesture criteria, and a determination that the first edge swipe gesture satisfies the standard edge swipe gesture criteria; means for enabling the extended edge swipe gesture according to a determination that the respective positions of the first edge swipe gesture correspond to a position of the first application on the touch-sensitive display, a determination that the first application is simultaneously associated with extended edge swipe gesture criteria, and a determination that the first edge swipe gesture satisfies the extended edge swipe gesture criteria, the extended edge swipe gesture including the 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, and for ceasing to perform the system operation; and means for withdrawing from performing the system operation that is enabled in accordance with a determination that the respective position of the first edge swipe gesture corresponds to a position of the 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; An information processing device comprising:

106. 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 containing instructions for performing a method according to any one of claims 87 to 101.

107. 102. A computer readable storage medium having stored thereon one or more programs comprising instructions that, when executed by an electronic device having a touch-sensitive display, cause the device to perform any one of the methods of claims 87 to 101.

108. A graphical user interface on an electronic device having a touch-sensitive display, a memory, and one or more processors executing one or more programs stored in the memory, the graphical user interface comprising a user interface displayed in accordance with any one of the methods of claims 87 to 101.

109. 1. An electronic device comprising: A touch-sensitive display; Means for carrying out any one of the methods according to claims 87 to 101, An electronic device comprising:

110. 1. An information processing apparatus for use in an electronic device having a touch-sensitive display, comprising: Means for carrying out any one of the methods according to claims 87 to 101, An information processing device comprising:

111. In an electronic device having a touch-sensitive display, simultaneously displaying on said 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 elements overlap with the first application without overlapping with the second application; a second application, wherein the appearance of the system user interface element is 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; Depending on the input detected, resizing the second application according to the input; pursuant to a determination that the system user interface element is overlaid with the second application without being overlaid with 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:

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

113. the first set of one or more behaviors includes requesting that the system user interface element be hidden when a predetermined criterion is met; The method of any one of claims 111 to 112, 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.

114. A method according to any one of claims 111 to 113, comprising: determining 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 response to detecting the input, in accordance with a determination that the system user interface element overlays the second application and the first application.

115. In response to detecting the input, pursuant to determining that the system user interface element overlays 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, determining an appearance of the system user interface element based on the first set of one or more behaviors associated with the system user interface element; A method according to any one of claims 111 to 114, comprising determining an 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 overlays 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 second set of one or more behaviors.

116. the first set of behaviors requires that an extended edge swipe gesture criterion be satisfied for an edge swipe gesture detected at a location occupied by the first application to perform the system action; the second set of behaviors requires that standard edge swipe gesture criteria be met for a detected edge swipe gesture at a location occupied by the first application to perform 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 is overlaid on the first application without being overlaid on the second application; displaying the system user interface element having the first appearance in accordance with determining that the system user interface element is overlaid with both the first application and the second application; 116. The method of any one of claims 111 to 115, comprising displaying the system user interface element having a second appearance in accordance with a determination that the system user interface element is overlaid on the second application without being overlaid on the first application.

117. the first set of behaviors requires that an extended edge swipe gesture criterion be satisfied for an edge swipe gesture detected at a location occupied by the first application to perform the system action; the second set of behaviors requires that standard edge swipe gesture criteria be met for a detected edge swipe gesture at a location occupied by the first application to perform 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 is overlaid on the first application without being overlaid on the second application; displaying the system user interface element having a second appearance in accordance with determining that the system user interface element is overlaid with both the first application and the second application; 116. The method of any one of claims 111 to 115, displaying the system user interface element having the second appearance in accordance with a determination that the system user interface element is overlaid on the second application without being overlaid on the first application.

118. the first set of one or more behaviors includes requesting 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 a 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 a predetermined criterion is met; In response to determining that the predetermined criteria is met for the first application, the method includes: reducing the visual distinction of the system user interface element relative to the remainder of the user interface displayed on the display in accordance with a determination that the system user interface element overlays the first application without overlapping the second application; reducing the visual distinction of the system user interface element relative to the remainder of the user interface displayed on the display in accordance with a determination that the system user interface element overlaps with both the first application and the second application; and 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 overlays the second application without overlapping the first application.

119. the first set of one or more behaviors includes requesting 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 a 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 a predetermined criterion is met; In response to determining that the predetermined criteria is met for the first application, the method includes: reducing the visual distinction of the system user interface element relative to the remainder of the user interface displayed on the display in accordance with a determination that the system user interface element overlays the first application without overlapping the second application; cease reducing the visual distinction of the system user interface element relative to the remainder of the user interface displayed on the display in accordance with a determination that the system user interface element overlays both the first application and the second application; and refraining from 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 overlays the second application without overlapping the first application.

120. the first application is associated with gesture criteria for an extended edge swipe gesture and detects an edge swipe input at a location corresponding to the system user interface element; 120. A method according to any one of claims 111 to 119, comprising in response to detecting the edge swipe input, changing an appearance of the system user interface element from a first appearance to a second user appearance.

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

122. A method according to any one of claims 111 to 121, wherein the appearance of the system user interface elements is influenced by the underlying content within the user interface.

123. A method according to any one of claims 111 to 122, wherein the system action is selected from a plurality of different system operations based on one or more parameters of the gesture.

124. 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: simultaneously displaying on said 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 elements overlap with the first application without overlapping with the second application; a second application, wherein the appearance of the system user interface element is 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; Depending on the input detected, resizing the second application according to the input; and in accordance with a determination that the system user interface element is overlaid with the second application without being overlaid with 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.

125. 1. A computer-readable storage medium having stored thereon one or more programs that, when executed by an electronic device having a touch-sensitive display, cause the device to: simultaneously displaying on said 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 elements overlap with the first application without overlapping with the second application; a second application, wherein the appearance of the system user interface element is 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; Depending on the input detected, resizing the second application according to the input; A computer-readable storage medium comprising instructions that, in accordance with a determination that the system user interface element is overlaid with the second application without being overlaid with the first application, cause the appearance of the system user interface element to be changed to an appearance based on the second set of one or more behaviors associated with the system user interface element.

126. 1. An electronic device comprising: A touch-sensitive display; simultaneously displaying on said 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 elements overlap with the first application without overlapping with the second application; a second application, wherein the appearance of the system user interface element is determined based on the first set of one or more behaviors; means for detecting an input corresponding to a request to resize the second application, the input being enabled while simultaneously displaying the first application, the second application, and the system user interface element; a means enabled in response to detecting said input, said means comprising: means for resizing the second application in accordance with the input; and means, enabled pursuant to a determination that the system user interface element overlays the second application without overlapping the first application, for changing an appearance of the system user interface element based on the second set of one or more behaviors associated with the system user interface element.

127. 1. An information processing apparatus for use in an electronic device having a touch-sensitive display, comprising: simultaneously displaying on said 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 elements overlap with the first application without overlapping with the second application; means for a second application, wherein an appearance of the system user interface element is determined based on the first set of one or more behaviors; means for detecting an input corresponding to a request to resize the second application, the input being enabled while simultaneously displaying the first application, the second application, and the system user interface element; a means enabled in response to detecting said input, said means comprising: means for resizing the second application in accordance with the input; and a means, enabled in accordance with a determination that the system user interface element overlays the second application without overlapping the first application, for changing an appearance of the system user interface element based on the second set of one or more behaviors associated with the system user interface element.

128. A touch-sensitive display; one or more processors; An electronic device comprising: a memory having stored therein 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 containing instructions for performing a method according to any one of claims 111 to 123.

129. 124. A computer-readable storage medium having stored thereon one or more programs, the one or more programs comprising instructions that, when executed by an electronic device having a touch-sensitive display, cause the device to perform any one of the methods of claims 111 to 123.

130. A graphical user interface on an electronic device having a touch-sensitive display, a memory, and one or more processors executing one or more programs stored in the memory, the graphical user interface comprising a user interface displayed in accordance with any one of the methods of claims 111 to 123.

131. 1. An electronic device comprising: A touch-sensitive display; Means for carrying out any one of the methods according to claims 111 to 123, An electronic device comprising:

132. 1. An information processing apparatus for use in an electronic device having a touch-sensitive display, comprising: Means for carrying out any one of the methods according to claims 111 to 123, An information processing device comprising:

Citation Information

Patent Citations

  • Information processor, operation input device, information processing system, information processing method, program and information storage medium

    JP2011221822A

  • Portable electronic devices and methods for controlling them

    JP2013529339A

  • Display device, and control method and control program for display device

    JP2014119914A

  • Multi-application environment

    JP2014519111A

  • Electronic device

    JP2016177560A