DEVICE, METHOD, AND GRAPHICAL USER INTERFACE FOR MANIPULATING USER INTERFACE OBJECTS WITH VISUAL AND / OR HAPTAL FEEDBACK - Patent application

Abstract

To provide faster and more efficient methods and interfaces for manipulating user interfaces.SOLUTION: The method includes displaying, on a display, a first user interface that includes a plurality of selectable objects associated with contact information, and detecting contact on a touch-sensitive surface at a location corresponding to each selectable object. The method includes displaying a menu including contact information for a selectable object so as to be superimposed on the first user interface in accordance with a determination that the detected touch meets an input threshold. The method includes 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 in accordance with a determination that contact liftoff is detected without the input criteria being met.SELECTED DRAWING: Figure 49A

Description

[Technical field]

[0001] This application relates generally to electronic devices with touch-sensitive surfaces, including, but not limited to, electronic devices with touch-sensitive surfaces that detect inputs for manipulating a user interface. [Background technology]

[0002] The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has grown significantly in recent years. Exemplary touch-sensitive surfaces include touchpads and touch screen displays. Such surfaces are widely used to manipulate user interfaces on the displays.

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

[0004] In some circumstances, a user may disable the use of a file management program (e.g., Finder, Apple Inc. of Cupertino, California), a messaging application (e.g., Messages, Apple Inc. of Cupertino, California), a photo management application (e.g., Photos, Apple Inc. of Cupertino, California), a camera application (e.g., Camera, Apple Inc. of Cupertino, California), a map application (e.g., Map, Apple Inc. of Cupertino, California), a note-taking application (e.g., Notes, Apple Inc. of Cupertino, California), a digital content (e.g., video and music) management application (e.g., Music and iTunes, Apple Inc. of Cupertino, California), a news application (e.g., News, Apple Inc. of Cupertino, California), a phone application (e.g., Phone, Apple Inc. of Cupertino, California), an email application (e.g., Outlook, Apple Inc. of Cupertino, California), a social networking application (e.g., LinkedIn, Apple Inc. of Cupertino, California), a social networking application (e.g., Facebook, Apple Inc. of Cupertino, California), a social networking application (e.g., Instagram ... Inc., Mail), browser applications (e.g., Safari by Apple Inc., Cupertino, California), drawing applications, presentation applications (e.g., Keynote by Apple Inc., Cupertino, California), word processing applications (e.g., Pages by Apple Inc., Cupertino, California), spreadsheet applications (e.g., Numbers by Apple Inc., Cupertino, California), reader applications (e.g., iBooks by Apple Inc., Cupertino, California), video creation applications (e.g., Apple Inc., Cupertino, California).Such actions must be performed on user interface objects within popular applications (e.g., iMovie from Apple Inc. of Apple, Inc. of Cupertino, California) and / or geolocation applications (e.g., Find Friends and Find iPhone from Apple Inc. of Apple, Inc. of Cupertino, California).

[0005] However, existing methods for performing these operations are cumbersome and inefficient, and furthermore, they waste energy by taking longer than necessary, this latter consideration being particularly important in battery-operated devices. Summary of the Invention

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

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

[0008] According to some embodiments, a method is performed on an electronic device having a touch-sensitive surface and a display. The device includes one or more sensors for detecting an intensity of contact with the touch-sensitive surface. The device displays a plurality of user interface objects in a first user interface on the display. The device detects a contact at a location on the touch-sensitive surface when a focus selector is at a location of a first user interface object in the plurality of user interface objects on the display. When the focus selector is at the first user interface object on the display, the device detects that a 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 the first intensity threshold, the device visually obscures a plurality of user interface objects other than the first user interface object in the first user interface while maintaining display of the first user interface object without visually obscuring the first user interface object, and the device detects that the characteristic intensity of the contact has continued to increase above the first intensity threshold, and in response to detecting that the characteristic intensity of the contact has continued to increase above the first intensity threshold, the device dynamically increases an amount of visual obscuration of the plurality of user interface objects other than the first user interface object in the first user interface while maintaining display of the first user interface object without visually obscuring the first user interface object.

[0009] According to some embodiments, an electronic device includes a display unit configured to display user interface objects, a touch-sensitive surface unit configured to receive a contact, one or more sensor units configured to detect an intensity of the contact, and a processing unit coupled to the touch-sensitive surface unit, the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable display of a plurality of user interface objects in a first user interface on the display unit, detect a contact at a location on the touch-sensitive surface unit while the focus selector is at the location of the first user interface object on the display unit, detect that a characteristic intensity of the contact increases to a first intensity threshold while the focus selector is at the location of the first user interface object on the display unit, in response to detecting that the characteristic intensity of the contact increases to the first intensity threshold, visually obscuring a plurality of 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, detect that the characteristic intensity of the contact continues to increase above the first intensity threshold, and in response to detecting that the characteristic intensity of the contact continues to increase above the first intensity threshold, dynamically increase an amount of visual obscuring the plurality of 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.

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

[0011] According to some embodiments, an electronic device includes a display unit configured to display user interface objects, a touch-sensitive surface unit configured to receive a contact, one or more sensor units configured to detect an intensity of a contact with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable display of a plurality of user interface objects in a first user interface on the display unit. The processing unit is configured to detect a contact input while a focus selector is over a first user interface object in the plurality of user interface objects on the display unit. In accordance with a determination that the input satisfies a selection criterion, the processing unit is configured to enable display of a second user interface, separate from the first user interface, in response to detecting the input. In accordance with a determination that a first portion of the input satisfies a preview criterion, the processing unit is configured to enable display of a preview area including a reduced representation of a preview area of ​​the second user interface overlaid on at least some of the plurality of user interface objects in the first user interface in response to detecting the first portion of the input. In response to a determination that a second portion of the contact input detected after the first portion of the input satisfies a user interface replacement criterion, the processing unit is configured to replace the display of the first user interface and the overlapping preview area with a display of the second user interface In response to a determination that the second portion of the contact input satisfies a preview area hiding criterion, the processing unit is configured to cease displaying the preview area and enable display of the first user interface after the input is terminated.

[0012] According to some embodiments, a method is performed on an electronic device with a touch-sensitive surface and a display. The device includes one or more sensors for detecting an intensity of contact with the touch-sensitive surface. The device displays a plurality of user interface objects in a first user interface on the display. The device detects a first portion of a press input of the contact at a location on the touch-sensitive surface corresponding to a location of the first user interface object in the plurality of user interface objects on the display. While detecting the first portion of the press input of the contact at a location on the touch-sensitive surface corresponding to a location of the first user interface object in the plurality of user interface objects on the display, the device selects the first user interface object and detects that an intensity of the contact has increased to a second intensity threshold. In response to detecting that an intensity of the contact has increased to the second intensity threshold, the device displays a preview area in the first user interface overlying at least some of the plurality of user interface objects. After detecting the 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 press input by the contact, in accordance with a determination that the second portion of the press input by the contact satisfies a user interface replacement criterion, the device replaces the display of the first user interface with a second user interface that is distinct from the first user interface. In accordance with a determination that the second portion of the press input by the contact satisfies a preview area maintenance criterion, the device maintains the display of a preview area overlying at least some of the user interface objects in the first user interface after the press input is terminated. In accordance with a determination that the second portion of the press input by the contact satisfies a preview area hiding criterion, the device ceases displaying in the preview area and maintains the display of the first user interface after the press input is terminated.

[0013] According to some embodiments, a method is performed on an electronic device that includes a display, a touch-sensitive surface, and one or more sensors for detecting an intensity of contact with the touch-sensitive surface. The method includes displaying a first user interface on the display including 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 displaying the first user interface on the display, the device performs a detection of a first portion of a first input, including detecting that a characteristic intensity of a first contact on the touch-sensitive surface increases above a first intensity threshold while a focus selector is over each of the plurality of selectable user interface objects. In response to detecting the first portion of the first input, the device displays supplemental information associated with the respective user interface objects. While displaying the supplemental information associated with the respective user interface objects, the device detects termination of the first input. In response to detecting an end of the first input, in accordance with a determination that the respective user interface object is a first type user interface object, the device ceases displaying the supplemental information associated with the respective user interface object, and in accordance with a determination that the respective user interface object is a second type user interface object, the device maintains displaying the supplemental information associated with the respective user interface object after detecting an end of the first input.

[0014] According to some embodiments, an 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 an intensity of contact with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable display of a first user interface on the display unit including 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; detect a first portion of a first input including detecting, while the first user interface is displayed on the display unit, that a characteristic intensity of a first contact on the touch-sensitive surface increases above a first intensity threshold while the focus selector is over each of the plurality of selectable user interface objects; and in response to detecting the first portion of the first input, enable display of supplemental information associated with the respective user interface objects; detect an end of the first input while the supplemental information associated with the respective user interface objects is displayed; and in response to detecting the end of the first input, cease enabling display of the supplemental information associated with the respective user interface objects in accordance with a determination that the respective user interface objects are user interface objects of the first type; and maintain display of the supplemental information associated with the respective user interface objects after detecting the end of the first input in accordance with a determination that the respective user interface objects are user interface objects of the second type.

[0015] According to some embodiments, a method is performed on an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting an 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 displaying the first user interface on the display, the device 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 detecting the first input by the first contact, and in accordance with a determination that the first contact has a characteristic intensity that exceeds a first intensity threshold, the device dynamically changes an appearance of the background of the first user interface without changing an appearance of the one or more foreground objects in the first user interface. The dynamic change in appearance of the background of the first user interface is based at least in part on the characteristic intensity of the first contact. The device detects a termination of the first input by the first contact while dynamically changing an appearance of the background of the first user interface, and in response to detecting the termination of the first input by the first contact, reverts the background of the first user interface to the first appearance of the background.

[0016] According to some embodiments, an electronic device comprises a display unit configured to display a user interface, background and foreground objects, a touch-sensitive surface unit configured to receive user input, one or more sensor units configured to detect an intensity of contact with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable display of a first user interface on the display, the first user interface including a background having a first appearance and one or more foreground objects. While displaying the first user interface on the display, the processing unit is configured to detect a first input by a first contact on the touch-sensitive 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 detecting the first input by the first contact, according to a determination that the first contact has a characteristic intensity above a first intensity threshold, the processing unit is configured to dynamically change an appearance of the background of the first user interface without changing an appearance of the one or more foreground objects in the first user interface. The dynamically changing an appearance of the background of the first user interface is based at least in part on a characteristic intensity of the first contact. The processing unit is configured to detect a termination of the first input by the first contact while dynamically changing the appearance of the background of the first user interface, and in response to detecting the termination of the first input by the first contact, to revert the background of the first user interface to its first appearance.

[0017] According to some embodiments, a method is performed on an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting an 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 displaying the first user interface on the display, the device detects an input on the touch-sensitive surface by a first contact having a characteristic intensity above a first intensity threshold. In response to detecting the input by the first contact, during the input, in accordance with a determination that the focus selector is at a location in the first user interface corresponding to the user interface background, the device dynamically changes an appearance of the background of the first user interface without changing an appearance of the one or more foreground objects in the first user interface. The dynamic change of the appearance of the background of the first user interface is based at least in part on the characteristic intensity of the first contact, and in accordance with a determination that the focus selector is at a location in the first user interface corresponding to a respective one of the one or more foreground objects in the first user interface, the device maintains the first appearance of the background of the first user interface.

[0018] According to some embodiments, an electronic device comprises a display unit configured to display a user interface, background and foreground objects, a touch-sensitive surface unit configured to receive user input, one or more sensor units configured to detect an intensity of a contact with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable display of a first user interface on the display unit, the first user interface including a background having a first appearance and one or more foreground objects. The processing unit is configured to detect a first contact input on the touch-sensitive surface unit having a characteristic intensity above a first intensity threshold while displaying the first user interface on the display unit. In response to detecting the first contact input and following a determination that during the input, the focus selector is at a location in the first user interface corresponding to the user interface background, the processing unit is configured to dynamically change an appearance of a background of the first user interface without changing an appearance of the one or more foreground objects in the first user interface. The dynamic change in appearance of the background of the first user interface is based at least in part on the characteristic intensity of the first contact. In accordance with a determination that the focus selector is at a location in the first user interface corresponding to a respective foreground object of one or more foreground objects in the first user interface, the processing unit is configured to maintain a first appearance of a background of the first user interface.

[0019] According to some embodiments, a method is performed on an electronic device including a display, a touch-sensitive surface, and one or more sensors for detecting an intensity of contact with the touch-sensitive surface. The device displays a first user interface on the display including a background and a foreground area overlapping a portion of the background and including a plurality of user interface objects. The device detects a contact input on the touch-sensitive surface while a first focus selector is on a first user interface object in the plurality of user interface objects in the foreground area. In response to detecting the contact input, the device performs a first predefined action corresponding to the first user interface object in the foreground area in response to a determination that the contact input satisfies one or more first press criteria including a criterion that is met if a characteristic intensity of the contact remains below a first intensity threshold during the input, and performs a second action, distinct from the first predefined action, corresponding to the first user interface object in the foreground area in response to a determination that the contact input satisfies one or more second press criteria including a criterion that is met if a characteristic intensity of the contact increases above the first intensity threshold during the input.

[0020] According to some embodiments, an electronic device comprises a display unit configured to display a user interface and user interface objects, a touch-sensitive surface unit configured to receive user input, one or more sensor units configured to detect an intensity of a contact with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable display on the display unit of a first user interface including a first appearance and a background having one or more foreground objects. While displaying the first user interface on the display unit, the processing unit is configured to detect a first contact input on the touch-sensitive surface unit having a characteristic intensity above a first intensity threshold. In response to detecting the first contact input and in accordance with a determination that during the input, the focus selector is at a location in the first user interface that corresponds to the user interface background, the processing unit is configured to dynamically change an appearance of a background of the first user interface without changing an appearance of the one or more foreground objects in the first user interface. The dynamic change in appearance of the background of the first user interface is based at least in part on the characteristic intensity of the first contact. In accordance with a determination that the focus selector is at a location in the first user interface corresponding to a respective foreground object of one or more foreground objects in the first user interface, the processing unit is configured to maintain a first appearance of a background of the first user interface.

[0021] According to some embodiments, a method is performed on an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting an intensity of contact with the touch-sensitive surface. The device displays an application launch user interface on the display including a plurality of application icons for launching corresponding applications. While displaying the application launch user interface, the device detects a first contact input including detecting a first contact at a location on the touch-sensitive surface corresponding to a first application icon of the plurality of application icons. The first application icon is an icon for launching a first application associated with one or more corresponding quick actions. In response to detecting the first contact input in accordance with a determination that the first contact input satisfies one or more application launch criteria, the device launches the first application. In accordance with a determination that the first contact input satisfies one or more quick action display criteria including criteria that are met when a characteristic intensity of the first contact increases above a respective 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, an electronic device includes 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 an intensity of contact with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable display of an application launch user interface on the display unit including a plurality of application icons for launching corresponding applications. While displaying the application launch user interface, the processing unit is configured to detect a first contact input including detecting a first contact at a location on the touch-sensitive surface unit corresponding to a first application icon of the plurality of application icons, the first application icon being 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 a determination that the first contact input satisfies one or more quick action display criteria, including criteria that are satisfied when a characteristic intensity of the first contact increases above a respective intensity threshold, the processing unit enables display of one or more quick action objects associated with the first application concurrently with the first application icon without launching the first application.

