HK1235878B - Devices and methods for navigating between user interfaces - Google Patents

Description

Device and method for navigating between user interfaces

Technical Field

The present disclosure relates generally to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that detect input for navigating between user interfaces.

Background Art

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 touchpads and touch screen displays. Such surfaces are widely used to navigate between related and unrelated user interfaces (e.g., between user interfaces for different applications and/or within a hierarchy of user interfaces within a single application).

The exemplary user interface hierarchy includes related user interface groups for: organizing files and applications; storing and/or displaying digital images, editable documents (such as word processing, spreadsheets, and presentation documents) and/or non-editable documents (such as protected files and/or .pdf documents); recording and/or playing video and/or music; text-based communications (such as email, text, Twitter, and social networking); voice and/or video communications (such as phone calls and video conferencing); and web browsing. In some cases, a user will need to perform such user interface navigation within or between: a file management program (e.g., Finder from Apple Inc. of Cupertino, California); an image management application (e.g., Photos from Apple Inc. of Cupertino, California); a digital content (e.g., video and music) management application (e.g., iTunes from Apple Inc. of Cupertino, California); a drawing application; a presentation application (e.g., Keynote from Apple Inc. of Cupertino, California); a word processing application (e.g., Pages from Apple Inc. of Cupertino, California); or a spreadsheet application (e.g., Numbers from Apple Inc. of Cupertino, California).

However, the methods used to perform these navigations between related user interfaces in a user interface hierarchy and to animate the transitions between these related user interfaces are cumbersome and inefficient. Furthermore, these methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.

Additionally, abrupt transitions between different user interfaces can be distracting and irritating to the user, thereby reducing the user's efficiency and enjoyment in using the device.

Summary of the Invention

Thus, there is a need for electronic devices with faster, more efficient methods and interfaces for navigating between user interfaces. Such methods and interfaces optionally supplement or replace conventional methods for navigating between user interfaces. Such methods and interfaces reduce the number, extent, and/or nature of inputs from the user and produce a more efficient human-computer interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.

The disclosed device reduces or eliminates the above-mentioned defects and other problems associated with user interfaces for electronic devices with touch-sensitive surfaces. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a laptop, tablet, or handheld device). In some embodiments, the device is a personal electronic device (e.g., a wearable electronic device, such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a "touch screen" or "touch screen display"). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or instruction sets stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and/or finger contacts and gestures on the touch-sensitive surface. In some embodiments, these functions optionally include image editing, drawing, presentations, word processing, spreadsheet creation, playing games, making and receiving calls, video conferencing, sending and receiving emails, instant messaging, exercise support, digital photography, digital video recording, web browsing, digital music playback, memo recording, and/or digital video playback. Executable instructions for performing these functions are optionally included in a non-transient computer-readable storage medium or other computer program product configured for execution by one or more processors.

In accordance with some embodiments, a method is performed at an electronic device having a display and a touch-sensitive surface. The method includes: displaying a plurality of user interface representations in a stack on the display. At least a first user interface representation and a second user interface representation disposed above the first user interface representation in the stack are visible on the display. The second user interface representation is offset from the first user interface representation in a first direction. The second user interface representation partially exposes the first user interface representation. The method also includes detecting a first drag gesture by a first contact at a location on the touch-sensitive surface corresponding to a location of the first user interface representation on the display, the first contact moving across the touch-sensitive surface in a direction corresponding to the first direction on the display. The method also includes, while the first contact is at a location on the touch-sensitive surface corresponding to the location of the first user interface representation on the display and moving across the touch-sensitive surface in a direction corresponding to the first direction on the display: moving the first user interface representation in the first direction on the display at a first speed according to a speed of the first contact on the touch-sensitive surface; and moving the second user interface representation disposed above the first user interface representation in the first direction at a second speed greater than the first speed.

In accordance with some embodiments, a method is performed at an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contacts with the touch-sensitive surface. The method includes: displaying a first user interface on the display. The method also includes, while the first user interface is displayed on the display, detecting input via a first contact on the touch-sensitive surface. The method also includes, upon detecting the input via the first contact, displaying a first user interface representation and at least a second user interface representation on the display. The method also includes, while the first user interface representation and at least the second user interface representation are displayed on the display, detecting termination of the input via the first contact. In response to detecting termination of the input via the first contact: displaying a second user interface corresponding to the second user interface representation based on determining that the first contact had a characteristic intensity below a predetermined intensity threshold during the input and that the first contact moved in a direction across the touch-sensitive surface corresponding to a predefined direction on the display during the input; and redisplaying the first user interface based on determining that the first contact had a characteristic intensity below the predetermined intensity threshold during the input and that the first contact did not move in the direction across the touch-sensitive surface corresponding to the predefined direction on the display during the input.

In accordance with some embodiments, a method is performed at an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contacts with the touch-sensitive surface. The method includes displaying a first user interface on the display. The method also includes, while the first user interface is displayed on the display, detecting input from a first contact on the touch-sensitive surface that includes a period of increasing intensity of the first contact. The method also includes, in response to detecting the input from the first contact that includes a period of increasing intensity of the first contact, displaying a first user interface representation for the first user interface and a second user interface representation for a second user interface on the display, wherein the first user interface representation is displayed over the second user interface representation and partially exposes the second user interface representation. The method also includes, while the first user interface representation and the second user interface representation are displayed on the display, detecting that during the period of increasing intensity of the first contact, the intensity of the first contact satisfies one or more predetermined intensity criteria. The method also includes, in response to detecting that the intensity of the first contact satisfies the one or more predetermined intensity criteria, ceasing to display the first user interface representation and the second user interface representation on the display, and displaying the second user interface on the display.

In accordance with some embodiments, a method is performed at an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contact with the touch-sensitive surface. The method includes displaying a plurality of user interface representations in a stack on the display. At least a first user interface representation, a second user interface representation, and a third user interface representation are visible on the display. The first user interface representation is laterally offset from the second user interface representation in a first direction and partially exposes the second user interface representation. The second user interface representation is laterally offset from the third user interface representation in the first direction and partially exposes the third user interface representation. The method also includes detecting input via a first contact on the touch-sensitive surface at a location corresponding to the second user interface representation on the display. The method also includes increasing an area of the second user interface representation exposed behind the first user interface representation by increasing the lateral offset between the first and second user interface representations based on an increase in intensity of the first contact detected at a location corresponding to the second user interface representation on the display.

In accordance with some embodiments, a method is performed at an electronic device having a display and a touch-sensitive surface. The method includes: displaying a plurality of user interface representations in a stack on the display. At least a first user interface representation, a second user interface representation, and a third user interface representation are visible on the display. The second user interface representation is laterally offset from the first user interface representation in a first direction and partially exposes the first user interface representation. The third user interface representation is laterally offset from the second user interface representation in the first direction and partially exposes the second user interface representation. The method also includes detecting a drag gesture by a first contact moving across the touch-sensitive surface, wherein movement of the drag gesture by the first contact corresponds to movement across one or more of the user interface representations in the stack. The method also includes, during the drag gesture, revealing more of the first user interface representation from behind the second user interface representation on the display as the first contact moves over a location on the touch-sensitive surface that corresponds to the first user interface representation on the display.

In accordance with some embodiments, a method is performed at an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contact with the touch-sensitive surface. The method includes: displaying a first user interface of a first application on the display, the first user interface including a back navigation control. The method also includes, while displaying the first user interface of the first application on the display, detecting a gesture by a first contact on the touch-sensitive surface at a location corresponding to the back navigation control on the display. The method also includes, in response to detecting the gesture by the first contact on the touch-sensitive surface at the location corresponding to the back navigation control: replacing display of the first user interface of the first application with display of multiple user interface representations of the first application (including representations of the first user interface and representations of a second user interface) based on determining that the gesture by the first contact is a gesture with an intensity of the first contact that meets one or more predetermined intensity criteria; and replacing display of the first user interface of the first application with display of the second user interface of the first application based on determining that the gesture by the first contact is a gesture with an intensity of the first contact that does not meet one or more predetermined intensity criteria.

In accordance with some embodiments, a method is performed at an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contacts with the touch-sensitive surface. The method includes: displaying a user interface for an application on the display; detecting an edge input, including detecting a change in a characteristic intensity of a contact proximate an edge of the touch-sensitive surface; and in response to detecting the edge input: performing an application-independent operation based on determining that the edge input meets system gesture criteria, wherein: the system gesture criteria includes an intensity criteria; the system gesture criteria includes a location criteria that is met when the intensity criteria for the contact is met when the contact is within a first area relative to the touch-sensitive surface; and determining the first area relative to the touch-sensitive surface based on one or more characteristics of the contact.

In accordance with some embodiments, a method is performed at an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contacts with the touch-sensitive surface. The method includes: displaying a first view of a first application on a display; while displaying the first view, detecting a first portion of a first input, including detecting a first contact on a touch-sensitive surface; in response to detecting the first portion of the first input, based on determining that the first portion of the first input satisfies an application switching criterion, simultaneously displaying portions of multiple application views including a first application view and a second application view on the display; while simultaneously displaying portions of multiple application views, detecting a second portion of the first input including a lift-off of the first contact; and in response to detecting the second portion of the first input including a lift-off of the first contact: based on determining that the second portion of the first input satisfies a first view display criterion, stopping displaying a portion of the second application view on the display and displaying the first application view, wherein the first view display criterion includes a criterion that is satisfied when a lift-off of the first contact is detected in a first area of the touch-sensitive surface; and based on determining that the second portion of the first input satisfies a multi-view display criterion, after detecting the lift-off of the first contact, maintaining at least a portion of the first application view and at least a portion of the second application view displayed simultaneously on the display, wherein the multi-view display criterion includes a criterion that is satisfied when a lift-off of the first contact is detected in a second area of the touch-sensitive surface that is different from the first area of the touch-sensitive surface.

According to some embodiments, an electronic device includes: a display unit configured to display a user interface; a touch-sensitive surface unit for receiving a contact; and a processing unit coupled to the display unit and the touch-sensitive surface unit. The processing unit is configured to: enable display of a plurality of user interface representations in a stack on the display unit. At least a first user interface representation and a second user interface representation disposed above the first user interface representation in the stack are visible on the display unit. The second user interface representation is offset from the first user interface representation in a first direction. The second user interface representation partially exposes the first user interface representation. The processing unit is further configured to detect a first drag gesture involving a first contact at a location on the touch-sensitive surface unit corresponding to a location of the first user interface representation on the display unit, the first contact moving across the touch-sensitive surface unit in a direction corresponding to the first direction on the display unit. The processing unit is further configured, when the first contact is at a location on the touch-sensitive surface unit corresponding to a location of the first user interface representation on the display unit and moves across the touch-sensitive surface unit in a direction corresponding to the first direction on the display unit: move the first user interface representation in the first direction on the display unit at a first speed according to a speed of the first contact on the touch-sensitive surface unit; and move the second user interface representation disposed above the first user interface representation in the first direction at a second speed greater than the first speed.

According to some embodiments, an electronic device includes: a display unit configured to display a user interface; a touch-sensitive surface unit for receiving contacts; one or more sensor units for detecting the intensity of contacts with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: enable display of a first user interface on the display unit. The processing unit is further configured to detect input through a first contact on the touch-sensitive surface unit while the first user interface is displayed on the display unit. The processing unit is further configured to enable display of a first user interface representation and at least a second user interface representation on the display unit upon detecting the input through the first contact. The processing unit is further configured to detect termination of the input through the first contact while the first user interface representation and at least the second user interface representation are displayed on the display unit. The processing unit is also configured to, in response to detecting termination of input through the first contact: display a second user interface corresponding to the second user interface representation based on determining that the first contact had a characteristic intensity below a predetermined intensity threshold during the input and that the first contact moved in a direction across the touch-sensitive surface corresponding to a predefined direction on the display during the input; and redisplay the first user interface based on determining that the first contact had a characteristic intensity below a predetermined intensity threshold during the input and that the first contact did not move in a direction across the touch-sensitive surface corresponding to the predefined direction on the display during the input.

According to some embodiments, an electronic device includes: a display unit configured to display a user interface; a touch-sensitive surface unit for receiving contacts; one or more sensor units for detecting intensity of contacts with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable display of a first user interface on the display unit. The processing unit is further configured to, while displaying the first user interface on the display unit, detect input from a first contact on the touch-sensitive surface unit that includes a period of increasing intensity of the first contact. The processing unit is further configured to, in response to detecting input from the first contact that includes a period of increasing intensity of the first contact, enable display of a first user interface representation for the first user interface and a second user interface representation for a second user interface on the display unit, wherein the first user interface representation is displayed over and partially exposes the second user interface representation. The processing unit is further configured to, while displaying the first user interface representation and the second user interface representation on the display unit, detect that the intensity of the first contact during the period of increasing intensity of the first contact meets one or more predetermined intensity criteria. The processing unit is further configured to, in response to detecting that the intensity of the first contact satisfies one or more predetermined intensity criteria: cease enabling display of the first user interface representation and the second user interface representation on the display unit, and enable display of the second user interface on the display.

According to some embodiments, an electronic device includes: a display unit configured to display a user interface; a touch-sensitive surface unit for receiving contacts; one or more sensor units for detecting intensity of contacts with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable display of a plurality of user interface representations in a stack on the display unit. At least a first user interface representation, a second user interface representation, and a third user interface representation are visible on the display unit. The first user interface representation is laterally offset from the second user interface representation in a first direction and partially exposes the second user interface representation. The second user interface representation is laterally offset from the third user interface representation in the first direction and partially exposes the third user interface representation. The processing unit is further configured to detect input via a first contact at a location on the touch-sensitive surface unit corresponding to the second user interface representation on the display unit. The processing unit is further configured to increase the area of the second user interface representation exposed behind the first user interface representation by increasing the lateral offset between the first and second user interface representations based on an increase in intensity of the first contact detected at a location on the touch-sensitive surface unit corresponding to the second user interface representation on the display unit.

In accordance with some embodiments, an electronic device includes: a display unit configured to display a user interface; a touch-sensitive surface unit for receiving contacts; one or more sensor units for detecting intensity of contacts with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable display of a plurality of user interface representations in a stack on the display unit. At least a first user interface representation, a second user interface representation, and a third user interface representation are visible on the display unit. The second user interface representation is laterally offset from the first user interface representation in a first direction and partially exposes the first user interface representation. The third user interface representation is laterally offset from the second user interface representation in the first direction and partially exposes the second user interface representation. The processing unit is further configured to detect a drag gesture by a first contact moving across the touch-sensitive surface unit, wherein movement of the drag gesture by the first contact corresponds to movement across one or more user interface representations in the stack. The processing unit is further configured to, during the drag gesture, reveal more of the first user interface representation from behind the second user interface representation on the display unit when the first contact moves over a location on the touch-sensitive surface unit corresponding to the first user interface representation on the display unit.

According to some embodiments, an electronic device includes: a display unit configured to display a user interface; a touch-sensitive surface unit for receiving contacts; one or more sensor units for detecting the intensity of contacts with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: enable display of a first user interface of a first application on the display unit, the first user interface including a back navigation control. The processing unit is further configured to, while displaying the first user interface of the first application on the display unit, detect a gesture of a first contact on the touch-sensitive surface unit at a location corresponding to the back navigation control on the display unit. The processing unit is also configured to, in response to detecting a gesture of a first contact through the touch-sensitive surface unit at a position corresponding to the back navigation control: replace the display of the first user interface of the first application with the display of multiple user interface representations of the first application (including representations of the first user interface and representations of the second user interface) based on determining that the gesture of the first contact through the first contact is a gesture with an intensity of the first contact that meets one or more predetermined intensity standards; and replace the display of the first user interface of the first application with the display of the second user interface of the first application based on determining that the gesture of the first contact through the first contact is a gesture with an intensity of the first contact that does not meet one or more predetermined intensity standards.

In accordance with some embodiments, an electronic device includes a display, a touch-sensitive surface, optionally one or more sensors for detecting intensity of contacts with the touch-sensitive surface, one or more processors, a memory, and one or more programs; the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions for performing or causing the execution of any of the methods described herein. In accordance with some embodiments, a computer-readable storage medium has stored therein instructions that, when executed by an electronic device having a display, a touch-sensitive surface, and optionally one or more sensors for detecting intensity of contacts with the touch-sensitive surface, cause the device to perform or cause the execution of any of the methods described herein. In accordance with some embodiments, a graphical user interface on an electronic device having a display, a touch-sensitive surface, optionally one or more sensors for detecting intensity of contacts with the touch-sensitive surface, 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, the elements being 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-sensitive surface, and optionally one or more sensors for detecting intensity of contact with the touch-sensitive surface; and means for performing or causing the operation of any of the above methods to be performed. According to some embodiments, an information processing device for use in an electronic device having a display and a touch-sensitive surface, and optionally one or more sensors for detecting intensity of contact with the touch-sensitive surface, includes means for performing or causing the operation of any of the above methods to be performed.

In accordance with some embodiments, an electronic device includes: a display unit configured to display a content item; a touch-sensitive surface unit configured to receive user input; one or more sensor units configured to detect intensity of contact with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: enable displaying a user interface for an application on the display; detect edge input, including detecting a change in characteristic intensity of a contact adjacent to an edge of the touch-sensitive surface; and in response to detecting the edge input: perform an application-independent operation based on determining that the edge input satisfies system gesture criteria, wherein: the system gesture criteria include intensity criteria; the system gesture criteria include location criteria that are satisfied when the intensity criteria for the contact are satisfied when the contact is within a first area relative to the touch-sensitive surface; and determining the first area relative to the touch-sensitive surface unit based on one or more characteristics of the contact.

According to some embodiments, an electronic device includes: a display unit configured to display a content item; a touch-sensitive surface unit configured to receive user input; one or more sensor units configured to detect the intensity of contact with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit and the one or more sensor units. The processing unit is configured to: implement displaying a first view of a first application on a display; when implementing displaying the first view, detect a first part of a first input, including detecting a first contact on a touch-sensitive surface; in response to detecting the first part of the first input, based on determining that the first part of the first input satisfies an application switching criterion, implement displaying portions of multiple application views including a first application view and a second application view on the display at the same time; when implementing displaying portions of multiple application views at the same time, detect a second part of the first input including a lift-off of the first contact; and in response to detecting the second part of the first input including a lift-off of the first contact: based on determining that the second part of the first input satisfies a first view display criterion, stop implementing displaying portions of the second application view and implement displaying the first application view on the display, wherein the first view display criterion includes a criterion that is satisfied when a lift-off of the first contact is detected in a first area of the touch-sensitive surface; and based on determining that the second part of the first input satisfies a multi-view display criterion, after detecting the lift-off of the first contact, maintain displaying at least a portion of the first application view and at least a portion of the second application view on the display at the same time, wherein the multi-view display criterion includes a criterion that is satisfied when a lift-off of the first contact is detected in a second area of the touch-sensitive surface that is different from the first area of the touch-sensitive surface.

Thus, an electronic device having a display, a touch-sensitive surface, and optionally one or more sensors for detecting intensity of contact with the touch-sensitive surface is provided with a faster and more efficient method and interface for navigating between user interfaces, thereby increasing the effectiveness, efficiency, and user satisfaction with such a device. Such a method and interface can supplement or replace conventional methods for navigating between user interfaces.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments of the present invention, reference should be made to the following description of the embodiments taken in conjunction with the following drawings, in which like reference numerals designate corresponding parts throughout the several views.

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

FIG. 1B is a block diagram illustrating exemplary components for event processing according to some embodiments.

FIG2 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.

3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.

4A illustrates an exemplary user interface for an applications menu on a portable multifunction device in accordance with some embodiments.

4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments.

4C-4E illustrate example dynamic intensity thresholds in accordance with some embodiments.

5A-5HH illustrate exemplary user interfaces for navigating between user interface representations in a user interface selection mode in accordance with some embodiments.

6A-6V illustrate exemplary user interfaces for navigating between a displayed user interface and a previously displayed user interface in accordance with some embodiments.

7A-7O illustrate exemplary user interfaces for navigating between a displayed user interface and a user interface immediately preceding the displayed user interface in accordance with some embodiments.

8A-8R illustrate exemplary user interfaces for navigating between user interface representations in a user interface selection mode in accordance with some embodiments.

9A-9H illustrate exemplary user interfaces for navigating between user interface representations in a user interface selection mode in accordance with some embodiments.

10A-10H are flow diagrams illustrating a method of navigating between user interface representations in a user interface selection mode in accordance with some embodiments.

11A-11E are flow diagrams illustrating a method of navigating between a displayed user interface and a previously displayed user interface in accordance with some embodiments.

12A-12E are flow diagrams illustrating methods of navigating between a displayed user interface and a user interface immediately preceding the displayed user interface in accordance with some embodiments.

13A-13D are flow diagrams illustrating methods of navigating between user interface representations in a user interface selection mode in accordance with some embodiments.

14A-14C are flow diagrams illustrating methods of navigating between user interface representations in a user interface selection mode in accordance with some embodiments.

15 is a flow diagram illustrating a method of navigating between user interfaces in a user interface hierarchy for an application in accordance with some embodiments.

16-21 are functional block diagrams of electronic devices according to some embodiments.

Figures 22A-22BA illustrate exemplary user interfaces for invoking a user interface selection mode and for navigating between user interfaces in an application in accordance with some embodiments.

23A-23T illustrate exemplary user interfaces for invoking a user interface selection mode and for navigating between user interfaces in an application in accordance with some embodiments.

24A-24F are flow diagrams illustrating methods of invoking a user interface selection mode and for navigating between user interfaces in an application in accordance with some embodiments.

Figures 25A-25H are flow diagrams illustrating methods of invoking a user interface selection mode and for navigating between user interfaces in an application in accordance with some embodiments.

26-27 are functional block diagrams of electronic devices according to some embodiments.

DETAILED DESCRIPTION

Many electronic devices have graphical user interfaces for multiple different applications. Users generally need to access multiple different applications in succession. It is more efficient to maintain an application in an active state (e.g., open) when working in this way, because opening and closing the same application multiple times a day is time-consuming and laborious. However, when multiple applications are opened simultaneously on an electronic device, it may be equally difficult to navigate through the open applications to identify and activate the display of the desired application. Similarly, navigating through a hierarchical structure with a large number of items (e.g., files, emails, previously displayed web pages, etc.) is cumbersome. The present disclosure improves this process by providing efficient and intuitive devices, methods, and user interfaces for navigating through active applications and representations of complex hierarchical structures. In some embodiments, improvement is achieved by providing a method for navigating through a large number of items with fewer and smaller user inputs. In some embodiments, improvement is achieved by incorporating a heuristic based on the intensity difference of the sensed contact, which does not require the user to make multiple user inputs or even lift the contact off the touch-sensitive surface to make a selection.

Below, Figures 1A-1B, 2, and 3 provide a description of an exemplary device. Figures 4A-4B, 5A-5HH, 6A-6V, 7A-7O, 8A-8R, 9A-9H, 22A-22BA, and 23A-23T illustrate exemplary user interfaces for navigating between user interfaces. Figures 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, 15, 24A-24F, and 25A-25H are flow diagrams of methods for navigating between user interface representations. The user interfaces in Figures 5A-5HH, 6A-6V, 7A-70, 8A-8R, 9A-9H, 22A-22BA, and 23A-23T are used to illustrate the processes in Figures 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, 15, 24A-24F, and 25A-25H.

Exemplary devices

Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are provided to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other cases, well-known methods, processes, components, circuits, and networks are not described in detail so as not to unnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms "first," "second," etc., are used herein in some embodiments to describe various elements, these elements should not be limited by these terms. These terms are simply used to distinguish one element from another. For example, a first contact can be named a second contact, and similarly, a second contact can be named a first contact without departing from the scope of the various described embodiments. Both a first contact and a second contact are contacts, but they are not the same contact unless the context clearly indicates otherwise.

The terms used in the description of the various described embodiments herein are only for the purpose of describing specific embodiments and are not intended to be limiting. As used in the description of the various described embodiments and in the appended claims, the singular forms "a", "an", and "the" are intended to also include the plural forms, unless the context clearly indicates otherwise. It will also be understood that the terms "and/or" used herein refer to and encompass any and all possible combinations of one or more items in the items listed in association. It will also be understood that the terms "comprises" and/or "comprising" when used in this specification specify the presence of stated features, integers, steps, operations, elements, and/or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts, and/or their groupings.

As used herein, the term “if” is alternatively interpreted to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined that…” or “if [stated condition or event] is detected” is alternatively interpreted to mean “upon determining…” or “in response to determining…” or “upon detecting [stated condition or event]” or “in response to detecting [stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPod and devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptop computers or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads), may alternatively be used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer with a touch-sensitive surface (e.g., touch screen displays and/or touch pads).

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

The device typically supports a variety of applications, such as one or more of the following: a memo-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 phone application, a video conferencing application, an email application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

Various applications executing 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 and corresponding information displayed on the device optionally adjust and/or change from one application to the next and/or within the corresponding application. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and clear to the user.

Attention is now directed to embodiments of portable devices with touch-sensitive displays. FIG1A is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display system 112 is sometimes referred to as a "touch screen" for convenience, and sometimes simply as a touch-sensitive display. Device 100 includes memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripherals interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input/output (I/O) subsystem 106, other input or control devices 116, and external ports 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more intensity sensors 165 for detecting the intensity of contacts on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

As used in this specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of a device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of gravity of the device that will be detected by a user through the user's sense of touch. For example, when a device or a component of the device is in contact with a surface that is touch-sensitive to a user (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation that corresponds to a perceived change in a physical property of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) may optionally be interpreted by the user as a "press click" or "lift click" of a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "lift click," even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement does not move. As another example, movement of a touch-sensitive surface may be interpreted or sensed by a user as "roughness" of the touch-sensitive surface, even when the smoothness of the touch-sensitive surface does not change. While such interpretation of touch by a user will be limited by the user's individual sensory perceptions, there are many sensory perceptions of touch that are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "lift-click," "press-click," "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or a component thereof that would generate the described sensory perception for a typical (or average) user.

It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 may optionally have more or fewer components than shown, may optionally combine two or more components, or may alternatively have a different configuration or arrangement of the components. The various components shown in FIG1A are implemented in hardware, software, firmware, or a combination thereof, including one or more signal processing and/or application specific integrated circuits.

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

The peripherals interface 118 may be used to couple the device's input and output peripherals to the CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or instruction sets stored in the memory 102 to perform various functions of the device 100 and process data.

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

RF (Radio Frequency) circuitry 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuitry 108 converts electrical signals into/from electromagnetic signals and communicates with a communication network and other communication devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a subscriber identity module (SIM) card, memory, and the like. RF circuitry 108 optionally communicates with a network and other devices via wireless communications, such as the Internet (also known as the World Wide Web (WWW)), an intranet, and/or a wireless network (such as a cellular telephone network, a wireless local area network (LAN), and/or a metropolitan area network (MAN)). Wireless communication may optionally use any of a variety of communication standards, protocols, and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolution, Data Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g, and/or IEEE 802.11d). 802.11n), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (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 Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols that have not yet been developed as of the filing date of this document.

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 the audio data into electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electrical signals into sound waves audible to the human ear. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals into audio data and transmits the audio data to the peripheral device interface 118 for processing. The audio data is optionally retrieved from and/or transmitted to the memory 102 and/or the RF circuit 108 by the peripheral device interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., 212 in FIG. 2 ). The headset jack provides an interface between the audio circuit 110 and a removable audio input/output peripheral device, such as an output-only headset or a headset with both output (e.g., a single-ear or dual-ear headset) and input (e.g., a microphone).

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

The touch-sensitive 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 the touch-sensitive display system 112 and/or sends electrical signals to the touch-sensitive display system 112. The touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, 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 graphical user interface object (e.g., a graphical user interface object configured to respond to input directed to a graphical user interface object). Examples of user-interactive graphical user interface objects include, but are not limited to, buttons, sliders, icons, selectable menu items, switches, hyperlinks, or other user interface controls.

The touch-sensitive display system 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on tactile and/or haptic contact. The touch-sensitive display system 112 and the display controller 156 (together with any associated modules and/or instruction sets in the memory 102) detect contact (and any movement or interruption of that contact) on the touch-sensitive display system 112 and convert the detected contact into interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch-sensitive display system 112. In an exemplary embodiment, the point of contact between the touch-sensitive display system 112 and the user corresponds to the user's finger or stylus.

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

The touch-sensitive display system 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touch screen video resolution exceeds 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally uses any suitable object or appendage, such as a stylus, finger, or the like, to contact the touch-sensitive display system 112. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of a finger on the touch screen. In some embodiments, the device translates rough finger-based input into precise pointer/cursor positions or commands to perform the user's desired action.

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

Device 100 also includes a power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power fault detection circuitry, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.

