用于在用户界面之间导航的设备和方法

Apparatus and method for navigating between user interfaces

文档序号：7059 发布日期：2021-09-17 浏览：28次中文

1. A method, comprising:

at an electronic device with one or more processors, memory, a touch-sensitive surface, a display, and one or more sensors to detect contacts with the touch-sensitive surface:

displaying a first user interface on the display;

while displaying the first user interface on the display, detecting an edge input through a first contact on the touch-sensitive surface, the edge input comprising movement of the first contact across the touch-sensitive surface;

while detecting the edge input by the first contact, displaying a first user interface representation and at least a second user interface representation on the display;

while displaying the first user interface representation and at least the second user interface representation on the display, detecting termination of the edge input by the first contact; and

in response to detecting termination of the edge input by the first contact:

if it is determined that the first contact moved more than a first threshold amount in a direction across the touch-sensitive surface that corresponds to a first predefined direction on the display during the edge input by the first contact, displaying a second user interface that corresponds to the second user interface representation; and

Redisplaying the first user interface if it is determined that the first contact has not moved more than the first threshold amount in a direction across the touch-sensitive surface that corresponds to the first predefined direction on the display during the edge input by the first contact.

2. The method of claim 1, comprising:

while detecting the edge input by the first contact:

if it is determined that the first contact is moving in a direction across the touch-sensitive surface that corresponds to the first predefined direction on the display, moving the first user interface representation and the second user interface representation in accordance with the movement of the first contact.

3. The method of claim 2, wherein the display and the touch-sensitive surface are provided by a touch screen, and the method comprises:

maintaining a fixed display of the first user interface representation relative to the first contact during the movement of the first contact.

4. The method of claim 2, comprising:

continuing movement of the first user interface representation after the termination of the edge input by the first contact.

5. The method of claim 2, wherein a vector component of the movement of the first contact that is orthogonal to a predefined movement path is reflected in the movement of the first user interface representation and the second user interface representation.

6. The method of claim 1, comprising:

while detecting the edge input by the first contact:

if it is determined that the edge input meets a predefined criterion, a user interface selection mode is entered and a plurality of user interface representations are displayed on the display in a stack, the stack comprising the first user interface representation displayed over and partially exposing the second user interface representation.

7. The method of claim 1, wherein:

the first user interface representation corresponds to a first open application, and,

the second user interface representation, when the edge input through the first contact is received, corresponds to a user interface of a second open application viewed just prior to displaying the first open application.

8. The method of claim 1, wherein the second user interface corresponding to the second user interface representation is displayed in response to the termination of the edge input by the first contact, and the method further comprises:

While displaying the second user interface on the display, detecting a second edge input through a second contact, including detecting movement of the second contact in a direction across the touch-sensitive surface that corresponds to a second predefined direction on the display that is opposite the first predefined direction and detecting lifting of the second contact; and

redisplaying the first user interface in response to detecting termination of the second edge input by the second contact after movement in the direction across the touch-sensitive surface that corresponds to the second predefined direction on the display exceeds a second threshold amount.

9. The method of claim 1, comprising:

while detecting the edge input by the first contact:

if it is determined that the first contact is moving in a direction across the touch-sensitive surface that corresponds to the first predefined direction on the display:

moving the first user interface representation partially away from the display; and

displaying a portion of the second user interface representation at a location of the display from which the first user interface representation has been displaced.

10. The method of claim 9, comprising:

maintaining a size of the first user interface representation when moving the first user interface representation partially off the display.

11. The method of claim 9, comprising:

maintaining a fixed display of the first user interface representation relative to the first contact when moving the first user interface representation partially away from the display.

12. An electronic device for navigating between user interfaces, comprising:

a display;

a touch-sensitive surface;

one or more sensors to detect contacts on the touch-sensitive surface;

one or more processors; and

memory storing one or more programs, the one or more programs including instructions for:

displaying a first user interface on the display;

while detecting the edge input by the first contact, displaying a first user interface representation and at least a second user interface representation on the display;

While displaying the first user interface representation and at least the second user interface representation on the display, detecting termination of the edge input by the first contact; and

in response to detecting termination of the edge input by the first contact:

redisplaying the first user interface if it is determined that the first contact has not moved more than the first threshold amount in a direction across the touch-sensitive surface that corresponds to the first predefined direction on the display during the edge input by the first contact.

13. The electronic device of claim 12, wherein the one or more programs include instructions for performing the method of any of claims 2-11.

14. A computer-readable storage medium storing instructions for navigating between user interfaces, wherein the instructions, when executed by one or more processors of an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect contacts on the touch-sensitive surface, cause the electronic device to perform operations comprising:

Displaying a first user interface on the display;

while detecting the edge input by the first contact, displaying a first user interface representation and at least a second user interface representation on the display;

while displaying the first user interface representation and at least the second user interface representation on the display, detecting termination of the edge input by the first contact; and

in response to detecting termination of the edge input by the first contact:

15. The computer-readable storage medium of claim 14, wherein the instructions, when executed by one or more processors, cause the electronic device to perform the method of any of claims 2-11.

Background

The use of touch sensitive surfaces as input devices for computers and other electronic computing devices has increased dramatically in recent years. Exemplary touch sensitive surfaces include touch pads 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).

An exemplary user interface hierarchy includes related user interface groups for: organizing files and applications; storing and/or displaying digital images, editable documents (e.g., word processing, spreadsheet, and presentation documents), and/or non-editable documents (e.g., protected files and/or pdf documents); recording and/or playing video and/or music; text-based communications (e.g., email, text, twitter, and social networking); voice and/or video communications (e.g., telephone calls and video conferences); and web browsing. In some cases, the user will need to perform such user interface navigation within or between: a file management program (e.g., Finder from apple Inc. of cupertino, Calif.); image management applications (e.g., Photos from apple, inc. of cupertino, california); digital content (e.g., video and music) management applications (e.g., iTunes from apple inc, cupertino, california); drawing applications; demonstration applications (e.g., Keynote from apple Inc. of Kuttino, Calif.); word processing applications (e.g., Pages from apple inc, cupertino, california); or a spreadsheet application (e.g., Numbers from apple inc. of cupertino, california).

Methods for performing these navigations between related user interfaces in a user interface hierarchy and animating transitions between these related user interfaces are cumbersome and inefficient. Furthermore, these methods require longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery operated devices.

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

Disclosure of Invention

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

The above-described deficiencies and other problems associated with user interfaces for electronic devices having touch-sensitive surfaces are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, 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 "touchscreen" or "touchscreen display"). In some embodiments, an apparatus has a Graphical User Interface (GUI), one or more processors, memory, and one or more modules, programs, or sets of instructions stored in the memory for performing a plurality of functions. In some embodiments, the user interacts with the GUI primarily through stylus and/or finger contacts and gestures on the touch-sensitive surface. In some embodiments, these functions optionally include image editing, drawing, presentation, word processing, spreadsheet making, game playing, telephone answering, video conferencing, e-mailing, instant messaging, exercise support, digital photography, digital video recording, web browsing, digital music playing, memo recording, and/or digital video playing. Executable instructions for performing these functions are optionally included in a non-transitory 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 with a display and a touch-sensitive surface. The method comprises the following steps: a plurality of user interface representations are displayed in a stack on a 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 the 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 that corresponds to a location of a first user interface representation on the display, the first contact moving across the touch-sensitive surface in a direction that corresponds to a first direction on the display. The method also includes, while the first contact is at a location on the touch-sensitive surface that corresponds to a location of the first user interface representation on the display and moving across the touch-sensitive surface in a direction that corresponds to a first direction on the display: moving the first user interface representation in a first direction on the display at a first speed in accordance with a speed of a first contact on the touch-sensitive surface; and moving a second user interface representation disposed above the first user interface representation in a first direction at a second speed greater than the first speed.

In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface. The method comprises the following steps: a first user interface is displayed on the display. The method also includes detecting an input through a first contact on the touch-sensitive surface while the first user interface is displayed on the display. The method also includes displaying, on the display, a first user interface representation and at least a second user interface representation upon detecting input through the first contact. The method also includes detecting termination of the input through the first contact while displaying the first user interface representation and at least the second user interface representation on the display. In response to detecting termination of the input through the first contact: in accordance with a determination that the first contact has a characteristic intensity below a predetermined intensity threshold during the input and that the first contact is moving in a direction across the touch-sensitive surface that corresponds to a predefined direction on the display during the input, displaying a second user interface that corresponds to the second user interface representation; and in accordance with a determination that the first contact has a characteristic intensity below the predetermined intensity threshold during the input and that the first contact has not moved in a direction across the touch-sensitive surface corresponding to the predefined direction on the display during the input, redisplaying the first user interface.

In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface. The method comprises the following steps: a first user interface is displayed on the display. The method also includes, while displaying the first user interface on the display, detecting, on the touch-sensitive surface, input of the first contact by a period of increased intensity that includes the first contact. The method also includes, in response to detecting input through the first contact over a period of increasing intensity including the first contact, displaying on the display a first user interface representation for the first user interface and a second user interface representation for the second user interface, wherein the first user interface representation is displayed over and partially exposes the second user interface representation. The method also includes detecting, while displaying the first user interface representation and the second user interface representation on the display, that an intensity of the first contact satisfies one or more predetermined intensity criteria during the period of increased intensity of the first contact. The method also includes, in response to detecting that the intensity of the first contact satisfies 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 with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface. The method comprises the following steps: a plurality of user interface representations are displayed in a stack on a display. At least the first user interface representation, the second user interface representation, and the third user interface representation are visible on the display. The first user interface representation is laterally offset from and partially exposes the second user interface representation in a first direction. The second user interface representation is laterally offset from and partially exposes the third user interface representation in the first direction. The method also includes detecting an input through a first contact on the touch-sensitive surface at a location corresponding to a second user interface representation on the display. The method also includes, in accordance with 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, increasing an area of the second user interface representation exposed behind the first user interface representation by increasing a lateral offset between the first user interface representation and the second user interface representation.

In accordance with some embodiments, a method is performed at an electronic device with a display and a touch-sensitive surface. The method comprises the following steps: a plurality of user interface representations are displayed in a stack on a display. At least the first user interface representation, the second user interface representation, and the third user interface representation are visible on the display. The second user interface representation is laterally offset from and partially exposes the first user interface representation in the first direction. The third user interface representation is laterally offset from and partially exposes the second user interface representation in the first direction. The method also includes detecting a fling gesture by a first contact moving across the touch-sensitive surface, wherein movement of the fling 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, surfacing the first user interface representation more 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 with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface. The method comprises the following steps: a first user interface of a first application is displayed 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 through a first contact on the touch-sensitive surface at a location corresponding to a back navigation control on the display. The method also includes, in response to detecting the gesture with the first contact on the touch-sensitive surface at the location corresponding to the back navigation control: in accordance with a determination that the gesture by the first contact is a gesture having an intensity of the first contact that satisfies one or more predetermined intensity criteria, replace display of the first user interface of the first application with display of a plurality of user interface representations of the first application (including a representation of the first user interface and a representation of the second user interface); and in accordance with a determination that the gesture by the first contact is a gesture having an intensity of the first contact that does not satisfy the one or more predetermined intensity criteria, replace display of the first user interface of the first application with display of the second user interface of the first application.

In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface. The method comprises the following steps: displaying a first view of a first application on a display; while displaying the first view, detecting a first portion of the first input, including detecting a first contact on the touch-sensitive surface; in response to detecting the first portion of the first input, in accordance with a determination that the first portion of the first input satisfies application-switching criteria, simultaneously displaying on the display a portion of the plurality of application views that includes the first application view and the second application view; while simultaneously displaying portions of the plurality of application views, detecting a second portion of the lifted first input that includes the first contact; and in response to detecting the second portion of the first input that includes the lift of the first contact: in accordance with a determination that the second portion of the first input satisfies first view display criteria, ceasing to display the portion of the second application view on the display and displaying 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; and in accordance with a determination that the second portion of the first input satisfies multi-view display criteria, after detecting the lift-off of the first contact, maintaining simultaneous display on the display of at least a portion of the first application view and at least a portion of the second application view, wherein the multi-view display criteria include criteria that are satisfied when the lift-off of the first contact is detected in a second region of the touch-sensitive surface that is different from the first region of the touch-sensitive surface.

According to some embodiments, an electronic device comprises: a display unit configured to display a user interface; a touch-sensitive surface unit for receiving a contact; and a processing unit coupled with the display unit and the touch-sensitive surface unit. The processing unit is configured to: the implementation displays a plurality of user interface representations in a stack on a 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 viewable on the display unit. The second user interface representation is offset from the first user interface representation in the 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 by a first contact on the touch-sensitive surface unit at a location 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 a first direction on the display unit. The processing unit is further configured to, while the first contact is at a location on the touch-sensitive surface unit that corresponds to a location of the first user interface representation on the display unit and moving across the touch-sensitive surface unit in a direction that corresponds to a first direction on the display unit: moving the first user interface representation in a first direction on the display unit at a first speed in accordance with a speed of a first contact on the touch-sensitive surface unit; and moving a second user interface representation disposed above the first user interface representation in a first direction at a second speed greater than the first speed.

According to some embodiments, an electronic device comprises: a display unit configured to display a user interface; a touch-sensitive surface unit for receiving a contact; one or more sensor units for detecting intensity of contacts with the touch-sensitive surface unit; and a processing unit coupled with the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: enabling display of a first user interface on a display unit. The processing unit is further configured to detect an input through a first contact on the touch-sensitive surface unit while displaying the first user interface on the display unit. The processing unit is further configured to, upon detecting input through the first contact, enable display of the first user interface representation and at least the second user interface representation on the display unit. The processing unit is further configured to detect termination of the input by 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 further configured to, in response to detecting termination of the input through the first contact: in accordance with a determination that the first contact has a characteristic intensity below a predetermined intensity threshold during the input and that the first contact is moving in a direction across the touch-sensitive surface that corresponds to a predefined direction on the display during the input, enabling display of a second user interface that corresponds to a second user interface representation; and in accordance with a determination that the first contact has a characteristic intensity below the predetermined intensity threshold during the input and that the first contact has not moved in a direction across the touch-sensitive surface that corresponds to the predefined direction on the display during the input, effect re-displaying the first user interface.

According to some embodiments, an electronic device comprises: a display unit configured to display a user interface; a touch-sensitive surface unit for receiving a contact; one or more sensor units for detecting intensity of contacts with the touch-sensitive surface unit; and a processing unit coupled with the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: enabling display of a first user interface on a display unit. The processing unit is further configured to detect, while displaying the first user interface on the display unit, an input of the first contact through a period of increased intensity that includes the first contact on the touch-sensitive surface unit. The processing unit is further configured to, in response to detecting the input of the first contact over a period of increased intensity comprising the first contact: display, on the display unit, a first user interface representation for a first user interface and a second user interface representation for a second user interface is enabled, wherein the first user interface representation is displayed over and partially exposes the second user interface representation. The processing unit is further configured to detect, while displaying the first user interface representation and the second user interface representation on the display unit, that the intensity of the first contact satisfies one or more predetermined intensity criteria during the period of increased intensity of the first contact. 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: ceasing to enable display of the first user interface representation and the second user interface representation on the display unit and enabling display of the second user interface on the display.

According to some embodiments, an electronic device comprises: a display unit configured to display a user interface; a touch-sensitive surface unit for receiving a contact; one or more sensor units for detecting intensity of contacts with the touch-sensitive surface unit; and a processing unit coupled with the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: the implementation displays a plurality of user interface representations in a stack on a display unit. At least the first user interface representation, the second user interface representation and the third user interface representation are visible on the display unit. The first user interface representation is laterally offset from and partially exposes the second user interface representation in a first direction. The second user interface representation is laterally offset from and partially exposes the third user interface representation in the first direction. The processing unit is further configured to detect an input through the first contact at a location on the touch-sensitive surface unit that corresponds to the second user interface representation on the display unit. The processing unit is further configured to increase 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 in accordance with detecting an increase in intensity of the first contact on the touch-sensitive surface unit at a location corresponding to the second user interface representation on the display unit.

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

According to some embodiments, an electronic device comprises: a display unit configured to display a user interface; a touch-sensitive surface unit for receiving a contact; one or more sensor units for detecting intensity of contacts with the touch-sensitive surface unit; and a processing unit coupled with the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: a first user interface of a first application is enabled to be displayed on a display unit, the first user interface including a back navigation control. The processing unit is further configured to detect a gesture through a first contact on the touch-sensitive surface unit at a location corresponding to a back navigation control on the display unit while displaying the first user interface of the first application on the display unit. The processing unit is further configured to, in response to detecting the gesture with the first contact on the touch-sensitive surface unit at the location corresponding to the backward navigation control: in accordance with a determination that the gesture by the first contact is a gesture having an intensity of the first contact that satisfies one or more predetermined intensity criteria, replace display of the first user interface of the first application with display of a plurality of user interface representations of the first application (including a representation of the first user interface and a representation of the second user interface); and in accordance with a determination that the gesture by the first contact is a gesture having an intensity of the first contact that does not satisfy the one or more predetermined intensity criteria, replace display of the first user interface of the first application with display of the second user interface of the first application.

In accordance with some embodiments, an electronic device includes a display, a touch-sensitive surface, optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, one or more processors, 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 performance of, the operations 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 with a display, a touch-sensitive surface, and optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, cause the device to perform or cause performance of the operations of any of the methods described herein. In accordance with some embodiments, a graphical user interface on an electronic device with a display, a touch-sensitive surface, optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, a memory, and one or more processors to execute one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described herein that are updated in response to an input, as described in any of the methods described herein. According to some embodiments, an electronic device comprises: a display, a touch-sensitive surface, and optionally one or more sensors for detecting intensity of contacts with the touch-sensitive surface; and means for performing or causing to be performed the operations of any one of the methods described above. In accordance with some embodiments, an information processing apparatus for use in an electronic device with a display and a touch-sensitive surface and, optionally, one or more sensors to detect intensity of contacts with the touch-sensitive surface, includes means for performing, or causing performance of, operations of any of the above-described methods.

According to some embodiments, an electronic device comprises: 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 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: enabling display of a first view of a first application on a display; while enabling display of the first view, detecting a first portion of the first input, including detecting a first contact on the touch-sensitive surface; in response to detecting the first portion of the first input, in accordance with a determination that the first portion of the first input satisfies application-switching criteria, enabling simultaneous display of a portion of a plurality of application views, including a first application view and a second application view, on the display; while enabling simultaneous display of portions of the plurality of application views, detecting a second portion of the lifted first input that includes the first contact; and in response to detecting the second portion of the first input that includes the lift of the first contact: in accordance with a determination that the second portion of the first input satisfies first view display criteria, ceasing to enable display of the portion of the second application view on the display and enabling display of 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; and in accordance with a determination that the second portion of the first input satisfies multi-view display criteria, after detecting the lift-off of the first contact, maintaining simultaneous display on the display of at least a portion of the first application view and at least a portion of the second application view, wherein the multi-view display criteria include criteria that are satisfied when the lift-off of the first contact is detected in a second region of the touch-sensitive surface that is different from the first region of the touch-sensitive surface.

Accordingly, electronic devices having a display, a touch-sensitive surface, and optionally one or more sensors for detecting intensity of contacts with the touch-sensitive surface are provided with faster and more efficient methods and interfaces for navigating between user interfaces, thereby increasing effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may supplement or replace conventional methods for navigating between user interfaces.

Drawings

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

FIG. 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.

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

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

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

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

Fig. 4C-4E illustrate exemplary dynamic intensity thresholds according to some embodiments.

5A-5HH illustrate an exemplary user interface for navigating between user interface representations in a user interface selection mode according to some embodiments.

6A-6V illustrate an exemplary user interface for navigating between a displayed user interface and a previously displayed user interface, according to some embodiments.

7A-7O illustrate an exemplary user interface 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 according to some embodiments.

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

10A-10H are flow diagrams illustrating methods of navigating between user interface representations in a user interface selection mode according to some embodiments.

11A-11E are flow diagrams illustrating methods of navigating between a displayed user interface and a previously displayed user interface, according to 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 according to some embodiments.

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

FIG. 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.

22A-22BA illustrate an exemplary user interface 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, according to 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, according to some embodiments.

25A-25H are flow diagrams illustrating methods of invoking a user interface selection mode and for navigating between user interfaces in an application, according to 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 a number of different applications. Users commonly need to access a number of different applications in succession. Maintaining applications in an active state (e.g., open) while working in this manner is more efficient because opening and closing the same application multiple times a day is time consuming and laborious. However, when multiple applications are open 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. Likewise, navigating through a hierarchy having a large number of items (e.g., files, emails, previously displayed web pages, etc.) is cumbersome. The present disclosure improves this process by providing an efficient and intuitive device, method, and user interface for navigating through active applications and representations of complex hierarchies. In some embodiments, improvements are achieved by providing methods for navigating through a large number of items with fewer and smaller user inputs. In some embodiments, improvements are achieved by incorporating heuristics based on sensing differences in intensity of contacts, which do not require the user to make multiple user inputs or even lift a contact off the touch-sensitive surface to make a selection.

1A-1B, 2 and 3 provide a description of exemplary devices. 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. 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, 15, 24A-24F, and 25A-25H are flow diagrams of methods of navigating between user interface representations. The user interfaces in FIGS. 5A-5HH, 6A-6V, 7A-7O, 8A-8R, 9A-9H, 22A-22BA, and 23A-23T are used to illustrate the processes in FIGS. 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, 15, 24A-24F, and 25A-25H.

Exemplary device

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

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

The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further 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 components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Depending on the context, the term "if" as used herein is optionally to be interpreted to mean "when … …" or "at … …" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if determined … …" or "if [ stated condition or event ] is detected" is optionally to be construed to mean "upon determination … …" or "in response to determination … …" or "upon detection of [ stated condition or event ] or" in response to detection of [ 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 that also contains other functions, such as PDA and/or music player functions, such as mobile electronicIf so. Exemplary embodiments of portable multifunction devices include, but are not limited to, those from apple Inc. of cupertino, californiaiPodAndan apparatus. Other portable electronic devices, such as laptop computers or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).

In the following discussion, an electronic device including a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device may alternatively 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 recording application, a drawing application, a presentation application, a word processing application, a website creation application, a disc authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, an exercise 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 are optionally adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture of the device (such as a 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 having touch sensitive displays. FIG. 1A 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 is sometimes referred to 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 peripheral interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, an input/output (I/O) subsystem 106, other input or control devices 116, and an external port 124. The 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 outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

As used in this specification and claims, the term "haptic output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to a center of gravity of the device that is to be detected by a user through a sense of touch of the user. For example, where a device or component of a device is in contact with a surface of the user that is sensitive to touch (e.g., a finger, palm, or other portion 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 the perceived change in the physical characteristic of the device or device component. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or a trackpad) is optionally interpreted by a user as a "press click" or a "lift click" of a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or a "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 is not moving. As another example, movement of the touch-sensitive surface is optionally interpreted or sensed by the user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. While such interpretation of touches by a user will be limited by the user's individualized sensory perception, sensory perception of many touches is common to most users. Thus, when a haptic 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 haptic output corresponds to a physical displacement of the device or a component thereof that would generate the described sensory perception of a typical (or ordinary) user.

It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of these components. The various components shown in fig. 1A are implemented in hardware, software, firmware, or a combination thereof, including one or more signal processing and/or application specific integrated circuits.

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

Peripheral interface 118 may be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions 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 called electromagnetic signals. The radio frequency circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a Subscriber Identity Module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the internet (also known as the World Wide Web (WWW)), intranets, and/or wireless networks, such as cellular telephone networks, wireless Local Area Networks (LANs), and/or Metropolitan Area Networks (MANs), as well as other devices via wireless communications. The wireless communication optionally uses any of a number of communication standards, protocols, and techniques, 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 +, 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.11n), Voice over Internet protocol (VoIP), Wi-MAX, electronic mail 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 with extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed at the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. The audio circuitry 110 receives audio data from the peripheral interface 118, converts the audio data to electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electrical signal 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 to audio data and transmits the audio data to the peripheral interface 118 for processing. Audio data is optionally retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripheral interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212 in fig. 2). The headset jack provides an interface between the audio circuitry 110 and a removable audio input/output peripheral, such as an output-only headset or a headset having both an output (e.g., a monaural or binaural headset) and an input (e.g., a microphone).

