Devices, methods, and graphical user interfaces for manipulating user interface objects using visual and / or haptic feedback.

Abstract

PROBLEM TO BE SOLVED: To provide a more efficient human-machine interface that reduces inputs from a user and improves extent and nature.SOLUTION: An electronic device with a touch-sensitive surface, a display and one or more sensors to detect intensity of contacts, displays a plurality of objects in a first user interface, and detects a contact while a focus selector is at the location of a first object. While the focus selector is at the location of the first object, the device detects an increase in characteristic intensity of the contact to a first intensity threshold, and visually obscure the plurality of objects other than the first object while maintaining display of the first object. The device detects that the characteristic intensity of the contact continues to increase above the first intensity threshold. In response thereto, the device dynamically increases the amount of visual obscuring of the plurality of user interface objects other than the first user interface object.SELECTED DRAWING: Figure 1A

Description

[Technical Field]

[0001] This application relates in general to an electronic device having a touch-sensing surface, and the electronic device includes, but is not limited to, an electronic device having a touch-sensing surface for detecting input for operating a user interface. [Background technology]

[0002] The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased dramatically in recent years. Exemplary examples of touch-sensitive surfaces include touchpads and touchscreen displays. Such surfaces are widely used to operate user interfaces on displays.

[0003] Examples of operations include adjusting the position and / or size of one or more user interface objects, activating a button, opening a file / application represented by a user interface object, associating metadata with one or more user interface objects, or otherwise manipulating the user interface. Examples of user interface objects include digital images, videos, text, icons, control elements such as buttons, and other graphics.

[0004] In some situations, users may be using file management programs (e.g., Finder from Apple Inc. in Cupertino, California), messaging applications (e.g., Messages from Apple Inc. in Cupertino, California), image management applications (e.g., Photos from Apple Inc. in Cupertino, California), camera applications (e.g., Camera from Apple Inc. in Cupertino, California), map applications (e.g., Maps from Apple Inc. in Cupertino, California), note-taking applications (e.g., Notes from Apple Inc. in Cupertino, California), digital content (e.g., video and music) management applications (e.g., Music and iTunes from Apple Inc. in Cupertino, California), news applications (e.g., News from Apple Inc. in Cupertino, California), phone applications (e.g., Phone from Apple Inc. in Cupertino, California), and email applications (e.g., Apple Inc. in Cupertino, California). Apple Inc.'s Mail, browser applications (e.g., Safari from Apple Inc. in Cupertino, California), drawing applications, presentation applications (e.g., Keynote from Apple Inc. in Cupertino, California), word processing applications (e.g., Pages from Apple Inc. in Cupertino, California), spreadsheet applications (e.g., Numbers from Apple Inc. in Cupertino, California), reader applications (e.g., iBooks from Apple Inc. in Cupertino, California), video creation applications (e.g., Apple Inc. in Cupertino, California)This action needs to be performed on user interface objects within iMovie and / or geolocation applications (e.g., Find Friends and Find iPhone from Apple Inc., located in Cupertino, California).

[0005] However, existing methods for performing these operations are cumbersome and inefficient. Furthermore, existing methods waste energy by taking unnecessarily long periods of time. This latter consideration is particularly important in battery-powered devices. [Overview of the Initiative]

[0006] Therefore, there is a need for electronic devices that have faster and more efficient methods and interfaces for operating the user interface. Such methods and interfaces optionally complement or replace conventional methods for operating the user interface. Such methods and interfaces reduce the frequency, extent, and / or nature of user input, creating a more efficient human-machine interface. In the case of battery-operated devices, such methods and interfaces save power and extend the time interval between battery charging.

[0007] The defects and other problems associated with user interfaces for electronic devices having touch-sensitive surfaces are mitigated or eliminated by the disclosed device. 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 wristwatch). 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, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or instruction sets stored in memory to perform multiple functions. In some embodiments, the user interacts with the GUI on the touch-sensitive surface, primarily via stylus and / or finger contact and gestures. In some embodiments, these functions optionally include image editing, drawing, presentation, word processing, spreadsheet creation, gameplay, making phone calls, video conferencing, sending emails, instant messaging, training support, digital photography, digital videography, web browsing, digital music playback, note-taking, and / or digital video playback. Executable instructions for performing these functions may optionally be included in a non-temporary computer-readable storage medium or in other computer program products configured to run by one or more processors.

[0008] According to several embodiments, a method is performed in an electronic device having a touch-sensitive surface and a display. The device includes one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The device displays a plurality of user interface objects on a first user interface on the display. The device detects contact at a location on the touch-sensitive surface when a focus selector is located at the location of the first user interface object among these plurality of user interface objects on the display. When the focus selector is located at the location of a first user interface object on the display, the device detects that the characteristic intensity of the contact has increased to a first intensity threshold, and in response to detecting that the characteristic intensity of the contact has increased to a first intensity threshold, the device visually obscures multiple user interface objects other than the first user interface object in the first user interface, while maintaining the display of the first user interface object without visually obscuring the first user interface object. The device then detects that the characteristic intensity of the contact has continued to increase and exceeded the first intensity threshold, and in response to detecting that the characteristic intensity of the contact has continued to increase and exceeded the first intensity threshold, the device dynamically increases the amount by which it visually obscures multiple user interface objects other than the first user interface object in the first user interface, while maintaining the display of the first user interface object without visually obscuring the first user interface object.

[0009] According to some embodiments, the electronic device includes a display unit configured to display user interface objects, a touch-sensing surface unit configured to receive contact, one or more sensor units configured to detect the intensity of contact, and a processing unit connected to the display unit, the touch-sensing surface unit, and the one or more sensor units. The processing unit is configured to enable the display of multiple user interface objects in a first user interface on a display unit, and to detect contact at a certain location on the touch sensing surface unit while the focus selector is at the location of the first user interface object in the multiple user interface objects on the display unit, and to detect that the characteristic intensity of the contact has increased to a first intensity threshold while the focus selector is at the location of the first user interface object on the display unit, and in response to the detection that the characteristic intensity of the contact has increased to a first intensity threshold, to visually obscure multiple user interface objects other than the first user interface object in the first user interface while maintaining the display of the first user interface object without visually obscuring the first user interface object, and to detect that the characteristic intensity of the contact has continued to increase and exceeded a first intensity threshold, and in response to the detection that the characteristic intensity of the contact has continued to increase and exceeded a first intensity threshold, to dynamically increase the amount by which multiple user interface objects other than the first user interface object in the first user interface are visually obscured while maintaining the display of the first user interface object without visually obscuring the first user interface object.

[0010] According to several embodiments, a method is performed in an electronic device having a touch-sensing surface and a display. The device includes one or more sensors for detecting the intensity of contact with the touch-sensing surface. The device displays a plurality of user interface objects on a first user interface on the display. The device detects a touch input while a focus selector is over the first user interface object among the plurality of user interface objects on the display. In accordance with the determination that the input satisfies selection criteria, the device displays a second user interface, separate from the first user interface, in response to the detection of the input. In accordance with the determination that a first portion of the input satisfies preview criteria, the device displays a preview area, including a reduced representation of the second user interface, overlapping on at least some of the plurality of user interface objects in the first user interface, in response to the detection of the first portion of the input. In accordance with the determination that a second portion of the touch input, detected after the first portion of the input, satisfies user interface replacement criteria, the device replaces the display of the first user interface and the overlapping preview area with the display of the second user interface. In accordance with the determination that a second portion of the input from the contact meets the criteria for hiding the preview area, the device stops displaying the preview area and displays the first user interface after the input has finished.

[0011] According to some embodiments, the electronic device includes a display unit configured to display user interface objects, a touch-sensing surface unit configured to receive contact, one or more sensor units configured to detect the intensity of contact with the touch-sensing surface unit, and a processing unit connected to the display unit, the touch-sensing surface unit, and the one or more sensor units. The processing unit is configured to enable the display of a plurality of user interface objects in a first user interface on the display unit. The processing unit is configured to detect input by contact while a focus selector is over the first user interface object among the plurality of user interface objects on the display unit. In accordance with the determination that the input satisfies selection criteria, the processing unit is configured to enable the display of a second user interface, separate from the first user interface, in response to the detection of the input. In accordance with the determination that a first portion of the input satisfies preview criteria, the processing unit is configured to enable the display of a preview area, including a reduced preview area representation of the second user interface, superimposed on at least some of the plurality of user interface objects in the first user interface, in response to the detection of the first portion of the input. In accordance with the determination that a second portion of the input resulting from contact, detected after a first portion of the input, satisfies the user interface replacement criterion, the processing unit is configured to replace the display of the first user interface and the overlapping preview area with the display of the second user interface. In accordance with the determination that a second portion of the input resulting from contact satisfies the preview area hiding criterion, the processing unit is configured to stop displaying the preview area and enable the display of the first user interface after the input has finished.

[0012] According to several embodiments, a method is performed in an electronic device having a touch-sensitive surface and a display. The device includes one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The device displays a plurality of user interface objects on a first user interface on the display. The device detects a first portion of a press input by contact at locations on the touch-sensitive surface corresponding to the locations of the first user interface objects on the plurality of user interface objects on the display. While detecting a first portion of a press input by contact at locations on the touch-sensitive surface corresponding to the locations of the first user interface objects on the plurality of user interface objects on the display, the device selects the first user interface object and detects that the intensity of the contact has increased to a second intensity threshold. In response to detecting that the intensity of the contact has increased to the second intensity threshold, the device displays a preview area on the first user interface that overlaps with at least some of the plurality of user interface objects. After detecting a first portion of the press input, the device detects a second portion of the press input of the contact. In response to detecting a second portion of the pressure input resulting from the contact, and in accordance with the determination that the second portion of the pressure input resulting from the contact satisfies the user interface replacement criterion, the device replaces the display of the first user interface with a second user interface that is separate from the first user interface. In accordance with the determination that the second portion of the pressure input resulting from the contact satisfies the preview area maintenance criterion, the device maintains the display of the preview area that overlaps at least some of the user interface objects within the first user interface even after the pressure input has ended. In accordance with the determination that the second portion of the pressure input resulting from the contact satisfies the preview area hiding criterion, the device stops displaying in the preview area and maintains the display of the first user interface even after the pressure input has ended.

[0013] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The method includes displaying a first user interface on the display, which includes a plurality of selectable user interface objects, including one or more user interface objects of a first type and one or more user interface objects of a second type distinct from the first type. While the device is displaying the first user interface on the display, it performs detection of a first portion of a first input, which includes detecting that the characteristic intensity of the first contact on the touch-sensitive surface has increased and exceeded a first intensity threshold while the focus selector is over each of the plurality of selectable user interface objects. In response to the detection of a first portion of a first input, the device displays supplemental information associated with each user interface object. While the device is displaying the supplemental information associated with each user interface object, it detects the end of the first input. Upon detecting the end of the first input, the device stops displaying the supplemental information associated with each user interface object, according to the determination that each user interface object is a first type of user interface object; and, according to the determination that each user interface object is a second type of user interface object, the device continues to display the supplemental information associated with each user interface object even after detecting the end of the first input.

[0014] According to some embodiments, the electronic device comprises a display unit configured to display content items, a touch-sensitive surface unit configured to receive user input, one or more sensor units configured to detect the intensity of contact with the touch-sensitive surface unit, and a processing unit connected to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable the display of a first user interface on a display unit, which includes a plurality of selectable user interface objects, including one or more user interface objects of a first type and one or more user interface objects of a second type distinct from the first type; to detect a first portion of a first input, which includes detecting that the characteristic intensity of a first contact on the touch-sensing surface has increased and exceeded a first intensity threshold while the focus selector is over each of the plurality of selectable user interface objects while the first user interface is displayed on the display unit; to enable the display of supplementary information associated with each user interface object in response to the detection of a first portion of a first input; to detect the end of the first input while the supplementary information associated with each user interface object is displayed; and to discontinue enabling the display of supplementary information associated with each user interface object in response to the detection of the end of the first input, according to the determination that each user interface object is a first type user interface object; and to maintain the display of supplementary information associated with each user interface object even after detecting the end of the first input, according to the determination that each user interface object is a second type user interface object.

[0015] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The device displays a first user interface on the display, including a first appearance and a background having one or more foreground objects. While the device displays the first user interface on the display, it detects a first input by a first contact on the touch-sensitive surface while a first focus selector is at a location in the first user interface corresponding to the background of the first user interface. In response to the detection of the first input by the first contact, and according to the determination that the first contact has a characteristic intensity exceeding a first intensity threshold, the device dynamically changes the appearance of the background of the first user interface without changing the appearance of one or more foreground objects in the first user interface. The dynamic change in the appearance of the background of the first user interface is at least partially based on the characteristic intensity of the first contact. While dynamically changing the appearance of the background of the first user interface, the device detects the end of the first input due to the first contact, and in response to detecting the end of the first input due to the first contact, it returns the background of the first user interface to its first appearance.

[0016] According to some embodiments, the electronic device comprises a display unit configured to display a user interface, background and foreground objects, a touch-sensing surface unit configured to receive user input, one or more sensor units configured to detect the intensity of contact with the touch-sensing surface unit, and a processing unit connected to the display unit, the touch-sensing surface unit, and the one or more sensor units. The processing unit is configured to enable the display of a first user interface on the display, including a first appearance and a background having one or more foreground objects. While the first user interface is displayed on the display, the processing unit is configured to detect a first input by a first contact on the touch-sensing surface unit while a first focus selector is at a location in the first user interface corresponding to the background of the first user interface. In response to the detection of a first input by a first contact, and according to the determination that the first contact has a characteristic intensity exceeding a first intensity threshold, the processing unit is configured to dynamically change the appearance of the background of the first user interface without changing the appearance of one or more foreground objects in the first user interface. The dynamic change in the appearance of the background of the first user interface is at least partially based on the characteristic intensity of the first contact. While dynamically changing the appearance of the background of the first user interface, the processing unit detects the end of the first input due to the first contact, and in response to detecting the end of the first input due to the first contact, the processing unit is configured to return the background of the first user interface to its first appearance.

[0017] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The device displays a first user interface on the display, including a first appearance and a background having one or more foreground objects. While the first user interface is displayed on the display, the device detects input on the touch-sensitive surface by a first touch having a characteristic intensity above a first intensity threshold. In response to the detection of input by the first touch, the device dynamically changes the appearance of the background of the first user interface without changing the appearance of one or more foreground objects in the first user interface, according to the determination that the focus selector is in a location in the first user interface corresponding to the background of the user interface during the duration of the input. The dynamic change in the appearance of the background of the first user interface is at least partially based on the characteristic intensity of the first touch, and according to the determination that the focus selector is in a location in the first user interface corresponding to each of the one or more foreground objects in the first user interface, the device maintains a first appearance of the background of the first user interface.

[0018] According to some embodiments, the electronic device comprises a display unit configured to display a user interface, background and foreground objects, a touch-sensing surface unit configured to receive user input, one or more sensor units configured to detect the intensity of contact with the touch-sensing surface unit, and a processing unit connected to the display unit, the touch-sensing surface unit, and the one or more sensor units. The processing unit is configured to enable the display of a first user interface on the display unit, including a first appearance and a background having one or more foreground objects. While the processing unit is displaying the first user interface on the display unit, it is configured to detect input from a first touch having a characteristic intensity exceeding a first intensity threshold on the touch-sensing surface unit. In response to the detection of input from the first touch, and according to the determination that the focus selector is at a location in the first user interface corresponding to the background of the user interface during the input, the processing unit is configured to dynamically change the appearance of the background of the first user interface without changing the appearance of one or more foreground objects in the first user interface. The dynamic change in the appearance of the background of the first user interface is at least partially based on the characteristic intensity of the first touch. According to the determination that the focus selector is located in the first user interface at a location within the first user interface corresponding to each of the foreground objects of one or more foreground objects within the first user interface, the processing unit is configured to maintain the first appearance of the background of the first user interface.

[0019] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The device displays a first user interface on the display, which includes a background and a foreground area overlapping a portion of the background and including a plurality of user interface objects. The device detects a touch input on the touch-sensitive surface while a first focus selector is on the first user interface object among the plurality of user interface objects in the foreground area. In response to detecting a touch input, the device performs a first predetermined action corresponding to the first user interface object in the foreground area, according to a determination that the touch input satisfies one or more first pressure criteria, which include criteria that are satisfied when the characteristic intensity of the contact remains below a first intensity threshold during the input, and the device performs a second action, separate from the first predetermined action, corresponding to the first user interface object in the foreground area, according to a determination that the touch input satisfies one or more second pressure criteria, which include criteria that are satisfied when the characteristic intensity of the contact increases and exceeds a first intensity threshold during the input.

[0020] According to some embodiments, the electronic device comprises a display unit configured to display a user interface and user interface objects; a touch-sensing surface unit configured to receive user input; one or more sensor units configured to detect the intensity of contact with the touch-sensing surface unit; and a processing unit connected to the display unit, the touch-sensing surface unit, and the one or more sensor units. The processing unit is configured to enable the display of a first user interface on the display unit, including a first appearance and a background having one or more foreground objects. While the first user interface is displayed on the display unit, the processing unit is configured to detect input from a first touch having a characteristic intensity above a first intensity threshold on the touch-sensing surface unit. In response to the detection of input from the first touch, and according to the determination that the focus selector is at a location in the first user interface corresponding to the background of the user interface during the input, the processing unit is configured to dynamically change the appearance of the background of the first user interface without changing the appearance of one or more foreground objects in the first user interface. The dynamic change in the appearance of the background of the first user interface is at least partially based on the characteristic intensity of the first touch. According to the determination that the focus selector is located in the first user interface at a location within the first user interface corresponding to each of the foreground objects of one or more foreground objects within the first user interface, the processing unit is configured to maintain the first appearance of the background of the first user interface.

[0021] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The device displays an application launch user interface on the display, which includes a plurality of application icons for launching corresponding applications. While displaying the application launch user interface, the device detects a first contact input, which includes detecting a first contact at a location on the touch-sensitive surface corresponding to a first application icon among the plurality of application icons. The first application icon is an icon for launching a first application which is associated with one or more corresponding quick actions. In response to detecting a first contact input according to a determination that the first contact input satisfies one or more application launch criteria, the device launches the first application. According to a determination that the first contact input satisfies one or more quick action display criteria, which include criteria that are satisfied when the characteristic intensity of the first contact increases and exceeds each intensity threshold, the device displays one or more quick action objects associated with the first application simultaneously with the first application icon, without launching the first application.

[0022] According to some embodiments, the electronic device comprises a display unit configured to display user interface objects, a touch-sensitive surface unit configured to receive user input, one or more sensor units configured to detect the intensity of contact with the touch-sensitive surface unit, and a processing unit connected to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable the display of an application launch user interface on the display unit, which includes a plurality of application icons for launching corresponding applications. While the application launch user interface is being displayed, the processing unit is configured to detect a first contact input, which includes detecting a first contact at a location on the touch-sensitive surface unit corresponding to a first application icon among the plurality of application icons, which is an icon for launching a first application associated with one or more corresponding quick actions. In response to detecting the first contact input, the processing unit is configured to launch the first application according to a determination that the first contact input satisfies one or more application launch criteria. In accordance with the determination that the first contact input satisfies one or more quick action display criteria, including criteria that are met when the characteristic intensity of the first contact increases and exceeds each intensity threshold, the processing unit enables the display of one or more quick action objects associated with the first application simultaneously with the first application icon, without launching the first application.