[0023] According to some embodiments, a method is performed on an electronic device having a display and one or more input devices. The electronic device displays a first user interface on the display including 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 corresponding to a request to display menu options for a first user interface object of 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 in accordance with a determination that the first user interface object is at a first location in the first user interface, and displaying the menu items corresponding to the first user interface object in a second order in the menu, the second order being different from the first order in accordance with a determination that the first user interface object is at a second location in the first user interface that is different from the first location.

[0024] According to some embodiments, an 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 coupled to the display unit and the one or more input devices. The processing unit is configured to enable display of a first user interface on the display unit including 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 the one or more input devices corresponding to a request to display menu options for a first user interface object of the plurality of user interface objects. In response to detecting the first input, the processing unit enables display of menu items in a menu corresponding 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 at a first location in the first user interface, and displaying the menu items corresponding to the first user interface object in a second order in the menu, the second order being different from the first order, according to a determination that the first user interface object is at a second location in the first user interface that is different from the first location.

[0025] According to some embodiments, a method is performed on an electronic device that includes a display, a touch-sensitive surface, and one or more sensors for detecting an intensity of contact with the touch-sensitive surface. The device displays a user interface on the display including a selectable user interface object associated with a plurality of actions for interacting with the user interface, the plurality of actions including a direct selection action and one or more other actions. While displaying the user interface including the selectable user interface object, the device detects an input including 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 including detecting the contact, in accordance with a determination that the input satisfies a selection criterion, the device displays a menu on the display including a graphical representation of a plurality of actions including the direct selection action and the one or more other actions, and in accordance with a determination that the input satisfies a direct selection criterion including a criterion that is satisfied if a characteristic intensity of the contact increases above a respective intensity threshold, the device performs the direct selection action.

[0026] According to some embodiments, an 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 an intensity of contact with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable display of a user interface on the display unit including a selectable user interface object associated with a plurality of actions for interacting with the user interface, the plurality of actions including a direct selection action and one or more other actions. The processing unit is configured to detect an input while displaying the user interface including the selectable user interface object, including detecting a contact on the touch-sensitive surface unit while a focus selector is over the selectable user interface object. In response to detecting the input, including detecting the contact, and in accordance with a determination that the input satisfies the selection criteria, the processing unit is configured to enable display on the display unit of a menu including a graphical representation of a plurality of actions including the direct selection action and one or more other actions, and in accordance with a determination that the input satisfies the direct selection criteria including criteria that are satisfied when a characteristic intensity of the contact increases above a respective intensity threshold, the processing unit is configured to perform the direct selection action.

[0027] There is a need for electronic devices 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 number, extent, and / or nature of inputs from the user, creating a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and extend the time between battery charges.

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

[0029] According to some embodiments, an electronic device comprises a display unit configured to display a user interface and user interface objects, a touch-sensitive surface unit configured to receive user input, one or more sensor units configured to detect an intensity of contact with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units.The processing unit enables display of a user interface on the display unit including a plurality of user interface elements including a first object displayed at a first location within the user interface and a second object displayed at a second location within the user interface, the plurality of user interface objects being associated with respective object specific actions triggered by a change in contact intensity, and detects a first contact on the touch-sensitive surface unit while displaying the user interface including the plurality of user interface elements, and detects that a characteristic intensity of the first contact has increased above a first intensity threshold, and in response to detecting the first input, a focus selector displays additional information associated with the first object on the display in accordance with a determination that the first object is at a first location within the displayed user interface. a second action associated with the second object, the second action being distinct from the first action associated with the first object, including displaying additional information associated with the second object on the display unit in accordance with a determination that the focus selector is at a second location in the user interface where the second object is being displayed; and a third action associated with the second object, the second action being distinct from the first action associated with the first object, in accordance with a determination that the focus selector is at a location in the user interface away from any objects associated with object-specific actions triggered by a change in contact intensity, the third action being updating the user interface on the display unit to simultaneously visually distinguish the first object and the second object in the user interface.

[0030] According to some embodiments, a method is performed on an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting an intensity of contact with the touch-sensitive surface. The device displays on the display a user interface including 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 the respective user interface element at a location corresponding to the respective user interface element, and for the remainder of the user interface, the device is not configured to respond to a user input of the first input type by performing a plurality of operations corresponding to the user interface element in the remainder of the user interface at a location corresponding to the user interface element in the remainder of the user interface. The device detects a first user input of the first input type while a 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 at a first location within the user interface, in accordance with a determination that the first location corresponds to a first user interface element in the first set of user interface elements, the device performs a number of operations corresponding to the first user interface element, and in accordance with a determination that the first location does not correspond to a user interface element in the first set of user interface elements, the device applies a visual effect to distinguish on the display between the first set of user interface elements and the remainder of the user interface.

[0031] According to some embodiments, an electronic device comprises a display unit configured to display a user interface and user interface elements, a touch-sensitive surface unit configured to receive user input, one or more sensor units configured to detect an intensity of contact with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable display of a user interface on the display unit comprising a first set of user interface elements, where for each user interface element in the first set of user interface elements, the device is configured to respond to user input of the first input type by performing a plurality of operations corresponding to the respective user interface element at a location corresponding to the respective user interface element, and where for the remainder of the user interface, the device is not configured to respond to user input of the first input type by performing a plurality of operations corresponding to the user interface element in the remainder of the user interface at a location corresponding to the 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 within the user interface, and in response to detecting the first user input of the first input type while the focus selector is at the first location within the user interface, perform a plurality of operations corresponding to the first user interface element in accordance with a determination that the first location corresponds to a first user interface element in the first set of user interface elements, and apply a visual effect on the display unit to distinguish the first set of user interface elements from the remainder of the user interface in accordance with a determination that the first location does not correspond to any user interface element in the first set of user interface elements.

[0032] Thus, electronic devices with a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface are provided with a fast and efficient method and interface for indicating which user interface elements have contact intensity-based functions and features, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace traditional 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 complementing or replacing conventional methods for previewing media content. Such methods reduce the number, extent, and / or nature of input from a user, creating a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and extend the time between battery charges.

[0034] According to some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting an intensity of a contact on the touch-sensitive surface. The method includes displaying a user interface on the display including 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 the second set of media items. The method further includes detecting an input including a movement of a 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 including movement of the contact on the touch-sensitive surface, outputting a preview of a media item from the first set of media items in accordance with a determination that the input satisfies media preview criteria including criteria that are met if the input includes an increase in a characteristic intensity of the contact while the focus selector is over the first media object and exceeding a media preview intensity threshold; in response to detecting the movement of the contact, ceasing outputting the preview of the media item from the first set of media items and outputting a preview of the media item from the second set of media items; and in accordance with a determination that the input does not satisfy the media preview criteria, moving the first media object and the second media object on the display in accordance with movement of the contact on the touch-sensitive surface.

[0035] According to some embodiments, an electronic device includes a display unit configured to display a user interface, a touch-sensitive surface unit for receiving a contact, one or more sensor units for detecting an intensity of a contact with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. Detecting an input including a movement of the contact on the touch-sensitive surface while a focus selector is over a first media object. The processing unit is configured to enable display of a user interface on the display unit including a plurality of media objects including a first media object representing a first set of one or more media items, the first media object being different from the second set of media items, and a second media object representing the second set of one or more media items. The processing unit is configured to detect an input including a movement of a contact on the touch-sensitive surface while the focus selector is over the first media object, and in response to detecting the input including the movement of the contact on the touch-sensitive surface, output a preview of a media item from the first set of media items in accordance with a determination that the input satisfies media preview criteria that include criteria that are satisfied if the input includes a characteristic intensity of the contact increasing while the focus selector is over the first media object to exceed a media preview intensity threshold, and in response to detecting the movement of the contact, stop outputting the preview of the media item from the first set of media items and output a preview of the media item from the second set of media items, and in response to detecting the movement of the contact, move the first media object and the second media object on the display in accordance with the movement of the contact on the touch-sensitive surface in accordance with a determination that the input does not satisfy the media preview criteria.

[0036] Thus, electronic devices that have a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface are provided with faster, more efficient methods and interfaces for previewing media content, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for previewing media content.

[0037] According to some embodiments, a method is performed on an electronic device that includes a display, a touch-sensitive surface, and one or more sensors for detecting an 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 the paginated content including a plurality of sections, each section in the plurality of sections including a respective plurality of pages, a first portion of the paginated content being part of a first section of the plurality of sections, the first portion of the paginated content being between a previous consecutive page in the first section and a next consecutive page in the first section, detecting a 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 the first portion of the input, detecting a lift-off of the contact from the touch-sensitive surface before a characteristic intensity of the contact reaches a first threshold intensity. In accordance with a determination that the first portion of the input satisfies a first content navigation criterion that includes criteria that are met when detected by the device, replacing on the display the displayed first portion of the paginated content with a second portion of the paginated content that includes a page that is contiguous with the first portion of the paginated content; and in accordance with a determination that the first portion of the input satisfies a second content navigation criterion that includes criteria that are met when detected by the device that a characteristic intensity of the contact increases to above a first intensity threshold, displaying an indication of a page number within a subsequent successive page in the first section or an indication of a page number within a previous successive page in the first section while the focus selector is within a first predetermined area of ​​the displayed first portion of the paginated content.

[0038] According to some embodiments, an electronic device comprises a display unit configured to display an item of content, a touch-sensitive surface unit configured to receive user input, one or more sensor units configured to detect an intensity of contact with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is adapted to: enable display on the display of a first portion of paginated content in a user interface, the first portion of the paginated content including a plurality of sections, each section within the plurality of sections including a respective plurality of pages, a first portion of the paginated content being part of a first section of the plurality of sections, the first portion of the paginated content being between a previous consecutive page in the first section and a next consecutive page in the first section; detect a 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 the first portion of the input, cause the device to detect lift-off of the contact from the touch-sensitive surface before a characteristic intensity of the contact reaches a first threshold intensity. in response to a determination that the first portion of the input satisfies a first content navigation criterion that includes a criterion that is satisfied when the device detects that a characteristic intensity of the contact has increased above a first intensity threshold, replace on the display the displayed first portion of the paginated content with a second portion of the paginated content that includes a page that is contiguous with the first portion of the paginated content, and in response to a determination that the first portion of the input satisfies a second content navigation criterion that includes a criterion that is satisfied when the device detects that a characteristic intensity of the contact has increased above a first intensity threshold, enable an explicit display of a page number within a subsequent successive page in the first section or enable an explicit display of a page number within a previous successive page in the first section while the focus selector is within a first predetermined area of ​​the displayed first portion of the paginated content.

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

[0040] According to some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting an intensity of a contact on the touch-sensitive surface. The method includes displaying a view of a map including a plurality of points of interest in a first user interface on the display. The method further includes detecting, while displaying the view of the map including the plurality of points of interest and while a focus selector is at each of the points of interest, that a characteristic intensity of the contact on the touch-sensitive surface increases above a preview threshold intensity. In response to detecting that the characteristic intensity of the contact increases above the preview threshold intensity, the method further includes zooming the map to display contextual information near each of the points of interest. The method further includes, after zooming the map, detecting a respective input including detecting a decrease in a characteristic intensity of the contact on the touch-sensitive surface below a predefined intensity threshold, and in response to detecting the respective input including detecting a decrease in the characteristic intensity of the contact, continuing to display the contextual information near each point of interest in accordance with a determination that the characteristic intensity of the contact increased above a context-preserving intensity threshold prior to detecting the respective input, and ceasing to display the contextual information near the point of interest and re-displaying a view of the map including the plurality of points of interest in accordance with a determination that the characteristic intensity of the contact did not increase above the context-preserving intensity threshold prior to detecting the respective input.

[0041] According to some embodiments, an electronic device includes a display unit, a touch-sensitive surface unit, one or more sensor units for detecting an intensity of a contact on the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable display of a view of the map including the plurality of points of interest in a first user interface on the display unit, detect that a characteristic intensity of a contact on the touch-sensitive surface has increased above a preview threshold intensity while the focus selector is at the respective points of interest, and in response to detecting that the characteristic intensity of the contact has increased above the preview threshold intensity, zoom the map to display contextual information near the respective points of interest, including detecting, after zooming the map, that a characteristic intensity of the contact on the touch-sensitive surface has decreased below a predefined intensity threshold, detect a respective input and detect a decrease in the characteristic intensity of the contact, in response to detecting the respective input, continue to enable the display of the contextual information near the respective points of interest in accordance with a determination that the characteristic intensity of the contact increased above the context-preserving intensity threshold prior to detecting the respective input, and stop enabling the display of the contextual information near the points of interest and re-display the view of the map including the plurality of points of interest in accordance with a determination that the characteristic intensity of the contact did not increase above the context-preserving intensity threshold prior to detecting the respective input.

[0042] Thus, electronic devices that include a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contact with the touch-sensitive surface are provided with faster, more efficient methods and interfaces for displaying contextual information associated with points of interest in a map, thereby improving the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for displaying contextual information associated with points of interest in a map.

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

[0044] According to some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting an intensity of a contact on the touch-sensitive surface. The method includes simultaneously displaying within a user interface on the display a map view including a plurality of points of interest and a context area, separate from the map view, including a representation of a first point of interest from the plurality of points of interest and a representation of a second point of interest from the plurality of points of interest. The method further includes detecting, while simultaneously displaying the map view and the context area on the display, that a characteristic intensity of the contact on the touch-sensitive surface increases above a respective intensity threshold. The method further includes, in response to detecting that the characteristic intensity of the contact has increased above a respective intensity threshold, zooming the map view to display respective context information for the first point of interest in the map view proximate the first point of interest in accordance with a determination that the focus selector was at the representation of the first point of interest in the context area when it was detected that the characteristic intensity of the contact has increased above a respective intensity threshold, and zooming the map view to display respective context information for the second point of interest in the map view proximate the second point of interest in accordance with a determination that the focus selector was at the representation of the second point of interest in the context area when it was detected that the characteristic intensity of the contact has increased above a respective intensity threshold.