The I/O subsystem 106 couples input/output peripheral devices on the device 100, such as the touch-sensitive display system 112 and other input or control devices 116, to a peripheral interface 118. The I/O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/transmit 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, one or more input controllers 160 are optionally coupled with any one (or none) of the following: a keyboard, infrared port, USB port, stylus, and/or pointer device such as a mouse. The one or more buttons (e.g., 208 in fig. 2) 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 fig. 2).

Touch-sensitive display system 112 provides an input interface and an output interface between the device and the user. Display controller 156 receives electrical signals from touch-sensitive display system 112 and/or transmits electrical signals to touch-sensitive display system 112. Touch display system 112 displays visual output to a user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output corresponds to a user interface object. As used herein, the term "affordance" refers to a user-interactive graphical user interface object (e.g., a graphical user interface object configured to respond to input directed to the 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.

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

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. Touch-sensitive display system 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a variety of touch sensing technologies now known or later developed, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch-sensitive display system 112Sensing technologies include, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as from apple Inc. of Kuttino, CalifiPodAndthe technique found.

Touch sensitive display system 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touchscreen video resolution exceeds 400dpi (e.g., 500dpi, 800dpi, or greater). The user optionally makes contact with touch-sensitive display system 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which may not be as accurate as stylus-based input due to the large contact area of the finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command to perform the action desired by the user.

In some embodiments, in addition to a touch screen, device 100 optionally includes a touch pad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike a 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.

The device 100 also includes a power system 162 for powering the various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., battery, Alternating Current (AC)), a recharging system, a power failure detection circuit, 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 further comprises one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to an optical sensor controller 158 in the I/O subsystem 106. The optical sensor 164 may optionally include a Charge Coupled Device (CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The optical sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 optionally captures still images and/or video. In some embodiments, an optical sensor is located on the back of device 100, opposite touch-sensitive display system 112 on the front of the device, enabling the touch screen to act as a viewfinder for still and/or video image capture. In some embodiments, another optical sensor is located on the front of the device so that an image of the user is obtained (e.g., for self-timer shooting, for video conferencing while the user is viewing other video conference participants on a touch screen, etc.).

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

The device 100 optionally further comprises one or more proximity sensors 166. Fig. 1A shows a proximity sensor 166 coupled to the peripheral interface 118. Alternatively, the proximity sensor 166 is coupled with the input controller 160 in the I/O subsystem 106. In some embodiments, the proximity sensor turns off and disables touch-sensitive display system 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally further comprises one or more tactile output generators 167. FIG. 1A shows a haptic output generator coupled to a haptic feedback controller 161 in the I/O subsystem 106. Tactile output generator 167 optionally includes: one or more electro-acoustic devices, such as speakers or other audio components; and/or an electromechanical device that converts energy into linear motion, such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts an electrical signal into a tactile output on the device). Haptic output generator 167 receives haptic feedback generation instructions from haptic feedback module 133 and generates haptic output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is collocated with or proximate 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., into/out of the surface of device 100) or laterally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch-sensitive display system 112, which is located on the front of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled with peripheral interface 118. Alternatively, accelerometer 168 is optionally coupled with input controller 160 in I/O subsystem 106. In some embodiments, the information is displayed in a portrait view or a landscape view on the touch screen display based on an analysis of the data received from the one or more accelerometers. The device 100 may optionally include 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 set of instructions) 128, a contact/motion module (or set of instructions) 130, a graphics module (or set of instructions) 132, a tactile feedback module (or set of instructions) 133, a text input module (or set of instructions) 134, a Global Positioning System (GPS) module (or set of instructions) 135, and an application (or set of instructions) 136. Further, in some embodiments, memory 102 stores device/global internal state 157, as shown in fig. 1A and 3. Device/global internal states 157 include 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 touch-sensitive display system 112; sensor status, including information obtained from various sensors of the device and other input or control devices 116; and position and/or location information regarding the position and/or pose of the device.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or embedded operating systems 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.

Communications module 128 facilitates communications with other devices through one or more external ports 124 and also includes various software components for processing data received by RF circuitry 108 and/or external ports 124. External port 124 (e.g., Universal Serial Bus (USB), firewire, etc.) is adapted to couple directly to other devices or indirectly through a network (e.g., the internet, wireless LAN, etc.). In some embodiments, the external ports are some of those found with apple Inc. of cupertino, californiaiPod Anda multi-pin (e.g., 30-pin) connector that is the same as or similar to and/or compatible with the 30-pin connector used on the device. In some embodiments, the external ports are some of those found with apple Inc. of cupertino, california iPodAnda Lightning connector identical or similar and/or compatible with the Lightning connector used on the device.

Contact/motion module 130 optionally detects contact with touch-sensitive display system 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or a physical click wheel). 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 contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining whether contact has ceased (e.g., detecting a finger-up event or a break in contact). The contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact represented by a series of contact data, optionally includes determining velocity (magnitude), velocity (magnitude and direction), and/or acceleration (change in magnitude and/or direction) of the point of contact. These operations may optionally be applied to a single contact (e.g., one finger contact or stylus contact) or to multiple simultaneous contacts (e.g., "multi-touch"/multiple finger contacts). In some embodiments, the contact/motion module 130 and the display controller 156 detect contact on the touch panel.

The contact/motion module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, the gesture is optionally detected by detecting a specific contact pattern. For example, detecting a single-finger tap gesture includes detecting a finger-down event, and then detecting a finger-up (lift-off) event at the same location (or substantially the same location) as the finger-down event (e.g., at an icon location). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event, then detecting one or more finger-dragging events, and then subsequently detecting a finger-up (lift-off) event. Similarly, taps, swipes, drags, and other gestures are optionally detected for a stylus by detecting a particular contact pattern for that stylus.

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

In some embodiments, 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 of a specified graphic to be displayed from an application or the like, and also receives coordinate data and other graphic attribute data together if necessary, and then generates screen image data to output to the display controller 156.

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

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

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

The applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:

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

a phone module 138;

a video conferencing module 139;

an email client module 140;

an Instant Messaging (IM) module 141;

exercise support module 142;

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

an image management module 144;

a browser module 147;

a calendar module 148;

desktop applet modules 149, optionally including one or more of the following: a weather desktop applet 149-1, a stock desktop applet 149-2, a calculator desktop applet 149-3, an alarm desktop applet 149-4, a dictionary desktop applet 149-5, and other desktop applets acquired by the user and a user created desktop applet 149-6;

a desktop applet creator module 150 for forming a user-created desktop applet 149-6;

a search module 151;

a video and music player module 152, optionally consisting of a video player module and a music player module;

a memo module 153;

a 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 touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 includes executable instructions for managing an address book or contact list (e.g., stored in memory 102 or in memory 370 in application internal state 192 of contacts module 137), including: adding one or more names to an address book; deleting one or more names from the address book; associating one or more telephone numbers, email addresses, physical addresses, or other information with a name; associating the image with a name; sorting and ordering names; providing a telephone number and/or email address to initiate and/or facilitate communication by telephone 138, 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, telephone module 138 includes executable instructions for entering a sequence of characters corresponding to a telephone number, accessing one or more telephone numbers in address book 137, modifying an already entered telephone number, dialing a corresponding telephone number, conducting a conversation, and disconnecting or hanging up when the conversation is complete. As noted above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

In conjunction 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 telephony module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants according to 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 to create, send, receive, and manage emails in response to user instructions. In conjunction with the image management module 144, the email client module 140 makes it very easy to create and send an email with a still image or a video image captured by the camera module 143.

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, instant messaging module 141 includes executable instructions for entering a sequence of characters corresponding to an instant message, modifying previously entered characters, transmitting a corresponding instant message (e.g., using a Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocol for a phone-based instant message or using XMPP, SIMPLE, apple information Push Service (APNs), or IMPS for an internet-based instant message), receiving an instant message, and viewing the received instant message. In some embodiments, the transmitted and/or received instant messages optionally include graphics, photos, audio files, video files, and/or MMS and/or other attachments supported in an Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both telephony-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 conjunction 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); communicating with exercise sensors (in sports devices and smart watches); receiving exercise sensor data; calibrating a sensor for monitoring exercise; selecting and playing music for exercise; and displaying, storing and transmitting the exercise 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 the still images or videos, and/or deleting the 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 slide or album), and storing still images and/or video images.

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

In conjunction with the radio frequency circuitry 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 a calendar and data associated with the calendar (e.g., calendar entries, to-do, etc.) according to user instructions.

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

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

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

In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speakers 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and playback 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, the device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple inc.).

In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, memo module 153 includes executable instructions to create and manage memos, backlogs, and the like according to user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions for receiving, displaying, modifying, and storing a map and data associated with the map (e.g., driving directions; data for stores or other points of interest at or near a particular location; and other location-based data) according to 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), playback (e.g., on touch screen 112 or an external display connected wirelessly or via external port 124), send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as h.264. In some embodiments, instant messaging module 141, rather than email client module 140, is used to send a link to a particular online video.

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

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

The predefined set of functions performed exclusively by the touch screen and/or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 to a main, home, or root menu. In such embodiments, a 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.

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

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

In some embodiments, the application internal state 192 includes additional information, such as one or more of the following: 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 a user to return to a previous state or view of the application 136-1, and a repeat/undo queue of previous actions taken by the user.

Event monitor 171 receives event information from peripheral interface 118. The event information includes information about the sub-event (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 (through audio circuitry 110). Information received by peripheral interface 118 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 peripheral interface 118 at predetermined intervals. In response, peripheral interface 118 transmits the event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving input above a predetermined noise threshold and/or receiving input for more than a predetermined duration).

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

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

Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the respective application) in which the touch is detected optionally corresponds to a programmatic level within a programmatic or view hierarchy of applications. For example, the lowest level view in which a touch is detected is optionally called a hit view, and the set of events identified as correct inputs is optionally determined based at least in part on the hit view of the initial touch, which begins with a touch-based gesture.

Hit view determination module 172 receives information related to sub-events of the contact-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should handle the sub-event. In most cases, the hit view is the lowest level view in which a hair driver 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.

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

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

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

In some embodiments, the application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the user interface of the application. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, the corresponding application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module, such as a user interface toolkit (not shown) or a higher level object from which the application 136-1 inherits methods and other characteristics. In some embodiments, the respective event handler 190 includes one or more of: data updater 176, object updater 177, 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 of the application views 191 include one or more respective event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.

The corresponding event recognizer 180 receives event information (e.g., event data 179) from the event classifier 170 and recognizes events from the event information. The event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event recognizer 180 further includes at least a subset of: metadata 183 and event delivery instructions 188 (which optionally include sub-event delivery instructions).

The event receiver 182 receives event information from the event sorter 170. The event information includes information about the sub-event, for example, a touch or touch movement. According to the sub-event, the event information further includes additional information, such as the location of the sub-event. When the sub-event relates to motion of a touch, the event information optionally also includes the velocity and direction of the sub-event. In some embodiments, the event comprises rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information comprises corresponding information about the current orientation of the device (also referred to as the device pose).

Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event or determines or updates the state of the event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definition 186 contains definitions of events (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, the definition of event 1(187-1) is a double click on the displayed object. For example, the double tap includes a first touch (touch start) on the displayed object for a predetermined length of time, a first lift-off (touch end) for a predetermined length of time, a second touch (touch start) on the displayed object for a predetermined length of time, and a second lift-off (touch end) for a predetermined length of time. In another example, the definition of event 2(187-2) is a drag on the displayed object. For example, the drag includes a predetermined length of time of a touch (or contact) on the displayed object, movement of the touch on touch-sensitive display system 112, and lifting of the touch (touch end). In some embodiments, the events also include information for one or more associated event handlers 190.

In some embodiments, event definition 187 includes definitions of events for respective 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 respective event handler 190, the event comparator uses the results of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects the event handler associated with the sub-event and the object that triggered the hit test.

In some embodiments, the definition of the respective event 187 further comprises 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 recognizer.

After it disregards subsequent sub-events of the touch-based gesture, when the respective event recognizer 180 determines that the sub-event string does not match any event in the event definition 186, the respective event recognizer 180 enters an event not possible, event failed, or event ended state. In this case, the 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, the respective event recognizer 180 includes metadata 183 with configurable attributes, tags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable attributes, flags, and/or lists that indicate how or how event recognizers interact with each other. In some embodiments, metadata 183 includes configurable attributes, tags, and/or lists that indicate whether a sub-event is delivered to varying levels in the view or programmatic hierarchy.

In some embodiments, when one or more particular sub-events of an event are identified, the respective event identifier 180 activates the event handler 190 associated with the event. In some embodiments, the respective event identifier 180 delivers event information associated with the event to the event handler 190. Activating event handler 190 is different from sending (and deferring) sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a flag associated with the recognized event, and the 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 sub-events without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the sub-event string or to actively participating views. Event handlers associated with the sub-event strings or with actively participating views receive the event information and perform predetermined processing.

In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates a phone number used in contacts module 137 or stores a video file 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 location 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 the 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 a respective 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 processing with respect to user touches on a touch sensitive display also applies to other forms of user input utilizing an input device to operate multifunction device 100, not all of which are initiated on a touch screen. For example, mouse movement and mouse button presses are optionally utilized, optionally in combination with single or multiple keyboard presses or holds; contact movements on the touchpad, such as tapping, dragging, scrolling, etc.; inputting by a stylus; movement of the device; verbal instructions; detected eye movement; a biometric input; and/or any combination thereof, as inputs corresponding to the sub-events, defining the event to be identified.

FIG. 2 illustrates a portable multifunction device 100 with a touch screen (e.g., touch-sensitive display system 112 in FIG. 1A), in accordance with some embodiments. The touch screen optionally displays one or more graphics within the 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, for example, gesturing graphically with one or more fingers 202 (not drawn to scale in the figure) or with one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when a user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, up, and/or down), and/or a rolling of a finger (right to left, left to right, up, and/or down) that has made contact with device 100. In some implementations, or in some cases, inadvertent contact with a graphic does not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that swipes over the application icon optionally does not select the corresponding application.

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

In some embodiments, device 100 includes a touch screen display, menu buttons 204, push buttons 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. The push button 206 is optionally used to power up/down the device by pressing the button and holding the button in a pressed state for a predefined time interval; locking the device by pressing a button and releasing the button before a predefined time interval has elapsed; and/or unlock the device or initiate an unlock process. In some embodiments, device 100 also accepts verbal input through microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contacts on touch-sensitive display system 112, and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. The device 300 need not be portable. In some embodiments, the device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a child learning toy), gaming system, or control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communication between system components. Device 300 includes an input/output (I/O) interface 330 that 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 touchpad 355, a tactile output generator 357 (e.g., similar to tactile output generator 167 described above with reference to fig. 1A) for generating tactile outputs on device 300, a sensor 359 (e.g., an optical sensor, an acceleration sensor, a proximity sensor, a touch-sensitive sensor, and/or a contact intensity sensor similar to contact intensity sensor 165 described above with reference to fig. 1A). Memory 370 comprises high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, and optionally 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, or a subset of, the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Further, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disc authoring module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

Each of the above identified elements of fig. 3 may optionally be stored in one or more of the previously mentioned memory devices. Each of the identified modules corresponds to a set of instructions for performing the functions described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures described above. In addition, memory 370 may optionally store additional modules and data structures not described above.

Attention is now directed to embodiments of a user interface ("UI") that may optionally be implemented on portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for an application menu on portable multifunction device 100, in accordance with some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or a subset or superset thereof:

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

A bluetooth indicator 405;

a battery status indicator 406;

tray 408 with common application icons such as:

an icon 416 of the telephony module 138 labeled "telephony", the icon 416 optionally including an indicator 414 of the number of missed calls or voice messages;

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

icon 420 of the browser module 147, labeled "browser"; and

an icon 422 labeled "iPod" of the video and music player module 152 (also called iPod (trademark of Apple inc.) module 152); and

icons for other applications, such as:

icon 424 of IM module 141 marking "message";

icon 426 of calendar module 148 labeled "calendar";

icon 428 of image management module 144 labeled "photo";

icon 430 of camera module 143 labeled "camera";

icon 432 of online video module 155 labeled "online video";

an icon 434 of "stock" of the stock desktop applet 149-2;

icon 436 of the map module 154 labeled "map";

icon 438 labeled "weather" for weather desktop applet 149-1;

Icon 440 of alarm clock desktop applet 149-4 labeled "clock";

icon 442 of exercise support module 142 labeled "exercise support";

icon 444 of memo module 153 which marks "memo"; and

an icon 446 of an application or module is set, which icon 446 provides access to the settings of the device 100 and its various applications 136.

It should be noted that the icon labels shown in fig. 4A are merely exemplary. For example, in some embodiments, the icon 422 of the video and music player module 152 is labeled "music" or "music player". Other labels are optionally used for various application icons. In some embodiments, the label of the respective application icon includes a name of the application corresponding to the respective 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.

Fig. 4B illustrates 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) separate from the display 450. Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 357) for detecting the intensity of contacts on touch-sensitive surface 451, and/or one or more tactile output generators 359 for generating tactile outputs for a user of device 300.

Fig. 4B illustrates 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) separate from the display 450. Although many of the examples below will be given with reference to input on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, as shown in fig. 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 fig. 4B) has a primary axis (e.g., 452 in fig. 4B) that corresponds to a primary axis (e.g., 453 in fig. 4B) on the display (e.g., 450). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in fig. 4B) with the touch-sensitive surface 451 at locations corresponding to respective locations on the display (e.g., in fig. 4B, 460 corresponds to 468 and 462 corresponds to 470). As such, 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 inputs (e.g., contacts 460 and 462, and their movements) detected by the device on the touch-sensitive surface are used by the device to manipulate the user interface on the display. It should be understood that similar methods may alternatively be used for the other user interfaces described herein.

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

As used herein, the term "focus selector" refers to an input element that indicates the current portion of the user interface with which the user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in fig. 3 or touch-sensitive surface 451 in fig. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in fig. 1A or touch screen in fig. 4A) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen serves as a "focus selector" such that when an input (e.g., a press input by the contact) is detected at a 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 in accordance with the detected input. In some implementations, the focus is moved from one area of the user interface to another area of the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by moving the focus from one button to another using tab or arrow keys); in these implementations, the focus selector moves according to focus movement between different regions of the user interface. Regardless of the particular form taken by the focus selector, the focus selector is typically a user interface element (or contact on a touch screen display) that is controlled by the user to convey the user's intended interaction with the user interface (e.g., by indicating to the device the elements of the user interface with which the user desires to interact). For example, upon detection of a press input on a touch-sensitive surface (e.g., a touchpad or a touchscreen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a respective button will indicate: the user expects to activate the corresponding button (rather than other user interface elements shown on the display of the device).

As used in this specification and 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 substitute (surrogate) for the force or pressure of a contact on the touch-sensitive surface. The intensity of the 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 the 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 force at various points on the touch-sensitive surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., a weighted average or sum) to determine an estimated force of the contact. Similarly, the pressure sensitive tip of the 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 changes thereto, the capacitance of the touch-sensitive surface adjacent to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface adjacent to the contact and/or changes thereto, are optionally used as a substitute 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 a user to access additional device functionality that may not be readily accessible by the user on a reduced-size device having 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, a touch-sensitive surface, or a physical/mechanical control such as a knob or button).

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

As used in the specification and claims, the term "characterizing intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, characterizing the intensity is based on a plurality of intensity samples. The characterizing intensity is optionally a predetermined number of intensities relative to a predetermined event (e.g., after contact is detected, before contact lift is detected, before or after contact start movement is detected, before or after contact end is detected, before or after an increase in contact intensity is detected, and/or before or after a decrease in contact intensity is detected), or a collection of intensity samples collected during a predetermined period of time (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds). The characterization intensity of the contact is optionally based on one or more of a maximum value of the contact intensity, a median of the contact intensity, an average value of the contact intensity, a value of up to 10% of the contact intensity, a value at half maximum of the contact intensity, a value at 90% maximum of the contact intensity, and the like. In some embodiments, the duration of the contact is used to determine the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characterized intensity is compared to a set of one or more intensity thresholds to determine whether an operation 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 having a characteristic intensity that does not exceed a first threshold results in a first operation, a contact having a characteristic intensity that exceeds the first intensity threshold and does not exceed a second intensity threshold results in a second operation, and a contact having a characteristic intensity that exceeds the second intensity threshold results in a third operation. In some embodiments, the comparison between the characterized intensities and the one or more intensity thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the respective option or forgo performing the respective operation), rather than to determine whether to perform the first operation or the second operation.

In some embodiments, a portion of the gesture is recognized for the purpose of determining the representative intensity. For example, the touch-sensitive surface may receive a continuous swipe (e.g., a drag gesture) transitioning from a starting location and reaching an ending location at which the contact intensity increases. In this example, the characterized intensity of the contact at the end position may be based on only a portion of the continuous sweeping contact, rather than the entire sweeping contact (e.g., only a portion of the sweeping contact at the end position). In some embodiments, a smoothing algorithm may be applied to the intensity of the swipe contact before determining the representative intensity of the contact. For example, the smoothing algorithm optionally includes one or more of an unweighted moving 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 sweep contact intensity for the purpose of determining the characterized intensity.

The user interface diagrams described herein (e.g., FIGS. 5A-5HH, 6A-6V, 7A-7O, 8A-8R, 9A-9H, 22A-22BA) optionally include various intensity maps illustrating intensity of the touch input relative to one or more intensity thresholds (e.g., touch detection intensity threshold IT) ₀Prompt (hit) intensity threshold IT_HLight press pressure intensity threshold IT_LDeep compression strength threshold IT_D(e.g., at least initially higher than I_L) And/or one or more other intensity thresholds (e.g., below I)_LIntensity threshold value of_H) Current contact intensity on the touch-sensitive surface. This intensity map is typically not part of the displayed user interface, but is provided to aid in the explanation of the drawings. In some embodiments, the light press intensity threshold corresponds to the intensity at which the device will perform operations typically associated with a tap of a button or trackpad of a physical mouse. 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 physical mouse button or touchpad stroke. In some embodiments, when a light pressure is detected with a light pressure below a threshold (e.g., and at a nominal contact detection intensity threshold IT)₀Above, below which no contact will be detected anymore), the device will move in accordance with the contact on the touch-sensitive surfaceThe focus selector is moved without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Typically, these intensity thresholds are consistent between different sets of user interface diagrams unless otherwise stated.

In some embodiments, the response of the device to an input detected by the device depends on criteria based on the intensity of the contact during the input. For example, for certain "light press" inputs, a contact intensity that exceeds a first intensity threshold during the input triggers a first response. In some embodiments, the response of the device to an input detected by the device depends on criteria including both the intensity of contact during the input and time-based criteria. For example, for certain "deep press" inputs, a contact intensity that exceeds a second intensity threshold (greater than the first intensity threshold for light presses) 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. During which this delay time is typically less than 200ms (e.g., 40, 100, or 120ms, depending on the magnitude of the second intensity threshold). This delay time helps to avoid accidental deep press inputs. As another example, for certain "deep press" inputs, a period of reduced sensitivity occurs after a time that satisfies the first intensity threshold. During the period of reduced sensitivity, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep press inputs. For other deep press inputs, the response to detecting a 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 execution, rate at which intensity is applied, number of concurrent inputs, user history, environmental factors (e.g., environmental noise), focus selector positioning, and so forth. 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, FIG. 4C illustrates a dynamic intensity threshold 480 that varies over time based in part on the intensity of the touch input 476 over time. The dynamic intensity threshold 480 is the sum of two components, a first component 474 decays over time after a predefined delay time p1 from the touch input 476 being initially detected, and a second component 478 trails the intensity of the touch input 476 over time. The initial high intensity threshold of first component 474 reduces the accidental triggering of a "deep press" response while still allowing for an immediate "deep press" response when touch input 476 provides significant intensity. The second component 478 reduces unintended triggering of a "deep press" response by gradual intensity fluctuations of the touch input. In some embodiments, a "deep press" response is triggered when the touch input 476 meets a dynamic intensity threshold 480 (e.g., at point 480 of fig. 4C).