[0023] According to some embodiments, a method is performed in an electronic device having a display and one or more input devices. The electronic device displays a first user interface on the display, which includes a plurality of user interface objects, each associated with a corresponding set of menu options. The device detects a first input via the one or more input devices that corresponds to a request to display menu options for the first user interface object among the plurality of user interface objects. In response to detecting the first input, the device displays menu items corresponding to the first user interface object in a menu. Displaying the menu includes displaying the menu items corresponding to the first user interface object in a first order in the menu, according to a determination that the first user interface object is in a first location within the first user interface, and displaying the menu items corresponding to the first user interface object in a second order in the menu, according to a determination that the first user interface object is in a second location within the first user interface, which is different from the first location.

[0024] According to some embodiments, the electronic device includes a display unit configured to display content items, one or more input devices configured to receive user input, and a processing unit connected to the display unit and one or more input devices. The processing unit is configured to enable the display of a first user interface on the display unit, which includes a plurality of user interface objects, each associated with a corresponding set of menu options. The processing unit is configured to detect a first input via one or more input devices in response to a request to display menu options for a first user interface object among the plurality of user interface objects. In response to detecting the first input, the processing unit enables the display of menu items in the menu that correspond to the first user interface object. Displaying the menu includes displaying the menu items corresponding to the first user interface object in a first order in the menu, according to a determination that the first user interface object is in a first location within the first user interface, and displaying the menu items corresponding to the first user interface object in a second order in the menu, according to a determination that the first user interface object is in a second location within the first user interface, which is different from the first location.

[0025] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The device displays a user interface on the display, which includes a user interface object that is a plurality of actions for interacting with the user interface, and which is associated with a plurality of actions, including a direct selection action and one or more other actions. While the device is displaying the user interface that includes the selectable user interface object, the device detects an input, which includes detecting a contact on the touch-sensitive surface while a focus selector is over the selectable user interface object. In response to detecting the input, which includes detecting the contact, the device displays a menu on the display that includes a graphical representation of a plurality of actions, including a direct selection action and one or more other actions, according to a determination that the input satisfies selection criteria, which include criteria that are met when the characteristic intensity of the contact increases and exceeds each intensity threshold, and the device performs a direct selection action, according to a determination that the input satisfies selection criteria, which include criteria that are met when the characteristic intensity of the contact increases and exceeds each intensity threshold.

[0026] According to some embodiments, the electronic device comprises a display unit configured to display content items, a touch-sensitive surface unit configured to receive user input, one or more sensor units configured to detect the intensity of contact with the touch-sensitive surface unit, and a processing unit connected to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable the display of a user interface on the display unit, which includes a plurality of actions for interacting with the user interface, including selectable user interface objects associated with a plurality of actions, including direct selection actions and one or more other actions. The processing unit is configured to detect input, including detecting contact on the touch-sensitive surface unit while a focus selector is over a selectable user interface object, while the user interface including the selectable user interface object is being displayed. Upon detecting an input, including the detection of contact, the processing unit is configured to enable the display of a menu on the display unit, which includes a graphical representation of multiple actions, including a direct selection action and one or more other actions, according to the determination that the input satisfies selection criteria, including criteria that are met when the characteristic intensity of the contact increases and exceeds each intensity threshold.

[0027] Electronic devices are needed with improved methods and interfaces for teaching users new user interface functions and features, such as new contact intensity-based functions and features. Such methods and interfaces optionally complement or replace conventional methods for teaching users new user interface functions and features. Such methods reduce the frequency, extent, and / or nature of user input, creating a more efficient human-machine interface. In the case of battery-operated devices, such methods and interfaces conserve power and extend the time interval between battery charges.

[0028] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The device displays a user interface on the display, which includes a plurality of user interface objects, each associated with an object-specific behavior triggered by a change in contact intensity, and including a first object displayed in a first location within the user interface and a second object displayed in a second location within the user interface. While displaying the user interface which includes the plurality of user interface elements, the device detects a first input, which includes detecting a first contact on the touch-sensitive surface and detecting that the characteristic intensity of the first contact has increased and exceeded a first intensity threshold. In response to detecting a first input, the device performs a first action associated with the first object, including displaying additional information associated with the first object on the display, in accordance with the determination that the focus selector is in a first location in the user interface where a first object is displayed; in accordance with the determination that the focus selector is in a second location in the user interface where a second object is displayed, the device performs a second action associated with the second object, which is separate from the first action associated with the first object, including displaying additional information associated with the second object on the display; and in accordance with the determination that the focus selector is in a location in the user interface that is far from any object associated with an object-specific action triggered by a change in contact intensity, the device performs a third action, including updating the user interface on the display to simultaneously visually distinguish the first and second objects in the user interface.

[0029] According to some embodiments, the electronic device comprises a display unit configured to display a user interface and user interface objects; a touch-sensing surface unit configured to receive user input; one or more sensor units configured to detect the intensity of contact with the touch-sensing surface unit; and a processing unit connected to the display unit, the touch-sensing surface unit, and the one or more sensor units.The processing unit enables the display on the display unit of a user interface that includes multiple user interface elements, each of which is associated with an object-specific action triggered by a change in contact intensity, and which includes a first object displayed in a first location within the user interface and a second object displayed in a second location within the user interface. While the user interface including the multiple user interface elements is being displayed, the processing unit detects a first input, which includes detecting a first contact on the touch sensing surface unit and detecting that the characteristic intensity of the first contact has increased and exceeded a first intensity threshold. In response to the detection of the first input, the focus selector displays additional information associated with the first object on the display, according to the determination that the first object is in a first location within the user interface where it is displayed. The system is configured to perform a first action associated with a first object, which includes displaying a first action associated with a first object; a second action associated with a second object, which is separate from the first action associated with a first object, which includes displaying additional information associated with the second object on the display unit in accordance with the determination that the focus selector is in a second location in the user interface where the second object is displayed; and a third action, which includes updating the user interface on the display unit to simultaneously visually distinguish the first object and the second object in the user interface in accordance with the determination that the focus selector is in a location in the user interface that is far from any object associated with an object-specific action triggered by a change in contact intensity.

[0030] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The device displays a user interface on the display, which includes a first set of user interface elements, and for each user interface element in the first set of user interface elements, the device is configured to respond to a user input of a first input type by performing a plurality of operations corresponding to each user interface element at the location corresponding to each user interface element, and for the rest of the user interface, the device is not configured to respond to a user input of a first input type by performing a plurality of operations corresponding to each user interface element at the location corresponding to each user interface element in the rest of the user interface. The device detects a first user input of a first input type while the focus selector is at a first location in the user interface. In response to detecting a first user input of a first input type while the focus selector is in a first location within the user interface, the device performs a set of actions corresponding to the first user interface element, according to the determination that the first location corresponds to a first user interface element in a first set of user interface elements; and according to the determination that the first location does not correspond to a user interface element in a first set of user interface elements, the device applies a visual effect on the display to distinguish the first set of user interface elements from the rest of the user interface.

[0031] According to some embodiments, the electronic device comprises a display unit configured to display a user interface and user interface elements; a touch-sensing surface unit configured to receive user input; one or more sensor units configured to detect the intensity of contact with the touch-sensing surface unit; and a processing unit connected to the display unit, the touch-sensing surface unit, and the one or more sensor units. The processing unit is configured to enable the display of a user interface including a first set of user interface elements on the display unit, and for each user interface element in the first set of user interface elements, the device is configured to respond to user input of a first input type by performing a plurality of operations corresponding to each user interface element at the location corresponding to each user interface element, and for the remainder of the user interface, the device is not configured to respond to user input of a first input type by performing a plurality of operations corresponding to each user interface element in the remainder of the user interface at the locations corresponding to each user interface element in the remainder of the user interface. The processing unit is configured to detect a first user input of a first input type while the focus selector is at a first location in the user interface, and in response to the detection of a first user input of a first input type while the focus selector is at a first location in the user interface, it performs a number of operations corresponding to the first user interface element according to the determination that the first location corresponds to a first user interface element in the first set of user interface elements, and applies a visual effect on the display unit to distinguish the first set of user interface elements from the rest of the user interface according to the determination that the first location does not correspond to any user interface element in the first set of user interface elements.

[0032] Thus, an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface is provided with a rapid and efficient method and interface for indicating which user interface elements have contact intensity-based functions and features, thereby improving the effectiveness, efficiency, and user satisfaction of such a device. Such a method and interface can complement or replace conventional methods for teaching users new capabilities and functions (e.g., force-sensitive or pressure-sensitive user interface elements).

[0033] There is a need for electronic devices with improved methods and interfaces for previewing media content. Such methods and interfaces optionally complement or replace conventional methods for previewing media content. Such methods reduce the frequency, extent, and / or nature of user input, creating a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and extend the time interval between battery charges.

[0034] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact on the touch-sensitive surface. The method includes displaying a user interface on the display that includes a plurality of media objects, including a first media object representing one or more media items of a first set, and a second media object representing one or more media items of a second set different from a second set of media items. The method further includes detecting input, including movement of contact on the touch-sensitive surface, while a focus selector is over the first media object. The method further includes, in response to detecting an input that includes the movement of its contact on a touch-sensing surface, outputting a preview of media items from a first set of media items in accordance with a determination that the input satisfies media preview criteria, which include criteria that are satisfied when the input includes an increase in the characteristic intensity of its contact while the focus selector is over a first media object, exceeding a media preview intensity threshold; stopping outputting the preview of media items from the first set of media items and outputting a preview of media items from a second set of media items in response to detecting the movement of its contact; and moving the first and second media objects on the display in accordance with the movement of its contact on the touch-sensing surface in accordance with a determination that the input does not satisfy the media preview criteria.

[0035] According to some embodiments, the electronic device includes a display unit configured to display a user interface, a touch-sensing surface unit for receiving contact, one or more sensor units for detecting the intensity of contact with the touch-sensing surface unit, and a processing unit connected to the display unit, the touch-sensing surface unit, and the one or more sensor units. The input, including the movement of contact on the touch-sensing surface, is detected while the focus selector is over a first media object. The processing unit is configured to enable the display of a user interface on the display unit, which includes a plurality of media objects, including a first media object that represents one or more first sets of media items, distinct from a second set of media items, and a second media object that represents one or more second sets of media items. The processing unit is configured to detect an input that includes the movement of a contact on the touch-sensing surface while the focus selector is over the first media object, and in response to the detection of such an input including the movement of a contact on the touch-sensing surface, output a preview of a media item from a first set of media items in accordance with the determination that the input satisfies a media preview criterion that includes a criterion that is satisfied when the input includes an increase in the characteristic intensity of the contact that exceeds a media preview intensity threshold while the focus selector is over the first media object, and in response to the detection of the movement of the contact, stop outputting the preview of a media item from the first set of media items and output a preview of a media item from a second set of media items, and in accordance with the determination that the input does not satisfy the media preview criterion, move the first media object and the second media object on the display in accordance with the movement of the contact on the touch-sensing surface.

[0036] Thus, an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface is provided with a faster, more efficient method and interface for previewing media content, thereby improving effectiveness, efficiency, and user satisfaction with such a device. Such a method and interface may complement or replace conventional methods for previewing media content.

[0037] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The method includes displaying on a display a first portion of paginated content in a user interface, the first portion of paginated content being a portion of a first section of the multiple sections, the first portion of paginated content being a portion of a consecutive preceding page within the first section and a consecutive subsequent page within the first section; detecting a first portion of the input, including detecting contact on the touch-sensitive surface while a focus selector is within a first predetermined area of ​​the displayed first portion of the paginated content on the display; and, in response to detecting a first portion of the input, lifting off the contact from the touch-sensitive surface before the characteristic intensity of the contact reaches a first threshold intensity. The following are included: replacing a displayed first portion of paginated content on the display with a second portion of paginated content that includes pages contiguously adjacent to the first portion of paginated content, in accordance with a determination that a first portion of its input satisfies a first content navigation criterion, which includes criteria that the device detects are satisfied when detected; and displaying a page number in a subsequent page in the first section, or a page number in a subsequent page in the first section, while the focus selector is within a first default area of ​​the displayed first portion of paginated content, in accordance with a determination that a first portion of its input satisfies a second content navigation criterion, which includes criteria that the device detects are satisfied when the characteristic intensity of its contact increases and exceeds a first intensity threshold.

[0038] According to some embodiments, the electronic device comprises a display unit configured to display content items, a touch-sensitive surface unit configured to receive user input, one or more sensor units configured to detect the intensity of contact with the touch-sensitive surface unit, and a processing unit connected to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit enables on the display the display of a first portion of paginated content in a user interface, which comprises a plurality of sections, each section comprising a plurality of pages, and a first portion of the paginated content is a portion of a first section of the plurality of sections, and the first portion of the paginated content is located between a consecutive preceding page and a consecutive subsequent page in the first section, and includes detecting a first portion of the input, including detecting contact on the touch-sensitive surface while the focus selector is within a first default area of ​​the displayed first portion of the paginated content on the display, and in response to detecting a first portion of the input, it devices the lift-off of the contact from the touch-sensitive surface before the characteristic intensity of the contact reaches a first threshold intensity. The device is configured to enable explicit display of page numbers in subsequent pages of a first section, or in subsequent pages of a first section, while the focus selector is within a first default area of ​​the first portion of the paginated content, according to a determination that a first portion of its input satisfies a first content navigation criterion, which includes criteria that are satisfied when the device detects that the characteristic intensity of the contact has increased and exceeded a first intensity threshold, according to a determination that a first portion of its input satisfies a second content navigation criterion, which includes criteria that are satisfied when the device detects that the characteristic intensity of the contact has increased and exceeded a first intensity threshold.

[0039] There is a need for electronic devices with improved methods and interfaces for displaying contextual information associated with a target location on a map. Such methods and interfaces optionally complement or replace conventional methods for displaying contextual information associated with a target location on a map. Such methods reduce the frequency, extent, and / or nature of user input, creating a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and extend the time interval between battery charges.

[0040] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact on the touch-sensitive surface. This method includes displaying a view of a map containing a plurality of points of interest within a first user interface on the display. This method further includes detecting that the characteristic intensity of the contact on the touch-sensitive surface has increased to exceed a preview threshold intensity while the view of the map containing the plurality of points of interest is displayed and while the focus selector is at the location of each point of interest. This method further includes zooming the map to display contextual information near each point of interest in response to the detection that the characteristic intensity of the contact has increased to exceed a preview threshold intensity. This method further includes detecting each input, which includes detecting that the characteristic intensity of the contact on the touch-sensitive surface has decreased after zooming in on the map and fallen below a predetermined intensity threshold; continuing to display context information near each target point in response to the detection of each input, which includes detecting the decrease in the characteristic intensity of the contact, according to the determination that the characteristic intensity of the contact had increased to exceed the context-maintaining intensity threshold before the input was detected; and stopping the display of context information near the target point and redisplaying the map view containing multiple target points, according to the determination that the characteristic intensity of the contact had not increased to exceed the context-maintaining intensity threshold before the input was detected.

[0041] According to some embodiments, the electronic device includes a display unit, a touch-sensing surface unit, one or more sensor units for detecting the intensity of contact on the touch-sensing surface unit, and a processing unit connected to the display unit, the touch-sensing surface unit, and one or more sensor units. This processing unit is configured to enable the display of a map view including multiple target points within a first user interface on the display unit, and while the map view including multiple target points is enabled and the focus selector is at the location of each target point, it detects when the characteristic intensity of contact on the touch-sensitive surface increases and exceeds the preview threshold intensity, and in response to the detection of the increased characteristic intensity of contact exceeding the preview threshold intensity, it zooms the map and displays context information near each target point, and after zooming the map, it detects when the characteristic intensity of contact on the touch-sensitive surface decreases and falls below a predetermined intensity threshold, and in response to the detection of the decreased characteristic intensity of contact, it continues to enable the display of context information near each target point according to the determination that the characteristic intensity of contact increased and exceeded the context maintenance intensity threshold before the input was detected, and stops enabling the display of context information near the target point and redisplays the map view including multiple target points according to the determination that the characteristic intensity of contact did not increase to exceed the context maintenance intensity threshold before the input was detected.

[0042] Therefore, an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface provides a faster and more efficient method and interface for displaying contextual information associated with a point of interest in a map, thereby improving effectiveness, efficiency, and user satisfaction with such a device. Such a method and interface can complement or replace conventional methods for displaying contextual information associated with a point of interest in a map.

[0043] There is a need for electronic devices with improved methods and interfaces for zooming in on a map and displaying contextual information near a point of interest. Such methods and interfaces optionally complement or replace conventional methods for zooming in on maps. Such methods reduce the frequency, extent, and / or nature of user input, creating a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and extend the time interval between battery charges.

[0044] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact on the touch-sensitive surface. This method includes simultaneously displaying a map view including a plurality of points of interest and a context region, separate from the map view, including representations of a first point of interest from the plurality of points of interest and representations of a second point of interest from the plurality of points of interest, within a user interface on the display. This method further includes detecting, while the map view and the context region are simultaneously displayed on the display, that the characteristic intensity of contact on the touch-sensitive surface has increased and exceeded its respective intensity threshold. The method further includes, upon detection that the characteristic intensity of contact has increased and exceeded its respective intensity threshold, zooming the map view to display the contextual information of the first target location in the map view near the first target location, according to the determination that the focus selector was at the location of the representation of the first target location in the context area when it was detected that the characteristic intensity of contact has increased and exceeded its respective intensity threshold; and upon detection that the characteristic intensity of contact has increased and exceeded its respective intensity threshold when it was determined that the focus selector was at the location of the representation of the second target location in the context area, zooming the map view to display the contextual information of the second target location in the map view near the second target location.

[0045] According to some embodiments, the electronic device includes a display unit, a touch sensing surface unit, one or more sensor units for detecting the intensity of contact on the touch sensing surface, and a processing unit connected to the display unit, the touch sensing surface unit, and the one or more sensor units, which enables simultaneous display of a map view including multiple target points within a user interface on the display unit, and a context area separate from the map view, including representations of a first target point from multiple target points and representations of a second target point from multiple target points, and while the map view and context area are being simultaneously displayed on the display unit, it detects when the characteristic intensity of contact on the touch sensing surface increases and exceeds the respective intensity thresholds. The system includes a processing unit configured to, upon detection that the characteristic intensity of contact has increased and exceeded its respective intensity threshold, zoom the map view to display the context information for the first target point in the map view near the first target point, in accordance with the determination that the focus selector was at the location of the representation of the first target point in the context area when the characteristic intensity of contact has increased and exceeded its respective intensity threshold, and upon detection that the characteristic intensity of contact has increased and exceeded its respective intensity threshold when the focus selector was at the location of the representation of the second target point in the context area, zoom the map view to display the context information for the second target point in the map view near the second target point.