[0045] According to some embodiments, an electronic device includes a display unit, a touch-sensitive surface unit, one or more sensor units for detecting an intensity of a contact on the touch-sensitive surface, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units, for enabling simultaneous display in a user interface on the display unit of a map view including a plurality of points of interest and a context area, separate from the map view, including a representation of a first point of interest from the plurality of points of interest and a representation of a second point of interest from the plurality of points of interest, and for detecting that while enabling the simultaneous display of the map view and the context area on the display unit, a characteristic intensity of the contact on the touch-sensitive surface increases above a respective intensity threshold. and a processing unit configured to, in response to detecting that the characteristic intensity of the contact has increased above a respective intensity threshold, zoom the map view to display the respective context information of the first point of interest in the map view proximate the first point of interest in accordance with a determination that the focus selector was at the representation of the first point of interest in the context area when it was detected that the characteristic intensity of the contact has increased above a respective intensity threshold, and to zoom the map view to display the respective context information of the second point of interest in the map view proximate the second point of interest in accordance with a determination that the focus selector was at the representation of the second point of interest in the context area when it was detected that the characteristic intensity of the contact has increased above a respective intensity threshold.

[0046] Thus, electronic devices having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface are provided with faster, more efficient methods and interfaces for zooming maps, thereby improving the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces complement or replace conventional methods for zooming 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 inputs from a user, creating a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and extend the time between battery charges.

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

[0049] According to some embodiments, an 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 an intensity of contact with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to enable display of a first user interface on the display unit including a plurality of selectable objects associated with contact information, detect an input including detecting a contact on the touch-sensitive surface unit while enabling display of the plurality of selectable objects and while the focus selector is at a location corresponding to the respective selectable objects, and in response to detecting the input, enable display of a menu of the respective selectable objects including the contact information of the respective selectable objects overlaid on the first user interface including the plurality of selectable objects in accordance with a determination that detecting the input includes detecting an increase in intensity of the contact satisfying an intensity criterion including a criterion that is satisfied when a characteristic intensity of the contact increases above a respective intensity threshold, and replace the display of the first user interface including the plurality of selectable objects with a display of a second user interface associated with the respective selectable objects in accordance with a determination that detecting the input includes detecting a lift-off of the contact without satisfying the intensity criterion.

[0050] Thus, faster, more efficient methods and interfaces for displaying menus containing contact information on electronic devices that have a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface are provided, thereby improving the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for displaying menus 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 an intensity of contact with the touch-sensitive surface, one or more processors, a memory, and one or more programs, the one or more programs being stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing or causing the performance of any of the operations of the methods described herein. According to some embodiments, a computer-readable storage medium has instructions stored therein that, when executed by an electronic device including a display, a touch-sensitive surface, and optionally one or more sensors for detecting an intensity of contact with the touch-sensitive surface, cause the device to perform or cause the performance of any of the operations of the methods described herein. According to some embodiments, an electronic device including a graphical user interface display, a touch-sensitive surface, optionally one or more sensors for detecting an intensity of contact with the touch-sensitive surface, a memory, and one or more processors for executing one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described herein, which elements are updated in response to an input as described in any of the methods described herein. According to some embodiments, an electronic device includes a display, a touch-sensitive surface, and optionally one or more sensors for detecting an intensity of contact with the touch-sensitive surface, and means for performing or causing the performance of any of the operations of the methods described herein. According to some embodiments, an information processing apparatus for use in an electronic device with a display and a touch-sensitive surface, and optionally one or more sensors for detecting an intensity of contact with the touch-sensitive surface, includes means for performing or causing the performance of any of the operations of the methods described herein.

[0052] Thus, electronic devices having a display, a touch-sensitive surface, and optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface are provided with faster, more efficient methods and interfaces for operating a user interface, thereby improving the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for operating a user interface. [Brief description of the drawings]

[0053] For a better understanding of the various embodiments described, please refer to the following Description of Embodiments in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout:

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

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

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

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

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

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

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

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

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

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

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

[0065] [Figure 9A] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9B] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9C] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9D] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9E] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9F] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9G] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9H] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9I] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9J] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9K] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9L] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9M] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9N] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9O] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9P] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9Q] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9R] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments. [Figure 9S] 1 illustrates an example user interface for dynamically changing a background of a user interface according to some embodiments.

[0066] [Figure 10A] 1 illustrates an example user interface for toggling between different actions based on input contact characteristics according to some embodiments. [Figure 10B] 1 illustrates an example user interface for toggling between different actions based on input contact characteristics according to some embodiments. [Figure 10C] 1 illustrates an example user interface for toggling between different actions based on input contact characteristics according to some embodiments. [Figure 10D] 1 illustrates an example user interface for toggling between different actions based on input contact characteristics according to some embodiments. [Figure 10E]1 illustrates an example user interface for toggling between different actions based on input contact characteristics according to some embodiments. [Figure 10F] 1 illustrates an example user interface for toggling between different actions based on input contact characteristics according to some embodiments. [Figure 10G] 1 illustrates an example user interface for toggling between different actions based on input contact characteristics according to some embodiments. [Figure 10H] 1 illustrates an example user interface for toggling between different actions based on input contact characteristics according to some embodiments. [Figure 10I] 1 illustrates an example user interface for toggling between different actions based on input contact characteristics according to some embodiments. [Figure 10J] 1 illustrates an example user interface for toggling between different actions based on input contact characteristics according to some embodiments. [Figure 10K] 1 illustrates an example user interface for toggling between different actions based on input contact characteristics according to some embodiments. [Figure 10L] 1 illustrates an example user interface for toggling between different actions based on input contact characteristics according to some embodiments.

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

[0068] [Figure 12A] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12B] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12C] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12D] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12E] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12F] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12G] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12H] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12I] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12J] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12K] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12L] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12M] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12N] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12O] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12P] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12Q] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12R] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12S] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12T] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12U] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12V] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 12W] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Fig. 12X] 1 illustrates an exemplary user interface for selecting a default option from a menu or displaying a menu of options according to some embodiments.

[0069] [Figure 13A] 4 is a flow diagram illustrating a method for visually obscuring certain user interface objects according to some embodiments. [Figure 13B] 4 is a flow diagram illustrating a method for visually obscuring certain user interface objects according to some embodiments. [Figure 13C] 4 is a flow diagram illustrating a method for visually obscuring certain user interface objects according to some embodiments.

[0070] [Figure 14] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

[0071] [Figure 15A] 1 is a flow diagram illustrating a method of navigating between a first user interface and a second user interface according to some embodiments. [Figure 15B] 1 is a flow diagram illustrating a method of navigating between a first user interface and a second user interface according to some embodiments. [Figure 15C] 1 is a flow diagram illustrating a method of navigating between a first user interface and a second user interface according to some embodiments. [Figure 15D] 1 is a flow diagram illustrating a method of navigating between a first user interface and a second user interface according to some embodiments. [Figure 15E] 1 is a flow diagram illustrating a method of navigating between a first user interface and a second user interface according to some embodiments. [Figure 15F] 1 is a flow diagram illustrating a method of navigating between a first user interface and a second user interface according to some embodiments. [Figure 15G] 1 is a flow diagram illustrating a method of navigating between a first user interface and a second user interface according to some embodiments.

[0072] [Figure 16] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

[0073] [Figure 17A] 1 is a flow diagram illustrating a method for providing supplemental information (eg, previews and menus) according to some embodiments. [Figure 17B]1 is a flow diagram illustrating a method for providing supplemental information (eg, previews and menus) according to some embodiments. [Figure 17C] 1 is a flow diagram illustrating a method for providing supplemental information (eg, previews and menus) according to some embodiments. [Figure 17D] 1 is a flow diagram illustrating a method for providing supplemental information (eg, previews and menus) according to some embodiments. [Figure 17E] 1 is a flow diagram illustrating a method for providing supplemental information (eg, previews and menus) according to some embodiments. [Figure 17F] 1 is a flow diagram illustrating a method for providing supplemental information (eg, previews and menus) according to some embodiments. [Figure 17G] 1 is a flow diagram illustrating a method for providing supplemental information (eg, previews and menus) according to some embodiments. [Figure 17H] 1 is a flow diagram illustrating a method for providing supplemental information (eg, previews and menus) according to some embodiments.

[0074] [Figure 18] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

[0075] [Figure 19A] 4 is a flow diagram illustrating a method for dynamically changing the background of a user interface according to some embodiments. [Figure 19B] 4 is a flow diagram illustrating a method for dynamically changing the background of a user interface according to some embodiments. [Figure 19C] 4 is a flow diagram illustrating a method for dynamically changing the background of a user interface according to some embodiments. [Figure 19D] 4 is a flow diagram illustrating a method for dynamically changing the background of a user interface according to some embodiments. [Figure 19E]4 is a flow diagram illustrating a method for dynamically changing the background of a user interface according to some embodiments. [Figure 19F] 4 is a flow diagram illustrating a method for dynamically changing the background of a user interface according to some embodiments.

[0076] [Figure 20] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

[0077] [Figure 21A] 4 is a flow diagram illustrating a method for dynamically changing the background of a user interface according to some embodiments. [Figure 21B] 4 is a flow diagram illustrating a method for dynamically changing the background of a user interface according to some embodiments. [Figure 21C] 4 is a flow diagram illustrating a method for dynamically changing the background of a user interface according to some embodiments.

[0078] [Figure 22] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

[0079] [Figure 23A] 1 is a flow diagram illustrating a method for toggling between different actions based on input contact characteristics according to some embodiments. [Figure 23B] 1 is a flow diagram illustrating a method for toggling between different actions based on input contact characteristics according to some embodiments. [Figure 23C] 1 is a flow diagram illustrating a method for toggling between different actions based on input contact characteristics according to some embodiments.

[0080] [Figure 24] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

[0081] [Figure 25A]4 is a flow diagram illustrating a method for launching an application or displaying a quick action menu according to some embodiments. [Figure 25B] 4 is a flow diagram illustrating a method for launching an application or displaying a quick action menu according to some embodiments. [Figure 25C] 4 is a flow diagram illustrating a method for launching an application or displaying a quick action menu according to some embodiments. [Figure 25D] 4 is a flow diagram illustrating a method for launching an application or displaying a quick action menu according to some embodiments. [Figure 25E] 4 is a flow diagram illustrating a method for launching an application or displaying a quick action menu according to some embodiments. [Figure 25F] 4 is a flow diagram illustrating a method for launching an application or displaying a quick action menu according to some embodiments. [Figure 25G] 4 is a flow diagram illustrating a method for launching an application or displaying a quick action menu according to some embodiments. [Fig. 25H] 4 is a flow diagram illustrating a method for launching an application or displaying a quick action menu according to some embodiments.

[0082] [Figure 26] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

[0083] [Figure 27A] 4 is a flow diagram illustrating a method for displaying a menu having a list of items arranged based on the location of a user interface object according to some embodiments. [Figure 27B] 4 is a flow diagram illustrating a method for displaying a menu having a list of items arranged based on the location of a user interface object according to some embodiments. [Figure 27C] 4 is a flow diagram illustrating a method for displaying a menu having a list of items arranged based on the location of a user interface object according to some embodiments. [Figure 27D] 4 is a flow diagram illustrating a method for displaying a menu having a list of items arranged based on the location of a user interface object according to some embodiments. [Figure 27E] 4 is a flow diagram illustrating a method for displaying a menu having a list of items arranged based on the location of a user interface object according to some embodiments.

[0084] [Figure 28] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

[0085] [Figure 29A] 4 is a flow diagram illustrating a method for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 29B] 4 is a flow diagram illustrating a method for selecting a default option from a menu or displaying a menu of options according to some embodiments. [Figure 29C] 4 is a flow diagram illustrating a method for selecting a default option from a menu or displaying a menu of options according to some embodiments.

[0086] [Diagram 30] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

[0087] [Figure 31A] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Figure 31B]1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Figure 31C] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Figure 31D] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Figure 31E] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Fig. 31F] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Figure 31G] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Fig. 31H] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Fig. 31I] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Figure 31J] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Figure 31K] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Figure 31L] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Figure 31M]1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Figure 31N] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Figure 31O] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Figure 31P] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments. [Figure 31Q] 1 illustrates an example user interface for visually distinguishing intensity-sensing objects within a user interface in accordance with some embodiments.

[0088] [Figure 32A] 4 is a flow diagram illustrating a method for visually distinguishing intensity-sensing objects in a user interface according to some embodiments. [Figure 32B] 4 is a flow diagram illustrating a method for visually distinguishing intensity-sensing objects in a user interface according to some embodiments. [Figure 32C] 4 is a flow diagram illustrating a method for visually distinguishing intensity-sensing objects in a user interface according to some embodiments. [Fig. 32D] 4 is a flow diagram illustrating a method for visually distinguishing intensity-sensing objects in a user interface according to some embodiments. [Figure 32E] 4 is a flow diagram illustrating a method for visually distinguishing intensity-sensing objects in a user interface according to some embodiments.

[0089] [Diagram 33] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

[0090] [Figure 34A] 1 is a flow diagram illustrating a method for visually distinguishing objects in a user interface according to some embodiments. [Figure 34B] 1 is a flow diagram illustrating a method for visually distinguishing objects in a user interface according to some embodiments. [Figure 34C] 1 is a flow diagram illustrating a method for visually distinguishing objects in a user interface according to some embodiments.

[0091] [Diagram 35] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

[0092] [Figure 36A] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36B] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36C] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36D] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36E] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36F] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36G] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Fig. 36H] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36I] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36J] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36K] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36L] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36M] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36N] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36O] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36P]1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36Q] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36R] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36S] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36T] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Fig. 36U] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments. [Figure 36V] 1 illustrates an exemplary user interface for previewing media content (eg, audio content and / or video content) according to some embodiments.

[0093] [Figure 37A] 4 is a flow diagram illustrating a method for previewing media content according to some embodiments. [Figure 37B] 4 is a flow diagram illustrating a method for previewing media content according to some embodiments. [Figure 37C] 4 is a flow diagram illustrating a method for previewing media content according to some embodiments. [Figure 37D] 4 is a flow diagram illustrating a method for previewing media content according to some embodiments. [Figure 37E] 4 is a flow diagram illustrating a method for previewing media content according to some embodiments. [Figure 37F] 4 is a flow diagram illustrating a method for previewing media content according to some embodiments. [Figure 37G] 4 is a flow diagram illustrating a method for previewing media content according to some embodiments. [Fig. 37H] 4 is a flow diagram illustrating a method for previewing media content according to some embodiments.

[0094] [Figure 38] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

[0095] [Figure 39A] 1 illustrates an exemplary user interface for navigating paginated content according to some embodiments. [Figure 39B] 1 illustrates an exemplary user interface for navigating paginated content according to some embodiments. [Figure 39C] 1 illustrates an exemplary user interface for navigating paginated content according to some embodiments. [Figure 39D] 1 illustrates an exemplary user interface for navigating paginated content according to some embodiments. [Figure 39E] 1 illustrates an exemplary user interface for navigating paginated content according to some embodiments. [Figure 39F] 1 illustrates an exemplary user interface for navigating paginated content according to some embodiments. [Figure 39G] 1 illustrates an exemplary user interface for navigating paginated content according to some embodiments. [Fig. 39H]1 illustrates an exemplary user interface for navigating paginated content according to some embodiments. [Figure 39I] 1 illustrates an exemplary user interface for navigating paginated content according to some embodiments. [Figure 39J] 1 illustrates an exemplary user interface for navigating paginated content according to some embodiments. [Figure 39K] 1 illustrates an exemplary user interface for navigating paginated content according to some embodiments.