FIG. 4D illustrates another dynamic intensity threshold 486 (e.g., intensity threshold I)_D). Fig. 4D also shows two other intensity thresholds: first intensity threshold I_HAnd a second intensity threshold I_L. In FIG. 4D, although the touch input 484 meets the first intensity threshold I before time p2_HAnd a second intensity threshold I_LBut does not provide a response until a delay time p2 has elapsed at time 482. Also in FIG. 4D, the dynamic intensity threshold 486 decays over time, where the decay has already been from time 482 (when compared to the second intensity threshold I)_LWhen the associated response is triggered) begins at time 488 after a predefined delay time p1 has elapsed. Such dynamic intensity thresholds reduce the proximity of triggers to lower intensity thresholds (such as the first intensity threshold I)_HOr a second intensity threshold I_L) The associated response or a response concurrent therewith is associated with a dynamic intensity threshold I_DAccidental triggering of an associated response.

FIG. 4E shows yet another dynamic intensity threshold 492 (e.g., intensity threshold I)_D). In FIG. 4E, with the intensity threshold I_LThe associated response is triggered after a delay time p2 has elapsed since the touch input 490 was initially detected. Concurrently, the dynamic intensity threshold 492 decays after a predefined delay time p1 has elapsed since the touch input 490 was initially detected. Thus, at the trigger and intensity threshold I _LIntensity of touch input 490 after an associated responseThe subsequent increase in the intensity of the touch input 490 without releasing the touch input 490 may trigger the intensity threshold I_DThe associated response (e.g., at time 494), even if the intensity of the touch input 490 is at another intensity threshold (e.g., intensity threshold I)_L) Below.

Characterization strength of contact from light press strength threshold IT_LThe intensity below is increased to a light press intensity threshold IT_LAnd deep compression strength threshold IT_DThe intensity in between is sometimes referred to as a "light press" input. Characterization intensity of contact from at deep press intensity threshold IT_DThe following intensity increases above the deep press intensity threshold IT_DIs sometimes referred to as a "deep press" input. Characterization intensity of contact from at-contact detection intensity threshold IT₀The following intensity is increased to the contact detection intensity threshold IT₀And light press intensity threshold IT_LIs sometimes referred to as detecting a contact on the touch-sensitive surface. The characteristic intensity of the contact is above a contact detection intensity threshold IT₀Is reduced to below a contact detection intensity threshold IT₀Is sometimes referred to as detecting that the contact is lifted from the touch surface. In some embodiments, IT₀Is zero. In some embodiments, IT ₀Greater than zero. In some illustrations, shaded circles or ellipses are used to represent the intensity of contacts on the touch-sensitive surface. In some illustrations, circles or ellipses without shading are used to represent respective contacts on the touch-sensitive surface without specifying the intensity of the respective contacts.

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

In some embodiments, the device utilizes intensity hysteresis to avoid accidental input sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold having a predetermined correlation to the 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 proportion of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in the respective contact intensity above a press input intensity threshold and a subsequent decrease in the contact intensity below a hysteresis intensity threshold corresponding to the press input intensity threshold, and a respective operation is performed in response to detecting the subsequent decrease in the respective contact intensity below the hysteresis intensity threshold (e.g., a respective operation is performed on an "up stroke" of the respective press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity 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 contact intensity to an intensity at or below the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., an increase in contact intensity or a decrease in contact intensity, depending on the situation).

For ease of explanation, an explanation of an operation performed in response to a press input associated with a press input intensity threshold or in response to a gesture that includes a press input is optionally triggered in response to detecting: the contact intensity increases above the press input intensity threshold, the contact intensity increases from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, the contact intensity decreases below the press input intensity threshold, or the contact intensity decreases below the hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples where the operation is described as being responsive to detecting a decrease in contact intensity below a press input intensity threshold, the operation is optionally performed responsive to detecting a decrease in contact intensity below a hysteresis intensity threshold corresponding to and below the press input intensity threshold. As described above, in some embodiments, the triggering of these responses also depends on the time-based criteria to be met (e.g., a delay time has elapsed between the first intensity threshold to be met and the second intensity threshold to be met).

User interface and associated processing

Attention is now directed to embodiments of a user interface ("UI") and associated processes 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 contacts with the touch-sensitive surface.

5A-5HH illustrate an exemplary user interface for navigating between user interfaces, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, 15, 24A-24F, and 25A-25H. For ease of illustration, some of the embodiments will be discussed with reference to operations performed on a device having touch-sensitive display system 112. In such embodiments, the focus selector is optionally: a respective finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., a centroid of or a point associated with a respective contact), or a centroid of two or more contacts detected on touch-sensitive display system 112. However, similar operations are optionally performed on a device having a display 450 and a separate touch-sensitive surface 451 in response to detecting a contact on the touch-sensitive surface 451 while displaying the user interface shown in the figures on the display 450 with a focus selector.

Fig. 5A-5T illustrate exemplary embodiments of user interface selection modes that allow a user to efficiently navigate among multiple user interfaces on an electronic device (e.g., multifunction device 100) according to some embodiments. Exemplary for user interface selection mode The user interface (e.g., user interface 506 displayed on touch screen 112) includes representations of a plurality of 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 that are displayed as virtual card piles (e.g., "piles"). User inputs (e.g., contacts, swipe/drag gestures, tap gestures, etc.) detected on touch screen 112 (e.g., a touch-sensitive surface) are used to navigate between user interfaces that may be selected for display on the screen. FIG. 5A illustrates a display of a graphical user interface 502 for a web browsing application on an electronic device. The user interface 502 includes a display of a status bar 503 that provides information to the user (e.g., signal strength indicator(s) 402, time 404, bluetooth indicator 405, and battery status indicator 406 for wireless communication (s)). 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 bezel of the device, including the intensity of the contact from being at IT_DThe following intensity was increased to IT_DThe above strength.

In some embodiments, system level gestures are used to activate a user interface selection mode. For example, as shown in fig. 5B and 5C, a deep press on the left side of the bezel of the device activates the user interface selection mode. In an alternative embodiment, as shown in fig. 5EE and 5C, where the device is able to distinguish 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 a user interface selection mode (e.g., from IT in response to detecting that the intensity of the included contact is included _DThe following intensity was increased to IT_DThumb press of the above intensity, device 100 replaces the display of user interface 502 with the display of user interface 506). In contrast, as shown in fig. 5FF-5GG, in response to detecting a deep finger press 572 within the user interface 502 (e.g., at the same location in fig. 5EE where the device 100 detected the thumb deep press 570), 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 fig. 5 GG). Thus, in some embodiments, for activationIn selecting between the user interface selection mode and performing an application-specific operation (e.g., previewing web content), the device distinguishes between the type of gesture (e.g., deep thumb press versus deep finger press) and the location of the gesture (e.g., deep finger press on the left side of the bezel versus deep finger press within the user interface).

Fig. 5C-5F illustrate an exemplary user interface (e.g., graphical user interface 502) for a user interface selection mode, including a representation 508 of web browsing user interface 502 and at least a representation 510 of messaging user interface 506 displayed on 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 a name "Safari" 514 and an icon 516 associated with web browsing application user interface 502 represented in card 508. Similarly, title bar 522 includes the name "message" 520 and icon 518 associated with 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 presentation card. In some embodiments, the title bar is not illustrated as being detached from the user interface presentation card. In some embodiments, title information (e.g., a title bar, application name, and/or icon corresponding to an application) is displayed as hovering over or under a user interface presentation card. In some embodiments, the user interface selection mode does not include display of header information.

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

Fig. 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 web-browsing card 508 (e.g., representation 508 of web-browsing user interface 502) displayed over messaging card 510 (e.g., representation 510 of messaging user interface 507).

FIG. 5D illustrates an embodiment in which the cards for the user interface that are displayed immediately prior to entering the user interface selection mode are displayed further back in the user interface selection stack. For example, user interface 502 shows web-browsing card 508 (e.g., representation 508 of web-browsing user interface 502) displayed under messaging card 510 (e.g., representation 510 of messaging user interface 507).

Figure 5E illustrates an embodiment in which the stack includes more than two cards. For example, user interface 502 shows web-browsing card 508 displayed over messaging card 510, which in turn is displayed over photo card 526 (e.g., representation 526 of user interface 524 for an image management application). The cards at the top of the stack are spread relative to each other more than the cards further back in the stack, so that more cards appear at the top of the stack than those further back. For example, web-browsing card 508 is extended farther to the right relative to messaging card 510 than messaging card 510 is relative to photo card 526. Thus, messaging card 510 appears more on touch screen 112 than photo card 526; appearing to display the entirety of the messaging icon 518 and only a portion of the photo icon 528. The additional cards present in the stack are illustrated as one or more edges 503 displayed under card 528 (e.g., the bottom-most card partially shown).

FIG. 5F illustrates an exemplary user interface for a user interface selection mode that displays a user interface representation card (e.g., in a three-dimensional representation) having a significant depth as if the user looked down on a card that floated sequentially from a deck of cards located on a table along a virtual z-axis that is substantially orthogonal to the plane of the display. The cards become larger as they extend further from the bottom of the stack, giving them the appearance of traveling substantially toward the user. Web-browsing card 508 is displayed larger than messaging card 510, e.g., on touch screen 112, because it is farther from the bottom of the heap. As shown, viewing the multiple cards looks like traveling up a straight or slightly curved path (e.g., along the virtual z-axis) and to the right from the stack of cards on the left-hand side of the display. However, in some embodiments, the cards travel up and to the left from the stack of cards on the right hand side of the display, and/or travel obliquely or along a non-linear path (e.g., along a curved or seemingly random path).

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

In response to detecting that the contact 530 moves 532 from position 530-a in FIG. 5G to position 530-b in FIG. 5H and continues to position 530-c in FIG. 5I, the device further deploys the user interface card to the right (e.g., in the direction of the drag gesture). As shown in fig. 5G-5I, messaging card 510 moves laterally across the screen from position 510-a in fig. 5G to position 510-b in fig. 5H and on to position 510-c in fig. 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 over a table. This is illustrated by maintaining a fixed display of card 510 relative to the location of contact 530 on touch screen 112 (e.g., a touch-sensitive surface). For example, the word "Will" in the representation of the messaging user interface 507 is held directly under contact in fig. 5G-5I.

As shown in fig. 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 thus faster than messaging card 510, traveling from location 508-a in fig. 5G to location 508-b in fig. 5H and finally off-screen in fig. 5I (e.g., to the right of the right edge of touch screen 112). Messaging cards 510 appear more from beneath web-browser card 508 as contact 530 moves to the right due to the speed difference between the cards. More dialog in the representation of user interface 507 is presented, for example, as contact 530 moves from location 530-a in fig. 5G to location 530-b in fig. 5H (this is also illustrated by the appearance of the name "message" 520 in title area 522 above card 510 in fig. 5H after being covered by web-browsing card 508 in fig. 5G).

As shown in fig. 5G-5I, the card displayed under the card directly manipulated by the contact moves faster than the contact. For example, photo card 526 moves slower than contact 530, and thus than messaging card 510. More photo cards 526 emerge from beneath messaging card 510 as contact 530 moves to the right due to the speed difference between cards. In addition, as the contact 530 moves from location 530-a in FIG. 5G to location 530-b in FIG. 5H, more photos in the representation of the user interface 524 are revealed (this is also illustrated by the gradual appearance of the name "photo" 532 in the title area above the card 526 in FIGS. 5H and 5G).

FIG. 5H also illustrates that as the photo card moves from location 526-a in FIG. 5G (e.g., where it is shown to be on top of all hidden cards in the pile) to location 526-b in FIG. 5H, a previously hidden music card 534 (e.g., a representation 534 or user interface 536 for a music management/playback application) is revealed from beneath the photo card 526. This movement gives the user the following effect: the photo card 526 is slid off the top of a deck of cards, revealing a portion of the next card (e.g., music card 534).

FIG. 5J illustrates lifting the contact 530 at position 530-c. As shown in fig. 5G-5J, movement of the card across the display is shown to stop when movement 532 of contact 530 stops in fig. 5I and lift of contact 530 is detected in fig. 5J. This is illustrated in fig. 5J by maintaining the display of messaging card 510 at location 510-c, where it is displayed after stopping movement 532 of contact 530 at location 530-c in fig. 5I.

The series of fig. 5G, 5H, 5J and 5K illustrate lifting the contact 530 before stopping the movement 532. As shown in FIG. 5K, presentation cards 510, 526, and 534 continue to move across touch screen 112 (e.g., with decreasing momentum). This is illustrated by, for example, the change in position of messaging card 510 from position 510-c in fig. 5J (upon detection of contact 530 being lifted) to position 510-d in fig. 5K. In some embodiments, the continued momentum of the presentation card moving across the display occurs in response to a tap gesture (e.g., the UI represents inertial scrolling of the card, where the card moves with simulated inertia and slows down with simulated friction and has an initial velocity based on a velocity of the contact at a predefined time corresponding to a lifting of the contact from the touch-sensitive surface, such as a velocity at the lifting of the contact or a velocity of the contact just prior to the lifting of the contact).

FIG. 5K also illustrates the presentation of a phone card 540 (e.g., a representation 540 of a user interface 542 for a phone application) as a previously hidden music card 534 moves from location 534-c in FIG. 5J to location 534-d in FIG. 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.

Although the movement of the card in response to the drag gesture is illustrated in FIGS. 5G-5K as being along a straight line, in some embodiments, the movement of the card may be skewed from a predefined axis or path in response to similarly skewing the user input. In some embodiments, the card's path is fixed to follow a predefined path, and vector components of the movement orthogonal to the predefined path (e.g., a downward component of the movement of the contact from the top left side to the bottom right side of the touch-sensitive surface) are ignored when moving the display of the card across the screen. In some embodiments, the vector component of the movement orthogonal to the predefined movement path is reflected in the movement of one or more cards across the screen (e.g., a card that is directly manipulated may be pulled up or down from the path of the stack in contact, or the entire path of the stack, e.g., all cards, may be altered).

In some embodiments, vector components of the movement that are orthogonal to the predefined movement path are ignored when the movement produces angles below a threshold angle from the predefined movement path, while vector components of the movement that are orthogonal to the predefined movement path are considered when the movement produces angles above the threshold angle from the predefined movement path. For example, when the user input movement is skewed from the predefined movement path by less than a threshold angle (e.g., 15 °), the movement of one or more presentation cards is stabilized to account for the undesirable drift of the user's movement. But when the user makes a significant upward gesture (e.g., at an angle 80 ° skewed from the predefined path of movement), one or more of the presentation 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 the card from the stack while continuing to navigate through the remaining cards).

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

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

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

As shown in fig. 5M-5N, photo card 526 moves slower than contact 546 because it is displayed above messaging card 510. Because messaging card 510 is traveling at the same speed as contacts 546, photo card 526 also travels slower than messaging card 510. Thus, the messaging card 510 begins to catch up and cover the photo card 546. For example, the application name "photo" 532 associated with photo card 526 is fully exposed in FIG. 5L. As the contact 546 continues to move 548 to the left on the display, the message card 510 slides progressively farther over the photo card 526, completely obscuring the application name "photo" 532 when the contact 545 reaches the position 546-f in FIG. 5N.

FIG. 5O illustrates the velocity of the user interface representation card relative to the lateral velocity of contacts 530 and 546 on touch screen 112 as shown in FIGS. 5G-5I and 5L-5N. As shown in the top panel, the contact 530 moves from left to right across the touch screen 112 at a constant speed (e.g., graphically represented as a function of pixel over time) equal to the slope of the movement 532. After the contact 530 is lifted at the location 530-c, the device detects the contact 546, the contact 546 being moved back across the touch-sensitive screen 112 from right to left at a constant speed (e.g., graphically represented as a function of pixel time) equal to the slope of the movement 548. Since contacts 530 and 546 are detected at locations on touch screen 112 corresponding to the display of messaging card 510, the speed of messaging card 510 is equal to the speed of the contacts.

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

Representing the absolute lateral velocity of cards 526, 510, and 508 relative to the actual velocity of the user's 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 in a position on touch screen 112 that corresponds to the display of messaging card 510. Thus, the speed of messaging card 510 is the speed of user contact. The lateral velocity of the Web-browsing card 508 is equal to a factor of the velocity of the user contact, e.g., equal to the velocity of the user contact multiplied by a factor, where the factor is greater than 1 (e.g., due to the Web-browsing card 508 having a higher z-position relative to the messaging card 510 that the user contact 546 directly manipulates). The lateral velocity of the photo card 526 is also equal to a factor of the velocity of the user contact, e.g., equal to the velocity of the user contact multiplied by a factor, where the factor is less than 1 (e.g., because the photo card 526 has a lower z-position relative to the messaging card 510 that the user contact 546 directly manipulates).

The middle panel of fig. 5O also illustrates the absolute z-position of the blur level applied to each card in the stack relative to the card, as in some embodiments. Thus, as the cards unwind 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 fuzzy changes to the particular card as the absolute z position of the particular card is manipulated by user input.

As shown in fig. 5M-5N, when moving in the opposite direction of the original gesture (e.g., back toward the base of the heap), web-browsing card 508 catches up with contact 546 because it travels faster, as shown in fig. 5O. When the leading edge (left edge) of web-browsing card 508 is displayed at location 508-f on the touch screen corresponding to the centroid of contact 546 at location 546-f, web-browsing card 508 moves between contact 546 and messaging card 510. At this point, contacts 546 begin to directly manipulate web-browsing card 508 rather than messaging card 510.

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

As shown in the lower panel of fig. 5O, the speed of the UI cards 526, 510, and 508 slows down when this handoff occurs. As the messaging card 510 moves when it is displayed at location 510-e (e.g., as in fig. 5M and as shown in the middle panel of fig. 5O), the web-browsing card 508 moves when displayed at location 508-f (e.g., as in fig. 5N) at a speed corresponding to the speed of the contact 546. Similarly, as photo card 526 travels while displayed at 526-e (e.g., as in FIG. 5M), messaging card 508 travels at the same slower relative speed while displayed at position 510-f (e.g., as in FIG. 5N) because it is now the card below contact 546. Finally, the photo card 526, when displayed at position 526-f (e.g., as in FIG. 5N), moves at a slower speed than it moves when displayed at position 526-e (e.g., as in FIG. 5M). 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. Thus, in response to detecting a user input gesture having a variable speed, the electronic device moves the UI card at the variable speed.

Speed profile 550 is an exemplary representation of the relationship between the speeds of the respective UI presentation cards displayed in the stack. A first card (e.g., web-browser card 508) displayed above a second card (e.g., messaging card 510) in a relative Z position (e.g., along a virtual Z-axis) will always travel faster than the second card. In some embodiments, the speed profile 550 represents other variable manipulations in the display of the UI presentation card. Such as a blur level applied to respective cards in the stack (e.g., cards displayed further down in the stack are more blurred than cards displayed toward the top of the stack), a size of respective 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 in the stack appearing smaller than cards displayed toward the top of the stack), or a lateral position of respective 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 in 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 the points on the velocity profile 550 (e.g., corresponding to the placement of the UI representation cards relative to each other) has a constant ordinate value difference (e.g., the change in the z-dimension between the two points as represented by the vertical difference is the same). In some embodiments, as shown in fig. 5O, where the velocity profile 550 follows a concave function, there is an increasing difference in the vertical distance between successive points (e.g., a greater 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-browser card 508. However, the difference between the lateral velocities of messaging card 510 and web-browsing card 508 is greater than the difference between the lateral velocities of photo card 526 and messaging card 510. This causes the following visible effects on the display: the top card displayed on the stack will quickly move out of the screen relative to the appearance of the card displayed further back in the stack.

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

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

FIG. 5T illustrates detecting that contact 556 is lifted at position 556-c without stopping movement 558, consistent with a tap gesture. Messaging card 510, traveling with contact 556 (e.g., at the same speed; directly manipulated by contact 556), continues to move on the display with simulated inertia, eventually stopping at location 510-c on touch screen 112.

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

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

5X-5AA illustrate removal of a user interface representation card upon detection of a predefined user input. FIG. 5X illustrates a user interface 506 for a user interface selection mode that displays a stack of user interface cards 508, 510, 526, and 534 navigated by a user. Device 100 detects a swipe gesture that includes a contact 560 and a movement 562 that is substantially orthogonal to a predefined movement path of the cards in the stack (e.g., swipe moves up touch screen 112, while cards in the stack move left and right across the screen while navigating), which movement originates from the location of touch screen 112 where messaging card 510 is displayed. In response to detecting movement 562 of contact 560 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-screen (e.g., continuing to position 510-g in figure 5Z via movement from position 510-b in figure 5X to position 510-f in figure 5Y).

As shown in fig. 5Z-5AA, device 100 moves photo card 526 and music card 534 up 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, replacing the void in the stack caused by the removal of messaging card 510. Likewise, the music card 534 moves from position 534-g in FIG. 5Z to position 534-h in FIG. 5AA, replacing the void in the stack caused by the photo card 526 moving up the stack. The blur level applied to the photo card 526 and the music card 534 also adjusts according to their upward movement in the pile. For example, photo card 526 is partially obscured at position 526-g shown in FIG. 5Z, but is in focus at position 526-h shown in FIG. 5 AA. In some embodiments, removing the user interface from the heap indicates that the card also closes the active application associated with the user interface.

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

Fig. 5DD illustrates a visual effect applied to a title area associated with a first user interface representation card as the user interface representation card displayed over the first card moves into close proximity. Fig. 5DD illustrates messaging card 510 displayed over photo card 526 in user interface 506 of the user interface selection mode, user interface 506 including a substantially two-dimensional representation of the heap. Photo card 526 is associated with a title bar 558 that includes the name "photo" 532 and icon 526 for the image management application associated with user interface 524. Messaging card 510 is associated with a title bar 522 that displays information related to the messaging application associated with user interface 507. The display of messaging card 510 gradually slides over photo card 526 over time (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 fig. 5 DD). As the edge of messaging title bar 522 approaches the display of the name "photo" 532 on photo title bar 558 (at location 508-b of messaging card 510 in the second panel), the transition of the device application name "photo" 532 fades. Panel three of FIG. 5DD illustrates the display with the name "photo" 532 removed before the messaging title bar 522 obscures the previous location of the name "photo" 532 on the photo title bar 558.

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

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

Fig. 6A-6V illustrate exemplary embodiments of user interface selection modes that allow a user to glance at a previously displayed representation of a user interface without leaving the current user interface, allow the user to quickly swap between two respective user interfaces, and allow the 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) that are displayed as virtual card piles (e.g., "piles"), or as selections between two most recently displayed user interfaces. User inputs (e.g., contacts, swipe/drag gestures, tap gestures, etc.) detected on touch screen 112 (e.g., a touch-sensitive surface) are used to navigate between user interfaces that may be selected for display on a screen (e.g., touch screen 112).

6A-6G illustrate embodiments in which a user operating an electronic device displaying a first user interface (e.g., any user interface for a respective application that opens on the device, such as a web browsing user interface) may navigate between the following using different gestures starting from a common contact on a touch-sensitive surface (e.g., touch screen 112 on multifunction device 100): (ii) (i) glance at the previously displayed user interface and revert back to the first user interface; (ii) change to a previous application; (iii) entering a user interface selection mode (e.g., an application selection mode); and (iv) scroll through the user interface within the user interface selection mode.

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

6B-6C, the device enters a user interface preview mode upon detecting user input including having a value below a predetermined threshold (e.g., below a deep press Intensity Threshold (IT)_D) The following; e.g., an exemplary predetermined input) of intensity 602 adjacent to the left edge of the touch screen 112 (e.g., on the bezel). Upon detection of an input that includes a contact 602,the device replaces the display of web browsing user interface 502 on touch screen 112 as shown in fig. 6B with a 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, such as representation 508 of web browsing user interface 502 and representation 510 of messaging user interface 507. As shown in FIGS. 6B and 6C, the intensity of contact 602 is maintained at the deep press Intensity Threshold (IT) _D) (e.g., an exemplary predetermined intensity threshold) and the contact is stationary at the point of origin detection.