[0046] Thus, an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface is provided with a faster, more efficient method and interface for zooming in on a map, thereby improving effectiveness, efficiency, and user satisfaction with such a device. Such a method and interface complements or replaces conventional methods for zooming in on maps.

[0047] There is a need for electronic devices with improved methods and interfaces for displaying and using menus containing contact information. Such methods and interfaces optionally complement or replace conventional methods for displaying and using menus containing contact information. Such methods reduce the number, extent, and / or nature of user input, creating a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and extend the time interval between battery charges.

[0048] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The method includes: displaying a first user interface on a display that includes a plurality of selectable objects associated with contact information; detecting an input, including detecting contact on the touch-sensitive surface while the plurality of selectable objects are displayed and while a focus selector is in the location corresponding to each selectable object; and, in response to the detection of the input, displaying a menu for each selectable object that includes contact information for each selectable object superimposed on the first user interface that includes the plurality of selectable objects, according to a determination that the detection of the input includes detecting an increase in the intensity of the contact that satisfies an intensity criterion, including a criterion that is satisfied when the characteristic intensity of the contact increases and exceeds a respective intensity threshold; and replacing the display of the first user interface that includes the plurality of selectable objects with a display of a second user interface associated with each selectable object, according to a determination that the detection of the input includes detecting a lift-off of the contact that does not satisfy its intensity criterion.

[0049] According to some embodiments, the electronic device includes a display unit configured to display a user interface, a touch-sensitive surface unit configured to receive user input, one or more sensor units configured to detect the intensity of contact with the touch-sensitive surface unit, and a processing unit connected to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable the display of a first user interface including multiple selectable objects associated with contact information on the display unit, and while the display of multiple selectable objects is enabled and the focus selector is in the location corresponding to each selectable object, it detects an input, and in response to the detection of the input, it enables the display of a menu for each selectable object including the contact information of each selectable object superimposed on the first user interface including multiple selectable objects, according to a determination that the detection of the input includes detecting an increase in the intensity of the contact that satisfies an intensity criterion including a criterion that is satisfied when the characteristic intensity of the contact increases and exceeds the respective intensity threshold, and in response to the detection of the input, it enables the display of a menu for each selectable object including the contact information of each selectable object superimposed on the first user interface including multiple selectable objects, according to a determination that the detection of the input includes detecting the lift-off of the contact without satisfying the intensity criterion.

[0050] Thus, a faster and more efficient method and interface is provided for displaying a menu containing contact information on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface, thereby improving effectiveness, efficiency, and user satisfaction with such a device. Such a method and interface may complement or replace conventional methods for displaying a menu containing contact information.

[0051] According to some embodiments, an electronic device includes a display, a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, one or more processors, memory, and one or more programs, the one or more programs being stored in memory and configured to be executed by one or more processors, and the one or more programs including instructions for performing or causing to perform any of the operations described herein. According to some embodiments, a computer-readable storage medium is having instructions stored therein, and when executed by an electronic device having a display, a touch-sensitive surface, and optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, the instructions cause the device to perform or cause to perform any of the operations described herein. According to some embodiments, an electronic device having a graphical user interface display, a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, memory, and one or more processors for executing one or more programs stored in memory includes one or more of the elements shown in any of the methods described herein, and these elements are updated in response to input as described in any of the methods described herein. According to some embodiments, the electronic device includes a display, a touch-sensitive surface, and optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, and means for performing or bringing to perform any of the actions described herein. According to some embodiments, an information processing device for use in an electronic device comprising a display and a touch-sensitive surface, and optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, includes means for performing or bringing to perform any of the actions described herein.

[0052] Thus, an electronic device comprising a display, a touch-sensitive surface, and optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface is provided with a faster, more efficient method and interface for operating a user interface, thereby improving effectiveness, efficiency, and user satisfaction with such a device. Such a method and interface may complement or replace conventional methods for operating a user interface. [Brief explanation of the drawing]

[0053] For a better understanding of the various embodiments described, please refer to the following “Description of Embodiments” in conjunction with the following drawings, where similar reference numbers refer to corresponding parts throughout those drawings.

[0054] [Figure 1A] This is a block diagram showing a portable multifunctional device with a touch-sensitive display, according to several embodiments.

[0055] [Figure 1B] This is a block diagram showing exemplary components for event handling according to several embodiments.

[0056] [Figure 2] Several embodiments of a portable multifunctional device equipped with a touchscreen are shown.

[0057] [Figure 3] This is a block diagram of an exemplary multifunctional device comprising a display and a touch-sensitive surface, according to several embodiments.

[0058] [Figure 4A] The following are exemplary user interfaces for application menus in portable multifunction devices according to several embodiments.

[0059] [Figure 4B]This document describes exemplary user interfaces for a multifunctional device having a touch-sensitive surface separate from a display, according to several embodiments.

[0060] [Figure 4C] Several exemplary dynamic intensity thresholds are shown according to various embodiments. [Figure 4D] Several exemplary dynamic intensity thresholds are shown according to various embodiments. [Figure 4E] Several exemplary dynamic intensity thresholds are shown according to various embodiments.

[0061] [Figure 5A] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5B] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5C] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5D] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5E] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5F]The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5G] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5H] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5I] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5J] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5K] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5L] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5M]The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5N] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5O] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5P] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5Q] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5R] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5S] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5T]The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5U] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5V] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5W] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5X] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5Y] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5Z] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AA]The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AB] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AC] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AD] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AE] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AF] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AG] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AH]The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AI] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AJ] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AK] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AL] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AM] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AN] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AO]The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AP] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AQ] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AR] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AS] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AT] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AU] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AV]The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments. [Figure 5AW] The following are exemplary user interfaces for quickly invoking one of several actions associated with each application, without first launching each application, according to some embodiments.

[0062] [Figure 6A] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6B] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6C] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6D] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6E] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6F] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6G] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6H]The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6I] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6J] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6K] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6L] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6M] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6N] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6O] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6P] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6Q] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6R]The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6S] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6T] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6U] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6V] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6W] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6X] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6Y] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6Z] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AA] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AB]The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AC] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AD] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AE] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AF] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AG] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AH] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AI] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AJ] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AK] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AL]The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AM] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AN] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AO] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AP] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AQ] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AR] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments. [Figure 6AS] The following are exemplary user interfaces for navigating between a first user interface and a second user interface, according to several embodiments.

[0063] [Figure 7A] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7B] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7C]The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7D] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7E] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7F] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7G] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7H] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7I] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7J] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7K] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7L] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7M] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7N]An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7O] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7P] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7Q] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7R] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7S] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7T] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7U] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7V] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7W] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7X] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7Y]An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7Z] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7AA] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7AB] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7AC] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7AD] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7AE] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7AF] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7AG] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7AH] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7AI] An exemplary user interface for navigating within and between applications according to some embodiments is shown. [Figure 7AJ]The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7AK] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7AL] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7AM] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7AN] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7AO] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7AP] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments. [Figure 7AQ] The following are exemplary user interfaces for navigating within and between applications, according to several embodiments.

[0064] [Figure 8A] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8B] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8C] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8D]An exemplary user interface for dynamically changing the background of a user interface according to some embodiments is shown. [Figure 8E] An exemplary user interface for dynamically changing the background of a user interface according to some embodiments is shown. [Figure 8F] An exemplary user interface for dynamically changing the background of a user interface according to some embodiments is shown. [Figure 8G] An exemplary user interface for dynamically changing the background of a user interface according to some embodiments is shown. [Figure 8H] An exemplary user interface for dynamically changing the background of a user interface according to some embodiments is shown. [Figure 8I] An exemplary user interface for dynamically changing the background of a user interface according to some embodiments is shown. [Figure 8J] An exemplary user interface for dynamically changing the background of a user interface according to some embodiments is shown. [Figure 8K] An exemplary user interface for dynamically changing the background of a user interface according to some embodiments is shown. [Figure 8L] An exemplary user interface for dynamically changing the background of a user interface according to some embodiments is shown. [Figure 8M] An exemplary user interface for dynamically changing the background of a user interface according to some embodiments is shown. [Figure 8N] An exemplary user interface for dynamically changing the background of a user interface according to some embodiments is shown. [Figure 8O] An exemplary user interface for dynamically changing the background of a user interface according to some embodiments is shown. [Figure 8P]The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8Q] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8R] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8S] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8T] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8U] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8V] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8W] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8X] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8Y] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8Z] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AA] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AB]The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AC] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AD] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AE] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AF] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AG] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AH] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AI] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AJ] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AK] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AL] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AM] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AN]The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AO] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AP] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AQ] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AR] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AS] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AT] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AU] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AV] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AW] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AX] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AY] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8AZ]The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8BA] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8BB] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8BC] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8BD] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8BE] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8BF] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8BG] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8BH] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8BI] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8BJ] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 8BK] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments.

[0065] [Figure 9A] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9B] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9C] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9D] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9E] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9F] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9G] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9H] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9I] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9J] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9K] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9L] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9M] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9N] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9O] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9P] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9Q] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9R] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments. [Figure 9S] The following are exemplary user interfaces for dynamically changing the background of a user interface, according to several embodiments.

[0066] [Figure 10A] The following are exemplary user interfaces for toggling between different actions based on input contact characteristics, according to several embodiments. [Figure 10B] The following are exemplary user interfaces for toggling between different actions based on input contact characteristics, according to several embodiments. [Figure 10C] The following are exemplary user interfaces for toggling between different actions based on input contact characteristics, according to several embodiments. [Figure 10D] The following are exemplary user interfaces for toggling between different actions based on input contact characteristics, according to several embodiments. [Figure 10E]The following are exemplary user interfaces for toggling between different actions based on input contact characteristics, according to several embodiments. [Figure 10F] The following are exemplary user interfaces for toggling between different actions based on input contact characteristics, according to several embodiments. [Figure 10G] The following are exemplary user interfaces for toggling between different actions based on input contact characteristics, according to several embodiments. [Figure 10H] The following are exemplary user interfaces for toggling between different actions based on input contact characteristics, according to several embodiments. [Figure 10I] The following are exemplary user interfaces for toggling between different actions based on input contact characteristics, according to several embodiments. [Figure 10J] The following are exemplary user interfaces for toggling between different actions based on input contact characteristics, according to several embodiments. [Figure 10K] The following are exemplary user interfaces for toggling between different actions based on input contact characteristics, according to several embodiments. [Figure 10L] The following are exemplary user interfaces for toggling between different actions based on input contact characteristics, according to several embodiments.

[0067] [Figure 11A] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11B] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11C] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11D] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11E] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11F] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11G] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11H] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11I] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11J] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11K] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11L] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11M] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11N]The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11O] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11P] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11Q] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11R] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11S] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11T] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11U] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11V] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11W] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11X]The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11Y] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11Z] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AA] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AB] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AC] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AD] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AE] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AF] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AG] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AH]The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AI] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AJ] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AK] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AL] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AM] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AN] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AO] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AP] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AQ] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AR]The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AS] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments. [Figure 11AT] The following are exemplary user interfaces for launching an application or displaying a quick action menu, according to several embodiments.

[0068] [Figure 12A] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12B] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12C] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12D] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12E] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12F] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12G] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12H] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12I] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12J] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12K] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12L] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12M] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12N] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12O] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12P] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12Q] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12R] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12S] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12T] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12U] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12V] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12W] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 12X] The following are exemplary user interfaces for selecting a default option from a menu or displaying a menu of options, according to several embodiments.

[0069] [Figure 13A] This flowchart illustrates a method for visually obscuring several user interface objects according to several embodiments. [Figure 13B] This flowchart illustrates a method for visually obscuring several user interface objects according to several embodiments. [Figure 13C] This flowchart illustrates a method for visually obscuring several user interface objects according to several embodiments.

[0070] [Figure 14] This is a functional block diagram of an electronic device according to several embodiments.

[0071] [Figure 15A] This flowchart illustrates a method for navigating between a first user interface and a second user interface according to several embodiments. [Figure 15B] This flowchart illustrates a method for navigating between a first user interface and a second user interface according to several embodiments. [Figure 15C] This flowchart illustrates a method for navigating between a first user interface and a second user interface according to several embodiments. [Figure 15D] This flowchart illustrates a method for navigating between a first user interface and a second user interface according to several embodiments. [Figure 15E] This flowchart illustrates a method for navigating between a first user interface and a second user interface according to several embodiments. [Figure 15F] This flowchart illustrates a method for navigating between a first user interface and a second user interface according to several embodiments. [Figure 15G] This flowchart illustrates a method for navigating between a first user interface and a second user interface according to several embodiments.

[0072] [Figure 16] This is a functional block diagram of an electronic device according to several embodiments.

[0073] [Figure 17A] This flowchart illustrates a method for providing supplementary information (e.g., previews and menus) according to several embodiments. [Figure 17B]This flowchart illustrates a method for providing supplementary information (e.g., previews and menus) according to several embodiments. [Figure 17C] This flowchart illustrates a method for providing supplementary information (e.g., previews and menus) according to several embodiments. [Figure 17D] This flowchart illustrates a method for providing supplementary information (e.g., previews and menus) according to several embodiments. [Figure 17E] This flowchart illustrates a method for providing supplementary information (e.g., previews and menus) according to several embodiments. [Figure 17F] This flowchart illustrates a method for providing supplementary information (e.g., previews and menus) according to several embodiments. [Figure 17G] This flowchart illustrates a method for providing supplementary information (e.g., previews and menus) according to several embodiments. [Figure 17H] This flowchart illustrates a method for providing supplementary information (e.g., previews and menus) according to several embodiments.

[0074] [Figure 18] This is a functional block diagram of an electronic device according to several embodiments.

[0075] [Figure 19A] This flowchart illustrates a method for dynamically changing the background of a user interface according to several embodiments. [Figure 19B] This flowchart illustrates a method for dynamically changing the background of a user interface according to several embodiments. [Figure 19C] This flowchart illustrates a method for dynamically changing the background of a user interface according to several embodiments. [Figure 19D] This flowchart illustrates a method for dynamically changing the background of a user interface according to several embodiments. [Figure 19E]This flowchart illustrates a method for dynamically changing the background of a user interface according to several embodiments. [Figure 19F] This flowchart illustrates a method for dynamically changing the background of a user interface according to several embodiments.

[0076] [Figure 20] This is a functional block diagram of an electronic device according to several embodiments.

[0077] [Figure 21A] This flowchart illustrates a method for dynamically changing the background of a user interface according to several embodiments. [Figure 21B] This flowchart illustrates a method for dynamically changing the background of a user interface according to several embodiments. [Figure 21C] This flowchart illustrates a method for dynamically changing the background of a user interface according to several embodiments.

[0078] [Figure 22] This is a functional block diagram of an electronic device according to several embodiments.

[0079] [Figure 23A] This flowchart illustrates a method for toggling between different actions based on input contact characteristics, according to several embodiments. [Figure 23B] This flowchart illustrates a method for toggling between different actions based on input contact characteristics, according to several embodiments. [Figure 23C] This flowchart illustrates a method for toggling between different actions based on input contact characteristics, according to several embodiments.

[0080] [Figure 24] This is a functional block diagram of an electronic device according to several embodiments.

[0081] [Figure 25A]This flowchart illustrates a method for launching an application or displaying a quick action menu, according to several embodiments. [Figure 25B] This flowchart illustrates a method for launching an application or displaying a quick action menu, according to several embodiments. [Figure 25C] This flowchart illustrates a method for launching an application or displaying a quick action menu, according to several embodiments. [Figure 25D] This flowchart illustrates a method for launching an application or displaying a quick action menu, according to several embodiments. [Figure 25E] This flowchart illustrates a method for launching an application or displaying a quick action menu, according to several embodiments. [Figure 25F] This flowchart illustrates a method for launching an application or displaying a quick action menu, according to several embodiments. [Figure 25G] This flowchart illustrates a method for launching an application or displaying a quick action menu, according to several embodiments. [Figure 25H] This flowchart illustrates a method for launching an application or displaying a quick action menu, according to several embodiments.

[0082] [Figure 26] This is a functional block diagram of an electronic device according to several embodiments.

[0083] [Figure 27A] This flowchart illustrates a method for displaying a menu having a list of items arranged based on the location of user interface objects, according to several embodiments. [Figure 27B] This flowchart illustrates a method for displaying a menu having a list of items arranged based on the location of user interface objects, according to several embodiments. [Figure 27C] This flowchart illustrates a method for displaying a menu having a list of items arranged based on the location of user interface objects, according to several embodiments. [Figure 27D] This flowchart illustrates a method for displaying a menu having a list of items arranged based on the location of user interface objects, according to several embodiments. [Figure 27E] This flowchart illustrates a method for displaying a menu having a list of items arranged based on the location of user interface objects, according to several embodiments.

[0084] [Figure 28] This is a functional block diagram of an electronic device according to several embodiments.

[0085] [Figure 29A] This flowchart illustrates a method for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 29B] This flowchart illustrates a method for selecting a default option from a menu or displaying a menu of options, according to several embodiments. [Figure 29C] This flowchart illustrates a method for selecting a default option from a menu or displaying a menu of options, according to several embodiments.

[0086] [Figure 30] This is a functional block diagram of an electronic device according to several embodiments.

[0087] [Figure 31A] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31B]The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31C] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31D] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31E] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31F] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31G] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31H] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31I] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31J] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31K] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31L] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31M]The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31N] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31O] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31P] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 31Q] The following are exemplary user interfaces for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments.

[0088] [Figure 32A] This flowchart illustrates a method for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 32B] This flowchart illustrates a method for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 32C] This flowchart illustrates a method for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 32D] This flowchart illustrates a method for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments. [Figure 32E] This flowchart illustrates a method for visually distinguishing intensity-sensing objects within a user interface, according to several embodiments.

[0089] [Figure 33] This is a functional block diagram of an electronic device according to several embodiments.

[0090] [Figure 34A] This flowchart illustrates a method for visually distinguishing objects within a user interface according to several embodiments. [Figure 34B] This flowchart illustrates a method for visually distinguishing objects within a user interface according to several embodiments. [Figure 34C] This flowchart illustrates a method for visually distinguishing objects within a user interface according to several embodiments.

[0091] [Figure 35] This is a functional block diagram of an electronic device according to several embodiments.

[0092] [Figure 36A] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36B] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36C] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36D] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36E] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36F] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36G] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36H] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36I] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36J] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36K] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36L] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36M] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36N] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36O] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36P]The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36Q] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36R] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36S] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36T] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36U] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments. [Figure 36V] The following are exemplary user interfaces for previewing media content (e.g., audio content and / or video content) according to several embodiments.