[0096] [Figure 39L] 1 shows an example flow diagram illustrating operations that occur in response to received input (or portion(s) thereof) that meet various content navigation criteria, according to some embodiments.

[0097] [Figure 40A] 4 is a flow diagram illustrating a method for navigating paginated content according to some embodiments. [Figure 40B] 4 is a flow diagram illustrating a method for navigating paginated content according to some embodiments. [Figure 40C] 4 is a flow diagram illustrating a method for navigating paginated content according to some embodiments. [Figure 40D] 4 is a flow diagram illustrating a method for navigating paginated content according to some embodiments. [Figure 40E] 4 is a flow diagram illustrating a method for navigating paginated content according to some embodiments.

[0098] [Diagram 41] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

[0099] [Figure 42A]1 illustrates an example user interface for displaying contextual information associated with a point of interest in a map according to some embodiments. [Figure 42B] 1 illustrates an example user interface for displaying contextual information associated with a point of interest in a map according to some embodiments. [Figure 42C] 1 illustrates an example user interface for displaying contextual information associated with a point of interest in a map according to some embodiments. [Fig.42D] 1 illustrates an example user interface for displaying contextual information associated with a point of interest in a map according to some embodiments. [Figure 42E] 1 illustrates an example user interface for displaying contextual information associated with a point of interest in a map according to some embodiments. [Fig.42F] 1 illustrates an example user interface for displaying contextual information associated with a point of interest in a map according to some embodiments. [Fig.42G] 1 illustrates an example user interface for displaying contextual information associated with a point of interest in a map according to some embodiments. [Fig. 42H] 1 illustrates an example user interface for displaying contextual information associated with a point of interest in a map according to some embodiments. [Fig.42I] 1 illustrates an example user interface for displaying contextual information associated with a point of interest in a map according to some embodiments. [Fig.42J] 1 illustrates an example user interface for displaying contextual information associated with a point of interest in a map according to some embodiments. [Figure 42K] 1 illustrates an example user interface for displaying contextual information associated with a point of interest in a map according to some embodiments. [Figure 42L]1 illustrates an example user interface for displaying contextual information associated with a point of interest in a map according to some embodiments. [Figure 42M] 1 illustrates an example user interface for displaying contextual information associated with a point of interest in a map according to some embodiments. [Figure 42N] 1 illustrates an example user interface for displaying contextual information associated with a point of interest in a map according to some embodiments.

[0100] [Figure 43A] 4 is a flow diagram illustrating a method for displaying contextual information associated with a point of interest in a map, according to some embodiments. [Figure 43B] 4 is a flow diagram illustrating a method for displaying contextual information associated with a point of interest in a map, according to some embodiments. [Figure 43C] 4 is a flow diagram illustrating a method for displaying contextual information associated with a point of interest in a map, according to some embodiments. [Fig. 43D] 4 is a flow diagram illustrating a method for displaying contextual information associated with a point of interest in a map, according to some embodiments.

[0101] [Diagram 44] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

[0102] [Figure 45A] 1 illustrates an example user interface for zooming a map to display contextual information near a point of interest according to some embodiments. [Figure 45B] 1 illustrates an example user interface for zooming a map to display contextual information near a point of interest according to some embodiments. [Figure 45C] 1 illustrates an example user interface for zooming a map to display contextual information near a point of interest according to some embodiments. [Figure 45D] 1 illustrates an example user interface for zooming a map to display contextual information near a point of interest according to some embodiments. [Figure 45E] 1 illustrates an example user interface for zooming a map to display contextual information near a point of interest according to some embodiments. [Fig.45F] 1 illustrates an example user interface for zooming a map to display contextual information near a point of interest according to some embodiments. [Figure 45G] 1 illustrates an example user interface for zooming a map to display contextual information near a point of interest according to some embodiments. [Fig. 45H] 1 illustrates an example user interface for zooming a map to display contextual information near a point of interest according to some embodiments. [Fig.45I] 1 illustrates an example user interface for zooming a map to display contextual information near a point of interest according to some embodiments. [Figure 45J] 1 illustrates an example user interface for zooming a map to display contextual information near a point of interest according to some embodiments. [Figure 45K] 1 illustrates an example user interface for zooming a map to display contextual information near a point of interest according to some embodiments. [Figure 45L] 1 illustrates an example user interface for zooming a map to display contextual information near a point of interest according to some embodiments.

[0103] [Figure 46A] 4 is a flow diagram illustrating a method for zooming a map to display contextual information near a point of interest according to some embodiments. [Figure 46B] 4 is a flow diagram illustrating a method for zooming a map to display contextual information near a point of interest according to some embodiments. [Figure 46C] 4 is a flow diagram illustrating a method for zooming a map to display contextual information near a point of interest according to some embodiments. [Figure 46D] 4 is a flow diagram illustrating a method for zooming a map to display contextual information near a point of interest according to some embodiments.

[0104] [Figure 47] FIG. 2 is a functional block diagram of an electronic device according to some embodiments.

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

[0106] [Figure 49A] 4 is a flow diagram illustrating a method for displaying a menu including contact information according to some embodiments. [Figure 49B] 4 is a flow diagram illustrating a method for displaying a menu including contact information according to some embodiments. [Figure 49C] 4 is a flow diagram illustrating a method for displaying a menu including contact information according to some embodiments. [Figure 49D] 4 is a flow diagram illustrating a method for displaying a menu including contact information according to some embodiments. [Figure 49E] 4 is a flow diagram illustrating a method for displaying a menu including contact information according to some embodiments. [Fig.49F] 4 is a flow diagram illustrating a method for displaying a menu including contact information according to some embodiments.

[0107] [Figure 50] FIG. 2 is a functional block diagram of an electronic device according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[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 systems where a trackpad or touchscreen display senses a range of contact intensities that includes more than one or two particular intensity values ​​(e.g., more than a simple on / off, binary intensity determination), the user interface provides a response (e.g., visual and / or tactile cues) indicative of the intensity of the contact within that range. This provides the user with a continuous response to the force or pressure of the user's contact, thereby providing the user with richer and more intuitive visual and / or tactile feedback. For example, such a continuous force response gives the user the experience of being able to press lightly to preview an action and / or press deeply to reach a predefined user interface state that corresponds to that action.

[0110] In some embodiments, for a device having a touch-sensitive surface that is sensitive to a range of contact intensities, multiple contact intensity thresholds are monitored by the device and different responses are mapped to the contact intensity thresholds.

[0111] In some embodiments, for devices with touch-sensitive surfaces that are sensitive to a range of contact intensities, the device provides additional functionality by allowing a user to perform complex actions with a single sustained contact.

[0112] In some embodiments, for devices with touch-sensitive surfaces that sense a range of contact intensities, the device provides additional functionality that complements traditional functionality. For example, the 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 traditional functionality provided by traditional tap and swipe gestures. A user can continue to use traditional gestures to perform traditional functions (e.g., tapping an application icon on the home screen to launch the corresponding application) without accidentally activating the additional functionality. However, a user can also easily discover, understand, and use the intensity-based input and the additional functionality (e.g., pressing an application icon on the home screen brings up the application's quick action menu and lifting off on a menu item to perform an action within the application).

[0113] Several different techniques for operating a user interface are described herein. Using one or more of these techniques (optionally in conjunction with each other) helps provide a user interface that intuitively provides additional information and functionality to the user. Using one or more of these techniques (optionally in conjunction with each other) reduces the number, extent, and / or nature of input from the user, providing a more efficient human-machine interface. This allows users to use devices having touch-sensitive surfaces faster and more efficiently. For battery-operated devices, these improvements conserve power and extend the time between battery charges. Exemplary Devices

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

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

[0116] The terminology used in the description of the various embodiments described herein is for the purpose of describing particular embodiments only and is not intended to be limiting. When used in the description of the various described embodiments and in the appended concluding claims, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly indicates otherwise. It is also to be understood that the term "and / or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items. Furthermore, it will be understood that the terms "includes," "including," "comprises," and / or "comprising," as used herein, specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

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

[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 telephone, that 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 from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad), are also optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or a touchpad).

[0119] In the following discussion, we describe an electronic device with a display and a touch-sensitive surface, but it should be understood that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and / or a joystick.

[0120] The device typically supports a variety of applications, such as one or more of drawing applications, presentation applications, word processing applications, website creation applications, disc authoring applications, spreadsheet applications, gaming applications, telephony applications, video conferencing applications, email applications, instant messaging applications, training support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music playback applications, and / or digital video playback applications.

[0121] The various applications running on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and the corresponding information displayed on the device optionally adjust and / or change from one application to the next and / or within each application. In this manner, the common physical architecture (such as the touch-sensitive surface) of the device optionally supports a variety of applications with user interfaces that are intuitive and transparent to the user.

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

[0123] As used herein and in the claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that is to be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of the device is in contact with a touch-sensitive surface of a user (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement is interpreted by the user as a tactile sensation that corresponds to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down-click" or "up-click" of a physical actuator button. In some cases, the user feels a tactile sensation such as a "down-click" or "up-click" even when no movement of a physical actuator button associated with the touch-sensitive surface is physically pressed (e.g., displaced) by the user's movement. As another example, movement of the touch-sensitive surface is optionally interpreted or felt by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. Such user interpretation of touch depends on the user's individual sensory perception, but there are many sensory perceptions of touch that are common to a majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an "up click," a "down click," "roughness"), unless otherwise noted, the generated tactile output corresponds to a physical displacement of the device, or a component of a device, that produces the described sensory perception of a typical (or average) user.

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

[0125] Memory 102 optionally includes high-speed random access memory, and optionally also 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 peripherals interface 118, is optionally controlled by memory controller 122.

[0126] A peripheral interface 118 can be used to couple input and output peripherals of the device to the CPU(s) 120 and memory 102. The one or more processors 120 run or execute various software programs and / or instruction sets stored in the memory 102 to perform various functions for the device 100 as well as to process data.

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

[0128] The RF (Radio Frequency) circuitry 108 transmits and receives RF signals, also referred to as electromagnetic signals. The RF circuitry 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuitry 108 optionally includes well-known circuits for performing the above functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and the like. The RF circuitry 108 optionally communicates with networks such as the Internet, also referred to as the Internet Information Retrieval System (WWW), intranets and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and other devices by wireless communication.The wireless communication optionally uses any of a number of communication standards, protocols, and technologies, including Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPADA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), 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.11g). 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 Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communications protocol, including communications protocols not yet developed as of the filing date of this document.

[0129] The audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and the device 100. The audio circuitry 110 receives voice data from the peripherals interface 118, converts the voice data to an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal to sound waves audible to humans. The audio circuitry 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuitry 110 converts the electrical signal to voice data and sends the voice data to the peripherals interface 118 for processing. The voice data is optionally retrieved from and / or sent to the memory 102 and / or the RF circuitry 108 by the peripherals interface 118. In some embodiments, the audio circuitry 110 further comprises a headset jack (e.g., 212 in FIG. 2). The headset jack provides an interface between audio circuitry 110 and a removable audio input / output peripheral device, such as an output-only headphone or a headset that has both an output (e.g., one- or binaural headphones) and an input (e.g., a microphone).

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

[0131] Touch-sensitive display system 112 provides an input and output interface between the device and a user. Display controller 156 receives and / or transmits electrical signals from / to touch-sensitive display system 112. Touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output corresponds to a user interface object. As used herein, the term "affordance" refers to a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to input directed at that graphical user interface object). Examples of user-interactive graphical user interface objects include, but are not limited to, a button, a slider, an icon, a selectable menu item, a switch, or other user interface control.

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

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

[0134] 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 more). A user optionally contacts touch-sensitive display system 112 using any suitable object or appendage, such as a stylus, a finger, or the like. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on a touchscreen. In some embodiments, the device translates the coarse finger-based input into precise pointer / cursor position or commands to perform the user's desired action.

[0135] In some embodiments, in addition to a touchscreen, device 100 optionally includes a touchpad (not shown) for activating or deactivating certain functions. In some embodiments, a touchpad is a touch-sensitive area of ​​a device that, unlike a touchscreen, does not display visual output. The touchpad is optionally a touch-sensitive surface that is separate from 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 providing power to the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power within a portable device.

[0137] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 in I / O subsystem 106. Light sensor(s) 164 optionally include a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor(s) 164 receive light from the environment, projected through one or more lenses, and convert the light into data representing an image. In conjunction with imaging module 143 (also referred to as a camera module), light sensor(s) 164 optionally capture still images and / or video. In some embodiments, a light sensor is located on the back of device 100, opposite touch-sensitive display system 112 on the front of the device, so that the touch screen can be used as a viewfinder for still image and / or video capture. In some embodiments, another light sensor is located on the front of the device so that an image of the user can be obtained (e.g., for a selfie, for video conferencing while the user sees other video conferencing participants on the touch screen, etc.).

[0138] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor(s) 165 optionally include one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor(s) 165 receive contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite 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 proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is coupled to input controller 160 in I / O subsystem 106. In some embodiments, when the multifunction device is placed near a user's ear (e.g., when the user is making a phone call), the proximity sensor is turned off and touch-sensitive display system 112 is disabled.

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

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

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

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

[0144] The communications 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 circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE®, etc.) are adapted to couple directly or indirectly via a network (e.g., Internet, wireless LAN, etc.) to other devices. In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors identical to, similar to, and / or compatible with the 30-pin connectors used in some iPhone®, iPod Touch®, and iPad® devices of Apple Inc. of Cupertino, California. In some embodiments, the external ports are Lightning® connectors identical to, similar to, and / or compatible with the Lightning® connectors used in some iPhone®, iPod Touch®, and iPad® devices of Apple Inc. of Cupertino, California.

[0145] Contact / motion module 130 optionally detects contact with touch-sensitive display system 112 (in conjunction with display controller 156), as well as contact with other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes various software components for performing various operations related to detection of contact (e.g., by a finger or stylus), such as determining whether contact has occurred (e.g., detecting a finger down event), determining the strength of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting a drag event of one or more fingers), and determining whether contact has stopped (e.g., detecting a finger up event or an interruption of contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point represented by the 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., a single finger or stylus contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / movement module 130 and display controller 156 detect contacts on a touchpad.

[0146] Contact / movement module 130 optionally detects gesture input by a user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or intensity of detected contact). Thus, gestures are optionally detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger down event, followed by a finger up (lift off) event at the same location (or substantially the same location) as the finger down event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on a touch-sensitive surface includes detecting a finger down event, followed by one or more finger drag events, followed by a finger up (lift off) event. Similarly, stylus taps, swipes, drags, and other gestures are optionally detected by detecting a particular stylus contact pattern.

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

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

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

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

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