Device 100 then detects termination of the user input in fig. 6D that includes contact 602. Since the intensity of contact 602 is maintained at the deep press Intensity Threshold (IT)_D) Thereafter, and since the user input does not include movement of the contact 602 (e.g., movement in a predefined direction on the touch screen 112), upon detecting termination (e.g., lifting) of the contact 602, the device 100 reverts the display back to the web browsing user interface 502 by replacing the display of the user interface 506 with the display of the user interface 502.

Series of fig. 6A, 6E-6G illustrate alternative embodiments in which a user views (e.g., "glances") a representation of a previously displayed user interface and selects to display the previously displayed user interface, rather than reverting back to the user interface displayed on the device prior to the glance. FIG. 6A illustrates a display of a graphical user interface 502 for a web browsing application on an electronic device.

FIG. 6E illustrates the device entering a user interface preview mode upon detecting user input including having a value below a predetermined threshold (e.g., below a deep press Intensity Threshold (IT)_D) The following; e.g., an exemplary predetermined input), adjacent to the left edge of the touch screen 112 (e.g., on the bezel). Upon detecting an input comprising 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, such as representation 508 of web browsing user interface 502 and representation 510 of messaging user interface 507. As shown in FIGS. 5B and 5C, the strength dimension of contact 604 Held at the deep compression Intensity Threshold (IT)_D) (e.g., an exemplary predetermined intensity threshold). However, the electronic device detects that contact 604 is moving 606 in a predefined direction (e.g., laterally across touch screen 112) from location 604-a in FIG. 6E to location 604-b in FIG. 6F.

Device 100 then detects termination of the user input in fig. 6D that includes contact 604. Since the strength of the contact 604 is maintained at the deep press strength threshold (IT)_D) Thereafter, and since the user input includes movement of the contact 604 on the touch screen 112 in a predefined direction (e.g., laterally across the display), the device 100 replaces the display of the user interface 506 with the display of the user interface 507 for the messaging application as shown in fig. 6D, rather than reverting back to the web browsing user interface 502.

Thus, in some embodiments, when a user input invoking the user interface preview mode has a characteristic intensity (e.g., a maximum intensity within the duration of the input below a predetermined threshold), the user may distinguish between resuming display of the user interface displayed immediately prior to entering the user interface preview mode (e.g., when the user is merely glancing at a 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).

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

As previously shown in FIGS. 6C and 6E, the device enters a user interface preview mode upon detecting user input including having a value below a predetermined threshold (e.g., below a deep press Intensity Threshold (IT)_D) The following; e.g., an exemplary predetermined input) adjacent to the left edge of the touch screen 112 (e.g., on the bezel). FIG. 6H also illustrates that a key is detectedWith the intensity of the contact (e.g., contact 608 in FIG. 6H) increasing, 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 FIGS. 5A-5 HH).

Device 100 then detects termination of the user input in fig. 6I that includes contact 608. Since the intensity of the contact 608 exceeds a predetermined intensity threshold (e.g., a deep press Intensity Threshold (IT) for invoking the stable user interface mode)_D) Device 100 does not replace the 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 FIGS. 5A-5 HH.

Thus, in some embodiments, the user may 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 control based on the intensity of the contact used to invoke the user interface selection preview mode.

6J-6L illustrate embodiments in which a user directly manipulates the display of a user interface selection pattern by increasing the intensity of the user input. FIG. 6J illustrates entering a stable user interface selection mode, including by detecting that a user has exceeded a predetermined intensity threshold (e.g., a deep press Intensity Threshold (IT)_D) Adjacent (e.g., on a bezel) to a left edge of touch screen 112), a stack of user interface representation cards (e.g., user interface representations 508, 510, and 526 displayed in relative Z positions to one another, e.g., as described with respect to fig. 5A-5 HH) is displayed in user interface 506.

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

6M-6P illustrate embodiments in which the device 100 distinguishes between user inputs based on the characteristic strength of the user inputs made within the application user interface. FIG. 6M 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 that includes a location on touch screen 112 corresponding to display of "back" button icon 614 having an intensity that exceeds a predetermined intensity threshold (e.g., a deep press Intensity Threshold (IT) _D) The characteristic strength of contact 612. In response to detecting the deep press, in FIG. 6N, device 100 replaces the display of web browsing user interface 502 on touch screen 112 with user interface 506 for the user interface selection mode, user interface 506 including user interface representations 508, 618, and 622 of previously viewed web browsing interfaces 502, 616, and 620 (e.g., previously viewed web pages in the hierarchy of browser histories).

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

FIG. 6O also 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 tap gesture (rather than a deep press as shown in FIG. 6M) that includes a tap gesture having a pressure at a predetermined intensity threshold (e.g., a deep press Intensity Threshold (IT)_D) Contact 624 of characteristic strength below. In response to detecting the tap gesture, device 100 replaces the display of web-browsing user interface 502 on touch screen 112 with web-browsing user interface 616 for associating previously viewed user interfaces in web-browsing applications (e.g., the last visited web page in web-browsing applications) as shown in FIG. 6P. Thus, in some embodiments, the electronic device distinguishes between application-specific user interface inputs based on the characteristic strength of the user input.

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 FIGS. 6A, 6E-6G, the user may quickly swap back to the first user interface by repeating the user gesture while the device displays the user interface for the second application.

FIG. 6Q illustrates that after detecting a user gesture that lifts up causing the device to change the user interface display to a second user interface 507 for the messaging application, the device detects a second user input comprising a user gesture having a value below a predetermined threshold (e.g., below a deep press Intensity Threshold (IT)_D) The following; e.g., an exemplary predetermined input), adjacent to the left edge of the touch screen 112 (e.g., on the bezel). Upon detecting an input that includes a contact 626, the device replaces the display of the messaging user interface 507 on the touch screen 112 with the display of the user interface selection mode 506. As shown in FIG. 6R, user selection mode 506 includes user interface representations of the last two user interfaces displayed on touch screen 112, such as representation 508 of web browsing user interface 502 and representation 510 of messaging user interface 507. However, the device is not suitable for use in a kitchenRather, the relative order of representations 508 and 510 in user interface 506 is switched as compared to the display of user interface 506 in fig. 6E-6F, because messaging user interface 507 is now the most recently displayed user interface on touch screen 112, and thus in fig. 6R, representation 510 of user interface 507 is displayed over representation 508 of user interface 502.

As shown in FIGS. 6Q and 6R, the strength of contact 626 is maintained at the deep press strength threshold (IT)_D) (e.g., an exemplary predetermined intensity threshold). However, the electronic device detects movement 628 of the contact 626 in a predefined direction (e.g., laterally across the touch screen 112) from the position 626-a in FIG. 6R. In fig. 6S, device 100 then detects termination of the user input including contact 626. Since the strength of contact 626 is maintained at the deep press strength threshold (IT)_D) Thereafter, and since the user input includes movement of the contact 626 in a predefined direction (e.g., laterally across the display) on the touch screen 112, the device replaces the display of the user interface 506 with the display of the user interface 502 for the web browsing application, rather than reverting back to the messaging user interface 507 as shown in fig. 6Q. Thus, the user switches back to the first user interface displayed on the touch screen 112 in FIG. 6A.

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. FIG. 6T illustrates a display of a graphical user interface 502 for a web browsing application on an electronic device. Device 100 detects a deep press that includes a touch screen 112 adjacent a right edge (e.g., on a bezel; a second predefined location) having an intensity that exceeds a predetermined intensity threshold (e.g., a deep press Intensity Threshold (IT) _D) ) of the characteristic strength of the contact 628. 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 on touch screen 112 for the previously displayed website as shown in fig. 6U.

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

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

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 or touch-sensitive track pad separate from the display), in accordance with some embodiments. In some embodiments, a user swaps between the two most recently viewed user interfaces using varying intensities of touch gestures at one or more predefined areas on the touch-sensitive surface.

Fig. 7A-7F illustrate embodiments in which a user previews (e.g., "glimpse") a previously displayed representation of a user interface using a touch gesture having a first characteristic intensity at 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. FIG. 7A illustrates a display of a graphical user interface 502 for a web browsing application on an electronic device.

FIG. 7B illustrates detecting a touch gesture that includes a touch gesture having a first characteristic intensity (e.g., exceeding a light press Intensity Threshold (IT)_L) But at the deep press Intensity Threshold (IT)_D) Below) adjacent to the left edge of the touch screen 112 (e.g., on the bezel; at a predefined location on the touch-sensitive surface). In response to detecting the touch gesture, device 100 enters a user interface selection mode, thereby utilizing the user interface on touch screen 112 in FIG. 7C The display of user interface 506 in the user interface selection mode replaces the display of web browsing user interface 502 on touch screen 112 in FIG. 7B.

FIG. 7C illustrates the display of user interface 506 for the 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. In some embodiments, the two representations are for the last two user interfaces displayed on the device (e.g., the last two applications open on the display). In some embodiments, the two representations are for the last two user interfaces (e.g., the last two web pages displayed in a web browser application or the last two messages displayed in an email management application) displayed for a particular application opened on touch screen 112 when the user interface selection mode is initiated.

As shown in fig. 7C, web-browsing card 508 is displayed as if above messaging card 510 in the Z-orientation (e.g., positioned along a virtual axis substantially orthogonal to the plane of the display) and is laterally displaced to the right of messaging card 510, as it represents the last user interface displayed on touch-screen 112 prior to activation of the user interface selection mode. Device 100 also applies an ambiguity 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 prior to activation of the user interface selection mode is displayed behind or equal to the second user interface representation in the relative Z-orientation.

FIG. 7D illustrates detecting an increase in intensity of the contact 702 (e.g., from just pressing the intensity threshold IT in FIG. 7C)_LIntensity above to just-in-depth compression intensity threshold IT in FIG. 7D_DThe following strength). In response to detecting the increase in intensity of contact 702, messaging card 510 increases in size and moves in the virtual z-dimension toward the plane of touch screen 112 (e.g., from location 510-a in FIG. 7C to location 510-b in FIG. 7D). Messaging card 510 also begins to become in focus (e.g., the ambiguity level decreases) as it moves up in the virtual z-dimension. All in oneAs time progresses, the web-browsing card 508 decreases in size and moves backward in the virtual z-dimension (e.g., from position 508-a in FIG. 7C to position 508-b in FIG. 7D). In some embodiments, an animation is displayed to show 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.

FIG. 7E illustrates detecting a further increase in intensity of contact 702 (e.g., exceeding a deep press Intensity Threshold (IT)_D)). In response to detecting that the intensity of the contact 702 exceeds a second characteristic intensity (e.g., exceeds a deep press Intensity Threshold (IT)_D) Messaging card 510 continues to move up in the virtual z-dimension and over web-browsing card 508, and web-browsing card 508 continues to move back in the virtual z-dimension and begins to blur.

In some embodiments, in response to detecting that the intensity of the contact 702 exceeds a second predetermined threshold (e.g., a deep press Intensity Threshold (IT)_D) The device automatically opens the 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 pattern with user interface 507 as shown in fig. 7F.

7G-7K illustrate alternative embodiments for "glancing at" and "popping up" a previously displayed user interface (e.g., and associated application) as described with respect to FIGS. 7A-7F. In this embodiment, the user interface representation is displayed in a substantially two-dimensional view rather than along a virtual z-axis.

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

FIG. 7G illustrates the display of user interface 506 for the 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 fig. 7G, messaging card 510 is displayed as if directly on top of web-browsing card 508 in the Z-orientation and is laterally displaced to the right of web-browsing card 508, as it represents the last user interface displayed on touch-screen 112 prior to activation of the user interface selection mode.

FIG. 7H illustrates detecting an increase in intensity of contact 704 (e.g., from just pressing intensity threshold IT in FIG. 7C)_LIntensity above to just-in-depth compression intensity threshold IT in FIG. 7D_DThe following strength). In response to detecting an increase in the intensity of the contact, web-browsing card 508 is further presented beneath messaging card 508 by moving messaging card 510 to the right of the screen from position 510-a in FIG. 7G to position 510-b in FIG. 7H.

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

FIG. 7J illustrates a further decrease in the intensity of the detected contact 704 below the first characteristic intensity (e.g., at a light press Intensity Threshold (IT)_L) Below). In response to falling below the first characteristic strength, device 5100 exits the user interface selection mode and replaces the display of user interface 506 with user interface 507 for the messaging application displayed immediately prior to entering the user interface selection mode (e.g., the device reverts to entering its last active state upon exiting the user interface selection mode because contact 704 failed to "pop-up" web-browsing card 508 from beneath messaging card 510). FIG. 7K further illustrates detecting that the contact 704 is lifted, thereby causing the user interface displayed on the touch screen 112 to be unchanged.

In contrast, the figures illustrate embodiments in which, after the user has swapped the user interface from the web browsing user interface 502 to the messaging user interface 507 (e.g., as described in fig. 5A-5F), the user again begins "glimpsing" in the event that a contact 706 is detected in a predetermined area on the touch-sensitive surface in fig. 7L (e.g., the left side of the bezel)And "pop" processing. In response to detecting an increase in the intensity of contact 706 from FIG. 7M to 7N, the messaging card moves from location 510-d in FIG. 7M to location 510-e in FIG. 7N. Detecting a further increase in the intensity of contact 706 beyond a second characteristic intensity (e.g., a deep press Intensity Threshold (IT) in fig. 7O_D) To bounce back to the web browsing application (e.g., the device replaces the display of the user interface 506 for the user interface selection mode with the user interface 502 for the web browsing application). Thus, the user has switched back to the originally displayed user interface.

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

Fig. 8A-8R illustrate exemplary embodiments for navigating among multiple user interfaces represented in a user interface selection mode, including the ability to "glance" and "pop-up" applications (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 or touch-sensitive track pad separate from the display), according to some embodiments.

8A-8D illustrate an embodiment in which a user "pops up" (e.g., selects) a user interface with a high intensity user input (e.g., deep press) for display on a device. Fig. 8A illustrates the display of a user interface 506 for a user interface selection mode, which includes a representation 508 of a web browsing user interface 502 ("web browsing card 508"), a representation 510 of a messaging user interface 507 ("messaging card 510"), and a representation 526 of a photo management user interface 524 ("photo card 526") in a user interface previously displayed on the device. A user interface representation is displayed in the card stack (extending rightward from the base of the stack). Each card is ordered 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 an increase in intensity of contact 802 from fig. 5A to fig. 5A at a location corresponding to the display of messaging card 510. In response, the display area of messaging card 510 is increased (e.g., the user glances at messaging card 510) by moving web-browsing card 508 further to the right (e.g., from position 508-a in FIG. 8A to position 508-B in FIG. 8B).

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

The device 100 then detects that the pressure of the contact 802 has increased further beyond a characteristic intensity (e.g., a deep press Intensity Threshold (IT)_D)). In response, messaging card 510 is "popped" from the heap and the device opens the associated application (e.g., replaces the display of user interface 506 for the user interface selection mode with the display of user interface 507 for the messaging application).

8E-8F illustrate embodiments in which a "pop-up" card (e.g., selecting an application and corresponding user interface) includes an animation. Fig. 8E illustrates an increase in pressure in response to detecting contact 802 beyond a characteristic intensity (e.g., a deep press Intensity Threshold (IT)_D) To select (e.g., "pop-up") a messaging card. In response, device 100 displays an animation that transitions from display of user interface 506 for the user interface selection mode to display of user interface 507 for the messaging application. The animation includes sliding web-browser card 508 completely off messaging card 510 (e.g., by moving the web-browser card further to the right to position 508-d). The animation also includes drawing the messaging cards 510 from the heap, and piece-by-pieceGradually increasing the size of messaging card 510, for example, until the display of user interface 507 fills the entire touch screen 112 (e.g., as illustrated by moving messaging card from position 510-b in fig. 8E to position 510-c in fig. 8F) to provide the effect that the card is moving in the virtual z-dimension toward the user.

8G-8H illustrate alternative embodiments for "glancing at" a user interface representation card. Fig. 8G illustrates the display of a user interface card stack as described with respect to fig. 8A (e.g., where web-browser card 508 is displayed on top of messaging card 510 and offset to the right of messaging card 510, and messaging card is displayed on top of photo card 526 and offset to the right of photo card 526). Fig. 8G also illustrates a contact 804 at a location of touch screen 112 corresponding to the display of messaging card 510.

Figure 8H illustrates that more areas of the messaging card are presented in response to detecting an increase in intensity of the contact 804 when displayed over the messaging card 510. However, rather than sliding web-browser card 508 to the right away from messaging card 510, FIG. 8H illustrates moving messaging card 510 to the left (e.g., the messaging card moves from position 510-a in FIG. 8G to position 510 in FIG. 8H) as if it were removed from the deck. Thus, fig. 8G and 8H illustrate using the strength of the contact (e.g., 804) to more visualize the user interface representation cards in the stack by sliding the cards out of the stack in a direction opposite to the direction in which the stack unfolds from the base of the stack.

Figure 8I illustrates another alternative embodiment for "glancing" messaging card 510, where in response to detecting an increase in intensity of contact 804 displayed at a location corresponding to the display of messaging card 510, web-browser card 508 moves to the right away from messaging card 510 and messaging card 510 is pulled from the deck to the left. Thus, fig. 8G and 8I illustrate the use of the intensity of the contact (e.g., 804) to more visualize the respective user interface representation card in the stack by sliding the card out of the stack in a direction opposite to the direction in which the stack is unfolded from the base of the stack, and further sliding the card displayed at least in a direction above the respective user interface representation card in the direction in which the stack is unfolded from the base of the stack.

8J-8R illustrate an expanded "glance" and "pop-up"navigation, where multiple cards are glanced at before popping up an application. FIG. 8J illustrates a display of a graphical user interface 502 for a web browsing application on an electronic device. FIG. 8K illustrates the device entering a user interface selection mode upon detection of a user input including having a characteristic intensity (e.g., exceeding a deep press Intensity Threshold (IT)_D) The strength of (c); e.g., an exemplary predetermined input) of a contact 806 adjacent to the left edge of the touch screen 112 (e.g., on the bezel). In response to activating the user interface selection mode, device 100 replaces the display of web browsing user interface 502 with user interface 506 for the user interface selection mode as shown in FIG. 8K.

Fig. 8K illustrates the display of a user interface card stack as described for fig. 8A (e.g., where web-browser card 508 is displayed on top of messaging card 510 and offset to the right of messaging card 510, which is displayed on top of photo card 526 and offset to the right of photo card 526). FIG. 8K also illustrates at location 806-a corresponding to the left edge of touch screen 112 and having the deep press Intensity Threshold (IT) exceeded_D) The strength of contact 806.

As shown in FIG. 8L, device 100 detects a decrease in intensity of user contact 806 to a deep press Intensity Threshold (IT)_D) The following. Device 100 also detects movement 808 of contact 806 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.

Fig. 8M illustrates detecting an increase in intensity of user contact 806 as displayed over messaging card 510, thereby causing a "glance" at messaging card 510 by moving a web-browser card away from messaging card 510.

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

FIG. 8P illustrates detecting an increase in intensity of the contact 506 as it appears on photo card 526, and in response, glimpsing at photo card 526 by moving the display of Web-browser card 508 and messaging card 510 to the right.

FIG. 8Q illustrates detecting a further increase in intensity of the contact 806 as displayed over the photo card 526 beyond a predefined intensity threshold (e.g., a deep press Intensity Threshold (IT)_D)). In response, the photo card 526 is contacted "pop-up," as illustrated by moving web-browsing card 508 and messaging card 510 completely off of photo card 526. Then when the electronic device enters the photo management application in FIG. 8R, the photo card 526 expands (e.g., via dynamic animation) to fill the entire touch screen 112 with the user interface 524.

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

Fig. 9A illustrates a display of a user interface 506 for a user interface selection mode that includes a display of a stack of user interface representations (e.g., user interface representation cards 508, 510, and 526 for a web browsing user interface 502, a messaging user interface 507, and an image management user interface 524). 5A-5HH, the user interface representation cards are unrolled to the right from the base of the stack and are ordered relative to each other in the Z position (e.g., representation 508 is laterally offset to the right of representation 510 and ordered above representation 510 along the Z axis).

Device 100 detects user input that includes contact 902 at a location on touch screen 112 that corresponds to display of user interface representation 526. The contact 902 has an intensity below a predefined intensity threshold (e.g., at a deep press Intensity Threshold (IT) _D) Below) characteristic strength. In response to detecting contact 902 at a location corresponding to the display of photo card 526, messaging card 510 and web-browsing card 508 are moved to the right (e.g., away from photo card 526) in FIG. 9B from locations 510-a and 508-a in FIG. 9APositions 510-b and 508-b, the device 100 more visualizes the photo card 526. Device 100 then detects that contact 902 moves 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 fig. 9C-9D, device 100 presents messaging card 510 more by moving messaging card 510 out from under web-browsing card 508 and back toward the stack (e.g., to the left on display 112) from position 510-b in fig. 9C to position 510-C in fig. 9D in response to contact 902 moving to a position corresponding to the display of messaging card 510.

9E-9F illustrate embodiments in which an application is selected from a user interface selection mode by lifting a contact displayed in a position above a user interface presentation card associated with the application. Device 100 detects the lifting of contact 902 when positioned over messaging card 510 (e.g., terminates user input including contact 902 at a location corresponding to the display of card 510 on touch screen 112) to select a 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 presentation card 510. For example, device 100 opens a messaging application associated with user interface 507 because contact 902 is above the corresponding card when the user lifts the contact.

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

22A-22BA illustrate an exemplary user interface for performing application-independent operations (e.g., system-wide actions), such as navigating between user interfaces, according to some embodiments. In some embodiments, this is accomplished by a user interface that distinguishes at least two types of input originating from an edge of the touch screen and, in response, performs a system-wide operation when a first type of input is detected and an application-specific application when a second type of input is detected. In some embodiments, the two types of operations are distinguished based at least on their proximity to the edges of the touch-sensitive surface and the 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 FIGS. 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, 15, 24A-24F, and 25A-25H. While some of the following examples will be given with reference to input on a touch screen display (where the touch sensitive surface and the display are combined), in some embodiments, the device detects input on a touch sensitive surface 451 separate from the display 450 as shown in fig. 4B.

22A-22D illustrate embodiments in which a device detects two inputs that meet system gesture intensity criteria and determines whether to perform an application-specific action or a system-wide action based on the proximity of the inputs to the edges of the touch screen, according to some embodiments. FIG. 22A illustrates a web browsing user interface 502 having two location boundaries 2202 and 2204. Location boundary 2202 defines an area of touch screen 112 to the left of the boundary (e.g., the area extends left out of the touch screen) in which 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 an intensity criteria). Location boundary 2204 defines a larger area of touch screen 112 to the left of the boundary (e.g., the area extending left out of the touch screen) in which contact must be detected in order to activate system-specific actions such as navigating to a previous user interface displayed within the active application (e.g., when the contact also meets the intensity criteria).

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

In FIG. 22D, the device detection has system-wide action (e.g., intensity threshold IT) in order to perform_L) And a characteristic intensity above a threshold intensity required for an application-specific action 2212. However, contact 2212 does not meet the system-wide action location criteria because it is detected to the right of boundary 2202. Since contact 2212 satisfies application-specific location criteria, in response to detecting that the contact moved to the right, the device navigates to a 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 fig. 22E.

22F-22G illustrate embodiments in which the device adjusts the location criteria needed to perform a system-wide action in response to the shape of the detected contact. In FIG. 22F, the device detects a signal having a threshold intensity (e.g., intensity threshold IT) needed to perform a system-wide action_L) The above characteristic strength contact 2214. However, contact 2214 does not meet the default system-wide action location criteria because it is detected to the right of boundary 2202. However, since the contacts are wider and elongated compared to typical fingertip contacts (e.g., this instructs the user to stretch their thumb to reach the left side of the device), the device adjusts the system-wide action location criteria so that the contact detected to the left of boundary 2204 satisfies the location criteria. Thus, in response to detecting that the contact moved to the right, the device enters a user interface selection mode, as indicated by replacing the web browsing user interface 502 with the multitasking user interface 506 in FIG. 22G.