[0093] [Figure 37A] This flowchart illustrates a method for previewing media content according to several embodiments. [Figure 37B] This flowchart illustrates a method for previewing media content according to several embodiments. [Figure 37C] This flowchart illustrates a method for previewing media content according to several embodiments. [Figure 37D] This flowchart illustrates a method for previewing media content according to several embodiments. [Figure 37E] This flowchart illustrates a method for previewing media content according to several embodiments. [Figure 37F] This flowchart illustrates a method for previewing media content according to several embodiments. [Figure 37G] This flowchart illustrates a method for previewing media content according to several embodiments. [Figure 37H] This flowchart illustrates a method for previewing media content according to several embodiments.

[0094] [Figure 38] This is a functional block diagram of an electronic device according to several embodiments.

[0095] [Figure 39A] The following are exemplary user interfaces for navigating paginated content according to several embodiments. [Figure 39B] The following are exemplary user interfaces for navigating paginated content according to several embodiments. [Figure 39C] The following are exemplary user interfaces for navigating paginated content according to several embodiments. [Figure 39D] The following are exemplary user interfaces for navigating paginated content according to several embodiments. [Figure 39E] The following are exemplary user interfaces for navigating paginated content according to several embodiments. [Figure 39F] The following are exemplary user interfaces for navigating paginated content according to several embodiments. [Figure 39G] The following are exemplary user interfaces for navigating paginated content according to several embodiments. [Figure 39H]The following are exemplary user interfaces for navigating paginated content according to several embodiments. [Figure 39I] The following are exemplary user interfaces for navigating paginated content according to several embodiments. [Figure 39J] The following are exemplary user interfaces for navigating paginated content according to several embodiments. [Figure 39K] The following are exemplary user interfaces for navigating paginated content according to several embodiments.

[0096] [Figure 39L] The following are illustrative flowcharts illustrating the actions that occur in response to received input (or parts thereof, singular or plural) that meet various content navigation criteria, according to several embodiments.

[0097] [Figure 40A] This flowchart illustrates a method for navigating paginated content according to several embodiments. [Figure 40B] This flowchart illustrates a method for navigating paginated content according to several embodiments. [Figure 40C] This flowchart illustrates a method for navigating paginated content according to several embodiments. [Figure 40D] This flowchart illustrates a method for navigating paginated content according to several embodiments. [Figure 40E] This flowchart illustrates a method for navigating paginated content according to several embodiments.

[0098] [Figure 41] This is a functional block diagram of an electronic device according to several embodiments.

[0099] [Figure 42A]The following are exemplary user interfaces for displaying contextual information associated with a target location in a map, according to several embodiments. [Figure 42B] The following are exemplary user interfaces for displaying contextual information associated with a target location in a map, according to several embodiments. [Figure 42C] The following are exemplary user interfaces for displaying contextual information associated with a target location in a map, according to several embodiments. [Figure 42D] The following are exemplary user interfaces for displaying contextual information associated with a target location in a map, according to several embodiments. [Figure 42E] The following are exemplary user interfaces for displaying contextual information associated with a target location in a map, according to several embodiments. [Figure 42F] The following are exemplary user interfaces for displaying contextual information associated with a target location in a map, according to several embodiments. [Figure 42G] The following are exemplary user interfaces for displaying contextual information associated with a target location in a map, according to several embodiments. [Figure 42H] The following are exemplary user interfaces for displaying contextual information associated with a target location in a map, according to several embodiments. [Figure 42I] The following are exemplary user interfaces for displaying contextual information associated with a target location in a map, according to several embodiments. [Figure 42J] The following are exemplary user interfaces for displaying contextual information associated with a target location in a map, according to several embodiments. [Figure 42K] The following are exemplary user interfaces for displaying contextual information associated with a target location in a map, according to several embodiments. [Figure 42L]The following are exemplary user interfaces for displaying contextual information associated with a target location in a map, according to several embodiments. [Figure 42M] The following are exemplary user interfaces for displaying contextual information associated with a target location in a map, according to several embodiments. [Figure 42N] The following are exemplary user interfaces for displaying contextual information associated with a target location in a map, according to several embodiments.

[0100] [Figure 43A] This flowchart illustrates a method for displaying contextual information associated with a target point in a map, according to several embodiments. [Figure 43B] This flowchart illustrates a method for displaying contextual information associated with a target point in a map, according to several embodiments. [Figure 43C] This flowchart illustrates a method for displaying contextual information associated with a target point in a map, according to several embodiments. [Figure 43D] This flowchart illustrates a method for displaying contextual information associated with a target point in a map, according to several embodiments.

[0101] [Figure 44] This is a functional block diagram of an electronic device according to several embodiments.

[0102] [Figure 45A] The following are exemplary user interfaces for zooming in on a map and displaying contextual information near a target location, according to several embodiments. [Figure 45B] The following are exemplary user interfaces for zooming in on a map and displaying contextual information near a target location, according to several embodiments. [Figure 45C] The following are exemplary user interfaces for zooming in on a map and displaying contextual information near a target location, according to several embodiments. [Figure 45D] The following are exemplary user interfaces for zooming in on a map and displaying contextual information near a target location, according to several embodiments. [Figure 45E] The following are exemplary user interfaces for zooming in on a map and displaying contextual information near a target location, according to several embodiments. [Figure 45F] The following are exemplary user interfaces for zooming in on a map and displaying contextual information near a target location, according to several embodiments. [Figure 45G] The following are exemplary user interfaces for zooming in on a map and displaying contextual information near a target location, according to several embodiments. [Figure 45H] The following are exemplary user interfaces for zooming in on a map and displaying contextual information near a target location, according to several embodiments. [Figure 45I] The following are exemplary user interfaces for zooming in on a map and displaying contextual information near a target location, according to several embodiments. [Figure 45J] The following are exemplary user interfaces for zooming in on a map and displaying contextual information near a target location, according to several embodiments. [Figure 45K] The following are exemplary user interfaces for zooming in on a map and displaying contextual information near a target location, according to several embodiments. [Figure 45L] The following are exemplary user interfaces for zooming in on a map and displaying contextual information near a target location, according to several embodiments.

[0103] [Figure 46A] This flowchart illustrates a method, according to several embodiments, for zooming in on a map to display contextual information near a target location. [Figure 46B] This flowchart illustrates a method, according to several embodiments, for zooming in on a map to display contextual information near a target location. [Figure 46C] This flowchart illustrates a method, according to several embodiments, for zooming in on a map to display contextual information near a target location. [Figure 46D] This flowchart illustrates a method, according to several embodiments, for zooming in on a map to display contextual information near a target location.

[0104] [Figure 47] This is a functional block diagram of an electronic device according to several embodiments.

[0105] [Figure 48A] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48B] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48C] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48D] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48E] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48F] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48G] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48H] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48I] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48J]The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48K] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48L] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48M] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48N] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48O] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48P] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48Q] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48R] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48S] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48T] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48U] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48V] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48W]The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48X] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48Y] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48Z] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48AA] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48BB] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48CC] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48DD] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments. [Figure 48EE] The following are exemplary user interfaces for displaying a menu containing contact information, according to several embodiments.

[0106] [Figure 49A] This flowchart illustrates a method for displaying a menu containing contact information, according to several embodiments. [Figure 49B] This flowchart illustrates a method for displaying a menu containing contact information, according to several embodiments. [Figure 49C] This flowchart illustrates a method for displaying a menu containing contact information, according to several embodiments. [Figure 49D] This flowchart illustrates a method for displaying a menu containing contact information, according to several embodiments. [Figure 49E] This flowchart illustrates a method for displaying a menu containing contact information, according to several embodiments. [Figure 49F] This flowchart illustrates a method for displaying a menu containing contact information, according to several embodiments.

[0107] [Figure 50] This is a functional block diagram of an electronic device according to several embodiments. [Modes for carrying out the invention]

[0108] The methods, devices, and GUIs described herein provide visual and / or tactile feedback that makes the manipulation of user interface objects more efficient and intuitive for the user.

[0109] In some embodiments, in a system where a trackpad or touchscreen display senses a range of touch intensity including one or more specific intensity values ​​(e.g., more than simple on / off, binary intensity determination), the user interface provides a response (e.g., a visual and / or haptic cue) indicating the intensity of the touch within that range. This provides the user with a continuous response to the force or pressure of the user's touch, thereby providing the user with richer and more intuitive visual and / or haptic feedback. For example, such a continuous force response gives the user the experience of being able to preview an action by lightly pressing and / or reach a default user interface state corresponding to that action by pressing deeply.

[0110] In some embodiments, with respect to a device having a touch-sensing surface that senses a range of contact intensity, multiple contact intensity thresholds are monitored by the device and different responses are mapped to the contact intensity thresholds.

[0111] In some embodiments, for a device having a touch-sensing surface that senses a range of contact intensity, the device provides additional functionality by enabling the user to perform complex actions with a single continuous touch.

[0112] In some embodiments, for devices having a touch-sensitive surface that senses a range of contact intensity, the device provides additional functionality that complements conventional functions. For example, additional functionality provided by intensity-based input (e.g., user interface previews and / or navigation shortcuts provided by light and / or deep press gestures) is seamlessly integrated with conventional functionality provided by conventional tap and swipe gestures. Users can continue to use conventional gestures to perform conventional functions (e.g., tapping an application icon on the home screen to launch the corresponding application) without accidentally activating the additional functionality. However, users can also easily discover, understand, and use intensity-based input and additional functionality (e.g., pressing an application icon on the home screen brings up the application's quick action menu, and lifting off a menu item performs an action within that application).

[0113] Several different techniques for manipulating a user interface are described herein. Using one or more of these techniques (optionally and in combination with each other) helps provide a user interface that intuitively delivers additional information and functionality to the user. Using one or more of these techniques (optionally and in combination with each other) reduces the number, extent, and / or nature of user input, resulting in a more efficient human-machine interface. This allows users to use touch-sensitive devices faster and more efficiently. For battery-operated devices, these improvements result in power savings and longer battery charging intervals. Example device

[0114] Here, embodiments shown in the accompanying drawings will be referred to in detail. The following detailed description includes numerous specific details to provide a complete understanding of the various embodiments described. However, it will be apparent to those skilled in the art that the various embodiments described can be practiced without these specific details. In other examples, well-known methods, procedures, components, circuits, and networks are not described in detail so as not to unnecessarily obscure the aspects of the embodiments.

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

[0116] The terminology used in the descriptions of the various embodiments described herein is intended solely to describe specific embodiments and not to limit them. Where used in the descriptions of the various embodiments and in the appended final claims, the singular forms “a,” “an,” and “the” are intended to include the plural form unless the context otherwise explicitly indicates. Where used herein, the term “and / or” should also be understood to refer to and include all possible combinations of one or more of the related enumerated items. Furthermore, where used herein, the terms “includes,” “comprises,” and / or “comprising” specify the presence of a described feature, integer, step, operation, element, and / or component, but not to exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0117] As used herein, the term "if" is interpreted, at its discretion, as contextual, to mean "when," "upon," "in response to determining," or "in response to detecting." Similarly, the phrases "if it is determined" or "if (a stated condition or event) is detected" are interpreted, at its discretion, as contextual, to mean "upon determining," "in response to determining," "upon detecting (the stated condition or event)," or "in response to detecting (the stated condition or event)."

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

[0119] The following discussion describes an electronic device comprising a display and a touch-sensitive surface. However, it should be understood that this electronic device optionally includes one or more other physical user interface devices such as a physical keyboard, mouse, and / or joystick.

[0120] This device generally supports a variety of applications, including drawing applications, presentation applications, word processing applications, website creation applications, disk authoring applications, spreadsheet applications, game applications, telephone applications, video conferencing applications, email applications, instant messaging applications, training support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music playback applications, and / or digital video playback applications.

[0121] Various applications running on this 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 the corresponding information displayed on the device are optionally adjusted and / or changed from one application to the next, and / or within each application. In this manner, the device's common physical architecture (such as a touch-sensitive surface) optionally supports various applications that have an intuitive and transparent user interface for the user.

[0122] Here, we turn our attention to embodiments of portable devices equipped with touch-sensitive displays. Figure 1A is a block diagram of a portable multifunction device 100 equipped with a touch-sensitive display system 112 according to several embodiments. The touch-sensitive display system 112 is sometimes referred to as a “touchscreen” for convenience, and sometimes simply as a touch-sensitive display. Device 100 includes a memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input or control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more intensity sensors 165 for detecting the intensity of contact on Device 100 (for example, on a touch-sensitive surface such as the touch-sensitive display system 112 of Device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on Device 100 (for example, generating tactile output on a touch-sensitive surface such as the touch-sensitive display system 112 of Device 100 or the touchpad 355 of Device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0123] As used herein and in the claims, the term “tactile output” means a physical displacement of the device relative to its previous position, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, which will be detected by the user through the user’s sense of touch. For example, in a situation where the device or a component of the device is in contact with the touch-sensitive surface of the user (e.g., the user’s fingers, palm, or other part of their hand), the tactile output generated by the physical displacement is interpreted by the user as a tactile sensation corresponding to a perceived change in the physical properties of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) may be optionally interpreted by the user as a “down-click” or “up-click” of a physical actuator button. In some cases, the user may feel a tactile sensation such as a “down-click” or “up-click” even when there is no movement of a physical actuator button associated with a touch-sensitive surface that is physically pressed (e.g., displaced) by the user’s movement. As another example, movement of a touch-sensitive surface can be optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. Such user interpretations of touch are based on the user's individual sensory perception, but there are many touch sensory perceptions common to the majority of users. Therefore, when a tactile output is described as corresponding to a user's specific sensory perception (e.g., "up-click," "down-click," "roughness"), unless otherwise stated, the generated tactile output corresponds to the physical displacement of the device or its components that produce the described sensory perception of a typical (or average) user.

[0124] Device 100 is merely one embodiment of a portable multifunction device, and it should be understood that Device 100 may optionally have more or fewer components than those shown, or may optionally have two or more components in combination, or may optionally have different configurations or arrangements of components. The various components shown in Figure 1A are implemented in hardware, software, firmware, or a combination thereof, including one or more signal processing and / or application-specific integrated circuits.

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

[0126] Using the peripheral interface 118, the input and output peripherals of this device can be connected to the CPU(s) 120 and memory 102. One or more processors 120 run or execute various software programs and / or instruction sets stored in memory 102 in order to perform various functions for device 100 and to perform data processing.

[0127] In some embodiments, the peripheral interface 118, the CPU(s) 120, and the 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.

[0128] The RF (radio frequency) circuit 108 transmits and receives RF signals, also known as electromagnetic signals. The RF circuit 108 converts electrical signals to electromagnetic signals, or electromagnetic signals to electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes, but is 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 identification module (SIM) card, memory, and other well-known circuits for performing the above functions. The RF circuit 108 optionally communicates wirelessly with networks such as the Internet, also known as the Internet of Things (WWW), intranets such as cellular telephone networks and / or wireless networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and other devices.Wireless communication uses one of several communication standards, protocols, and technologies at will. These communication standards, protocols, and technologies include Global System for Mobile Communications (GSM), Extended Data GSM Environment (EDGE), High-Speed ​​Downlink Packet Connection (HSDPA), High-Speed ​​Uplink Packet Connection (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), Long-Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth®, Wireless Fidelity (Wi-Fi)® (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and / or IEEE 802.11b). Examples of suitable communication protocols include, but are not limited to, 802.11n), Voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Use Extension (SIMPLE), Instant Messaging and Pleasance Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocols, including communication protocols not yet developed as of the filing date of this document.

[0129] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into human audible sound waves. The audio circuit 110 also receives the electrical signal converted from the sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data and sends the audio data to the peripheral interface 118 for processing. The audio data is optionally taken in by the peripheral interface 118 from memory 102 and / or RF circuit 108, and / or sent back to memory 102 and / or RF circuit 108. In some embodiments, the audio circuit mechanism 110 further includes a headset jack (e.g., 212 in Figure 2). The headset jack provides an interface between the audio circuit 110 and a detachable audio input / output peripheral, such as output-only headphones or a headset that has both output (e.g., headphones for one or both ears) and input (e.g., a microphone).

[0130] The I / O subsystem 106 connects the input / output peripherals of device 100, such as the touch-sensitive display system 112 and other input or control devices 116, to the 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 haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. One or more input controllers 160 receive / transmit electrical signals to / from the other input or control devices 116. The other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller(s) 160 are optionally connected to (or not connected to) any of the following: a keyboard, an infrared port, a USB port, a stylus, and / or a pointer device such as a mouse. One or more buttons (e.g., 208 in Figure 2) optionally include up / down buttons for adjusting the volume of speaker 111 and / or microphone 113. One or more buttons optionally include push buttons (e.g., 206 in Figure 2).

[0131] The touch-sensitive display system 112 provides input and output interfaces between the device and the user. The display controller 156 receives and / or transmits electrical signals to and from the touch-sensitive display system 112. The touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively referred to as “graphics”). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term “affordance” means a user-interactive graphical user interface object (for example, a graphical user interface object configured to respond to input directed to that 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, or other user interface controls.

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

[0133] The touch-sensitive display system 112 optionally uses LCD (liquid crystal display) technology, LPD (polymer light-emitting display) technology, or LED (light-emitting diode) technology, but other display technologies are used in other embodiments. The touch-sensitive display system 112 and the display controller 156 optionally detect touch and any movement or interruption using any of several currently known or future-developed touch-sensing technologies, including but not limited to capacitive technology, resistive technology, infrared technology, and surface ultrasonic technology, as well as other proximity sensors or other elements for determining one or more contact points with the touch-sensitive display system 112. In one exemplary embodiment, projected mutual capacitance sensing technology is used, as seen in iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, California.

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

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

[0136] Device 100 also includes a power system 162 for supplying power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., a battery, alternating current (AC)), a recharge 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 within the portable device.

[0137] Device 100 also optionally includes one or more optical sensors 164. Figure 1A shows an optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106. The optical sensor(s) 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The optical sensor(s) 164 receives light from the environment projected through one or more lenses and converts that light into data representing an image. In use with an imaging module 143 (also referred to as a camera module), the optical sensor(s) 164 optionally captures still images and / or video. In some embodiments, the optical sensor is located on the back of device 100, opposite the touch-sensitive display system 112 on the front of the device, so that the touchscreen can be used as a viewfinder for acquiring still images and / or video. In some embodiments, a separate light sensor is positioned on the front of the device to capture the user's image (for example, for taking selfies, or for the user to conduct a video conference while viewing other video conference participants on a touchscreen).

[0138] Device 100 also optionally includes one or more contact strength sensors 165. Figure 1A shows a contact strength sensor coupled to a strength sensor controller 159 in the I / O subsystem 106. The contact strength sensor(s) 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, pressure-power sensors, optical force sensors, capacitive touch-sensing surfaces, or other strength sensors (e.g., sensors used to measure the force (or pressure) of contact on a touch-sensing surface). The contact strength sensor(s) 165 receives contact strength information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact strength sensor is located juxtaposed with or in close proximity to the touch-sensing surface (e.g., touch-sensing display system 112). In some embodiments, at least one contact strength sensor is located on the back of Device 100, opposite the touchscreen display system 112 located on the front of Device 100.