[0152] Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: ● a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ●Video conferencing module 139; ● an email client module 140; ● Instant messaging (IM) module 141; ● Training support module 142, A camera module 143 for still and / or video images, ● Image management module 144, ● Browser module 147, ● Calendar module 148, A widget module 149, optionally including one or more of a weather widget 149-1, a stock price widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6; ● a widget creation module 150 for creating user-created widgets 149-6; ● Search module 151, ● Optionally, a video and music playback module 152, which is composed 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 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA® enabled applications, encryption, digital rights management, voice recognition, and voice duplication.

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

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

[0156] Video conferencing module 139, in conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, includes executable instructions for initiating, conducting, and terminating a video conference between a user and one or more other participants in accordance with the user's instructions.

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

[0158] Instant messaging module 141, in conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, includes executable instructions for entering a series of characters corresponding to an instant message, modifying previously entered characters, sending the corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephone-based instant messaging, or using XMPP, SIMPLE, Apple Push Notification Service (APN), or IMPS for Internet-based instant messaging), receiving instant messages, and displaying received instant messages. In some embodiments, sent 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 Service (EMS). As used herein, "instant messaging" refers to both telephone-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, in conjunction with the RF circuitry 108, the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154, and the music playback module 146, includes executable instructions for creating workouts (e.g., having time, distance, and / or calorie burn goals), communicating with training sensors (in the sports device and the smart watch), receiving training sensor data, measuring sensors used to monitor the workouts, selecting and playing music for the workouts, and displaying, storing, and transmitting the workout data.

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

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

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

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

[0164] Widget modules 149, in conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, are mini-applications (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) that are optionally downloaded and used by a user, or mini-applications (e.g., user-created widget 149-6) that are created by a user. In some embodiments, a widget includes an HTML (HyperText Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widget).

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

[0166] Search module 151, in conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, contains executable instructions for searching for text, music, sound, images, video, and / or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with a user's instructions.

[0167] Video and music playback module 152, in conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, includes executable instructions that enable a user to download and play pre-recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions for displaying, presenting, or otherwise playing video (e.g., on touch-sensitive display system 112 or on an external display connected via wireless or 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 notes module 153, in conjunction with the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, and the text input module 134, contains executable instructions for creating and managing notes, to-do lists, and the like, as directed by a user.

[0169] Map module 154, in conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, contains executable instructions for receiving, displaying, modifying, and storing maps and data associated with maps (e.g., driving directions, data about businesses and other points of interest at or near a particular location, and other location-based data).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0183] 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, active event recognizer determination module 173 determines that only the hit view should accept a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that contain the physical location of the sub-events are actively participating views, and therefore all actively participating views should accept a particular sequence of sub-events. In other embodiments, views higher in the hierarchy will remain actively participating views even if the touch sub-events are completely confined to the area associated with a particular view.

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

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

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

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

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

[0189] The event comparator 184 compares the event information to predefined event or sub-event definitions and determines the event or sub-event or determines or updates the state of the event or sub-event based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes a definition of an event (e.g., a predefined sequence of sub-events), such as, for example, event 1 (187-1), event 2 (187-2), etc. In some embodiments, the sub-events in the event 187 include, for example, touch start, touch end, touch movement, touch stop, and multiple touches. In one example, the definition of event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch (touch start) for a given stage on the displayed object, a first lift off (touch end) for a given stage, a second touch (touch start) for a given stage on the displayed object, and a second lift off (touch end) for a given stage. In another embodiment, the definition of event 2 (187-2) is a drag on a displayed object. Dragging includes, for example, a touch (or contact) of a given degree on a displayed object, a movement of the touch across the touch-sensitive display system 112, and a lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

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

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

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

[0193] In some embodiments, each event recognizer 180 includes metadata 183 with configurable properties, flags, and / or lists that indicate how the event delivery system performs sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers may interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are distributed to various levels in a view hierarchy or programmatic hierarchy.

[0194] In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more particular sub-events of the event are recognized. In some embodiments, each event recognizer 180 distributes event information associated with the event to the event handler 190. A distinction is made between activating an event handler 190 and sending (and deferring sending) sub-events to the respective hit view. In some embodiments, the event recognizer 180 throws a flag associated with the recognized event, and the event handler 190 associated with the flag catches the flag and performs predefined processing.

[0195] In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions distribute the event information to event handlers associated with a set of sub-events or actively participating views. The event handlers associated with the set of sub-events or actively participating views accept the event information and perform the specified processing.

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

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

[0198] It will be understood that the foregoing discussion regarding event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 using input devices, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holds, touch movements such as tapping, dragging, scrolling on a touchpad, pen stylus input, device movement, oral communication, detected eye movement, biometric input, and / or any combination thereof, are optionally utilized as inputs corresponding to sub-events that define the event to be recognized.

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

[0200] Device 100 also optionally includes one or more physical buttons, such as a "home" or menu button 204. As mentioned above, menu button 204 is optionally used for navigation to any application 136 within a set of applications optionally executing 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 touch screen display, a menu button 204, a push button 206 for powering the device on / off and locking the device, a volume control button(s) 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and an external port 124 for docking / charging. Push button 206 is optionally used to turn power on / off on the device by pressing the button and holding it down for a predefined time interval, and to lock the device and / or unlock the device or initiate an unlocking process by pressing the button and releasing it before the predefined time interval has elapsed. In some embodiments, device 100 also accepts verbal input to activate or deactivate some features through microphone 113. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of a contact on touch-sensitive display system 112 and / or one or more tactile output generators 167 for generating a tactile output for a user of device 100.

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

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

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

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

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

[0207] 4B shows an example user interface on a device (e.g., device 300 of FIG. 3) with touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3) that is separate from 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 a contact on touch-sensitive surface 451 and / or one or more tactile output generators 359 for generating a tactile output to a user of device 300.

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

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

[0210] As used herein, the term "focus selector" refers to an input element that indicates the current portion of a user interface with which a user is interacting. In implementations that include a cursor or other location marker, the cursor acts as a "focus selector" when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element) when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 of FIG. 3 or touch-sensitive surface 451 of FIG. 4B), and the particular user interface element is adjusted according to the detected input. In some implementations that include a touchscreen display (e.g., touch-sensitive display system 112 of FIG. 1A or touchscreen of FIG. 4A) that allows direct interaction with user interface elements on the touchscreen display, contact detected on the touch screen serves as a "focus selector" such that when an input (e.g., a press input by contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface (e.g., by using the tab or arrow keys to move focus from one button to another) without a corresponding cursor movement or contact movement on the touchscreen display. In these implementations, the focus selector moves to follow the movement of focus between different regions of the user interface. Regardless of the particular form that the focus selector takes, the focus selector is generally a user interface element (or a contact on a touchscreen display) controlled by the user to convey the user's intended interaction with the user interface (e.g., by indicating to the device which element of the user interface the user wants to interact with).For example, the location of a focus selector (e.g., a cursor, contact, or selection box) over the respective button when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen) indicates that the user is about to activate the respective button (as opposed to other user interface elements displayed on the device's display).

[0211] As used herein and in the claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., finger or stylus contact) on the touch-sensitive surface, or a surrogate (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values, including at least four different values, and more typically including hundreds or more different values ​​(e.g., at least 256). The intensity of a contact is optionally determined (or measured) using a variety of methods and a variety of sensors, or combinations of sensors. For example, one or more sensors disposed under 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, the force measurements of multiple force sensors are combined (e.g., weighted average or sum) to determine an estimated force of the contact. Similarly, a 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 capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact, are optionally used as a proxy for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the proxy measure of the force or pressure of the contact is used directly to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the proxy measure). In some implementations, the proxy measure of the force or pressure of the contact is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of contact as an attribute of user input allows a user access to additional device functionality that may not otherwise be accessible to a user on devices sized with a 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 controls such as knobs or buttons).

[0212] In some embodiments, the contact / movement module 130 uses a set of one or more intensity thresholds for determining whether an action has been performed by the user (e.g., for determining whether the user has "clicked" on an icon). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of a particular physical actuator and may be adjusted without changing the physical hardware of the device 100). For example, the mouse "click" threshold of a trackpad or touchscreen display may be set to any of a wide range of predefined thresholds without changing the trackpad or touchscreen display hardware. Additionally, in some implementations, a user of the device is provided with a software setting to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds upon a system-level click of an "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 a plurality of intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected within a predefined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting a contact, before detecting lift-off of the contact, before or after detecting the start of movement of the contact, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of the contact is optionally based on one or more of the maximum intensity of the contact, the mean of the intensity of the contact, the average of the intensity of the contact, the top 10 percentiles of the intensity of the contact, half the maximum intensity of the contact, 90 percent of the maximum intensity of the contact, etc. In some embodiments, the duration of the contact is used to determine the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is performed by the user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity not exceeding the first threshold results in a first action being performed, a contact having a characteristic intensity exceeding the first intensity threshold and not exceeding the second intensity threshold results in a second action being performed, and a contact having a characteristic intensity above the second intensity threshold results in a third action being performed. 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 (e.g., to perform a respective option or to omit performing a respective action).

[0214] In some embodiments, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact (e.g., a drag gesture) that transitions from a start location to an end location at which the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location may be based on only a portion of the continuous swipe contact (e.g., only the portion of the swipe contact at the end location) rather than the entire continuous swipe contact. In some embodiments, a smoothing algorithm may be applied to the intensity of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some situations, these smoothing algorithms exclude small increases or decreases in the intensity of the swipe contact for purposes of determining the characteristic intensity.