22H-22I illustrate embodiments in which a device detects a contact that meets system-wide action location criteria, but does not meet system-wide action intensity. In FIG. 22H, Equipment checkA contact 2218 that meets the positional requirements for performing a system-wide action is detected (e.g., because it is detected to the left of boundary 2202). However, contact 2218 has a threshold intensity (e.g., intensity threshold IT) that is needed in order to perform system-wide action criteria _L) The following characteristic strengths. Since contact 2218 satisfies the application-specific intensity criteria, in response to detecting that the contact moved to the right, the device navigates within the web browsing application to the previously viewed user interface, as indicated by replacing web browsing user interface 502 with web browsing user interface 616 in fig. 22I.

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

In FIG. 22K, the device detects a signal having a threshold intensity (e.g., intensity threshold IT) needed to perform a system-wide action_L) Contact 2226 of the above characteristic strength. Since the device determines that the user's finger used to make contact 2226 must extend to the left beyond the 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 was wider, as indicated by the dashed line in fig. 22K. Since the farthest point in the projected contact is to the left of position boundary 2222, contact 2226 also satisfies the system-wide action position criteria. Thus, in response to detecting that the contact moved to the right, the device enters a user interface selection mode, as indicated by replacing the web browsing user interface 502 with the multitasking user interface 506 in FIG. 22L.

In FIG. 22M, the device detects a signal having a threshold intensity (e.g., intensity threshold IT) needed to perform a system-wide action_L) The above characteristic strength contact 2230. The device then projects the leftmost border where contact 2230 will be located outside the edges of touch screen 112. Since the farthest point in the projected contact is to the right of position boundary 2222, contact 2226 fails to satisfy the seriesSystem wide action location criteria. Since contact 2230 satisfies application-specific location criteria, in response to detecting the contact moving to the right, the device navigates within the web browsing application to the previously viewed user interface, as indicated by replacing web browsing user interface 502 with web browsing user interface 616 in fig. 22N.

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

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

22AB-22AG illustrate embodiments in which the gesture further includes a direction criterion. When the gesture satisfies the direction criteria, the device performs a system-wide action as shown in fig. 22AB-22 AD. When the gesture does not meet the direction criteria, the device does not perform system-wide actions, as shown in FIGS. 22AE-22 AG.

22AH-22AO illustrate an embodiment in which system-wide actions are still performed when the device first detects an input outside of a location boundary, but the contact is moved into the location boundary, and then the intensity criteria is met, as shown in FIG. 22AH-22AK instead of in FIG. 22AL-22 AO.

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

22AT-22AY illustrates an embodiment in which the system-wide action intensity criteria are higher during the time period immediately after the detection of the on-screen contact. In the event that the contact moves outside of the active area before higher intensity requirements are achieved, the device does not perform system-wide actions as shown in fig. 22AT-22 AU. In the event that the contact achieves a higher intensity requirement before moving outside of the activation zone or waits for the intensity threshold to drop, the device performs a system-wide action as shown in fig. 22AW-22 AY.

22AZ-22BA illustrate an embodiment in which the system-wide action intensity criteria are higher near the top and bottom of the touch screen.

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

FIG. 23A illustrates a web browsing user interface 502 having location boundaries 2302 and 2312. When a contact that meets the system-wide action activation criteria does not cross boundary 2302, the device does not navigate to the new user interface upon terminating input as shown in FIGS. 23B-23D. Upon a contact meeting the system-wide action activation criteria crossing boundary 2302 instead of boundary 2312, the device navigates to the user interface selection mode as shown in fig. 23E-23G. Upon a contact meeting the system-wide action activation criteria crossing boundary 2302 and boundary 2312, the device navigates to the last user interface active on the device as shown in fig. 23I-23K.

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

23Q-23T illustrate embodiments in which the device provides the following cues: the intensity of the contact approaches the intensity threshold needed to activate system-wide action. For example, as the intensity of contact 2326 approaches intensity threshold IT_LThe device begins to slide right across active user interface 502, revealing previously active user interface 507. In fig. 23S, in response to detecting that the intensity of contact 2326 has further increased above intensity threshold 2326, the device activates a system-wide action, allowing navigation between user interfaces (e.g., by sliding the contact to the right into one of the three zones). In FIG. 23T, the intensity of contact 2326 is detected and further increased to a deep press intensity threshold IT_DIn the above, the device enters the multitasking user interface selection mode as indicated by replacing web browsing user interface 502 with multitasking user interface 506 in FIG. 23T.

10A-10H illustrate a flow diagram of a method 1000 of navigating between user interfaces, according to some embodiments. Method 1000 is performed at an electronic device having a display and a touch-sensitive surface, such as device 300 of FIG. 3 or portable multifunction device 100 of FIG. 1A. 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 the track pad 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 for managing, playing back, and/or streaming (e.g., from an external server) audio and/or visual files, the electronic device in communication with a remote control and a display (e.g., Apple TV from Apple inc. of cupertino, california). Some of the operations in method 1000 are optionally combined, and/or the order of some of the operations is optionally changed.

As described below, the method 1000 provides an intuitive way for navigating between user interfaces. The method reduces the number, extent and/or nature of inputs from a user while navigating between user interfaces, thereby creating a more efficient human-machine interface. For battery operated electronic devices, enabling a user 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 the display. Such as a user interface to open an application (e.g., user interface 502 for a web browsing application in fig. 5A-5B, 6A-6B, 6D, 6M, 6O, 6S-6T, 7A-7B, and 7O, user interface 616 for a web browsing application in fig. 6P and 6U, user interface 507 for a messaging application in fig. 5CC, 6Q, 7F, 7J-7L, 8D, 8J, 9F, and 9H, or user interface 526 for an image management application in fig. 8R). The first user interface corresponds to a first user interface representation of the plurality of user interface representations. For example, as described further below, the user interface representations correspond in some embodiments to a user interface of an open application, currently and previously viewed user interfaces of a single application (e.g., an open user interface for a web browsing application, each displaying the same or different websites; 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 so forth.

While displaying the first user interface, the device detects (1004) a predetermined input. E.g., a double tap or double press on the "home" button on the device; or for an electronic device that includes one or more sensors to detect intensity of contacts with the touch-sensitive display, a deep press on a predetermined area (e.g., upper left corner) of the first user interface; a deep press with a 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 a left edge of a touch-sensitive surface (e.g., a touch-sensitive display or touch-sensitive track pad separate from the display), in a predefined area adjacent to an edge (e.g., left edge) of the touch-sensitive surface (e.g., a touch-sensitive display). Such as a deep press (e.g., deep press 504 in fig. 504, 608 in fig. 6H, 612 in fig. 6M, and 806 in fig. 8K) on a bezel or a predetermined region of a bezel, such as a bezel adjacent to a left edge of the touch-sensitive surface.

In response (1005) to detecting the predetermined input: the device enters (1006) a user interface selection mode and displays (1008) a plurality of user interface representations in the stack, wherein at least a portion of the first user interface representation is visible and at least a portion of the 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 upon detection of the initiation input) and 510 (corresponding to user interface 507 of the messaging application) in fig. 5C and 5D.

In some embodiments, the representation of the user interface displayed on the screen immediately prior to entering the user interface selection mode is displayed on top of the heap, or as a first representation corresponding to an open application (e.g., when the home screen or one or more representations of transient applications are also displayed when entering the user interface selection mode). For example, in fig. 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 the user interface displayed on the screen immediately prior to entering the user interface selection mode is displayed beneath at least a second user interface representation (e.g., a representation of the user interface for display immediately prior to display of the user interface displayed when the user interface selection mode was initiated). For example, in fig. 5D, a user interface representation 508 (corresponding to the user interface 502 displayed when the deep press 504 is detected) is displayed below the 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 of the plurality of user interface representations (e.g., as shown in fig. 5D, the representation of the user interface displayed when the user interface selection mode is initiated is displayed as the 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 a user interface selection mode and displays a stack in which at least a portion of the first user interface representation is visible and at least a portion of the second user interface representation is visible.

In some embodiments, at least a portion of the third user interface representation is visually displayed in response to detecting a predetermined input for entering the user interface selection mode. For example, in response to detecting deep press 504 in fig. 5B, multifunction device 100 displays user interface representations 508, 510, and 526 in fig. 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 under a first, second and optional third representation comprising visible information. For example, fig. 5E illustrates an indication 503 (e.g., an image of a representative edge or an actual edge of an additional user interface representation) below the third user interface representation 526 in fig. 5E and 5F.

In some embodiments, in response to (1005) detecting the predetermined input: the device stops displaying (1010) the status bar on the display. The status bar is displayed concurrently with the respective user interface prior to entering the user interface selection mode and displaying the heap. 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 the deep press 504 in fig. 5B, as shown in fig. 5E, the device enters a user interface selection mode (e.g., as indicated by displaying the stack in fig. 5E) that does not include display of the status bar 503 in the corresponding user interface 506. In some embodiments, as shown in FIG. 5C, a user interface (e.g., user interface 506) for a user interface selection mode includes a 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, and the like. 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 an indication that: the heap in the user interface selection mode is not the normal user interface for the application, but is a system user interface configured to navigate, select, and manage (e.g., close) open applications on the device. In some embodiments, tactile feedback is provided upon entering a 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 multiple user interfaces represent a pile of cards (or other objects) similar to the user interface representing open applications in z-layer 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 that the cards are stacked one on top of the other), representing currently and previously viewed user interfaces for a single application, representing messages in an email chain, representing different menu options in a menu hierarchy, and so forth. For example, fig. 5E and 5F illustrate a stack that includes representations 508, 510, and 526 of a user interface to open an application. In z-layer order, representation 508 is shown as a top card, representation 510 is a middle card, and representation 526 is a bottom card. In some embodiments, such as shown in FIG. 5E, the stack is displayed as a substantially two-dimensional representation (although in some embodiments there is still z-layer order of the cards). In some embodiments, the stack is displayed as a substantially three-dimensional representation, for example as shown in fig. 5F.

At least a first user interface representation (e.g., a card representing an application displayed immediately prior to displaying the heap in a user interface selection mode, such as a mode for selecting among open applications, a mode for selecting among user interfaces in a single open application, or a mode for selecting from 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 jump) disposed above the first user interface representation in the heap are visible on the display. First user interface representation 510 is displayed below second user interface representation 508, for example, in fig. 5E-5F.

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). For example, second user interface 508 is offset to the right of the center of first user interface representation 510 in fig. 5E-5F.

The second user interface representation partially exposes the first user interface representation. In some embodiments, the representations in the stack are partially unrolled in one direction on the display (e.g., to the right as shown in fig. 5E-5F). 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 (e.g., 2, 3, 4, or 5 representations) in the heap is visible, while the remaining representations in the heap are off-screen or under representations that include visible information. In some embodiments, the representations underlying the representations that include the visible information are closely stacked together such that no information is displayed for the representations. In some embodiments, the representations underlying the representations that include the visual information are style representations, such as generic edges 503 only of these representations, as shown in fig. 5E-5F.

In some embodiments, the respective user interface representation has a corresponding location in the heap (1014). For example, as shown in fig. 5P, user interface representation 508 has a corresponding first location in the heap, user interface representation 510 has a corresponding second location in the heap, and user interface representation 526 has a corresponding third location in the heap.

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

For example, in some embodiments, upon entering the application selection mode, the user interface representation heap represents opening the application heap, the user interface representations below correspond to open applications that have not been viewed for a longer period of time, and the user interface representations for those applications are applied with more obfuscation than the user interface representations of open applications that are viewed more recently. In some embodiments, the user interface representation for the most recently viewed application is not obscured; the user interface representation for the next most recently viewed application is obscured by a first amount; the user interface representation for opening the application also earlier is obscured by a second amount greater than the first amount; and so on. For example, as shown in FIG. 5P, device 100 applies little or no blurring to user interface representation 508 because the card has a first relative z-position on top of the card that is simultaneously visible on touch screen 112. Device 100 applies a moderate blur to user interface representation 510 because the card has a second relative z-position in the middle of the card that is simultaneously visible on touch screen 112. Device 100 applies a large amount of ambiguity to user interface representation 526 because the card has a third relative z-position of the bottom of the card that is simultaneously visible on touch screen 112.

In some embodiments, the respective user interface representation has a corresponding simulated absolute z-position in the stack. For a user interface representation visible on the display, the device applies (1020) a blur level to the user interface representation according to a corresponding simulated absolute z-position of the user interface representation in the z-dimension.

For example, in some embodiments, 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, the 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 blur level 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 user interface representation stack moves in the x-direction on a concave incremental x-z curve, and the gap in the z-direction between each pair of adjacent user interface representations is maintained at a constant value during movement of the user interface representation 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 in fig. 5C associated with user interface representation 508 and title bar 520 in fig. 5D associated with user interface representation 510) having respective title content (e.g., a title area including an icon (e.g., icon 516 in fig. 5C and title 518 in fig. 5D) and a name of an application represented by the user interface representation (or a name of a web page, menu, etc., such as "Safari" 514 in fig. 5C and "message" 520 in fig. 5D)). In some embodiments, for a currently visible user interface representation 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 fig. 5 DD), the device applies (1022) a visible effect (e.g., a blur, fade, and/or clip as shown in fig. 5 DD) to at least a first portion of the title content of the user interface representation (e.g., fading of only the title text portion of the title content, e.g., "photo" 532 in fig. 5DD, or fading of both the title text and the icon in the title content, e.g., both "photo" 532 and icon 528 in fig. 5 DD).

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

In some embodiments, the heap includes (1026) user interface representations for the home screen (e.g., representations of any of one or more user interfaces accessible immediately after device startup, such as a notification center, a search UI, or a dashboard 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., representations of a user interface for an incoming or ongoing phone or IP call session (e.g., user interface representation 554 of user interface 556 for an incoming phone call in fig. 5W), a user interface showing hand-over of one or more application sessions from different devices, a user interface for a recommendation application, a user interface for a print session, etc.), and one or more open application user interface representations (e.g., representations just prior to entering a user interface selection mode) Representations of previously viewed current applications, prior applications prior to the current application, and other earlier opened applications (e.g., user interface representations 508, 510, and 526 in fig. 5E-5F)).

As used in this specification and claims, the term "open an application" refers to a software application having state information maintained (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:

active applications that are currently displayed on display 112 (or the corresponding application view currently displayed on the display);

a background application (or background process) that is not currently displayed on the display 112, but one or more application processes (e.g., instructions) for the corresponding application are being processed (i.e., running) by the one or more processors 120;

a suspended application that is not currently running and that is stored in volatile memory (e.g., DRAM, SRAM, DDR RAM of memory 102 or other volatile random access solid state memory device); and

dormant applications that are not running and are stored in non-volatile memory (e.g., one or more magnetic disk storage devices, optical disk storage devices, flash memory storage devices, or other non-volatile solid-state storage devices of the memory 102).

As used herein, the term "closed application" refers to a software application that has no maintained state information (e.g., the state information for the closed application is not stored in the memory of the device). Thus, closing an application includes stopping and/or removing application processing for the application and removing state information for the application from the memory of the device. Generally, opening the second application while in the first application does not close the first application. While the second application is displayed and the first application is stopped from being displayed, the first application, which was active at the time of display, may become a background application, a suspended application, or a dormant application, but the first application is still an open application, with its state information being maintained by the device.

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

In some embodiments, the transient application user interface representations include (1028) a phone interface representation for an active call or a missed call, a continuity interface representation for a suggested application, a continuity interface representation for a hand-off 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 on the touch-sensitive surface at a location corresponding to a location of the first user interface representation on the display (e.g., device 100 detecting a drag gesture that includes contact 530 and movement 532 on touch-screen 112 in fig. 5G at a location corresponding to 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 moving from left to right across touch-screen 112 in fig. 5G-5I).

While the first contact is at a location on the touch-sensitive surface that corresponds to a location of the first user interface representation on the display and moving (1032) across the touch-sensitive surface in a direction that corresponds to a first direction on the display: in accordance with the speed of the first contact on the touch-sensitive surface, the device moves (1034) a first user interface representation (e.g., user interface representation 510 in fig. 5G and 5R) in a first direction on the display at a first speed. For example, on a touch-sensitive display (e.g., touch screen 112), the card or other representation below the finger contact moves at the same speed as the finger contact (e.g., user interface representation 510 moves at the same speed as contact 530 in FIGS. 5G-5I and user interface representation 510 moves at the same speed as contact 556 in FIGS. 5R-5 as shown by the constant positional relationship between the display of the user interface representation and the contact on touch screen 112). On a display coupled to the track pad, a card or other representation of 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 a 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 differentiator that separates an on-screen object (e.g., user interface representation) from its peer-to-peer object that is not focused upon.

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 contact. In some embodiments, this movement of the first user interface representation produces the visual effect that the finger contact is capturing 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 produces the following visual effect: as the second user interface representation moves in the first direction toward an edge of the display, an increasingly larger portion of the first user interface representation emerges from beneath the second user interface representation. For example, as second user interface representation 508 is moved on the display to the right at a greater speed than first user interface representation 510, as shown in FIGS. 5G-5H, more user interface representations 510 appear when displayed at location 510-b than when displayed at location 510-a before moving to the right. In combination, the 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 heap includes at least a third user interface representation (e.g., user interface representation 526 in FIGS. 5E-5F) disposed below the first user interface representation. The first user interface representation is offset in a first direction from the third user interface representation (e.g., offset to the right of user interface representation 526 in fig. 5E-5F from user interface 510). The first user interface representation partially exposes the third user interface representation. While the 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 is moving across the touch-sensitive surface in a direction that corresponds to the first direction on the display: the device moves (1038) a 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.

The third user interface representation, e.g., below the first user interface representation (e.g., the card under 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, fig. 5O illustrates representative velocities of user interface representations 508 (e.g., second user interface representation), 510 (e.g., first user interface representation), and 526 (e.g., third user interface representation) relative to movement 532 of contact 530 in fig. 5G-5I.

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

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 incremental x-z curve, wherein the z-spacing between adjacent cards is maintained as the cards move along the x-direction. Since the slope of the curve decreases with increasing x-position, the cards move at higher and 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, when moving a third user interface representation disposed below the first user interface representation in the first direction at a third speed (1046) (e.g., moving user interface representation 526 to the right on touch screen 112 at a relative speed that is less than the speed at which user interface 510 travels to the right in fig. 5G-5I (e.g., as shown in fig. 5O)): the device renders (1048) an increasingly larger portion of the fourth user interface representation disposed below the third user interface representation in the pile on the display (e.g., gradually rendering the user interface 534 from behind the user interface representation 526 in fig. 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 superior user interface representation moves in the first direction, one or more user interface representations in the heap disposed below the fourth user interface representation (e.g., as user interface representations 540 in fig. 5I and 5T) are also presented in this manner.

In some embodiments, after detecting the first drag gesture (e.g., a drag gesture including contact 530 and movement 532 in fig. 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 (e.g., to the left) on the display opposite to the first direction (e.g., to the right) on the display. For example, in fig. 5L-5N, device 100 detects a drag gesture that includes a contact 546 and a movement 548 originating from a location on the display that corresponds to user interface representation 510 and continuing 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 intermediate lifting of the first contact. In some embodiments, as in the series of fig. 5J; 5L-5N, the first contact is lifted after the first drag gesture, and a second drag gesture is made with the second contact after the second contact is touched down on the touch-sensitive surface.

While the second contact is at a location on the touch-sensitive surface that corresponds to the first user interface representation on the display and the second contact is moving (1054) across the touch-sensitive surface in a direction that corresponds to a second direction on the display that is opposite the first direction on the display: in accordance with the speed 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 fig. 5L-5N) in a second direction on the display at a new first speed (e.g., the card or other representation below the finger contact moves on the touch-sensitive display at the same speed as the finger contact). The device also moves (1058) a second user interface representation (e.g., user interface representation 508 in fig. 5L-5N) disposed above the first user interface representation in a second direction at a new second speed that is greater than the new first speed. The device also moves (1060) a third user interface representation (e.g., user interface representation 526 in fig. 5L-5N) disposed below the first user interface representation in the second direction at a new third speed that is less than the new first speed.

In some embodiments, the device detects (1062) that the second user interface representation has moved between the first user interface representation and a location on the display that corresponds to a location of the second contact on the touch-sensitive surface when moving the second user interface representation in the second direction faster than moving the first user interface representation in the second direction. For example, on the touch-sensitive display, it is detected that a portion of the second contact or a representative point (e.g., centroid) of the second contact is touching the second user interface representation, but not the first user interface representation (e.g., centroid of contact 546 touches user interface representation 508 but not user interface representation 510 in location 546-f in fig. 5N).

In response to detecting that the second user interface representation has moved between the first user interface representation and a location on the display that corresponds to a 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 according to the current speed of the second contact. For example, on the touch-sensitive display, the second user interface representation (e.g., user interface representation 508 in FIG. 5N) has caught up with the finger movement and started moving at the same speed as the second finger contact, rather than 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 when position 508-f in FIG. 5O is reached).

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

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

In some embodiments, the difference between the modified second velocity and the modified first velocity maintains (1074) a first constant z-position difference between the second user interface representation and the first user interface representation, while the difference between the modified first velocity and the modified third velocity maintains a second constant z-position difference between the first user interface representation and the third user interface representation, wherein 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, a ratio between the modified second speed and the modified first speed is equal to a ratio between the modified first speed and the modified third speed (1078).

In some embodiments, the device detects (1080) activation of a transient application at the device while displaying at least a first user interface representation and a second user interface representation above the first user interface representation in the heap. For example, as shown in fig. 5U-5V, upon displaying user interface representations 508, 510, 526, and 534, device 100 detects an incoming telephone call, thereby activating a telephony 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 a phone application is inserted between user interface representations 510 and 526 in fig. 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 is moved to the right, and the user interface representation of the transient application occupies a place before the second user interface representation (e.g., in fig. 5V-5W, user interface representations 510 and 508 are moved to the right to make room for inserting user representation 554 into the heap).

In response to detecting a deletion input (1086) involving the first user interface representation: the device removes (1088) the first user interface representation from the first location in the stack (e.g., removes user interface 510 from the stack in fig. 5X-5Z). The device also moves (1090) a respective user interface representation disposed immediately below the first user interface representation into a first position in the stack (e.g., in fig. 5Z-5AA, user interface representation 526 moves up the stack to occupy the position vacated by user interface representation 510). In some embodiments, in response to detecting a deletion input involving the first user interface representation, an application corresponding to the first user interface representation is closed.

In some embodiments, after detecting the 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 fig. 5 BB). While displaying at least two of the plurality of user interface representations in the pile, 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 representations) that relates to one of the at least two user interface representations in the pile. For example, in FIG. 5BB, device 100 detects a tap gesture that includes contact 564 at a location on touch screen 112 that corresponds to the display of user interface representation 510.

In response to detecting the selection input (1093): the device stops displaying (1094) the heap 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 while any user interfaces corresponding to other user interface representations in the heap are not displayed. In some embodiments, the display of the user interface corresponding to the selected user interface representation replaces the display of the heap. 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 the user interface selection mode and displays user interface 507 on touch screen 112.

In some embodiments, while at least the first user interface representation and a second user interface representation disposed above the first user interface representation in the stack are stationary on the display, the device detects (1096) a first tap gesture by a second contact on the touch-sensitive surface at a location corresponding 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 corresponding to a 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 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 that detects the second contact based on whether a location on the touch-sensitive surface that corresponds to the first user interface representation or the second user interface representation on the display corresponds to (e.g., user interface representation 510 travels farther 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 involved 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 involved 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 indirectly pushes the top card to the right).