[0139] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows a proximity sensor 166 connected to a peripheral interface 118. Alternatively, the proximity sensor 166 is connected to an input controller 160 in the I / O subsystem 106. In some embodiments, when the multifunction device is positioned near the user's ear (for example, when the user is making a phone call), the proximity sensor is turned off and the touch-sensitive display system 112 is disabled.

[0140] Device 100 also optionally includes one or more tactile output generators 167. Figure 1A shows a tactile output generator connected to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator(s) 167 optionally includes one or more electroacoustic devices, such as a speaker or other sound component, and / or electromechanical devices that convert energy into linear motion, such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output component (e.g., a component that converts an electrical signal into a tactile output on the device). The tactile output generator(s) 167 receives a tactile feedback generation command from the tactile feedback module 133 and generates a tactile output on device 100 that can be sensed by the user of device 100. In some embodiments, at least one tactile output generator is positioned juxtaposed with or adjacent to a touch-sensing surface (e.g., a touch-sensing display system 112) and optionally generates a tactile output by moving the touch-sensing surface vertically (e.g., inward / outward from the surface of device 100) or laterally (e.g., in the forward / backward direction on the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is positioned on the back of device 100, opposite the touch-sensing display system 112 which is positioned on the front of device 100.

[0141] Device 100 also optionally includes one or more accelerometers 168. Figure 1A shows an accelerometer 168 connected to a peripheral interface 118. Alternatively, the accelerometer 168 is optionally connected to an input controller 160 in the I / O subsystem 106. In some embodiments, information is displayed on a touchscreen display in portrait or landscape view based on an analysis of data received from one or more accelerometers. Device 100 optionally includes, as needed, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information about the location and orientation of Device 100 (e.g., portrait or landscape), in addition to the accelerometer(s) 168.

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

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

[0144] The communication module 128 facilitates communication with other devices via one or more external ports 124 and includes various software components for processing data received by the RF circuit 108 and / or external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire®, etc.) are adapted to connect to other devices directly or indirectly via a network (e.g., the Internet, Wi-Fi, etc.). In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors identical or similar to and / or compatible with the 30-pin connector used in certain iPhone®, iPod Touch®, and iPad® devices of Apple Inc., located in Cupertino, California. In some embodiments, the external ports are Lightning connectors identical or similar to and / or compatible with the Lightning® connector used in certain iPhone®, iPod Touch®, and iPad® devices of Apple Inc., located in Cupertino, California.

[0145] The contact / motion module 130 optionally detects contact with the touch-sensitive display system 112 (in conjunction with the display controller 156) and contact with other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection (e.g., by a finger or stylus), such as determining whether contact has occurred (e.g., detecting a finger being lowered), determining the intensity of contact (e.g., the force or pressure of contact, or a substitute for the force or pressure of contact), determining whether there is movement of contact, tracking movement across the touch-sensitive surface (e.g., detecting an event of dragging one or more fingers), and determining whether contact has stopped (e.g., detecting a finger being lifted or an interruption of contact). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of a contact point represented by a series of contact data optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These operations optionally apply to a single contact (e.g., one finger or stylus contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / movement module 130 and the display controller 156 detect contact on the touchpad.

[0146] The contact / movement module 130 optionally detects gesture input from the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or intensity of detected contact). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture involves detecting a finger-down event, followed by a finger-lift-off event at the same location (or substantially the same location) as the finger-down event (e.g., at the icon's position). In another embodiment, detecting a finger swipe gesture on the touch-sensitive surface involves detecting a finger-down event, followed by one or more finger-drag events, and then a finger-up (lift-off) event. Similarly, stylus taps, swipes, drags, and other gestures are also optionally detected by detecting specific contact patterns of the stylus.

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

[0148] In some embodiments, the graphics module 132 stores data representing the graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes specifying the graphics to be displayed, along with coordinate data and other graphic property data, as needed from an application or the like, and generates screen image data to be output to the display controller 156.

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

[0150] The text input module 134 is optionally a component of the graphics module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other applications that require text input).

[0151] The GPS module 135 determines the device's location and provides this information for use in various applications (for example, to the telephone 138 for use in location-based dialing, to the camera 143 as picture / video metadata, and to applications that provide location-based services such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0152] Application 136 optionally includes the following modules (or sets of instructions), or subsets or supersets thereof: ● Contact module 137 (sometimes called address book or contact list), ●Telephone module 138, ●Video conferencing module 139, ● Email client module 140, ● Instant messaging (IM) module 141, ●Training support module 142, ● Camera module 143 for still images and / or video images, ●Image management module 144, ● Browser module 147, ●Calendar module 148, ● A widget module 149 optionally includes one or more of the following: weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6. ●Widget creation module 150 for creating user-created widget 149-6, ● Search module 151, ●Optionally, a video and music playback module 152 consisting of a video playback module and a music playback module, ●Memo Module 153, ●Map module 154 and / or ● Online video module 155.

[0153] Examples of other applications 136 that may be optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, Java®-enabled applications, encryption, digital rights management, speech recognition, and speech duplication.

[0154] Together with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the contact module 137 includes executable instructions for managing an address book or contact list (stored, for example, in the application internal state 192 of the contact module 137 in memory 102 or memory 370), which includes adding and removing names(s) from the address book, associating telephone numbers(single or multiple), email addresses(single or multiple), addresses(single or multiple), or other information with names, associating images with names, classifying and sorting names, providing telephone numbers and / or email addresses to initiate and / or facilitate communication by telephone 138, video conferencing 139, email 140, or IM 141, and so on.

[0155] The telephone module 138, together with the RF circuit 108, audio circuit 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, includes executable commands for inputting a series of characters corresponding to a telephone number, accessing one or more telephone numbers in the address book 137, modifying the entered telephone number, dialing each telephone number, conducting a conversation, and disconnecting the connection or ending the call when the conversation is complete. As described above, wireless communication may optionally use any of several communication standards, protocols, and technologies.

[0156] The video conferencing module 139, together with an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, a touch-sensitive display system 112, a display controller 156, one or more optical sensors 164, an optical sensor controller 158, a contact module 130, a graphics module 132, a text input module 134, a contact list 137, and a telephone module 138, includes executable commands for initiating, conducting, and ending a video conference between the user and one or more other participants according to the user's instructions.

[0157] The email client module 140, together with the RF circuit 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, includes executable commands for creating, sending, receiving, and managing emails according to user instructions. Together with the image management module 144, the email client module 140 makes it very easy to create still images or videos captured by the camera module 143 and send them via email.

[0158] The instant messaging module 141, together with the RF circuit 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, includes executable instructions for inputting a series of characters corresponding to an instant message, modifying entered characters, sending the corresponding instant message (e.g., using the Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocol for phone-based instant messaging, or using XMPP, SIMPLE, Apple Push Notification Service (APN), or IMPS for internet-based instant messaging), receiving instant messages, and displaying received instant messages. In some embodiments, transmitted and / or received instant messages optionally include graphics, photographs, audio files, video files, and / or other attachments, as supported by MMS and / or Enhanced Messaging Services (EMS). As used herein, “instant messaging” refers to both phone-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, APN, or IMPS).

[0159] The training support module 142, together with the RF circuit 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 playback module 146, includes executable commands for creating training (e.g., with time, distance, and / or calorie consumption targets), communicating with training sensors (in sports devices and smartwatches), receiving training sensor data, measuring sensors used to monitor training, selecting and playing music for training, and displaying, storing, and transmitting training data.

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

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

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

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

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

[0165] The widget creation module 150, together with the RF circuit 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, includes executable instructions for creating widgets (for example, converting user-specified portions of a web page into widgets).

[0166] The search module 151, together with the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, and the text input module 134, includes executable instructions for searching for text, music, sounds, 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) according to user instructions.

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

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

[0169] The map module 154, together with the RF circuit 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, includes executable instructions for receiving, displaying, modifying, and storing maps and map-associated data (e.g., driving directions, data about stores and other points of interest in or near a specific location, and other location-based data).

[0170] The online video module 155, together with the touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, includes executable instructions for enabling a user to access, view, receive (e.g., by streaming and / or downloading), play (e.g., on the touchscreen 112, or wirelessly or on an external display connected via external port 124) a specific online video, send emails containing links to that specific online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, an instant messaging module 141, rather than the email client module 140, is used to send links to specific online videos.

[0171] Each of the modules and applications identified above corresponds to an executable instruction set and a method of this application (e.g., a method performed by a computer and other information processing methods described herein) for performing one or more of the above functions. These modules (i.e., instruction sets) do not need to be implemented as separate software programs, procedures, or modules, and therefore various subsets of these modules can be optionally combined or rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the identified modules and data structures described above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.

[0172] In some embodiments, device 100 is a device in which the operation of a default set of functions on the device is performed exclusively via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for the operation of device 100, the number of physical input control devices (such as push buttons, dials, and similar devices) on device 100 is optionally reduced.

[0173] A default set of functions, performed exclusively via the touchscreen and / or touchpad, optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 from any user interface displayed on the device 100 to the main menu, home menu, or root menu. In such embodiments, the “menu button” is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.

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

[0175] The event sorter 170 receives event information and determines the application 136-1 and the application view 191 of application 136-1 to which the event information will be distributed. The event sorter 170 includes an event monitor 171 and an event dispatcher module 174. In some embodiments, application 136-1 includes an application internal state 192 indicating the current application view(s) displayed on the touch-sensitive display system 112 when the application is active or running. In some embodiments, the device / global internal state 157 is used by the event sorter 170 to determine which application is currently active, and the application internal state 192 is used by the event sorter 170 to determine the application view 191 to which the event information will be distributed.

[0176] In some embodiments, the application internal state 192 includes additional information such as resume information used when the application 136-1 resumes execution, user interface state information indicating that information is displayed or ready to be displayed by the application 136-1, state queues to allow the user to return to a previous state or view of the application 136-1, and redo / undo queues for actions previously performed by the user.

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

[0178] In some embodiments, the event monitor 171 sends requests to the peripheral device interface 118 at predetermined intervals. In response, the peripheral device interface 118 sends event information. In other embodiments, the peripheral device interface 118 sends event information only when there is a significant event (e.g., exceeding a predetermined noise threshold and / or receiving input for longer than a predetermined time).

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

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

[0181] Another aspect of the user interface associated with an application is a set of views, which may be referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures are performed. The application views (of each application) in which touches are detected optionally correspond to the program level within the application's program hierarchy or view hierarchy. For example, the lowest level view in which touches are detected is optionally called a hit view, and the set of events recognized as appropriate inputs is optionally determined, at least in part, based on the hit view of the initial touch that initiates a touch-based gesture.

[0182] The hit view determination module 172 receives information associated with sub-events of touch-based gestures. If the application has multiple views organized hierarchically, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest-level view where the first sub-event (i.e., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once a hit view is identified by the hit view determination module, the hit view typically accepts all sub-events associated with the same touch or input source that identified it as a hit view.

[0183] The active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognition determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognition determination module 173 determines that all views, including the physical location of the sub-event, are actively involved views, and therefore all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is entirely confined to an area associated with a particular view, higher-level views in the hierarchy will remain actively involved views.

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

[0185] In some embodiments, the operating system 126 includes an event sorter 170. Alternatively, application 136-1 includes an event sorter 170. In yet another embodiment, the event sorter 170 is a standalone module or part of another module stored in memory 102, such as a contact / movement module 130.

[0186] In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each containing instructions for handling touch events occurring within each view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognition units 180. Typically, each application view 191 includes a plurality of event recognition units 180. In other embodiments, one or more of the event recognition units 180 are part of a separate module, such as a user interface kit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, each event handler 190 includes one or more event data 179 received from a data updater 176, an object updater 177, a GUI updater 178, and / or an event sorter 170. The event handler 190 optionally uses or calls the data updater 176, object updater 177, or GUI updater 178 to update the application's internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. In some embodiments, one or more of the data updater 176, object updater 177, and GUI updater 178 are included within each application view 191.

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

[0188] The event receiver 182 receives event information from the event sorter 170. The event information includes, for example, information about sub-events such as touches or movement of touches. Depending on the sub-event, the event information may also include additional information such as the location of the sub-event. When the sub-event involves movement of a touch, the event information may optionally further include the velocity and direction of the sub-event. In some embodiments, an event includes rotation of the device from one direction to another (for example, from portrait orientation to landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also called the device orientation).

[0189] The event comparison unit 184 compares event information with a default event or sub-event definition and determines an event or sub-event, or determines or updates the state of an event or sub-event based on the comparison. In some embodiments, the event comparison unit 184 includes an event definition 186. The event definition 186 includes an event definition (e.g., a default sequence of sub-events), such as event 1 (187-1) and event 2 (187-2). In some embodiments, sub-events within event 187 include, for example, touch start, touch end, touch movement, touch cancellation, and multiple touches. In one embodiment, the definition of event 1 (187-1) is a double tap on a displayed object. A double tap includes, for example, a first touch (touch start) for a predetermined stage on the displayed object, a first lift-off (touch end) for the predetermined stage, a second touch (touch start) for the predetermined stage on the displayed object, and a second lift-off (touch end) for the predetermined stage. In another embodiment, event 2(187-2) is defined as a drag on a displayed object. Dragging includes, for example, touching (or contacting) a predetermined stage on the displayed object, moving the touch across the touch-sensitive display system 112, and lifting off the touch (end of touch). In some embodiments, the event also includes information about one or more associated event handlers 190.

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

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

[0192] If each event recognition unit 180 determines that a series of sub-events does not match any of the events in the event definition 186, each event recognition unit 180 enters an event impossible, event failed, or event terminated state and thereafter ignores subsequent sub-events of the touch-based gesture. In this situation, any other event recognition units that remain active for the hit view continue to track and process the sub-events of the ongoing touch-based gesture.

[0193] In some embodiments, each event recognition unit 180 includes metadata 183 having configurable properties, flags, and / or lists indicating how the event distribution system performs sub-event distribution to event recognition units in which it is actively involved. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists indicating how event recognition units may interact with each other. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists indicating whether sub-events are distributed to various levels within the view hierarchy or program hierarchy.

[0194] In some embodiments, each event recognition unit 180 activates an event handler 190 associated with an event when one or more specific sub-events of an event are recognized. In some embodiments, each event recognition unit 180 distributes event information associated with the event to the event handler 190. Activating the event handler 190 is distinct from sending (and deferring) the sub-events to their respective hit views. In some embodiments, the event recognition unit 180 throws a flag associated with the recognized event, and the event handler 190 associated with the flag catches the flag and performs default processing.

[0195] In some embodiments, the event distribution command 188 includes a sub-event distribution command that distributes event information about a sub-event without activating an event handler. Instead, the sub-event distribution command distributes the event information to an event handler or an actively involved view associated with a set of sub-events. The event handler associated with the set of sub-events or the actively involved view receives the event information and performs predetermined processing.

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

[0197] In some embodiments, the event handler 190 includes or has access to a data updater 176, an object updater 177, and a GUI updater 178. In some embodiments, the data updater 176, the object updater 177, and the GUI updater 178 are included in one module of their respective applications 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0198] The aforementioned discussion of event processing for user touch on a touch-sensitive display also applies to other forms of user input for operating the multifunction device 100 using input devices, but it will be understood that not all of this begins on a touchscreen. For example, mouse movements and mouse button presses optionally matched to single or multiple keyboard presses or holds, touch movements such as taps, drags, and scrolls on a touchpad, pen stylus input, device movement, verbal communication, detected eye movements, biometric input, and / or any combination thereof may be optionally used as inputs corresponding to sub-events that define the event to be recognized.

[0199] Figure 2 shows a portable multifunctional device 100 having a touchscreen (e.g., the touch-sensitive display system 112 in Figure 1A) according to several embodiments. The touchscreen optionally displays one or more graphics within the user interface (UI) 200. In embodiments described later and in this embodiment, the user can select one or more graphics by making gestures on the graphics using, for example, one or more fingers 202 (not shown in the figure to an exact scale) or one or more styluses 203 (not shown in the figure to an exact scale). In some embodiments, the selection of one or more graphics occurs when the user discontinues contact with one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward, and / or downward), and / or rolling of a finger in contact with the device 100 (from right to left, left to right, upward, and / or downward). In some implementations or situations, accidental contact with a graphic does not select the graphic; for example, if the gesture corresponding to selection is a tap, a swipe gesture over an application icon does not arbitrarily select the corresponding application.

[0200] Device 100 also optionally includes one or more physical buttons, such as a "Home" or menu button 204. As previously stated, the menu button 204 is optionally used to navigate to any application 136 within a set of applications that can be optionally run on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on a touchscreen display.

[0201] In some embodiments, device 100 includes a touchscreen display, a menu button 204, a push button 206 for turning the device on / off and locking the device, one or more volume buttons 208, a subscriber identification module (SIM) card slot 210, a headset jack 212, and an external docking / charging port 124. The push button 206 is optionally used to turn the device on / off by pressing and holding the button for a predetermined time interval, and to lock and / or unlock the device or initiate an unlocking process by pressing and releasing the button before the predetermined time interval has elapsed. In some embodiments, device 100 also accepts verbal input through a microphone 113 to activate or deactivate certain functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contact on the touch-sensitive display system 112 and / or one or more tactile output generators 167 for generating user tactile output for Device 100.

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

[0203] Each of the elements of Figure 3 identified above is optionally stored in one or more of the aforementioned memory devices. Each of the modules identified above corresponds to an instruction set for performing the function described above. The identified modules or programs (i.e., instruction sets) described above do not need to be implemented as separate software programs, procedures, or modules; therefore, in various embodiments, various subsets of these modules are optionally combined or rearranged in other ways. In some embodiments, memory 370 optionally stores subsets of the identified modules and data structures described above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.

[0204] Here, we turn our attention to embodiments of user interfaces ("UI") that are optionally implemented on the portable multifunction device 100.

[0205] Figure 4A shows an exemplary user interface for an application menu on a portable multifunction device 100 according to several embodiments. A similar user interface may be optionally implemented on the device 300. In some embodiments, the user interface 400 includes the following elements, or subsets or supersets thereof. ●Signal strength indicators (single or multiple) for wireless communication (single or multiple) such as cellular and Wi-Fi signals 402, ●Time 404, ●Bluetooth indicator 405, ●Battery status indicator 406, ●Tray 408 contains the following icons for frequently used applications. ○Optionally including an indicator 414 for the number of missed calls or voicemail messages, an icon 416 of the phone module 138 labeled "Phone", ○Optionally includes an indicator 410 for the number of unread emails, an icon 418 of the email client module 140 labeled "Mail", ○ Icon 420 of browser module 147, labeled "Browser", and ○ Icon 422 of the video and music playback module 152, also known as the iPod (registered trademark of Apple Inc.) module 152, labeled as "iPod," and ● Icons of other applications below ○ Icon 424 of IM module 141, labeled "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" ○ Icon 434 of the stock widget 149-2, labeled "Stocks" ○ Icon 436 of map module 154, labeled "Map" ○ Icon 438 of weather widget 149-1, labeled "Weather" ○ Icon 440 of the alarm clock widget 149-4, labeled "Clock" ○ Icon 442 of training support module 142, labeled "Training Support" ○ Icon 444 of memo module 153, labeled as "Memo", and ○ An icon 446 for a configuration application or module that provides access to settings related to device 100 and its various applications 136.