[0215] The user interface diagrams described herein may include one or more intensity thresholds (e.g., a contact detection intensity threshold IT 0 , Light pressure intensity threshold IT L , (e.g., at least initially I L (higher than the deep pressure intensity threshold IT D , and / or one or more other intensity thresholds (e.g., I L An intensity threshold lower than I H), which indicates the current intensity of a contact on the touch-sensitive surface relative to a specific intensity of the touch-sensitive surface. The intensity graphs are typically not part of the displayed user interface, but are provided to aid in interpretation of those graphs. In some embodiments, the light press intensity threshold corresponds to an intensity that will cause the device to perform an action typically associated with a physical mouse button or a trackpad click. In some embodiments, the deep press intensity threshold corresponds to an intensity that will cause the device to perform an action different from the action typically associated with a physical mouse button or a trackpad click. In some embodiments, a slight contact detection intensity threshold IT below the light press intensity threshold (e.g., and below which a contact is no longer detected) is set. 0 If a contact is detected having a characteristic intensity (greater than or equal to the light pressure intensity threshold), the device moves the focus selector according to the movement of the contact on the touch-sensitive surface without performing any action associated with the light pressure intensity threshold or the deep pressure intensity threshold. Generally, unless otherwise noted, these intensity thresholds are consistent across different sets of user interface views.

[0216] In some embodiments, the device's response to an input detected by the device depends on criteria based on the contact intensity during the input. For example, for some "light press" inputs, the 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 criteria including both the contact intensity during the input and a time-based criterion. For example, for some "deep press" inputs, the 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 intensity threshold and meeting the second intensity threshold. 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. As another example, for some "deep press" inputs, there is a desensitization period that occurs after the time when the first intensity threshold is met. During this desensitization period, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep press inputs. For other deep press inputs, the response to the detection of a deep press input does not depend on a time-based criterion.

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

[0218] For example, FIG. 4C illustrates 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 predefined delay p1 from when touch input 476 is first detected, and a second component 478 that tracks the intensity of touch input 476 over time. The intensity threshold of the first component 474, which has a high initial value, reduces accidental triggering of a "deep press" response, while still allowing an immediate "deep press" response if touch input 476 provides sufficient intensity. The second component 478 reduces unintentional triggering of a "deep press" response by gradually varying the intensity of the touch input. In some embodiments, when 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 illustrates another dynamic intensity threshold 486 (e.g., intensity threshold I D ) is shown in FIG. 4D. H and a second intensity threshold I L In FIG. 4D, the touch input 484 crosses the first intensity threshold I before time p2. H and a second intensity threshold I L Although the second intensity threshold I is met, no response is provided until a delay time p2 has elapsed at time 482. Also in FIG. 4D, the dynamic intensity threshold 486 decays over time. This decay occurs after time 482 (the second intensity threshold I L This type of dynamic intensity threshold starts at time 488 after a predefined delay time p1 has elapsed from when the response associated with the first intensity threshold I H or the second intensity threshold I L Immediately after or simultaneously with triggering a response associated with a lower intensity threshold, such as D and reducing accidental triggering of the associated response.

[0220] FIG. 4E illustrates yet another dynamic intensity threshold 492 (e.g., intensity threshold I D4E, the intensity threshold I is increased after a delay time p2 has elapsed since the touch input 490 was first detected. L At the same time, the dynamic intensity threshold 492 decays after a predefined delay time p1 from when the touch input 490 is first detected. L If the intensity of the touch input 490 decreases after triggering a response associated with the intensity threshold I, and then the intensity of the touch input 490 increases without releasing the touch input 490, the intensity of the touch input 490 may increase beyond, for example, the intensity threshold I. L Even if it is below another intensity threshold, such as intensity threshold I D A response associated with the may be triggered (eg, at time 494).

[0221] Light pressure intensity threshold IT L From the intensity below the light pressure intensity threshold IT L and deep pressure intensity threshold IT D An increase in the characteristic intensity of a contact from an intensity below the deep press intensity threshold IT to an intensity between the deep press intensity threshold IT D An increase in the characteristic strength of a contact to an intensity above the contact-detection strength threshold I T 0 From the intensity below the contact detection intensity threshold IT 0 and light pressure intensity threshold IT L An increase in the characteristic intensity of the contact to an intensity between 0 and 100 may be referred to as detecting a contact on the touch surface. 0 From the intensity exceeding the contact detection intensity threshold IT 0 A decrease in the characteristic intensity of the contact to an intensity below I T may be referred to as detecting lift-off of the contact from the touch surface. 0 is zero. In some embodiments, IT 0 is greater than zero. In some figures, shaded circles or ellipses are used to represent the intensity of a contact on the touch-sensitive surface. In some figures, unshaded circles or ellipses are used to represent each contact on the touch-sensitive surface without specifying the intensity of each contact.

[0222] In some embodiments described herein, one or more actions are performed in response to detecting a gesture including a respective pressure input or in response to detecting a respective pressure input performed with a respective contact (or multiple contacts), where the respective pressure inputs are detected based at least in part on detecting an increase in intensity of the contact (or multiple contacts) above a pressure input threshold intensity. In some embodiments, the respective actions are performed in response to detecting an increase in intensity of the respective contact to an intensity above the pressure input threshold intensity (e.g., the respective actions are performed by a "downstroke" of the respective pressure input). In some embodiments, the pressure input includes an increase in intensity of the respective contact to an intensity above the pressure input threshold intensity and a subsequent decrease in intensity of the contact below the pressure input threshold intensity, where the respective actions are performed in response to detecting a subsequent decrease in intensity of the respective contact below the pressure input threshold (e.g., the respective actions are performed by an "upstroke" of the respective pressure 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 predefined relationship to the pressure input threshold intensity (e.g., the hysteresis intensity threshold is X intensity units below the pressure input threshold intensity, or 75%, 90%, or some reasonable percentage of the pressure input threshold intensity). Thus, in some embodiments, the pressure input includes an increase in the intensity of each contact to an intensity above the pressure input threshold intensity, and a subsequent decrease in the intensity of each contact below the respective hysteresis intensity threshold, and a respective action is performed in response to detecting the subsequent decrease in the intensity of each contact to an intensity below the hysteresis intensity threshold (e.g., each action is performed by an "upstroke" of the corresponding pressure input). Similarly, in some embodiments, a pressure input is detected only if the device detects an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the pressure input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and a respective action is performed in response to detecting that pressure input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, as the case may be).

[0224] For ease of explanation, the description of actions performed in response to a press input associated with a press input threshold intensity or in response to a press input gesture is optionally triggered in response to detecting an increase in the intensity of the contact above the press input threshold intensity, an increase in the intensity of the contact from an intensity below a hysteresis intensity threshold to an intensity above the press input threshold intensity, a decrease in the intensity of the contact below the press input threshold intensity, or a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input threshold intensity. Additionally, in examples where an action is described as being performed in response to detecting a decrease in the intensity of the contact below a press input intensity threshold, the action is optionally performed in response to detecting a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold and below the press input intensity threshold. As mentioned above, in some embodiments, the triggering of these responses also depends on a time-based criterion being met (e.g., a delay has elapsed between the first intensity threshold being met and the second intensity threshold being met). User Interface and Related Processes

[0225] Attention now turns to embodiments of a user interface "UI" and associated processes that may be implemented on an electronic device, such as portable multifunction device 100 or device 300, that 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 with 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 portable multifunction device 100, the display is touch-sensitive display system 112, and the touch-sensitive surface includes tactile output generator 167 on the display ( FIG. 1A ). For ease of explanation, the described embodiments are discussed with reference to operations performed on a device with touch-sensitive display system 112. In such embodiments, the focus selector is optionally a respective finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., a centroid of the respective contact or a point associated with the respective contact), or a centroid of two or more contacts detected on touch-sensitive display system 112. However, in response to detecting a contact on touch-sensitive surface 451 while displaying the user interface shown in these figures on display 450 with a focus selector, similar operations are optionally performed on a device with display 450 and separate touch-sensitive surface 451.

[0227] 5A-5AW illustrate an exemplary user interface for quickly invoking one of several actions associated with a respective application without first activating the respective application, according to some embodiments. In some embodiments, this is accomplished by providing the user with a menu (e.g., a "quick action menu") containing quick action items for the respective application upon detecting a user input that is distinct (e.g., based on the amount of force the user applies) from a traditional user input used to launch an 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 an intensity threshold). This allows the user to modify their input to avoid unintentionally activating the quick action menu. This also helps the user determine the amount of force required to invoke the quick action menu. Exemplary quick action functions are described in Appendix A.

[0228] The user interfaces in these figures are used to illustrate the processes described below. Although some of the examples below are presented with reference to input on a touchscreen display (where the touch-sensitive surface and display are combined), in some embodiments the device detects input on touch-sensitive surface 451, which is separate from display 450, as shown in FIG.

[0229] 5A-5G, 5I-5W, 5Y-5AA, 5AC-5AJ, and 5AL-5AW illustrate an example user interface of a home screen for displaying a number of 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 upon detecting an application launch input (e.g., a tap gesture having a maximum intensity below a threshold for invoking a quick action menu). Some of the launch icons are also associated with a corresponding quick action menu that is activated on the electronic device upon detecting a quick action display input (e.g., a force press gesture having a maximum intensity equal to or greater than a threshold for invoking a quick action menu).

[0230] 5A-5H illustrate an embodiment in which a user may invoke a quick action display menu and an action to reply to a recent message from a home screen of electronic device 100. FIG. 5A illustrates a home screen user interface 500 displaying application launch icons for several applications, including a message icon 424 for activating a messaging application. The device may display an intensity threshold (e.g., IT) required to invoke the quick action menu in FIG. 5B. L ) on the message icon 424. In FIG. 5C, the intensity of the contact 502 is increased to a “hint” threshold (e.g., IT H), but still below the intensity threshold required to invoke the quick actions menu. The device notifies the user that they are approaching the intensity required to invoke the quick actions menu by blurring other activation icons and beginning to move them further away in virtual z-space (e.g., away from the screen) and by providing a hint graphic 503 emerging from beneath the message icon 424. As shown in FIG. 5D, the icon blurring, icon movement in z-space, and hint graphic are indicative of the intensity threshold being exceeded when the user clicks the quick actions menu. L ) the hint graphic 503 continues to grow and begins to move away from under the message icon 424.

[0231] In FIG. 5E, the intensity of the contact 502 increases to the threshold (e.g., IT L ) in response, hint graphic 503 changes to quick action menu 504, displaying icons and text for each of the selections 506, 508, 510, and 512 that are now available to the user. The device also provides tactile feedback 513 to inform the user that the quick action menu is now functional. Although the user lifts off contact 502 in FIG. 5F, quick action menu 504 is still displayed on touch screen 112 because it is a selection menu. As shown in FIG. 5G, the user selects to respond to Mom's message by tapping (via contact 514) on option 508 in quick action menu 504. In response, the device activates the messaging application and displays user interface 501 including a text prompt for replying to Mom's message, rather than opening the application to a default user interface (e.g., a view of the last received message).

[0232] FIG. 5I illustrates an alternative hint state in accordance with some embodiments, in which a messaging icon 424 increases in size (e.g., simulating the icon moving off the screen toward the user) in response to a contact 516 having an intensity above the “hint” threshold but below the “quick action menu” intensity threshold.

[0233] 5J-5N illustrate an embodiment in which a user initiates invocation of a quick action menu but does not reach the required intensity threshold. In FIG. 5J, device 100 displays the intensity threshold (e.g., IT) required to invoke the quick action menu displayed within home screen user interface 500. L ) on the message icon 424. In FIGS. 5K and 5L, the intensity of the contact 518 is increased to a “hint” threshold (e.g., IT H ), but still below the intensity threshold required to invoke the quick actions menu. The device informs the user that they are approaching the intensity required to invoke the quick actions menu by dynamically blurring other launching icons, dynamically pushing back other icons in virtual z-space (e.g., shrinking them relative to the message icon 424), and providing a hint graphic 503 that dynamically emerges from under the message icon 424. However, FIG. 5M illustrates that the intensity threshold required to invoke the quick actions menu (e.g., IT L 5N , the user lifts off contact 518. The intensity of contact 518 is shown to decrease before the intensity of contact 518 reaches the intensity threshold (e.g., IT 100) required to invoke the quick action menu. In response, the device dynamically reverses the blurring and shrinking of the icon and begins to shrink the hint graphic 503 that notified the user that they were approaching the quick action intensity threshold. In FIG. 5N , the user lifts off contact 518. L ), the device returns the display of user interface 500 to the same state it was in before contact 518 was detected.

[0234] 5O-5R illustrate an embodiment in which a user performs a gesture that meets the quick action display input criteria at an activation icon that does not have an associated quick action menu. In FIG. 5O, device 100 displays the intensity threshold (e.g., IT) required to invoke the quick action menu displayed within home screen user interface 500. L ) on the settings activation icon 446. In FIG. 5P, the intensity of the contact 520 increases to a “hint” threshold (e.g., IT H ), but still below the intensity threshold required to invoke the quick actions menu. The device informs the user that they are approaching the intensity required to invoke the quick actions menu by (e.g., dynamically) blurring other launch icons. However, because Settings launch icon 446 is not associated with the quick actions menu, the device does not provide a hint graphic (e.g., like hint graphic 503 in FIG. 5C ). In FIG. 5Q , the intensity of contact 520 increases to the threshold (e.g., IT L ), however, because there is no Settings launch icon 446 associated with it, the device does not display a quick action menu. Instead, the device provides negative haptic feedback 522, distinct from the positive haptic feedback 513 shown in FIG. 5E, to indicate to the user that there is no Settings launch icon 446 quick action menu available. The device then returns the display of user interface 500 to the same state it was in before contact 520 was detected in FIG. 5R, regardless of whether the user lifts off contact 520.

[0235] 5S-5U illustrate an embodiment in which a user invokes a quick action menu at an activation icon in the upper left section of touch screen 112. In FIG. 5J, device 100 displays the intensity threshold (e.g., IT) required to invoke the quick action menu displayed in the upper left section of home screen user interface 500. L) on the message icon 424. In FIG. 5T, the intensity of the contact 524 is increased to a “hint” threshold (e.g., IT H ), but still below the intensity threshold required to invoke the quick actions menu. The device notifies the user that they are approaching the intensity required to invoke the quick actions menu by dynamically blurring other activation icons and by providing a hint graphic 503 that dynamically appears from under the message icon 424.

[0236] In FIG. 5U, the intensity of contact 524 increases to reach the threshold required to invoke the quick action menu (e.g., IT L), the hint graphic 503 changes to a quick action menu 528, displaying icons and text for each of the selections 506, 508, 510, and 512 that are now 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 with the left edge of the message launch icon 424, instead of the right edge as shown in FIG. 5E (e.g., when the message launch icon 424 was displayed on the right side of the touch screen 112). Similarly, the icons associated with the options 506, 508, 510, and 512 are aligned with the left side of the quick action menu 528, instead of the right edge as shown in FIG. 5E. Also, because the launch icon is displayed on the top half of the touch screen 112, the quick action menu 528 is displayed below the message launch icon 424, instead of above it as shown in FIG. 5E (e.g., when the message launch icon 424 was displayed on the bottom half of the touch screen 112). Similarly, the vertical order of options 506, 508, 510, and 512 is reversed from the quick action menu 504 of FIG. 5E, so that the relative distance of each option to the message launch icon 424 in the message quick action menus 504 and 528 is the same (e.g., the option to transcribe a new message 512 to reply to a recently received message takes priority over options 506, 508, and 510, so option 512 appears closest to the message launch icon 424 in both quick action menus).

[0237] 5V-5AF illustrate alternative user inputs for performing various actions after invoking a quick actions menu, according to some embodiments.

[0238] In FIG. 5V, the user invokes the message quick action menu 528 on the home screen user interface 500 via contact 524 and then slides contact 524 over option 508 to reply to the message from Mom, as shown in FIG. 5W. As shown in FIG. 5W, the user modulates the intensity of contact 524 to exceed the quick action menu intensity threshold (e.g., IT L ) above the contact 524. The user then lifts off contact 524 while over option 508, and the device activates the messaging application and displays user interface 501 including a text prompt to reply to Mom's message, as shown in FIG.

[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 in a default state by displaying user interface 535 including a display of the most recently 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 at a location on the touch screen 112 other than where the message launch icon 424 and quick action menu 528 are displayed via contact 538, as shown in Figure 5AE. In response, the device clears the quick action menu 528 and returns the display of the user interface 500 to the same state it was in before contact 524 was detected, as shown in Figure 5AF.

[0241] 5AG-5AK illustrate an embodiment in which a user performs a preferred action via activation of a quick action menu via a press. In FIG. 5AG, device 100 displays a strength threshold (e.g., IT) required to invoke the quick action menu displayed in home screen user interface 500. L 5AH and 5AI, the intensity of the contact 540 is increased to a "hint" threshold (e.g., IT H ), but still below the intensity threshold required to invoke the quick actions menu. The device informs the user that they are approaching the intensity required to invoke the quick actions menu by dynamically blurring other activation icons, dynamically pushing back other icons in virtual z-space (e.g., shrinking them relative to the message icon 424), and providing a hint graphic 503 that dynamically emerges from under the message icon 424.

[0242] In FIG. 5AJ, the intensity of the contact 540 increases to the threshold required to invoke the message quick action menu 504 (e.g., IT L ) in response, hint graphic 503 changes to quick action menu 504, displaying icons and text for each selection that is now available to the user, such as selection 512 for the 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 invoking quick action menu 504, the intensity of contact 540 continues to increase until it exceeds a third intensity threshold (e.g., IT D In response, the device activates the associated messaging application in a preferred state (e.g., corresponding to option 512) by displaying user interface 541 for composing a new message, as shown in FIG. 5AK.

[0243] 5AL-5AN illustrate an embodiment in which a user invokes a quick action menu on a launch icon of a folder that contains launch icons of multiple applications with associated notifications. In FIG. 5AL, device 100 determines the intensity threshold (e.g., IT L ) on networking launch icon 488. Networking launch icon 488 is associated with a folder that, when activated, opens to reveal launch icons of multiple applications (e.g., launch icons "F," "T," and "L") that are represented on networking launch icon 488. As shown in FIG. 5AL, the applications associated with launch icons stored in the networking folder have seven combined user notifications.

[0244] In FIG. 5AM, the intensity of contact 542 is increased to reach a “hint” threshold (e.g., IT H ), but still below the intensity threshold required to invoke the quick actions menu. The device notifies the user that they are approaching the intensity required to invoke the quick actions menu by dynamically blurring other launch icons and by providing a hint graphic 543 that dynamically emerges from beneath the networking launch icon 488. In FIG. 5AN, the intensity of contact 542 increases to indicate that the intensity is approaching the threshold required to invoke the quick actions menu (e.g., IT L ) in response, hint graphic 543 changes to quick action menu 544, displaying icons and text for each selection 546, 548, 550, and 552 that is now available to the user. The icons displayed for each selection are graphical representations of launch icons for applications associated with one or more of the seven notifications. The text displayed for each selection is the name of the notification associated with the respective application.

[0245] 5AO-5AQ illustrate an embodiment in which a user invokes a quick action menu on a launch icon of a third-party application. In FIG. 5AO, device 100 determines the intensity threshold (e.g., IT L ) on the training activation icon 442. In FIG. 5AP, the intensity of the contact 554 is increased to a “hint” threshold (e.g., IT H ), but still below the intensity threshold required to invoke the quick action menu. The device notifies the user that they are approaching the intensity required to invoke the quick action menu by dynamically blurring other launch icons and by providing a hint graphic 556 that dynamically appears from under the training launch icon 442. In FIG. 5AQ, the intensity of contact 554 increases to indicate that the intensity is approaching the threshold (e.g., IT L ) in response, hint graphic 556 changes to a quick action menu 558 displaying icons and text for each selection 560, 562, 564, 566, and 568 that is now available to the user. Selection 568 allows the user to share the third party application with a friend (e.g., by sending the friend a link to download the third party application from an application store).

[0246] 5AR-5AT illustrate an embodiment in which a user invokes a quick action menu at an activation icon in the upper right section of touch screen 112. In FIG. 5AR, device 100 displays the intensity threshold (e.g., IT) required to invoke the quick action menu in the upper left section of home screen user interface 500. L ) on the message icon 424. In FIG. 5AS, the intensity of the contact 570 is increased to a “hint” threshold (e.g., IT H), but still below the intensity threshold required to invoke the quick actions menu. The device notifies the user that they are approaching the intensity required to invoke the quick actions menu by dynamically blurring other activation icons and by providing a hint graphic 569 that dynamically appears from under the message icon 424.

[0247] In FIG. 5AT, the intensity of contact 570 is increased to reach the threshold required to invoke the quick action menu (e.g., IT L ) in response to the touch screen graphic 569 changes to a quick action menu 571 that displays the icons and text of each of the selections 506, 508, 510, and 512 that are now available to the user. Because the launch icons are displayed on the right side of the screen 112, the quick action menu 571 is aligned with the right edge of the message launch icon 424. Similarly, the icons associated with the options 506, 508, 510, and 512 are aligned with the right side of the quick action menu 571. Because the launch icons are displayed on the top half of the touch screen 112, the quick action menu 571 is displayed below the message launch icon 424. Similarly, the vertical order of the options 506, 508, 510, and 512 is reversed from the quick action menu 504 of FIG. 5E.

[0248] 5AU-5AW illustrate an embodiment in which a user invokes a quick action menu at an activation icon in the lower left section of touch screen 112. In FIG. 5AU, device 100 displays the intensity threshold (e.g., IT) required to invoke the quick action menu in the lower left section of home screen user interface 500. L ) on the message icon 424. In FIG. 5AV, the intensity of the contact 572 is increased to a “hint” threshold (e.g., IT H), but still below the intensity threshold required to invoke the quick actions menu. The device notifies the user that they are approaching the intensity required to invoke the quick actions menu by dynamically blurring other activation icons and by providing a hint graphic 573 that dynamically appears from under the message icon 424.