It should be understood that the particular order in which the operations in fig. 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. 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 1100, 1200, 1300, 1400, 1500, 2400, and 2500) also apply in a similar manner to method 1000 described above with respect to fig. 10A-10H. Contacts, gestures, user interface objects, focus selectors, and animations, such as those described above with reference to method 1000, optionally have one or more of the characteristics of contacts, gestures, user interface objects, focus selectors, and animations described herein with reference to other methods (e.g., methods 1100, 1200, 1300, 1400, 1500, 2400, and 2500) described herein. For the sake of brevity, these details are not repeated here.

11A-11E illustrate a flow diagram of a method 1100 of navigating between user interfaces, according to some embodiments. Method 1100 is performed at an electronic device (e.g., device 300 of FIG. 3 or portable multifunction device 100 of FIG. 1A) having a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the 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 the track pad 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 for managing, playing back, and/or streaming (e.g., from an external server) audio and/or visual files, the electronic device in communication with a remote control and a display (e.g., Apple TV from Apple inc. of cupertino, california). Some of the operations in method 1100 are optionally combined, and/or the order of some of the operations is optionally changed.

As described below, the method 1100 provides an intuitive way for navigating between user interfaces. The method reduces the cognitive burden on the user when navigating between user interfaces, thereby creating a more efficient human-machine interface. For battery operated electronic devices, enabling a user 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 a user interface of a currently open application. In some embodiments, the first user interface is a current user interface of the application, preceded by a sequence of previous user interfaces for the application accessible through 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 through 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 through the first contact begins at a location on the touch-sensitive surface that corresponds to a 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 input via the first contact, the device displays (1106) a first user interface representation and at least a second user interface representation (e.g., user interface representations 508 and 510 in FIG. 6C) on the display.

In some embodiments, the first contact is determined to be atHaving a characteristic intensity below a predetermined intensity threshold during the input, the device displays (1108) a first user interface representation for the first user interface and a second user interface representation at least for the second user interface on the display, wherein the first user interface representation is displayed over the second user interface representation and the second user interface representation is partially exposed. Such as in fig. 6B-6C, in determining that the intensity of contact 602 has not reached the deep press Intensity Threshold (IT)_D) User interface representation 508 is displayed over user interface representation 510 in fig. 6C. In some embodiments, a first user interface representation and a second user interface representation are displayed in a heap.

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

In some embodiments, the display of the heap replaces the display of the first user interface on the display. For example, user interface 506, including the heap in fig. 6H, replaces the display of user interface 507.

In some embodiments, the stack of user interface representations is progressively 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 to the maximum intensity in FIG. 6L, the user interface representations in the stack are unrolled as shown by moving user interface representation 510 out of position 510-a in FIG. 6J, through position 510-b in FIG. 6K, to position 510-c in FIG. 6L, which is almost completely away from touch screen 112.

In some embodiments, the heap is visualized in a "glance" mode before the intensity reaches a predetermined threshold intensity, and the contact intensity is reduced during the "glance" mode so that the previously dilated heap is retracted. In some embodiments, a fast deep press input with an intensity that crosses a predetermined threshold intensity causes an immediate display of the heap, skipping a glance mode.

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

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

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

In response to detecting termination of the input through the first contact (618): in accordance with a determination that the first contact has a predetermined intensity threshold (e.g., a deep press Intensity Threshold (IT) during the input_D) A characteristic intensity below (e.g., a representative intensity such as a maximum intensity) and the first contact moves in a direction across the touch-sensitive surface that corresponds to a predefined direction on the display during the input (e.g., to the right in a drag or swipe gesture; or the contact moves to a position on the touch-sensitive surface above a second user interface representation in the stack on the display Corresponding location), the device displays (1120) a second user interface corresponding to the second user interface representation. For example, in the series of FIGS. 6A, 6E-6G, the device 100 determines that the intensity of the contact 604 has not reached a predetermined deep press Intensity Threshold (IT)_D) And the input includes movement of the contact 604 to the right. Thus, upon detecting that the contact 604 is lifted, the device 100 displays, as shown in fig. 6G, a user interface 507 corresponding to the second user interface representation 510 during the glance gesture.

In some embodiments, the second user interface is displayed while other user interfaces corresponding to the plurality of user interface representations in the stack are not displayed. In some embodiments, the display of the second user interface replaces the display of the heap on the display. In some embodiments, a swipe gesture following a light press produces a "glance" that includes a display of a representation of a prior user interface followed by a display of the prior user interface. In some embodiments, the swipe gesture that repeatedly follows a light press enables the user to quickly swap between the current view and the immediately preceding view (e.g., after swapping from the first user interface 502 to the second interface 507 in fig. 6G, the user performs the same light press input and movement in fig. 6Q-6S to swap back to the first user interface 502 as shown in fig. 6S).

The method also includes determining that the first contact has a predetermined intensity threshold (e.g., a deep press Intensity Threshold (IT)) during the input in accordance with the determination_D) A characteristic intensity (e.g., a maximum intensity) below and the first contact has not moved in a direction across the touch-sensitive surface that corresponds to a predefined direction on the display during the input (e.g., the first contact is stationary during the input or moved less than a threshold amount during the input), the device redisplays (1122) the first user interface. For example, in FIGS. 6A-6D, device 100 determines that contact 602 has not reached the deep press Intensity Threshold (IT)_D) And is stationary. Thus, upon detecting that the contact 602 is lifted, the device 100 redisplays the first user interface 502 as shown in fig. 6D.

In some embodiments, the first user interface is displayed while other user interfaces corresponding to the plurality of user interface representations in the heap are not displayed. In some embodiments, the display of the first user interface replaces the display of the heap on the display. In some embodiments, a stationary light press produces a "glance" that includes the display of a representation of a prior user interface followed by a redisplay of the current user interface. In some embodiments, the intensity is fully released during the "glance" without additional movement of the first contact, so that the display returns to showing the first user interface.

In some embodiments, in response to detecting termination of the input by the first contact, in accordance with a determination that the first contact reached a predetermined intensity threshold (e.g., a deep press Intensity Threshold (IT) during the input_D) Above) the intensity, the device remains (1124) in the user interface selection mode and maintains the display of the heap. For example, in FIGS. 6H-6I, device 100 determines that contact 608 reached a deep press Intensity Threshold (IT)_D). Thus, upon detecting that the contact 608 is lifted, the device 100 maintains the display of the stack as shown in fig. 6I.

In some embodiments, a deep press having an intensity that crosses a predetermined threshold intensity produces a display of a stack maintained at the end of the deep press input (e.g., as shown in fig. 6H-6I). In some embodiments, the heap includes at least a user interface representation of all open applications, and the user may navigate through the representation and select a desired application using subsequent input (e.g., a drag gesture to the left or right 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 through a second contact (e.g., contact 626 in fig. 6Q) on the touch-sensitive surface. Upon detecting a second input via a second contact, the device redisplays (1128) the first user interface representation and at least a second user interface representation on the display (e.g., as shown in fig. 6R, where user interface representation 510 is now displayed over user interface representation 508).

In some embodiments, upon 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., contact 626 lift as shown in fig. 6S). In response toDetecting termination of the second input by the second contact (1132): in accordance with a determination that the second contact has a predetermined intensity threshold (e.g., a deep press Intensity Threshold (IT)) during the second input_D) ) and the second contact is moved in a direction across the touch-sensitive surface corresponding to the predefined direction on the display during the second input, the device redisplays (1134) the first user interface (e.g., swap back from the second user interface to the first user interface as shown in fig. 6S).

In response to detecting termination (1132) of the second input by the second contact: in accordance with a determination that the second contact has a predetermined intensity threshold (e.g., a deep press Intensity Threshold (IT)) during the second input_D) And the second contact does not move in a direction across the touch-sensitive surface that corresponds to a predefined direction on the display (e.g., the contact is stationary) during the second input, the device redisplays (1136) the second user interface (e.g., the user merely glimpses back at the representation of the first user interface without swapping 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 fig. 6A-6D, such as a left edge of the display or bezel). Upon displaying the first user interface on the display after detecting termination of the input through the first contact, the device detects (1138) a second input through a second contact on the touch-sensitive surface, wherein the second input through 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 navigation hierarchy). The input via 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 a first edge of the touch-sensitive surface. In response to detecting an edge swipe gesture originating from a first edge of the touch-sensitive surface, the device displays (1144) a view (e.g., a previously viewed web page) in a view hierarchy of the first application that precedes the first user interface.

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

In some embodiments, while displaying the first user interface of the 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 fling gesture through the first contact, in accordance with a determination that the fling gesture through the first contact occurs within an area of the touch-sensitive surface that corresponds to a first predefined area on or near the display, an application selection mode is entered. In accordance with a determination that the drag gesture by the first contact occurs within an area of the touch-sensitive surface that corresponds to a second predefined area on or near the display that is different from the first predefined area, displaying, on the display, a second user interface of the first application that is displayed just prior to displaying the first user interface of the first application.

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 the area above the first predefined area. In some embodiments, a drag gesture by the first contact occurring within a region of the touch-sensitive surface corresponding to the first predefined region or within a region of the touch-sensitive surface corresponding to the second predefined region is also required to begin (in order to enter an application selection mode or display a second user interface) on or in a region of the touch-sensitive surface corresponding to a predefined region adjacent to a left edge of the display.

In some embodiments, in accordance with a determination that the drag gesture by the first contact begins in an area of the touch-sensitive surface that corresponds to a first predefined area on the display, the device displays, on the display, a plurality of user interface representations for a corresponding plurality of 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 that is different from the first application. In some embodiments, the display of the heap replaces the display of the first user interface of the first application on the display. In some embodiments, multiple user interface representations are displayed in the heap. In some embodiments, the first user interface representation is displayed over and partially exposes the second user interface representation.

In some embodiments, upon detecting termination of the input by the first contact, the device detects (1146) a drag gesture by a second contact on the touch-sensitive surface at a location corresponding to a second user interface representation on the display when the stack is displayed in the user interface selection mode in accordance with a determination that the first contact reaches an intensity above a predetermined intensity threshold during the input (e.g., as shown in fig. 6H-6I), wherein 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 fig. 5G-5I).

In response to detecting a fling gesture (1148) with a second contact on the touch-sensitive surface at a location corresponding to a second user interface representation on the display, wherein the fling 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 FIG. 5G to location 510-c in FIG. 5I); and the device moves (1152) the first user interface representation disposed above the second user interface representation in a first direction at a first speed that is greater than the second speed (e.g., user interface representation 508 moves from position 508-a to position 508-b in fig. 5G and off-screen in fig. 5I). In some embodiments, once the user interface selection mode is activated, navigation may be performed according to the process described above with respect to method 1000.

It should be understood that the particular order in which the operations in fig. 11A-11E are described is merely exemplary and is not intended to indicate that the order described 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, 1200, 1300, 1400, 1500, 2400, and 2500) also apply in a similar manner to method 1100 described above with respect to fig. 11A-11E. Contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations, such as those described above with reference to method 1100, optionally have one or more of the characteristics of contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described herein with respect to other methods described herein, such as methods 1000, 1200, 1300, 1400, 1500, 2400, and 2500. For the sake of brevity, these details are not repeated here.

12A-12E illustrate a flow diagram of a method 1200 of navigating between user interfaces, according to some embodiments. Method 1200 is performed at an electronic device (e.g., device 300 of FIG. 3 or portable multifunction device 100 of FIG. 1A) having a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the 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 the track pad 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 for managing, playing back, and/or streaming (e.g., from an external server) audio and/or visual files, the electronic device in communication with a remote control and a display (e.g., Apple TV from Apple inc. of cupertino, california). Some of the operations in method 1200 are optionally combined, and/or the order of some of the operations is optionally changed.

As described below, the method 1200 provides an intuitive way for navigating between user interfaces. The method reduces the cognitive burden on the user when navigating between user interfaces, thereby creating a more efficient human-machine interface. For battery operated electronic devices, enabling a user 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 the display. In some embodiments, the first user interface is a user interface of a currently open application. In some embodiments, the first user interface is a current user interface of the application and is displayed prior to display of the first user interface is a sequential display of a previous user interface (e.g., a previous web page) of the application. In some embodiments, the previous user interface is accessible by activating a "back" button (e.g., back button 614 in fig. 7A) provided on the user interface of the application.

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

In response to detecting an input through a first contact that includes a period of increased 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 just prior to 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 fig. 7C).

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

In some embodiments, the user interface enters a "glance" mode in response to the tap, and as the intensity of the contact increases or decreases after the "glance" mode is activated, the amount of change in the user interface representation for the previously displayed application is visualized from below the representation of the user interface for the current application (e.g., as the intensity of the contact 702 increases from fig. 7C to fig. 7D, user interface representation 510 is visualized more from below user interface representation 508).

In some embodiments, the first contact has a period of varying intensity that includes both a rising and falling intensity prior to the period of increasing intensity of the first contact (e.g., the intensity of contact 704 increases from fig. 7G to fig. 7H, decreases from fig. 7H to fig. 7I, and then increases again from fig. 7I to fig. 7J). In accordance with the rise and fall of 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 appears behind the first user interface representation (e.g., more user interface representation 508 appears as the intensity of contact 704 increases from FIG. 7G to FIG. 7H; less user interface representation 508 appears as the intensity of contact 704 decreases from FIG. 7H to FIG. 7I, and then more user interface representation 708 appears again as the intensity of contact 704 increases from FIG. 7I to FIG. 7J).

The method further includes while displaying the first user interface representation and the second user interface representation on the display, the device detecting (1210) that an intensity of the first contact satisfies one or more predetermined intensity criteria during the period of increased intensity of the first contact (e.g., the intensity of the first contact is at, for example, a deep press Intensity Threshold (IT) as shown in fig. 7E _D) Such as a predetermined threshold intensity or above).

In some embodiments, during the period of increased contact intensity of the first contact, and before the intensity of the first contact satisfies one or more predetermined intensity criteria, the device increases (1212), in accordance with the increase in intensity of the first contact, an area of the second user interface representation that emerges behind the first user interface representation. For example, user interface representation 510 appears more from below user interface representation 508 as the intensity of contact 702 increases from FIG. 7C to FIG. 7D. In some embodiments, the second user interface is displayed larger (e.g., as coming from behind the plane of the display toward the user) in response to an increasing intensity of the contact.

In some embodiments, increasing the area of the second user interface representation appearing behind the first user interface representation as a function of increasing intensity of the first contact includes displaying (1214) an animation that dynamically changes an amount of area of the second user interface representation appearing behind the first user interface representation based on changes in 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 satisfies one or more predetermined intensity criteria. In some embodiments, the animation is a fluid animation that is updated as the intensity of the first contact changes to provide feedback to the user regarding the amount of intensity detected by the device (e.g., feedback regarding the amount of force applied by the user). In some embodiments, the animation is updated smoothly and quickly to produce the following appearance for the user: the user interface responds to changes in the force applied to the touch-sensitive surface in real-time (e.g., the animation is perceptually transient for the user to provide immediate feedback to the user and to 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 having different or changing intensities).

In some embodiments, increasing the area of the second user interface representation that emerges from behind the first user interface representation in accordance with the increase in intensity of the first contact includes moving (1216) the first user interface representation in a first direction to increase a lateral positional 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 FIG. 7G to FIG. 7H, user interface representation 510 slides rightward from location 510-a in FIG. 7G to location 510-b in FIG. 7H, 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 or adjacent to the left edge of the display, the first user interface representation moves to the left to more visualize the second user interface representation.

In some embodiments, increasing the area of the second user interface representation that emerges behind the first user interface representation as a function of the increase in 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 as the first user interface representation is moved in the first direction to increase the lateral positional offset on the display between the first user interface representation and the second user interface representation (e.g., as the intensity of the contact 702 increases from fig. 7C to fig. 7D, the first user interface representation 508 appears to move away from the surface of the touch-screen 112 and the 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 z-layer order.

In some embodiments, the device detects (1220) that the intensity of the first contact satisfies one or more predetermined intensity criteria (e.g., a deep press Intensity Threshold (IT) as shown in fig. 7E_D)). In response to detecting that the intensity of the first contact satisfies one or more predetermined intensity criteria, the device displays (1222) an animation that shows 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 out behind user interface representation 508 as shown in fig. 7E, and then the animation transitions the display to user interface 507 in fig. 7F).

In some embodiments, the device changes (1224) a blur effect level 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 fig. 7C-7E, during the animation, the first user interface representation becomes more blurred, and/or the second user interface representation becomes less blurred, where user interface representation 510 begins to blur in fig. 7C and becomes in focus as it appears to move toward the surface of touch-screen 112. In contrast, user interface 508 is initially in focus in FIG. 7C and becomes blurred as it appears to move away from the surface of touch screen 112.

The method further includes, in response to detecting that the intensity of the first contact satisfies one or more predetermined intensity criteria (1226): the device ceases to display (1228) the first user interface representation and the second user interface representation on the display; and the device displays (1230) a second user interface (e.g., without displaying the first user interface) on the display. In some embodiments, a "pop-up" to display the second user interface is followed by a "glance" when the contact intensity reaches or exceeds a predetermined deep-press threshold intensity. For example, when the intensity of contacts 702, 704, and 706 reaches the deep press Intensity Threshold (IT) in FIGS. 7F, 7J, and 7O, respectively_D) The second user interface represents "pop-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 increased intensity of the second contact (e.g., contact 706 with increased intensity in fig. 7L-7O).

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

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

In some embodiments, the user interface enters a "glance" mode in response to the tap, and as the intensity of the contact increases or decreases after the "glance" mode is activated, the amount of change in the user interface representation for the previously displayed application appears from below the representation of the user interface for the current application. User interface representation 508 appears more from behind user interface representation 510, e.g., in response to detecting contact 706 in fig. 7M-7N increasing in intensity.

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

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

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

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

In some embodiments, the user interface enters a "glance" mode in response to the tap, and as the intensity of the contact increases or decreases after the "glance" mode is activated, the amount of change in the user interface representation for the previously displayed application appears from below the representation of the user interface for the current application. User interface representation 508 appears more from behind user interface representation 510, e.g., in response to detecting contact 704 in fig. 7G-7H increasing in intensity.

While displaying the first user interface representation and the second user interface representation on the display, the device detects (1248) termination of the input through the second contact (e.g., detects lifting of the second contact (e.g., as in fig. 7K), or detects that the intensity of the second contact falls below a minimum intensity detection threshold (e.g., as in fig. 7J)), while the intensity of the second contact does not meet one or more predetermined intensity criteria.

In response to detecting termination of the input by the second contact while the intensity of the second contact does not meet one or more predetermined intensity criteria (1250): the device stops 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, the intensity at which the device 100 detects the contact 704 falls to a minimum intensity detection threshold (IT) ₀) Thereafter, and in response replaces the display of user interface 506 with second user interface 510 in FIG. 7J. In some embodiments, the "glance" stops and the second user interface is redisplayed when the input terminates and the contact intensity does not reach the predetermined deep-press threshold intensity.

It should be understood that the particular order in which the operations in fig. 12A-12E have been described is merely exemplary and is not intended to indicate that the order described 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, 1300, 1400, 1500, 2400, and 2500) also apply in a similar manner to method 1200 described above with respect to fig. 12A-12E. Contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations, such as those described above with reference to method 1200, optionally have one or more of the characteristics of contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described herein with reference to other methods (e.g., methods 1000, 1100, 1300, 1400, 1500, 2400, and 2500) described herein. For the sake of brevity, these details are not repeated here.

13A-13D illustrate a flow diagram of a method 1300 of navigating between user interfaces, according to some embodiments. Method 1300 is performed at an electronic device (e.g., device 300 of fig. 3 or portable multifunction device 100 of fig. 1A) having a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the 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 the track pad 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 for managing, playing back, and/or streaming (e.g., from an external server) audio and/or visual files, the electronic device in communication with a remote control and a display (e.g., Apple TV from Apple inc. of cupertino, california). Some of the operations in method 1300 may optionally be combined, and/or the order of some of the operations may optionally be changed.

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

The device displays (1302) multiple user interface representations in a heap on a display (e.g., in a user interface selection mode, a heap of z-layer order cards (or other objects) representing user interfaces that open applications, cards representing currently and previously viewed user interfaces for a single application, cards representing messages in an email chain, etc.) is displayed. At least the first user interface representation, the second user interface representation, and the 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 in a first direction from the second user interface representation (e.g., laterally offset to the right on the display), and the second user interface representation is partially exposed. The second user interface representation (e.g., user interface representation 510 in fig. 8A) is laterally offset (e.g., laterally offset to the right on the display) from the third user interface representation (e.g., user interface representation 526 in fig. 8A) in the first direction and partially exposes the third user interface representation. For example, in some embodiments, as shown in FIG. 8A, the heap is displayed while the display is in the user interface selection mode.

In some embodiments, prior to displaying the stack on the display (1304): the device displays (1306) a first user interface (e.g., user interface 502 of a web browsing application as shown in fig. 7A) on the display that corresponds to the first user interface representation. 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 to detect intensity of contacts with a touch-sensitive display: a deep press on a predetermined area (e.g., upper left corner) of the first user interface; a deep press with a 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 a left edge of the touch-sensitive display, in a predefined area adjacent to the left edge of the touch-sensitive display, on a 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 the predetermined input (1310): the device enters (1313) a user interface selection mode; and the device displays (1312) a heap that includes a plurality of user interface representations (e.g., display of user interface 506 in a user interface selection mode, including display of the heap in fig. 9A).

In some embodiments, the stack is displayed (1316) in response to detecting an input through 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., the contact 806 is detected at a location 806-a that does not correspond to the display of the user interface representation 510 on the touch-screen 112 in fig. 8J-8K). Prior to detecting the increase in intensity of the first contact, the first contact is moved on the touch-sensitive surface from the first location to a location corresponding to the second user interface representation on the display (e.g., contact 806-a is moved from location 806-a to location 806-b in FIGS. 8K-8L). The first contact is continuously detected on the device, for example, from before a time at which the second user interface representation is displayed, at least until a time at which an increased 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) input through a first contact on the touch-sensitive surface at a location corresponding to the second user interface representation on the display (e.g., contact 802 at a location corresponding to display of user interface representation 510 on touch-screen 112 in fig. 8A). In some embodiments, the device detects a press by a finger contact at a location on the touch-sensitive surface that corresponds 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 fig. 8A to fig. 8B, decreases from fig. 8B to fig. 8C, and then increases again from fig. 8C to fig. 8D).

In some embodiments, the input by the first contact includes a period of decreased intensity of the first contact after a period of increased intensity of the first contact. During the period of reduced intensity of the first contact, the device reduces (1320) an area of the second user interface representation exposed behind the first user interface representation by reducing a 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 FIG. 8B to FIG. 8C, user interface representation 508 begins to slide back over user interface representation 510, moving from position 508-B in FIG. 8B to position 508-C in FIG. 8C.

In some embodiments, after more of the second user interface representation is rendered in response to detecting an increase in the intensity of the contact, the device renders less of the second user interface representation in response to detecting a decrease in the intensity of the contact (e.g., user interface representation 508 slides to the right of user interface representation 510 moving from location 508-a in fig. 8A to location 508-B in fig. 8B in response to increasing the intensity of contact 802 from fig. 8A to fig. 8B). In some embodiments, an animation is displayed to show 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 first contact (e.g., movement of user interface representation 508 in fig. 8A-8C is directly manipulated by a user to increase or decrease the intensity of contact 802).

In accordance with 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 increases (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 an increase in intensity of contact 802 from fig. 8A to fig. 8B, user interface representation 508 slides to the right of user interface representation 510, moving from location 508-a in fig. 8A to location 508-B in fig. 8B and revealing more of user interface representation 810).

In some embodiments, the second user interface representation (e.g., user interface representation 510 in fig. 8A-8C) is positioned below the first user interface representation (e.g., user interface representation 508 in fig. 8A-8C) and above the third user interface representation (e.g., user interface representation 526 in fig. 8A-8C) in z-layer order, and the second user interface representation is more pronounced by a press of a contact at a location on the touch-sensitive surface that corresponds to an exposed portion of the second user interface representation. In some embodiments, to more visualize the second user interface representation, in response to detecting an increase in intensity of the contact at a location on the touch-sensitive surface that corresponds to the exposed portion of the second user interface representation, the first user interface representation moves to the right, thereby more "glancing" at the second user interface representation (e.g., user interface 508 moves from location 508-a in FIG. 8A to location 508-B in FIG. 8B in response to an increase in intensity of contact 802 to more visualize user interface representation 510)