The device 100 optionally also includes one or more optical sensors 164. Figure 1A shows an optical sensor coupled to the optical sensor controller 158 in the I/O subsystem 106. The optical sensor 164 optionally includes a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected from the environment through one or more lenses and converts the light into data representing an image. In conjunction with the imaging module 143 (also called a camera module), the optical sensor 164 optionally captures still images and/or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite the touch-sensitive display system 112 on the front of the device, so that the touch screen can be used as a viewfinder for still image and/or video image acquisition. In some embodiments, another optical sensor is located on the front of the device so that the image of the user is obtained (e.g., for self-portraits, for video conferencing when the user views other video conference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact force sensors 165. FIG1A shows a contact force sensor coupled to force sensor controller 159 in I/O subsystem 106. Contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of a contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the back of device 100, opposite touch-sensitive display system 112, which is located on the front of device 100.

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

Device 100 optionally also includes one or more tactile output generators 167. FIG1A shows a tactile output generator coupled to tactile feedback controller 161 in I/O subsystem 106. Tactile output generator 167 optionally includes: one or more electroacoustic devices, such as speakers or other audio components; and/or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile outputs on the device). Tactile output generator 167 receives tactile feedback generation instructions from tactile feedback module 133 and generates tactile outputs on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112), and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., inward/outward toward the surface of device 100) or laterally (e.g., front to back in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch-sensitive display system 112, which is located on the front of device 100.

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

In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact/motion module (or instruction set) 130, a graphics module (or instruction set) 132, a haptic feedback module (or instruction set) 133, a text input module (or instruction set) 134, a global positioning system (GPS) module (or instruction set) 135, and applications (or instruction sets) 136. In addition, in some embodiments, memory 102 stores a device/global internal state 157, as shown in Figures 1A and 3. The device/global internal state 157 includes one or more of the following: an active application state, indicating which applications (if any) are currently active; a display state, indicating what applications, views, or other information occupy various areas of the touch-sensitive display system 112; a sensor state, including information obtained from various sensors and other input or control devices 116 of the device; and position and/or location information regarding the position and/or posture of the device.

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

The communication module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by the RF circuitry 108 and/or the external ports 124. The external port 124 (e.g., a Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices or indirectly via a network (e.g., the Internet, a wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, similar to, and/or compatible with the 30-pin connector used on some iPods and devices by Apple Inc. of Cupertino, California. In some embodiments, the external port is a Lightning connector that is the same as, similar to, and/or compatible with the Lightning connector used on some iPods and devices by Apple Inc. of Cupertino, California.

The contact/motion module 130 optionally detects contact with the touch-sensitive display system 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact/motion module 130 includes various software components for performing various operations related to the detection of contact (e.g., by a finger or by 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 a surrogate for the force or pressure of the contact), determining whether there has been movement of the contact and tracking that movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has ceased (e.g., detecting a finger up event or contact break). The contact/motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of a contact point represented by a series of contact data optionally includes determining the rate (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 (eg, one finger contact or stylus contact) or to multiple simultaneous contacts (eg, "multi-touch"/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contacts on a touchpad.

The contact/motion module 130 optionally detects gesture input from a user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of the detected contacts). Thus, gestures are optionally detected by detecting specific contact patterns. For example, detecting a single-finger tap gesture includes detecting a finger press event and then detecting a finger lift (lift-off) event at the same location (or substantially the same location) as the finger press event (e.g., at an icon location). As another example, detecting a finger swipe gesture on a touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and then detecting a finger lift (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.

The graphics module 132 includes various known software components for rendering and displaying graphics on the touch-sensitive display system 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including, but not limited to, text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, and the like.

In some embodiments, the graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes specifying the graphics to be displayed from an application, etc., along with coordinate data and other graphic attribute data, if necessary, and then generates screen image data for output to the display controller 156.

Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator 167 to produce tactile output at one or more locations on device 100 in response to user interaction with device 100 .

The text input module 134, which is optionally a component of the graphics module 132, provides a soft keyboard for entering text in various applications (eg, contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).

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 dialing, to the camera 143 as photo/video metadata, and to applications that provide location-based services, such as the weather widget, the local yellow pages widget, and the map/navigation widget).

Application 136 may optionally include the following modules (or instruction sets) or a subset or superset thereof:

Contacts module 137 (sometimes called address book or contact list);

Telephone module 138;

Video conferencing module 139;

Email client module 140;

Instant messaging (IM) module 141;

Exercise support module 142;

A camera module 143 for still and/or video images;

Image management module 144;

Browser module 147;

Calendar module 148;

A widget module 149, which optionally includes one or more of the following: a weather widget 149-1, a stock widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, other widgets acquired by the user, and a widget 149-6 created by the user;

A widget creator module 150 for forming user-created widgets 149-6;

Search module 151;

Video and music player module 152, optionally composed of a video player module and a music player module;

Memo module 153;

Map module 154; and/or

Online video module 155.

Examples of other applications 136 that may optionally be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

In conjunction with the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, and the text input module 134, the contacts module 137 includes executable instructions for managing an address book or contact list (e.g., stored in the application internal state 192 of the contacts module 137 in memory 102 or memory 370), including: adding one or more names to the address book; deleting one or more names from the address book; associating one or more phone numbers, email addresses, physical addresses, or other information with a name; associating an image with a name; categorizing and sorting names; providing phone numbers and/or email addresses to initiate and/or facilitate telephone 138 communications, video conference 139, email 140, or IM 141; and so on.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, phone module 138 includes executable instructions for entering a character sequence corresponding to a phone number, accessing one or more phone numbers in address book 137, modifying an already entered phone number, dialing the corresponding phone number, conducting a conversation, and disconnecting or hanging up when the conversation is complete. As described above, wireless communication may optionally use any of a variety of communication standards, protocols, and technologies.

In combination with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and phone module 138, video conferencing module 139 includes executable instructions for initiating, conducting, and terminating a video conference between a user and one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with image management module 144, email client module 140 makes it very easy to create and send emails with still images or video images captured by camera module 143.

In conjunction with the RF circuitry 108, the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, and the text input module 134, the instant messaging module 141 includes executable instructions for entering a character sequence corresponding to an instant message, modifying previously entered characters, transmitting the corresponding instant message (e.g., using the Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for phone-based instant messaging or using XMPP, SIMPLE, Apple Push Notification Service (APNs), or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and/or received instant messages may optionally include graphics, photos, audio files, video files, and/or other attachments supported in MMS and/or Enhanced Messaging Service (EMS). As used herein, "instant messaging" 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).

In combination with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 145, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burn goals); communicate with workout sensors (in sports equipment and smart watches); receive workout sensor data; calibrate sensors for monitoring a workout; select and play music for a workout; and display, store, and send workout data.

In conjunction with touch-sensitive display system 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions for capturing still images or videos (including video streams) and storing them in memory 102, modifying characteristics of still images or videos, and/or deleting still images or videos from memory 102.

In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and/or video images.

In combination with the RF circuit 108, the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with user instructions (including searching for, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages).

In combination with the RF circuit 108, the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, the text input module 134, the email client module 140, and the browser module 147, the calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with the calendars (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

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

In combination with the RF circuit 108, the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, the text input module 134 and the browser module 147, the desktop widget creator module 150 includes executable instructions for creating a desktop widget (e.g., transferring a user-specified portion of a web page into a desktop widget).

In combination with the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, and the text input module 134, the search module 151 includes executable instructions for searching the memory 102 for text, music, sound, images, videos, and/or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and play back recorded music and other sound files stored in one or more file formats (such as MP3 or AAC files), as well as executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch-sensitive display system 112 or on an external display connected wirelessly or via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

In conjunction with the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, and the text input module 134, the memo module 153 includes executable instructions for creating and managing memos, to-do lists, etc. according to user instructions.

In combination with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions for receiving, displaying, modifying, and storing maps and data associated with the maps (e.g., driving directions; data about stores or other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes executable instructions that allow a user to access, browse, receive (e.g., by streaming and/or downloading), play back (e.g., on touch screen 112 or an external display connected wirelessly or via external port 124), send an email with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than email client module 140, is used to send a link to a particular online video.

Each module and application in the modules indicated above corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., computer-implemented methods and other information processing methods described herein). These modules (i.e., instruction sets) do not have to be implemented as separate software programs, processes, or modules, so various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores subsets of the above modules and data structures. In addition, memory 102 optionally stores additional modules and data structures not described above.

In some embodiments, device 100 is a device in which operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using the touch screen and/or the touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, etc.) on device 100 is optionally reduced.

The predefined set of functions that are exclusively performed via the touch screen and/or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 from any user interface displayed on the device 100 to a main menu, home menu, or root menu. In such embodiments, the touchpad is used to implement a "menu button." In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.

FIG1B is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 (in FIG1A ) or memory 370 (in FIG3 ) includes an event classifier 170 (e.g., in operating system 126 ) and a corresponding application 136 - 1 (e.g., any of the aforementioned applications 136 , 137 , 155 , 380 - 390 ).

Event classifier 170 receives event information and determines the application 136-1 and the application view 191 of application 136-1 to which the event information is to be delivered. Event classifier 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192 that indicates the current application view displayed on touch-sensitive display system 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event classifier 170 to determine which application(s) is currently active, and application internal state 192 is used by event classifier 170 to determine the application view 191 to which the event information is to be delivered.

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

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

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

In some embodiments, event classifier 170 also includes a click hit determination module 172 and/or an activation event recognizer determination module 173 .

When the touch-sensitive display system 112 displays more than one view, the hit view determination module 172 provides software procedures for determining where a sub-event has occurred within one or more views. A view consists of controls and other elements that a user can see on the display.

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

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

Activation event recognizer determination module 173 determines which views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, activation event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, activation event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with a particular view, views higher in the hierarchy will still remain actively participating views.

Event dispatcher module 174 dispatches event information to an event recognizer (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores the event information in an event queue, which is retrieved by corresponding event receiver module 182.

In some embodiments, operating system 126 includes event classifier 170. Alternatively, application 136-1 includes event classifier 170. In other embodiments, event classifier 170 is a standalone module or part of another module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 is part of a separate module, such as a user interface toolkit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, a corresponding event handler 190 includes one or more of: a data updater 176, an object updater 177, a GUI updater 178, and/or event data received from event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more application views in application view 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of the data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

A corresponding event identifier 180 receives event information (e.g., event data 179) from event classifier 170 and identifies an event from the event information. Event identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event identifier 180 also includes at least a subset of the following: metadata 183 and event delivery instructions 188 (which optionally include sub-event delivery instructions).

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

Event comparator 184 compares event information with predefined event or sub-event definitions and, based on the comparison result, determines the event or sub-event, or determines or updates the state of the event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 includes event definitions (e.g., predefined sub-event sequences), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in event 187 include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, event 1 (187-1) is defined as a double-click on a displayed object. For example, the double-click includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on the displayed object, and a second lift (touch end) of a predetermined duration. In another example, event 2 (187-2) is defined as a drag on a displayed object. For example, the drag includes a touch (or contact) of a predetermined duration on the displayed object, movement of the touch on the touch-sensitive display system 112, and a lift-off (touch end) of the touch. In some embodiments, the event also includes information for one or more associated event handlers 190.

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

In some embodiments, the definition of the corresponding event 187 also includes a delay action that delays the delivery of the event information until after it has been determined whether the sequence of sub-events does correspond to the event type of the event identifier.

After it disregards subsequent sub-events of a touch-based gesture, the corresponding event recognizer 180 enters the event not possible, event failed, or event ended state when it determines that the sub-event string does not match any event in event definitions 186. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

In some embodiments, corresponding event recognizers 180 include metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery for actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact or can interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in a view or programmatic hierarchy.

In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the corresponding event recognizer 180 delivers event information associated with the event to event handler 190. Activating event handler 190 is distinct from sending (and deferred sending) the sub-events to the corresponding hit view. In some embodiments, event recognizer 180 throws a flag associated with the identified event, and event handler 190 associated with the flag receives the flag and performs predefined processing.

In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with the sub-event string or to an actively participating view. The event handler associated with the sub-event string or the actively participating view receives the event information and performs predetermined processing.

In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates phone numbers used in contact module 137 or stores video files used in video player module 145. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user interface object or updates the position of a user interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on a touch-sensitive display.

In some embodiments, one or more event handlers 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

It should be understood that the above discussion of event handling for user touches on a touch-sensitive display is also applicable to other forms of user input for operating the multifunction device 100 using input devices, and not all user inputs are initiated on the touch screen. For example, mouse movement and mouse button presses, optionally in combination with single or multiple keyboard presses or holds; contact movement on a touchpad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; spoken commands; detected eye movement; biometric input; and/or any combination thereof, may be used as input corresponding to a sub-event to define an event to be recognized.

Figure 2 illustrates a portable multifunction device 100 with a touchscreen (e.g., touch-sensitive display system 112 in Figure 1A ), according to some embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment, as well as other embodiments described below, a user can select one or more of these graphics by making gestures on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figures) or with one or more styluses 203 (not drawn to scale in the figures). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, from right to left, upward, and/or downward), and/or a rolling motion (from right to left, from left to right, upward, and/or downward) of a finger that has made contact with the device 100. In some implementations or in some circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture over an application icon may not select the corresponding application when the gesture corresponding to selection is a tap.

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

In some embodiments, device 100 includes a touchscreen display, a menu button 204, a push button 206 for powering the device on and off, and locking the device, a subscriber identity module (SIM) card slot 210, a headset jack 212, a docking/charging external port 124, and one or more volume adjustment buttons 208. Push button 206 is optionally used to power the device on and off by pressing and holding the button for a predefined time interval; to lock the device by pressing and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In some embodiments, device 100 also accepts voice input for activating or deactivating certain functions via microphone 113. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contact on touch-sensitive display system 112, and/or one or more tactile output generators 167 for generating tactile output for a user of device 100.

Fig. 3 is a block diagram of an exemplary multifunctional device with a display and a touch-sensitive surface according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system or a 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, a memory 370 and one or more communication buses 320 for interconnecting these components. Communication bus 320 optionally includes a circuit (sometimes called a chipset) that interconnects system components and controls the communication between system components. Device 300 includes an input/output (I/O) interface 330, which includes a display 340, which is typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on device 300 (e.g., similar to tactile output generator 167 described above with reference to FIG1A ), and a sensor 359 (e.g., an optical sensor, an acceleration sensor, a proximity sensor, a touch-sensitive sensor, and/or a contact force sensor similar to contact force sensor 165 described above with reference to FIG1A ). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to those stored in memory 102 of portable multifunction device 100 ( FIG1A ), or a subset thereof. Furthermore, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores 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 memory 102 of portable multifunction device 100 ( FIG. 1A ) optionally does not store these modules.

Each element in the above-mentioned identified element among Fig. 3 is optionally stored in one or more previously mentioned memory devices.Each module in the above-mentioned identified module corresponds to a group of instructions for performing the functions mentioned above.The above-mentioned identified module or program (that is, instruction set) need not be implemented as independent software program, process or module, and therefore the various subgroups of these modules are optionally combined or otherwise rearranged in various embodiments.In certain embodiments, memory 370 stores the subgroup of above-mentioned modules and data structure optionally.In addition, memory 370 stores other modules and data structure not described above optionally.

Attention is now turned to an embodiment of a user interface (“UI”) that may optionally be implemented on portable multifunction device 100 .

Figure 4A shows an exemplary user interface for an application menu on portable multifunction device 100 according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

Signal strength indicators 402 for wireless communications (such as cellular and Wi-Fi signals);

Time 404;

Bluetooth indicator 405;

Battery status indicator 406;

A tray 408 with commonly used application icons, such as:

o An icon 416 labeled "Phone" for the phone module 138, the icon 416 optionally including an indicator 414 of the number of missed calls or voice messages;

o An icon 418 labeled "Mail" of the email client module 140, the icon 418 optionally including an indicator 410 of the number of unread emails;

o An icon 420 labeled "Browser" of the browser module 147; and

o An icon 422 labeled "iPod" for the video and music player module 152 (also called the iPod (trademark of Apple Inc.) module 152); and

Icons of other applications, such as:

o An icon 424 labeled "Message" of the IM module 141;

o An icon 426 labeled "Calendar" of the calendar module 148;

o Icon 428 labeled "Photos" of the image management module 144;

o An icon 430 labeled “Camera” of the camera module 143;

o Icon 432 of the online video module 155 labeled "Online Video";

○ The icon 434 labeled “Stocks” of the Stocks desktop applet 149-2;

o An icon 436 labeled “Map” of the map module 154;

○ Icon 438 labeled “Weather” of the weather widget 149-1;

○ Icon 440 labeled “Clock” of the alarm clock widget 149-4;

o Icon 442 of the exercise support module 142 labeled "Exercise Support";

o An icon 444 of the memo module 153 labeled "Memo"; and

o An icon 446 for a settings application or module that provides access to settings for the device 100 and its various applications 136 .

It should be noted that the icon labels shown in FIG4A are merely exemplary. For example, in some embodiments, icon 422 of video and music player module 152 is labeled "Music" or "Music Player." Other labels may optionally be used for various application icons. In some embodiments, the label of a corresponding application icon includes the name of the application corresponding to the corresponding application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

4B shows an exemplary user interface on a device (e.g., device 300 in FIG. 3 ) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355 in FIG. 3 ) that is separate from display 450. Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 357 ) for detecting intensity of contacts on touch-sensitive surface 451 and/or one or more tactile output generators 359 for generating tactile output for a user of device 300.

Figure 4B illustrates an exemplary user interface on a device (e.g., device 300 in Figure 3 ) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355 in Figure 3 ) that is separate from display 450. While many of the following examples will be presented with reference to input on touchscreen display 112 (where the touch-sensitive surface and display are combined), in some embodiments, as shown in Figure 4B , the device detects input on a touch-sensitive surface that is separate from the display. In some embodiments, the touch-sensitive surface (e.g., 451 in Figure 4B ) has a primary axis (e.g., 452 in Figure 4B ) that corresponds to a primary axis (e.g., 453 in Figure 4B ) on the display (e.g., 450). In accordance with these embodiments, the device detects contact (e.g., 460 and 462 in Figure 4B ) with touch-sensitive surface 451 at locations corresponding to corresponding locations on the display (e.g., 460 corresponds to 468 and 462 corresponds to 470 in Figure 4B ). Thus, when the touch-sensitive surface (e.g., 451 in FIG. 4B ) is separated from the display (450 in FIG. 4B ) of the multifunction device, user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

In addition, although the following examples are primarily given with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures, etc.), it should be understood that in some embodiments, one or more of these finger inputs are replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of contact) followed by movement of a cursor along the path of the swipe gesture (e.g., instead of movement of the contact). For another example, a tap gesture is optionally replaced by a mouse click when the cursor is over the location of the tap gesture (e.g., instead of detection of contact followed by termination of detecting contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or one mouse and multiple finger contacts are optionally used simultaneously.

As used herein, the term "focus selector" refers to an input element that indicates the current portion of a user interface with which a user is interacting. In some embodiments that include a cursor or other position marker, the cursor acts as a "focus selector" such that when input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B ) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted based on the detected input. In some embodiments that include a touch screen display (e.g., 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 acts as a "focus selector" such that when input (e.g., a press input by a 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 based on the detected input. In some implementations, focus moves from one area of a user interface to another area of the user interface without corresponding movement of a cursor or movement of a contact on a touchscreen display (e.g., by using a tab key or arrow keys to move focus from one button to another); in these implementations, a focus selector moves in accordance with the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user intends to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device's display).

As used in this specification and in the claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact or a stylus contact) on the touch-sensitive surface, or to a surrogate (surrogate) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at various points on the touch-sensitive surface. In some embodiments, the force measurements from multiple force sensors are combined (e.g., weighted average or sum) to determine an estimated force of the contact. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or its change, the capacitance of the touch-sensitive surface adjacent to the contact and/or its change, and/or the resistance of the touch-sensitive surface adjacent to the contact and/or its change are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measurement of contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measurement). In some implementations, the surrogate measurement of contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using contact intensity as an attribute of user input allows the user to access additional device functionality that may not be readily accessible to the user on a reduced size device with a limited footprint for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical/mechanical controls such as knobs or buttons).

In some embodiments, the contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by activation thresholds of specific physical actuators and can be adjusted without changing the physical hardware of the device 100). For example, a mouse "click" threshold for a touchpad or touchscreen can be set to any one of a large range of predefined thresholds without changing the touchpad or touchscreen display hardware. In addition, in some embodiments, a software setting is provided to the user of the device for adjusting one or more thresholds in the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting multiple intensity thresholds at once using a system-level click on an "intensity" parameter).

As used in the specification and claims, the term "characterized intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characterized intensity is based on multiple intensity samples. The characterized intensity is optionally a predetermined number of intensities relative to a predetermined event (e.g., after detecting the contact, before detecting the contact is lifted, before or after detecting the contact starts to move, before detecting the contact ends, before or after detecting an increase in contact intensity, and/or before or after detecting a decrease in contact intensity), or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds). The characterized intensity of the contact is optionally based on one or more of the maximum contact intensity, the median contact intensity, the average contact intensity, the top 10% contact intensity, the value at half-maximum contact intensity, the value at 90% maximum contact intensity, etc. In some embodiments, the duration of the contact is used to determine the characterized intensity (e.g., when the characterized intensity is the average of the contact intensity over time). In some embodiments, the characterized intensity is compared to a set of one or more intensity thresholds to determine whether an action has been performed by the user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characterized intensity that does not exceed the first threshold results in a first operation, a contact with a characterized intensity that exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second operation, and a contact with a characterized intensity that exceeds the second intensity threshold results in a third operation. In some embodiments, a comparison between the characterized intensity and one or more intensity thresholds is used to determine whether to perform one or more operations (e.g., whether to perform a corresponding option or abstain from performing a corresponding operation), rather than to determine whether to perform the first operation or the second operation.

In some embodiments, a portion of a gesture is recognized for the purpose of determining a characterization intensity. For example, a touch-sensitive surface may receive a continuous swipe (e.g., a drag gesture) that transitions from a starting position and reaches an ending position where the contact intensity increases. In this example, the characterization intensity of the contact at the ending position may be based on only a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the contact that was swiped at the ending position). In some embodiments, a smoothing algorithm may be applied to the intensity of the swipe contact before determining the characterization intensity of the contact. For example, the smoothing algorithm optionally includes one or more of an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact for the purpose of determining the characterization intensity.

The user interface figures described herein (e.g., Figures 5A-5HH, 6A-6V, 7A-7O, 8A-8R, 9A-9H, 22A-23BA) optionally include various intensity graphs that illustrate the current contact intensity on the touch-sensitive surface relative to one or more intensity thresholds (e.g., a contact detection intensity threshold IT ₀ , a hint intensity threshold IT _H , a light press intensity threshold IT _L , a deep press intensity threshold IT _D (e.g., at least initially above _IL ), and/or one or more other intensity thresholds (e.g., an intensity threshold I _H below _IL )). This intensity graph is typically not part of the displayed user interface, but is provided to aid in explaining the figures. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with a tap of a physical mouse button or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations other than those typically associated with a tap of a physical mouse button or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below a light press intensity threshold (e.g., and above a nominal contact detection intensity threshold IT ₀ , below which the contact is no longer detected), the device moves the focus selector in accordance with movement of the contact on the touch-sensitive surface without performing operations associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent across different sets of user interface diagrams.

In some embodiments, a device's response to an input detected by the device depends on criteria based on contact intensity during the input. For example, for certain "light press" inputs, a contact intensity exceeding a first intensity threshold during the input triggers a first response. In some embodiments, a device's response to an input detected by the device depends on criteria that include both contact intensity during the input and time-based criteria. For example, for certain "deep press" inputs, a contact intensity exceeding a second intensity threshold (greater than the first intensity threshold for a light press) during the input triggers a second response only if a certain delay time has elapsed between the first intensity threshold being met and the second intensity threshold being met. This delay time is typically less than 200 ms (e.g., 40, 100, or 120 ms, depending on the magnitude of the second intensity threshold). This delay time helps avoid accidental deep press inputs. As another example, for certain "deep press" inputs, a period of reduced sensitivity occurs after the first intensity threshold is met. During this period of reduced sensitivity, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps avoid accidental deep press inputs. For other deep press inputs, the response to detecting the deep press input does not depend on time-based criteria.

In some embodiments, one or more of the input intensity thresholds and/or corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, application running, rate at which intensity is applied, number of concurrent inputs, user history, environmental factors (e.g., ambient noise), focus selector positioning, etc. Exemplary factors are described in U.S. Patent Application Serial Nos. 14/399,606 and 14/624,296, the contents of which are incorporated herein by reference.

For example, FIG4C illustrates a dynamic intensity threshold 480 that varies over time based in part on the intensity of touch input 476 over time. Dynamic intensity threshold 480 is the sum of two components: a first component 474 that decays over time after a predefined delay time p1 from when touch input 476 is initially detected, and a second component 478 that tracks the intensity of touch input 476 over time. The initial high intensity threshold of first component 474 reduces accidental triggering of a "deep press" response while still allowing an immediate "deep press" response when touch input 476 provides significant intensity. Second component 478 reduces unintentional triggering of a "deep press" response through gradual intensity fluctuations of the touch input. In some embodiments, a "deep press" response is triggered when touch input 476 satisfies dynamic intensity threshold 480 (e.g., at point 480 in FIG4C ).

FIG4D illustrates another dynamic intensity threshold 486 (e.g., intensity threshold _ID ). FIG4D also illustrates two other intensity thresholds: a first intensity threshold _IH and a second intensity threshold _IL . In FIG4D, although touch input 484 satisfies both the first intensity threshold _IH and the second intensity threshold _IL before time p2, no response is provided until delay time p2 has elapsed at time 482. Also in FIG4D, dynamic intensity threshold 486 decays over time, with decay beginning at time 488 after a predefined delay time p1 has elapsed from time 482 (when the response associated with the second intensity threshold _IL was triggered). Such a dynamic intensity threshold reduces the risk of inadvertently triggering a response associated with a lower intensity threshold (such as the first intensity threshold _IH or the second intensity threshold _IL ) or concurrently with the dynamic intensity threshold _ID .

FIG4E illustrates yet another dynamic intensity threshold 492 (e.g., intensity threshold _ID ). In FIG4E, the response associated with intensity threshold _IL is triggered after a delay time p2 has elapsed since touch input 490 was initially detected. Concurrently, dynamic intensity threshold 492 decays after a predefined delay time p1 has elapsed since touch input 490 was initially detected. Thus, a decrease in the intensity of touch input 490 after triggering the response associated with intensity threshold _IL , followed by an increase in the intensity of touch input 490 without releasing touch input 490, can trigger a response associated with intensity threshold _ID (e.g., at time 494), even when the intensity of touch input 490 is below another intensity threshold (e.g., intensity threshold _IL ).

An increase in the representative intensity of a contact from an intensity below a light press intensity threshold IT _L to an intensity between the light press intensity threshold IT _L and the deep press intensity threshold IT _D is sometimes referred to as a "light press" input. An increase in the representative intensity of a contact from an intensity below a deep press intensity threshold IT _D to an intensity above the deep press intensity threshold IT _D is sometimes referred to as a "deep press" input. An increase in the representative intensity of a contact from an intensity below a contact detection intensity threshold IT ₀ to an intensity between the contact detection intensity threshold IT ₀ and the light press intensity threshold IT _L is sometimes referred to as detecting a contact on the touch-sensitive surface. A decrease in the representative intensity of a contact from an intensity above the contact detection intensity threshold IT ₀ to an intensity below the contact detection intensity threshold IT ₀ is sometimes referred to as detecting lift-off of the contact from the touch surface. In some embodiments, IT ₀ is zero. In some embodiments, IT ₀ is greater than zero. In some illustrations, shaded circles or ellipses are used to represent the intensity of a contact on the touch-sensitive surface. In some illustrations, unshaded circles or ellipses are used to represent corresponding contacts on the touch-sensitive surface without specifying the intensity of the corresponding contacts.