[0249] In FIG. 5AW, the intensity of contact 572 is increased to reach the threshold required to invoke the quick action menu (e.g., IT L ) in response to the touch screen 573, the quick action menu 574 changes to display the icons and text of each of the selections 506, 508, 510, and 512 that are now available to the user. Because the launch icons are displayed on the left side of the screen 112, the quick action menu 574 is aligned with the left edge of the message launch icon 424. Similarly, the icons associated with the options 506, 508, 510, and 512 are also aligned with the left side of the quick action menu 574. Because the launch icons are displayed on the bottom half of the touch screen 112, the quick action menu 574 is displayed above the message launch icon 424. Similarly, the vertical order of the options 506, 508, 510, and 512 is the same as the quick action menu 504 of FIG. 5E.

[0250] 6A-6AS illustrate exemplary embodiments of a user interface that allows a user to efficiently navigate between a first user interface and a second user interface, according to some embodiments. In some embodiments, this is accomplished by providing a user with the ability to preview the content of the second user interface without leaving the first user interface upon detecting a user input that is distinct (e.g., based on the amount of force applied by the user) from traditional user inputs used to navigate between user interfaces. In some embodiments, the user interface provides a user with the ability to perform actions associated with the second user interface while previewing. Although some of the examples below are presented with reference to an email messaging application, the methods may be implemented within any number of different applications, as described herein.

[0251] The user interfaces in these figures are used to illustrate the processes described below. Although some of the examples below are presented with reference to input on a touchscreen display (where the touch-sensitive surface and display are combined), in some embodiments the device detects input on touch-sensitive surface 451, which is separate from display 450, as shown in FIG.

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

[0253] 6A-6G illustrate an embodiment in which a user previews the contents of an email from an email inbox and then navigates to the email with a single gesture. FIG. 6A illustrates an email inbox displaying partial views of email messages, including a partial view of email message 602. Device 100 determines the intensity threshold (e.g., IT) required to invoke a preview of the email in FIG. 6B. L 6C, the intensity of the contact 610 increases to above the "hint" threshold (e.g., IT), but not to the intensity threshold required to invoke the preview area of ​​the email (e.g., IT L ) the device will begin to blur other partial views of the email (e.g., away from the screen) and move further back in virtual z-space to indicate that the user is approaching the intensity required to invoke the preview area. As shown in FIG. 6D, the blurring and movement further back in virtual z-space occurs when the preview area is close to the threshold (e.g., IT L ) to dynamically respond to increases in the intensity of contact 610 below.

[0254] In FIG. 6E, the intensity of the contact 610 is increased to reach the threshold (e.g., ITL ) in response, the device displays a preview area 612 over a portion of the partial view of the email message in the user interface 600. This preview displays a view of the email that includes 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 the preview area has been activated. The user continues to increase the intensity of contact 610 between FIGS. 6E and 6F until a third threshold (e.g., IT D ) in response, the device navigates to user interface 614 to display the full email associated with partial view 602 and preview area 612, as shown in FIGURE 6F. The device also provides tactile feedback 615, distinct from tactile feedback 611, to inform the user that navigation to the full email has occurred. As shown in FIGURE 6G, the device maintains the display of user interface 614 after the user has finished input (e.g., contact 610).

[0255] 6H-6K illustrate an embodiment in which a user begins to invoke a full-text preview of an email associated with partial view 602, but does not reach the required intensity threshold. In FIG. 6H, device 100 detects the intensity threshold (e.g., IT) required to invoke a preview of an email displayed within email inbox user interface 600. L 6I, the intensity of the contact 616 is increased to a “hint” threshold (e.g., IT H ) but not exceeding the intensity threshold required to invoke the email preview area (e.g., IT L) the device will signal that the user is approaching the intensity required to invoke the preview area by beginning to blur other partial views of the email (e.g., away from the screen) and move them further away in virtual z-space. However, Figure 6J shows that the intensity threshold required to invoke the preview area (e.g., IT L ), the device dynamically reverses the blur of the other partial views and moves them forward in virtual z-space. In FIG. 6K, the user lifts off contact 616. The intensity of contact 616 drops below the intensity threshold required to navigate to the full-text version of the email (e.g., the IT D ), the device returns the display of user interface 600 to the same state it was in before contact 616 was detected.

[0256] 6L-6O illustrate an embodiment in which a user activates 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 FIG. 6L, device 100 detects an intensity threshold (e.g., IT) required to invoke a preview of an email displayed within email inbox user interface 600. L ) on the partial view of the email message 602. In FIG. 6M, the device detects a contact 618 on the partial view of the email message 602 when the intensity of the contact 618 increases to a value below a preview area invocation threshold (e.g., IT L), the device displays preview area 612. The device also displays caret 619 to inform the user that selectable actions can be revealed by swiping up on touch screen 112. As shown in FIG. 6N, the user moves contact 620 up on touch screen 112. In FIG. 6O, in response to detecting the movement of contact from location 618-a to location 618-b, preview area 612 moves up on the display and selectable action options 624, 626, and 628 appear below the preview area. The device also provides tactile feedback 6123, distinct from tactile feedback 611 and 615, to inform the user that more actions are available. As shown in FIG. 6P, the device maintains the display of preview area 612 after the user lifts off contact 618 to reveal selectable action options 624, 626, and 628.

[0257] 6Q-6W illustrate an embodiment in which a user previews the contents of an email and then deletes the email with a single gesture. In FIG. 6R, device 100 detects the intensity threshold (e.g., IT) required to invoke a preview of an email displayed within email inbox user interface 600. L 6R, the device detects a contact 630 on the partial view of the email message 602 having an intensity below a preview area invocation threshold (e.g., IT L6S, the user begins to move contact 630 (via movement 632) to the left on touch screen 112. In response, in FIGS. 6T-6U, preview area 612 moves with the contact, gradually revealing action icon 634 from below the preview area. As the user continues to move preview area 612 to the left, action icon 634 changes color, as shown in FIG. 6V, to notify the user that an associated action (e.g., deleting the email from the inbox) is active for execution once contact ends. As shown in FIG. 6W, when the user lifts contact 630 off touch screen 112 while the action associated with action icon 634 is active, the device ceases displaying 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 partial views of other emails up in user interface 600 to reveal the next partial view of email 636.

[0258] 6X-6AC illustrate an embodiment in which a user begins to delete an email while in preview mode, but does not reach the location threshold required to activate the delete action. In FIG. 6X, device 100 detects the intensity threshold (e.g., IT) required to invoke a preview of the email displayed in email inbox user interface 600. L ) on the partial view of the email message 602. In FIG. 6Y, the device detects contact 638 on the partial view of the email message 602 when the intensity of contact 638 increases to a value below a preview area invocation threshold (e.g., IT L) is exceeded. In FIG. 6Z, the user begins to move contact 638 (via movement 640) to the left on touch screen 112. In response, in FIG. 6AA, preview area 612 moves with the contact, partially revealing action icon 634 from beneath the preview area. The user increases the strength of contact 638 to exceed a navigation threshold (e.g., IT D ), but because the user partially manifested the associated action (e.g., action icon 634), the device locks out navigation commands. Because the user did not swipe left enough on preview area 612 (e.g., as indicated by action icon 634 not switching color in FIG. 6AB), the device then restores the display of email inbox user interface 600 to the state it was in before contact 634 was detected upon lift-off in FIG. 6AC.

[0259] 6AD-6AH illustrate an embodiment in which a user previews an email and begins to navigate to the full-text email, but does not reach the required intensity threshold. In FIG. 6AD, device 100 detects the intensity threshold (e.g., IT) required to invoke a preview of an email displayed within email inbox user interface 600. L ) on the partial view of email message 602. In FIG. 6AE, the device detects contact 642 on the partial view of email message 602 when the intensity of contact 642 increases to a value below a preview area invocation threshold (e.g., IT L ) to display preview area 612. As the user continues to increase the strength of contact 642, the device increases the size of preview area 612 in FIG. 6AF to notify the user that they are approaching the strength threshold required to navigate to the full email. However, FIG. 6AG does not show how the strength threshold (e.g., IT D6AH, the user lifts off contact 642. The intensity of contact 642 is shown to decrease before reaching the intensity threshold (e.g., IT D ), the device returns the display of user interface 600 to the same state it was in before contact 642 was detected.

[0260] 6A-6A show a user previewing a full-text email and then navigating to the full-text email, crossing the preview area display threshold twice. In FIG. 6A, device 100 crosses the intensity threshold (e.g., IT) required to invoke a preview of an email displayed within email inbox user interface 600. L ) on the partial view of the email message 602. In FIG. 6AJ, the intensity of the contact 644 is increased to a "hint" threshold (e.g., IT H ) but not exceeding the intensity threshold required to invoke the email preview area (e.g., IT L ) the device signals that the user is approaching the intensity required to invoke the preview area by beginning to blur and move other partial views of the email further away in virtual z-space. In FIG. 6AE, the device detects that the intensity of contact 644 has increased to the point where it is below the preview area display threshold (e.g., IT L ) and, in response to detecting that the preview area display threshold (e.g., IT), the user reduces the intensity of contact 644 below the preview area display threshold, as illustrated by the dynamic reversal of blurring of the partial view of the email message displayed behind preview area 612 in FIG. 6AL. However, because the user has not ended contact 644, the device maintains the display of preview area 612. The user subsequently increases the intensity of contact 644 between FIGS. 6AL and 6AM, causing the device to display the preview area display threshold (e.g., IT L) again. In response, the device navigates to user interface 614 to display the full email associated with partial view 602 and preview area 612, as shown in FIG.

[0261] 6AN-6AS illustrate an 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 FIG. 6AN, device 100 detects an intensity threshold (e.g., IT) required to invoke a preview of an email displayed within email inbox user interface 600. L ) on the partial view of email message 602. In FIG. 6AO, the device detects contact 646 on the partial view of email message 602 when the intensity of contact 646 increases to a value below a preview area invocation threshold (e.g., IT L 6A-6W, the device displays the preview area 612 in response to detecting that the contact exceeds the threshold 648 of the touch screen 112. In FIG. 6AP, the user begins to move the contact 646 (via movement 648) to the right on the touch screen 112. In response, in FIGS. 6AQ-6AR, the preview area 612 moves with the contact, gradually revealing an action icon 650 from below the preview area. In FIG. 6AR, the action icon 650 changes color to signal that an associated action (e.g., flagging an email) is active for execution upon contact termination. In comparison to the quick delete action shown in FIGS. 6Q-6W, in FIG. 6AR, the user does not have to move the preview area 612 far to invoke the flagging action. As shown in FIG. 6AS, when the user lifts the contact 646 off the touch screen 112 while the action associated with the action icon 650 is active, the device terminates display of the preview area 612 and flags a partial view of the email message 602 via a change in the appearance of the indicator icon 652.

[0262] 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 first having to activate the second application. According to some embodiments, the exemplary user interface illustrated in FIGS. 7A-7AQ also allows a user to efficiently navigate between a first and a second user interface. In some embodiments, when the exemplary user interface detects a user input that is distinguishable (e.g., based on the amount of force the user applies) from a traditional user input used to switch between applications, the exemplary user interface provides the user with a menu that includes quick action items (e.g., a "quick action menu") associated with the other user interface (e.g., the other application). Similarly, in some embodiments, when the exemplary user interface detects a user input that is distinguishable (e.g., based on the amount of force the user applies) from a traditional user input used to navigate between user interfaces, the exemplary user interface allows a 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 a user is about to invoke a quick action menu (e.g., when a user input approaches an intensity threshold). Although some of the examples below are presented with reference to an email messaging application, in some embodiments, the 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. Although some of the examples below are presented with reference to input on a touchscreen display (where the touch-sensitive surface and display are combined), in some embodiments the device detects input on touch-sensitive surface 451, which is separate from display 450, as shown in FIG.

[0264] 7A-7R and 7U-7AP illustrate an example user interface 700 for viewing an email message including a user interface object associated with a second application. For example, the contact icon 702 is associated with contact information in a contact management application that is activated (e.g., launched) on the electronic device 100 upon detecting an application launch input (e.g., a tap gesture having a maximum intensity below a threshold for invoking a quick action menu). The contact icon 702 is also associated with a quick action menu that includes options for performing actions associated with the contact management program upon detecting a quick action display input (e.g., a force press gesture having a maximum intensity equal to or greater than a threshold for invoking a quick action menu). Similarly, the date and time 704 is associated with a calendar application that is activated (e.g., launched) on the electronic device 100 upon detecting an application launch input (e.g., a tap gesture having a maximum intensity below a threshold for invoking a preview of content associated with the calendar application). The date and time 704 is also associated with a potential new event in the calendar application with additional content that becomes available upon detecting a preview area display input (e.g., a force press gesture having a maximum intensity equal to or greater than the threshold for invoking the preview area).

[0265] 7A-7O illustrate an 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 a touch recognized in the email. FIG. 7A shows an email message viewing user interface 700 displaying a contact icon 702 and a date and time 704. In FIG. 7B, the device determines the intensity threshold (e.g., IT) required to invoke a preview area of ​​the associated event in the calendar application. L ) on the date and time 704. In FIG. 7C, the intensity of the contact 706 increases to a "hint" threshold (e.g., IT H ) but not exceeding the intensity threshold required to invoke the preview area of ​​the event (e.g., IT L ) the device notifies the user that they are 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 by increasing the size of the date and time 704 (e.g., giving the user the appearance that the date and time are moving forward in virtual z-space relative to other user interface objects). As shown in FIG. 7D, the blurring and the movement forward in virtual z-space occurs when the preview area is close to the intensity required to invoke the preview area. L ) to dynamically respond to increases in the intensity of contact 706 below.