[0206] It will be understood that the icon labels shown in Figure 4A are merely illustrative. For example, in some embodiments, the icon 422 for the video and music playback module 152 is labeled "Music" or "Music Player." Other labels are used optionally for various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to that application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to that particular application icon.

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

[0208] Figure 4B shows an exemplary user interface on a device (e.g., device 300 in Figure 3) that has a touch-sensitive surface 451 (e.g., tablet or touchpad 355 in Figure 3) separate from the display 450. Many of the following embodiments will be described with reference to input on the touchscreen display 112 (when the touch-sensitive surface and display are combined), but in some embodiments, the device detects input on a touch-sensitive surface separate from the display, as shown in Figure 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in Figure 4B) has a principal axis (e.g., 452 in Figure 4B) corresponding to a principal axis (e.g., 453 in Figure 4B) on the display (e.g., 450). In these embodiments, the device detects contact (e.g., 460 and 462 in Figure 4B) with the touch-sensitive surface 451 at locations corresponding to each location on the display (e.g., 460 corresponds to 468 and 462 corresponds to 470 in Figure 4B). Thus, when the touch-sensitive surface is separate from the display, user input detected by the device on the touch-sensitive surface (e.g., 451 in Figure 4B) (e.g., touches 460 and 462, and their movement) is used by the device to operate the user interface on the display of the multifunction device (e.g., 450 in Figure 4B). It should be understood that a similar method may be optionally used for other user interfaces described herein.

[0209] In addition, while the following embodiments are primarily illustrated with reference to finger input (e.g., finger touch, finger tap gesture, finger swipe gesture, etc.), it will be understood that in some embodiments, one or more of these finger inputs may be replaced by input from another input device (e.g., mouse-based input, or stylus input). For example, a swipe gesture may be optionally replaced with a mouse click (e.g., instead of touch), followed by cursor movement along the swipe path (e.g., instead of touch movement). In another embodiment, a tap gesture may be optionally replaced with a mouse click (e.g., instead of touch detection followed by cessation of touch detection), while the cursor is positioned over the location of the tap gesture. Similarly, when multiple user inputs are detected simultaneously, it will be understood that multiple computer mice may be used simultaneously, optionally, or a mouse and finger touch may be used simultaneously.

[0210] As used herein, the term “focus selector” refers to an input element that indicates the current portion of the user interface that the user is interacting with. In implementations including a cursor or other location marker, the cursor functions as a “focus selector” when input (e.g., press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in Figure 3, or touch-sensitive surface 451 in Figure 4B) and the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), and the particular user interface element is adjusted according to the detected input. In some implementations including a touchscreen display (e.g., touch-sensitive display system 112 in Figure 1A, or touchscreen in Figure 4A) that enables direct interaction with user interface elements on the touchscreen display, the contact detected on the touchscreen acts as a “focus selector,” so that when input (e.g., press input by touch) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, that particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one area of ​​the user interface to another without corresponding cursor movement or touch movement on the touchscreen display (for example, by moving focus from one button to another using the tab key or arrow keys). In these implementations, the focus selector moves in accordance with the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector as a whole is a user interface element (or touch on the touchscreen display) controlled by the user to convey the user's intended interaction with the user interface (for example, by instructing the device to interact with the user interface element the user wishes to interact with).For example, when pressure input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the location of the focus selector (e.g., a cursor, touch, or selection box) above each button indicates (unlike other user interface elements displayed on the device's display) that the user is attempting to activate that button.

[0211] As used herein and in the claims, the term “strength” of contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of contact (e.g., finger contact or stylus contact) on the touch-sensitive surface, or a substitute for the force or pressure of contact on the touch-sensitive surface. The strength of contact has a numerical range, including at least four different numerical values, and more typically including hundreds or more different numerical values ​​(e.g., at least 256). The strength of contact is determined (or measured) optionally using various methods and various sensors, or combinations of sensors. For example, one or more sensors placed below or adjacent to the touch-sensitive surface are optionally used to measure the force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average or sum) to determine the estimated force of contact. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the touch-sensitive surface adjacent to the contact, and / or the resistance and / or change in the touch-sensitive surface adjacent to the contact may be optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurement of the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some implementations, the substitute measurement of the force or pressure of the contact is converted to an estimated force or pressure, and this estimated force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). By using the intensity of contact as an attribute of user input, it becomes possible to enable user access to additional device functions that might otherwise be inaccessible in devices of limited size with limited area for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical control such as a knob or button).

[0212] In some embodiments, the contact / movement module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by the user (for example, whether the user has "clicked" on an icon). In some embodiments, at least a subset of the intensity thresholds is determined according to software parameters (for example, the intensity thresholds may not be determined by an activation threshold for a particular physical actuator and may be adjusted without changing the physical hardware of the device 100). For example, the mouse "click" threshold for a trackpad or touchscreen display may be set to one of a range of default thresholds without changing the trackpad or touchscreen display hardware. In addition, in some implementations, the user of the device is provided with software settings to adjust one or more of the set of intensity thresholds (for example, by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds immediately after a system-level click of the "intensity" parameter).

[0213] As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples, or on a set of intensity samples collected within a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) for a predetermined event (e.g., after detection of contact, before detection of lift-off of contact, before or after detection of the start of movement of contact, before detection of the end of contact, before or after detection of an increase in contact intensity, and / or before or after detection of a decrease in contact intensity). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum intensity of the contact, the mean intensity of the contact, the average intensity of the contact, the top 10 percentile values ​​of the contact intensity, half the maximum intensity of the contact, the 90 percent of the maximum intensity of the contact, etc. In some embodiments, the duration of contact is used to determine the characteristic intensity (for example, when the characteristic intensity is the average of the contact intensity over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action was performed by a user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this embodiment, a first action is performed as a result of contact with a characteristic intensity not exceeding the first threshold, a second action is performed as a result of contact with a characteristic intensity exceeding the first intensity threshold but not exceeding the second intensity threshold, and a third action is performed as a result of contact with a characteristic intensity exceeding the second intensity threshold. In some embodiments, the comparison between the characteristic intensity and one or more intensity thresholds is not used to determine whether to perform the first or second action, but rather to determine whether to perform one or more actions (for example, whether to perform each option or to omit the performance of each action).

[0214] In some embodiments, a portion of the gesture is identified for the purpose of determining characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact (e.g., a drag gesture) that transitions from a starting location to an ending location, which is a point where the intensity of the contact increases. In this embodiment, the characteristic intensity of the contact at the ending location may be based not on the entire continuous swipe contact, but only on a portion of the swipe contact (e.g., only the portion of the swipe contact at the ending location). In some embodiments, a smoothing algorithm may be applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm may optionally include one or more of the following: a non-weighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some situations, these smoothing algorithms exclude small increases or decreases in the intensity of the swipe contact in order to determine the characteristic intensity.

[0215] The user interface diagrams described herein include one or more intensity thresholds (e.g., contact detection intensity threshold IT0, light pressure intensity threshold IT0). L (For example, at least initially I L (Higher than) Deep pressure intensity threshold IT D , and / or one or more other intensity thresholds (e.g., I L Lower intensity threshold I HThe system optionally includes various intensity charts showing the current intensity of contact on the touch-sensitive surface. These intensity charts are typically not part of the displayed user interface but are provided to aid in the interpretation of those charts. In some embodiments, the light-pressure intensity threshold corresponds to the intensity at which the device will perform an action typically associated with a physical mouse button or trackpad click. In some embodiments, the deep-pressure intensity threshold corresponds to the intensity at which the device will perform an action different from the action typically associated with a physical mouse button or trackpad click. In some embodiments, if a contact with a characteristic intensity below the light-pressure intensity threshold (for example, above a slight contact detection intensity threshold IT0 below which contact is no longer detected) is detected, the device moves the focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing the action associated with the light-pressure or deep-pressure intensity threshold. In general, unless otherwise specified, these intensity thresholds are consistent across different sets of user interface charts.

[0216] In some embodiments, the device's response to an input detected by the device depends on a criterion based on the contact intensity during the input. For example, for some "light press" inputs, a contact intensity exceeding a first intensity threshold during the input triggers a first response. In some embodiments, the device's response to an input detected by the device depends on a criterion that includes both the contact intensity during the input and a time-based criterion. For example, for some "deep press" inputs, a contact intensity exceeding a second intensity threshold during the input and higher than the first intensity threshold for light presses triggers a second response only if a delay time has elapsed between meeting the first and second intensity thresholds. This delay time is typically less than 200 milliseconds (e.g., 40, 100, or 120 milliseconds, depending on the magnitude of the second intensity threshold, and this delay time increases with increasing second intensity threshold). This delay time helps to avoid accidental deep press inputs. In another embodiment, for some "deep pressure" inputs, there is a sensitivity reduction period that occurs after the time the first intensity threshold is met. During this sensitivity reduction period, the second intensity threshold increases. This temporary increase in the second intensity threshold also helps to avoid accidental deep pressure inputs. For other deep pressure inputs, the response to the detection of the deep pressure input is independent of a time-based criterion.

[0217] In some embodiments, one or more input intensity thresholds and / or corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, application status, intensity application rate, number of simultaneous inputs, user history, environmental factors (e.g., ambient noise), and focus selector position. Exemplary factors are described in U.S. Patent Applications 14 / 399,606 and 14 / 624,296, which are incorporated herein by reference in their entirety.

[0218] For example, FIG. 4C shows a dynamic intensity threshold 480 that varies over time, based in part on the intensity of touch input 476. The dynamic intensity threshold 480 is the sum of two components: a first component 474 that decays over time after a predetermined delay time p1 from when the touch input 476 is first detected, and a second component 478 that tracks the intensity of the touch input 476 over time. The intensity threshold of the first component 474, which has a high initial value, reduces spurious triggering of the "deep press" response while still allowing an immediate "deep press" response when the touch input 476 provides sufficient intensity. The second component 478 reduces triggering of an unintentional "deep press" response as the intensity of the touch input gradually varies. In some embodiments, when the touch input 476 (e.g., at point 481 in FIG. 4C) meets the dynamic intensity threshold 480, a "deep press" response is triggered.

[0219] FIG. 4D shows another dynamic intensity threshold 486 (e.g., intensity threshold I D ). FIG. 4D also shows two other intensity thresholds: a first intensity threshold I H and a second intensity threshold I L . In FIG. 4D, the touch input 484 meets the first intensity threshold I H and the second intensity threshold I L before time p2, but no response is provided until the delay time p2 elapses at time 482. FIG. 4D also shows that the dynamic intensity threshold 486 decays over time. This decay starts at time 488 after a predetermined delay time p1 has elapsed from time 482 (when the response associated with the second intensity threshold I L is triggered). This type of dynamic intensity threshold reduces spurious triggering of the response associated with the dynamic intensity threshold I H or the second intensity threshold I L immediately after or simultaneously with triggering a response associated with a lower intensity threshold, such as the first intensity threshold I D .

[0220] FIG. 4E shows yet another dynamic intensity threshold 492 (e.g., intensity threshold I DFigure 4E shows that after a delay time p2 has elapsed since the first detection of touch input 490, the intensity threshold I L The associated response is triggered. Simultaneously, the dynamic intensity threshold 492 decays after a predetermined delay time p1 has elapsed since the first detection of the touch input 490. Therefore, the intensity threshold I L If the intensity of touch input 490 decreases after triggering the associated response, and then increases without releasing touch input 490, the intensity of touch input 490 will, for example, reach an intensity threshold I L Even if it falls below another intensity threshold, the intensity threshold I D A response associated with this may be triggered (for example, at time 494).

[0221] Light pressure intensity threshold IT L From an intensity below the light pressure intensity threshold IT L and deep pressure intensity threshold IT D The increase in the characteristic intensity of contact between the intensity and the intensity is sometimes referred to as a "light pressure" input. From an intensity below the deep pressure intensity threshold IT, to the deep pressure intensity threshold IT D An increase in the characteristic intensity of contact beyond the intensity threshold IT0 is sometimes referred to as a "deep pressure" input. From an intensity below the contact detection intensity threshold IT0, the contact detection intensity threshold IT0 and the light pressure intensity threshold IT0 are... L An increase in the characteristic intensity of contact between a certain intensity and a certain intensity may be referred to as the detection of contact on the touch surface. A decrease in the characteristic intensity of contact from an intensity above the contact detection intensity threshold IT0 to an intensity below the contact detection intensity threshold IT0 may be referred to as the detection of lift-off of contact from the touch surface. In some embodiments, IT0 is zero. In some embodiments, IT0 is greater than zero. In some figures, shaded circles or ellipses are used to represent the intensity of contact on the touch-sensing surface. In some figures, unshaded circles or ellipses are used to represent each contact on the touch-sensing surface without specifying the intensity of each contact.

[0222] In some embodiments described herein, one or more actions are performed in response to the detection of a gesture including each pressing input, or in response to the detection of each pressing input performed at each (or more) contact, and each of those pressing inputs is detected at least in part on the detection of an increase in the intensity of the contact (or more) above a pressing input threshold intensity. In some embodiments, each action is performed in response to the detection of an increase in the intensity of each contact to an intensity above a pressing input threshold intensity (for example, each action is performed by the "downstroke" of each pressing input). In some embodiments, a pressing input includes an increase in the intensity of each contact to an intensity above a pressing input threshold intensity, followed by a decrease in the intensity of the contact below the pressing input threshold intensity, and each action is performed in response to the detection of a subsequent decrease in the intensity of each contact below the pressing input threshold (for example, each action is performed by the "upstroke" of each pressing input).

[0223] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as “jitter,” and the device defines or selects a hysteresis intensity threshold that has a predetermined correlation with the press input threshold intensity (for example, the hysteresis intensity threshold is X intensity units lower than the press input threshold intensity, or 75%, 90%, or some reasonable ratio of the press input threshold intensity). Thus, in some embodiments, the press input includes an increase in the intensity of each contact to an intensity above the press input threshold intensity, followed by a decrease in the intensity of the contact to a strength below the respective hysteresis intensity threshold, and each action is performed in response to the detection of a subsequent decrease in the intensity of each contact to an intensity below the hysteresis intensity threshold (for example, each action is performed by an “upstroke” of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity from an intensity below a hysteresis intensity threshold to an intensity above a press input intensity threshold, and optionally a decrease in subsequent contact intensity to an intensity below the hysteresis intensity, and each action is performed in response to the detection of that press input (e.g., an increase in contact intensity or a decrease in contact intensity, depending on the situation).

[0224] For the sake of clarity, the description of actions performed in response to a press input associated with a press input threshold strength, or in response to a press input gesture, is optionally triggered in response to the detection of an increase in contact intensity above the press input threshold strength, an increase in contact intensity from below a hysteresis intensity threshold to above the press input threshold strength, a decrease in contact intensity below the press input threshold strength, or a decrease in contact intensity below a hysteresis intensity threshold corresponding to the press input threshold strength. Furthermore, in embodiments described as performing an action in response to the detection of a decrease in contact intensity below the press input intensity threshold, the action is optionally performed in response to the detection of a decrease in contact intensity below a hysteresis intensity threshold that corresponds to and is lower than the press input intensity threshold. As described above, in some embodiments, the triggering of these responses also depends on the satisfaction of a time-based criterion (e.g., a delay time elapses between the satisfaction of a first intensity threshold and the satisfaction of a second intensity threshold). User interface and related processes

[0225] Here, we draw our attention to embodiments of user interfaces "UI" and related processes that may be implemented on an electronic device, such as a portable multifunction device 100 or device 300, which includes a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface.

[0226] In some embodiments, the device is an electronic device comprising a separate display (e.g., display 450) and a separate touch-sensitive surface (e.g., touch-sensitive surface 451). In some embodiments, the device is a portable multifunction device 100, the display is a touch-sensitive display system 112, and the touch-sensitive surface includes a tactile output generator 167 on the display (Figure 1A). For ease of explanation, the embodiments described will be discussed with reference to operations performed on a device comprising the touch-sensitive display system 112. In such embodiments, the focus selector is optionally each finger or stylus contact, a representative point corresponding to each finger or stylus contact (e.g., the centroid of each contact or a point associated with each contact), or the centroid of two or more contacts detected on the touch-sensitive display system 112. However, similar operations are optionally performed on a device comprising the display 450 and the separate touch-sensitive surface 451 in response to the detection of a contact on the touch-sensitive surface 451 while the user interface shown in these figures is displayed on the display 450 together with the focus selector.

[0227] Figures 5A–5AW illustrate exemplary user interfaces for quickly invoking one of several actions associated with each application without first activating each application, according to several embodiments. In some embodiments, this is achieved by detecting user input that can be distinguished (e.g., based on the magnitude of the force applied by the user) from conventional user input used to launch an application, and then providing the user with a menu (e.g., a “Quick Actions Menu”) containing quick action items for each application. In some embodiments, the user interface provides feedback (e.g., visual, auditory, and / or tactile feedback) when the user is about to invoke the quick action menu (e.g., when the user input approaches a strength threshold). This allows the user to modify their input to avoid unintentionally activating the quick action menu. This also helps the user determine the magnitude of the force required to invoke the quick action menu. Exemplary quick action functions are described in Annex A.

[0228] The user interfaces in these figures are used to illustrate the processes described below. Some of the following embodiments are presented with reference to input on a touchscreen display (where the touch-sensing surface and the display are combined), but in some embodiments, the device detects input on a touch-sensing surface 451 that is separate from the display 450, as shown in Figure 4B.

[0229] Figures 5A–5G, 5I–5W, 5Y–5AA, 5AC–5AJ, and 5AL–5AW illustrate an exemplary user interface for a home screen displaying multiple application launch icons (e.g., icons 480, 426, 428, 482, 432, 434, 436, 438, 440, 442, 444, 446, 484, 430, 486, 488, 416, 418, 420, and 424). Each of these launch icons is associated with an application that is activated (e.g., "launched") on the electronic device 100 when an application launch input (e.g., a tap gesture with a maximum intensity below a threshold for calling a quick action menu) is detected. Some of the launch icons are also associated with corresponding quick action menus that are activated on the electronic device when a quick action display input (e.g., a force press gesture with a maximum intensity above a threshold for calling a quick action menu) is detected.

[0230] Figures 5A to 5H illustrate one embodiment in which a user invokes a quick action display menu from the home screen of an electronic device 100 and invokes an action to reply to a recent message. Figure 5A shows a home screen user interface 500 that displays application launch icons for several applications, including a message icon 424 for activating a messaging application. In Figure 5B, the device has an intensity threshold (e.g., IT) required to invoke the quick action menu. L A contact 502 with an intensity below the "hint" threshold (e.g., IT) is detected on the message icon 424. In Figure 5C, the intensity of contact 502 increases and the "hint" threshold (e.g., IT) is lowered. H) is above the threshold but still below the intensity threshold required to invoke the quick action menu. The device notifies the user that it is approaching the intensity required to invoke the quick action menu by blurring other launch icons, moving them further away in virtual z-space (e.g., away from the screen), and providing a hint graphic 503 that emerges from beneath the message icon 424. As shown in Figure 5D, the blurring of the icons, the movement of the icons in z-space, and the hint graphic indicate that the quick action menu threshold (e.g., IT) is exceeded. L It dynamically responds to the increasing intensity of contact 502, which is below ). The hint graphic 503 continues to increase and begins to move away from below the message icon 424.

[0231] In Figure 5E, the intensity of contact 502 increases to the threshold required to invoke the message quick action menu 504 (for example, IT L ) is exceeded. Accordingly, the hint graphic 503 changes to the quick action menu 504, displaying the icons and text of each of the selections 506, 508, 510, and 512 that have become available to the user. The device also provides tactile feedback 513 to inform the user that the quick action menu is now functional. The user has lifted off the touch 502 in Figure 5F, but the quick action menu 504 is still visible on the touchscreen 112 because it is a selection menu. As shown in Figure 5G, the user chooses to respond to Mom's message by tapping on option 508 in the quick action menu 504 (via the touch 514). Accordingly, the device activates the messaging application and displays the user interface 501 containing a text prompt to reply to Mom's message, rather than opening the application to the default user interface (e.g., a view of the last received message).

[0232] Figure 5I shows alternative hint states according to several embodiments, in which the size of the messaging icon 424 increases in response to a contact 516 with an intensity that exceeds the “hint” threshold but falls below the “quick action menu” intensity threshold (for example, simulating the icon coming off the screen and moving towards the user).

[0233] Figures 5J to 5N illustrate one embodiment in which a user initiates a call to a quick action menu, but fails to reach the required intensity threshold. In Figure 5J, device 100 displays the quick action menu within the home screen user interface 500, which is the required intensity threshold (e.g., IT) to initiate the call. L A contact 518 with an intensity below the "hint" threshold (e.g., IT) is detected on the message icon 424. In Figures 5K and 5L, the intensity of the contact 518 increases and the "hint" threshold (e.g., IT) is lowered. H ) is above the threshold required to invoke the quick action menu, but still below the threshold required to invoke the quick action menu. The device notifies the user that it is approaching the threshold required to invoke the quick action menu by dynamically blurring other launch icons, dynamically pushing back other icons in the virtual z space (e.g., shrinking them relative to the message icon 424), and providing a hint graphic 503 that appears from below the message icon 424 and pops out dynamically. However, Figure 5M shows that the threshold required to invoke the quick action menu (e.g., IT L The device shows the user reducing the intensity of contact 518 before it reaches the intensity threshold required to invoke the quick action menu (e.g., IT). In response, the device dynamically reverses the blurring and shrinking of the icon and begins to shrink the hint graphic 503 that was informing the user that the user was approaching the quick action intensity threshold. In Figure 5N, the user lifts off contact 518. The intensity of contact 518 reaches the intensity threshold required to invoke the quick action menu (e.g., IT). L Since the contact 518 was not reached, the device returns the display of the user interface 500 to the same state as before the contact 518 was detected.

[0234] Figures 5O to 5R illustrate one embodiment in which a user performs a gesture that satisfies the quick action display input criteria in a launch icon that does not have an associated quick action menu. In Figure 5O, device 100 displays within the home screen user interface 500 the intensity threshold required to invoke the quick action menu (e.g., IT L A contact 520 with an intensity below the "hint" threshold (e.g., IT) is detected on the activation icon 446. In Figure 5P, the intensity of the contact 520 increases and the "hint" threshold (e.g., IT) is lowered. H ) is above the threshold but still below the intensity threshold required to invoke the quick action menu. The device notifies the user that it is approaching the intensity required to invoke the quick action menu by blurring other launch icons (e.g., dynamically). However, because the settings launch icon 446 is not associated with the quick action menu, the device does not provide a hint graphic (e.g., hint graphic 503 in Figure 5C). In Figure 5Q, the intensity of the contact 520 increases to the threshold required to invoke the quick action menu (e.g., IT L ) is exceeded. However, the device does not display the quick action menu because the settings launch icon 446 is not associated with it. Instead, the device provides negative haptic feedback 522, which is distinguishable from the positive haptic feedback 513 shown in Figure 5E, to indicate to the user that there is no quick action menu for the settings launch icon 446 available. The device then returns the display of the user interface 500 to the state it was in before the contact 520 was detected in Figure 5R, regardless of whether the user has lifted off the contact 520.

[0235] Figures 5S to 5U show one embodiment in which the user invokes the quick action menu via the launch icon in the upper left compartment of the touchscreen 112. In Figure 5J, device 100 has an intensity threshold (e.g., IT) required to invoke the quick action menu displayed in the upper left compartment of the home screen user interface 500. LA contact 524 with an intensity below the "hint" threshold (e.g., IT) is detected on the message icon 424. In Figure 5T, the intensity of the contact 524 increases and the "hint" threshold (e.g., IT) is lowered. H ) is above but still below the intensity threshold required to invoke the quick action menu. The device notifies the user that it is approaching the intensity required to invoke the quick action menu by dynamically blurring other launch icons and providing a hint graphic 503 that appears from below the message icon 424 and pops out dynamically.

[0236] In Figure 5U, the intensity of contact 524 increases to the threshold required to invoke the quick action menu (e.g., IT L) is exceeded. Accordingly, the hint graphic 503 changes to a quick action menu 528, displaying the icons and text of each of the selections 506, 508, 510, and 512 that have become available to the user. However, because the launch icon is displayed on the left side of the screen 112, the quick action menu 528 is aligned to the left edge of the message launch icon 424, rather than to the right edge as shown in Figure 5E (for example, when the message launch icon 424 is displayed on the right side of the touchscreen 112). Similarly, the icons associated with options 506, 508, 510, and 512 are also aligned to the left side of the quick action menu 528, rather than to the right side as shown in Figure 5E. Also, because the launch icon is displayed in the upper half of the touchscreen 112, the quick action menu 528 is displayed below the message launch icon 424, rather than above it as shown in Figure 5E (for example, when the message launch icon 424 is displayed in the lower half of the touchscreen 112). Similarly, because the vertical order of options 506, 508, 510, and 512 is reversed compared to the quick action menu 504 in Figure 5E, the relative distance of each option to the message launch icon 424 is the same in the message quick action menus 504 and 528 (for example, the option to transcribe new message 512 to reply to a recently received message takes precedence over options 506, 508, and 510, so option 512 appears closest to the message launch icon 424 in both quick action menus).

[0237] Figures 5V to 5AF show alternative user inputs for performing various actions after calling up a quick action menu, according to several embodiments.

[0238] In Figure 5V, the user invokes the message quick action menu 528 on the home screen user interface 500 via contact 524, and then, as shown in Figure 5W, slides contact 524 over option 508 to reply to the message from mother. As shown in Figure 5W, the user adjusts the intensity of contact 524 during movement 530 to the quick action menu intensity threshold (e.g., IT L ) does not need to be kept above. The user then lifts off contact 524 while on option 508, and as shown in Figure 5X, the device activates the messaging application and displays user interface 501 containing a text prompt for replying to the mother's message.

[0239] In Figure 5Y, the user invokes the message quick action menu 528 on the home screen user interface 500 via contact 532, and then lifts off contact 532 as shown in Figure 5Z. The user then taps the message launch icon 424 via contact 534 as shown in Figure 5AA. In response, the device activates the associated messaging application by default by displaying the user interface 535, which includes a display of the most recent received messages, as shown in Figure 5AB.

[0240] In Figure 5AC, the user invokes the message quick action menu 528 on the home screen user interface 500 via contact 536, and then lifts off contact 536 as shown in Figure 5AD. The user then taps a location on the touchscreen 112 other than where the message launch icon 424 and the quick action menu 528 are displayed via contact 538, as shown in Figure 5AE. Accordingly, the device clears the quick action menu 528 and returns the display of the user interface 500 to the same state as before contact 524 was detected, as shown in Figure 5AF.

[0241] Figures 5AG to 5AK illustrate one embodiment in which a user performs a preferred action after activating a quick action menu by pressing. In Figure 5AG, device 100 has an intensity threshold (e.g., IT) required to invoke the quick action menu displayed within the home screen user interface 500. L A contact 540 with an intensity below the "hint" threshold (e.g., IT) is detected on the message icon 424. In Figures 5AH and 5AI, the intensity of the contact 540 increases and the "hint" threshold (e.g., IT) is lowered. H ) is above but still below the intensity threshold required to invoke the quick action menu. The device notifies the user that it is approaching the intensity required to invoke the quick action menu by dynamically blurring other launch icons, dynamically pushing back other icons in the virtual z space (for example, shrinking them relative to the message icon 424), and providing a hint graphic 503 that appears from below the message icon 424 and pops out dynamically.

[0242] In Figure 5AJ, the intensity of contact 540 increases to the threshold required to invoke the message quick action menu 504 (for example, IT L ) is exceeded. Accordingly, the hint graphic 503 changes to a quick action menu 504, displaying icons and text for each selection that has become available to the user, such as selection 512 for a preferred action of creating a new message. The device also provides tactile feedback 513 to inform the user that the quick action menu is now functional. After calling up the quick action menu 504, the intensity of the contact 540 continues to increase until a third intensity threshold (e.g., IT) is reached. D ) exceeds this. Accordingly, the device activates the associated messaging application in a preferred state (e.g., corresponding to option 512) by displaying a user interface 541 for writing a new message, as shown in Figure 5AK.