In some embodiments, increasing the area of the second user interface representation exposed 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 more fully visualize user interface representation 510 in fig. 8A-8B.

In some embodiments, increasing the area of the second user interface representation exposed behind the first user interface representation includes moving (1326) the second user interface representation in a second direction opposite the first direction (e.g., moving the second user interface representation 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 more visualize the representations in fig. 8G-8H.

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

In response to detecting a drag gesture (1330) on the touch-sensitive surface in a direction corresponding to a second direction on the display by a second contact on the touch-sensitive surface at a location corresponding to the second user interface representation, the device: moving (1332) the second user interface representation in a second direction at a second speed on the display based on the speed of the second contact on the touch-sensitive surface; moving (1334) the first user interface representation in a second direction at a first speed greater than the second speed; moving (1336) the third user interface representation in the second direction at a third speed, which is lower than the second speed; and moving (1338) the fourth user interface representation in the second direction at a fourth speed 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 in the heap on top of the first user interface representation.

In some embodiments, the fourth user interface representation moves out of the display to the right in response to a prior drag gesture to the right. 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 causes the user interface representation 508 to come back into view on the display from the right, the drag gesture including a contact 546 and a movement 548 from position 546-c in FIG. 5L, through position 546-e in FIG. 5M, to position 546-f in FIG. 5N). In some embodiments, the fourth user interface representation is faster than any user interface representation below it in the relative z-position.

In some embodiments, the device detects (1340) that the intensity of the first contact at the location corresponding to the second user interface representation on the touch-sensitive surface satisfies 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 the location corresponding to the second user interface representation satisfies one or more predetermined intensity criteria (1342), the device: stopping displaying (1344) the stack; and displaying (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 (IT) at a location on touch screen 112 corresponding to the display of the user interface representation _D) Device 100 replaces the display of user interface 506 (corresponding to the user interface selection mode) with the display of user interface 507 (corresponding to user interface representation 510) in fig. 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 the display of the heap.

In some embodiments, in response to detecting that the intensity of the first contact on the touch-sensitive surface at the location corresponding to the second user interface representation satisfies 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 (IT) at a location on touch screen 112 corresponding to the display of the user interface representation_D) Device 100 displays an animation in which, as the device transitions to the display of user interface 507, first user interface representation 508 slides completely off of second user interface representation 510 to the right, second user interface 510 appears to be lifted from the heap (e.g., via position 510-b in FIG. 8E to position 510-C in FIG. 8F), and first user interface representation 508 is shuffled back into the heap beneath second user interface representation 510, as shown in the series of FIGS. 8C, 8E, and 8F.

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

In accordance with detecting an increase in 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) an area of the third user interface representation exposed from behind the second user interface representation by increasing a lateral offset between the second user interface representation and the third user interface representation (e.g., device 100 detects an increase in intensity of contact 806 from FIG. 8O to FIG. 8P, and in response moves user interface representations 510 and 508 to the right, from locations 510-a and 508-a in FIG. 8O to locations 510-h and 508-h in FIG. 8P, respectively, to more visualize user interface 526). In some embodiments, only 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 to make way to more visualize the selected user interface representation. For example, only user interface representation 510 will be moved in FIG. 8O to more visualize user interface representation 526 (e.g., by sliding further under user interface representation 508).

In some embodiments, as the user drags their finger over different representations in the stack, the stack expands to appear more of the representations below the user's finger. In some embodiments, the user may increase the intensity of the contact to glance at one representation, decrease the intensity (without lifting), move to the next representation, increase the intensity to glance at the next representation, decrease the intensity (without lifting), move to another representation, and so forth.

It should be understood that the particular order in which the operations in fig. 13A-13D have been described is merely exemplary and is not intended to indicate that the order described 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, 1400, 1500, 2400, and 2500) also apply in a similar manner to method 1300 described above with respect to fig. 13A-13D. Contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations, such as those described above with reference to method 1300, optionally have one or more of the characteristics of contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described herein with reference to other methods (e.g., methods 1000, 1100, 1200, 1400, 1500, 2400, and 2500) described herein. For the sake of brevity, these details are not repeated here.

14A-14C illustrate a flow diagram of a method 1400 of navigating between user interfaces, according to some embodiments. Method 1400 is performed at an electronic device (e.g., device 300 of fig. 3 or portable multifunction device 100 of fig. 1A) having a display, a touch-sensitive surface, and optionally one or more sensors for detecting intensity of contacts with the 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 the track pad 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, playback, and/or stream (e.g., from an external server) audio and/or visual files, the electronic device in communication with a remote control and a display (e.g., Apple TV from Apple inc. of cupertino, california). Some of the operations in the method 1400 are optionally combined, and/or the order of some of the operations is optionally changed.

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

The device displays (1402) multiple user interface representations in a heap on the display (e.g., in a user interface selection mode, a heap of z-layer order cards (or other objects) representing user interfaces to open applications, cards representing currently and previously viewed user interfaces for a single application, cards representing messages in an email chain, etc. is displayed). At least the first user interface representation, the second user interface representation, and the 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 in the first direction from the second user interface representation (e.g., laterally offset to the right on the display), and partially exposes the second user interface representation.

The device detects (1404) a fling gesture by a first contact moving across the touch-sensitive surface, wherein movement of the fling 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, the device renders (1406) the first user interface representation more on the display from behind the second user interface representation as the first contact moves over a location on the touch-sensitive surface that corresponds to the first user interface representation on the display. For example, as the contact 902 moves over the user interface representation 526, the user interface representations 510 and 508 move to the right to more visualize the user interface representation 526 in FIG. 9B.

In some embodiments, surfacing the first user interface representation more 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 a lateral offset between the first user interface representation and the second user interface representation).

In some embodiments, surfacing 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 the first direction (e.g., moving the first user interface representation left (with or without the second user interface representation moving simultaneously to the right) to increase a lateral offset between the first user interface representation and the second user interface representation on the display).

In some embodiments, during the drag gesture, while the first contact is moved (1412) from a first location on the touch-sensitive surface corresponding to the first user interface representation to a second location on the touch-sensitive surface corresponding to the second user interface representation (e.g., the contact 902 is moved from a location 902-a corresponding to the display of the user interface representation 526 in fig. 9B to a location 904 corresponding to the display of the user interface representation 510 in fig. 9C): the device renders (1414) the second user interface representation more behind the third user interface representation on the display and renders (1416) the first user interface representation less behind the second user interface representation on the display (e.g., in fig. 9D, user representation 510 moves to the left, thereby rendering its user interface representation more and overlaying user interface representation 526 more).

In some embodiments, the device detects (1418) the lift 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., the device 100 detects the lift of the contact 902 in fig. 9E). In response to detecting the lift of the first contact (1420): the device stops displaying (1422) the stack; and the device displays (1424) a user interface corresponding to the one of the plurality of user interface representations (e.g., device 100 replaces the display of user interface 506 in fig. 9E with the display of user interface 507 in fig. 9F).

For example, if a first contact in the drag gesture is lifted while over a location corresponding to the first user interface representation, the first user interface is displayed. The second user interface is displayed if the first contact in the drag gesture is lifted while over the location corresponding to the second user interface representation. More generally, if a first contact in a drag gesture lifts while over a location corresponding to a respective 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 heap.

In some embodiments in which the device has one or more sensors for detecting intensity of contacts with the touch-sensitive surface, the device detects (1426) that the intensity of the first contact satisfies 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) when 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.

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 plurality of user interface representations (e.g., device 100 replaces the display of user interface 506 in fig. 9G with the display of user interface 907 in fig. 9H).

For example, if a first contact in the drag gesture makes a deep press while over a location corresponding to the first user interface representation, the first user interface is displayed. If the first contact in the drag gesture makes a deep press while over a location corresponding to the second user interface representation, the second user interface is displayed. More generally, if a first contact in a drag gesture makes a deep press while over a location corresponding to a respective 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 heap.

It should be understood that the particular order in which the operations in diagram 1400 have been described is merely exemplary and is not intended to indicate that the order described 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, 1500, 2400, and 2500) also apply in a similar manner to method 1400 described above with respect to fig. 14A-14C. Contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations, such as described above with reference to method 1400, optionally have one or more of the characteristics of contacts, gestures, user interface objects, intensity thresholds, focus selectors, and animations described herein with reference to other methods described herein, such as methods 1000, 1100, 1200, 1300, 1500, 2400, and 2500. For the sake of brevity, these details are not repeated here.

FIG. 15 illustrates a flow diagram of a method 1500 for navigating between user interfaces, according to some embodiments. Method 1500 is performed at an electronic device (e.g., device 300 of fig. 3 or portable multifunction device 100 of fig. 1A) having a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the 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 the track pad 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 for managing, playing back, and/or streaming (e.g., from an external server) audio and/or visual files, the electronic device in communication with a remote control and a display (e.g., Apple TV from Apple inc. of cupertino, california). Some of the operations in method 1500 are optionally combined, and/or the order of some of the operations is optionally changed.

As described below, the method 1500 provides an intuitive way for navigating between user interfaces. The method reduces the cognitive burden on the user when navigating between user interfaces, thereby creating a more efficient human-machine interface. For battery operated electronic devices, enabling a user 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 6M including 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 the current user interface in the application with the display of the previous user interface displayed in the application. In some embodiments, the first user interface is a current user interface of the application, which is preceded by display of a previous sequence of user interfaces of the application. In some embodiments, a previous user interface sequence of the application is navigated in reverse temporal order by activating a back navigation control provided on the user interface.

In some embodiments, the user interfaces for the applications are arranged in a hierarchy, and 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 a display of a current user interface at a first level of the hierarchy with a 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 of the application, which is preceded by display of a sequence of previous user interfaces in the hierarchy. In some embodiments, a hierarchical sequence of a user interface for an application is navigated in reverse hierarchical order by activating a back navigation control. The hierarchical sequence (including multiple levels of mailboxes and inboxes) in the email application is navigated in reverse hierarchical order, for example, by activating a back navigation control provided on the user interface.

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

In response to detecting the gesture (1506) through the first contact on the touch-sensitive surface at the location corresponding to the back navigation control: in accordance with a determination 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 meets 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) the display of the first user interface of the first application with a display of a plurality of 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 fig. 6M-6N, device 100 determines that contact 612 includes an intensity that satisfies a 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, rather than requiring a deep press gesture to be made on the backward navigation control, the deep press gesture is made on or in a region of the touch-sensitive surface that corresponds to a region adjacent to a left edge of the display. In some embodiments, rather than requiring a deep press gesture to be made anywhere on the touch-sensitive surface on the region of the touch-sensitive surface that corresponds to the back navigation control, the deep press gesture is made. In some embodiments, the gesture through the first contact is made with a flat portion of the thumb.

In response to detecting the gesture (1506) through the first contact on the touch-sensitive surface at the location corresponding to the back navigation control: in accordance with a determination that the gesture by the first contact is a gesture (e.g., a tap gesture) having an intensity of the first contact that does not satisfy 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) the display of the first user interface of the first application with the 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 fig. 6O-6P, device 100 determines that contact 624 does not include an intensity that satisfies the deep press intensity threshold and, in response, displays user interface 616 that corresponds to the web browsing user interface displayed prior to 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 just prior to displaying the first user interface of the first application.

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

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 order described 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, 2400, and 2500) also apply in a similar manner to method 1500 described above with respect to fig. 15. Such as contacts, gestures, user interface objects, intensity thresholds, focus selectors, animations described above with reference to the methods, optionally have one or more of the characteristics of contacts, gestures, user interface objects, intensity thresholds, focus selectors, 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.