[0266] In FIG. 7E, the intensity of the contact 706 increases to a threshold (e.g., IT L) in response, the device displays a preview area 707 over a portion of the email message in user interface 700. The preview area displays a view of a calendar user interface for creating a new event based on the date and time information in the email. The device also provides tactile feedback 705 to inform the user that the preview area has been activated. In FIG. 7F, the device displays an intensity threshold (e.g., IT D 7G, the user 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 ), the device lifts contact 706 off of touch screen 112. Because the preview area did not include one or more selectable action options, the device stops displaying preview area 707 and returns the display of user interface 700 to the same state it was in before contact 706 was detected.

[0267] In FIG. 7H, the device detects the intensity threshold (e.g., IT L ) on the contact icon 702. In FIG. 7I, the intensity of the contact 708 is increased to a “hint” threshold (e.g., IT H ) but still below the intensity threshold required to invoke the quick actions menu. The device notifies the user that they are approaching the intensity required to invoke the quick actions menu by beginning to blur other objects in the user interface 700, including the date and time 704, and by increasing the size of the contact icon 702 (e.g., giving the user the appearance that the contact icon is moving forward in virtual z-space relative to other user interface objects). As shown in FIG. 7J, the blurring and the movement forward in virtual z-space increases the intensity required to invoke the quick actions menu by beginning to blur other objects in the user interface 700, including the date and time 704, and by increasing the size of the contact icon 702 (e.g., giving the user the appearance that the contact icon is moving forward in virtual z-space relative to other user interface objects).L ) to dynamically respond to increases in the intensity of contact 708 below.

[0268] In FIG. 7K, the intensity of the contact 708 increases to the threshold required to invoke the quick action menu (e.g., IT L ) in response. In response, contact icon 702 changes to a quick action menu 710 that displays options for navigating to Harold Goffrey's contact information within contact management application 712, calling Harold using phone information associated with contact management application 714, sending Harold a message using contact information associated with contact management application 716, and sending an email message to Harold using email address information associated with the contact management application. The device also provides tactile feedback 711, distinct from tactile feedback 705, to inform the user that the quick action menu is now functional. Because the quick action menu 710 includes selectable options for performing actions, the device maintains the display of the menu even when the user reduces the intensity of contact 708 in FIG. 7L and then lifts the contact off of touch screen 112 in FIG. 7M. The user then clears the quick action menu by tapping (via contact 720) on the touch screen anywhere other than where the quick action menu 710 is displayed.

[0269] 7P-7T illustrate an embodiment in which a user previews the contents of a new event and then navigates to an associated user interface in a calendar application with a single gesture. The device 100 determines the intensity threshold (e.g., IT) required to invoke the preview of the new event. L ) on the date and time 704 in the email viewing user interface 700. In FIG. 7Q, the intensity of the contact 722 increases to a “hint” threshold (e.g., IT H) but not exceeding the intensity threshold required to invoke the email preview area (e.g., IT L ) the device signals that the user 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 by increasing the size of the date and time 704. In FIG. 7R, the device indicates that the intensity of contact 722 has increased to the point where it exceeds the preview area invocation threshold (e.g., IT L 7R and 7S, the user continues to increase the intensity of the contact 722 until a third threshold (e.g., IT D ) in response, the device navigates to a user interface 724 in the calendar application to display a form for creating an event based on the contents of the email being viewed in the user interface 700, as shown in FIG 7S. Because the device navigates out of the messaging application, lifting contact 722 off causes the display of the new event user interface 724 in the calendar application to remain visible, as shown in FIG 7T.

[0270] In contrast, Figures 7U-7Y show an embodiment in which the same input that navigated to the calendar application in Figures 7P-7T does not leave the email message application when performed on a contact icon (e.g., a user interface object associated with a quick action menu). In Figure 7U, device 100 determines the intensity threshold (e.g., IT) required to invoke the quick action menu. L ) on the contact icon 702. In FIG. 7V, the intensity of the contact 708 increases to a “hint” threshold (e.g., IT H) but still below the intensity threshold required to invoke the quick actions menu. The device signals that the user is approaching the intensity required to invoke the quick actions menu by beginning to blur other objects in the user interface 700, including the date and time 704, and by increasing the size of the contact icon 702. In FIG. 7W, the device detects that the intensity of contact 726 has increased to the point where it exceeds the quick actions menu threshold (e.g., IT L 7W and 7X, the user continues to increase the intensity of the contact 726 to exceed a third threshold (e.g., IT D ) However, unlike date and time 704, image icon 702 is not associated with a navigation action even when it detects an intensity above a third threshold. Therefore, device 100 simply maintains display of quick action menu 710 after detecting increased intensity of contact 726 in FIG. 7X and lift-off in FIG. 7Y.

[0271] 7Z-7AE illustrate an embodiment in which a user may preview a potential new event in a calendar event and subsequently create the calendar event with a single gesture without leaving an email messaging application. In FIG. 7Z, device 100 determines the intensity threshold (e.g., IT) required to invoke a preview of the potential new event. L 7AA, the device detects a contact 728 on the date and time 704 having an intensity below a preview area invocation threshold (e.g., IT L), the device displays preview area 707. The device also displays caret 729 to inform the user that one or more actions associated with the preview area can be revealed by swiping right on touch screen 112. In FIG. 7AB, the user begins to move contact 728 (via movement 730) to the right on touch screen 112. In response, in FIGS. 7AC-7AD, preview area 707 moves with the contact and gradually reveals action icon 732 from below the preview area. As shown in FIG. 7AC, navigation to a calendar application by further increasing the intensity of contact 728 (e.g., as shown in FIGS. 7R-7S) is disabled by the movement of contact. As the user continues to move preview area 707 to the right, as shown in FIG. 7AD, action icon 732 changes color to inform the user that an associated action (e.g., creating a calendar event based on information provided in the email displayed in user interface 700) is active for execution when contact ends. As shown in FIG. 7AE, when the user lifts contact 732 off touch screen 112 while the action associated with action icon 732 is active, the device ceases displaying preview area 707 and creates a new event (not shown).

[0272] In contrast, Figures 7AF-7AJ show an embodiment in which the same swipe input that created the calendar event in Figures 7Z-7AE is inactive when performed on a contact icon (e.g., a user interface object associated with a quick action menu). In Figure 7AF, device 100 detects the intensity threshold (e.g., IT L ) on the contact icon 702. In FIG. 7AG, the device detects a contact 732 on the contact icon 702 having an intensity below a quick action menu threshold (e.g., IT L7AI), the device 100 displays the quick action menu 710 in response to detecting that the activation contact 732 has exceeded the threshold 734. In FIG. 7AH, the user begins to move contact 732 to the right (via movement 734) on the touch screen 112. However, unlike the date and time 704, the image icon 702 is not associated with an action upon detecting the movement of the activation contact to the right. Therefore, the device 100 simply maintains the display of the quick action menu 710 after detecting the movement of contact 732 in FIG. 7AI and the lift-off in FIG. 7AJ.

[0273] 7AK-7AO illustrate an embodiment in which a user begins to create a new calendar event while navigating within an email messaging application, but does not reach the location threshold required to activate the create action. In FIG. 7AK, device 100 detects the intensity threshold (e.g., IT) required to invoke a preview of the email. L ) on the contact icon 702. In FIG. 7AL, the device detects a contact 736 on the contact icon 702 having an intensity below a preview area invocation threshold (e.g., IT L 7AM, the user begins to move contact 736 to the right on touch screen 112 (via movement 738). In response, in FIG. 7AN, preview area 707 moves with the contact, partially revealing action icon 732 from beneath preview area 707. Because the user did not swipe preview area 707 far enough to the left (e.g., as indicated by action icon 732 not switching color in FIG. 7AN), the device then restores email browsing us...

Claims

1. 1. An electronic device comprising a display and a touch-sensitive surface, displaying on the display a first user interface including a plurality of selectable objects associated with respective information; detecting an input while displaying the plurality of selectable objects, the input including detecting contact with the touch-sensitive surface at a location corresponding to each selectable object; In response to detecting the input, in response to a determination that the input satisfies input criteria, including criteria that are met when the contact with the touch-sensitive surface meets a respective input threshold; displaying a menu for each of the selectable objects including the respective information for each of the selectable objects overlaid on the first user interface including the plurality of selectable objects; blurring at least one other selectable object among the plurality of selectable objects other than each of the selectable objects while displaying the menu; replacing a representation of the first user interface including the plurality of selectable objects with a representation of a second user interface associated with each of the selectable objects in response to a determination that detecting the input includes detecting a lift-off of the contact without the input satisfying the input criterion; A method comprising:

2. In response to detecting the input, The method of claim 1 , further comprising: displaying additional descriptive information describing the respective selectable object in response to a determination that detecting the input includes detecting the contact satisfying the input criteria.

3. The method of claim 1 , further comprising applying a visual effect while displaying the menu that obscures the first user interface including the plurality of selectable objects.

4. detecting a predefined release gesture toward a location outside the menu on the first user interface while displaying the menu for the respective selectable object; In response to detecting the predetermined release gesture, ceasing to display said menu for each said selectable object; restoring a display of the first user interface including the plurality of selectable objects; The method of claim 1 , comprising:

5. the menu includes one or more communication objects, the method comprising: detecting a movement of the contact on the touch-sensitive surface corresponding to a movement of a focus selector to a respective communicating object of the one or more communicating objects on the display while the contact on the touch-sensitive surface is maintained; detecting a portion of the input that satisfies a selection criterion while the focus selector is on the respective communicating object; in response to detecting the portion of the input that satisfies the selection criteria, initiating a communication function corresponding to the respective communicating object; The method of claim 1 , comprising:

6. The method of claim 5 , wherein the portion of the input that satisfies the selection criterion is a terminal portion of the input.

7. The method of claim 5 , wherein the portion of the input that satisfies the selection criterion corresponds to a change in intensity of the contact.

8. The method of claim 5 , wherein initiating the communication function corresponding to the respective communicating object comprises initiating a communication corresponding to the respective communicating object.

9. initiating the communication function corresponding to the respective communicating object in response to detecting the portion of the input that satisfies the selection criteria. In response to detecting the portion of the input that satisfies the selection criterion, initiating communication with the respective selectable object at a default selection among a plurality of selections associated with the respective communicating object in response to a determination that the focus selector is located at a first portion of the respective communicating object; displaying the plurality of options associated with the respective communicating object for the respective selectable object in accordance with a determination that the focus selector is located on a second portion of the respective communicating object; The method of claim 5 , comprising:

10. The method of claim 9 , wherein the plurality of options associated with the respective communicating object evolve from the respective communicating object.

11. detecting a selection of each option of the plurality of options associated with each of the communicating objects; In response to detecting the selection of the respective option, initiating a communication corresponding to the respective option; 10. The method of claim 9, comprising:

12. The method of claim 1 , wherein the respective information includes one or more of the following: one or more phone numbers, one or more email addresses, one or more geographic addresses, and one or more message contact addresses or identification information.

13. The method of claim 1 , wherein the plurality of selectable objects associated with contact information includes a representation of a user associated with the respective information.

14. each said selectable object being an avatar, said method comprising: The method of claim 1 , further comprising: displaying an enlarged version of the avatar within the menu in response to a determination that detecting the input comprises detecting the contact satisfying the input criteria.

15. The method of claim 1 , wherein the plurality of selectable objects associated with contact information includes a representation of a location associated with the respective information.

16. The method of claim 1 , wherein the menu includes a header, the header including additional information regarding each of the selectable objects.

17. Each of the selectable objects occupies a portion of a second selectable object, the method comprising: detecting a second input, including detecting a second contact on the touch-sensitive surface satisfying the respective input threshold while displaying the plurality of selectable objects and while a focus selector is in a respective position corresponding to a respective portion of the second selectable object; In response to detecting the second input, displaying the menu for the respective selectable object including the respective information for the respective selectable object in accordance with a determination that the respective locations correspond to the respective selectable objects, overlaid on the first user interface including the plurality of selectable objects; displaying content associated with the second selectable object distinct from the menu for the respective selectable object in response to a determination that the respective location corresponds to a portion of the second selectable object other than the respective selectable object; The method of claim 1 , comprising:

18. displaying content associated with the second selectable object that is different from the menu for the respective selectable object; displaying a preview area including a reduced representation of the second user interface overlaid on at least some of the plurality of selectable objects in the first user interface in accordance with a determination that a first portion of the second input satisfies a preview criterion; and replacing a display of the first user interface and the superimposed preview area with a display of the second user interface in accordance with a determination that a second portion of the second input, detected after the first portion of the input, satisfies a user interface replacement criterion; in accordance with a determination that the second portion of the second input satisfies a preview area disappearance criterion, ceasing to display the preview area after the input is terminated and displaying the first user interface; 20. The method of claim 17, comprising:

19. 20. The method of claim 18, wherein determining that the first portion of the second input satisfies a preview criterion comprises detecting that the second contact during the first portion of the second input satisfies a first input threshold.

20. 20. The method of claim 18, wherein determining that the second portion of the second input satisfies a user interface replacement criterion comprises detecting that the second contact during the second portion of the second input satisfies a second input threshold that is greater than a first input threshold.

21. 20. The method of claim 18, wherein determining that the second portion of the second input satisfies a preview area disappearance criterion comprises detecting a lift-off of the second contact during the second portion of the second input without satisfying the user interface replacement criterion.

22. The method of claim 18, comprising applying a visual effect to obscure the first user interface while displaying the preview area.

23. 1. An electronic device comprising: A display and a touch-sensitive surface; and one or more processors; Memory, and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing any of the methods of claims 1 to 22.

24. 23. A computer program comprising instructions which, when executed by an electronic device having a display and a touch-sensitive surface, cause the device to perform any of the methods recited in claims 1 to 22.

25. 1. An electronic device comprising: A display and a touch-sensitive surface; and and means for performing any of the methods according to claims 1 to 22.

Images