In some embodiments described herein, one or more operations are performed in response to detecting a gesture including a corresponding press input, or in response to detecting a corresponding press input performed with a corresponding contact (or contacts), wherein the corresponding press input is detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some embodiments, in response to detecting an increase in intensity of the corresponding contact above the press input intensity threshold, the corresponding operation is performed (e.g., performing the corresponding operation on a "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in intensity of the corresponding contact above the press input intensity threshold and then a decrease in intensity of the contact below the press input intensity threshold, and in response to detecting a decrease in intensity of the corresponding contact below the press input threshold, the corresponding operation is performed (e.g., performing the corresponding operation on an "up stroke" of the corresponding press input).

In some embodiments, the device utilizes intensity hysteresis to avoid unintended input, sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold that has a predetermined correlation with a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable fraction of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in the intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold, and in response to detecting the subsequent decrease in the intensity of the corresponding contact below the hysteresis intensity threshold, performing a corresponding action (e.g., performing a corresponding action for an "upward stroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in the intensity of the contact from at or below the hysteresis intensity threshold to an intensity at or above the press input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to at or below the hysteresis intensity, and in response to detecting the press input, a corresponding action (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, depending on the circumstances) is performed.

For ease of explanation, descriptions of operations performed in response to a press input associated with a press input intensity threshold or in response to a gesture including a press input are optionally triggered in response to detecting: contact intensity increasing above the press input intensity threshold, contact intensity increasing from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, contact intensity decreasing below the press input intensity threshold, or contact intensity decreasing below a hysteresis intensity threshold that corresponds to the press input intensity threshold. Additionally, in examples where operations are described as being in response to detecting a decrease in contact intensity below the press input intensity threshold, operations are optionally performed in response to detecting a decrease in contact intensity below a hysteresis intensity threshold that corresponds to and is below the press input intensity threshold. As described above, in some embodiments, triggering of these responses also depends on time-based criteria being met (e.g., a delay time having elapsed between a first intensity threshold being met and a second intensity threshold being met).

User interface and contextual processing

Attention now turns to embodiments of a user interface ("UI") and associated processing that may be implemented on an electronic device (such as portable multifunction device 100 or device 300) having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contact with the touch-sensitive surface.

Figures 5A-5HH illustrate exemplary user interfaces for navigating between user interfaces in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, 15, 24A-24F, and 25A-25H. For ease of explanation, some embodiments will be discussed with reference to operations performed on a device with a touch-sensitive display system 112. In such embodiments, the focus selector may optionally be: a corresponding finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., the center of mass of the corresponding contact or a point associated with the corresponding contact), or the center of mass of two or more contacts detected on the touch-sensitive display system 112. However, similar operations may optionally be performed on a device with 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 illustrated user interface on the display 450 along with the focus selector.

Figures 5A-5T illustrate exemplary embodiments of a user interface selection mode that allows a user to efficiently navigate between multiple user interfaces on an electronic device (e.g., multifunction device 100) in accordance with some embodiments. An exemplary user interface for the user interface selection mode (e.g., user interface 506 displayed on touch screen 112) includes representations of multiple user interfaces (e.g., representations 508, 510, 526, 534, 540, and 552 of user interfaces 502, 507, 524, 536, 542, and 552, respectively, for applications associated with the electronic device displayed as virtual card stacks (e.g., "stacks"). User input detected on touch screen 112 (e.g., a touch-sensitive surface) (e.g., a contact, a swipe/drag gesture, a tap gesture, etc.) is used to navigate between the user interfaces that can be selected for display on the screen. Figure 5A illustrates the display of a graphical user interface 502 for a web browsing application on the electronic device. User interface 502 includes display of a status bar 503 that provides information to the user (e.g., signal strength indicator(s) 402 for wireless communication(s), time 404, Bluetooth indicator 405, and battery status indicator 406). As shown in Figures 5B-5C, the device enters a user interface selection mode upon detecting a deep press 504 (e.g., an exemplary predetermined input) on the left side of the device's bezel, the deep press including increasing the intensity of the contact from an intensity below IT _D to an intensity above IT _D.

In some embodiments, system-level gestures are used to activate user interface selection mode. For example, as shown in Figures 5B and 5C, a deep press on the left side of the device's frame activates user interface selection mode. In an alternative embodiment, as shown in Figures 5EE and 5C, where the device is capable of distinguishing between user thumb contact and user finger contact, detecting a deep thumb press 570 on touch screen 112 (e.g., anywhere on the associated touch-sensitive surface) activates user interface selection mode (e.g., in response to detecting a thumb press comprising contact increasing from an intensity below IT _D to an intensity above IT _D , the device 100 replaces the display of user interface 502 with the display of user interface 506). In contrast, as shown in Figures 5FF-5GG, in response to detecting a deep finger press 572 within user interface 502 (e.g., at the same location where the device 100 detected deep thumb press 570 in Figure 5EE), the device previews web content associated with the object displayed at the location of the deep finger press 572 (e.g., the device displays a preview window 574 in Figure 5GG). Thus, in some embodiments, when selecting between activating a user interface selection mode and performing an application-specific operation (e.g., previewing web content), the device distinguishes between both the type of gesture (e.g., a deep thumb press versus a deep finger press) and the location of the gesture (e.g., a deep finger press on the left side of the bezel versus a deep finger press within the user interface).

5C-5F illustrate an exemplary user interface (e.g., graphical user interface 502) for a user interface selection mode, including a representation 508 of the web browsing user interface 502 and a representation 510 of at least the messaging user interface 506 displayed on the touch screen 112 immediately prior to entering the user interface selection mode.

Optional title bars 512 and 522 provide information about the user interface represented in the card. For example, title bar 512 includes the name "Safari" 514 and icon 516 associated with the web browsing application user interface 502 represented in card 508. Similarly, title bar 522 includes the name "Messages" 520 and icon 518 associated with the messaging application user interface 506 represented in card 510. In some embodiments, the title area (e.g., title bar) is not part of the user interface representation card. In some embodiments, the title bar is not illustrated as being detached from the user interface representation card. In some embodiments, title information (e.g., a title bar corresponding to the application, the application name, and/or icon) is displayed as hovering above or below the user interface representation card. In some embodiments, the user interface selection mode does not include the display of title information.

5C-5E illustrate an exemplary user interface for a user interface selection mode that displays a user interface representation without apparent depth (e.g., in a substantially two-dimensional representation) as if the user is looking down at a deck of cards spread out on a table. As shown, the plurality of cards are viewed as spreading out in a straight line from the top of the card stack on the left-hand side of the display to the right. However, in some embodiments, the cards spread out from the top of the card stack on the right-hand side of the display to the left, and/or spread out skewed or along a nonlinear path (e.g., along a curved or seemingly random path).

5C illustrates an embodiment in which the card for the user interface displayed immediately before entering the user interface selection mode is displayed as the top card in the user interface selection stack. For example, user interface 502 shows a web browsing card 508 (e.g., representation 508 of web browsing user interface 502) displayed above a messaging card 510 (e.g., representation 510 of messaging user interface 507).

5D illustrates an embodiment in which the card for the user interface displayed immediately before entering the user interface selection mode is displayed further back in the user interface selection stack. For example, user interface 502 shows a web browsing card 508 (e.g., representation 508 of web browsing user interface 502) displayed below messaging card 510 (e.g., representation 510 of messaging user interface 507).

Figure 5E illustrates an embodiment in which a stack includes more than two cards. For example, user interface 502 shows web browsing card 508 displayed above messaging card 510, which in turn is displayed above photo card 526 (e.g., representation 526 of user interface 524 for an image management application). Cards at the top of the stack are spread out more relative to each other than cards further back in the stack, resulting in more of the top card appearing than those further back. For example, web browsing card 508 is spread out further to the right relative to messaging card 510 than messaging card 510 is relative to photo card 526. Consequently, more of messaging card 510 appears on touch screen 112 than photo card 526; this is manifested by displaying the entire messaging icon 518 and only a portion of photo icon 528. Additional cards present in the stack are illustrated as one or more edges 503 displayed below card 528 (e.g., the partially displayed bottom-most card).

5F illustrates an exemplary user interface for a user interface selection mode, which displays a user interface representation of cards with apparent depth (e.g., in a three-dimensional representation), as if the user is looking down at the cards floating in sequence from a deck of cards on a table along a virtual z-axis substantially orthogonal to the plane of the display. The cards become larger as they extend further from the bottom of the stack, giving the appearance that they are generally moving toward the user. For example, the web browsing card 508 is displayed larger than the messaging card 510 on the touch screen 112 because it is further from the bottom of the stack. As shown, viewing the multiple cards appears to progress upward (e.g., along the virtual z-axis) and to the right from the stack of cards on the left-hand side of the display along a straight or slightly curved path. However, in some embodiments, the cards progress upward and to the left from the stack of cards on the right-hand side of the display, and/or progress obliquely or along a nonlinear path (e.g., along a curved or seemingly random path).

Figures 5G-5K illustrate moving user interface representation cards on a display in response to user input in a substantially two-dimensional representation of a stack (e.g., navigating between multiple user interface representations). As shown in Figure 5G, device 100 displays a stack of user interface cards 508, 510, and 526 that expands to the right. Device 100 detects a drag gesture (e.g., user input) that includes contact 530 and movement 532 originating from the location of touch screen 112 displaying messaging card 510 (e.g., the user touches and drags messaging card 510).

In response to detecting that contact 530 moves 532 from position 530-a in Figure 5G to position 530-b in Figure 5H and continuing to position 530-c in Figure 5I, the device further unfolds the user interface card to the right (e.g., in the direction of the drag gesture). As shown in Figures 5G-5I, the messaging card 510 moves laterally across the screen from position 510-a in Figure 5G to position 510-b in Figure 5H and continuing to position 510-c in Figure 5I at the same speed as contact 530 (e.g., directly manipulated by the contact), as if the contact actually pressed down and moved the card on the table. This is illustrated by maintaining a fixed display of card 510 relative to the position of contact 530 on touch screen 112 (e.g., a touch-sensitive surface). For example, the word "Will" in the representation of messaging user interface 507 remains directly under the contact in Figures 5G-5I.

As shown in Figures 5G-5I, the card displayed above the card directly manipulated by the contact moves faster than the contact. For example, web browsing card 508 moves faster than contact 530, and therefore faster than messaging card 510, thereby traveling from position 508-a in Figure 5G to position 508-b in Figure 5H and ultimately leaving the screen in Figure 5I (e.g., to the right of the right edge of touch screen 112). Due to the speed difference between the cards, as contact 530 moves to the right, more of messaging card 510 is revealed from under web browsing card 508. For example, as contact 530 moves from position 530-a in Figure 5G to position 530-b in Figure 5H, more conversations in the representation of user interface 507 are revealed (this is also shown by the appearance of the name "Messages" 520 in title area 522 above card 510 in Figure 5H after being covered by web browsing card 508 in Figure 5G).

As shown in Figures 5G-5I , cards displayed below the card directly manipulated by a contact move faster than the contact. For example, photo card 526 moves slower than contact 530, and therefore slower than messaging card 510. Due to the speed difference between the cards, more photo cards 526 appear from below messaging card 510 as contact 530 moves to the right. Additionally, as contact 530 moves from position 530-a in Figure 5G to position 530-b in Figure 5H , more photos appear in the representation of user interface 524 (this is also illustrated by the gradual appearance of the name "Photos" 532 in the title area above card 526 in Figures 5H and 5G ).

Figure 5H also illustrates that as the photo card moves from position 526-a in Figure 5G (e.g., where it is shown as being on top of all hidden cards in the stack) to position 526-b in Figure 5H, a previously hidden music card 534 (e.g., a representation 534 for a music management/playing application or user interface 536) is revealed from beneath photo card 526. This movement gives the user the effect of sliding photo card 526 away from the top of the deck, thereby revealing a portion of the next card (e.g., music card 534).

Figure 5J illustrates contact 530 being lifted at position 530-c. As shown in Figures 5G-5J, the movement of the presentation card across the display stops when movement 532 of contact 530 stops in Figure 5I and lift of contact 530 is detected in Figure 5J. This is illustrated in Figure 5J by maintaining display of messaging card 510 at position 510-c, which was displayed after movement 532 of contact 530 stopped at position 530-c in Figure 5I.

The series of Figures 5G, 5H, 5J, and 5K illustrate lifting contact 530 before ceasing movement 532. As shown in Figure 5K, representation cards 510, 526, and 534 continue to move across touch screen 112 (e.g., with decreasing momentum). This is illustrated by, for example, the position of messaging card 510 changing from position 510-c in Figure 5J (when lift-off of contact 530 is detected) to position 510-d in Figure 5K. In some embodiments, the continued momentum of the representation cards moving across the display occurs in response to a tap gesture (e.g., inertial scrolling of UI representation cards, where the cards move with simulated inertia and slow down with simulated friction and have an initial velocity based on the velocity of the contact at a predefined time corresponding to lifting the contact from the touch-sensitive surface, such as the velocity at the time of lifting the contact or the velocity of the contact just before lifting the contact).

Figure 5K also illustrates the revealing of phone card 540 (e.g., a representation 540 of a user interface 542 for a phone application) as previously hidden music card 534 moves from position 534-c in Figure 5J to position 534-d in Figure 5K. Thus, in some embodiments, the stack includes more than one hidden card that can be revealed by continuing to navigate the user interface selection mode.

While the movement of cards in response to a drag gesture is illustrated in Figures 5G-5K as being along a straight line, in some embodiments, the movement of cards can be deflected from a predefined axis or path in response to a similarly deflecting user input. In some embodiments, the path of the cards is fixed to be along the predefined path, and vector components of the movement that are orthogonal to the predefined path (e.g., a downward component of a contact moving from the upper left side to the lower right side of the touch-sensitive surface) are ignored when moving the display of the cards across the screen. In some embodiments, vector components of the movement that are orthogonal to the predefined path of movement are reflected in the movement of one or more cards across the screen (e.g., a card that is directly manipulated by a contact can be pulled up or down from the path of the stack, or the entire path of the stack, e.g., all cards, can be changed).

In some embodiments, when the movement results in an angle below a threshold angle from the predefined movement path, the vector component of the movement that is orthogonal to the predefined movement path is ignored, while when the movement results in an angle above the threshold angle from the predefined movement path, the vector component of the movement that is orthogonal to the predefined movement path is taken into account. For example, when the user input movement deviates from the predefined movement path by less than a threshold angle (e.g., 15°), the movement of one or more representation cards is stabilized to account for undesirable drift of the user's movement. However, when the user makes a significant upward gesture (e.g., at an angle of 80° from the predefined movement path), one or more representation cards are moved up or down on the display corresponding to the orthogonal vector component of the movement (e.g., so that the user can remove cards from the stack while continuing to navigate through the remaining cards).

Figures 5L-5N illustrate the card moving in the opposite direction in response to a user input that includes movement in the opposite direction. Figure 5L illustrates displaying user interface 506 for user interface selection mode after lifting contact 530 (e.g., inertial scrolling) in Figures 5I-5J. The device detects a second drag gesture (e.g., user input) that includes contact 546 and movement 548 originating from the location on touch screen 112 where messaging card 510 is displayed (e.g., the user touches and drags messaging card 510 back toward the base of the stack).

In response to detecting contact 546 moving 548 from position 546-c in Figure 5L to position 546-d in Figure 5M and continuing to position 5N in Figure 5N, the device pulls UI representation cards 534, 526, 510, and 508 back toward the base of the stack. Messaging card 510 moves laterally across the screen from position 510-c in Figure 5L to position 510-e in Figure 5H and continuing to position 510-f in Figure 5I at the same speed as contact 548 (e.g., directly manipulated by the contact), as the card is displayed at a position corresponding to contact 546. This is illustrated by maintaining a fixed display of card 510 relative to the position of contact 546 on touch screen 112. For example, the word "Do" in the representation of messaging user interface 507 remains directly above and to the left of the contact in Figures 5L-5N.

As shown in Figures 5M-5N, web browsing card 508 moves faster than contact 546 because it is displayed above messaging card 510. Since messaging card 510 travels at the same speed as contact 546, web browsing card 508 also travels faster than messaging card 510. As a result, web browsing card 508 begins to catch up with and cover messaging card 508. For example, web browsing card 508 only covers the edge of messaging card 510 in Figure 5M. As contact 546 continues to move 548 to the left on the display, web browsing card 508 begins to slide over messaging card 510, covering half of messaging card 510 in Figure 5N.

As shown in Figures 5M-5N, photo card 526 moves more slowly than contact 546 because it is displayed above messaging card 510. Since messaging card 510 travels at the same speed as contact 546, photo card 526 also travels more slowly than messaging card 510. As a result, messaging card 510 begins to catch up with and cover photo card 546. For example, in Figure 5L, the application name "Photos" 532 associated with photo card 526 is completely exposed. As contact 546 continues to move 548 to the left on the display, message card 510 gradually slides further above photo card 526, completely covering application name "Photos" 532 when contact 545 reaches position 546-f in Figure 5N.

Figure 50 illustrates the velocity of the user interface presentation card relative to the lateral velocity of contacts 530 and 546 on touch screen 112, as shown in Figures 5G-5I and 5L-5N. As shown in the top panel, contact 530 moves from left to right across touch screen 112 at a constant velocity equal to the slope of movement 532 (e.g., represented graphically as a function of pixels over time). After contact 530 is lifted at location 530-c, the device detects contact 546, which moves backward from right to left across touch screen 112 at a constant velocity equal to the slope of movement 548 (e.g., represented graphically as a function of pixels over time). Because contacts 530 and 546 were detected at locations on touch screen 112 corresponding to the display of messaging card 510, the velocity of messaging card 510 is equal to the velocity of the contacts.

The middle panel of FIG5O illustrates the relative speed of the UI presentation cards along speed curve 550 at position "e" during movement 548 of contact 546 (e.g., as shown in FIG5M ). The relative lateral speed of messaging card 510 at position 510-f is equal to the absolute value of the slope of movement 548, as graphically illustrated in the top panel of FIG5O . Due to the relative Z position (e.g., along a virtual Z axis substantially orthogonal to the plane of the device's display) of web browsing card 508 above messaging card 510 in user interface 506 (e.g., an exemplary user interface for user interface selection mode), speed curve 550 shows that web browsing card 508 travels relatively faster than messaging card 510. Similarly, due to the relative Z position of photo card 526 below messaging card 510 in user interface 506, speed curve 550 shows that photo card 526 travels slower than messaging card 510.

The absolute lateral velocity of cards 526, 510, and 508 is represented relative to the actual velocity of the user gesture (e.g., the lateral component of the user's contact moving across the touch-sensitive surface). As shown in the middle panel of FIG. 5O , user contact 546 directly manipulates the movement of messaging card 510 because the contact is at a location on touch screen 112 corresponding to the display of messaging card 510. Therefore, the velocity of messaging card 510 is the velocity of the user contact. The lateral velocity of web browsing card 508 is equal to a factor of the velocity of the user contact, e.g., the velocity of the user contact multiplied by a coefficient, where the coefficient is greater than 1 (e.g., due to the higher z-position of web browsing card 508 relative to messaging card 510, which is directly manipulated by user contact 546). The lateral velocity of photo card 526 is also equal to a factor of the velocity of the user contact, e.g., the velocity of the user contact multiplied by a coefficient, where the coefficient is less than 1 (e.g., due to the lower z-position of photo card 526 relative to messaging card 510, which is directly manipulated by user contact 546).

The middle panel of Figure 5O also illustrates the level of blur applied to each card in the stack relative to the card's absolute z position, as in some embodiments. Thus, as cards are spread out from the stack (e.g., to the right), their absolute z position increases and the applied blur decreases. In some embodiments, the device applies dynamic blur changes to a particular card as its absolute z position is manipulated by user input.

5M-5N , when moving in the opposite direction of the original gesture (e.g., back toward the base of the stack), web browsing card 508 catches up with contact 546 because it is traveling faster, as shown in FIG50 . When the leading edge (left edge) of web browsing card 508 is displayed at position 508-f on the touch screen corresponding to the center of mass of contact 546 at position 546-f, web browsing card 508 moves between contact 546 and messaging card 510. At this point, contact 546 begins to directly manipulate web browsing card 508 rather than messaging card 510.

As shown in Figures 5N and 5HH, device 100 detects continued movement 548 of contact 546 from position 546-f in Figure 5N to position 546-g in Figure 5HH. In response, as indicated by maintaining a fixed display of card 508 relative to the position of contact 546 on touch screen 112, web browsing card 508 continues to move laterally across the screen toward the base of the stack (e.g., from position 508-f in Figure 5N to position 508-g in Figure 5HH) at the same speed as contact 546 (which now directly manipulates web browsing card 508 rather than messaging card 510).

As shown in the lower panel of FIG5O, the speeds of UI cards 526, 510, and 508 slow down as this transition occurs. Just as messaging card 510 moves when displayed at position 510-e (e.g., as shown in FIG5M and in the middle panel of FIG5O), web browsing card 508 moves at a speed corresponding to the speed of contact 546 when displayed at position 508-f (e.g., as shown in FIG5N). Similarly, as photo card 526 moves when displayed at 526-e (e.g., as shown in FIG5M), messaging card 508 moves at the same slower relative speed when displayed at position 510-f (e.g., as shown in FIG5N) because it is now the card below the card below contact 546. Finally, photo card 526 moves at a slower speed when displayed at position 526-f (e.g., as shown in FIG5N) than it did when displayed at position 526-e (e.g., as shown in FIG5M). Although the movement of the UI card is illustrated as being at a constant speed, the speed of the card is relative to the speed of the user input. Therefore, in response to detecting a user input gesture with a variable speed, the electronic device moves the UI card at a variable speed.

Speed curve 550 is an exemplary representation of the relationship between the speeds of corresponding UI representation cards displayed in a stack. A first card (e.g., web browsing card 508) displayed above a second card (e.g., messaging card 510) in relative Z position (e.g., along a virtual z-axis) will always travel faster than the second card. In some embodiments, speed curve 550 represents other variable manipulations in the display of UI representation cards, such as the level of blur applied to corresponding cards in the stack (e.g., cards displayed further down the stack are blurrier than cards displayed toward the top of the stack), the size of corresponding cards in the stack (e.g., in a user interface selection mode, the user interface displays the stack as a three-dimensional representation, with cards displayed further down the stack appearing smaller than cards displayed toward the top of the stack), or the lateral position of corresponding cards in the stack (e.g., in a user interface selection mode, the user interface displays the stack as a substantially two-dimensional representation, with cards displayed further down the stack appearing closer to the bottom of the stack than cards displayed toward the top of the stack).

In some embodiments, the spacing of points on velocity curve 550 (e.g., corresponding to the placement of UI presentation cards relative to one another) has a constant difference in vertical coordinate values (e.g., the change in the z dimension, as represented by the vertical difference, between the two points is the same). In some embodiments, as shown in FIG. 50 , where velocity curve 550 follows a concave function, there is an increasing difference in vertical distance between successive points (e.g., a larger change in the x-direction). For example, the difference between the relative Z positions of photo card 526 and messaging card 510 is the same as the difference between the relative Z positions of messaging card 510 and web browsing card 508. However, the difference between the lateral speeds of messaging card 510 and web browsing card 508 is greater than the difference between the lateral speeds of photo card 526 and messaging card 510. This creates a visible effect on the display: the top card displayed in the stack will move off-screen faster relative to the appearance of cards displayed further back in the stack.

Figures 5P-5T illustrate the movement of user interface representation cards on a display in a substantially three-dimensional representation of a stack in response to user input (e.g., navigating between multiple user interface representations). As shown in Figure 5P, device 100 displays a stack of user interface cards 508, 510, and 526 that appear to unfold upward from a card stack positioned at the rear of the device. Web browsing card 508 is offset to the right, partially covering messaging card 510, and is displayed larger than messaging card 510 (e.g., to simulate being positioned above messaging card 510 in a virtual z-dimension that is substantially orthogonal to the plane of touch screen 112). Messaging card 510 and photo card 526 are displayed as increasingly blurred relative to web browsing card 508 (e.g., to further simulate distance in the display). Figure 5Q additionally illustrates the display of a home screen card 554 (e.g., a representation 554 of user interface 552 for a home screen on the device).

As shown in Figure 5R, device 100 detects a tap gesture (e.g., user input) that includes contact 556 and movement 558 originating from the location of touch screen 112 displaying messaging card 510 (e.g., the user touches and drags messaging card 510). In response to detecting movement 558 of contact 556 from position 556-a in Figure 5G to position 556-b in Figure 5H and continuing to position 556-c in Figure 5I, the device moves the card away from the base of the stack and toward the screen along the virtual z-axis. For example, as it moves from position 510-a in Figure 5R to position 510-b in Figure 5S, messaging card 510 becomes larger and moves to the right, and continues to become larger as it moves off the screen to the right at position 510-c in Figure 5T.

5T illustrates detecting contact 556 being lifted at position 556-c without ceasing movement 558, consistent with a tap gesture. The messaging card 510 continues to move across the display with simulated inertia as contact 556 travels (e.g., at the same speed; being directly manipulated by contact 556), ultimately ceasing at position 510-c on the touch screen 112.

Figures 5R-5T also illustrate the change in the blur level applied to UI representation cards as they move from the base of the stack. For example, when initially displayed at position 526-a as the bottom card visible in the stack, photo card 526 is moderately blurred. As photo card 526 moves from position 526-a in Figure 5R to position 526-b in Figure 5S (e.g., in response to contact 556 moving 558 from position 556-a in Figure 5R to position 556-b in Figure 5S), and finally to position 556-c in Figure 5T, it gradually comes into focus (e.g., becomes less blurry). In some embodiments, the blur level applied to UI representation cards follows a relationship similar to the relationship of lateral velocity with respect to the Z position of the card, as shown in velocity curve 550 in Figure 5O.

Figures 5U-5W illustrate user interface representation cards inserted for transient applications activated when the device is in user interface selection mode. Figure 5U illustrates user interface 506 for user interface selection mode, which displays a stack of user interface cards 508, 510, 526, and 534 that the user navigates through. Device 100 then receives a phone call and, in response, as shown in Figures 5V-5W , shuffles a phone card 554 (e.g., a representation 554 of a user interface 556 for a received call within a phone application) into the stack at position 555-b as shown in Figure 5W . As shown in Figures 5V-5W , the device moves web browsing card 508 and messaging card 510 upward in the stack (e.g., from positions 508-b and 510-b, respectively, shown as dashed outlines in Figure 5V , off the display, and to position 510-e in Figure 5W ) to make room for phone card 556. While Figures 5V-5W illustrate an animation in which phone card 555 is brought to the screen in Figure 5V and inserted into the stack behind web browsing card 508 and messaging card 510 in Figure 5W, other animations and placements of user interface representations for transient applications are contemplated (e.g., a new card becomes the top of the stack, or a card further back in the stack is pushed further down to make room for the new card).

Figures 5X-5AA illustrate removing user interface representation cards upon detecting a predefined user input. Figure 5X illustrates user interface 506 for a user interface selection mode, which displays a stack of user interface cards 508, 510, 526, and 534 for user navigation. Device 100 detects a swipe gesture comprising contact 560 and movement 562 that is substantially orthogonal to a predefined path of movement for the cards in the stack (e.g., a swipe moves upward along touch screen 112, while cards in the stack move left and right across the screen during navigation), originating from a location on touch screen 112 displaying messaging card 510. In response to detecting contact 560 moving 562 from position 560-a in Figure 5X to position 560-b in Figure 5Y and continuing to position 560-c in Figure 5Z, the device lifts the messaging card 510 from the stack and sends it off the screen (e.g., via moving from position 510-b in Figure 5X to position 510-f in Figure 5Y and continuing to position 510-g in Figure 5Z).

As shown in Figures 5Z-5AA, device 100 moves photo card 526 and music card 534 upward in the stack after removing messaging card 510. Photo card 526 moves from position 526-g in Figure 5Z to position 526-h in Figure 5AA, thereby replacing the gap in the stack created by the removal of messaging card 510. Similarly, music card 534 moves from position 534-g in Figure 5Z to position 534-h in Figure 5AA, thereby replacing the gap in the stack created by the upward movement of photo card 526. The blur level applied to photo card 526 and music card 534 also adjusts based on their upward movement in the stack. For example, photo card 526 is partially blurred when displayed at position 526-g in Figure 5Z, but is in focus when displayed at position 526-h in Figure 5AA. In some embodiments, removing a user interface presentation card from the stack also closes the active application associated with the user interface.

Figures 5BB and 5CC illustrate leaving user interface selection mode by selecting a user interface representation. Figure 5BB illustrates user interface 506 for user interface selection mode, which displays a stack of user interface cards 508, 510, 526, and 534 for navigation by the user. Device 100 detects a tap gesture that includes contact 564 on touch screen 112 at a location where messaging card 510 (e.g., representation 510 of user interface 507 for a messaging application) is displayed. In response to detecting the tap gesture, as shown in Figure 5CC, the device activates the messaging application associated with user interface 507 and changes the display on touch screen 112 from user interface 506 for user interface selection mode to user interface 507 for a messaging application.

Figure 5DD illustrates a visual effect applied to the title area associated with a first user interface representation card as a user interface representation card displayed above the first card moves into close proximity. Figure 5DD illustrates messaging card 510 displayed above photo card 526 in user interface 506 in user interface selection mode, which includes a substantially two-dimensional representation of a stack. Photo card 526 is associated with title bar 558, which includes the name "Photos" 532 and icon 526 for the image management application associated with user interface 524. Messaging card 510 is associated with title bar 522, which displays information related to the messaging application associated with user interface 507. The display of messaging card 510 gradually slides over time above photo card 526 (via movement from position 510-a in the top panel, through positions 510-b and 510-c in the middle panel, to position 510-d in the bottom panel of Figure 5DD). As the edge of the messaging title bar 522 approaches the display of the name "Photos" 532 on the photos title bar 558 (when the messaging card 510 is in position 508-b in the second panel), the device applies a transitional fade to the name "Photos" 532. Panel three of Figure 5DD illustrates the removal of the display of the name "Photos" 532 before the messaging title bar 522 obscures the name "Photos" 532 from its previous position on the photos title bar 558.

Similarly, as the edge of the messaging title bar 552 approaches the display of icon 528 associated with the image management application on the photo title bar 558 (when the messaging card 510 is at position 508-d in the bottom panel of Figure 5DD), the transition of the device application icon 528 fades, thereby removing the display of icon 528 from the display before the messaging title bar 522 obscures the icon 528's previous position on the photo title bar 558. In some embodiments, such as where the user interface selection mode includes a substantially three-dimensional representation of a stack, it is the edge of the second user interface representation card (e.g., the top card) rather than the associated title bar that approaches and triggers the animation to remove the title information associated with the first user interface representation card (e.g., the bottom card). In some embodiments, the animation applied to the information displayed in the title area (e.g., the title bar) is a blur or clipping rather than the fading shown in Figure 5DD. In some embodiments, the icons stack rather than disappear as the next user representation card approaches.

Figures 6A-6V illustrate exemplary user interfaces for navigating between user interfaces in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, 15, 24A-24F, and 25A-25H. Although some of the following examples will be given with reference to input on a touch screen display (where a touch-sensitive surface and display are combined), in some embodiments, as shown in Figure 4B, the device detects input on a touch-sensitive surface 451 that is separate from the display 450.

6A-6V illustrate exemplary embodiments of a user interface selection mode that allows a user to glance at a representation of a previously displayed user interface without leaving the current user interface, allows a user to quickly swap between two corresponding user interfaces, and allows a user to easily enter a user interface selection mode with different types of hierarchical selections on an electronic device (e.g., multifunction device 100). An exemplary user interface for the user interface selection mode (e.g., user interface 506 displayed on touch screen 112) includes representations of multiple user interfaces for applications associated with the electronic device (e.g., representations 508, 510, 526, 534, 540, and 552 of user interfaces 502, 507, 524, 536, 542, and 552, respectively), which are displayed as a virtual card stack (e.g., a "stack") or as a selection between two most recently displayed user interfaces. User input (e.g., contact, swipe/drag gesture, tap gesture, etc.) detected on touch screen 112 (e.g., a touch-sensitive surface) is used to navigate between the user interfaces that can be selected for display on the screen (e.g., touch screen 112).

Figures 6A-6G illustrate an embodiment in which a user of an electronic device displaying a first user interface (e.g., any user interface for a corresponding application open on the device, such as a web browsing user interface) can use different gestures initiated from a common contact on a touch-sensitive surface (e.g., touch screen 112 on multifunction device 100) to navigate between: (i) glancing at a previously displayed user interface and reverting back to the first user interface; (ii) changing to a previous application; (iii) entering a user interface selection mode (e.g., an application selection mode); and (iv) scrolling through user interfaces within user interface selection mode.

6A-6D illustrate embodiments in which a user views (e.g., "peeks") a representation of a previously displayed user interface and then automatically reverts back to the user interface displayed on the device prior to the peek (e.g., reverts back to an application open on the device). FIG6A illustrates the display of a graphical user interface 502 for a web browsing application on an electronic device.

As shown in Figures 6B-6C , the device enters user interface preview mode upon detecting user input including contact 602 adjacent to the left edge of touch screen 112 (e.g., on the bezel) with an intensity below a predetermined threshold (e.g., below a deep press intensity threshold (IT _D ); e.g., an exemplary predetermined input). Upon detecting the input including contact 602, the device replaces the display of web browsing user interface 502 on touch screen 112, as shown in Figure 6B , with the display of user interface selection mode 506. User selection mode 506 includes user interface representations of the last two user interfaces displayed on touch screen 112, e.g., representation 508 of web browsing user interface 502 and representation 510 of messaging user interface 507. As shown in Figures 6B and 6C , the intensity of contact 602 remains below the deep press intensity threshold (IT _D ) (e.g., an exemplary predetermined intensity threshold), and the contact remains stationary at the original detection point.

Device 100 then detects termination of the user input including contact 602 in Figure 6D. Because the intensity of contact 602 remains below the deep press intensity threshold ( _ITD ), and because the user input does not include movement of contact 602 (e.g., movement in a predefined direction on touch screen 112), upon detecting termination of contact 602 (e.g., lift-off), device 100 restores the display back to web browsing user interface 502 by replacing the display of user interface 506 with the display of user interface 502.

Figure series 6A, 6E-6G illustrate an alternative embodiment in which a user views (e.g., "peeks") at a representation of a previously displayed user interface and chooses to display the previously displayed user interface, rather than reverting to the user interface displayed on the device before the peek. Figure 6A illustrates the display of a graphical user interface 502 for a web browsing application on an electronic device.

FIG6E illustrates the device entering a user interface preview mode upon detecting user input including contact 604 adjacent to the left edge of touch screen 112 (e.g., on a bezel) with an intensity below a predetermined threshold (e.g., below a deep press intensity threshold ( _ITD ); e.g., an exemplary predetermined input). Upon detecting the input including contact 604, the device replaces the display of web browsing user interface 502 on touch screen 112 with the display of user interface selection mode 506. User selection mode 506 includes user interface representations of the last two user interfaces displayed on touch screen 112, e.g., representation 508 of web browsing user interface 502 and representation 510 of messaging user interface 507. As shown in FIG5B and FIG5C , the intensity of contact 604 remains below the deep press intensity threshold ( _ITD ) (e.g., an exemplary predetermined intensity threshold). However, the electronic device detects that contact 604 has moved 606 in a predefined direction (e.g., laterally across touch screen 112) from position 604-a in FIG6E to position 604-b in FIG6F.

Device 100 then detects termination of the user input including contact 604 in Figure 6D . Because the intensity of contact 604 remains below the deep press intensity threshold (IT _D ), and because the user input includes movement of contact 604 on touch screen 112 in a predefined direction (e.g., laterally across the display), device 100 replaces display of user interface 506 with display of user interface 507 for the messaging application, as shown in Figure 6D , rather than reverting back to web browsing user interface 502.

Thus, in some embodiments, when the user input that invokes user interface preview mode has a characteristic intensity (e.g., a maximum intensity over the duration of the input that is below a predetermined threshold), the user can distinguish between reverting to display of the user interface that was displayed immediately prior to entering user interface preview mode (e.g., when the user merely glanced at the previously displayed user interface) and changing the display to the previously displayed user interface by moving the contact associated with the gesture in a predetermined direction or not (e.g., keeping the contact stationary).

Figure series 6A, 6H-6I illustrate another alternative embodiment in which a user views (e.g., "peeks") at a representation of a previously displayed user interface and chooses to steadily enter user interface selection mode, rather than reverting back to display of any of the previously displayed user interfaces represented during the user's glance. Figure 6A illustrates display of a graphical user interface 502 for a web browsing application on an electronic device.

As previously shown in Figures 6C and 6E , the device enters the user interface preview mode upon detecting a user input comprising a contact adjacent to the left edge of touch screen 112 (e.g., on a bezel) having an intensity below a predetermined threshold (e.g., below a deep press intensity threshold (IT _D ); e.g., an exemplary predetermined input). Figure 6H also illustrates that upon detecting an increase in the intensity of a calling contact (e.g., contact 608 in Figure 6H ), the device enters a stable user interface selection mode. Upon entering the stable user interface selection mode, device 100 displays a stack of user interface representation cards on touch screen 112, including user interface representations 508, 510, and 526 displayed in relative Z positions (e.g., as described with respect to Figures 5A-5HH ).

Device 100 then detects termination of the user input including contact 608 in Figure 6I. Because the intensity of contact 608 exceeds a predetermined intensity threshold for invoking stable user interface mode (e.g., a deep press intensity threshold ( _ITD )), device 100 does not replace display of user interface 506 on touch screen 112. In some embodiments, further navigation within the stable user interface selection mode is performed as described with respect to Figures 5A-5HH.

Thus, in some embodiments, the user can further distinguish between glancing at and selecting one of a limited number of user interfaces displayed in the user interface selection preview mode for display on the touch screen 112 and entering a stable user interface selection mode with further navigation controls based on the intensity of the contact used to invoke the user interface selection preview mode.

6J-6L illustrate an embodiment in which a user directly manipulates the display of a user interface selection mode by increasing the intensity of a user input. FIG6J illustrates entering a stable user interface selection mode, including displaying a stack of user interface representation cards (e.g., user interface representations 508, 510, and 526 displayed in relative Z positions to each other, e.g., as described with respect to FIG5A- _5HH ) in user interface 506 by detecting contact 610 adjacent to a left edge (e.g., on a bezel) of touch screen 112 with an intensity exceeding a predetermined intensity threshold (e.g., a deep press intensity threshold (ITD)).

Figures 6K-6L illustrate expanding the user interface representation cards displayed in the stack (e.g., along a z-axis substantially orthogonal to the plane of the display) based on direct user manipulation of the intensity of contact 610 as device 100 detects a further increase in the intensity of contact 610. In some embodiments, as shown in Figures 6K-6L, a small change in intensity (e.g., from a detected intensity just below the top tick line in Figure 6K to a detected intensity just above the top tick line in Figure 6L) causes messaging card 510 to move from position 510-b in Figure 6K to position 510-c in Figure 6L, thereby revealing more of photo card 526 and music card 534 in Figure 6L.

6M-6P illustrate an embodiment in which device 100 distinguishes between user inputs based on the characteristic intensity of the user input made within an application user interface. FIG6M illustrates a display of a graphical user interface 502 for a web browsing application on an electronic device. User interface 502 includes an application-specific "back" button icon 614 for navigating within the application to a previously displayed user interface (e.g., a previous web page displayed on touch screen 112). Device 100 detects a deep press, which includes contact 612 with a characteristic intensity exceeding a predetermined intensity threshold (e.g., a deep press intensity threshold (IT _D )) at a location on touch screen 112 that corresponds to display of a “back” button icon 614. In response to detecting the deep press, in FIG. 6N , device 100 replaces display of web browsing user interface 502 on touch screen 112 with user interface 506 for a user interface selection mode, which includes user interface representations 508, 618, and 622 of previously viewed web browsing interfaces 502, 616, and 620 (e.g., previously viewed web pages in a hierarchy of browser history).

Alternatively, in Figure 6V, device 100 detects a swipe gesture (e.g., movement 632 of contact 630) originating at the edge of touch screen 112. In response, device 100 navigates backward in the application-specific user interface hierarchy (e.g., back to the last web page viewed in a web browsing application) and replaces the display of user interface 502 in Figure 6V with user interface 616 in Figure 6P. In some embodiments, device 100 applies a dynamic animation upon detecting an edge swipe, such as an animated sliding of user interface 502 off the screen, thereby gradually revealing previously displayed user interface 616 as if stacked beneath user interface 502. In some embodiments, the animation is directly manipulated by the progress of the user swipe gesture. Thus, Figures 6V and 6P illustrate the use of an edge swipe gesture (e.g., including movement 632 of contact 630) to navigate back in the application-specific user interface hierarchy.

Figure 6O also illustrates the display of a graphical user interface 502 for a web browsing application on the electronic device. User interface 502 includes an application-specific "back" button icon 614 for navigating within the application to a previously displayed user interface (e.g., a previous web page displayed on touch screen 112). Device 100 detects a tap gesture (rather than a deep press as shown in Figure 6M) that includes a contact 624 having a characteristic intensity below a predetermined intensity threshold (e.g., a deep press intensity threshold ( _ITD )). In response to detecting the tap gesture, device 100 replaces the display of web browsing user interface 502 on touch screen 112 with a web browsing user interface 616 associated with a previously viewed user interface in the web browsing application (e.g., a last visited web page in the web browsing application), as shown in Figure 6P. Thus, in some embodiments, the electronic device distinguishes between application-specific user interface inputs based on the characteristic intensity of the user input.

Figures 6Q-6S illustrate that after swapping between the first user interface and the second user interface through the user interface preview mode as described for Figures 6A, 6E-6G, the user can quickly swap back to the first user interface by repeating the user gesture when the device displays the user interface for the second application.

Figure 6Q illustrates that after detecting a user gesture that causes the device to change the user interface display to a second user interface 507 for a messaging application, the device detects a second user input comprising contact 626 adjacent to the left edge of touch screen 112 (e.g., on a bezel) having an intensity below a predetermined threshold (e.g., below a deep press intensity threshold ( _ITD ); e.g., an exemplary predetermined input). Upon detecting the input comprising contact 626, the device replaces the display of messaging user interface 507 on touch screen 112 with the display of user interface selection mode 506. As shown in Figure 6R, user selection mode 506 includes user interface representations of the last two user interfaces displayed on touch screen 112, e.g., representation 508 of web browsing user interface 502 and representation 510 of messaging user interface 507. However, compared to the display of user interface 506 in Figures 6E-6F, the relative order of representations 508 and 510 in user interface 506 is switched because the messaging user interface 507 is now the most recently displayed user interface on touch screen 112, and therefore in Figure 6R, representation 510 of user interface 507 is displayed above representation 508 of user interface 502.

As shown in Figures 6Q and 6R, the intensity of contact 626 remains below a deep press intensity threshold ( _ITD ) (e.g., an exemplary predetermined intensity threshold). However, the electronic device detects movement 628 of contact 626 from position 626-a in Figure 6R in a predefined direction (e.g., laterally across touch screen 112). In Figure 6S, device 100 then detects termination of the user input including contact 626. Because the intensity of contact 626 remains below the deep press intensity threshold ( _ITD ), and because the user input includes movement of contact 626 on touch screen 112 in a predefined direction (e.g., laterally across the display), the device replaces display of user interface 506 with display of user interface 502 for a web browsing application, rather than reverting back to messaging user interface 507 as shown in Figure 6Q. Thus, the user switches back to the first user interface displayed on touch screen 112 in Figure 6A.

Figures 6T-6U illustrate an embodiment in which device 100 distinguishes between user input made at a first predefined location on device 112 and user input made at a second predefined location. Figure 6T illustrates the display of graphical user interface 502 for a web browsing application on the electronic device. Device 100 detects a deep press, which includes contact 628 adjacent to the right edge of touch screen 112 (e.g., on the bezel; the second predefined location) having a characteristic intensity exceeding a predetermined intensity threshold (e.g., a deep press intensity threshold (IT _D )). In response to detecting the deep press, device 100 replaces the display of web browsing user interface 502 on touch screen 112 with web browsing user interface 616 for the previously displayed website on touch screen 112, as shown in Figure 6U.

This is in contrast to the detection of a deep press input adjacent to the left edge of touch screen 112 (e.g., on the bezel; in the first predefined location) in Figure 6H that causes the device to enter a stable user interface selection mode. Thus, in some embodiments, different operations are performed depending on whether the invocation gesture is detected within the first predefined location or the second predefined location on the touch-sensitive surface.

Figures 7A-7O illustrate exemplary user interfaces for navigating between user interfaces in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, 15, 24A-24F, and 25A-25H. Although some of the following examples will be given with reference to input on a touch screen display (where the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from the display 450, as shown in Figure 4B.

Figures 7A-7O illustrate exemplary embodiments for navigating between previously displayed user interfaces using a single touch gesture on a predefined area of a touch-sensitive surface (e.g., a touch-sensitive display separate from the display or a touch-sensitive trackpad) in accordance with some embodiments. In some embodiments, a user swaps between two most recently viewed user interfaces using touch gestures of varying intensity on one or more predefined areas of the touch-sensitive surface.

7A-7F illustrate an embodiment in which a user previews (e.g., "peeks") a representation of a previously displayed user interface using a touch gesture with a first characteristic intensity on a predefined area of a touch-sensitive surface, and then opens the user interface (e.g., opens an application) by increasing the intensity of the touch gesture to a second characteristic intensity. FIG7A illustrates the display of a graphical user interface 502 for a web browsing application on an electronic device.

7B illustrates detecting a touch gesture that includes contact 702 with a first characteristic intensity (e.g., exceeding a light press intensity threshold (IT _L ) but below a deep press intensity threshold (IT _D )) adjacent to a left edge (e.g., on a bezel; in a predefined location on the touch-sensitive surface) of touch screen 112. In response to detecting the touch gesture, device 100 enters a user interface selection mode, replacing display of web browsing user interface 502 on touch screen 112 in FIG. 7B with display of user interface 506 for user interface selection mode on touch screen 112 in FIG. 7C .

7C illustrates the display of user interface 506 for user interface selection mode, which includes representation 508 of web browsing user interface 502 (“web browsing card 508”) and representation 510 of messaging user interface 507 (“messaging card 510”) of two user interfaces previously displayed on touch screen 112. In some embodiments, the two representations are for the last two user interfaces displayed on the device (e.g., the last two applications opened on the display). In some embodiments, the two representations are for the last two user interfaces displayed for a particular application opened on touch screen 112 when user interface selection mode was initiated (e.g., the last two web pages displayed in a web browser application or the last two messages displayed in an email management application).

As shown in FIG7C , web browsing card 508 is displayed as if it is above messaging card 510 in a Z orientation (e.g., positioned along a virtual axis substantially orthogonal to the plane of the display) and laterally displaced to the right of messaging card 510 because it represents the last user interface displayed on touch screen 112 before the user interface selection mode is activated. Device 100 also applies a blur level (e.g., associated with its relative or absolute Z position) to messaging card 510. In some embodiments, the representation of the last user interface displayed before the user interface selection mode is activated is displayed behind or equal to the second user interface representation in a relative Z orientation.

Figure 7D illustrates detecting an increase in the intensity of contact 702 (e.g., from an intensity just above the light press intensity threshold IT _L in Figure 7C to an intensity just below the deep press intensity threshold IT _D in Figure 7D). In response to detecting an increase in the intensity of contact 702, messaging card 510 increases in size and moves toward the plane of touch screen 112 in the virtual z dimension (e.g., from position 510-a in Figure 7C to position 510-b in Figure 7D). Messaging card 510 also begins to come into focus (e.g., the blur level decreases) as it moves upward in the virtual z dimension. At the same time, web browsing card 508 decreases in size and moves backward in the virtual z dimension (e.g., from position 508-a in Figure 7C to position 508-b in Figure 7D). In some embodiments, an animation is displayed to show the movement of the first user interface representation and the second user interface representation in a manner that dynamically responds to small changes in the intensity of the contact.

7E illustrates detecting a further increase in the intensity of contact 702 (e.g., exceeding a deep press intensity threshold (IT _D )). In response to detecting that the intensity of contact 702 exceeds a second characteristic intensity (e.g., exceeding a deep press intensity threshold (IT _D )), messaging card 510 continues to move upward in the virtual z-dimension and moves over web browsing card 508, which continues to move backward in the virtual z-dimension and begins to blur.

In some embodiments, in response to detecting that the intensity of contact 702 exceeds a second predetermined threshold (e.g., a deep press intensity threshold (IT _D )), the device automatically opens a messaging application associated with user interface 507 (e.g., a card or associated application "pop-up") and replaces the display of the user interface selection mode with user interface 507 as shown in FIG. 7F .

7G-7K illustrate an alternative embodiment for "peek" and "pop-up" a previously displayed user interface (e.g., and associated applications) as described for FIG7A-7F. In this embodiment, the user interface representation is displayed in a substantially two-dimensional view rather than along a virtual z-axis.

Figure 7G illustrates detecting a touch gesture that includes contact 704 with a first characteristic intensity (e.g., exceeding a light press intensity threshold (IT _L ) but below a deep press intensity threshold (IT _D )) adjacent to a left edge (e.g., on a bezel; in a predefined location on the touch-sensitive surface) of touch screen 112. In response to detecting the touch gesture, device 100 enters a user interface selection mode, displaying user interface 506 for user interface selection mode on touch screen 112 in Figure 7G .

FIG7G illustrates the display of user interface 506 for user interface selection mode, which includes representation 508 of web browsing user interface 502 (“web browsing card 508”) and representation 510 of messaging user interface 507 (“messaging card 510”), of the two user interfaces previously displayed on touch screen 112. As shown in FIG7G , messaging card 510 is displayed as if directly on top of web browsing card 508 in the Z orientation and laterally shifted to the right of web browsing card 508 because it represents the last user interface displayed on touch screen 112 before user interface selection mode was activated.

FIG7H illustrates detecting an increase in the intensity of contact 704 (e.g., from an intensity just above the light press intensity threshold IT _L in FIG7C to an intensity just below the deep press intensity threshold IT _D in FIG7D ). In response to detecting the increase in the intensity of the contact, web browsing card 508 is revealed further below messaging card 508 by moving messaging card 510 to the right of the screen from position 510 - a in FIG7G to position 510 - b in FIG7H .

7E illustrates detecting a decrease in the intensity of contact 704. In response to detecting a decrease in the intensity of contact 702, messaging card 510 begins to slide back over web browsing card 508.

Figure 7J illustrates detecting that the intensity of contact 704 is further reduced to below the first characteristic intensity (e.g., below the light press intensity threshold (IT _L )). In response to the reduction to below the first characteristic intensity, device 5100 exits user interface selection mode and replaces the display of user interface 506 with user interface 507 for the messaging application displayed immediately before entering user interface selection mode (e.g., because contact 704 failed to "pop up" web browsing card 508 from under messaging card 510, the device resumes its last active state when exiting user interface selection mode). Figure 7K further illustrates detecting that contact 704 is lifted, resulting in the user interface displayed on touch screen 112 remaining unchanged.

In contrast, the following embodiment is illustrated in which, after the user switches the user interface from web browsing user interface 502 to messaging user interface 507 (e.g., as described in Figures 5A-5F), the user again initiates the "peek" and "pop" process when contact 706 is detected in a predetermined area (e.g., the left side of the bezel) on the touch-sensitive surface in Figure 7L. In response to detecting an increase in the intensity of contact 706 from Figures 7M to 7N, the messaging card moves from position 510-d in Figure 7M to position 510-e in Figure 7N. In Figure 7O, a further increase in the intensity of contact 706 is detected beyond a second characteristic intensity (e.g., a deep press intensity threshold ( _ITD )), which pops the web browsing application back (e.g., the device replaces the display of user interface 506 for user interface selection mode with user interface 502 for the web browsing application). Thus, the user has switched back to the previously displayed user interface.

Figures 8A-8R illustrate exemplary user interfaces for navigating between user interfaces in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, 15, 24A-24F, and 25A-25H. Although some of the following examples will be given with reference to input on a touch screen display (where a touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from the display 450, as shown in Figure 4B.

Figures 8A-8R illustrate exemplary embodiments for navigating between multiple user interfaces represented in a user interface selection mode in accordance with some embodiments, including the ability to "peek" and "pop" an application (e.g., and associated user interfaces) from a display of multiple user interface representations using user input detected on a touch-sensitive surface (e.g., a touch-sensitive display separate from the display or a touch-sensitive trackpad).

Figures 8A-8D illustrate an embodiment in which a user "pops up" (e.g., selects) a user interface for display on a device using a high-intensity user input (e.g., a deep press). Figure 8A illustrates the display of user interface 506 for user interface selection mode, which includes a representation 508 of web browsing user interface 502 ("web browsing card 508"), a representation 510 of messaging user interface 507 ("messaging card 510"), and a representation 526 of photo management user interface 524 ("photo card 526") in a user interface previously displayed on the device. The user interface representations are displayed in a card stack (extending rightward from the base of the stack). Each card is sorted in a z-layer (e.g., substantially orthogonal to the plane of touch screen 112) and laterally offset to the right of the card below it, thereby revealing a portion of each card.

Device 100 detects that the intensity of contact 802 at the location corresponding to the display of messaging card 510 increases from FIG5A to FIG5B . In response, the display area of messaging card 510 increases by moving web browsing card 508 further to the right (e.g., from position 508 - a in FIG8A to position 508 - b in FIG8B ) (e.g., the user glances at messaging card 510).

As shown in Figure 8C, the display of the relative lateral positions of the cards is dynamically linked to the amount of pressure detected for the user contact. For example, in response to detecting a small decrease in the pressure of contact 802 from Figure 8B to Figure 8C, web browsing card 508 begins to move back over messaging card 510 (e.g., web browsing card 508 moves from position 508-b in Figure 8B to position 508-c in Figure 8C). In some embodiments, an animation is displayed to illustrate the movement of user interface representations relative to each other in a manner that dynamically responds to small changes in the intensity of the contact.

Device 100 then detects a further increase in pressure of contact 802 beyond a characteristic intensity (e.g., a deep press intensity threshold (IT _D )). In response, messaging card 510 is "popped" from the stack, and the device opens the associated application (e.g., replacing display of user interface 506 for user interface selection mode with display of user interface 507 for the messaging application).

Figures 8E-8F illustrate an embodiment in which a "pop-up" card (e.g., selecting an application and corresponding user interface) includes an animation. Figure 8E illustrates selecting (e.g., "pop-up") a messaging card in response to detecting an increase in pressure on contact 802 exceeding a characteristic intensity (e.g., a deep press intensity threshold ( _ITD )). In response, device 100 displays an animation that transitions from displaying user interface 506 for a user interface selection mode to displaying user interface 507 for a messaging application. The animation includes sliding web browsing card 508 completely away from messaging card 510 (e.g., by moving the web browsing card further to the right to position 508-d). The animation also includes removing messaging card 510 from the stack and gradually increasing the size of messaging card 510, e.g., until the display of user interface 507 fills the entire touch screen 112 (e.g., as illustrated by moving the messaging card from position 510-b in Figure 8E to position 510-c in Figure 8F) to provide the effect of the card moving toward the user in a virtual z-dimension.

Figures 8G-8H illustrate an alternative embodiment for "peek" user interface representation cards. Figure 8G illustrates the display of the user interface card stack as described with respect to Figure 8A (e.g., wherein web browsing card 508 is displayed on top of and offset to the right of messaging card 510, which is displayed on top of and offset to the right of photo card 526). Figure 8G also illustrates contact 804 at a location on touch screen 112 corresponding to the display of messaging card 510.

Figure 8H illustrates that in response to detecting an increase in the intensity of contact 804 when displayed over messaging card 510, more area of the messaging card is revealed. However, rather than sliding web browsing card 508 to the right away from messaging card 510, Figure 8H illustrates moving messaging card 510 to the left (e.g., the messaging card moves from position 510-a in Figure 8G to position 510 in Figure 8H), as if it were being removed from the deck. Thus, Figures 8G and 8H illustrate using the intensity of contact (e.g., 804) to reveal more of the user interface representation card in the stack by sliding the card out of the stack in a direction opposite to the direction the stack expands from the base of the stack.

8I illustrates another alternative embodiment for “peek” messaging card 510, wherein in response to detecting an increase in the intensity of contact 804 displayed at a location corresponding to the display of messaging card 510, web browsing card 508 moves to the right away from messaging card 510, and messaging card 510 is pulled to the left from the deck. Thus, FIG8G and 8I illustrate using the intensity of contact (e.g., 804) to reveal more of a corresponding user interface representation card in the stack by sliding the card out of the stack in a direction opposite to the direction the stack expands from the base of the stack, and further sliding the card displayed in a direction above the corresponding user interface representation card in the direction the stack expands from the base of the stack.

Figures 8J-8R illustrate expanded "peek" and "pop" navigation, where multiple cards are peeked at before an application is popped open. Figure 8J illustrates display of a graphical user interface 502 for a web browsing application on an electronic device. Figure 8K illustrates the device entering a user interface selection mode upon detecting user input comprising a contact 806 adjacent to a left edge of touch screen 112 (e.g., on a bezel) having a characteristic intensity (e.g., an intensity exceeding a deep press intensity threshold ( _ITD ); e.g., an exemplary predetermined input). In response to activating the user interface selection mode, device 100 replaces display of web browsing user interface 502 with user interface 506 for user interface selection mode as shown in Figure 8K.

Figure 8K illustrates display of the user interface card stack as described for Figure 8A (e.g., with web browsing card 508 displayed on top of and offset to the right of messaging card 510, which is displayed on top of and offset to the right of photo card 526). Figure 8K also illustrates contact 806 at a location 806-a corresponding to the left edge of touch screen 112 and with an intensity exceeding a deep press intensity threshold ( _ITD ).

8L , device 100 detects that the intensity of user contact 806 decreases below a deep press intensity threshold (IT _D ). Device 100 also detects that contact 806 moves 808 from the left edge of the display (e.g., position 806 - a in FIG. 8K ) to a position corresponding to the display of messaging card 510.

8M illustrates detecting an increase in intensity of user contact 806 while displayed over messaging card 510 , resulting in a “peek” at messaging card 510 via moving the web browsing card away from messaging card 510 .

Figure 8N illustrates detecting a decrease in the intensity of user contact 806. In response, web browsing card 508 moves back over messaging card 510. The device also detects that contact 806 continues to move 808 from position 806-b in Figure 8N to position 806-c in Figure 8O corresponding to the display of photo card 526.

8P illustrates detecting an increase in intensity of contact 506 while displayed over photo card 526, and in response, glancing at photo card 526 by moving display of web browsing card 508 and messaging card 510 to the right.

FIG8Q illustrates detecting that the intensity of contact 806 further increases beyond a predefined intensity threshold (e.g., a deep press intensity threshold (IT _D )) while displayed over photo card 526. In response, the contact "pops" photo card 526, as illustrated by moving web browsing card 508 and messaging card 510 completely away from photo card 526. Photo card 526 then expands (e.g., via a dynamic animation) to fill the entire touch screen 112 with user interface 524 when the electronic device enters the photo management application in FIG8R .

Figures 9A-9H illustrate exemplary user interfaces for navigating between user interfaces in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, 15, 24A-24F, and 25A-25H. Although some of the following examples will be given with reference to input on a touch screen display (where a touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from the display 450, as shown in Figure 4B.

9A illustrates the display of user interface 506 for a user interface selection mode, which includes a display of a stack of user interface representations, such as user interface representation cards 508, 510, and 526 for web browsing user interface 502, messaging user interface 507, and image management user interface 524. As described with respect to FIGs. 5A-5HH, the user interface representation cards spread out from the base of the stack to the right and are ordered relative to each other in Z positions (e.g., representation 508 is offset laterally to the right of representation 510 and ordered above representation 510 along the Z axis).

Device 100 detects user input including contact 902 at a location on touch screen 112 corresponding to display of user interface representation 526. Contact 902 has a characteristic intensity below a predefined intensity threshold (e.g., below a deep press intensity threshold (IT _D )). In response to detecting contact 902 at a location corresponding to display of photo card 526, device 100 reveals more of photo card 526 by moving messaging card 510 and web browsing card 508 from positions 510 - a and 508 - a in FIG. 9A to the right (e.g., away from photo card 526) to positions 510 - b and 508 - b in FIG. 9B . Device 100 then detects contact 902 moving from over photo card 526 to over messaging card 510 (e.g., from position 902 - a in FIG. 9B to position 902 - b in FIG. 9C ).

As shown in Figures 9C-9D, in response to contact 902 moving to a position corresponding to display of the messaging card 510, the device 100 reveals more of the messaging card 510 by moving the messaging card 510 from under the web browsing card 508 and back toward the stack (e.g., to the left on the display 112) from position 510-b in Figure 9C to position 510-c in Figure 9D.

Figures 9E-9F illustrate an embodiment in which an application is selected from user interface selection mode by lifting a contact displayed at a location above a user interface representation card associated with the application. Device 100 detects the lifting of contact 902 while positioned over messaging card 510 (e.g., terminating user input that includes contact 902 at a location corresponding to the display of card 510 on touch screen 112), thereby selecting the messaging application associated with messaging card 510. In response, device 100 replaces the display of user interface 506 with the display of user interface 507 corresponding to user interface representation card 510. For example, device 100 opens the messaging application associated with user interface 507 because contact 902 was above the corresponding card when the user lifted the contact.

Figures 9G-9H illustrate an alternative embodiment in which an application is selected from user interface selection mode by "popping" the application with a deep press gesture. Continuing from Figures 9A-9D, while contact 902 is positioned over messaging card 510, device 100 detects an increase in the intensity of contact 902 exceeding a predefined intensity threshold (e.g., a deep press intensity threshold ( _ITD )). In response, device 100 replaces the display of user interface 506 with the display of user interface 507 corresponding to user interface representation card 510. For example, device 100 opens the messaging application associated with user interface 507 because contact 902 was over the corresponding card when the deep press was detected.

Figures 22A-22BA illustrate exemplary user interfaces for performing application-independent operations (e.g., system-wide actions) such as navigating between user interfaces in accordance with some embodiments. In some embodiments, this is achieved by a user interface that distinguishes between at least two types of input originating from an edge of the touch screen and, in response, performs a system-wide operation upon detection of a first type of input and performs an application-specific operation upon detection of a second type of input. In some embodiments, the two types of operations are distinguished based on at least their proximity to the edge of the touch-sensitive surface and a characteristic intensity of the contact included in the input.

The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, 15, 24A-24F, and 25A-25H. Although some of the following examples will be given with reference to input on a touch screen display (in which the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from the display 450, as shown in Figure 4B.

Figures 22A-22D illustrate embodiments in which, according to some embodiments, the device detects two inputs that meet system gesture strength criteria and, based on the proximity of the inputs to the edge of the touch screen, determines whether to perform an application-specific action or a system-wide action. Figure 22A illustrates a web browsing user interface 502 with two position boundaries 2202 and 2204. Position boundary 2202 defines an area of the touch screen 112 to the left of the boundary (e.g., the area extending to the left of the touch screen) in which a contact must be detected in order to activate a system-wide action, such as entering a user interface selection mode (e.g., when the contact also meets the strength criteria). Position boundary 2204 defines a larger area of the touch screen 112 to the left of the boundary (e.g., the area extending to the left of the touch screen) in which a contact must be detected in order to activate a system-specific action, such as navigating to a previous user interface displayed within the active application (e.g., when the contact also meets the strength criteria).

In Figure 22B, the device detects contact 2206 having a characteristic intensity above a threshold intensity required to perform a system-wide action (e.g., intensity threshold IT _L ). Contact 2206 also meets the system-wide action location criteria because it is detected to the left of boundary 2202. Thus, although the contact also meets the application-specific action criteria, in response to detecting movement of the contact to the right, as indicated by replacing web browsing user interface 502 with multitasking user interface 506 in Figure 22C, the device enters user interface selection mode.

In Figure 22D, the device detects contact 2212 having a characteristic intensity above a threshold intensity required to perform both a system-wide action (e.g., intensity threshold IT _L ) and an application-specific action. However, contact 2212 does not meet the system-wide action location criteria because it is detected to the right of boundary 2202. Because contact 2212 meets the application-specific location criteria, in response to detecting movement of the contact to the right, as indicated by replacing web browsing user interface 502 with web browsing user interface 616 in Figure 22E, the device navigates to the previously viewed user interface within the web browsing application.

Figures 22F-22G illustrate an embodiment in which the device adjusts the position criteria required to perform a system-wide action in response to the shape of the detected contact. In Figure 22F, the device detects contact 2214 having a characteristic intensity above a threshold intensity (e.g., intensity threshold IT _L ) required to perform a system-wide action. However, contact 2214 does not meet the default system-wide action position criteria because it is detected to the right of boundary 2202. However, because the contact is wider and more elongated than a typical fingertip contact (e.g., this indicates that the user extends their thumb to reach the left side of the device), the device adjusts the system-wide action position criteria so that the contact detected to the left of boundary 2204 meets the position criteria. Therefore, in response to detecting that the contact moves to the right, the device enters user interface selection mode, as indicated by replacing web browsing user interface 502 with multitasking user interface 506 in Figure 22G.

Figures 22H-22I illustrate an embodiment in which the device detects a contact that meets the system-wide action location criteria, but does not meet the system-wide action intensity. In Figure 22H, the device detects contact 2218 that meets the location requirements for performing the system-wide action (e.g., because it is detected to the left of boundary 2202). However, contact 2218 has a characteristic intensity below the threshold intensity required to perform the system-wide action criteria (e.g., intensity threshold IT _L ). Because contact 2218 meets the application-specific intensity criteria, in response to detecting that the contact is moving to the right, as indicated by replacing web browsing user interface 502 with web browsing user interface 616 in Figure 22I, the device navigates to the previously viewed user interface within the web browsing application.

22J-22N illustrate an embodiment in which the boundaries defining the system-wide action location criteria are located beyond the left edge of the touch screen 112. Fig. 22J illustrates the web browsing user interface 502 with location boundaries 2222 and 2224 defining the right edge of the location requirements for performing system-wide and application-specific actions.

In FIG22K , the device detects contact 2226 having a characteristic intensity above a threshold intensity required to perform a system-wide action (e.g., intensity threshold IT _L ). Because the device determines that the user's finger used to make contact 2226 must extend to the left beyond touch screen 112 (e.g., based on the shape and size of the contact), the device projects (e.g., virtually) where the contact would extend if the touch screen were wider, as indicated by the dashed line in FIG22K . Since the farthest point in the projected contact is to the left of location boundary 2222, contact 2226 also meets the system-wide action location criteria. Therefore, in response to detecting that the contact has moved to the right, as indicated by replacing web browsing user interface 502 with multitasking user interface 506 in FIG22L , the device enters user interface selection mode.

In FIG22M , the device detects contact 2230 having a characteristic intensity above a threshold intensity required to perform a system-wide action (e.g., intensity threshold IT _L ). The device then projects the leftmost boundary of where contact 2230 will be located beyond the edge of touch screen 112. Because the farthest point in the projected contact is to the right of location boundary 2222, contact 2226 does not meet the system-wide action location criteria. Because contact 2230 meets the application-specific location criteria, in response to detecting that the contact has moved to the right, the device navigates to the previously viewed user interface within the web browsing application, as indicated by replacing web browsing user interface 502 with web browsing user interface 616 in FIG22N .

22O-22R illustrate an embodiment in which the device does not extend the system-wide action location boundary in response to detecting a larger contact when a contact is detected in an upper corner or a lower corner of touch screen 112. Thus, when the device detects a wider contact in FIG22P that would satisfy the modified location criteria, the device performs an application-specific action rather than a system-wide action as shown in FIG22R.

Figures 22S-22AA illustrate an embodiment in which the device modifies the system-wide action location boundaries as the contact travels faster on the touch screen to allow for further buffering for users who are rushing to perform gestures. As shown in Figures 22S-22U, when a gesture meets both the speed and intensity criteria within buffer 250, the device still performs the system-wide action. As shown in Figures 22V-22X and 22Y-22AA, when a gesture does not simultaneously meet all three criteria, the device does not perform the system-wide action.

Figures 22AB-22AG illustrate an embodiment in which the gesture further includes a directional criterion. When the gesture satisfies the directional criterion, as shown in Figures 22AB-22AD, the device performs a system-wide action. When the gesture does not satisfy the directional criterion, as shown in Figures 22AE-22AG, the device does not perform the system-wide action.

Figures 22AH-22AO illustrate an embodiment in which a system-wide action is still performed when the device first detects input outside the location boundaries, but the contact is moved into the location boundaries and then meets the strength criteria, as shown in Figures 22AH-22AK rather than Figures 22AL-22AO.

22AP-22AS illustrate an embodiment in which the device blocks system-wide actions if input is ever detected at a location outside of buffer 2286.

Figures 22AT-22AY illustrate an embodiment in which the system-wide action intensity criterion is higher during the period immediately after a contact on the screen is detected. If the contact moves outside the activation zone before achieving the higher intensity requirement, the device does not perform the system-wide action as shown in Figures 22AT-22AU. If the contact achieves the higher intensity requirement before moving outside the activation zone or waits for the intensity threshold to drop, the device performs the system-wide action as shown in Figures 22AW-22AY.

Figures 22AZ-22BA illustrate an embodiment in which the system-wide motion intensity standard is higher near the top and bottom of the touch screen.

Figures 23A-23AT illustrate exemplary user interfaces for performing application-independent operations (e.g., system-wide actions) such as navigating between user interfaces in accordance with some embodiments. In some embodiments, this is accomplished by distinguishing how far a contact (e.g., as described above with respect to method 2400 and Figures 22A-22BA) has traveled across the touch screen to meet activation criteria.

The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, 15, 24A-24F, and 25A-25H. Although some of the following examples will be given with reference to input on a touch screen display (in which the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from the display 450, as shown in Figure 4B.

FIG23A illustrates a web browsing user interface 502 with position boundaries 2302 and 2312. When a contact meeting the system-wide motion activation criteria does not cross boundary 2302, the device does not navigate to a new user interface upon termination of input, as shown in FIG23B-23D. When a contact meeting the system-wide motion activation criteria crosses boundary 2302 but not boundary 2312, the device navigates to a user interface selection mode, as shown in FIG23E-23G. When a contact meeting the system-wide motion activation criteria crosses both boundary 2302 and boundary 2312, the device navigates to the last user interface active on the device, as shown in FIG23I-23K.

23L-23R illustrate an embodiment in which the device provides visual feedback as the user approaches and crosses over position boundaries 2302 and 2312. The feedback is dynamic and reverses when the contact moves in the opposite direction on the touch screen.

Figures 23Q-23T illustrate an embodiment in which the device provides a prompt that the intensity of the contact is approaching the intensity threshold required to activate a system-wide action. For example, as the intensity of contact 2326 approaches intensity threshold IT _L , the device begins to slide rightward over active user interface 502, thereby revealing previously active user interface 507. In Figure 23S, in response to detecting that the intensity of contact 2326 further increases above intensity threshold 2326, the device activates a system-wide action, thereby allowing navigation between user interfaces (e.g., by sliding the contact rightward into one of the three zones). In Figure 23T, in response to detecting that the intensity of contact 2326 further increases above deep press intensity threshold IT _D , the device enters multitasking user interface selection mode, as indicated by replacing web browsing user interface 502 with multitasking user interface 506 in Figure 23T.

Figures 10A-10H illustrate a flow diagram of a method 1000 for navigating between user interfaces in accordance with some embodiments. Method 1000 is performed on an electronic device having a display and a touch-sensitive surface (e.g., device 300 of Figure 3 or portable multifunction device 100 of Figure 1A). In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on or integrated with the display. In some embodiments, the display is separate from the touch-sensitive surface. In some embodiments, the touch-sensitive surface is a portion of a trackpad or remote control device that is separate from the display. In some embodiments, the operations in method 1000 are performed by an electronic device configured to manage, play back, and/or stream (e.g., from an external server) audio and/or visual files that communicates with a remote control and display (e.g., an Apple TV from Apple Inc. of Cupertino, California). Some operations in method 1000 may optionally be combined, and/or the order of some operations may optionally be changed.

As described below, method 1000 provides an intuitive way to navigate between user interfaces. The method reduces the number, extent, and/or nature of input from a user when navigating between user interfaces, thereby creating a more efficient human-computer interface. For battery-operated electronic devices, enabling users to navigate between user interfaces faster and more efficiently conserves power and increases the time between battery charges.

In some embodiments, the device displays (1002) a first user interface on a display. For example, a user interface for opening an application (e.g., user interface 502 for a web browsing application in Figures 5A-5B, 6A-6B, 6D, 6M, 6O, 6S-6T, 7A-7B, and 7O, user interface 616 for a web browsing application in Figures 6P and 6U, user interface 507 for a messaging application in Figures 5CC, 6Q, 7F, 7J-7L, 8D, 8J, 9F, and 9H, or user interface 526 for an image management application in Figure 8R). The first user interface corresponds to a first user interface representation among a plurality of user interface representations. For example, as further described below, the user interface representation, in some embodiments, corresponds to user interfaces of open applications, currently and previously viewed user interfaces for a single application (e.g., open user interfaces for a web browsing application, each open user interface displaying the same or a different website; or a history of previously viewed user interfaces for a web browsing application—e.g., corresponding to at least a portion of a browser history), messages in an email chain, menu options in a menu hierarchy (e.g., selection of files such as audio and/or visual files for playback or streaming), and the like.

While displaying a first user interface, the device detects (1004) a predetermined input. For example, a double tap or double press on a "home" button on the device; or, for an electronic device that includes one or more sensors for detecting intensity of contact with a touch-sensitive display, a deep press on a predetermined area (e.g., the upper left corner) of the first user interface; a deep press with the flat portion of a thumb anywhere on the first user interface; or a deep press on a predetermined area of the device, such as on the left edge of a touch-sensitive surface (e.g., a touch-sensitive display separate from the display or a touch-sensitive trackpad), in a predefined area adjacent to an edge (e.g., the left edge) of a touch-sensitive surface (e.g., a touch-sensitive display). For example, a deep press on a bezel or a predetermined area of a bezel (e.g., a bezel adjacent to the left edge of the touch-sensitive surface) (e.g., deep presses 504 in FIG. 504 , 608 in FIG. 6H , 612 in FIG. 6M , and 806 in FIG. 8K ).

In response to detecting a predetermined input (1005), the device enters (1006) a user interface selection mode and displays (1008) a plurality of user interface representations in a stack, wherein at least a portion of a first user interface representation is visible and at least a portion of a second user interface representation is visible. For example, in response to detecting deep press 504 in FIG. 5B , multifunction device 100 displays user interface representations 508 (corresponding to user interface 502 of the web browsing application displayed on the screen when the initiating input is detected) and 510 (corresponding to user interface 507 of the messaging application) in FIG. 5C and 5D .

In some embodiments, a representation of the user interface that was displayed on the screen immediately before entering user interface selection mode is displayed on top of the stack, or as the first representation corresponding to an open application (e.g., when a home screen or one or more representations of transient applications are also displayed upon entering user interface selection mode). For example, in Figure 5C, user interface representation 508 (corresponding to user interface 502 displayed when deep press 504 is detected) is displayed above user interface representation 507 in the stack.

In some embodiments, a representation of a user interface displayed on the screen immediately before entering user interface selection mode is displayed below at least a second user interface representation (e.g., a representation of a user interface displayed immediately before display of the user interface displayed when user interface selection mode was initiated.) For example, in FIG5D , user interface representation 508 (corresponding to user interface 502 displayed when deep press 504 was detected) is displayed below user interface representation 507 in the stack.

In some embodiments, the device displays a second user interface on the display, where the second user interface corresponds to a second user interface representation in a plurality of user interface representations (e.g., as shown in FIG5D , the representation of the user interface displayed when the user interface selection mode is initiated is displayed as a second representation in the stack). While displaying the second user interface, the device detects a predetermined input. In response to detecting the predetermined input, the device enters the user interface selection mode and displays the stack with at least a portion of the first user interface representation visible and at least a portion of the second user interface representation visible.

In some embodiments, in response to detecting a predetermined input for entering a user interface selection mode, at least a portion of a third user interface representation is visibly displayed. For example, in response to detecting deep press 504 in Figure 5B, multifunction device 100 displays user interface representations 508, 510, and 526 in Figures 5E and 5F (corresponding to user interface 524 of the image management application).

In some embodiments, the remaining representations in the stack are off-screen or below the first, second, and optional third representations that include visible information. For example, Figure 5E illustrates an indication 503 (e.g., an image representing an edge or actual edge of an additional user interface representation) below third user interface representation 526 in Figures 5E and 5F.

In some embodiments, in response (1005) to detecting a predetermined input: the device stops displaying (1010) a status bar on the display. Before entering the user interface selection mode and displaying the stack, the status bar is displayed concurrently with the corresponding user interface. For example, before the device enters the user interface selection mode, status bar 503 is displayed on user interface 502 in FIG. 5A . Upon detecting a deep press 504 in FIG. 5B , as shown in FIG. 5E , the device enters the user interface selection mode (e.g., as indicated by displaying the stack in FIG. 5E ), which does not include display of status bar 503 in corresponding user interface 506. In some embodiments, as shown in FIG. 5C , the user interface for the user interface selection mode (e.g., user interface 506) includes display of a status bar (e.g., status bar 503).

In some embodiments, the status bar includes the current time, battery level, cellular signal strength indicator, WiFi signal strength indicator, etc. The status bar is typically always displayed with the user interface of the open application. In some embodiments, removing the status bar provides the user with the following indication: the stack in the user interface selection mode is not a normal user interface of the application, but is instead a system user interface configured for navigating, selecting, and managing (e.g., closing) the open applications on the device. In some embodiments, tactile feedback is provided when entering the user interface selection mode.

Method 1000 includes a device (e.g., multifunction device 100) displaying (1012) a plurality of user interface representations in a stack on a display. In some embodiments, the plurality of user interface representations may resemble a stack of cards (or other objects) representing user interfaces of open applications in a z-order (e.g., positioned relative to each other along a z-axis substantially orthogonal to the plane of the display on the device to provide the effect of the cards being stacked one on top of the other), cards representing currently and previously viewed user interfaces of a single application, cards representing messages in an email chain, cards representing different menu options in a menu hierarchy, and the like. For example, Figures 5E and 5F illustrate a stack including representations 508, 510, and 526 of user interfaces of open applications. In the z-order, representation 508 is displayed as the top card, representation 510 as the middle card, and representation 526 as the bottom card. In some embodiments, such as shown in Figure 5E, the stack is displayed as a substantially two-dimensional representation (although in some embodiments, the z-order of the cards is still maintained). In some embodiments, such as shown in Figure 5F, the stack is displayed as a substantially three-dimensional representation.

At least a first user interface representation (e.g., a card representing an application that was displayed immediately before the stack was displayed in a user interface selection mode, such as a mode for selecting among open applications, a mode for selecting among user interfaces within a single open application, or a mode for selecting among menu items in a menu (e.g., a menu in a menu hierarchy for a set-top box, etc.) and a second user interface representation (e.g., a card representing another open application, a transient application, or a home screen or application springboard) disposed above the first user interface representation in the stack are visible on the display. For example, first user interface representation 510 is displayed below second user interface representation 508 in Figures 5E-5F.

The second user interface representation is offset from the first user interface representation in a first direction (eg, offset laterally to the right on the display). For example, the second user interface 508 is offset to the right of the center of the first user interface representation 510 in Figures 5E-5F.

The second user interface representation partially exposes the first user interface representation. In some embodiments, the representations in the stack are partially expanded in one direction on the display (e.g., to the right as shown in Figures 5E-5F). In some embodiments, at a given time, information (e.g., icons, titles, and content for the corresponding user interface) for a predetermined number of representations in the stack (e.g., 2, 3, 4, or 5 representations) is visible, while the remaining representations in the stack are off-screen or below the representations that include visible information. In some embodiments, the representations below the representations that include visible information are stacked closely together so that no information is displayed for these representations. In some embodiments, the representations below the representations that include visible information are style representations, such as only the common edges 503 of these representations, as shown in Figures 5E-5F.

In some embodiments, the respective user interface representations have corresponding positions in the stack 1014. For example, as shown in FIG5P , user interface representation 508 has a corresponding first position in the stack, user interface representation 510 has a corresponding second position in the stack, and user interface representation 526 has a corresponding third position in the stack.

In some embodiments, for a respective user interface representation visible on the display: the device determines (1016) a respective relative z position of the user interface representation as compared to one or more other user interface representations that are simultaneously visible on the display; and applies (1018) a blur level to the user interface representation based on the relative z position (relative height in the z dimension or relative z level in the stack) of the user interface representation as compared to one or more other user interface representations that are simultaneously visible on the display.

For example, in some embodiments, upon entering application selection mode, the UI representation stack represents a stack of open applications, with underlying UI representations corresponding to open applications that have not been viewed for a longer period of time, and more blur is applied to the UI representations of those applications than to UI representations of more recently viewed open applications. In some embodiments, the UI representation for the most recently viewed application is unblurred; the UI representation for the next most recently viewed application is blurred by a first amount; the UI representation for an even earlier open application is blurred by a second amount that is greater than the first amount; and so on. For example, as shown in FIG5P , device 100 applies little or no blur to UI representation 508 because the card has a first relative z position at the top of the cards simultaneously visible on touch screen 112. Device 100 applies a moderate blur to UI representation 510 because the card has a second relative z position in the middle of the cards simultaneously visible on touch screen 112. Device 100 applies a heavy blur to UI representation 526 because the card has a third relative z position at the bottom of the cards simultaneously visible on touch screen 112.

In some embodiments, the respective user interface representations have corresponding simulated absolute z positions in the stack.For the user interface representations visible on the display, the device applies (1020) a blur level to the user interface representations according to their corresponding simulated absolute z positions in the z dimension.

In some embodiments, for example, the z dimension is a dimension perpendicular (e.g., substantially orthogonal) to the plane of the display, or a lateral direction of the space represented on the display. In some embodiments, a level of blur applied to each of the user interface representations visible on the display is determined based on a simulated absolute z position of the user interface representation. In some embodiments, the change in the level of blur applied to each user interface representation is gradual and directly related to the current simulated absolute z position of the user interface representation. In some embodiments, the stack of user interface representations moves in the x-direction on a concave increasing x-z curve, and a gap between each pair of adjacent user interface representations in the z-direction is maintained at a constant value during movement of the user interface representations along the x-z curve in the x-direction.

In some embodiments, the respective user interface representation is associated with a respective title area (e.g., a title bar, such as title bar 512 associated with user interface representation 508 in FIG. 5C and title bar 520 associated with user interface representation 510 in FIG. 5D ) having respective title content (e.g., the title area includes an icon (e.g., icon 516 in FIG. 5C and title 518 in FIG. 5D ) and the name of the application represented by the user interface representation (or the name of a web page, menu, etc., such as “Safari” 514 in FIG. 5C and “Messages” 520 in FIG. 5D )). In some embodiments, for a user interface representation that is currently visible below an adjacent user interface representation on the display, as the adjacent user interface representation approaches (e.g., as user interface representation 510 slides over user interface representation 526 in Figure 5DD), the device applies (1022) a visible effect (e.g., a blur, a fade, and/or a clipping as shown in Figure 5DD) to at least a first portion of the title content of the user interface representation (e.g., only the title text portion of the title content, such as the fading of "Photos" 532 in Figure 5DD; or both the title text and the icon in the title content, such as the fading of both "Photos" 532 and icon 528 in Figure 5DD).

In some embodiments, as the title area of an adjacent user interface representation or an adjacent user interface representation moves within a threshold lateral distance on the display of the title content, the device applies (1024) a visible effect to the title text in the title content while maintaining the original appearance of the icons in the title content. For example, as user interface representation 510 moves to position 510-b adjacent to "Photos" 532 before icon 526 fades away, "Photos" 532 fades away in Figure 5DD.

In some embodiments, the stack includes (1026) a user interface representation for a home screen (e.g., a representation of any of one or more user interfaces accessible immediately after the device is booted up, such as a notification center, a search UI, or a springboard or dashboard showing applications available on the device, such as representation 554 of user interface 552 of the home screen in FIG. 5Q ), zero or more transient application user interface representations (e.g., a user interface for an incoming or ongoing phone or IP call session (e.g., user interface representation 554 for user interface 556 for an incoming phone call in FIG. 5W ), a user interface showing the handover of one or more application sessions from different devices, a user interface for recommending applications, a user interface for a print session, etc.), and one or more open application user interface representations (e.g., a current application being viewed just prior to entering user interface selection mode, a previous application preceding the current application, and representations of other earlier open applications (e.g., user interface representations 508, 510, and 526 in FIGs. 5E-5F )).

As used in this specification and claims, the term "open application" refers to a software application that has maintained state information (e.g., as part of device/global internal state 157 and/or application internal state 192). An open application is any of the following types of applications:

The active application, which is currently displayed on the display 112 (or the corresponding application view currently displayed on the display);

Background applications (or background processes), which are not currently displayed on the display 112 , but for which one or more application processes (e.g., instructions) are being processed (i.e., running) by the one or more processors 120 ;

Suspended applications, which are not currently running and are stored in volatile memory (e.g., DRAM, SRAM, DDR RAM, or other volatile random access solid-state memory devices of memory 102); and

• Dormant applications, which are not running and are stored in non-volatile memory (eg, one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices of memory 102).

As used herein, the term "closed application" refers to a software application that has no retained state information (e.g., state information for a closed application is not stored in the device's memory). Thus, closing an application includes stopping and/or removing application processing for the application and removing state information for the application from the device's memory. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application is no longer displayed, the first application that was the active application when displayed may become a background application, a suspended application, or a dormant application, but the first application remains an open application and its state information is retained by the device.

In some embodiments, user interface representations for the home screen are displayed above transient application user interface representations, which are in turn displayed above open application user interface representations, in a z-order. As used herein, a "z-order" is a front-to-back order of displayed objects (e.g., user interface representations). Thus, if two objects overlap, an object that is higher in the layer order (e.g., an object that is "on top of," "in front of," or "above") is displayed at any point where the two objects overlap, thereby partially obscuring an object that is lower in the layer order (e.g., an object that is "below," "behind," or "behind" another object). A "z-order" is also sometimes referred to as a "layer order," "z-order," or "front-to-back object order."

In some embodiments, the transient application user interface representation includes (1028) a phone interface representation for an active or missed call, a continuity interface representation for suggested applications, a continuity interface representation for a handover from another device, and a printer interface representation for an active print job.

Method 1000 also includes the device detecting (1030) a first drag gesture by a first contact at a location on the touch-sensitive surface corresponding to a location of the first user interface representation on the display (e.g., device 100 detects a drag gesture comprising contact 530 and movement 532 on touch screen 112 in FIG. 5G ) at a location corresponding to the display of user interface representation 510, the first contact moving across the touch-sensitive surface in a direction corresponding to the first direction on the display (e.g., movement 532 of contact 530 moves from left to right across touch screen 112 in FIG. 5G-5I ).

When a first contact is moved across the touch-sensitive surface at a location on the touch-sensitive surface corresponding to a location of a first user interface representation on the display and in a direction corresponding to a first direction on the display (1032): the device moves (1034) the first user interface representation (e.g., user interface representation 510 in Figures 5G and 5R) in a first direction on the display at a first speed, based on a velocity of the first contact on the touch-sensitive surface. For example, on the touch-sensitive display (e.g., touch screen 112), a card or other representation under the finger contact moves at the same speed as the finger contact (e.g., as shown by the constant positional relationship between the display of the user interface representation and the contact on touch screen 112, user interface representation 510 moves at the same speed as contact 530 in Figures 5G-5I and user interface representation 510 moves at the same speed as contact 556 in Figures 5R-5). On a display coupled to a track pad, the card or other representation at the location corresponding to the location of the contact moves at an on-screen velocity corresponding to (or based on) the velocity of the finger contact on the track pad. In some embodiments, a focus selector is shown on the display to indicate the on-screen location corresponding to the location of the contact on the touch-sensitive surface. In some embodiments, the focus selector may be represented by a cursor, a movable icon, or a visual distinguisher that separates an on-screen object (eg, a user interface representation) from its non-focused counterpart.

While the first contact is at a location on the touch-sensitive surface corresponding to the location of the first user interface representation on the display and moves across the touch-sensitive surface in a direction corresponding to the first direction on the display (1032): the device also moves (1036) a second user interface representation (e.g., user interface representation 508 in Figures 5G and 5R) that is disposed above the first user interface representation at a second speed in the first direction that is greater than the first speed.

In some embodiments, the first direction is rightward. In some embodiments, the first speed is the same speed as the current speed of the contact. In some embodiments, this movement of the first user interface representation creates the visual effect that the finger contact is grabbing and dragging the first user interface representation. Simultaneously, the second user interface representation is moving faster than the first user interface representation. This faster movement of the second user interface representation creates the visual effect of revealing a larger and larger portion of the first user interface representation from beneath the second user interface representation as the second user interface representation moves toward the edge of the display in the first direction. For example, as second user interface representation 508 moves toward the right on the display at a greater speed than first user interface representation 510, as shown in Figures 5G-5H, more of user interface representation 510 is revealed when displayed at position 510-b than when displayed at position 510-a before the rightward movement. Combined, these two simultaneous movements enable the user to see more of the first user interface representation before deciding whether to select and display the corresponding first user interface.

In some embodiments, the stack includes at least a third user interface representation (e.g., user interface representation 526 in Figures 5E-5F ) disposed below the first user interface representation. The first user interface representation is offset from the third user interface representation in a first direction (e.g., user interface 510 is offset to the right of user interface representation 526 in Figures 5E-5F ). The first user interface representation partially exposes the third user interface representation. When a first contact is at a location on the touch-sensitive surface that corresponds to the first user interface representation on the display and the first contact moves across the touch-sensitive surface in a direction corresponding to the first direction on the display: the device moves 1038 the third user interface representation disposed below the first user interface representation in the first direction at a third speed that is less than the first speed.

For example, a third user interface representation below a first user interface representation (e.g., a card below the finger contact) moves at a slower speed than the first user interface representation, thereby exposing more of the third user interface representation as the finger contact moves across the touch-sensitive surface in a direction corresponding to the first direction on the display. For example, Figure 5O illustrates representative speeds of user interface representations 508 (e.g., the second user interface representation), 510 (e.g., the first user interface representation), and 526 (e.g., the third user interface representation) relative to movement 532 of contact 530 in Figures 5G-5I.

In some embodiments, one or more user interface representations below the third user interface representation are simultaneously revealed as the third user interface representation moves in a first direction (e.g., to the right). For example, as shown in Figures 5H-5I, as third user interface representation 526 moves to the right in response to detecting user input including contact 530 and movement 532, user interface representations 534 and 540 are revealed.

In some embodiments, the difference between the second speed and the first speed maintains (1040) a first constant z-position difference between the second user interface representation and the first user interface representation. The difference between the first speed and the third speed maintains a second constant z-position difference between the first user interface representation and the third user interface representation. The first constant z-position difference is the same as the second z-position difference. In some embodiments, the cards travel on a concave increasing x-z curve, wherein the z spacing between adjacent cards is maintained as the cards move along the x-direction. Because the slope of the curve decreases with increasing x-position, the cards move at increasingly higher speeds in the x-direction as their current x-position increases.

In some embodiments, the difference between the second speed and the first speed is equal to the difference between the first speed and the third speed (1042).

In some embodiments, the ratio between the second speed and the first speed is equal to the ratio between the first speed and the third speed (1044).

In some embodiments, while a third user interface representation disposed below a first user interface representation is moved in a first direction at a third speed (1046) (e.g., moving user interface representation 526 to the right on touch screen 112 in Figures 5G-5I at a relative speed that is less than the speed at which user interface 510 is traveling to the right (e.g., as shown in Figure 5O )): the device renders (1048) increasingly larger portions of a fourth user interface representation disposed below the third user interface representation in a stack on the display (e.g., gradually rendering user interface 534 from behind user interface representation 526 in Figures 5G-5I ).

In some embodiments, the device then moves 1050 a fourth user interface representation disposed below the third user interface representation in the first direction at a fourth speed that is less than the third speed. In some embodiments, as the upper-level user interface representation moves in the first direction, one or more user interface representations disposed below the fourth user interface representation in the stack (e.g., user interface representation 540 in Figures 5I and 5T) are also revealed in this manner.

In some embodiments, after detecting a first drag gesture (e.g., the drag gesture including contact 530 and movement 532 in Figures 5G-5I ), the device detects 1052 a second drag gesture by a second contact on the touch-sensitive surface at a location corresponding to the first user interface representation on the display, the second contact moving across the touch-sensitive surface in a direction corresponding to a second direction on the display (e.g., left) that is opposite to the first direction on the display (e.g., right). For example, in Figures 5L-5N , device 100 detects a drag gesture that includes contact 546 and movement 548 that originates from the location on the display corresponding to user interface representation 510 and continues to the left.

In some embodiments, the second contact is the same as the first contact, and the second drag gesture follows the first drag gesture without lifting the first contact in between. In some embodiments, as shown in the series of Figures 5J; 5L-5N, the first contact is lifted after the first drag gesture, and the second drag gesture is made with the second contact after the second contact touches down on the touch-sensitive surface.

When a second contact is at a location on the touch-sensitive surface that corresponds to a first user interface representation on the display and the second contact moves across the touch-sensitive surface in a direction on the display that corresponds to a second direction on the display that is opposite the first direction on the display (1054): based on the velocity of the second contact on the touch-sensitive surface, the device moves (1056) the first user interface representation (e.g., user interface representation 510 in Figures 5L-5N) in a second direction on the display at a new first velocity (e.g., a card or other representation on the touch-sensitive display that is below the finger contact moves at the same velocity as the finger contact). The device also moves (1058) a second user interface representation (e.g., user interface representation 508 in Figures 5L-5N) that is positioned above the first user interface representation in the second direction at a new second velocity that is greater than the new first velocity. The device also moves (1060) a third user interface representation (e.g., user interface representation 526 in Figures 5L-5N) that is positioned below the first user interface representation in the second direction at a new third velocity that is less than the new first velocity.

In some embodiments, while the second user interface representation is moved in the second direction faster than the first user interface representation is moved in the second direction, the device detects (1062) that the second user interface representation has moved between the first user interface representation and a location on the display corresponding to a location of the second contact on the touch-sensitive surface. For example, on the touch-sensitive display, detecting that a portion of the second contact or a representative point (e.g., a centroid) of the second contact is touching the second user interface representation instead of the first user interface representation (e.g., at location 546-f in Figure 5N, the centroid of contact 546 is touching user interface representation 508 instead of user interface representation 510).

In response to detecting that the second user interface representation has moved between the first user interface representation and a location on the display corresponding to the location of the second contact on the touch-sensitive surface (1064): the device moves (1068) the second user interface representation in a second direction at a modified second speed based on a current speed of the second contact. For example, instead of having the first user interface representation move at the same speed as the second finger contact in the second drag gesture (e.g., as illustrated by changing the speed of user interface representation 508 along speed curve 550 upon reaching position 508-f in Figure 5O), the second user interface representation (e.g., user interface representation 508 in Figure 5N) has caught up with the finger movement on the touch-sensitive display and begins moving at the same speed as the second finger contact.

The device also moves (1070) a first user interface representation (e.g., user interface representation 510) disposed below the second user interface representation in the second direction at a modified first speed that is less than the modified second speed. In some embodiments, on a touch-sensitive display, once the second user interface representation becomes the representation below the finger contact, the first user interface representation moves at a speed slower than the speed of the second user interface representation (e.g., a fixed or proportional amount below the speed of the second user interface representation, as shown on speed curve 550 in FIG. 5O ).

In some embodiments, the device also moves (1072) a third user interface representation (e.g., user interface representation 526 in Figure 5N) disposed below the first user interface representation in a second direction at a modified third speed (e.g., as shown on speed curve 550 in Figure 5O) that is less than the modified first speed.

In some embodiments, the difference between the modified second speed and the modified first speed maintains (1074) a first constant z position difference between the second user interface representation and the first user interface representation, and the difference between the modified first speed and the modified third speed maintains a second constant z position difference between the first user interface representation and the third user interface representation, where the first constant z position difference is the same as the second z position difference.

In some embodiments, the difference between the modified second speed and the modified first speed is equal to the difference between the modified first speed and the modified third speed (1076).

In some embodiments, the ratio between the modified second speed and the modified first speed is equal to the ratio between the modified first speed and the modified third speed (1078).

In some embodiments, while displaying at least a first user interface representation and a second user interface representation above the first user interface representation in a stack, the device detects (1080) activation of a transient application on the device. For example, as shown in Figures 5U-5V, while displaying user interface representations 508, 510, 526, and 534, device 100 detects an incoming phone call, thereby activating a phone application.

In response to detecting activation of the transient application, the device inserts (1082) a user interface representation for the transient application in the stack between the first user interface representation and the second user interface representation. For example, user interface representation 554 of user interface 556 corresponding to the phone application is inserted between user interface representations 510 and 526 in Figures 5U-5W. In some embodiments, to make room for the user interface representation of the transient application on the display, the second user interface representation moves to the right, and the user interface representation of the transient application takes over the place where the second user interface representation previously was (for example, in Figures 5V-5W, user interface representations 510 and 508 move to the right to make room for inserting user representation 554 into the stack).

In some embodiments, while displaying at least a first user interface representation and a second user interface representation above the first user interface representation in a stack, the device detects (1084) a deletion input involving the first user interface representation (e.g., an upward drag gesture at a location on the touch-sensitive surface that corresponds to a location on the first user interface representation). For example, in Figure 5X, device 100 detects a drag gesture that includes contact 560 and movement 562 at a location on touch screen 112 that corresponds to display of user interface representation 510.

In response to detecting a delete input (1086) involving the first user interface representation: the device removes (1088) the first user interface representation from the first position in the stack (e.g., removing user interface 510 from the stack in Figures 5X-5Z). The device also moves (1090) a corresponding user interface representation that is immediately below the first user interface representation to the first position in the stack (e.g., in Figures 5Z-5AA, user interface representation 526 moves upward in the stack to occupy the position vacated by user interface representation 510). In some embodiments, in response to detecting the delete input involving the first user interface representation, the application corresponding to the first user interface representation is closed.

In some embodiments, after detecting termination of the first drag gesture, the device displays (1091) at least two of the user interface representations in the stack on the display (e.g., user interface representations 508, 510, and 526 in Figure 5BB). While displaying at least two of the plurality of user interface representations in the stack, the device detects (1092) a selection input (e.g., a tap gesture at a location on the touch-sensitive surface that corresponds to a location on the user interface representation) involving one of the at least two user interface representations in the stack. For example, in Figure 5BB, device 100 detects a tap gesture that includes contact 564 at a location on touch screen 112 that corresponds to display of user interface representation 510.

In response to detecting a selection input (1093): the device ceases displaying (1094) the stack and displays (1095) a user interface corresponding to a selected one of the at least two user interface representations. In some embodiments, the user interface corresponding to the selected user interface representation is displayed without displaying any user interfaces corresponding to other user interface representations in the stack. In some embodiments, the display of the user interface corresponding to the selected user interface representation replaces the display of the stack. For example, in response to detecting a tap gesture that includes contact 564 at a location on touch screen 112 that corresponds to display of user interface representation 510 of user interface 507, device 110 exits user interface selection mode and displays user interface 507 on touch screen 112.

In some embodiments, while at least a first user interface representation and a second user interface representation disposed above the first user interface representation in a stack are stationary on the display, the device detects (1096) a first tap gesture by a second contact at a location on the touch-sensitive surface that corresponds to one of the first user interface representation or the second user interface representation on the display. The tap gesture moves across the touch-sensitive surface in a direction that corresponds to the first direction on the display. For example, device 100 detects a tap gesture that includes contact 556 and movement 558 at a location on touch screen 112 that corresponds to the display of user interface representation 510.

In response to detecting the first tap gesture by the second contact, the device moves the second user interface representation with simulated inertia based on whether the second contact is detected at a location on the touch-sensitive surface corresponding to the first user interface representation or the second user interface representation on the display (e.g., user interface representation 510 travels further than the length of movement 558). In some embodiments, when the tap gesture involves the second user interface representation, the second user interface representation moves with less inertia than if the tap gesture involves the first user interface representation. In some embodiments, when the tap gesture involves the second user interface representation, the second user interface representation moves with greater inertia than if the tap gesture involves the first user interface representation. In some embodiments, if the top card is tapped to the right, the top card flies off the screen faster than would occur if the lower card were tapped to the right (which would indirectly push the top card to the right).

It should be understood that the particular order in which the operations in Figures 10AA-10H have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations may be performed. One of ordinary skill in the art will recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., methods 1100, 1200, 1300, 1400, 1500, 2400, and 2500) also apply in a similar manner to method 1000 described above with respect to Figures 10A-10H. For example, the contacts, gestures, user interface objects, focus selectors, and animations described above with reference to method 1000 may optionally have one or more of the characteristics of the contacts, gestures, user interface objects, focus selectors, and animations described herein with reference to other methods described herein (e.g., methods 1100, 1200, 1300, 1400, 1500, 2400, and 2500). For the sake of brevity, these details are not repeated here.

Figures 11A-11E illustrate a flow diagram of a method 1100 for navigating between user interfaces in accordance with some embodiments. Method 1100 is performed on an electronic device (e.g., device 300 of Figure 3 or portable multifunction device 100 of Figure 1A) having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on or integrated with the display. In some embodiments, the display is separate from the touch-sensitive surface. In some embodiments, the touch-sensitive surface is a portion of a trackpad or remote control device that is separate from the display. In some embodiments, the operations in method 1100 are performed by an electronic device configured to manage, play back, and/or stream (e.g., from an external server) audio and/or visual files that communicates with a remote control and display (e.g., an Apple TV from Apple Inc. of Cupertino, California). Some operations in method 1100 may optionally be combined, and/or the order of some operations may optionally be changed.

As described below, method 1100 provides an intuitive way to navigate between user interfaces. The method reduces the cognitive burden on users when navigating between user interfaces, thereby creating a more efficient human-computer interface. For battery-operated electronic devices, enabling users to navigate between user interfaces faster and more efficiently conserves power and increases the time between battery charges.

The device displays (1102) a first user interface on a display (e.g., user interface 502 in FIG. 6A ). In some embodiments, the first user interface is the user interface of a currently open application. In some embodiments, the first user interface is the current user interface of the application, preceded by a sequence of previous user interfaces for the application accessible via a “back” button provided on the user interface for the application.

While displaying the first user interface on the display, the device detects (1104) input by a first contact (e.g., contact 602 in FIG. 6B ) on the touch-sensitive surface. In some embodiments, the input by the first contact begins at a predefined location on the touch-sensitive display, such as on a left edge of the touch-sensitive display or in a predefined area adjacent to the left edge of the touch-sensitive display. In some embodiments, the input by the first contact begins at a location on the touch-sensitive surface that corresponds to the predefined location on the display, such as on a left edge of the display or in a predefined area adjacent to the left edge of the display. In some embodiments, the input comprises a press input made with a flat portion of a thumb.

Upon detecting the input by the first contact, the device displays ( 1106 ) on the display a first user interface representation and at least a second user interface representation (eg, user interface representations 508 and 510 in FIG. 6C ).

In some embodiments, based on determining that the first contact has a characteristic intensity below a predetermined intensity threshold during the input, the device displays (1108) on the display a first user interface representation for the first user interface and at least a second user interface representation for the second user interface, wherein the first user interface representation is displayed above the second user interface representation and partially exposes the second user interface representation. For example, in Figures 6B-6C, upon determining that the intensity of contact 602 does not reach the deep press intensity threshold (IT _D ), user interface representation 508 is displayed above user interface representation 510 in Figure 6C. In some embodiments, the first user interface representation and the second user interface representation are displayed in a stack.

In some embodiments, based on determining that the first contact reaches an intensity above a predetermined intensity threshold during input, the device enters (1110) a user interface selection mode and displays a plurality of user interface representations in a stack on the display, the stack including the first user interface representation displayed above and partially exposing a second user interface representation. For example, upon determining that the intensity of contact 608 reaches the deep press intensity threshold (IT _D ) in FIG. 6H , the device enters user interface selection mode, including display of user interface representations 508 , 510 , and 526 .

In some embodiments, the display of the stack replaces the display of the first user interface on the display, such as in FIG6H , where user interface 506 including the stack replaces the display of user interface 507 .

In some embodiments, the stack of user interface representations is gradually expanded with increasing contact intensity during input. For example, as the intensity of contact 610 continues to increase from FIG. 6J to FIG. 6K and then increases to a maximum intensity in FIG. 6L , the user interface representations in the stack are expanded, as shown by user interface representation 510 moving from position 510 - a in FIG. 6J through position 510 - b in FIG. 6K to position 510 - c in FIG. 6L , which is almost completely off touch screen 112.

In some embodiments, the stack is revealed in "peek" mode before the intensity reaches a predetermined threshold intensity, and reducing contact intensity during "peek" mode causes the previously expanded stack to retract. In some embodiments, a quick deep press input with an intensity that crosses the predetermined threshold intensity causes the stack to be immediately displayed, thereby skipping the glance mode.

In some embodiments, the first user interface corresponds to (1112) a first open application, and when the input via the first contact is received, the second user interface is the user interface of the second open application that was viewed just before the first open application was displayed. For example, the first and second user interface representations correspond to the last two applications opened on the device. For example, as shown in FIG6C , first user interface representation 508 is of first user interface 502 displayed on touch screen 112 immediately before the user interface representation is displayed, and second user interface representation 510 is of second user interface 507 displayed on touch screen 112 immediately before the first user interface 502 is displayed.

In some embodiments, the first user interface corresponds to (614) a first open application, and upon receiving the input through the first contact, the second user interface is a user interface of the first open application that was viewed just before the first user interface of the first open application was displayed. For example, the first and second user interfaces represent the last two user interfaces corresponding to the application that was open before the glance.

The method also includes the device detecting (1116) termination of input through the first contact (e.g., detecting liftoff of the first contact or detecting a drop in strength of the first contact below a minimum strength detection threshold, such as detecting liftoff of contact 602 in Figures 6D and 6G) while displaying the first user interface representation and at least the second user interface representation on the display.

In response to detecting termination of input by the first contact (618): based on determining that the first contact had a characteristic intensity (e.g., a representative intensity such as maximum intensity) below a predetermined intensity threshold (e.g., a deep press intensity threshold ( _ITD )) during the input and the first contact moved in a direction across the touch-sensitive surface corresponding to a predefined direction on the display (e.g., to the right in a drag or swipe gesture; or the contact moved to a position on the touch-sensitive surface corresponding to a position above a second user interface representation in the stack on the display) during the input, the device displays (1120) a second user interface corresponding to the second user interface representation. For example, in the series of Figures 6A, 6E-6G, device 100 determines that the intensity of contact 604 did not reach the predetermined deep press intensity threshold ( _ITD ) and that the input included movement of contact 604 to the right. Therefore, upon detecting liftoff of contact 604, device 100 displays user interface 507 corresponding to second user interface representation 510 during the peek gesture, as shown in Figure 6G.

In some embodiments, the second user interface is displayed without displaying other user interfaces corresponding to the plurality of user interface representations in the stack. In some embodiments, the display of the second user interface replaces the display of the stack on the display. In some embodiments, a swipe gesture followed by a light press produces a "peek" that includes display of a representation of a prior user interface followed by display of the prior user interface. In some embodiments, repeated swipe gestures followed by a light press enable the user to quickly swap between the current view and the immediately prior view (e.g., after swapping from first user interface 502 to second interface 507 in FIG. 6G , the user performs the same light press input and movement in FIG. 6Q-6S to swap back to first user interface 502 as shown in FIG. 6S ).

The method also includes, based on determining that the first contact had a characteristic intensity (e.g., a maximum intensity) below a predetermined intensity threshold (e.g., a deep press intensity threshold ( _ITD )) during the input and the first contact did not move in a direction across the touch-sensitive surface corresponding to a predefined direction on the display during the input (e.g., the first contact was stationary during the input or was moved less than a threshold amount during the input), the device redisplaying (1122) the first user interface. For example, in Figures 6A-6D, device 100 determines that contact 602 did not reach the deep press intensity threshold ( _ITD ) and was stationary. Therefore, upon detecting lift-off of contact 602, device 100 redisplays first user interface 502 as shown in Figure 6D.

In some embodiments, the first user interface is displayed without displaying other user interfaces corresponding to the plurality of user interface representations in the stack. In some embodiments, the display of the first user interface replaces the display of the stack on the display. In some embodiments, a stationary light press produces a "peek" that includes display of a representation of a prior user interface followed by a redisplay of the current user interface. In some embodiments, fully releasing the intensity during the "peek" without additional movement of the first contact causes the display to return to showing the first user interface.

In some embodiments, in response to detecting termination of input by the first contact, based on determining that the first contact reached an intensity above a predetermined intensity threshold (e.g., a deep press intensity threshold (IT _D )) during the input, the device maintains ( 1124 ) the user interface selection mode and maintains display of the stack. For example, in Figures 6H-6I , device 100 determines that contact 608 reached the deep press intensity threshold (IT _D ). Therefore, upon detecting liftoff of contact 608, device 100 maintains display of the stack as shown in Figure 6I .

In some embodiments, a deep press with an intensity that crosses a predetermined threshold intensity results in display of a stack that is maintained at the end of the deep press input (e.g., as shown in Figures 6H-6I). In some embodiments, the stack includes at least user interface representations of all open applications, and the user can navigate through the representations and select a desired application using subsequent input (e.g., a left or right drag gesture according to the operations described for method 1000).

In some embodiments, while displaying the second user interface on the display, the device detects (1126) a second input via a second contact on the touch-sensitive surface (e.g., contact 626 in Figure 6Q ). Upon detecting the second input via the second contact, the device redisplays (1128) the first user interface representation and at least the second user interface representation on the display (e.g., as shown in Figure 6R , where user interface representation 510 is now displayed over user interface representation 508).

In some embodiments, while redisplaying the first user interface representation and at least the second user interface representation on the display, the device detects (1130) termination of the second input by the second contact (e.g., lift-off of contact 626 as shown in Figure 6S). In response to detecting termination of the second input by the second contact (1132): based on determining that the second contact has a characteristic intensity below a predetermined intensity threshold (e.g., a deep press intensity threshold ( _ITD )) during the second input and the second contact moves in a direction across the touch-sensitive surface corresponding to a predefined direction on the display during the second input, the device redisplays (1134) the first user interface (e.g., swaps back from the second user interface to the first user interface as shown in Figure 6S).

In response to detecting termination of the second input through the second contact (1132): based on determining that the second contact had a characteristic intensity below a predetermined intensity threshold (e.g., a deep press intensity threshold ( _ITD )) during the second input and the second contact did not move in a direction across the touch-sensitive surface corresponding to a predefined direction on the display during the second input (e.g., the contact was stationary), the device redisplays (1136) the second user interface (e.g., the user merely glanced back at the representation of the first user interface and did not switch back).

In some embodiments, the input by the first contact includes a press input at a location on the touch-sensitive surface that corresponds to a first predetermined area on or near the display (e.g., as shown in Figures 6A-6D, such as a left edge of the display or bezel). While displaying the first user interface on the display after detecting termination of the input by the first contact, the device detects (1138) a second input by a second contact on the touch-sensitive surface, wherein the second input by the second contact on the touch-sensitive surface is a press input at a location on the touch-sensitive surface that corresponds to a second predetermined area on or near the display that is different from the first predetermined area (e.g., a right edge of the display or bezel, or somewhere within the first user interface).

In response to detecting a second input through a second contact on the touch-sensitive surface, the device performs (1140) a content-dependent operation associated with the content of the first user interface (e.g., the content-dependent operation is selecting or activating an item in the first user interface, or any other content-specific operation associated with the first user interface that is unrelated to the user interface selection mode).

In some embodiments, the first user interface is a view of the first application that includes a view hierarchy (e.g., a web page history or a navigation hierarchy). The input through the first contact includes a press input at or near a first edge of the touch-sensitive surface. After redisplaying the first user interface, the device detects (1142) an edge swipe gesture originating from the first edge of the touch-sensitive surface. In response to detecting the edge swipe gesture originating from the first edge of the touch-sensitive surface, the device displays (1144) a view in the view hierarchy of the first application that was before the first user interface (e.g., a previously viewed web page).

In some embodiments, the first user interface is the user interface of the currently open application. In some embodiments, the first user interface is the current user interface of the application, and the current user interface is preceded by a sequence of previous user interfaces for the application accessible by a "back" button provided on each of the user interfaces.

In some embodiments, while displaying a first user interface of a first application on the display, the device detects a drag gesture by a first contact on the touch-sensitive surface. In response to detecting the drag gesture by the first contact, based on determining that the drag gesture by the first contact occurs within an area of the touch-sensitive surface corresponding to a first predefined area on or near the display, an application selection mode is entered. Based on determining that the drag gesture by the first contact occurs within an area of the touch-sensitive surface corresponding to a second predefined area on or near the display that is different from the first predefined area, a second user interface of the first application that was displayed immediately before displaying the first user interface of the first application is displayed on the display.

In some embodiments, the first predefined area is adjacent to a bottom edge of the display, and the second predefined area is at least a portion of the remaining area of the display, such as an area above the first predefined area. In some embodiments, a drag gesture with the first contact occurring within the area of the touch-sensitive surface corresponding to the first predefined area or within the area of the touch-sensitive surface corresponding to the second predefined area is further required to begin on the area of the touch-sensitive surface corresponding to the left edge of the display or in the area of the touch-sensitive surface corresponding to the predefined area adjacent to the left edge of the display (in order to enter application selection mode or display the second user interface).

In some embodiments, based on determining that a drag gesture via a first contact begins in an area of the touch-sensitive surface corresponding to a first predefined area on the display, the device displays on the display a plurality of user interface representations for corresponding multiple applications, including a first user interface representation corresponding to a first user interface of a first application and a second user interface representation corresponding to a second user interface of a second application different from the first application. In some embodiments, display of the stack replaces display of the first user interface of the first application on the display. In some embodiments, the plurality of user interface representations are displayed in a stack. In some embodiments, the first user interface representation is displayed over the second user interface representation and partially exposes the second user interface representation.

In some embodiments, after detecting termination of input through the first contact, while displaying the stack in user interface selection mode based on determining that the first contact reached an intensity above a predetermined intensity threshold during the input (e.g., as shown in Figures 6H-6I), the device detects (1146) a drag gesture through a second contact on the touch-sensitive surface at a location corresponding to a second user interface representation on the display, where the drag gesture moves across the touch-sensitive surface in a direction corresponding to the first direction on the display (e.g., as shown in Figures 5G-5I).

In response to detecting a drag gesture (1148) by a second contact on the touch-sensitive surface at a location corresponding to a second user interface representation on the display, wherein the drag gesture moves across the touch-sensitive surface in a direction corresponding to the first direction on the display, the device moves (1150) the second user interface representation in the first direction at a second speed based on the speed of the second contact (e.g., user interface representation 510 moves from location 510-a in Figure 5G to location 510-c in Figure 5I); and the device moves (1152) the first user interface representation disposed above the second user interface representation in the first direction at a first speed greater than the second speed (e.g., user interface representation 508 moves from location 508-a in Figure 5G to location 508-b and off the screen in Figure 5I). In some embodiments, once the user interface selection mode is activated, navigation can be performed according to the processing described above for method 1000.

It should be understood that the particular order in which the operations in Figures 11A-11E are described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations can be performed. One of ordinary skill in the art will recognize various ways to reorder the operations described herein. Additionally, it should be noted that the details of other processes described herein with respect to other methods described herein (e.g., methods 1000, 1200, 1300, 1400, 1500, 2400, and 2500) also apply in a similar manner to method 1100 described above with respect to Figures 11A-11E. For example, the contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described above with reference to method 1100 may optionally have one or more of the characteristics of the contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described herein with respect to other methods described herein (e.g., methods 1000, 1200, 1300, 1400, 1500, 2400, and 2500). For the sake of brevity, these details are not repeated here.

Figures 12A-12E illustrate a flow diagram of a method 1200 for navigating between user interfaces in accordance with some embodiments. Method 1200 is performed on an electronic device (e.g., device 300 of Figure 3 or portable multifunction device 100 of Figure 1A) having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on or integrated with the display. In some embodiments, the display is separate from the touch-sensitive surface. In some embodiments, the touch-sensitive surface is a portion of a trackpad or remote control device that is separate from the display. In some embodiments, the operations in method 1200 are performed by an electronic device configured to manage, play back, and/or stream (e.g., from an external server) audio and/or visual files that communicates with a remote control and display (e.g., an Apple TV from Apple Inc. of Cupertino, California). Some operations in method 1200 may optionally be combined, and/or the order of some operations may optionally be changed.

As described below, method 1200 provides an intuitive way to navigate between user interfaces. The method reduces the cognitive burden on users when navigating between user interfaces, thereby creating a more efficient human-computer interface. For battery-operated electronic devices, enabling users to navigate between user interfaces faster and more efficiently conserves power and increases the time between battery charges.

The device displays (1202) a first user interface (e.g., user interface 502 in FIG. 7A ) on a display. In some embodiments, the first user interface is the user interface of a currently open application. In some embodiments, the first user interface is the current user interface of the application, and the display of the first user interface is preceded by a sequence of displays of previous user interfaces (e.g., previous web pages) of the application. In some embodiments, the previous user interfaces are accessible by activating a “back” button provided on the user interface of the application (e.g., back button 614 in FIG. 7A ).

While displaying the first user interface on the display, the device detects (1204) input on the touch-sensitive surface by a first contact, the first contact including a period of increasing intensity of the first contact (e.g., contact 702 with increasing intensity in Figures 7B-7E). In some embodiments, the input by the first contact is made with a flat portion of a thumb.

In response to detecting input through a first contact (the first contact including a period of increasing intensity of the first contact) (e.g., contact 702), the device displays (1206) on the display a first user interface representation for a first user interface and a second user interface representation for a second user interface (e.g., a user interface of a second application that is displayed immediately before the first user interface of the current application), wherein the first user interface representation is displayed over the second user interface representation and partially exposes the second user interface representation (e.g., user interface representations 508 and 510 in Figure 7C).

In some embodiments, the first user interface representation and the second user interface representation are displayed in a stack. In some embodiments, display of the stack replaces display of the first user interface on the display.

In some embodiments, the user interface enters "glance" mode in response to a light press, and as the intensity of contact increases or decreases after activating "glance" mode, changing amounts of the user interface representation for the previously displayed application appear from beneath the representation of the user interface of the current application (e.g., as the intensity of contact 702 increases from Figure 7C to Figure 7D, more of user interface representation 510 appears from beneath user interface representation 508).

In some embodiments, the period of increasing intensity of the first contact is preceded by a period of varying intensity of the first contact that includes both rising and falling intensity (e.g., the intensity of contact 704 increases from FIG. 7G to FIG. 7H , falls from FIG. 7H to FIG. 7I , and then increases again from FIG. 7I to FIG. 7J ). Based on the rise and fall in the intensity of the first contact during the period of varying intensity, the device dynamically changes ( 1208 ) the area of the second user interface representation that is revealed behind the first user interface representation (e.g., more of the second user interface representation 508 is revealed as the intensity of contact 704 increases from FIG. 7G to FIG. 7H ; less of the second user interface representation 508 is revealed as the intensity of contact 704 falls from FIG. 7H to FIG. 7I , and then more of the second user interface representation 708 is revealed again as the intensity of contact 704 rises from FIG. 7I to FIG. 7J ).

The method also includes, while displaying the first user interface representation and the second user interface representation on the display, the device detecting (1210) that during a period of increasing intensity of the first contact, the intensity of the first contact meets one or more predetermined intensity criteria (e.g., the intensity of the first contact is at or above a predetermined threshold intensity such as a deep press intensity threshold (IT _D ) as shown in FIG. 7E ).

In some embodiments, during the period of increasing contact intensity of the first contact, and before the intensity of the first contact meets one or more predetermined intensity criteria, in response to the increasing intensity of the first contact, the device increases (1212) the area of the second user interface representation that is revealed from behind the first user interface representation. For example, as the intensity of contact 702 increases from Figure 7C to Figure 7D, user interface representation 510 is revealed further from below user interface representation 508. In some embodiments, in response to the increasing intensity of the contact, the second user interface is displayed larger (e.g., as if coming toward the user from behind the plane of the display).

In some embodiments, increasing the area of the second user interface representation that appears from behind the first user interface representation based on an increase in the intensity of the first contact includes displaying (1214) an animation that dynamically changes the amount of area of the second user interface representation that appears from behind the first user interface representation based on a change in the intensity of the first contact over time.

In some embodiments, dynamically changing the amount of area includes updating the amount of area of the second user interface multiple times a second (e.g., 10, 20, 30, or 60 times per second), optionally without regard to whether the contact meets one or more predetermined intensity criteria. In some embodiments, the animation is a fluid animation that updates as the intensity of the first contact changes, so as to provide feedback to the user about the amount of intensity detected by the device (e.g., feedback about the amount of force applied by the user). In some embodiments, the animation is updated smoothly and quickly to create the appearance to the user that the user interface is responding to changes in the force applied to the touch-sensitive surface in real time (e.g., the animation is perceptually instantaneous to the user, so as to provide immediate feedback to the user and enable the user to better modulate the force they apply to the touch-sensitive surface to efficiently interact with user interface objects that respond to contacts of different or changing intensities).

In some embodiments, increasing the area of the second user interface representation that is revealed behind the first user interface representation based on the increasing intensity of the first contact includes moving (1216) the first user interface representation in a first direction to increase the lateral position offset on the display between the first user interface representation and the second user interface representation. For example, as the intensity of contact 704 increases from Figure 7G to Figure 7H, user interface representation 510 slides to the right from position 510-a in Figure 7G to position 510-b in Figure 7H, thereby revealing more of user interface representation 508. In some embodiments, as the finger contact presses harder on the touch-sensitive surface at a location corresponding to the left edge of the display or in a predefined area adjacent to the left edge of the display, the first user interface representation moves to the left to reveal more of the second user interface representation.

In some embodiments, increasing the area of the second user interface representation that appears behind the first user interface representation in accordance with increasing intensity of the first contact includes moving (718) the first user interface representation and the second user interface representation toward each other in a second direction perpendicular to the first direction while moving the first user interface representation in the first direction to increase the lateral position offset between the first user interface representation and the second user interface representation on the display (e.g., as the intensity of contact 702 increases from FIG. 7C to FIG. 7D , first user interface representation 508 appears to move away from the surface of touch screen 112 and second user interface representation 510 appears to move toward the surface of the touch screen). In some embodiments, the second direction perpendicular to the first direction is a z-direction perpendicular to the surface of the display. In some embodiments, the first user interface representation and the second user interface representation move toward the same layer in a z-layer order.

In some embodiments, the device detects (1220) that the intensity of the first contact meets one or more predetermined intensity criteria (e.g., a deep press intensity threshold ( _ITD ) as shown in FIG. 7E ). In response to detecting that the intensity of the first contact meets the one or more predetermined intensity criteria, the device displays (1222) an animation showing the first user interface representation receding behind the second user interface representation, and the second user interface representation moving into the foreground and transitioning to the second user interface (e.g., user interface representation 510 pops up from behind user interface representation 508 as shown in FIG. 7E , and then the animation shows the transition to user interface 507 in FIG. 7F ).

In some embodiments, the device changes (1224) the level of blur effect applied to at least one of the first user interface representation and the second user interface representation during the animation. For example, as shown in the series of Figures 7C-7E, during the animation, the first user interface representation becomes blurrier and/or the second user interface representation becomes less blurrier, where user interface representation 510 begins blurry in Figure 7C and comes into focus as it appears to move toward the surface of touch screen 112. In contrast, user interface 508 begins in focus in Figure 7C and becomes blurrier as it appears to move away from the surface of touch screen 112.

The method also includes, in response to detecting that the intensity of the first contact meets one or more predetermined intensity criteria (1226), the device ceasing to display (1228) the first user interface representation and the second user interface representation on the display; and the device displaying (1230) the second user interface on the display (e.g., without displaying the first user interface). In some embodiments, when the intensity of the contact reaches or exceeds a predetermined deep press threshold intensity, the "peek" is followed by a "pop-up" displaying the second user interface. For example, when the intensity of contacts 702, 704, and 706 reaches the deep press intensity threshold (IT _D ) in Figures 7F, 7J, and 7O, respectively, the second user interface representation "pops up" and the display displays the corresponding user interface.

In some embodiments, while displaying the second user interface on the display, the device detects (1232) input on the touch-sensitive surface through a second contact that includes a period of increasing intensity of the second contact (e.g., contact 706 with increasing intensity in Figures 7L to 7O).

In response to detecting input through a second contact (the second contact including a period of increased intensity of the second contact), the device displays (1234) a first user interface representation and a second user interface representation on the display, wherein the second user interface representation is displayed over the first user interface representation and partially exposes the first user interface representation (e.g., the display of user interface representations 508 and 510 in Figure 7M).

In some embodiments, the first user interface representation and the second user interface representation are displayed in a second stack. In some embodiments, display of the second stack replaces display of the second user interface on the display.

In some embodiments, the user interface enters a "peek" mode in response to a light press, and as the intensity of the contact increases or decreases after activating the "peek" mode, varying amounts of the user interface representation for the previously displayed application are revealed from beneath the representation of the user interface of the current application. For example, in response to detecting increasing intensity of contact 706 in Figures 7M-7N, more of user interface representation 508 is revealed from behind user interface representation 510.

In some embodiments, while displaying the first user interface representation and the second user interface representation on the display, the device detects (1236) that during the period of increasing intensity of the second contact, the intensity of the second contact meets one or more predetermined intensity criteria.

In response to detecting that the intensity of the second contact meets one or more predetermined intensity criteria (1238), the device ceases displaying (1240) the first user interface representation and the second user interface representation on the display; and the device displays (1242) the first user interface on the display (e.g., without displaying the second user interface). For example, device 100 detects that the intensity of contact 706 exceeds a deep press intensity threshold (IT _D ) and, in response, replaces display of user interface 506 with first user interface 508 in FIG. 7O . In some embodiments, the "peek" is followed by a "pop" displaying the first user interface when the intensity of the contact reaches or exceeds the predetermined deep press threshold intensity.

In some embodiments, while displaying the second user interface on the display, the device detects (1244) input on the touch-sensitive surface through a second contact that includes a period of increasing intensity of the second contact (e.g., contact 704 with increasing intensity in Figures 7G-7H).

In response to detecting input through a second contact (the second contact including a period of increased intensity of the second contact), the device displays (1246) a first user interface representation and a second user interface representation on the display, wherein the second user interface representation is displayed over the first user interface representation and partially exposes the first user interface representation (e.g., the display of user interface representations 508 and 510 in Figure 7M).

In some embodiments, the first user interface representation and the second user interface representation are displayed in a second stack. In some embodiments, display of the second stack replaces display of the second user interface on the display.

In some embodiments, the user interface enters a "peek" mode in response to a light press, and as the intensity of the contact increases or decreases after activating the "peek" mode, varying amounts of the user interface representation for the previously displayed application are revealed from beneath the representation of the user interface of the current application. For example, in response to detecting increasing intensity of contact 704 in Figures 7G-7H, more of user interface representation 508 is revealed from behind user interface representation 510.

While displaying the first user interface representation and the second user interface representation on the display, the device detects (1248) termination of input by the second contact (e.g., detecting lift-off of the second contact (e.g., as in FIG. 7K ), or detecting a drop in strength of the second contact below a minimum strength detection threshold (e.g., as in FIG. 7J )), without the strength of the second contact meeting one or more predetermined strength criteria.

In response to detecting termination of input through the second contact without the intensity of the second contact meeting one or more predetermined intensity criteria (1250): the device ceases displaying (1252) the first user interface representation and the second user interface representation on the display; and the device displays (1254) the second user interface on the display (e.g., without displaying the first user interface). For example, device 100 detects that the intensity of contact 704 drops below a minimum intensity detection threshold (IT ₀ ) and, in response, replaces display of user interface 506 with second user interface 510 in FIG. 7J . In some embodiments, when the input terminates without the intensity of the contact reaching a predetermined deep press threshold intensity, the “glance” ceases and the second user interface is redisplayed.

It should be understood that the particular order in which the operations in Figures 12A-12E have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations may be performed. One of ordinary skill in the art will recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., methods 1000, 1100, 1300, 1400, 1500, 2400, and 2500) also apply in a similar manner to method 1200 described above with respect to Figures 12A-12E. For example, the contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described above with respect to method 1200 may optionally have one or more of the characteristics of the contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described herein with respect to other methods described herein (e.g., methods 1000, 1100, 1300, 1400, 1500, 2400, and 2500). For the sake of brevity, these details are not repeated here.

Figures 13A-13D illustrate a flow diagram of a method 1300 for navigating between user interfaces in accordance with some embodiments. Method 1300 is performed on an electronic device (e.g., device 300 of Figure 3 or portable multifunction device 100 of Figure 1A) having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on or integrated with the display. In some embodiments, the display is separate from the touch-sensitive surface. In some embodiments, the touch-sensitive surface is a portion of a trackpad or remote control device that is separate from the display. In some embodiments, the operations in method 1300 are performed by an electronic device configured to manage, play back, and/or stream (e.g., from an external server) audio and/or visual files that communicates with a remote control and display (e.g., an Apple TV from Apple Inc. of Cupertino, California). Some operations in method 1300 may optionally be combined, and/or the order of some operations may optionally be changed.

As described below, method 1300 provides an intuitive way to navigate between user interfaces. The method reduces the cognitive burden on users when navigating between user interfaces, thereby creating a more efficient human-computer interface. For battery-operated electronic devices, enabling users to navigate between user interfaces faster and more efficiently conserves power and increases the time between battery charges.

The device displays (1302) on a display a plurality of user interface representations in a stack (e.g., in user interface selection mode, a stack of cards (or other objects) representing user interfaces of open applications in z-order, cards representing currently and previously viewed user interfaces of a single application, cards representing messages in an email chain, etc.). At least a first user interface representation, a second user interface representation, and a third user interface representation are visible on the display. The first user interface representation (e.g., user interface representation 508 in FIG. 8A ) is laterally offset from the second user interface representation in a first direction (e.g., laterally offset to the right on the display) and partially exposes the second user interface representation. The second user interface representation (e.g., user interface representation 510 in FIG. 8A ) is laterally offset from the third user interface representation (e.g., user interface representation 526 in FIG. 8A ) in a first direction (e.g., laterally offset to the right on the display) and partially exposes the third user interface representation. For example, in some embodiments, as shown in FIG. 8A , the stack is displayed when the display is in user interface selection mode.

In some embodiments, before displaying the stack on the display (1304): the device displays (1306) on the display a first user interface corresponding to a first user interface representation (e.g., user interface 502 of a web browsing application as shown in FIG. 7A ). While displaying the first user interface, the device detects (1308) a predetermined input. In some embodiments, the predetermined input is, for example, a double tap or double press on a “home” button on the device; or, for an electronic device that includes one or more sensors for detecting intensity of contact with a touch-sensitive display: a deep press on a predetermined area of the first user interface (e.g., the upper left corner); a deep press with the flat portion of the thumb anywhere on the first user interface; or a deep press on a predetermined area of the device, such as on the left edge of the touch-sensitive display, in a predefined area adjacent to the left edge of the touch-sensitive display, on the bottom edge of the touch-sensitive display, or in a predefined area adjacent to the bottom edge of the touch-sensitive display.

In response to detecting a predetermined input (1310): the device enters (1313) a user interface selection mode; and the device displays (1312) a stack comprising a plurality of user interface representations (e.g., a display of user interface 506 in user interface selection mode, including the display of the stack in Figure 9A).

In some embodiments, in response to detecting input by the first contact (e.g., a press input having an intensity above a predefined threshold) while the first contact is at a first location on the touch-sensitive surface that corresponds to an on-screen location other than the second user interface representation (e.g., contact 806 is detected at location 806-a that does not correspond to display of user interface representation 510 on touch screen 112 in Figures 8J-8K), the stack is displayed (1316). Before detecting an increase in intensity of the first contact, the first contact moves from the first location on the touch-sensitive surface to a location corresponding to the second user interface representation on the display (e.g., contact 806-a moves from location 806-a to location 806-b in Figures 8K-8L). The first contact is detected continuously on the device, for example, starting before the second user interface representation is displayed and at least until an increasing area of the second user interface representation exposed from behind the first user interface representation is displayed.

The method also includes the device detecting (1318) an input by a first contact on the touch-sensitive surface at a location corresponding to a second user interface representation on the display (e.g., contact 802 at a location corresponding to the display of user interface representation 510 on touch screen 112 in Figure 8A). In some embodiments, the device detects a press by a finger contact at a location on the touch-sensitive surface corresponding to a user interface representation in the stack, and the device detects a changing intensity of the finger contact (e.g., the intensity of contact 802 increases from Figure 8A to Figure 8B, decreases from Figure 8B to Figure 8C, and then increases again from Figure 8C to Figure 8D).

In some embodiments, the input by the first contact includes a period of decreasing intensity of the first contact following the period of increasing intensity of the first contact. During the period of decreasing intensity of the first contact, the device reduces (1320) the area of the second user interface representation exposed from behind the first user interface representation by reducing the lateral offset between the first user interface representation and the second user interface representation. For example, in response to the decreasing intensity of contact 802 from Figure 8B to Figure 8C, user interface representation 508 begins to slide back over user interface representation 510, thereby moving from position 508-b in Figure 8B to position 508-c in Figure 8C.

In some embodiments, after revealing more of the second user interface representation in response to detecting an increase in contact intensity, the device reveals less of the second user interface representation in response to detecting a decrease in contact intensity (e.g., in response to the intensity of contact 802 increasing from FIG. 8A to FIG. 8B , user interface representation 508 slides to the right of user interface representation 510, thereby moving from position 508 - a in FIG. 8A to position 508 - b in FIG. 8B ). In some embodiments, an animation is displayed to illustrate movement of the first and second user interface representations in a manner that dynamically responds to small changes in the intensity of the first contact (e.g., the movement of user interface representation 508 in FIG. 8A-8C is directly manipulated by the user increasing or decreasing the intensity of contact 802).

The method also includes, in response to detecting an increase in intensity of the first contact on the touch-sensitive surface at a location corresponding to the second user interface representation on the display, the device increasing (1322) an area of the second user interface representation exposed from behind the first user interface representation by increasing a lateral offset between the first user interface representation and the second user interface representation (e.g., in response to the intensity of contact 802 increasing from FIG. 8A to FIG. 8B , user interface representation 508 slides to the right of user interface representation 510, thereby moving from position 508-a in FIG. 8A to position 508-b in FIG. 8B and revealing more of user interface representation 810).

In some embodiments, a second user interface representation (e.g., user interface representation 510 in Figures 8A-8C) is positioned below a first user interface representation (e.g., user interface representation 508 in Figures 8A-8C) and above a third user interface representation (e.g., user interface representation 526 in Figures 8A-8C) in a z-layer order, and the second user interface representation is revealed more by a depression of a contact at a location on the touch-sensitive surface corresponding to an exposed portion of the second user interface representation. In some embodiments, to reveal more of the second user interface representation, in response to detecting an increase in intensity of the contact at a location on the touch-sensitive surface corresponding to the exposed portion of the second user interface representation, the first user interface representation moves to the right, thereby "glimpsing" more of the second user interface representation (e.g., user interface 508 moves from location 508-a in Figure 8A to location 508-b in Figure 8B in response to the increase in intensity of contact 802, revealing more of user interface representation 510).

In some embodiments, increasing the area of the second user interface representation exposed from behind the first user interface representation includes moving (1324) the first user interface representation in a first direction (e.g., moving the first user interface representation to the right to increase the lateral offset between the first user interface representation and the second user interface representation). For example, user interface representation 508 is moved to the right to reveal more of user interface representation 510 in Figures 8A-8B.

In some embodiments, increasing the area of the second user interface representation exposed from behind the first user interface representation includes moving (1326) the second user interface representation in a second direction opposite to the first direction (e.g., moving the second user interface representation to the left (with or without the first user interface representation simultaneously moving to the right) to increase the lateral offset between the first user interface representation and the second user interface representation on the display). For example, user interface representation 510 is moved to the left to reveal more of the representation in Figures 8G-8H.

In some embodiments, while the stack is displayed, the device detects (1328) a drag gesture by a second contact that is at a location on the touch-sensitive surface that corresponds to the second user interface representation and that moves across the touch-sensitive surface in a direction that corresponds to a second direction that is opposite to the first direction on the display (e.g., detecting a left drag on the touch-sensitive surface at a location that corresponds to the second user interface representation).

In response to detecting a drag gesture (1330) in a direction on the touch-sensitive surface that corresponds to a second direction on the display by a second contact on the touch-sensitive surface at a location corresponding to a second user interface representation, the device: moves (1332) the second user interface representation on the display in a second direction at a second speed based on a speed of the second contact on the touch-sensitive surface; moves (1334) the first user interface representation in the second direction at a first speed that is greater than the second speed; moves (1336) the third user interface representation in the second direction at a third speed that is less than the second speed; and moves (1338) the fourth user interface representation in the second direction at a fourth speed that is greater than the second speed. In some embodiments, the fourth speed is greater than the first speed. In some embodiments, the fourth user interface representation is disposed on top of the first user interface representation in the stack.

In some embodiments, in response to a prior drag gesture to the right, the fourth user interface representation moves to the right, off the display. A subsequent drag gesture to the left causes the fourth user interface representation to come into view on the display from the right (e.g., a drag gesture including contact 546 and movement 548 from position 546-c in Figure 5L to position 546-e in Figure 5M to position 546-f in Figure 5N causes user interface representation 508 to come back into view on the display from the right). In some embodiments, the fourth user interface representation moves faster than any user interface representation below it in relative z-position.

In some embodiments, the device detects (1340) that an intensity of the first contact on the touch-sensitive surface at a location corresponding to the second user interface representation meets one or more predetermined intensity criteria (e.g., the intensity of the first contact is at or above a predetermined threshold intensity, such as a deep press intensity threshold, as shown in FIG. 8D ).

In response to detecting that the intensity of the first contact on the touch-sensitive surface at a location corresponding to the second user interface representation satisfies one or more predetermined intensity criteria (1342), the device: ceases displaying (1344) the stack; and displays (1348) a second user interface corresponding to the second user interface representation. For example, in response to detecting that the intensity of contact 802 exceeds a deep press intensity threshold ( _ITD ) at a location on touch screen 112 corresponding to the display of the user interface representations, device 100 replaces display of user interface 506 (corresponding to user interface selection mode) with display of user interface 507 (corresponding to user interface representation 510) in Figures 8C-8D. In some embodiments, the second user interface is displayed without displaying any user interfaces corresponding to other user interface representations in the stack. In some embodiments, the display of the second user interface replaces display of the stack.

In some embodiments, in response to detecting that the intensity of the first contact at a location on the touch-sensitive surface corresponding to the second user interface representation meets one or more predetermined intensity criteria, the device displays an animation of the second user interface representation transitioning to the second user interface. For example, in response to detecting that the intensity of contact 802 exceeds a deep press intensity threshold ( _ITD ) at a location on touch screen 112 corresponding to the display of the user interface representation, device 100 displays the following animation in which, as shown in the series of Figures 8C, 8E, and 8F, as the device transitions to display of user interface 507, first user interface representation 508 slides completely to the right away from second user interface representation 510, second user interface 510 appears to be lifted from the stack (e.g., through position 510-b in Figure 8E to position 510-c in Figure 8F), and first user interface representation 508 is shuffled back into the stack below second user interface representation 510.

In some embodiments, the device detects (1350) a first contact moving from a location on the touch-sensitive surface corresponding to the second user interface representation to a location on the touch-sensitive surface corresponding to a third user interface representation on the display, where an intensity of the first contact during the movement of the first contact is less than a characteristic intensity detected during an increase in intensity of the first contact at the location on the touch-sensitive surface corresponding to the second user interface representation (e.g., device 100 detects contact 806 moving 808 from position 806-b in Figure 8N corresponding to the display of user interface representation 510 to position 806-c in Figure 8O corresponding to the display of user interface representation 526).

In response to detecting an increase in the intensity of the first contact on the touch-sensitive surface at a location corresponding to the third user interface representation on the display, the device increases (1352) the area of the third user interface representation exposed from behind the second user interface representation by increasing the lateral offset between the second user interface representation and the third user interface representation (e.g., device 100 detects an increase in the intensity of contact 806 from FIG. 8O to FIG. 8P , and in response moves user interface representations 510 and 508 rightward, from positions 510-a and 508-a in FIG. 8O to positions 510-h and 508-h in FIG. 8P , respectively, to reveal more of user interface 526). In some embodiments, only the user interface representations directly above the selected user interface representation (e.g., not all user interface representations above the selected user interface representation) are moved out of the way to reveal more of the selected user interface representation. For example, only user interface representation 510 would be moved in FIG. 8O to reveal more of user interface representation 526 (e.g., by sliding further below user interface representation 508).

In some embodiments, as the user drags their finger over different representations in the stack, the stack expands to reveal more of the representations beneath the user's finger. In some embodiments, the user can increase the intensity of the contact to peek at one representation, decrease the intensity (without lifting), move to the next representation, increase the intensity to peek at the next representation, decrease the intensity (without lifting), move to another representation, etc.

It should be understood that the particular order in which the operations in Figures 13A-13D have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations may be performed. One of ordinary skill in the art will recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., methods 1000, 1100, 1200, 1400, 1500, 2400, and 2500) also apply in a similar manner to method 1300 described above with respect to Figures 13A-13D. For example, the contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described above with respect to method 1300 may optionally have one or more of the characteristics of the contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described herein with respect to other methods described herein (e.g., methods 1000, 1100, 1200, 1400, 1500, 2400, and 2500). For the sake of brevity, these details are not repeated here.

Figures 14A-14C illustrate a flow diagram of method 1400 for navigating between user interfaces in accordance with some embodiments. Method 1400 is performed on an electronic device (e.g., device 300 of Figure 3 or portable multifunction device 100 of Figure 1A) having a display, a touch-sensitive surface, and optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface. In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on or integrated with the display. In some embodiments, the display is separate from the touch-sensitive surface. In some embodiments, the touch-sensitive surface is a portion of a trackpad or remote control device that is separate from the display. In some embodiments, the operations in method 1400 are performed by an electronic device configured to manage, play back, and/or stream (e.g., from an external server) audio and/or visual files that communicates with a remote control and display (e.g., an Apple TV from Apple Inc. of Cupertino, California). Some operations in method 1400 may optionally be combined, and/or the order of some operations may optionally be changed.

As described below, method 1400 provides an intuitive way to navigate between user interfaces. The method reduces the cognitive burden on users when navigating between user interfaces, thereby creating a more efficient human-computer interface. For battery-operated electronic devices, enabling users to navigate between user interfaces faster and more efficiently conserves power and increases the time between battery charges.

The device displays (1402) a plurality of user interface representations in a stack on a display (e.g., in a user interface selection mode, a stack of cards (or other objects) representing user interfaces of open applications in z-order, cards representing currently and previously viewed user interfaces of a single application, cards representing messages in an email chain, etc.). At least a first user interface representation, a second user interface representation, and a third user interface representation are visible on the display (e.g., as shown in FIG. 9A , a stack of user interface representations 508, 510, and 526 is displayed). The second user interface representation (e.g., user interface representation 510 in FIG. 9A ) is laterally offset from the first user interface representation in a first direction (e.g., laterally offset to the right on the display) and partially exposes the first user interface representation (e.g., user interface representation 526 in FIG. 9A ). The third user interface representation (e.g., user interface representation 508 in FIG. 9A ) is laterally offset from the second user interface representation in the first direction (e.g., laterally offset to the right on the display) and partially exposes the second user interface representation.

The device detects (1404) a drag gesture by a first contact moving across the touch-sensitive surface, wherein the movement of the drag gesture by the first contact corresponds to movement across one or more of the plurality of user interface representations in the stack. For example, the drag gesture includes contact 902 and movement 904 in FIG. 9B .

During the drag gesture, as the first contact moves over a location on the touch-sensitive surface that corresponds to the first user interface representation on the display, the device reveals 1406 more of the first user interface representation on the display from behind the second user interface representation. For example, as contact 902 moves over user interface representation 526, user interface representations 510 and 508 move to the right to reveal more of user interface representation 526 in FIG. 9B .

In some embodiments, revealing more of the first user interface representation from behind the second user interface representation includes moving (1408) the second user interface representation in a first direction (e.g., moving the second user interface representation to the right to increase the lateral offset between the first user interface representation and the second user interface representation).

In some embodiments, revealing more area of the first user interface representation from behind the second user interface representation includes moving (1410) the first user interface representation in a second direction opposite to the first direction (e.g., moving the first user interface representation to the left (with or without the second user interface representation simultaneously moving to the right) to increase the lateral offset between the first user interface representation and the second user interface representation on the display).

In some embodiments, during a drag gesture, when the first contact moves (1412) from a first position on the touch-sensitive surface corresponding to the first user interface representation to a second position on the touch-sensitive surface corresponding to the second user interface representation (e.g., contact 902 moves from position 902-a corresponding to the display of user interface representation 526 in Figure 9B to position 904 corresponding to the display of user interface representation 510 in Figure 9C): the device reveals (1414) more of the second user interface representation from behind a third user interface representation on the display, and reveals (1416) less of the first user interface representation from behind the second user interface representation on the display (e.g., in Figure 9D, user representation 510 moves to the left, thereby revealing more of its user interface representation and covering more of user interface representation 526).

In some embodiments, the device detects (1418) a liftoff of the first contact while the first contact is at a location on the touch-sensitive surface that corresponds to one of the plurality of user interface representations in the stack (e.g., device 100 detects liftoff of contact 902 in Figure 9E ). In response to detecting liftoff of the first contact (1420): the device stops displaying (1422) the stack; and the device displays (1424) a user interface that corresponds to the one of the plurality of user interface representations (e.g., device 100 replaces display of user interface 506 in Figure 9E with display of user interface 507 in Figure 9F ).

For example, if the first contact in a drag gesture is lifted while over a location corresponding to a first user interface representation, the first user interface is displayed. If the first contact in a drag gesture is lifted while over a location corresponding to a second user interface representation, the second user interface is displayed. More generally, if the first contact in a drag gesture is lifted while over a location corresponding to a corresponding user interface representation, the corresponding user interface is displayed. In some embodiments, the display of the user interface corresponding to the one of the plurality of user interface representations replaces the display of the stack.

In some embodiments where the device has one or more sensors for detecting intensity of contacts with the touch-sensitive surface, when the first contact is at a location on the touch-sensitive surface that corresponds to one of the multiple user interface representations in the stack, the device detects (1426) that the intensity of the first contact meets one or more predetermined intensity criteria (e.g., the intensity of the first contact is at or above a predetermined threshold intensity such as a deep press intensity threshold as shown in FIG. 9G ).

In response to detecting that the intensity of the first contact meets one or more predetermined intensity criteria (1428): the device stops displaying (1430) the stack; and the device displays (1432) a user interface corresponding to the one of the multiple user interface representations (e.g., device 100 replaces display of user interface 506 in Figure 9G with display of user interface 907 in Figure 9H).

For example, if the first contact in a drag gesture makes a deep press while over a location corresponding to a first user interface representation, the first user interface is displayed. If the first contact in a drag gesture makes a deep press while over a location corresponding to a second user interface representation, the second user interface is displayed. More generally, if the first contact in a drag gesture makes a deep press while over a location corresponding to a respective user interface representation, the respective user interface is displayed. In some embodiments, the display of the user interface corresponding to the one of the plurality of user interface representations replaces the display of the stack.

It should be understood that the particular order in which the operations in Figure 1400 have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations may be performed. One of ordinary skill in the art will recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., methods 1000, 1100, 1200, 1300, 1500, 2400, and 2500) also apply in a similar manner to method 1400 described above with respect to Figures 14A-14C. For example, the contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described above with reference to method 1400 may optionally have one or more of the characteristics of the contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described herein with reference to other methods described herein (e.g., methods 1000, 1100, 1200, 1300, 1500, 2400, and 2500). For the sake of brevity, these details are not repeated here.

Figure 15 illustrates a flow diagram of a method 1500 for navigating between user interfaces in accordance with some embodiments. Method 1500 is performed on an electronic device (e.g., device 300 of Figure 3 or portable multifunction device 100 of Figure 1A) having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on or integrated with the display. In some embodiments, the display is separate from the touch-sensitive surface. In some embodiments, the touch-sensitive surface is a portion of a trackpad or remote control device that is separate from the display. In some embodiments, the operations in method 1500 are performed by an electronic device configured to manage, play back, and/or stream (e.g., from an external server) audio and/or visual files that communicates with a remote control and display (e.g., an Apple TV from Apple Inc. of Cupertino, California). Some operations in method 1500 may optionally be combined, and/or the order of some operations may optionally be changed.

As described below, method 1500 provides an intuitive way to navigate between user interfaces. The method reduces the cognitive burden on users when navigating between user interfaces, thereby creating a more efficient human-computer interface. For battery-operated electronic devices, enabling users to navigate between user interfaces faster and more efficiently conserves power and increases the time between battery charges.

The device displays (1502) a first user interface of a first application on a display. The first user interface includes a back navigation control (e.g., user interface 654 including a back navigation control icon 614). In some embodiments, the back navigation control is a back button or other icon that, when activated (e.g., by a tap gesture), causes the device to replace the display of a current user interface in the application with the display of a previous user interface displayed in the application. In some embodiments, the first user interface is the current user interface of the application, and the display of the current user interface was preceded by the display of a previous sequence of user interfaces of the application. In some embodiments, by activating the back navigation control provided on the user interface, the previous sequence of user interfaces of the application is navigated in reverse chronological order.

In some embodiments, user interfaces for applications are arranged in a hierarchical structure, and a back navigation control is a back button or other icon that, when activated (e.g., by a tap gesture), causes the device to replace display of a current user interface at a first level of the hierarchy with display of a previous user interface at a second level in the hierarchy, where the second level is adjacent to and higher than the first level in the hierarchy. In some embodiments, the first user interface is a current user interface for the application, and display of the current user interface was preceded by display of a previous sequence of user interfaces in the hierarchy. In some embodiments, the hierarchical sequence of user interfaces for the application is navigated in reverse hierarchical order by activating the back navigation control. For example, a hierarchical sequence (including multiple levels of mailboxes and inboxes) in an email application is navigated in reverse hierarchical order by activating a back navigation control provided on the user interface.

While displaying a first user interface of a first application on the display, the device detects (1504) a gesture of a first contact on the touch-sensitive surface at a location corresponding to a back navigation control on the display (e.g., a tap gesture including contact 612 in FIG. 6M or a tap gesture including contact 624 in FIG. 6O ).

In response to detecting a gesture (1506) by a first contact on the touch-sensitive surface at a location corresponding to a back navigation control: in accordance with determining that the gesture by the first contact is a gesture (e.g., a stationary deep press gesture) having an intensity of the first contact that satisfies one or more predetermined intensity criteria (e.g., the intensity of the first contact during the gesture meets or exceeds a predetermined threshold intensity, such as a deep press intensity threshold), the device replaces (1508) display of a first user interface of the first application with a display of representations of multiple user interfaces of the first application, including a representation of the first user interface and a representation of the second user interface. For example, as shown in Figures 6M-6N, device 100 determines that contact 612 includes an intensity that satisfies the deep press intensity threshold and, in response, displays user interface representations 508, 618, and 622 of previously displayed web browsing user interfaces 502, 616, and 620, respectively.

In some embodiments, the deep press gesture is not required to be made on the back navigation control, on the area of the touch-sensitive surface corresponding to the left edge of the display, or in an area of the touch-sensitive surface corresponding to the left edge of the display. In some embodiments, the deep press gesture is not required to be made on the area of the touch-sensitive surface corresponding to the back navigation control, but anywhere on the touch-sensitive surface. In some embodiments, the gesture with the flat portion of the thumb is made with the first contact.

In response to detecting a gesture (1506) by a first contact on the touch-sensitive surface at a location corresponding to a back navigation control: based on determining that the gesture by the first contact is a gesture (e.g., a tap gesture) with an intensity of the first contact that does not meet one or more predetermined intensity criteria (e.g., the intensity of the first contact remains below a predetermined threshold intensity during the gesture), the device replaces (1510) display of the first user interface of the first application with display of the second user interface of the first application (e.g., without displaying other user interfaces in the first application other than the second user interface). For example, as shown in Figures 6O-6P, device 100 determines that contact 624 does not include an intensity that meets the deep press intensity threshold, and in response, displays user interface 616 corresponding to the web browsing user interface that was displayed before displaying web browsing user interface 502.

In some embodiments, the second user interface representation corresponds ( 1512 ) to a user interface in the first application that was displayed immediately before the first user interface of the first application was displayed.

In some embodiments, the user interfaces in the first application are arranged in a hierarchical structure, and the second user interface corresponds ( 1514 ) to a user interface adjacent to and higher than the first user interface in the hierarchical structure.

It should be understood that the particular order in which the operations in FIG. 15 have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations may be performed. One of ordinary skill in the art will recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., methods 1000, 1100, 1200, 1300, 1400, 2400, and 2500) also apply in a similar manner to method 1500 described above with respect to FIG. 15 . For example, the contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described above with reference to the methods may optionally have one or more of the characteristics of the contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described herein with reference to other methods described herein (e.g., methods 1000, 1100, 1200, 1300, 1400, 2400, and 2500). For the sake of brevity, these details are not repeated here.

Figures 24A-24F illustrate a flow diagram of a method 2400 for navigating between user interfaces in accordance with some embodiments. Method 2400 is performed on an electronic device (e.g., device 300 of Figure 3 or portable multifunction device 100 of Figure 1A) having a display and a touch-sensitive surface. In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on or integrated with the display. In some embodiments, the display is separate from the touch-sensitive surface. In some embodiments, the touch-sensitive surface is a portion of a trackpad or remote control device that is separate from the display. In some embodiments, the operations in method 2400 are performed by an electronic device configured to manage, play back, and/or stream (e.g., from an external server) audio and/or visual files that communicates with a remote control and display (e.g., an Apple TV from Apple Inc. of Cupertino, California). Some operations in method 2400 may optionally be combined, and/or the order of some operations may optionally be changed.

As described below, method 2400 provides an intuitive way to navigate between user interfaces. The method reduces the cognitive burden on users when navigating between user interfaces, thereby creating a more efficient human-computer interface. For battery-operated electronic devices, enabling users to navigate between user interfaces faster and more efficiently conserves power and increases the time between battery charges.

The device displays (2402) a user interface for an application on a display. The device detects (2404) an edge input, including detecting a change in a characteristic intensity of a contact adjacent to an edge of a touch-sensitive surface. In response to detecting the edge input: based on determining that the edge input meets system gesture criteria, the device performs (2406) an application-independent operation (e.g., detection of the system gesture criteria overrides detection of the application gesture criteria; e.g., performing the application-independent operation even when the application gesture criteria are also met). The system gesture criteria include an intensity criterion. In some embodiments, the intensity criterion is met when a characteristic intensity of the contact is above a first intensity threshold (e.g., a light press "IT _L " threshold). The system gesture criteria include a location criterion that is met when the intensity criterion for the contact is met when (a predetermined portion of) the contact is within a first area relative to the touch-sensitive surface (e.g., an area that may or may not include a portion of the touch-sensitive surface). The first area relative to the touch-sensitive surface is determined based on one or more characteristics of the contact.

In some embodiments, a change in a characteristic intensity of a contact adjacent to an edge of the touch-sensitive surface is detected (2408) at a location corresponding to a corresponding operation in the application.

In some embodiments, in response to detecting the edge input: based on determining that the edge input satisfies the application gesture criteria but does not satisfy the system gesture criteria, the device performs (2410) a corresponding operation in the application instead of performing the application-independent operation. In some embodiments, based on determining that the edge input does not satisfy the system gesture criteria and does not satisfy the application gesture criteria, the device forgoes performing the application-independent operation and the corresponding operation in the application.

In some embodiments, the intensity criterion (2412) is met when: a (detected) characteristic intensity of the contact adjacent to the edge of the touch-sensitive surface is above a first intensity threshold; and a (detected) characteristic intensity of the contact adjacent to the edge of the touch-sensitive surface is below a second intensity threshold. In some embodiments, detecting an increase in the characteristic intensity of the input above the second intensity threshold invokes a multitasking UI without requiring movement of the contact.

In some embodiments, a first region relative to the touch-sensitive surface has (2414) a first boundary (e.g., a first size and position) when a contact adjacent to an edge of the touch-sensitive surface has a first spatial property (e.g., a large, oblong contact characteristic of a flat finger input), and has a second boundary (e.g., a second size and/or position) different from the first boundary when the contact adjacent to the edge of the touch-sensitive surface has a second spatial property (e.g., a small, circular contact characteristic of a fingertip input). In some embodiments, the size and/or position of the region changes dynamically with the size of the contact. In some embodiments, the contact is classified, and one of a plurality of regions of different sizes and/or shapes is selected based on the classification of the contact.

In some embodiments, detecting an edge input includes (2416): detecting a first portion of a contact on the touch-sensitive surface adjacent to an edge of the touch-sensitive surface; and inferring a second portion of the contact adjacent to the edge of the touch-sensitive surface based on the first portion of the contact, the second portion extending beyond the edge of the touch-sensitive surface, wherein a position of the contact for purposes of satisfying the position criteria is determined at least in part based on the inferred second portion of the contact (e.g., a position of the second portion of the contact adjacent to the edge of the touch-sensitive surface having a maximum distance from the edge of the touch-sensitive surface based on a projection of the position of the second portion of the contact) (e.g., the contact is projected to the left, and the position determination is based on the leftmost portion of the contact).

In some embodiments, based on determining that the contact adjacent to an edge of the touch-sensitive surface has a first spatial property, a first area relative to the touch-sensitive surface is positioned (2418) completely off the touch-sensitive surface (e.g., in an area that begins outside the touch-sensitive surface and extends away from the edge of the touch-sensitive surface where the first portion of the first contact is detected, such that the determination of whether the contact is within the first area is based on a second portion of the contact extending beyond the presumed edge of the touch-sensitive surface); and based on determining that the contact adjacent to an edge of the touch-sensitive surface has a second spatial property, the first area relative to the touch-sensitive surface includes a first portion on the touch-sensitive surface adjacent to the edge of the touch-sensitive surface and a second portion extending away from the touch-sensitive surface from the edge of the touch-sensitive surface (e.g., in an area that begins within the touch-sensitive surface but extends away from the edge of the touch-sensitive surface away from the first portion of the first contact, such that the determination of whether the contact is within the first area can be based on the second portion of the contact extending beyond the presumed edge of the touch-sensitive surface or based on the portion of the contact detected on the touch-sensitive surface (e.g., if the contact is detected entirely on the touch-sensitive surface)).

In some embodiments, based on determining that the contact adjacent to the edge of the touch-sensitive surface has a first spatial property, the first area relative to the touch-sensitive surface is positioned (2420) completely off the touch-sensitive surface so as to extend away from a first boundary that is located at a fixed distance from the edge of the touch-sensitive surface (e.g., in an area that begins outside the touch-sensitive surface and extends away from the edge of the touch-sensitive surface where the first portion of the first contact is detected, such that the determination of whether the contact is within the first area is based on a second portion of the contact that extends beyond the edge of the touch-sensitive surface); and based on determining that the contact adjacent to the edge of the touch-sensitive surface has a second spatial property, the first area relative to the touch-sensitive surface is positioned completely off the touch-sensitive surface so as to extend away from a second boundary that is located at a second fixed distance from the edge of the touch-sensitive surface, where the second fixed distance is shorter than the first fixed distance (e.g., a boundary corresponding to a flat finger input is closer to the edge of the touch-sensitive surface than a boundary corresponding to a fingertip input).

In some embodiments, based on determining that a portion (e.g., a second portion) of the contact adjacent to an edge of the touch-sensitive surface extends beyond the edge of the touch-sensitive surface, based on a projection of the position of the (second) portion of the contact that extends beyond the edge of the touch-sensitive surface, the position of the contact is (2422) the position of the (second) portion of the contact that extends farthest from the edge of the touch-sensitive surface (e.g., when the contact extends beyond the touch-sensitive surface, the position of the contact is defined as the point farthest from the edge); and based on determining that the portion of the contact adjacent to the edge of the touch-sensitive surface does not extend beyond the edge of the touch-sensitive surface, the position of the contact is the position of the contact closest to the edge of the touch-sensitive surface (e.g., when the contact is entirely on the touch-sensitive surface, the position of the contact is defined as the point closest to the edge. In some embodiments, the position of the contact is defined as the average position of multiple points on the leading (e.g., left) edge of the contact). In some embodiments, the position of the contact is defined as the center of mass of the contact.

In some embodiments, the one or more characteristics relative to the first area of the touch-sensitive surface are based on include (2424) the size of the contact adjacent to an edge of the touch-sensitive surface (e.g., contact shape characteristics for a fingertip input invoke a more restrictive activation area than contact shape characteristics for a flat finger input).

In some embodiments, the size of a contact adjacent to an edge of the touch-sensitive surface is (2426) based on one or more of: a measurement of the capacitance of the contact, the shape of the contact, and the area of the contact (e.g., a flat thumb is indicated by: a larger Signal Total, which is a normalized sum of the capacitance of the contact (e.g., how firmly contact is made with the touch-sensitive surface); a larger geomean (geomean) radius √((major axis)2 + (minor axis)2) (e.g., which indicates the area of the contact and is larger for more oblong contacts); and a larger minor radius (e.g., which indicates whether the finger is lying flat on the touch-sensitive surface)).

In some embodiments, the difference (2428) between the first boundary of the first area and the second boundary of the first area is greater near a central portion of the edge of the touch-sensitive surface and is smaller near a distal portion of the edge of the touch-sensitive surface (e.g., the distance between the boundary of the first area and the boundary of the second area decreases toward a corner of the touch-sensitive surface). In some embodiments, the first boundary of the first area and the second boundary of the first area coincide within a predetermined distance from a corner of the touch-sensitive surface. In some embodiments, when a contact adjacent to an edge of the screen has a second spatial property: based on determining that the location of the contact is adjacent to a corner of the touch-sensitive surface, the first area has a second size that is the same as the first size (e.g., an expanded activation area is not available at a corner of the touch-sensitive surface to avoid accidental activation by a user's palm when reaching across the device); and based on determining that the location of the contact is not adjacent to a corner of the touch-sensitive surface, the first area has a second size that is larger than the first size.

In some embodiments, a first area relative to the touch-sensitive surface has (2430) a first or second size (e.g., depending on the size of the contact) when a contact adjacent to an edge of the touch-sensitive surface moves at a speed above a first speed threshold (e.g., input parameters detected above a given threshold include input parameters detected at a given threshold (e.g., "above" means "at or above"), and has a third size when the contact adjacent to the edge of the touch-sensitive surface moves at a speed below the first speed threshold. In some embodiments, the touch must initiate within the first area (e.g., 5 mm), and a characteristic intensity must be detected increasing above an intensity threshold while the contact moves above the speed threshold and within a second area (e.g., 20 mm). In some embodiments (e.g., where an application associates location with an edge swipe operation), if the contact does not meet the system gesture criteria, the device performs an application-specific operation (e.g., navigating within the application).

In some embodiments, the system gesture criteria also include (2432) directional criteria that specify a predetermined direction of movement on the touch-sensitive surface, wherein the directional criteria is satisfied when a contact adjacent to an edge of the touch-sensitive surface moves in a predetermined direction on the touch-sensitive surface (e.g., a movement that is more vertical than horizontal).

In some embodiments, after initiating performance of the application-independent operation: the device detects (2434) movement of a contact on the touch-sensitive surface adjacent to an edge of the touch-sensitive surface. In response to detecting the movement of the contact: based on determining that the movement of the contact is in a predetermined direction, the device continues to perform the application-independent operation; and based on determining that the movement of the contact is in a direction different from the predetermined direction, the device terminates performance of the application-independent operation.

In some embodiments, the system gesture criteria also include (2436) a failure condition that prevents a contact adjacent to an edge of the touch-sensitive surface from satisfying the system gesture criteria when the contact moves outside a second region relative to the touch-sensitive surface (e.g., on the touch-sensitive surface) (e.g., more than 20 mm from the edge) before the system gesture criteria are satisfied (e.g., the system gesture criteria is still not satisfied even if the contact moves back into the region). For example, before initiating performance of an application-independent operation: the device detects movement of a contact adjacent to the edge of the touch-sensitive surface on the touch-sensitive surface; and in response to detecting movement of the contact, based on determining that the contact moves outside the second region relative to the touch-sensitive surface, the device prevents satisfaction of the system gesture criteria (e.g., the device prevents performance of the application-independent operation). While preventing satisfaction of the system gesture criteria, the device detects termination of the input (e.g., including lift-off of the contact adjacent to the edge of the touch-sensitive surface); and in response to detecting termination of the input, the device ceases preventing satisfaction of the system gesture criteria.

In some embodiments, the system gesture criteria include (2438) a requirement (e.g., an additional requirement) that a characteristic intensity of a contact adjacent to an edge of the touch-sensitive surface increases from an intensity below an intensity threshold to an intensity at or above the intensity threshold while the contact is within a first region relative to the touch-sensitive surface (e.g., the system gesture criteria is not met if the characteristic intensity of the contact increases above the intensity threshold while the contact is outside the first region and then the contact moves into the first region without decreasing the characteristic intensity of the contact to below the intensity threshold).

In some embodiments, the intensity criterion varies based on time (2440) (e.g., relative to the first detection of contact proximate to an edge of the touch-sensitive surface or the detection of a change in intensity of the contact; e.g., adding 150g to the intensity threshold for the first 100ms after a touch down).

In some embodiments, the application-independent operation (eg, system operation) is ( 2442 ) an operation for navigating between applications of the electronic device (eg, a multitasking operation; eg, switching to a different/previous application or entering a multitasking user interface).

In some embodiments, the corresponding operation in the application is (2444) a key press operation (eg, a character insertion operation for a keyboard, or a keyboard switching operation, or a shift key activating an option).

In some embodiments, the corresponding operation in the application is (2446) a page switching operation (eg, next page, previous page, etc.).

In some embodiments, the corresponding operation (2448) in the application is used to navigate within a hierarchical structure associated with the application, such as between levels of the application (e.g., songs compared to a playlist) or the history of the application (e.g., back and forward within a web browsing history).

In some embodiments, the corresponding operation in the application is ( 2450 ) a preview operation (eg, peek and pop a link or row in a list).

In some embodiments, the corresponding operation in the application is ( 2452 ) a menu display operation (eg, a quick action or a touch menu).

It should be understood that the particular order in which the operations in Figures 24A-24F have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations may be performed. One of ordinary skill in the art will recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., methods 1000, 1100, 1200, 1300, 1400, 1500, and 2500) also apply in a similar manner to method 2400 described above with respect to Figures 24A-24F. For example, the contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described above with reference to the methods may optionally have one or more of the characteristics of the contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described herein with reference to other methods described herein (e.g., methods 1000, 1100, 1200, 1300, 1400, 1500, and 2500). For the sake of brevity, these details are not repeated here.

Figures 25A-25H illustrate a flow diagram of a method 2500 for navigating between user interfaces in accordance with some embodiments. Method 2500 is performed on an electronic device (e.g., device 300 of Figure 3 or portable multifunction device 100 of Figure 1A) having a display and a touch-sensitive surface. In some embodiments, the display is a touch screen display, and the touch-sensitive surface is on or integrated with the display. In some embodiments, the display is separate from the touch-sensitive surface. In some embodiments, the touch-sensitive surface is a portion of a trackpad or remote control device that is separate from the display. In some embodiments, the operations in method 2500 are performed by an electronic device configured to manage, play back, and/or stream (e.g., from an external server) audio and/or visual files that communicates with a remote control and display (e.g., an Apple TV from Apple Inc. of Cupertino, California). Some operations in method 2500 may optionally be combined, and/or the order of some operations may optionally be changed.

As described below, method 2500 provides an intuitive way to navigate between user interfaces. The method reduces the cognitive burden on users when navigating between user interfaces, thereby creating a more efficient human-computer interface. For battery-operated electronic devices, enabling users to navigate between user interfaces faster and more efficiently conserves power and increases the time between battery charges.

The device displays (2502) a first view of a first application on a display. While displaying the first view, the device detects (2504) a first portion of a first input, including detecting a first contact on a touch-sensitive surface. In response to detecting the first portion of the first input, based on a determination that the first portion of the first input meets application switching criteria (e.g., including intensity criteria (e.g., "glance" intensity) and location criteria (e.g., proximity to an edge of the touch-sensitive surface) or an intensity-based edge swipe heuristic such as described above with reference to method 2400), the device simultaneously displays (2506) portions of multiple application views on the display including the first application view and a second application view (and optionally stops displaying another portion of the first application view (e.g., by sliding the portion of the first application view off the display)). While simultaneously displaying the portions of the multiple application views, the device detects (2508) a second portion of the first input including liftoff of the first contact. In response to detecting a second portion of the first input including a lift-off of the first contact: based on determining that the second portion of the first input satisfies first view display criteria, the device stops (2510) displaying a portion of the second application view on the display and displays the (entire) first application view, wherein the first view display criteria include criteria that are satisfied when lift-off of the first contact is detected in a first area of the touch-sensitive surface (e.g., a portion adjacent to a left edge of the touch-sensitive surface); and based on determining that the second portion of the first input satisfies multi-view display criteria, after detecting lift-off of the first contact, the device maintains simultaneous display of at least a portion of the first application view and at least a portion of the second application view on the display, wherein the multi-view display criteria include criteria that are satisfied when lift-off of the first contact is detected in a second area of the touch-sensitive surface that is different from the first area of the touch-sensitive surface (e.g., a middle portion of the touch-sensitive surface).

In some embodiments, in response to detecting a second portion of the first input that includes a lift-off of the first contact: based on determining that the second portion of the first input satisfies second view display criteria, the device stops (2512) displaying the first application view on the display and displays the (entire) second application view, where the second view display criteria include criteria that are met when the lift-off of the first contact is detected in a third area of the touch-sensitive surface that is different from the first area of the touch-sensitive surface and the second area of the touch-sensitive surface (for example, a portion adjacent to the right edge of the touch-sensitive surface).

In some embodiments, after detecting a first portion of the first input including detecting a first contact on the touch-sensitive surface, and before detecting a second portion of the first input including a lift-off of the first contact: the device detects (2514) movement of the first contact on the touch-sensitive surface. In response to detecting the movement of the first contact, based on determining that the first contact has moved into a second area of the touch-sensitive surface, the device reduces respective sizes of a plurality of application views including a first application view and a second application view. In some embodiments, as the contact continues to move across the second area of the touch-sensitive surface, the sizes of the application views are dynamically reduced (e.g., there is a correlation between how far the contact has traveled across the second area and the sizes of the application views). In some embodiments, reducing the size of the application views while the contact is in the second area of the touch-sensitive surface indicates to the user that the lift-off of the contact in the second area will invoke a multitasking user interface. In some embodiments, a portion of the second application view shrinks and moves in the direction of the movement of the contact in the second area (e.g., simulating a dynamic shrinking and sliding of an application "card" away from a "stack"). In some embodiments, a distance between two or more application views in the application view changes based on the movement of the first contact (e.g., in addition to reducing in size as the first contact moves across the display, application views other than the top application view move apart).

In some embodiments, while reducing the respective sizes of the plurality of application views including the first application view and the second application view: the device detects (2516) continued movement of the first contact on the touch-sensitive surface. In response to detecting the continued movement of the first contact, based on determining that the first contact has moved into a third area of the touch-sensitive surface, the device increases the respective sizes of the plurality of application views including the first application view and the second application view. In some embodiments, the sizes of the application views are dynamically increased as the contact continues to move across the third area of the touch-sensitive surface (e.g., there is a correlation between how far the contact has traveled across the third area and the sizes of the application views). In some embodiments, increasing the size of the application views while the contact is in the third area of the touch-sensitive surface indicates to the user that lifting off the contact in the third area will activate the application associated with the second application view (e.g., switching to the previous application). In some embodiments, a portion of the second application view expands and moves in a direction opposite to the movement of the contact in the third area (e.g., simulating the second application view dynamically expanding into a user interface for a second user). In some embodiments, the distance between two or more application views in the application view changes based on the movement of the first contact (e.g., in addition to increasing in size as the first contact continues to move across the display, application views other than the top application view also move together).

In some embodiments, after detecting a first portion of the first input including detecting a first contact on the touch-sensitive surface and before detecting a second portion of the first input including lift-off of the first contact: the device detects (2518) movement of the first contact on the touch-sensitive surface. In response to detecting the movement of the first contact, the device provides a tactile output based on determining that the first contact crosses a boundary between two corresponding areas on the touch-sensitive surface. In some embodiments, the device provides tactile feedback when the contact moves from the second area of the touch-sensitive surface into the third area of the touch-sensitive surface, but not when the contact moves from the third area back to the second area.

In some embodiments, the display of respective portions of the multiple application views (2520) partially overlaps, including a displayed portion of a first application view partially overlapping a displayed portion of a second application view.

In some embodiments, the first application view and the second application view are (2522) views of the same application (eg, web page tabs).

In some embodiments, the first application view is ( 2524 ) a view of a first application, and the second application view is a view of a second application different from the first application.

In some embodiments, based on determining that the second portion of the first input satisfies multi-view display criteria (wherein the multi-view display criteria include criteria that are satisfied when lift-off of the first contact is detected in a second area of the touch-sensitive surface that is different from the first area of the touch-sensitive surface), maintaining simultaneous display of at least a portion of the first application view and at least a portion of the second application on the display includes (2526): entering a user interface selection mode; and displaying a plurality of user interface representations in a stack on the display, including at least a portion of the first application view and at least a portion of the second application view, wherein: at least a first user interface representation corresponding to at least a portion of the second application view and at least a second user interface representation corresponding to at least a portion of the first application view and disposed above the first user interface representation in the stack are visible on the display, the second user interface representation is offset from the first user interface representation in a first direction (e.g., offset laterally to the right on the display), and the second user interface representation partially exposes the first user interface representation. In some embodiments, the representations in the stack are partially expanded in one direction on the display (e.g., to the right as shown in Figures 5P and 22C). In some embodiments, at a given time, information (e.g., icons, titles, and content for corresponding user interfaces) for a predetermined number of representations in the stack (e.g., 2, 3, 4, or 5 representations) is visible, while the remaining representations in the stack are off-screen or below the representations that include visible information. In some embodiments, the representations below the representations that include visible information are stacked so closely together that no information is displayed for those representations. In some embodiments, the representations below the representations that include visible information are style representations, such as just a generic edge 503 as shown in FIG. 5P .

In some embodiments, while in user interface selection mode: the device detects (2528) a second input comprising a drag gesture via a second contact at a location on the touch-sensitive surface corresponding to a location of a first user interface representation on the display, the second contact moving across the touch-sensitive surface in a direction corresponding to a first direction on the display; and while the second contact is at a location on the touch-sensitive surface corresponding to the location of the first user interface representation on the display and moving across the touch-sensitive surface in a direction corresponding to the first direction on the display: the device moves the first user interface representation in the first direction on the display at a first speed according to a speed of the second contact on the touch-sensitive surface; and the device moves a second user interface representation disposed above the first user interface representation in the first direction at a second speed greater than the first speed. For example, with respect to moving the first user interface representation, on the touch-sensitive display, a card or other representation below the finger contact moves at the same speed as the finger contact; and on a display coupled to a track pad, a card or other representation at a location corresponding to the location of the contact moves at an on-screen speed corresponding to (or based on) the speed of the finger contact on the track pad. In some embodiments, a focus selector is shown on the display to indicate an on-screen location corresponding to the location of the contact on the touch-sensitive surface. In some embodiments, the focus selector can be represented by a cursor, a movable icon, or a visual distinguisher that separates an on-screen object (e.g., a user interface representation) from its non-focus counterpart. In another example, with respect to moving the second user interface representation, in some embodiments, the first direction is to the right. In some embodiments, the first speed is the same speed as the current speed of the contact. In some embodiments, the movement of the first user interface representation creates a visual effect that the finger contact is grabbing and dragging the first user interface representation. At the same time, the second user interface representation is moving faster than the first user interface representation. This faster movement of the second user interface representation creates the following visual effect: as the second user interface representation moves in the first direction toward the edge of the display, a larger and larger portion of the first user interface representation appears from under the second user interface representation. In combination, these two simultaneous movements enable the user to see more of the first user interface representation before deciding whether to select and display the corresponding first user interface.

In some embodiments, while in a user interface selection mode comprising displaying at least two user interface representations from a plurality of user interface representations in a stack, the device detects (2530) a selection input (e.g., a tap gesture at a location on the user interface representation corresponding to a location on the user interface representation) relating to one of the at least two user interface representations in the stack. In response to detecting the selection input: the device stops displaying the stack and displays a user interface corresponding to the selected one of the at least two user interface representations. In some embodiments, the user interface corresponding to the selected user interface representation is displayed without displaying any user interfaces corresponding to other user interface representations in the stack. In some embodiments, the display of the user interface corresponding to the selected user interface representation replaces display of the stack.

In some embodiments, while displaying at least a first user interface representation and a second user interface representation above the first user interface representation in a stack: the device detects (2532) a deletion input involving the first user interface representation (e.g., an upward drag gesture on the touch-sensitive surface at a location corresponding to a location on the first user interface representation). In response to detecting the deletion input involving the first user interface representation: the device removes the first user interface representation from the first location in the stack. In some embodiments, upon swiping to close, adjacent application views move together in z-space (e.g., an application view behind the application view being manipulated moves toward the current application view). If the movement is in opposite directions, the adjacent application views move away from each other in z-space (e.g., the application view behind the application view being manipulated moves away from the current application view).

In some embodiments, entering the user interface selection mode includes (2534): animating a reduction in size of the first application view upon transitioning to the second user interface representation; and animating a reduction in size of the second application view upon transitioning to the first user interface representation. For example, in the "peek" stage, the UI card is referred to as the application view, and in the "pop-up" stage (e.g., the multitasking user interface), the UI card is referred to as the user interface representation. In some embodiments, the device indicates to the user that the device has entered the multitasking user interface by reducing the size of the application view (e.g., it becomes the user interface representation).

In some embodiments, the application switching criteria include (2536) an intensity criterion. In some embodiments, the intensity criterion is satisfied when a characteristic intensity of the contact is above a first intensity threshold. In some embodiments, the system gesture criteria include a location criterion that is satisfied when the intensity criterion for the contact is satisfied when the contact is within a first area relative to the touch-sensitive surface (e.g., an area that may or may not include a portion of the touch-sensitive surface, such as those described above with reference to method 2400).

In some embodiments, a size of a first area relative to the touch-sensitive surface is determined (2538) based on one or more characteristics of the contact. In some embodiments, the first area relative to the touch-sensitive surface has a first size when the contact adjacent to an edge of the touch-sensitive surface has a first spatial property (e.g., a large, oblong contact characteristic of a flat finger input) and has a second size when the contact adjacent to the edge of the touch-sensitive surface has a second spatial property (e.g., a small, circular contact characteristic of a fingertip input). In some embodiments, the size of the area changes dynamically with the size of the contact. In some embodiments, the contact is categorized and one of a plurality of discretely sized areas is selected.

In some embodiments, the intensity criteria for applying the switching criteria are satisfied (2540) when: the (detected) characteristic intensity of the first contact is above a first intensity threshold (e.g., a glance/preview intensity threshold); and the (detected) characteristic intensity of the second contact is below a second intensity threshold (e.g., a pop-up/delivery intensity threshold).

In some embodiments, in response to detecting the first portion of the first input, the device provides (2542) a tactile output based on determining that the first portion of the first input satisfies application switching criteria.

In some embodiments, in response to detecting the first portion of the first input, based on determining that the first portion of the first input meets the preview criteria: the device moves (2544) the first view of the first application partially off the display (e.g., sliding the active user interface to the right with or without reducing the size of the user interface), and displays a portion of the second application view on the display at a location from which the first view of the first application was displaced (e.g., the active user interface slides over, thereby revealing the edge of the previously active user interface from under the currently active user interface).

In some embodiments, the preview criteria include (2546): a location criterion that is satisfied when the contact is within a first area relative to the touch-sensitive surface, and an intensity criterion that is satisfied when a characteristic intensity of the contact is above a preview intensity threshold (e.g., a "hint" intensity) and below an apply-switch intensity threshold (e.g., a "glance" intensity/first intensity threshold).

In some embodiments, the application switching criteria include (2548) criteria that are satisfied when the intensity of the first contact increases to above a first intensity threshold (e.g., a peek/preview intensity threshold); maintaining simultaneous display of at least a portion of the first application view and at least a portion of the second application view on the display after detecting liftoff of the first contact includes displaying a multitasking user interface; and in response to detecting the first portion of the first input, based on determining that the first portion of the first input satisfies the multitasking criteria, the device displays the multitasking user interface, the multitasking criteria including criteria that are satisfied when the intensity of the first contact increases to above a second intensity threshold that is greater than the first intensity threshold. For example, the multitasking user interface can be displayed by satisfying the application switching criteria (which can be satisfied with a contact having an intensity above the first intensity threshold and below the second intensity threshold) and then moving the contact across the touch-sensitive surface to a position corresponding to a middle portion of the display; or by satisfying the multitasking criteria, which can be satisfied with a contact having an intensity above the second intensity threshold.

In some embodiments, in response to detecting the first portion of the first input, in accordance with determining that the first portion of the first input meets multitasking criteria (e.g., including a high intensity criterion (e.g., "pop-up" intensity) and, optionally, a position criterion (e.g., adjacent to an edge of the touch-sensitive surface, in the first region, or in the second region)): the device enters (2250) a user interface selection mode and displays a plurality of user interface representations in a stack on the display, including at least a portion of the first application view and at least a portion of the second application view. In some embodiments, at least a first user interface representation corresponding to at least a portion of the second application view and at least a second user interface representation corresponding to at least a portion of the first application view and disposed above the first user interface representation in the stack are visible on the display, the second user interface representation is offset from the first user interface representation in a first direction (e.g., offset laterally to the right on the display), and the second user interface representation partially exposes the first user interface representation. In some embodiments, the representations in the stack are partially expanded in one direction on the display (e.g., to the right as shown in Figures 5P and 23G). In some embodiments, at a given time, information (e.g., icons, titles, and content for a corresponding user interface) for a predetermined number of representations in the stack (e.g., 2, 3, 4, or 5 representations) is visible, while the remaining representations in the stack are off-screen or below the representations that include visible information. In some embodiments, the representations below the representations that include visible information are stacked so closely together that no information is displayed for those representations. In some embodiments, the representations below the representations that include visible information are style representations, such as just a generic edge 503 as shown in FIG. 5E .

In some embodiments, the multitasking criteria include ( 2552 ) an intensity criterion that is met when a (detected) characteristic intensity of the first contact is above a second intensity threshold.

In some embodiments, the multitasking criteria include ( 2554 ) a location criterion that is satisfied when the multitasking intensity criterion is satisfied when the contact is within the first area of the touch-sensitive surface.

It should be understood that the particular order in which the operations in Figures 25A-25H have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations may be performed. Those of ordinary skill in the art will recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., methods 1000, 1100, 1200, 1300, 1400, 1500, and 2400) also apply in a similar manner to method 2500 described above with respect to Figures 25A-25H. For example, the contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described above with reference to the methods may optionally have one or more of the characteristics of the contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described herein with reference to other methods described herein (e.g., methods 1000, 1100, 1200, 1300, 1400, 1500, and 2400). For the sake of brevity, these details are not repeated here.

According to some embodiments, Figure 16 shows a functional block diagram of an electronic device 1600 configured according to the principle of the various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of hardware and software to implement the principle of the various described embodiments. Those skilled in the art will appreciate that the functional blocks described in Figure 16 are optionally combined or separated into sub-blocks to implement the principle of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or other limitations of the functional blocks described herein.

As shown in FIG16 , electronic device 1600 includes a display unit 1602 configured to display a user interface; a touch-sensitive surface unit 1604 configured to receive contacts; optionally, one or more sensor units 1606 configured to detect intensity of contacts with touch-sensitive surface unit 1604; and a processing unit 1608 coupled to display unit 1602, touch-sensitive surface unit 1604, and the optional one or more sensor units 1606. In some embodiments, processing unit 1608 includes a display implementation unit 1610, a detection unit 1612, a movement unit 1614, an entry unit 1616, a presentation unit 1618, a determination unit 1620, an application unit 1622, an insertion unit 1624, and a removal unit 1626.

The processing unit 1610 is configured to: implement displaying multiple user interface representations in a stack on the display unit 1602 (for example, using the display implementation unit 1610), wherein: at least a first user interface representation and a second user interface representation arranged above the first user interface representation in the stack are visible on the display unit 1602, the second user interface representation is offset from the first user interface representation in a first direction, and the second user interface representation partially exposes the first user interface representation; detect a first drag gesture by a first contact at a position on the touch-sensitive surface unit 1604 corresponding to the position of the first user interface representation on the display unit 1602 (for example, using the detection unit 1612), the first contact being at a position corresponding to the position of the first user interface representation on the display unit 1602; and when the first contact is at a position on the touch-sensitive surface unit 1604 corresponding to the position of the first user interface representation on the display unit 1602 and moves across the touch-sensitive surface unit 1604 in a direction corresponding to the first direction on the display unit: moving the first user interface representation in the first direction on the display unit 1602 at a first speed according to the speed of the first contact on the touch-sensitive surface unit 1604 (for example, using moving unit 1614); and moving a second user interface representation that is disposed above the first user interface representation in the first direction at a second speed that is greater than the first speed (for example, using moving unit 1614).

According to some embodiments, Figure 17 shows a functional block diagram of an electronic device 1700 configured according to the principles of the various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of hardware and software to implement the principles of the various described embodiments. Those skilled in the art will appreciate that the functional blocks described in Figure 17 are optionally combined or separated into sub-blocks. To implement the principles of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or other limitations of the functional blocks described herein.

As shown in FIG17 , electronic device 1700 includes a display unit 1702 configured to display a user interface; a touch-sensitive surface unit 1704 configured to receive contacts; one or more sensor units 1706 configured to detect the intensity of contacts with touch-sensitive surface unit 1704; and a processing unit 1708 coupled to display unit 1702, touch-sensitive surface unit 1704, and one or more sensor units 1706. In some embodiments, processing unit 1708 includes a display implementation unit 1710, a detection unit 1712, a movement unit 1714, an entry unit 1716, and an operation execution unit 1718.

The processing unit 1710 is configured to: implement displaying a first user interface on the display unit 1702 (e.g., using the display implementation unit 1710); while the first user interface is displayed on the display unit 1702, detect input through a first contact on the touch-sensitive surface unit 1704 (e.g., using the detection unit 1702); upon detecting input through the first contact, implement displaying a first user interface representation and at least a second user interface representation on the display unit 1702 (e.g., using the display implementation unit 1710); while the first user interface representation and at least the second user interface representation are displayed on the display unit 1702, detect termination of input through the first contact (e.g., using detection unit 1712); and in response to detecting termination of input through the first contact: based on determining that the first contact has a characteristic intensity below a predetermined intensity threshold during the input and the first contact moves in a direction corresponding to a predefined direction on the display 1702 across the touch-sensitive surface 1704 during the input, enabling display of a second user interface corresponding to the second user interface representation (e.g., using display implementation unit 1710); and based on determining that the first contact has a characteristic intensity below a predetermined intensity threshold during the input and the first contact does not move in a direction corresponding to a predefined direction on the display unit 1702 across the touch-sensitive surface unit 1704 during the input, enabling redisplay of the first user interface (e.g., using display implementation unit 1710).

According to some embodiments, Figure 18 shows a functional block diagram of an electronic device 1800 configured according to the principle of the various described embodiments. The functional block of the device is optionally implemented by hardware, software, or a combination of hardware and software to implement the principle of the various described embodiments. Those skilled in the art will appreciate that the functional block described in Figure 18 is optionally combined or separated into sub-blocks to implement the principle of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or other limitation of the functional block described herein.

As shown in FIG18 , electronic device 1800 includes: a display unit 1802 configured to display a user interface; a touch-sensitive surface unit 1804 configured to receive contacts; one or more sensor units 1806 configured to detect the intensity of contacts with touch-sensitive surface unit 1804; and a processing unit 1808 coupled to display unit 1802, touch-sensitive surface unit 1804, and one or more sensor units 1806. In some embodiments, processing unit 1808 includes a display implementation unit 1810, a detection unit 1812, a movement unit 1814, an addition unit 1816, a change unit 1818, and a variation unit 1820.

Processing unit 1810 is configured to: enable display of a first user interface on the display unit (e.g., using display enabling unit 1810); while enabling display of the first user interface on the display unit, detect, on touch-sensitive surface unit 1804, an input of a first contact that includes a period of increasing intensity of the first contact (e.g., using detection unit 1812); in response to detecting the input of the first contact that includes a period of increasing intensity of the first contact: enable display of a first user interface representation for the first user interface and a second user interface representation for the second user interface on display unit 1802 (e.g., using display enabling unit 1810), wherein the first user interface representation is displayed above the second user interface representation and partially exposes the second user interface representation; when displaying the first user interface representation and the second user interface representation on the display unit 1802, detecting that the strength of the first contact meets one or more predetermined strength standards during a period of increasing strength of the first contact (for example, using the detection unit 1812); in response to detecting that the strength of the first contact meets one or more predetermined strength standards: stopping displaying the first user interface representation and the second user interface representation on the display unit 1802 (for example, using the display implementation unit 1810); and implementing display of the second user interface on the display unit 1802 (for example, using the display implementation unit 1810).

According to some embodiments, Figure 19 shows a functional block diagram of an electronic device 1900 configured according to the principle of the various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of hardware and software to implement the principle of the various described embodiments. Those skilled in the art will appreciate that the functional blocks described in Figure 19 are optionally combined or separated into sub-blocks to implement the principle of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or other limitation of the functional blocks described herein.

19 , electronic device 1900 includes a display unit 1902 configured to display a user interface; a touch-sensitive surface unit 1904 configured to receive contacts; one or more sensor units 1906 configured to detect the intensity of contacts with touch-sensitive surface unit 1904; and a processing unit 1908 coupled to display unit 1902, touch-sensitive surface unit 1904, and one or more sensor units 1906. In some embodiments, processing unit 1908 includes a display implementation unit 1910, a detection unit 1912, a movement unit 1914, an increase unit 1916, a decrease unit 1918, and an entry unit 1920.

The processing unit 1910 is configured to: implement display of multiple user interface representations in a stack on the display unit 1902 (for example, using the display implementation unit 1910), wherein: at least a first user interface representation, a second user interface representation, and a third user interface representation are visible on the display unit 1902, the first user interface representation is laterally offset from the second user interface representation in a first direction and partially exposes the second user interface representation, and the second user interface representation is laterally offset from the third user interface representation in the first direction and partially exposes the third user interface representation; detect input through a first contact on the touch-sensitive surface unit 1904 at a position corresponding to the second user interface representation on the display unit 1902 (for example, using the detection unit 1922); and increase the area of the second user interface representation exposed from behind the first user interface representation by increasing the lateral offset between the first user interface representation and the second user interface representation (for example, using the increase unit 1916) based on an increase in the intensity of the first contact detected on the touch-sensitive surface unit 1904 at a position corresponding to the second user interface representation on the display unit 1902 (for example, using the detection unit 1912).

According to some embodiments, Figure 20 shows a functional block diagram of an electronic device 2000 configured according to the principle of the various described embodiments. The functional block of the device is optionally implemented by hardware, software, or a combination of hardware and software to implement the principle of the various described embodiments. Those skilled in the art will appreciate that the functional block described in Figure 20 is optionally combined or separated into sub-blocks to implement the principle of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or other limitation of the functional block described herein.

As shown in Figure 20, electronic device 2000 includes: a display unit 2002 configured to display a user interface; a touch-sensitive surface unit 2004 configured to receive contacts; optionally includes one or more sensor units 2006 configured to detect the intensity of contacts with touch-sensitive surface unit 2004; and a processing unit 2008 coupled to display unit 2002, touch-sensitive surface unit 2004, and the optional one or more sensor units 2006. In some embodiments, processing unit 2008 includes: a display implementation unit 2010, a detection unit 2012, a movement unit 2014, and a presentation unit 2016.

The processing unit 2010 is configured to: implement display of multiple user interface representations in a stack on the display unit 2002 (for example, using the display implementation unit 2010), wherein: at least a first user interface representation, a second user interface representation, and a third user interface representation are visible on the display unit 2002, the second user interface representation is laterally offset from the first user interface representation in a first direction and partially exposes the first user interface representation, and the third user interface representation is laterally offset from the second user interface representation in the first direction and partially exposes the second user interface representation; detect a drag gesture of a first contact moving across the touch-sensitive surface unit 2004 (for example, using the detection unit 2012), wherein the movement of the drag gesture by the first contact corresponds to the movement of one or more user interface representations across the multiple user interface representations in the stack; and during the drag gesture, when the first contact moves over a position on the touch-sensitive surface unit 2004 corresponding to the first user interface representation on the display unit 2002, more of the first user interface representation is revealed from behind the second user interface representation on the display unit (for example, using the revealing unit 2016).

According to some embodiments, Figure 21 shows a functional block diagram of an electronic device 2100 configured according to the principle of the various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of hardware and software to implement the principle of the various described embodiments. Those skilled in the art will appreciate that the functional blocks described in Figure 21 are optionally combined or separated into sub-blocks to implement the principle of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or other limitation of the functional blocks described herein.

As shown in FIG21 , the electronic device 210 includes: a display unit 1602 configured to display a user interface; a touch-sensitive surface unit 2104 configured to receive contacts; one or more sensor units 2106 configured to detect the intensity of contacts with the touch-sensitive surface unit 2104; and a processing unit 2108 coupled to the display unit 2102, the touch-sensitive surface unit 2104, and the one or more sensor units 2106. In some embodiments, the processing unit 2108 includes a display implementation unit 2110 and a detection unit 2112.

The processing unit 2110 is configured to: implement displaying a first user interface of a first application on the display unit 2102 (for example, using the display implementation unit 2110), the first user interface including a back navigation control; when displaying the first user interface of the first application on the display unit 2102, detect a gesture of a first contact on the touch-sensitive surface unit 2104 at a position corresponding to the back navigation control on the display unit 2102 (for example, using the detection unit 2112); in response to detecting a gesture of a first contact on the touch-sensitive surface unit 2104 at a position corresponding to the back navigation control: based on determining that the gesture through the first contact is a gesture with an intensity of the first contact that meets one or more predetermined intensity standards, replace the display of the first user interface of the first application with a display of multiple user interface representations of the first application (including an indication of the first user interface and an indication of the second user interface) (for example, using the display implementation unit 2110); and based on determining that the gesture through the first contact is a gesture with an intensity of the first contact that does not meet one or more predetermined intensity standards, replace the display of the first user interface of the first application with a display of the second user interface of the first application (for example, using the display implementation unit 2110).

According to some embodiments, Figure 26 shows a functional block diagram of an electronic device 2600 configured according to the principle of the various described embodiments. The functional block of the device is optionally implemented by hardware, software, or a combination of hardware and software to implement the principle of the various described embodiments. Those skilled in the art will appreciate that the functional block described in Figure 26 is optionally combined or separated into sub-blocks to implement the principle of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or other limitation of the functional block described herein.

26 , the electronic device includes: a display unit 2602 configured to display a content item; a touch-sensitive surface unit 2604 configured to receive user input; one or more sensor units 2606 configured to detect intensity of contact with the touch-sensitive surface unit 2604; and a processing unit 2608 coupled to the display unit 2602, the touch-sensitive surface unit 2604, and the one or more sensor units 2606. In some embodiments, the processing unit 2608 includes a display enabling unit 2610, a detecting unit 2612, and a determining unit 2614. In some embodiments, processing unit 2608 is configured to: enable display (e.g., with display enabling unit 2610) of a user interface for an application on a display unit (e.g., display unit 2602); detect (e.g., with detection unit 2612) edge input, including detecting a change in characteristic intensity of a contact adjacent to an edge of the touch-sensitive surface; and in response to detecting the edge input: perform an application-independent operation based on determining (e.g., with determination unit 2614) that the edge input satisfies system gesture criteria, wherein: the system gesture criteria include intensity criteria; the system gesture criteria include location criteria that are satisfied when the intensity criteria for the contact are satisfied when the contact is within a first area relative to the touch-sensitive surface; and determining the first area relative to touch-sensitive surface unit 2604 based on one or more characteristics of the contact.

According to some embodiments, Figure 27 shows a functional block diagram of an electronic device 2700 configured according to the principle of the various described embodiments. The functional block of the device is optionally implemented by hardware, software, or a combination of hardware and software to implement the principle of the various described embodiments. Those skilled in the art will appreciate that the functional block described in Figure 27 is optionally combined or separated into sub-blocks to implement the principle of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or other limitation of the functional block described herein.

27 , the electronic device includes a display unit 2702 configured to display a content item; a touch-sensitive surface unit 2704 configured to receive user input; one or more sensor units 2706 configured to detect intensity of contact with the touch-sensitive surface unit 2704; and a processing unit 2708 coupled to the display unit 2702, the touch-sensitive surface unit 2704, and the one or more sensor units 2706. In some embodiments, the processing unit 2708 includes a display enabling unit 2710, a detecting unit 2712, and a determining unit 2714. In some embodiments, the processing unit 2708 is configured to: implement display (e.g., using the display implementation unit 2710) of a first view of a first application on a display unit (e.g., the display unit 2702); when implementing the display of the first view, detect (e.g., using the detection unit 2712) a first portion of the first input, including detecting a first contact on the touch-sensitive surface unit 2704; in response to detecting the first portion of the first input, based on determining (e.g., using the determination unit 2714) that the first portion of the first input meets the application switching criteria, implement displaying (e.g., using the display implementation unit 2710) a portion of multiple application views including the first application view and the second application view on the display unit simultaneously; when implementing the simultaneous display of the portion of multiple application views, detect (e.g., using the detection unit 2712) a second portion of the first input including the lifting of the first contact; and in response to detecting the second portion of the first input including the lifting of the first contact: based on determining (For example, using determination unit 2714) that the second portion of the first input satisfies the first view display criteria, stopping displaying (for example, using display implementation unit 2710) the portion of the second application view on the display unit and implementing displaying (for example, using display implementation unit 2710) the first application view, wherein the first view display criteria include criteria that are satisfied when a lift-off of the first contact is detected in the first area of the touch-sensitive surface unit 2704; and based on determining (for example, using determination unit 2714) that the second portion of the first input satisfies the multi-view display criteria, after detecting the lift-off of the first contact, maintaining simultaneous display (for example, using display implementation unit 2710) of at least a portion of the first application view and at least a portion of the second application view on the display, wherein the multi-view display criteria include criteria that are satisfied when a lift-off of the first contact is detected in a second area of the touch-sensitive surface unit 2704 that is different from the first area of the touch-sensitive surface unit 2704.

The operations in the information processing method described above may optionally be implemented by running one or more functional modules in an information processing device such as a general-purpose processor or a dedicated chip (eg, as described above with respect to FIG. 1A and 3 ).

The operations described above with reference to Figures 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, and 15 may alternatively be implemented by the components depicted in Figures 1A-1B or Figures 16-21. For example, user interface entry operations 1006, 1110, and 1312, visual effect application operations 1018, 1024, 1048, 1208, 1212, 1224, 1320, 1322, 1350, 1408, 1410, 1414, and 1416, detection operations 1030, 1052, 1062, 1080, 1084, 1091, 1092, 1096, 1104, 1116, 1126, 1130, 1138, 1142, 1146, 1204, 1210, 1220, 1232, 1236, 1244, 1248, 1308, 1318, 1328, 1340, 1346, 1350, 1404, 1418, 1426, and 1504, user interface representation insertion operation 1082, user interface representation removal operation 1088, user interface representation move operations 1034, 1036, 1050, 1056, 1058, 1060, 1068, 1070, 1072, 1098, 1150, 1152, 1324, 1326, 1332, 1334, 1336, and 1338, and content-dependent execution operation 1140 are optionally implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects contacts on touch-sensitive display 112, and event dispatcher module 174 delivers event information to application 136-1. The corresponding event recognizer 180 of application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first contact at the first position on the touch-sensitive surface (or whether the rotation of the device) corresponds to a predefined event or sub-event, such as selecting an object on the user interface, or rotating the device from one orientation to another. Upon detecting the corresponding predefined event or sub-event, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally uses or calls data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 192 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, it will be clear to a person of ordinary skill in the art how other processing can be implemented based on the components depicted in Figures 1A-1B.

The foregoing description has been described with reference to specific embodiments for illustrative purposes. However, the above illustrative discussion is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in accordance with the above teachings. For example, the methods described herein are also applicable in a similar manner to electronic devices configured for managing, playing back and/or streaming (e.g., from an external server) audio and/or visual content, which communicate with a remote control and a display (e.g., Apple TV from Apple Inc. of Cupertino, California). For such devices, input corresponding to gestures on a touch-sensitive surface of a remote control, voice input to the remote control, and/or activation of buttons on the remote control is optionally received, rather than having a touch-sensitive surface, an audio input device (e.g., a microphone), and/or buttons on the device itself. For such devices, data is optionally provided to a display, rather than being displayed by the device itself. The embodiments are selected and described in order to best illustrate the principles of the invention and its practical application, so as to enable those skilled in the art to best use the invention and the various described embodiments and various modifications suitable for the specific use envisioned.

Claims (69)

1. An electronic device, comprising: The display unit is configured to display content items; A touch-sensitive surface unit configured to receive user input; One or more sensor units are configured to detect the intensity of contact with the touch-sensitive surface unit; and A processing unit, coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units, is configured to: To display a user interface for the application on the display; Detecting edge input, the edge input including detecting changes in the characteristic intensity of contact adjacent to the edge of the touch-sensitive surface; and In response to the detection of the edge input: Based on the determination that the edge input meets the system gesture standard, perform an operation independent of the application, wherein: The system's gesture standards include intensity standards; The system gesture criteria include a positional criterion that is satisfied when the contact is within a first region relative to the touch-sensitive surface and satisfies the intensity criterion for the contact; and Based on one or more characteristics of the contact, the size and position of the first region relative to the touch-sensitive surface are dynamically adjusted, wherein the one or more characteristics of the contact include the size of the contact located at or adjacent to the edge of the touch-sensitive surface. 2. The electronic device of claim 1, wherein the change in the characteristic intensity of the contact adjacent to the edge of the touch-sensitive surface is detected at a location corresponding to a corresponding operation in the application. 3. The electronic device according to claim 2, wherein the processing unit is configured to: In response to the detection of the edge input: If the edge input is determined to meet the application gesture standard but not the system gesture standard, the corresponding operation in the application is performed instead of the operation independent of the application. 4. The electronic device of claim 1, wherein the strength standard is satisfied when: The characteristic intensity of the contact adjacent to the edge of the touch-sensitive surface is above a first intensity threshold; and The intensity of the characteristic of the contact adjacent to the edge of the touch-sensitive surface is below a second intensity threshold. 5. The electronic device of claim 1, wherein the first region relative to the touch-sensitive surface has a first boundary when the contact adjacent to the edge of the touch-sensitive surface has a first spatial property, and has a second boundary different from the first boundary when the contact adjacent to the edge of the touch-sensitive surface has a second spatial property. 6. The electronic device of claim 1, wherein detecting the edge input comprises: Detecting a first portion of the contact on the touch-sensitive surface adjacent to the edge of the touch-sensitive surface; and Based on the first portion of the contact, a second portion of the contact is inferred to be adjacent to the edge of the touch-sensitive surface, the second portion extending beyond the edge of the touch-sensitive surface. The location of the contact is determined, at least in part, based on the second portion of the inferred contact, for the purpose of satisfying the location criterion. 7. The electronic device according to claim 6, wherein: Based on the determination that the contact adjacent to the edge of the touch-sensitive surface has a first spatial property, the first region relative to the touch-sensitive surface is positioned completely away from the touch-sensitive surface; and Based on the determination that the contact adjacent to the edge of the touch-sensitive surface has a second spatial property, the first region relative to the touch-sensitive surface includes a first portion located on the touch-sensitive surface adjacent to the edge of the touch-sensitive surface and a second portion extending away from the edge of the touch-sensitive surface. 8. The electronic device according to claim 6, wherein: Based on the determination that the contact adjacent to the edge of the touch-sensitive surface has a first spatial property, the first region relative to the touch-sensitive surface is positioned completely away from the touch-sensitive surface, thereby extending from a first boundary located at a first fixed distance from the edge of the touch-sensitive surface; and Based on the determination that the contact adjacent to the edge of the touch-sensitive surface has a second spatial property, the first region relative to the touch-sensitive surface is positioned completely away from the touch-sensitive surface, thereby extending from a second boundary located at a second fixed distance from the edge of the touch-sensitive surface, wherein the second fixed distance is shorter than the first fixed distance. 9. The electronic device according to claim 1, wherein: Based on a projection of the location of the portion of the contact extending beyond the edge of the touch-sensitive surface, which is adjacent to the edge of the touch-sensitive surface, the location of the contact is the location of the portion of the contact extending beyond the edge of the touch-sensitive surface that is furthest from the edge of the touch-sensitive surface; and The location of the contact is determined to be the location of the contact closest to the edge of the touch-sensitive surface, based on the fact that the portion of the contact adjacent to the edge of the touch-sensitive surface does not extend beyond the edge of the touch-sensitive surface. 10. The electronic device of claim 1, wherein the size of the contact adjacent to the edge of the touch-sensitive surface is based on one or more of the following: a measurement of the capacitance of the contact, the shape of the contact, and the area of the contact. 11. The electronic device of claim 5, wherein the difference between the first boundary of the first region and the second boundary of the first region is greater near the central portion of the edge of the touch-sensitive surface and smaller near the distal portion of the edge of the touch-sensitive surface. 12. The electronic device of claim 1, wherein the first region relative to the touch-sensitive surface has a first size or a second size when the contact adjacent to the edge of the touch-sensitive surface moves at a speed greater than a first speed threshold, and has a third size when the contact adjacent to the edge of the touch-sensitive surface moves at a speed less than the first speed threshold. 13. The electronic device of claim 1, wherein the system gesture standard further includes a direction standard specifying a predetermined direction of movement on the touch-sensitive surface, wherein the direction standard is satisfied when the contact adjacent to the edge of the touch-sensitive surface moves in the predetermined direction on the touch-sensitive surface. 14. The electronic device of claim 13, wherein the processing unit is configured to: After initiating the operation that is independent of the application: Detecting movement of the contact adjacent to the edge of the touch-sensitive surface on the touch-sensitive surface; and The movement in response to the detection of the contact: Based on the movement determining the contact in the predetermined direction, the operation independent of the application continues; and If the movement of the contact is determined to be in a direction different from the predetermined direction, the operation independent of the application is terminated. 15. The electronic device of claim 1, wherein the system gesture criterion further includes a failure condition that prevents the system gesture criterion from being satisfied when the contact adjacent to the edge of the touch-sensitive surface moves outside a second region relative to the touch-sensitive surface prior to the satisfaction of the system gesture criterion. 16. The electronic device of claim 1, wherein the system gesture standard includes a requirement that the characteristic intensity of the contact adjacent to the edge of the touch-sensitive surface increases from an intensity below an intensity threshold to an intensity above or equal to the intensity threshold when the contact is in the first region relative to the touch-sensitive surface. 17. The electronic device of claim 1, wherein the intensity standard varies over time. 18. The electronic device of claim 1, wherein the operation independent of the application is an operation for navigating between applications of the electronic device. 19. The electronic device of claim 2, wherein the corresponding operation in the application is a key press operation. 20. The electronic device of claim 2, wherein the corresponding operation in the application is a page switching operation. 21. The electronic device of claim 2, wherein the corresponding operation in the application is used for navigation within a hierarchical structure associated with the application. 22. The electronic device of claim 2, wherein the corresponding operation in the application is a preview operation. 23. The electronic device according to claim 2, wherein the corresponding operation in the application is a menu display operation. 24. An apparatus for performing an operation in response to detecting an edge input, comprising: Components for displaying a user interface for an application on a display of an electronic device, the electronic device including a touch-sensitive surface and one or more sensors for detecting the intensity of contact with the touch-sensitive surface; A component for detecting edge input, the edge input detection including detecting changes in the characteristic intensity of contact adjacent to the edge of the touch-sensitive surface; and Components implemented in response to the detection of the edge input for the following purposes: Based on the determination that the edge input meets the system gesture standard, perform an operation independent of the application, wherein: The system's gesture standards include intensity standards; The system gesture criteria include a positional criterion that is satisfied when the contact is within a first region relative to the touch-sensitive surface and satisfies the intensity criterion for the contact; and Based on one or more characteristics of the contact, the size and position of the first region relative to the touch-sensitive surface are dynamically adjusted, wherein the one or more characteristics of the contact include the size of the contact located at or adjacent to the edge of the touch-sensitive surface. 25. The apparatus of claim 24, wherein the change in the characteristic intensity of the contact adjacent to the edge of the touch-sensitive surface is detected at a location corresponding to a corresponding operation in the application. 26. The apparatus of claim 25, comprising: In response to the detection of the edge input: A component for performing the corresponding operation in the application, rather than performing the operation independent of the application, based on the determination that the edge input meets the application gesture standard but does not meet the system gesture standard. 27. The apparatus of claim 24, wherein the strength criterion is satisfied when: The characteristic intensity of the contact adjacent to the edge of the touch-sensitive surface is above a first intensity threshold; and The intensity of the characteristic of the contact adjacent to the edge of the touch-sensitive surface is below a second intensity threshold. 28. The apparatus of claim 24, wherein the first region relative to the touch-sensitive surface has a first boundary when the contact adjacent to the edge of the touch-sensitive surface has a first spatial property, and has a second boundary different from the first boundary when the contact adjacent to the edge of the touch-sensitive surface has a second spatial property. 29. The apparatus of claim 24, wherein detecting the edge input comprises: Detecting a first portion of the contact on the touch-sensitive surface adjacent to the edge of the touch-sensitive surface; and Based on the first portion of the contact, a second portion of the contact is inferred to be adjacent to the edge of the touch-sensitive surface, the second portion extending beyond the edge of the touch-sensitive surface. The location of the contact is determined, at least in part, based on the second portion of the inferred contact, for the purpose of satisfying the location criterion. 30. The apparatus according to claim 29, wherein: Based on the determination that the contact adjacent to the edge of the touch-sensitive surface has a first spatial property, the first region relative to the touch-sensitive surface is positioned completely away from the touch-sensitive surface; and Based on the determination that the contact adjacent to the edge of the touch-sensitive surface has a second spatial property, the first region relative to the touch-sensitive surface includes a first portion located on the touch-sensitive surface adjacent to the edge of the touch-sensitive surface and a second portion extending away from the edge of the touch-sensitive surface. 31. The apparatus according to claim 29, wherein: Based on the determination that the contact adjacent to the edge of the touch-sensitive surface has a first spatial property, the first region relative to the touch-sensitive surface is positioned completely away from the touch-sensitive surface, thereby extending from a first boundary located at a first fixed distance from the edge of the touch-sensitive surface; and Based on the determination that the contact adjacent to the edge of the touch-sensitive surface has a second spatial property, the first region relative to the touch-sensitive surface is positioned completely away from the touch-sensitive surface, thereby extending from a second boundary located at a second fixed distance from the edge of the touch-sensitive surface, wherein the second fixed distance is shorter than the first fixed distance. 32. The apparatus according to claim 24, wherein: Based on a projection of the location of the portion of the contact extending beyond the edge of the touch-sensitive surface, which is adjacent to the edge of the touch-sensitive surface, the location of the contact is the location of the portion of the contact extending beyond the edge of the touch-sensitive surface that is furthest from the edge of the touch-sensitive surface; and The location of the contact is determined to be the location of the contact closest to the edge of the touch-sensitive surface, based on the fact that the portion of the contact adjacent to the edge of the touch-sensitive surface does not extend beyond the edge of the touch-sensitive surface. 33. The apparatus of claim 24, wherein the dimensions of the contact adjacent to the edge of the touch-sensitive surface are based on one or more of the following: a measurement of the capacitance of the contact, the shape of the contact, and the area of the contact. 34. The apparatus of claim 28, wherein the difference between the first boundary of the first region and the second boundary of the first region is greater near the central portion of the edge of the touch-sensitive surface and smaller near the distal portion of the edge of the touch-sensitive surface. 35. The apparatus of claim 24, wherein the first region relative to the touch-sensitive surface has a first size or a second size when the contact adjacent to the edge of the touch-sensitive surface moves at a speed greater than a first speed threshold, and has a third size when the contact adjacent to the edge of the touch-sensitive surface moves at a speed less than the first speed threshold. 36. The apparatus of claim 24, wherein the system gesture standard further includes a direction standard specifying a predetermined direction of movement on the touch-sensitive surface, wherein the direction standard is satisfied when the contact adjacent to the edge of the touch-sensitive surface moves in the predetermined direction on the touch-sensitive surface. 37. The apparatus of claim 36, comprising: After initiating the operation that is independent of the application: A component for detecting movement of the contact on the touch-sensitive surface adjacent to the edge of the touch-sensitive surface; and The movement in response to the detection of the contact: A component for continuing to perform the operation independent of the application in the predetermined direction based on the movement that determines the contact; and A component for terminating the operation independent of the application based on determining that the movement of the contact is in a direction different from the predetermined direction. 38. The apparatus of claim 24, wherein the system gesture criterion further includes a failure condition that prevents the system gesture criterion from being satisfied when the contact adjacent to the edge of the touch-sensitive surface moves outside a second region relative to the touch-sensitive surface prior to the satisfaction of the system gesture criterion. 39. The apparatus of claim 24, wherein the system gesture standard includes a requirement that the characteristic intensity of the contact adjacent to the edge of the touch-sensitive surface increases from an intensity below an intensity threshold to an intensity above or equal to the intensity threshold when the contact is in the first region relative to the touch-sensitive surface. 40. The apparatus of claim 24, wherein the intensity criterion varies over time. 41. The apparatus of claim 24, wherein the operation independent of the application is an operation for navigating between applications of the electronic device. 42. The apparatus of claim 25, wherein the corresponding operation in the application is a key pressing operation. 43. The apparatus of claim 25, wherein the corresponding operation in the application is a page switching operation. 44. The apparatus of claim 25, wherein the corresponding operation in the application is used for navigation within a hierarchical structure associated with the application. 45. The apparatus of claim 25, wherein the corresponding operation in the application is a preview operation. 46. The apparatus of claim 25, wherein the corresponding operation in the application is a menu display operation. 47. A method for performing an operation in response to detecting edge input, comprising: In an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface: A user interface for an application is displayed on a display of an electronic device, the electronic device including a touch-sensitive surface and one or more sensors for detecting the intensity of contact with the touch-sensitive surface; Detecting edge input, the edge input including detecting changes in the characteristic intensity of contact adjacent to the edge of the touch-sensitive surface; and In response to the detection of the edge input: Based on the determination that the edge input meets the system gesture standard, perform an operation independent of the application, wherein: The system's gesture standards include intensity standards; The system gesture criteria include a positional criterion that is satisfied when the contact is within a first region relative to the touch-sensitive surface and satisfies the intensity criterion for the contact; and Based on one or more characteristics of the contact, the size and position of the first region relative to the touch-sensitive surface are dynamically changed, wherein the one or more characteristics of the contact include the size of the contact located at or adjacent to the edge of the touch-sensitive surface. 48. The method of claim 47, wherein the change in the characteristic intensity of the contact adjacent to the edge of the touch-sensitive surface is detected at a location corresponding to a corresponding operation in the application. 49. The method of claim 48, comprising: In response to the detection of the edge input: If the edge input is determined to meet the application gesture standard but not the system gesture standard, the corresponding operation in the application is performed instead of the operation independent of the application. 50. The method of claim 47, wherein the strength criterion is satisfied when: The characteristic intensity of the contact adjacent to the edge of the touch-sensitive surface is above a first intensity threshold; and The intensity of the characteristic of the contact adjacent to the edge of the touch-sensitive surface is below a second intensity threshold. 51. The method of claim 47, wherein the first region relative to the touch-sensitive surface has a first boundary when the contact adjacent to the edge of the touch-sensitive surface has a first spatial property, and has a second boundary different from the first boundary when the contact adjacent to the edge of the touch-sensitive surface has a second spatial property. 52. The method of claim 47, wherein detecting the edge input comprises: Detecting a first portion of the contact on the touch-sensitive surface adjacent to the edge of the touch-sensitive surface; and Based on the first portion of the contact, a second portion of the contact is inferred to be adjacent to the edge of the touch-sensitive surface, the second portion extending beyond the edge of the touch-sensitive surface. The location of the contact is determined, at least in part, based on the second portion of the inferred contact, for the purpose of satisfying the location criterion. 53. The method according to claim 52, wherein: Based on the determination that the contact adjacent to the edge of the touch-sensitive surface has a first spatial property, the first region relative to the touch-sensitive surface is positioned completely away from the touch-sensitive surface; and Based on the determination that the contact adjacent to the edge of the touch-sensitive surface has a second spatial property, the first region relative to the touch-sensitive surface includes a first portion located on the touch-sensitive surface adjacent to the edge of the touch-sensitive surface and a second portion extending away from the edge of the touch-sensitive surface. 54. The method according to claim 52, wherein: Based on the determination that the contact adjacent to the edge of the touch-sensitive surface has a first spatial property, the first region relative to the touch-sensitive surface is positioned completely away from the touch-sensitive surface, thereby extending from a first boundary located at a first fixed distance from the edge of the touch-sensitive surface; and Based on the determination that the contact adjacent to the edge of the touch-sensitive surface has a second spatial property, the first region relative to the touch-sensitive surface is positioned completely away from the touch-sensitive surface, thereby extending from a second boundary located at a second fixed distance from the edge of the touch-sensitive surface, wherein the second fixed distance is shorter than the first fixed distance. 55. The method of claim 47, wherein: Based on a projection of the location of the portion of the contact extending beyond the edge of the touch-sensitive surface, which is adjacent to the edge of the touch-sensitive surface, the location of the contact is the location of the portion of the contact extending beyond the edge of the touch-sensitive surface that is furthest from the edge of the touch-sensitive surface; and The location of the contact is determined to be the location of the contact closest to the edge of the touch-sensitive surface, based on the fact that the portion of the contact adjacent to the edge of the touch-sensitive surface does not extend beyond the edge of the touch-sensitive surface. 56. The method of claim 47, wherein the size of the contact adjacent to the edge of the touch-sensitive surface is based on one or more of the following: a measurement of the capacitance of the contact, the shape of the contact, and the area of the contact. 57. The method of claim 51, wherein the difference between the first boundary of the first region and the second boundary of the first region is greater near the central portion of the edge of the touch-sensitive surface and smaller near the distal portion of the edge of the touch-sensitive surface. 58. The method of claim 47, wherein the first region relative to the touch-sensitive surface has a first size or a second size when the contact adjacent to the edge of the touch-sensitive surface moves at a speed greater than a first speed threshold, and has a third size when the contact adjacent to the edge of the touch-sensitive surface moves at a speed less than the first speed threshold. 59. The method of claim 49, wherein the system gesture standard further includes a direction standard specifying a predetermined direction of movement on the touch-sensitive surface, wherein the direction standard is satisfied when the contact adjacent to the edge of the touch-sensitive surface moves in the predetermined direction on the touch-sensitive surface. 60. The method of claim 59, comprising: After initiating the operation that is independent of the application: Detecting movement of the contact adjacent to the edge of the touch-sensitive surface on the touch-sensitive surface; and The movement in response to the detection of the contact: Based on the movement determining the contact in the predetermined direction, the operation independent of the application continues; and If the movement of the contact is determined to be in a direction different from the predetermined direction, the operation independent of the application is terminated. 61. The method of claim 47, wherein the system gesture criterion further includes a failure condition that prevents the system gesture criterion from being satisfied when the contact adjacent to the edge of the touch-sensitive surface moves outside a second region relative to the touch-sensitive surface prior to the satisfaction of the system gesture criterion. 62. The method of claim 47, wherein the system gesture standard includes requiring the characteristic intensity of the contact adjacent to the edge of the touch-sensitive surface to increase from an intensity below an intensity threshold to an intensity above the intensity threshold when the contact is in the first region relative to the touch-sensitive surface. 63. The method of claim 47, wherein the intensity criterion varies over time. 64. The method of claim 47, wherein the operation independent of the application is an operation for navigating between applications of the electronic device. 65. The method of claim 48, wherein the corresponding operation in the application is a key press operation. 66. The method of claim 48, wherein the corresponding operation in the application is a page switching operation. 67. The method of claim 48, wherein the corresponding operation in the application is used for navigation within a hierarchical structure associated with the application. 68. The method of claim 48, wherein the corresponding operation in the application is a preview operation. 69. The method of claim 48, wherein the corresponding operation in the application is a menu display operation.