[0243] Figures 5AL to 5AN illustrate one embodiment in which a user invokes a quick action menu in the launch icon of a folder containing launch icons for multiple applications that have associated notifications. In Figure 5AL, device 100 invokes an intensity threshold (e.g., IT) required to invoke the quick action menu. L A contact 542 with an intensity below ) is detected on the networking launch icon 488. The networking launch icon 488 is associated with a folder that, when activated, opens and explicitly displays the launch icons of multiple applications represented on the networking launch icon 488 (e.g., launch icons "F", "T", and "L"). As shown in Figure 5AL, the applications associated with the launch icons stored in the networking folder have seven composite user notifications.

[0244] In Figure 5AM, the intensity of contact 542 increases, reaching the "hint" threshold (e.g., IT). H ) is above the threshold required to invoke the quick action menu, but still below it. The device notifies the user that it is approaching the threshold required to invoke the quick action menu by dynamically blurring other launch icons and providing a hint graphic 543 that appears from below the networking launch icon 488 and pops out dynamically. In Figure 5AN, the intensity of the contact 542 increases, but still below the threshold required to invoke the quick action menu (e.g., IT L ) exceeds. Accordingly, the hint graphic 543 changes to the quick action menu 544, displaying the icons and text for each of the selections 546, 548, 550, and 552 that have become available to the user. The icon displayed for each selection is a graphical representation of the launch icon of the application associated with one or more of these seven notifications. The text displayed for each selection is the name of the notification associated with each application.

[0245] Figures 5AO to 5AQ illustrate one embodiment in which a user invokes a quick action menu on the launch icon of a third-party application. In Figure 5AO, device 100 has an intensity threshold (e.g., IT) required to invoke the quick action menu. L Contact 554 with an intensity below the "hint" threshold (e.g., IT) is detected on the training launch icon 442. In Figure 5AP, the intensity of contact 554 increases and the "hint" threshold (e.g., IT) is lowered. H ) is above the threshold required to invoke the quick action menu, but still below it. The device notifies the user that it is approaching the threshold required to invoke the quick action menu by dynamically blurring other launch icons and providing a hint graphic 556 that appears from below the training launch icon 442 and pops out dynamically. In Figure 5AQ, the intensity of the contact 554 increases, which is above the threshold required to invoke the quick action menu (e.g., IT L ) exceeds. Accordingly, the hint graphic 556 changes to a quick action menu 558, displaying the icons and text of each of the selections 560, 562, 564, 566, and 568 that have become available to the user. Selection 568 allows the user to share a third-party application with a friend (for example, by sending a friend a link to download the third-party application from the application store).

[0246] Figures 5AR to 5AT show one embodiment in which a user invokes a quick action menu via a launch icon in the upper right-hand area of ​​the touchscreen 112. In Figure 5AR, device 100 invokes the intensity threshold (e.g., IT) required to invoke the quick action menu displayed in the upper left-hand area of ​​the home screen user interface 500. L A contact 574 with an intensity below the "hint" threshold (e.g., IT) is detected on the message icon 424. In Figure 5AS, the intensity of contact 570 increases and the "hint" threshold (e.g., IT) is lowered. H) is above but still below the intensity threshold required to invoke the quick action menu. The device notifies the user that it is approaching the intensity required to invoke the quick action menu by dynamically blurring other launch icons and providing a hint graphic 569 that appears from below the message icon 424 and pops out dynamically.

[0247] In Figure 5AT, the intensity of contact 570 increases, reaching the threshold required to invoke the quick action menu (e.g., IT). L ) exceeds. Accordingly, the hint graphic 569 changes to the quick action menu 571, displaying the icons and text of each of the selections 506, 508, 510, and 512 that have become available to the user. Because the launch icon is displayed on the right side of screen 112, the quick action menu 571 is aligned to the right edge of the message launch icon 424. Similarly, the icons associated with options 506, 508, 510, and 512 are also aligned to the right of the quick action menu 571. Because the launch icon is displayed in the upper half of touchscreen 112, the quick action menu 571 is displayed below the message launch icon 424. Similarly, the vertical order of options 506, 508, 510, and 512 is reversed compared to the quick action menu 504 in Figure 5E.

[0248] Figures 5AU to 5AW show one embodiment in which a user can invoke a quick action menu using the launch icon in the lower left compartment of the touchscreen 112. In Figure 5AU, device 100 has an intensity threshold (e.g., IT) required to invoke the quick action menu displayed in the lower left compartment of the home screen user interface 500. L A contact 572 with an intensity below the "hint" threshold (e.g., IT) is detected on the message icon 424. In Figure 5AV, the intensity of contact 572 increases and the "hint" threshold (e.g., IT) is lowered. H) is above but still below the intensity threshold required to invoke the quick action menu. The device notifies the user that it is approaching the intensity required to invoke the quick action menu by dynamically blurring other launch icons and providing a hint graphic 573 that appears from below the message icon 424 and pops out dynamically.

[0249] In Figure 5AW, the intensity of contact 572 increases, reaching the threshold required to invoke the quick action menu (e.g., IT L ) is exceeded. Accordingly, the hint graphic 573 changes to the quick action menu 574, displaying the icons and text of each of the selections 506, 508, 510, and 512 that have become available to the user. Because the launch icon is displayed on the left side of the screen 112, the quick action menu 574 is aligned to the left edge of the message launch icon 424. Similarly, the icons associated with options 506, 508, 510, and 512 are also aligned to the left of the quick action menu 574. Because the launch icon is displayed in the lower half of the touchscreen 112, the quick action menu 574 is displayed above the message launch icon 424. Similarly, the vertical order of options 506, 508, 510, and 512 is the same as in the quick action menu 504 in Figure 5E.

[0250] Figures 6A to 6AS illustrate exemplary embodiments of a user interface that allows a user to efficiently navigate between a first and a second user interface, according to several embodiments. In some embodiments, this is achieved by providing the user with the ability to preview the content of the second user interface without leaving the first user interface, upon detecting user input that can be distinguished (for example, based on the magnitude of force applied by the user) from conventional user input used to navigate between user interfaces. In some embodiments, the user interface provides the user with the ability to perform actions associated with the second user interface while previewing. Some of the subsequent embodiments are presented with reference to an email messaging application, but these methods can be implemented in any number of different applications as described herein.

[0251] The user interfaces in these figures are used to illustrate the processes described below. Some of the following embodiments are presented with reference to input on a touchscreen display (where the touch-sensing surface and the display are combined), but in some embodiments, the device detects input on a touch-sensing surface 451 that is separate from the display 450, as shown in Figure 4B.

[0252] Figures 6A–6E, 6H–6AL, and 6AN–6AS illustrate an exemplary user interface 600 for managing email messages in the inbox. The user interface displays multiple partial views of email messages (e.g., partial views of email messages 602, 604, 606, 608, and 636). Each partial view of an email message is associated with the complete email message, which contains more content than what is displayed in user interface 600 (for example, as shown in Figure 6F, user interface 614 displays additional content associated with the partial view of email message 602 in user interface 600).

[0253] Figures 6A to 6G illustrate one embodiment in which a user previews the content of an email from their email inbox and then navigates to that email with a single gesture. Figure 6A shows the email inbox displaying a partial view of an email message, including a partial view of email message 602. In Figure 6B, device 100 has an intensity threshold (e.g., IT) required to invoke the email preview. L A contact 610 with an intensity below ) is detected on a partial view of the email message 602. In Figure 6C, the intensity of contact 610 increases and exceeds the “hint” threshold (e.g., IT), but the intensity threshold required to invoke the email preview area (e.g., IT) is not reached. L ) remains below the threshold. The device signals that the user is approaching the intensity required to invoke the preview area by blurring the view of other parts of the email (e.g., away from the screen) and beginning to move it further away in virtual z-space. As shown in Figure 6D, the blurring and movement further away in virtual z-space indicate that the preview area invoke threshold (e.g., IT L It dynamically responds to an increase in contact intensity 610 below ).

[0254] In Figure 6E, the intensity of contact 610 increases to the threshold required to invoke the email message preview area 612 (e.g., ITL ) is exceeded. Accordingly, the device displays a preview area 612 above the portion of the partial view of the email message in the user interface 600. This preview displays a view of the email that contains more content than is provided in the partial view of the email message 602. The device also provides tactile feedback 611 to inform the user that its preview area has been activated. The user continues to increase the intensity of contact 610 between Figures 6E and 6F to exceed a third threshold (e.g., IT). D ) is exceeded. Accordingly, the device navigates to the user interface 614, as shown in Figure 6F, to display the full-text email associated with the partial view 602 and the preview area 612. The device also provides tactile feedback 615, which is distinct from tactile feedback 611, to inform the user that navigation to the full-text email has taken place. As shown in Figure 6G, the device maintains the display of the user interface 614 even after the user has finished inputting (e.g., touching 610).