24A-24F illustrate a flow diagram of a method 2400 of navigating between user interfaces, according to some embodiments. Method 2400 is performed at an electronic device (e.g., device 300 of fig. 3 or portable multifunction device 100 of fig. 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 the track pad 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 for managing, playing back, and/or streaming (e.g., from an external server) audio and/or visual files, the electronic device in communication with a remote control and a display (e.g., Apple TV from Apple inc. of cupertino, california). Some of the operations in method 2400 are optionally combined, and/or the order of some of the operations is optionally changed.

As described below, the method 2400 provides an intuitive way for navigating between user interfaces. The method reduces the cognitive burden on the user when navigating between user interfaces, thereby creating a more efficient human-machine interface. For battery operated electronic devices, enabling a user 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 the application on the display. The device detects (2404) an edge input, including detecting a change in a characteristic intensity of a contact proximate to an edge of the touch-sensitive surface. In response to detecting the edge input: in accordance with a determination that the edge input satisfies the 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., performs the application-independent operation even when the application gesture criteria are simultaneously satisfied). The system gesture criteria include intensity criteria. In some embodiments, the characteristic intensity at the contact is at a first intensity threshold (e.g., a light press "IT)_L"threshold value") above. The system gesture criteria include a location criterion that is met when (a predetermined portion of) the contact meets an intensity criterion for the contact while within a first region relative to the touch-sensitive surface (e.g., a region that may or may not include a portion of the touch-sensitive surface). A first region relative to the touch-sensitive surface is determined based on one or more characteristics of the contact.

In some embodiments, changes in characteristic intensities of contacts proximate to an edge of the touch-sensitive surface are detected (2408) at locations corresponding to respective operations in the application.

In some embodiments, in response to detecting the edge input: in accordance with a determination 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, rather than performing an application-independent operation. In some embodiments, in accordance with a determination 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 criteria are met (2412) when: (ii) a characteristic intensity of a contact proximate to an edge of the touch-sensitive surface is above a first intensity threshold; and the (detected) characteristic intensity of the contact proximate 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 the multitasking UI without requiring movement of the contact.

In some embodiments, the first region relative to the touch-sensitive surface has (2414) a first boundary (e.g., a first size and location) when the contact proximate to the edge of the touch-sensitive surface has a first spatial property (e.g., a large oblong contact characteristic for a flat finger input), and a second boundary (e.g., a second size and/or location) different from the first boundary when the contact proximate to the edge of the touch-sensitive surface has a second spatial property (e.g., a small circular contact characteristic for a fingertip input). In some embodiments, the size and/or location of the region dynamically changes 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 the 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 the location of the contact for satisfying the location criterion purpose is determined based at least in part on the inferred second portion of the contact (e.g., the location of the second portion of the contact is determined based on a projection of the location of the second portion of the contact, the second portion of the contact adjacent to the edge of the touch-sensitive surface having a greatest distance from the edge of the touch-sensitive surface is determined) (e.g., the contact is projected to the left, and the location determination is based on a leftmost portion of the contact).

In some embodiments, in accordance with a determination that the contact proximate to the edge of the touch-sensitive surface has the first spatial property, being positioned (2418) entirely away from the touch-sensitive surface relative to a first region of the touch-sensitive surface (e.g., in a region that begins outside of the touch-sensitive surface and extends away from the edge of the touch-sensitive surface where the first portion of the first contact was detected, such that the determination of whether the contact is within the first region is based on a presumed second portion of the contact that extends beyond the edge of the touch-sensitive surface); and in accordance with a determination that the contact adjacent to the edge of the touch-sensitive surface has the second spatial property, including, with respect to the first region of the touch-sensitive surface, a first portion on the touch-sensitive surface adjacent to the edge of the touch-sensitive surface and a second portion that extends away from the edge of the touch-sensitive surface (e.g., in a region that begins within the touch-sensitive surface but extends away from the edge of the touch-sensitive surface where the first portion of the first contact was detected and away from the edge of the touch-sensitive surface, such that the determination of whether the contact is within the first region may be based on the inferred second portion of the contact extending beyond the 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, in accordance with a determination that the contact proximate to the edge of the touch-sensitive surface has the first spatial property, being positioned (2420) entirely away from the touch-sensitive surface relative to a first region of 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 a region that begins outside of the touch-sensitive surface and extends away from the edge of the touch-sensitive surface where a first portion of the first contact was detected so that the determination of whether the contact is within the first region is based on a presumed second portion of the contact that extends beyond the edge of the touch-sensitive surface); and in accordance with a determination that the contact proximate to the edge of the touch-sensitive surface has the second spatial property, positioning the first region relative to the touch-sensitive surface entirely away from 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, wherein the second fixed distance is shorter than the first fixed distance (e.g., the boundary corresponding to a flat finger input is closer to the edge of the touch-sensitive surface than the boundary corresponding to a fingertip input).

In some embodiments, in accordance with a determination that a portion (e.g., a second portion) of the contact adjacent to the edge of the touch-sensitive surface extends beyond the edge of the touch-sensitive surface, the location of the contact is (2422) the location of the (second) portion of the contact that extends furthest from the edge of the touch-sensitive surface that extends beyond the edge of the touch-sensitive surface (e.g., the location of the contact is defined as the point furthest from the edge when the contact extends beyond the touch-sensitive surface) based on a projection of the location of the (second) portion of the contact that extends beyond the edge of the touch-sensitive surface; in some embodiments, the location of the contact is defined as the average location of a plurality of points on the leading (e.g., left) edge of the contact. In some embodiments, the location of the contact is defined as the centroid of the contact.

In some embodiments, the one or more characteristics based with respect to the first region of the touch-sensitive surface include (2424) a size of the contact proximate to the edge of the touch-sensitive surface (e.g., a contact shape characteristic of a fingertip input invokes a more rigid activation region than a contact shape characteristic of a flat finger input).

In some embodiments, the size of the contact proximate to the edge of the touch-sensitive surface is (2426) based on one or more of: a measure 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 sum, which is a normalized sum of the capacitance of the contact (e.g., how firmly the contact is made with the touch-sensitive surface), a larger geometric mean (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 short radius (e.g., which indicates whether a finger lies flat on the touch-sensitive surface)).

In some embodiments, the difference (2428) between the first boundary of the first region and the second boundary of the first region is greater near a central portion of the edge of the touch-sensitive surface and is less near a distal portion of the edge of the touch-sensitive surface (e.g., the distance between the boundary of the first region and the boundary of the second region decreases toward the corners 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 the contact adjacent to the edge of the screen has the second spatial property: in accordance with a determination that the location of the contact is adjacent to a corner of the touch-sensitive surface, the first region has a second size that is the same as the first size (e.g., an expanded activation region is not available at the corner of the touch-sensitive surface to avoid accidental activation of the user's palm in time of touchdown across the device); and in accordance with a determination 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, the first region relative to the touch-sensitive surface has (2430) a first or second size (e.g., depending on the size of the contact) when the contact proximate to the edge of the touch-sensitive surface moves at a speed above a first speed threshold (e.g., the input parameters detected above a given threshold include the input parameters detected at a given threshold (e.g., "above … …" means "above … … or above")), and has a third size when the contact proximate to the edge of the touch-sensitive surface moves at a speed below the first speed threshold. In some embodiments, the touch must begin within a first area (e.g., 5mm) and the detection characteristic intensity must increase above the intensity threshold when the contact moves above the velocity threshold and within a second area (e.g., 20 mm). In some embodiments (e.g., where the application associates a location with an edge swipe operation), if the contact does not satisfy the system gesture criteria, the device performs an application-specific operation (e.g., navigates within the application).

In some embodiments, the system gesture criteria further include (2432) a direction criterion specifying a predetermined direction of motion on the touch-sensitive surface, wherein the direction criterion is satisfied when a contact proximate to an edge of the touch-sensitive surface moves in the predetermined direction on the touch-sensitive surface (e.g., moves more vertically than horizontal movement).

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

In some embodiments, the system gesture criteria further include (2436) a fail condition that prevents a contact proximate to an edge of the touch-sensitive surface from satisfying the system gesture criteria (e.g., failing to satisfy the system gesture criteria even if the contact moves back into the region) when the contact moves outside (e.g., more than 20mm away from the edge) a second region relative to the touch-sensitive surface (e.g., on the touch-sensitive surface) before the system gesture criteria are satisfied. For example, prior to initiating execution of an application-independent operation: the device detects movement of a contact proximate to an edge of the touch-sensitive surface on the touch-sensitive surface; and in response to detecting the movement of the contact, in accordance with a determination that the contact is moving outside the second region relative to the touch-sensitive surface, the device prevents the system gesture criteria from being met (e.g., the device prevents execution of an application-independent operation). In preventing satisfaction of the system gesture criteria, the device detects termination of the input (e.g., including lifting of a contact proximate to an edge of the touch-sensitive surface); and in response to detecting termination of the input, the device stops preventing satisfaction of the system gesture criteria.

In some embodiments, the system gesture criteria include (2438) requiring (e.g., additionally requiring) that a characteristic intensity of the contact proximate to an edge of the touch-sensitive surface increase 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 are not met when 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 below the intensity threshold).

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

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

In some embodiments, the corresponding operation in the application is a (2444) key press operation (e.g., a character insertion operation for a keyboard, or a keyboard switch operation, or a shift key activation option).

In some embodiments, the corresponding operation in the application is a (2446) page switch operation (e.g., next page, previous page, etc.).

In some embodiments, a corresponding operation (2448) in the application is used to navigate within a hierarchy associated with the application, such as between levels of the application (e.g., song versus playlist) or a history of the application (e.g., back and forth within a web browsing history).

In some embodiments, the corresponding operation in the application is a (2450) preview operation (e.g., glance at a link or row in a pop-up list).

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

It should be understood that the particular order in which the operations in fig. 24A-24F have been described is merely exemplary and is not intended to indicate that the order described 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 2500) also apply in a similar manner to method 2400 described above with respect to fig. 24A-24F. Such as contacts, gestures, user interface objects, intensity thresholds, focus selectors, animations described above with reference to the methods, optionally have one or more of the characteristics of contacts, gestures, user interface objects, intensity thresholds, focus selectors, 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.

25A-25H illustrate a flow diagram of a method 2500 for navigating between user interfaces, according to some embodiments. Method 2500 is performed at an electronic device (e.g., device 300 of FIG. 3 or portable multifunction device 100 of FIG. 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 the track pad 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, playback, and/or stream (e.g., from an external server) audio and/or visual files, the electronic device in communication with a remote control and a display (e.g., Apple TV from Apple inc. of cupertino, california). Some operations in method 2500 are optionally combined, and/or the order of some operations is optionally changed.

As described below, the method 2500 provides an intuitive way for navigating between user interfaces. The method reduces the cognitive burden on the user when navigating between user interfaces, thereby creating a more efficient human-machine interface. For battery operated electronic devices, enabling a user 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 the display. While displaying the first view, the device detects (2504) a first portion of the first input, including detecting a first contact on the touch-sensitive surface. In response to detecting the first portion of the first input, in accordance with a determination that the first portion of the first input satisfies application-switching criteria (e.g., including intensity criteria (e.g., "glance" intensity) and location criteria (e.g., adjacent 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) a portion of the plurality of application views including the first application view and the second application view on the display (and optionally ceases to display another portion of the first application view (e.g., by sliding a portion of the first application view off the display)). While simultaneously displaying portions of the multiple application views, the device detects (2508) a second portion of the lifted first input that includes the first contact. In response to detecting the second portion of the first input that includes the lift of the first contact: in accordance with a determination that the second portion of the first input satisfies first view display criteria, the device stops (2510) displaying the 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 a first contact lift is detected in a first region of the touch-sensitive surface (e.g., a portion adjacent to a left edge of the touch-sensitive surface); and in accordance with a determination that the second portion of the first input satisfies multi-view display criteria, after detecting the lift-off of the first contact, the device maintains simultaneous display on the display of at least a portion of the first application view and at least a portion of the second application view, wherein the multi-view display criteria include criteria that are satisfied when the lift-off of the first contact is detected in a second region of the touch-sensitive surface that is different from the first region of the touch-sensitive surface (e.g., a middle portion of the touch-sensitive surface).

In some embodiments, in response to detecting the second portion of the first input that includes the lift of the first contact: in accordance with a determination that the second portion of the first input satisfies second view display criteria, the device stops (2512) displaying the first application view and displays (entirely) the second application view on the display, wherein the second view display criteria include a criterion that is satisfied when a lift-off of the first contact is detected in a third region of the touch-sensitive surface that is different from the first region of the touch-sensitive surface and the second region of the touch-sensitive surface (e.g., a portion adjacent to a right edge of the touch-sensitive surface).

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

In some embodiments, in reducing the respective sizes of a plurality of application views including the first application view and the second application view: the device detects (2516) continued movement of the first contact across the touch-sensitive surface. In accordance with a determination that the first contact moves into the third region of the touch-sensitive surface, in response to detecting continued movement of the first contact, the device increases respective sizes of a plurality of application views including the first application view and the second application view. In some embodiments, the size of the application view is 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 size of the application view). In some embodiments, increasing the size of the application view while the contact is in the third area of the touch-sensitive surface indicates to the user that lifting of the contact in the third area will activate the application associated with the second application view (e.g., switch to a previous application). In some embodiments, the portion of the second application view expands and moves in a direction opposite the movement of the contact in the third region (e.g., simulating the second application view dynamically expanding into a user interface for the second user). In some embodiments, the distance between two or more of the application views changes in accordance with movement of the first contact (e.g., application views other than the top application view move together in addition to increasing in size as the first contact continues to move across the display).

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

In some embodiments, the first application view and the second application view are (2522) views of the same application (e.g., 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, in accordance with a determination that the second portion of the first input satisfies multiview display criteria (where the multiview display criteria include criteria that are satisfied when a lift of the first contact is detected in a second region of the touch-sensitive surface that is different from the first region of the touch-sensitive surface), maintaining concurrent 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 the heap 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., laterally offset 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 unrolled in one direction on the display (e.g., to the right as shown in fig. 5P and 22C). 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 (e.g., 2, 3, 4, or 5 representations) in the heap is visible, while the remaining representations in the heap are off-screen or under representations that include visible information. In some embodiments, the representations underlying the representations that include the visible information are stacked together so close that no information is displayed for these representations. In some embodiments, the representation below the representation including the visible information is a style representation, such as just a generic edge 503 as shown in fig. 5P.

In some embodiments, while in the user interface selection mode: detecting (2528) a second input by the device, the second input comprising a drag gesture by a second contact on the touch-sensitive surface at a location corresponding to the location of the first user interface representation on the display, the second contact moving across the touch-sensitive surface in a direction corresponding to the first direction on the display; and while the second contact is at a location on the touch-sensitive surface that corresponds to the location of the first user interface representation on the display and moving across the touch-sensitive surface in a direction that corresponds to the first direction on the display: the device moves the first user interface representation in a first direction on the display at a first speed in accordance with a speed of a second contact on the touch-sensitive surface; and the device moves a second user interface representation disposed above the first user interface representation in a first direction at a second speed greater than the first speed. For example, in relation to moving the first user interface representation, on the touch-sensitive display, the card or other representation below the finger contact moves at the same speed as the finger contact; and on a display coupled to the track pad, the 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 a 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 differentiator that separates an on-screen object (e.g., user interface representation) from its peer-to-peer object that is not focused upon. 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 contact. In some embodiments, the movement of the first user interface representation produces a visual effect that the finger contact is capturing 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 produces the following visual effect: as the second user interface representation moves in the first direction toward an edge of the display, an increasingly larger portion of the first user interface representation emerges from beneath the second user interface representation. In combination, the 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, including displaying at least two of the plurality of user interface representations in the pile, 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) involving one of the at least two user interface representations in the pile. In response to detecting the selection input: the device stops displaying the stack and displays 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 while any user interfaces corresponding to other user interface representations in the heap are not displayed. In some embodiments, the display of the user interface corresponding to the selected user interface representation replaces the display of the heap.

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 the heap: the device detects (2532) a deletion input involving the first user interface representation (e.g., a drag-up gesture at a location on the touch-sensitive surface that corresponds to a location on the first user interface representation). In response to detecting a deletion input involving the first user interface representation: the device removes the first user interface representation from the first location in the heap. 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 the opposite direction, then 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 when transitioning to the second user interface representation; and animating a reduction in size of the second application view when transitioning to the first user interface representation. For example, in a "glance" phase, the UI card is referred to as an application view, and in a "pop-up" phase (e.g., a multitasking user interface), the UI card is referred to as a 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, applying the switching criteria includes (2536) an intensity criterion. In some embodiments, the intensity criterion is satisfied when the characteristic intensity of the contact is above a first intensity threshold. In some embodiments, the system gesture criteria include a location criterion that is met when the contact is within a first region relative to the touch-sensitive surface (e.g., regions 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 the 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 region relative to the touch-sensitive surface has a first size when contacts proximate to an edge of the touch-sensitive surface have a first spatial property (e.g., large oblong contact characteristic for a flat finger input) and a second size when contacts proximate to an edge of the touch-sensitive surface have a second spatial property (e.g., small circular contact characteristic for a fingertip input). In some embodiments, the size of the region dynamically changes with the size of the contact. In some embodiments, the contacts are classified and one of a plurality of discretely sized regions is selected.

In some embodiments, the strength criteria of the application switching criteria are met (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, in accordance with a determination that the first portion of the first input satisfies the application switching criteria, the device provides (2542) a haptic output.

In some embodiments, in response to detecting the first portion of the first input, in accordance with a determination that the first portion of the first input satisfies the preview criteria: the device moves (2544) the first view of the first application partially off the display (e.g., slides 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 at a location of the display from which the first view of the first application was displaced (e.g., the active user interface slides over, revealing an edge of the previously active user interface from below the currently active user interface).

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

In some embodiments, applying the switching criteria includes (2548) a criterion that is met when the intensity of the first contact increases above a first intensity threshold (e.g., a glance/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 lifting of the first contact includes displaying a multitasking user interface; and in response to detecting the first portion of the first input, in accordance with a determination that the first portion of the first input satisfies multitasking criteria, the multitasking criteria including criteria that are satisfied when the intensity of the first contact increases above a second intensity threshold that is greater than the first intensity threshold. For example, a multitasking user interface may be displayed by: by satisfying an application switching criterion (which may be satisfied with a contact having an intensity above a first intensity threshold and below a second intensity threshold), and then moving the contact across the touch-sensitive surface to a location corresponding to a middle portion of the display; or by satisfying a multitasking criterion, which may be satisfied with contacts having an intensity above a second intensity threshold.

In some embodiments, in response to detecting the first portion of the first input, in accordance with a determination that the first portion of the first input satisfies the multitasking criteria (e.g., includes a high intensity criterion (e.g., "pop-up" intensity) and optionally a location criterion (e.g., adjacent to an edge of the touch-sensitive surface, in the first area, or in the second area)): the device enters (2250) a user interface selection mode and displays a plurality of user interface representations in the heap 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 unrolled in one direction on the display (e.g., to the right as shown in fig. 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 (e.g., 2, 3, 4, or 5 representations) in the heap is visible, while the remaining representations in the heap are off-screen or under representations that include visible information. In some embodiments, the representations underlying the representations that include the visible information are stacked together so close that no information is displayed for these representations. In some embodiments, the representation below the representation including the visible information is a style representation, such as shown in fig. 5E as just a generic edge 503.

In some embodiments, the multitasking criteria include (2552) an intensity criterion that is met when the (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 met when the multitasking intensity criterion is met when the contact is within the first region of the touch-sensitive surface.

It should be understood that the particular order in which the operations in fig. 25A-25H have been described is merely exemplary and is not intended to indicate that the order described 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 fig. 25A-25H. Such as contacts, gestures, user interface objects, intensity thresholds, focus selectors, animations described above with reference to the methods, optionally have one or more of the characteristics of contacts, gestures, user interface objects, intensity thresholds, focus selectors, 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, fig. 16 illustrates a functional block diagram of an electronic device 1600 configured according to the principles of various described embodiments. The functional blocks of the device are optionally implemented by hardware, software or a combination of hardware and software to carry out the principles of the various described embodiments. Those skilled in the art will understand that the functional blocks described in fig. 16 may alternatively be combined or separated into sub-blocks to implement the principles of the various described embodiments. Thus, the description herein optionally supports any possible combination or separation or other definition of the functional blocks described herein.

As shown in fig. 16, an electronic device 1600 includes: a display unit 1602 configured to display a user interface; a touch-sensitive surface element 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 optionally one or more sensor units 1606. In some embodiments, the processing unit 1608 comprises: a display implementation unit 1610, a detection unit 1612, a moving 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: implementing display of multiple user interface representations in a stack on display unit 1602 (e.g., with display implementation unit 1610), wherein: 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 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 (e.g., with detection unit 1612) by a first contact at a location on touch-sensitive surface unit 1604 that corresponds to a location of the first user interface representation on display unit 1602, the first contact moving across touch-sensitive surface unit 1604 in a direction that corresponds to a first direction on display unit 1602; and while the first contact is at a location on touch-sensitive surface unit 1604 that corresponds to the location of the first user interface representation on display unit 1602 and is moving across touch-sensitive surface unit 1604 in a direction that corresponds to the first direction on the display unit: move the first user interface representation in a first direction on display unit 1602 (e.g., with movement unit 1614) at a first speed in accordance with a speed of a first contact on touch-sensitive surface unit 1604; and moving 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 (e.g., with the moving unit 1614).

Fig. 17 illustrates a functional block diagram of an electronic device 1700 configured in accordance with the principles of various described embodiments, according to some embodiments. The functional blocks of the device are optionally implemented by hardware, software or a combination of hardware and software to carry out the principles of the various described embodiments. Those skilled in the art will appreciate that the functional blocks depicted in fig. 17 may alternatively be combined or separated into sub-blocks. To carry out the principles of the various described embodiments. Thus, the description herein optionally supports any possible combination or separation or other definition of the functional blocks described herein.

As shown in fig. 17, an electronic device 1700 includes: a display unit 1702 configured to display a user interface; a touch-sensitive surface unit 1704 configured to receive a contact; one or more sensor units 1706 configured to detect intensity of contacts with the touch-sensitive surface unit 1704; and a processing unit 1708 coupled to the display unit 1702, the touch-sensitive surface unit 1704, and the one or more sensor units 1706. In some embodiments, the processing unit 1708 includes: a display implementing unit 1710, a detecting unit 1712, a moving unit 1714, an entering unit 1716, and an operation executing unit 1718.

The processing unit 1710 is configured to: enable display of a first user interface on the display unit 1702 (e.g., with the display enabling unit 1710); while displaying the first user interface on the display unit 1702, detect input through a first contact on the touch-sensitive surface unit 1704 (e.g., with the detection unit 1702); upon detecting input via the first contact, enabling display of the first user interface representation and at least the second user interface representation on the display unit 1702 (e.g., with a display enabling unit 1710); while displaying the first user interface representation and the at least second user interface representation on the display unit 1702, detecting termination of the input by the first contact (e.g., with detecting unit 1712); and in response to detecting termination of the input through the first contact: in accordance with a determination that the first contact has 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 1704 that corresponds to the predefined direction on the display 1702 during the input, enable display of a second user interface corresponding to the second user interface representation (e.g., with display enabling unit 1710); and in accordance with a determination that the first contact has a characteristic intensity below the predetermined intensity threshold during the input and that the first contact has not moved in a direction across the touch-sensitive surface unit 1704 that corresponds to the predefined direction on the display unit 1702 during the input, enable re-displaying the first user interface (e.g., with the display enabling unit 1710).

Fig. 18 illustrates a functional block diagram of an electronic device 1800 configured in accordance with the principles of various described embodiments, in accordance with some embodiments. The functional blocks of the device are optionally implemented by hardware, software or a combination of hardware and software to carry out the principles of the various described embodiments. Those skilled in the art will understand that the functional blocks described in fig. 18 may alternatively be combined or separated into sub-blocks to implement the principles of the various described embodiments. Thus, the description herein optionally supports any possible combination or separation or other definition of the functional blocks described herein.

As shown in fig. 18, the electronic device 1800 includes: a display unit 1802 configured to display a user interface; a touch-sensitive surface unit 1804 configured to receive a contact; one or more sensor units 1806 configured to detect intensity of contacts with the touch-sensitive surface unit 1804; and a processing unit 1808 coupled to the display unit 1802, the touch-sensitive surface unit 1804, and the 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 change unit 1820.

The processing unit 1810 is configured to: enable display of a first user interface on the display unit (e.g., with display enabling unit 1810); while enabling display of the first user interface on the display unit, detecting, on the touch-sensitive surface unit 1804, an input of a first contact through a period of increased intensity that includes the first contact (e.g., with the detecting unit 1812); in response to detecting input of a first contact through a period of increased intensity including the first contact: enabling display of a first user interface representation for a first user interface and a second user interface representation for a second user interface on display unit 1802 (e.g., with display enabling unit 1810), wherein the first user interface representation is displayed over and partially exposes the second user interface representation; in enabling display of the first user interface representation and the second user interface representation on the display unit 1802, detecting that an intensity of the first contact satisfies one or more predetermined intensity criteria during the period of increased intensity of the first contact (e.g., with the detecting unit 1812); in response to detecting that the intensity of the first contact satisfies one or more predetermined intensity criteria: ceasing to implement displaying the first user interface representation and the second user interface representation on display unit 1802 (e.g., with display implementation unit 1810); and enabling display of the second user interface on display unit 1802 (e.g., with display enabling unit 1810).

Fig. 19 illustrates a functional block diagram of an electronic device 1900 configured in accordance with the principles of various described embodiments, in accordance with some embodiments. The functional blocks of the device are optionally implemented by hardware, software or a combination of hardware and software to carry out the principles of the various described embodiments. Those skilled in the art will understand that the functional blocks described in fig. 19 are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Thus, the description herein optionally supports any possible combination or separation or other definition of the functional blocks described herein.

As shown in fig. 19, an 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 intensity of contacts with the touch-sensitive surface unit 1904; and a processing unit 1908 coupled with the display unit 1902, the touch-sensitive surface unit 1904, and the one or more sensor units 1906. In some embodiments, the processing unit 1908 comprises: an implementation unit 1910, a detection unit 1912, a moving unit 1914, an increasing unit 1916, a decreasing unit 1918, and an entering unit 1920 are shown.

The processing unit 1910 is configured to: implementing display of multiple user interface representations in the stack on the display unit 1902 (e.g., with 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 being laterally offset from and partially exposing the second user interface representation in a first direction, and the second user interface representation being laterally offset from and partially exposing the third user interface representation in the first direction; detect input (e.g., with detection unit 1922) through a first contact on touch-sensitive surface unit 1904 at a location corresponding to the second user interface representation on display unit 1902; and in accordance with detecting an increase in intensity of the first contact on the touch-sensitive surface unit 1904 at a location corresponding to the second user interface representation on the display unit 1902 (e.g., with the detecting unit 1912), increasing an area of the second user interface representation exposed 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., with the increasing unit 1916).

Fig. 20 illustrates a functional block diagram of an electronic device 2000 configured in accordance with the principles of various described embodiments, according to some embodiments. The functional blocks of the device are optionally implemented by hardware, software or a combination of hardware and software to carry out the principles of the various described embodiments. Those skilled in the art will understand that the functional blocks depicted in fig. 20 may alternatively be combined or separated into sub-blocks to implement the principles of the various described embodiments. Thus, the description herein optionally supports any possible combination or separation or other definition of the functional blocks described herein.

As shown in fig. 20, the 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 one or more sensor units 2006 configured to detect intensity of contacts with the touch-sensitive surface unit 2004; and a processing unit 2008 coupled with the display unit 2002, the touch-sensitive surface unit 2004, and optionally one or more sensor units 2006. In some embodiments, the processing unit 2008 includes: the display implementation unit 2010, the detection unit 2012, the moving unit 2014, and the presentation unit 2016.

Processing unit 2010 is configured to: enabling display of a plurality of user interface representations in a stack on a display unit 2002 (e.g., with a display enabling 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 being laterally offset from and partially exposing the first user interface representation in a first direction, and the third user interface representation being laterally offset from and partially exposing the second user interface representation in the first direction; detect a fling gesture (e.g., with detection unit 2012) by a first contact moving across the touch-sensitive surface unit 2004, wherein movement of the fling gesture by the first contact corresponds to movement across one or more of the plurality of user interface representations in the stack; and during the fling gesture, more of the first user interface representation is rendered from behind the second user interface representation on the display unit (e.g., with the rendering unit 2016) as the first contact moves over a location on the touch-sensitive surface unit 2004 that corresponds to the first user interface representation on the display unit 2002.

Fig. 21 illustrates a functional block diagram of an electronic device 2100 configured in accordance with the principles of various described embodiments, in accordance with some embodiments. The functional blocks of the device are optionally implemented by hardware, software or a combination of hardware and software to carry out the principles of the various described embodiments. Those skilled in the art will understand that the functional blocks described in fig. 21 are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Thus, the description herein optionally supports any possible combination or separation or other definition of the functional blocks described herein.

As shown in fig. 21, the electronic device 210 includes: a display unit 1602 configured to display a user interface; a touch-sensitive surface unit 2104 configured to receive a contact; one or more sensor units 2106 configured to detect intensity of contacts with the touch-sensitive surface unit 2104; and a processing unit 2108 coupled with 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 comprises: a display implementing unit 2110 and a detecting unit 2112.

The processing unit 2110 is configured to: enabling display of a first user interface of a first application on the display unit 2102 (e.g., with the display enabling unit 2110), the first user interface including a back navigation control; while displaying the first user interface of the first application on the display unit 2102, detecting a gesture (e.g., with the detection unit 2112) through a first contact on the touch-sensitive surface unit 2104 at a location corresponding to a back navigation control on the display unit 2102; in response to detecting the gesture with the first contact on the touch-sensitive surface unit 2104 at the location corresponding to the back navigation control: in accordance with a determination that the gesture by the first contact is a gesture having an intensity of the first contact that satisfies one or more predetermined intensity criteria, replace the display of the first user interface of the first application (e.g., with display implementation unit 2110) with the display of a plurality of user interface representations of the first application (including the representation of the first user interface and the representation of the second user interface); and in accordance with a determination that the gesture by the first contact is a gesture having an intensity of the first contact that does not satisfy the one or more predetermined intensity criteria, replace the display of the first user interface of the first application with the display of the second user interface of the first application (e.g., using display implementation unit 2110).

According to some embodiments, fig. 26 illustrates a functional block diagram of an electronic device 2600 configured according to the principles of various described embodiments. The functional blocks of the device are optionally implemented by hardware, software or a combination of hardware and software to carry out the principles of the various described embodiments. Those skilled in the art will understand that the functional blocks described in fig. 26 are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Thus, the description herein optionally supports any possible combination or separation or other definition of the functional blocks described herein.

As shown in fig. 26, the electronic apparatus includes: a display unit 2602 configured to display content items; a touch-sensitive surface unit 2604 configured to receive user input; one or more sensor units 2606 configured to detect intensity of contacts with the touch-sensitive surface unit 2604; and a processing unit 2608 coupled with the display unit 2602, the touch-sensitive surface unit 2604, and the one or more sensor units 2606. In some embodiments, processing unit 2608 includes a display implementation unit 2610, a detection unit 2612, and a determination unit 2614. In some embodiments, the processing unit 2608 is configured to: enable display (e.g., with display implementation unit 2610) of a user interface for an application on a display unit (e.g., display unit 2602); detecting (e.g., with detection unit 2612) an edge input, including detecting a change in a characteristic intensity of a contact proximate to an edge of the touch-sensitive surface; and in response to detecting the edge input: in accordance with a determination (e.g., with determination unit 2614) that the edge input satisfies the system gesture criteria, performing an application-independent operation, wherein: the system gesture criteria include intensity criteria; the system gesture criteria include a location criterion that is satisfied when the contact satisfies an intensity criterion for the contact while within the first region relative to the touch-sensitive surface; and determine a first region relative to the touch-sensitive surface unit 2604 based on one or more characteristics of the contact.

According to some embodiments, fig. 27 illustrates a functional block diagram of an electronic device 2700 configured according to the principles of various described embodiments. The functional blocks of the device are optionally implemented by hardware, software or a combination of hardware and software to carry out the principles of the various described embodiments. Those skilled in the art will understand that the functional blocks described in fig. 27 may alternatively be combined or separated into sub-blocks to implement the principles of the various described embodiments. Thus, the description herein optionally supports any possible combination or separation or other definition of the functional blocks described herein.

As shown in fig. 27, the electronic apparatus includes: a display unit 2702 configured to display content items; a touch-sensitive surface unit 2704 configured to receive user input; one or more sensor units 2706 configured to detect intensity of contacts with the touch-sensitive surface unit 2704; and a processing unit 2708 coupled to display unit 2702, touch-sensitive surface unit 2704, and one or more sensor units 2706. In some embodiments, processing unit 2708 includes a display implementation unit 2710, a detection unit 2712, and a determination unit 2714. In some embodiments, the processing unit 2708 is configured to: enable display (e.g., with display enabling unit 2710) of a first view of a first application on a display unit (e.g., display unit 2702); while enabling display of the first view, detecting (e.g., with detection unit 2712) a first portion of the first input includes detecting a first contact on touch-sensitive surface unit 2704; in response to detecting the first portion of the first input, in accordance with a determination (e.g., with determination unit 2714) that the first portion of the first input satisfies the application-switching criteria, enable simultaneous display (e.g., with display implementation unit 2710) of a portion of the plurality of application views, including the first application view and the second application view, on the display unit; in enabling simultaneous display of portions of multiple application views, detecting (e.g., with detection unit 2712) a second portion of the lifted first input that includes the first contact; and in response to detecting the second portion of the first input that includes the lift of the first contact: in accordance with a determination (e.g., with determination unit 2714) that the second portion of the first input satisfies first view display criteria, ceasing to enable display (e.g., with display enabling unit 2710) of the portion of the second application view on the display unit and enabling display (e.g., with display enabling unit 2710) of 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 region of the touch-sensitive surface unit 2704; and in accordance with a determination (e.g., with determination unit 2714) that the second portion of the first input satisfies the multi-view display criteria, maintain simultaneous display (e.g., with display implementation unit 2710) on the display of at least a portion of the first application view and at least a portion of the second application view after detecting liftoff of the first contact, wherein the multi-view display criteria include criteria that are satisfied when liftoff of the first contact is detected in a second region of the touch-sensitive surface unit 2704 that is different from the first region of the touch-sensitive surface unit 2704.

The operations in the information processing method described above are optionally implemented by running one or more functional modules in an information processing apparatus such as a general-purpose processor or a dedicated chip (e.g., as described above with respect to fig. 1A and 3).

The operations described above with reference to FIGS. 10A-10H, 11A-11E, 12A-12E, 13A-13D, 14A-14C, and 15 may optionally be performed by components depicted in FIGS. 1A-1B or 16-21. For example, user interface enter operations 1006, 1110, and 1312, visual effects 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 insert operation 1082, user interface representation remove operation 1088, user interface representation move operations 1034, 1036, 1140, 1056, 1058, 1068, 1072, 1098, 1150, 1152, 1324, 1326, 1332, 1334, 1336, and 1338, and content dependent execution operations are optionally performed by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112 and event dispatcher module 174 delivers the event information to application 136-1. The respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186 and determines whether the first contact at the first location 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 a user interface or rotating the device from one orientation to another. Upon detection of a respective predefined event or sub-event, the 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 a respective GUI updater 178 to update the content displayed by the application. Similarly, it will be clear to one of ordinary skill in the art how other processes may be implemented based on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching. 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 that are in communication with a remote control and a display (e.g., Apple TV from Apple inc. of cupertino, california). For such devices, rather than having a touch-sensitive surface, an audio input device (e.g., a microphone), and/or buttons on the device itself, input corresponding to gestures on the touch-sensitive surface of the remote control, voice input to the remote control, and/or activation of buttons on the remote control is optionally received. For such devices, the data is optionally provided to a display, rather than being displayed by the device itself. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, to thereby enable others skilled in the art to best utilize the invention and various described embodiments with various modifications as are suited to the particular use contemplated.

完整详细技术资料下载

上一篇：石墨接头机器人自动装卡簧、装栓机

下一篇：触控显示面板

Apparatus and method for navigating between user interfaces

相关技术

网友询问留言