[0255] Figures 6H to 6K illustrate one embodiment in which the user begins to invoke a full-text preview of an email associated with a partial view 602, but does not reach the required intensity threshold. In Figure 6H, device 100 is displayed within the email inbox user interface 600, and the required intensity threshold (e.g., IT) is not reached to invoke the email preview. L A contact 616 on a partial view of email message 602 is detected when the intensity of the contact 616 is below the "hint" threshold (e.g., IT). In Figure 6I, the intensity of the contact 616 increases as the "hint" threshold (e.g., IT) increases. H ) exceeds the strength threshold required to invoke the email preview area (for example, IT L) remains below the threshold. The device signals that the user is approaching the intensity required to invoke the preview area by blurring the view of other parts of the email (e.g., away from the screen) and beginning to move them further back in the virtual z-space. However, Figure 6J shows the intensity threshold required to invoke the preview area (e.g., IT L The user reduces the intensity of contact 616 before reaching the intensity threshold (e.g., IT). In response, the device dynamically reverses the blurring of other partial views and moves them forward in virtual z-space. In Figure 6K, the user lifts off contact 616. The intensity of contact 616 reaches the intensity threshold required to navigate to the full-text view of the email (e.g., IT D Since the condition was not met, the device returns the display of the user interface 600 to the same state as before contact 616 was detected.

[0256] Figures 6L to 6O illustrate one embodiment in which a user can activate a menu of selectable actions associated with an entire email message while viewing a preview of the message (e.g., without leaving the email inbox). In Figure 6L, device 100 displays within the email inbox user interface 600 an intensity threshold (e.g., IT) required to invoke the email preview. L The device detects a contact 618 with an intensity below the preview area call threshold (e.g., IT) on a partial view of the email message 602. In Figure 6M, the device detects when the intensity of contact 618 increases and the preview area call threshold (e.g., IT) is reached. LIn response to detecting that the touch has exceeded a certain point, the device displays the preview area 612. The device also displays a caret 619 to inform the user that the available actions can be revealed by swiping upward on the touchscreen 112. As shown in Figure 6N, the user moves the touch 620 upward on the touchscreen 112. In Figure 6O, in response to detecting the movement of the touch from position 618-a to position 618-b, the preview area 612 moves upward on the display, and the available action options 624, 626, and 628 appear below the preview area. The device also provides tactile feedback 6123, which is distinct from tactile feedback 611 and 615, to inform the user that more actions are available. As shown in Figure 6P, the device maintains the display of the preview area 612 even after the user lifts off the touch 618 because the available action options 624, 626, and 628 have appeared.

[0257] Figures 6Q to 6W illustrate one embodiment in which a user previews the content of an email and then deletes the email with a single gesture. In Figure 6R, device 100 displays an intensity threshold (e.g., IT) required to invoke the email preview within the email inbox user interface 600. L The device detects a contact 630 on a partial view of email message 602 that has an intensity below the preview area call threshold (e.g., IT). In Figure 6R, the device detects that the intensity of contact 630 has increased and the preview area call threshold (e.g., IT) has increased. LIn response to detecting that the touch has exceeded a certain threshold, the preview area 612 is displayed. In Figure 6S, the user begins to move the touch 630 to the left (via movement 632) on the touchscreen 112. Accordingly, in Figures 6T-6U, the preview area 612 moves in response to the touch, gradually revealing the action icon 634 from the bottom of the preview area. As the user continues to move the preview area 612 to the left, the color of the action icon 634 changes, as shown in Figure 6V, notifying the user that the associated action (e.g., deleting an email from the inbox) is active for execution when the touch ends. As shown in Figure 6W, when the user lifts the touch 630 off the touchscreen 112 while the action icon 634 and associated action are active, the device exits the display of the preview area 612 and deletes the associated email. The device also updates the display of the email inbox by deleting the partial view of the associated email and moving the partial views of other emails upward within the user interface 600 to reveal the next partial view of email 636.

[0258] Figures 6X to 6AC illustrate one embodiment in which the user begins deleting an email while in preview mode, but does not reach the position threshold required to activate the delete action. In Figure 6X, device 100 displays within the email inbox user interface 600 the intensity threshold required to invoke the email preview (e.g., IT L The device detects a contact 638 with an intensity below the preview area call threshold (e.g., IT) on a partial view of the email message 602. In Figure 6Y, the device detects that the intensity of contact 638 is increasing and the preview area call threshold (e.g., IT) is being called. LIn response to detecting that the threshold (e.g., IT) has been exceeded, the preview area 612 is displayed. In Figure 6Z, the user begins to move the touch 638 to the left (via movement 640) on the touchscreen 112. Accordingly, in Figure 6AA, the preview area 612 moves with the touch, partially revealing the action icon 634 from below the preview area. In Figure 6AB, the user increases the intensity of the touch 638 to exceed the navigation threshold (e.g., IT). D The device attempts to navigate to the full-text email by exceeding the limit. However, because the user has partially indicated the associated action (e.g., action icon 634), the device locks out the navigation command. (For example, as shown by the action icon 634 which does not change color in Figure 6AB,) because the user has not swiped far enough left in the preview area 612, the device then restores the display of the email inbox user interface 600 to its state before the detection of contact 634, as shown in Figure 6AC, when lifted off.

[0259] Figures 6AD to 6AH illustrate one embodiment in which a user previews an email and begins navigating to the full-text email, but does not reach the required intensity threshold. In Figure 6AD, device 100 displays within the email inbox user interface 600 the intensity threshold required to invoke the email preview (e.g., IT L The device detects a contact 642 having an intensity below the preview area call threshold (e.g., IT) on a partial view of the email message 602. In Figure 6AE, the device detects when the intensity of contact 642 increases and the preview area call threshold (e.g., IT) is reached. L In response to detecting that the intensity of contact 642 has been exceeded, the preview area 612 is displayed. If the user continues to increase the intensity of contact 642, the device increases the size of the preview area 612 in Figure 6AF to notify the user that the intensity is approaching the level required to navigate to the full-text email. However, Figure 6AG shows the intensity threshold required to navigate to the full-text email (e.g., IT DThe device shows the user reducing the intensity of contact 642 before reaching the intensity threshold (e.g., IT) required to navigate to the full text version of the email. In Figure 6AH, the user lifts off contact 642. D Since the condition was not met, the device returns the display of the user interface 600 to the same state as before contact 642 was detected.

[0260] Figures 6AI to 6AM show the preview area display threshold twice, where the user previews the full-text email and then navigates to the full-text email. In Figure 6AI, device 100 crosses the intensity threshold (e.g., IT) required to invoke the email preview displayed within the email inbox user interface 600. L A contact 644 with an intensity below the "hint" threshold (e.g., IT) is detected on a partial view of the email message 602. In Figure 6AJ, the intensity of contact 644 increases as the "hint" threshold (e.g., IT) increases. H ) exceeds the strength threshold required to invoke the email preview area (for example, IT L ) remains below the threshold. The device notifies the user that it is approaching the intensity required to invoke the preview area by blurring the view of other parts of the email and beginning to move it further back in the virtual z space. In Figure 6AE, the device indicates that the intensity of contact 644 is increasing as the preview area indicative threshold (e.g., IT) increases. L In response to detecting that the threshold (e.g., IT) has been exceeded, the preview area 612 is displayed. As shown in Figure 6AL by the dynamic reversal of the blur of the partial view of the email message displayed behind the preview area 612, the user reduces the intensity of contact 644 below the preview area display threshold. However, since the user has not ended contact 644, the device maintains the display of the preview area 612. The user then increases the intensity of contact 644 between Figures 6AL and 6AM to exceed the preview area display threshold (e.g., IT). L) is again exceeded. Accordingly, the device navigates to the user interface 614, as shown in Figure 6AM, to display the email in full text, associated with the partial view 602 and the preview area 612.

[0261] Figures 6AN to 6AS illustrate one embodiment in which a user flags an email with a single gesture by sliding the preview area in the opposite direction, rather than deleting the email. In Figure 6AN, device 100 displays an intensity threshold (e.g., IT) required to invoke the email preview displayed within the email inbox user interface 600. L The device detects a contact 646 with an intensity below the preview area call threshold (e.g., IT) on a partial view of the email message 602. In Figure 6AO, the device detects when the intensity of contact 646 increases and the preview area call threshold (e.g., IT) is reached. L In response to detecting that the touch has exceeded a certain threshold, the preview area 612 is displayed. In Figure 6AP, the user begins to move touch 646 to the right on the touchscreen 112 (via movement 648). Accordingly, in Figures 6AQ to 6AR, the preview area 612 moves with the touch, gradually revealing the action icon 650 from the bottom of the preview area. In Figure 6AR, the color of the action icon 650 changes to indicate that it is active for execution when the associated action (e.g., flagging an email) is finished. Compared to the quick deletion of actions shown in Figures 6Q to 6W, in Figure 6AR, the user does not need to move the preview area 612 far to invoke the flagging action. As shown in Figure 6AS, when the user lifts off touch 646 from the touchscreen 112 while the action icon 650 and associated action are active, the device terminates the display of the preview area 612 and flags the partial view of the email message 602 via a change in the appearance of the indicator icon 652.

[0262] Figures 7A–7AQ illustrate exemplary embodiments of a user interface that allows a user to quickly invoke one of several actions associated with a second application while navigating within a first application, without requiring the user to first activate the second application. According to some embodiments, the exemplary user interfaces shown in Figures 7A–7AQ also allow the user to efficiently navigate between the first and second user interfaces. In some embodiments, when the exemplary user interface detects user input that can be distinguished from conventional user input used for switching between applications (for example, based on the magnitude of the force applied by the user), it provides the user with a menu containing quick action items associated with other user interfaces (for example, other applications) (e.g., "Quick Action Menu"). Similarly, in some embodiments, when this exemplary user interface detects user input that can be distinguished from conventional user input used for navigating between user interfaces (for example, based on the magnitude of the force applied by the user), it allows the user to preview the content of the second user interface without leaving the first user interface. In some embodiments, these exemplary user interfaces provide feedback (e.g., visual, auditory, and / or tactile feedback) when the user is about to invoke a quick action menu (e.g., when user input approaches an intensity threshold). While some of the subsequent embodiments are presented with reference to an email messaging application, in some embodiments, these methods are implemented within any number of different applications as described herein.

[0263] The user interfaces in these figures are used to illustrate the processes described below. Some of the following embodiments are presented with reference to input on a touchscreen display (where the touch-sensing surface and the display are combined), but in some embodiments, the device detects input on a touch-sensing surface 451 that is separate from the display 450, as shown in Figure 4B.

[0264] Figures 7A–7R and 7U–7AP show an exemplary user interface 700 for referencing email messages, including user interface objects associated with a second application. For example, a contact icon 702 is associated with contact information in a contact management application, which is activated (e.g., launched) on the electronic device 100 when an application launch input (e.g., a tap gesture with a maximum intensity below a threshold for calling a quick action menu) is detected. The contact icon 702 is also associated with a quick action menu containing options for performing actions associated with the contact management program when a quick action display input (e.g., a force press gesture with a maximum intensity above a threshold for calling a quick action menu) is detected. Similarly, a date and time 704 is associated with a calendar application, which is activated (e.g., launched) on the electronic device 100 when an application launch input (e.g., a tap gesture with a maximum intensity below a threshold for calling a preview of content associated with the calendar application) is detected. The date and time 704 are also associated with potential new events in the calendar application, which include additional content that becomes available when a preview area display input (e.g., a force press gesture with a maximum intensity above the threshold for invoking the preview area) is detected.

[0265] Figures 7A to 7O illustrate one embodiment in which a user invokes a preview of a calendar event associated with a date in an email, and then invokes a quick action menu of actions associated with a contact management application based on the contact recognized in the email. Figure 7A shows an email message viewing user interface 700 displaying a contact icon 702 and a date and time 704. In Figure 7B, the device invokes an intensity threshold (e.g., IT) required to invoke the preview area of ​​the associated event in the calendar application. L A contact 706 with an intensity below the "hint" threshold (e.g., IT) is detected on the date and time 704. In Figure 7C, the intensity of the contact 706 increases and the "hint" threshold (e.g., IT) is reached. H ) exceeds the intensity threshold required to invoke the event preview area (for example, IT L ) remains below the threshold. The device signals that it is approaching the intensity required to invoke the preview area by beginning to blur other objects in the user interface 700, including the contact icon 702, and increasing the size of the date and time 704 (for example, giving the user the appearance that the date and time are moving in front of other user interface objects in virtual z space). As shown in Figure 7D, the blurring and movement in front in virtual z space trigger the preview area invoke threshold (for example, IT L It dynamically responds to an increase in the intensity of contact 706 that falls below ).

[0266] In Figure 7E, the intensity of contact 706 increases to the threshold required to invoke the event preview area 707 in the calendar application (e.g., IT L) exceeds. Accordingly, the device displays a preview area 707 over a portion of an email message within the user interface 700. The preview area displays a view of a calendar user interface for creating a new event based on date and time information within the email. The device also provides haptic feedback 705 to inform the user that the preview area has been activated. In FIG. 7F, the device maintains the display of the preview area 707 even if the user reduces the intensity of the contact 706 before reaching the intensity threshold (e.g., IT D ) required to navigate to the calendar user interface for creating a new event. In FIG. 7G, the user lifts the contact 706 from the touch screen 112 without reaching the intensity threshold (e.g., IT D ) required to navigate to the calendar user interface. Since the preview area did not include one or more selectable action options, the device stops displaying the preview area 707 and returns the display of the user interface 700 to the same state as before the contact 706 was detected.

[0267] In FIG. 7H, the device detects a contact 708 having an intensity below the intensity threshold (e.g., IT L ) required to invoke the quick action menu on the contact icon 702. In FIG. 7I, the intensity of the contact 708 increases and exceeds a "hint" threshold (e.g., IT H ) but still remains below the intensity threshold required to invoke the quick action menu. The device begins to blur other objects within the user interface 700, including the date and time 704, and increases the size of the contact icon 702 (e.g., providing the user with the appearance that the contact icon is moving forward relative to other user interface objects in virtual z-space) to notify the user that they are approaching the intensity required to invoke the quick action menu. As shown in FIG. 7J, the blurring and the forward movement in virtual z-space are at the quick action menu threshold (e.g., ITL It dynamically responds to an increase in contact intensity 708 below ).

[0268] In Figure 7K, the intensity of contact 708 increases to the threshold required to invoke the quick action menu (e.g., IT L ) exceeds. Accordingly, the contact icon 702 transforms into a quick action menu 710 that displays options to navigate to Harold Goffrey's contact information in the contact management application 712, to call Harold using the phone information associated with the contact management application 714, to send a message to Harold using the contact information associated with the contact management application 716, and to send an email message to Harold using the email address information associated with the contact management application. The device also provides tactile feedback 711, which is distinguishable from tactile feedback 705, to inform the user that the quick action menu is now functional. Because the quick action menu 710 contains selectable options for performing actions, the device maintains the display of the menu even if the user reduces the intensity of contact 708 in Figure 7L and then lifts the contact off the touchscreen 112 in Figure 7M. The user then clears the quick action menu by tapping (via contact 720) on the touchscreen, but elsewhere than where the quick action menu 710 is displayed.

[0269] Figures 7P to 7T illustrate one embodiment in which a user previews the content of a new event and then navigates to the associated user interface within the calendar application with a single gesture. Device 100 has an intensity threshold (e.g., IT) required to invoke the preview of a new event. L A contact 722 with an intensity below the "hint" threshold (e.g., IT...

Claims

1. A method for manipulating user interface objects, An electronic device comprising one or more processors, memory, a touch-sensing surface, a display, and one or more sensors for detecting the intensity of contact with the touch-sensing surface, The first user interface, Including the background, Including a foreground area that overlaps with a portion of the aforementioned background, The foreground area displays a first user interface, which includes a plurality of user interface objects, on the display. The first focus selector detects input by touch on the touch-sensing surface while it is on the first user interface object among the plurality of user interface objects in the foreground area, In response to detecting the input caused by the aforementioned contact, In accordance with the determination that the input resulting from the contact satisfies one or more first pressing criteria, which include a criterion that is satisfied when the characteristic intensity of the contact is below a first intensity threshold during the input, a first predetermined action corresponding to the first user interface object in the foreground area is performed, wherein the first predetermined action modifies the settings corresponding to the first user interface object in the foreground area. In accordance with the determination that the input resulting from the contact satisfies one or more second pressing criteria, which include a criterion that is satisfied when the characteristic intensity of the contact increases above the first intensity threshold during the input, a second predetermined action corresponding to the first user interface object in the foreground area is performed, separate from the first predetermined action. Includes, The second predetermined action displays a menu area superimposed on a portion of the foreground, and the menu area displays one or more selectable actions performed by the application corresponding to the first user interface object. The method wherein the menu area remains on the display even after it is detected that the contact has left the touch-sensing surface.

2. The method according to claim 1, wherein when the input is detected, the electronic device is in a locked mode in which access to a plurality of different operations that are accessible when the device is in an unlocked state is prevented.

3. In response to detecting the input caused by the aforementioned contact, The method according to claim 1 or 2, comprising performing a third predetermined action, separate from the first predetermined action and the second predetermined action, corresponding to the first user interface object in the foreground area, in accordance with a determination that the input due to the contact satisfies one or more third pressing criteria, which include a criterion that is satisfied when, during the input, the characteristic intensity of the contact increases above a second intensity threshold greater than the first intensity threshold.

4. Before displaying the foreground area, a first user interface is provided, A background having a first appearance, One or more foreground objects, Displaying the first user interface, which is a lock screen user interface, on the display, While the lock screen user interface is displayed on the display, the input is detected by a second touch on the touch-sensitive surface while the focus selector is in a position within the lock screen user interface corresponding to the background of the lock screen user interface. In response to detecting the input caused by the second contact, and in accordance with the determination that the second contact has a characteristic intensity exceeding the first intensity threshold, the appearance of the background of the lock screen user interface is dynamically changed without changing the appearance of one or more foreground objects in the lock screen user interface. The method according to any one of claims 1 to 3, wherein the dynamic change of the appearance of the background of the lock screen user interface is based at least in part on the characteristic intensity of the second contact.

5. The method according to any one of claims 1 to 4, wherein the foreground area is displayed superimposed on the portion of the background in response to the detection of a gesture starting from the edge of the touch-sensing surface.

6. The method according to any one of claims 1 to 5, wherein the first predetermined action includes toggling a wireless connection, and the second predetermined action includes displaying a user interface for selecting a wireless network to connect to.

7. The method according to any one of claims 1 to 5, wherein the first predetermined action includes toggling a limited notification operation mode, and the second predetermined action includes displaying a user interface for setting a timer associated with the limited notification operation mode.

8. The method according to any one of claims 1 to 5, wherein the first predetermined action includes toggling a flashlight function, and the second predetermined action includes displaying a user interface for selecting an operating mode for the flashlight function.

9. The method according to any one of claims 1 to 5, wherein the first predetermined action includes starting a timer application, and the second predetermined action includes displaying a user interface for performing timer management operations without starting the timer application.

10. The method according to any one of claims 1 to 5, wherein the first predetermined action includes launching an alarm application, and the second predetermined action includes displaying a user interface for performing alarm management operations without launching the alarm application.

11. The method according to any one of claims 1 to 5, wherein the first predetermined action includes launching a corresponding application, and the second predetermined action includes displaying a user interface for performing an operation associated with the corresponding application without launching the corresponding application.

12. It is an electronic device, The display and Touch-sensitive surface and One or more sensors for detecting the intensity of contact with the touch sensing surface, One or more processors, Memory and An electronic device comprising one or more programs, wherein 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 the method according to any one of claims 1 to 11.

13. A computer program, when executed by an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface, comprising instructions to cause the device to perform the method according to any one of claims 1 to 11.

Images