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

By detecting input intensity on touch-sensitive surfaces, electronic devices can perform user interface manipulations more efficiently, addressing inefficiencies in existing methods and conserving energy, thereby improving interaction speed and user satisfaction.

JP7577102B2Active Publication Date: 2024-11-01APPLE INC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2022181211
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2016-08-08
Filing Date
2022-11-11
Publication Date
2024-11-01
Estimated Expiration
2036-08-09

AI Technical Summary

Technical Problem

Existing methods for manipulating user interfaces on electronic devices with touch-sensitive surfaces are cumbersome, inefficient, and energy-intensive, particularly in battery-operated devices.

Method used

The implementation of electronic devices with touch-sensitive surfaces that detect input intensity, allowing for faster and more efficient user interface manipulation through methods that reduce the number and variety of user inputs, conserve power, and enhance interaction efficiency.

Benefits of technology

These methods enable quicker and more efficient user interface operations, reducing energy consumption and enhancing user satisfaction by allowing for intuitive and dynamic interactions without the need for traditional, energy-intensive input processes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007577102000004
    Figure 0007577102000004
  • Figure 0007577102000005
    Figure 0007577102000005
  • Figure 0007577102000006
    Figure 0007577102000006
Patent Text Reader

Abstract

A visual feedback method and electronic device are provided that make user interface operations efficient and intuitive. The method detects a first portion of a first input while displaying a first form of a notification associated with a first application overlaid on a background user interface, and launches the first application in accordance with a determination that the first portion of the first input satisfies an application launch criterion. The launching stops displaying the background user interface and displays a user interface associated with the first application. The method also displays a second form of notification in accordance with a determination that the first portion of the first input satisfies a notification enlargement criterion. The second form of notification has a second size larger than the first size, includes enlarged notification content not displayed in the first form of notification, and is overlaid on the background user interface.
Need to check novelty before this filing date? Find Prior Art

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 operating 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 touchscreen displays. Such surfaces are widely used to operate user interfaces on 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, associating metadata with one or more user interface objects, or otherwise manipulating the user interface. Exemplary user interface objects include digital images, video, text, icons, and control elements such as buttons and other graphics.

[0004] Users may, in some circumstances, perform such operations through file management programs (e.g., Finder by Apple Inc., Cupertino, California), messaging applications (e.g., Messages by Apple Inc., Cupertino, California), photo management applications (e.g., Photos by Apple Inc., Cupertino, California), camera applications (e.g., Camera by Apple Inc., Cupertino, California), map applications (e.g., Maps by Apple Inc., Cupertino, California), note-taking applications (e.g., Notes by Apple Inc., Cupertino, California), digital content (e.g., video and music) management applications (e.g., Music and iTunes by Apple Inc., Cupertino, California), news applications (e.g., News by Apple Inc., Cupertino, California), phone applications (e.g., Apple Inc. (Cupertino, California)), email applications (e.g., Mail by Apple Inc. (Cupertino, California)), 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)), book applications (e.g., iBooks by Apple Inc. (Cupertino, California)), video creation applications (e.g., Apple Inc.This needs to be done for user interface objects within applications such as iMovie (by Apple Inc., Cupertino, California), and / or geolocation applications (e.g., Find Friends and Find iPhone (by Apple Inc., Cupertino, California)).

[0005] However, existing methods for performing these operations are cumbersome and inefficient. Moreover, existing methods waste energy by taking longer than necessary. This latter consideration is especially important in battery-operated devices. Summary of the Invention

[0006] Therefore, there is a need for electronic devices with faster, more efficient methods and interfaces for operating a user interface. Such methods and interfaces, optionally complementing or replacing conventional methods for operating a user interface, reduce the number, range, and / or type of inputs from a user, creating a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.

[0007] The above-mentioned deficiencies and other problems associated with user interfaces for electronic devices with touch-sensitive surfaces are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, 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 "touchscreen display"). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or instruction sets stored in the memory for performing multiple 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, the functionality optionally includes 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 functionality 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 comprising a display, a touch-sensitive surface, and one or more sensors for detecting an intensity of a contact on the touch-sensitive surface. The device simultaneously displays on the display a background user interface and a first form of notification associated with a first application, where the first form of notification has a first size, the first form of notification includes first content, and the first form of notification is overlaid on the background user interface. While the first form of notification associated with the first application overlaid on the background user interface is displayed, the device detects a first portion of a first input, which includes detecting a first contact at a location on the touch-sensitive surface that corresponds to the first form of notification. In response to detecting the first portion of the first input, the device initiates a process to launch a first application according to a determination that the first portion of the first input satisfies application launch criteria, where the application launch criteria do not require a characteristic intensity of the first contact on the touch-sensitive surface to meet a preview intensity threshold, and launching the first application includes ceasing to display a background user interface and displaying a user interface associated with the first application, and the device displays a second form of notification according to a determination that the first portion of the first input satisfies notification magnification criteria, where the notification magnification criteria require a characteristic intensity of the first contact on the touch-sensitive surface to meet a preview intensity threshold, the second form of notification having a second size that is larger than the first size, the second form of notification including magnified notification content that is not displayed in the first form of notification, and the second form of notification is overlaid on the background user interface.

[0009] According to some embodiments, there is an electronic device including a display unit configured to display a user interface, a touch-sensitive surface unit configured to receive contacts by a user, one or more sensor units configured to detect intensity of contacts with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit simultaneously enables display on the display unit of a background user interface and a first form of notification associated with a first application, where the first form of notification has a first size, includes first content, and is overlaid on the background user interface. While the first form of notification associated with the first application overlaid on the background user interface is displayed, the processing unit detects a first portion of a first input, which includes detecting a first contact at a location on the touch-sensitive surface unit that corresponds to the first form of notification. In response to detecting the first portion of the first input, the processing unit initiates a process to launch the first application in accordance with a determination that the first portion of the first input satisfies an application launch criterion, where the application launch criterion does not require that the characteristic intensity of the first contact on the touch-sensitive surface meet a preview intensity threshold for the application launch criterion to be met, and where launching the first application includes ceasing to display a background user interface and displaying a user interface associated with the first application.In response to detecting the first portion of the first input, the processing unit enables display of a second form of notification in accordance with a determination that the first portion of the first input satisfies a notification magnification criterion, where the notification magnification criterion requires that a characteristic intensity of the first contact on the touch-sensitive surface meets a preview intensity threshold for the notification magnification criterion to be met, the second form of notification has a second size that is greater than the first size, the second form of notification includes enlarged notification content that is not displayed in the first form of notification, and the second form of notification is overlaid on a background user interface.

[0010] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting an intensity of a contact on the touch-sensitive surface. The method includes: displaying a user interface on the display including a plurality of application icons corresponding to different applications of a plurality of applications; detecting a first input while the user interface including the plurality of application icons is displayed, the detecting the first input including detecting a first contact on the touch-sensitive surface at a location on the touch-sensitive surface that corresponds to a first application icon of the plurality of application icons, the first application icon being associated with the first application of the plurality of applications; responsive to detecting the first input, launching the first application in accordance with a determination that the first input satisfies an application launch criterion; and replacing the display of the user interface including the plurality of application icons with a user interface of the first application. the application launch criteria do not require a characteristic intensity of the first contact on the touch-sensitive surface to satisfy a first intensity threshold for the application launch criteria to be met; and in accordance with a determination that the first input satisfies the menu presentation criteria, simultaneously displaying a contextual content object and a corresponding affordance associated with the contextual content object, wherein the menu presentation criteria require a characteristic intensity of the first contact on the touch-sensitive surface to satisfy a first intensity threshold for the menu presentation criteria to be met, the contextual content object includes contextually selected content from the first application based on a current context of the electronic device, and the corresponding affordance is configured, upon actuation, to add the contextual content object to a user interface that includes information about the multiple applications.

[0011] According to some embodiments, an electronic device includes a display unit configured to display one or more user interfaces; a touch-sensitive surface unit configured to receive contacts by one or more users; one or more sensor units configured to detect an intensity of contacts with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units.The processing unit enables display on the display unit of a user interface including a plurality of application icons corresponding to different applications of the plurality of applications; detects a first input while display of the user interface including the plurality of application icons is enabled, where detecting the first input includes detecting a first contact on the touch-sensitive surface unit at a location on the touch-sensitive surface unit that corresponds to a first application icon of the plurality of application icons, the first application icon being associated with the first application of the plurality of applications; and detects, in response to detecting the first input, that the first input satisfies an application launch criterion, the application launch criterion not requiring that a characteristic intensity of the first contact on the touch-sensitive surface meet a first intensity threshold for the application launch criterion to be satisfied. the first input is a menu presentation criterion that requires a characteristic intensity of the first contact on the touch-sensitive surface to satisfy a first intensity threshold for the menu presentation criterion to be satisfied; the contextual content object includes contexted selected content that is automatically selected from the first application based on a current context of the electronic device, and the corresponding affordance is configured, upon activation, to add the contextual content object to the user interface that includes information about the plurality of applications; and the method is configured to simultaneously enable display of the contextual content object and the corresponding affordance associated with the contextual content object in accordance with the determination that the menu presentation criterion is satisfied.

[0012] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting an intensity of a contact on the touch-sensitive surface. The method includes: displaying a user interface on the display including a plurality of user interface objects corresponding to different applications of a plurality of applications, the plurality of user interface objects including a first user interface object corresponding to a first application that is in the process of downloading; detecting a first input while the user interface including the plurality of user interface objects is displayed, the first input including detecting a first contact at a location on the touch-sensitive surface corresponding to the first user interface object; and displaying one or more first selectable options that, upon activation, are configured to perform an action related to downloading the first application in accordance with a determination that, in response to detecting the first input, the first user interface object corresponds to an application that has not completed downloading and that the first input satisfies menu presentation criteria, the menu presentation criteria requiring that a characteristic intensity of the contact at the detected input meets a first intensity threshold for the menu presentation criteria to be met.

[0013] 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 contacts by a user, one or more sensor units configured to detect intensity of contacts with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: enable display of a user interface on the display unit including a plurality of user interface objects corresponding to different applications of the plurality of applications, the plurality of user interface objects including a first user interface object corresponding to a first application that is in the process of downloading; detect a first input while the display of the user interface including the plurality of user interface objects is enabled, the first input including detecting a first contact at a location on the touch-sensitive surface unit that corresponds to the first user interface object; and enable display of one or more first selectable options that, upon activation, are configured to perform an action related to downloading the first application in accordance with a determination that, in response to detecting the first input, the first user interface object corresponds to an application that has not completed downloading; and a determination that the first input satisfies a menu presentation criterion that requires that a characteristic intensity of the contact at the detected input meets a first intensity threshold for the menu presentation criterion to be satisfied.

[0014] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors for detecting an intensity of a contact on the touch-sensitive surface. The method includes: displaying a user interface on the display, the user interface including a folder icon corresponding to an application folder including a plurality of application icons, the plurality of application icons corresponding to different applications of the plurality of applications, the plurality of applications including one or more applications having one or more unread notifications; detecting a first input while the user interface including the folder icon is displayed, the first input including detecting a first contact at a location on the touch-sensitive surface corresponding to the folder icon; and in response to detecting the first input, displaying one or more selectable options according to a determination that the first input satisfies menu presentation criteria, the one or more selectable options being configured, upon actuation, to launch a corresponding application from the plurality of applications in the application folder having the unread notifications, the menu presentation criteria requiring that a characteristic intensity of the contact in the detected input meets a first intensity threshold for the menu presentation criteria to be met.

[0015] 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 contacts by a user, one or more sensor units configured to detect intensity of contacts with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: enable display of a user interface on the display unit, the user interface including a folder icon corresponding to an application folder including a plurality of application icons, the plurality of application icons corresponding to different applications of the plurality of applications, the plurality of applications including one or more applications having one or more unread notifications; detect a first input while the display of the user interface including the folder icon is enabled, the first input including detecting a first contact at a location on the touch-sensitive surface corresponding to the folder icon; and in response to detecting the first input, enable display of one or more selectable options according to a determination that the first input satisfies menu presentation criteria, the one or more selectable options being configured, upon actuation, to launch a corresponding application from the plurality of applications in the application folder having the unread notifications, the menu presentation criteria requiring that a characteristic intensity of the contact in the detected input meets a first intensity threshold for the menu presentation criteria to be met.

[0016] According to some embodiments, a method is performed in an electronic device that includes a display, a touch-sensitive surface, and one or more sensors that detect an intensity of contact with the touch-sensitive surface. The method includes displaying a control user interface including a plurality of control affordances; detecting on the display a first input by contact at a location on the touch-sensitive surface corresponding to a first control affordance of the plurality of control affordances; in response to detecting the first input, toggling a function of a control corresponding to the first control affordance in accordance with a determination that the first input satisfies a control toggle criterion, the control toggle criterion not requiring a characteristic intensity of the contact to satisfy a first intensity threshold for the control toggle criterion to be satisfied; displaying one or more change options for the control corresponding to the first control affordance in accordance with a determination that the first input satisfies an extended control criterion, the extended control criterion requiring a characteristic intensity of the contact to satisfy a first intensity threshold for the extended control criterion to be satisfied; detecting a second input while the one or more change options for the control corresponding to the first control affordance are displayed, the second input activating a first change option of the one or more change options; and modifying the control corresponding to the first control affordance in accordance with the activated first change option.

[0017] 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 contacts by a user, one or more sensor units configured to detect intensity of contact with 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. The processing unit enables display of a control user interface including a plurality of control affordances, detects on the display unit a first input by contact at a location on the touch-sensitive surface unit that corresponds to a first control affordance of the plurality of control affordances, and, in response to detecting the first input, toggles a function of a control corresponding to the first control affordance in accordance with a determination that the first input satisfies a control toggle criterion that does not require that a characteristic intensity of the contact meet a first intensity threshold for the control toggle criterion to be satisfied, and the extended control criterion requiring that the characteristic intensity of the contact meet a first intensity threshold for the extended control criterion to be met; in accordance with a determination of satisfying the extended control criterion, enable display of one or more change options for the control corresponding to the first control affordance; activate a first change option of the one or more change options while the display of the one or more change options for the control corresponding to the first control affordance is enabled; detect a second input; and modify the control corresponding to the first control affordance according to the activated first change option.

[0018] According to some embodiments, a method is performed on an electronic device comprising a display, a touch-sensitive surface, and one or more sensors that detect an intensity of contact with the touch-sensitive surface. The method includes: displaying a user interface including an editable content region having a plurality of characters and a content deletion control; detecting a delete input, the delete input including detecting a contact on the display at a location on the touch-sensitive surface that corresponds to the content deletion control; and, in response to detecting the delete input, deleting content within the editable content region based on a duration and a characteristic intensity of the contact, wherein, pursuant to a determination that the contact has been maintained for a first period of time without the characteristic intensity of the contact increasing above a first intensity threshold, successively deleting the plurality of content subunits of a first type of content subunit at a rate that does not vary based on the characteristic intensity of the contact. removing the content within the editable content area by successively deleting a plurality of content sub-units of the second type of content sub-units at a rate that does not vary based on the characteristic intensity of the contact pursuant to a determination that the characteristic intensity of the contact has increased above the first intensity threshold; and removing the content within the editable content area by successively deleting a plurality of content sub-units of the second type at a rate that varies based on the characteristic intensity of the contact pursuant to a determination that the characteristic intensity of the contact has increased above the first intensity threshold.

[0019] According to some embodiments, an electronic device includes a display unit configured to display one or more user interfaces, a touch-sensitive surface unit configured to receive a contact by a user, one or more sensor units configured to detect an intensity of the 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 including an editable content region having a plurality of characters and a content deletion control; detects a delete input, including detecting a contact on the display unit at a location on the touch-sensitive surface unit that corresponds to the content deletion control; and, in response to detecting the delete input, deletes the content in the editable content region by successively deleting a plurality of content subunits of a first type of content subunit at a rate that does not vary based on a duration and a characteristic intensity of the contact, and in accordance with a determination that the contact has been maintained for a first period of time without the characteristic intensity of the contact increasing above a first intensity threshold. deleting content in the editable content area based on the characteristic intensity, including deleting a plurality of content sub-units of the second type of content sub-units in accordance with a determination that the contact has been maintained for a second time period, the second time period being longer than the first time period, without the characteristic intensity of the contact increasing above a first intensity threshold; and deleting content in the editable content area by successively deleting a plurality of content sub-units of the second type of content sub-units at a rate that does not vary based on the characteristic intensity of the contact in accordance with a determination that the characteristic intensity of the contact has increased above the first intensity threshold.

[0020] According to some embodiments, a method is performed on an electronic device comprising a display, a touch-sensitive surface, and one or more sensors that detect an intensity of contact with the touch-sensitive surface. The method includes: displaying on the display a messaging interface including a conversation record and a message entry area, the message entry area including an affordance for sending a message; detecting a first input by contact at a location on the touch-sensitive surface corresponding to the affordance for sending the message while the message entry area includes message content; determining a characteristic intensity of the contact at the first input; in response to detecting the first input, initiating transmission of the message content to a remote device in accordance with a determination that the first input satisfies a transmission criterion, the transmission criterion not requiring that the characteristic intensity of the contact meet a first intensity threshold for the transmission criterion to be met; and displaying a message when received at the remote device in accordance with a determination that the contact meets a message impact criterion. displaying a plurality of message impact effect options for modifying an animation displayed on the touch-sensitive surface, the message impact criterion requiring that a characteristic intensity of the contact meets a first intensity threshold for the message impact criterion to be met; detecting a second input by the contact while the plurality of message impact effect options are displayed to transmit message content with a message impact effect option selected from the plurality of impact effect options; and in response to detecting the second input, initiating transmission of the message content with the first message impact effect option to the remote device in accordance with a determination that the second input has been received at a location on the touch-sensitive surface corresponding to a first message impact effect option of the plurality of impact effect options.

[0021] According to some embodiments, an electronic device includes a display unit configured to display a user interface, a touch-sensitive surface unit configured to detect contacts, one or more sensor units for detecting intensity of contacts with the touch-sensitive surface unit, and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit enables display of a messaging interface on the display unit, the messaging interface including a conversation record and a message entry area, the message entry area including an affordance for sending a message, detects a first input by contact at a position on the touch-sensitive surface unit corresponding to the affordance for sending the message while the message entry area includes message content, determines a characteristic intensity of the contact at the first input, and initiates transmission of the message content to a remote device in response to detecting the first input, in accordance with a determination that the first input satisfies a transmission criterion, the transmission criterion not requiring that the characteristic intensity of the contact meet a first intensity threshold for the transmission criterion to be met, and the contact is a message impact criterion, the message impact criterion not requiring that the characteristic intensity of the contact meet a first intensity threshold for the message impact criterion to be met. The touch-sensitive surface unit is configured to: enable display of a plurality of message impact effect options for modifying an animation displayed when the message is received at the remote device in accordance with a determination that the message impact criterion is met, the message impact criterion requiring the intensity to meet a first intensity threshold; detect a second input by contact while the display of the plurality of message impact effect options is enabled to transmit the message content with a message impact effect option selected from the plurality of impact effect options; and in response to detecting the second input, initiate transmission of the message content with the first message impact effect option to the remote device in accordance with a determination that the second input has been received at a location on the touch-sensitive surface unit corresponding to a first message impact effect option of the plurality of impact effect options.

[0022] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors that detect an intensity of contact with the touch-sensitive surface. The method includes displaying on the display a user interface including a plurality of actuatable objects, the plurality of actuatable objects including a first actuatable object having a first appearance, and the device performs, for the intensity-sensitive actuatable objects, an action corresponding to the intensity-sensitive actuatable objects based on a characteristic intensity of an input on the touch-sensitive surface corresponding to the intensity-sensitive actuatable objects resulting in an input corresponding to each intensity-sensitive actuatable object on the touch-sensitive surface, where the action corresponding to each intensity-sensitive actuatable object is performed as a result of the characteristic intensity of the contact satisfying the intensity-based actuation criterion, and, for the non-intensity-sensitive actuatable objects, an action corresponding to the non-intensity-sensitive actuatable objects on each intensity-sensitive object regardless of whether the input on the touch-sensitive surface corresponding to the non-intensity-sensitive actuatable objects satisfies the intensity-based actuation criterion. and performing an action corresponding to each non-intensity responsive actuatable object when a characteristic intensity of a contact resulting in an input corresponding to the non-intensity responsive actuatable object satisfies an intensity-based actuation criterion, the action corresponding to each non-intensity responsive actuatable object not being performed as a result of the characteristic intensity of the contact satisfying the intensity-based actuation criterion, the method comprising: detecting, while a user interface is displayed on a display, an input corresponding to a request to select a first actuatable object from among the plurality of actuatable objects, wherein the characteristic intensity of the input does not satisfy the intensity-based actuation criterion during the input; and, in response to detecting the input, displaying the first actuatable object with a first change from a first appearance in accordance with a determination that the first actuatable object is an intensity-responsive actuatable object; and displaying the first actuatable object without displaying the first change in accordance with a determination that the first actuatable object is a non-intensity responsive actuatable object.

[0023] 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 enables display on the display unit of a user interface including a plurality of actuatable objects, the plurality of actuatable objects including a first actuatable object having a first appearance, and the processing unit performs, for the intensity-sensitive actuatable objects, an action corresponding to the intensity-sensitive actuatable objects based on a characteristic intensity of an input on the touch-sensitive surface unit corresponding to the intensity-sensitive actuatable objects, the action resulting in an input corresponding to each intensity-sensitive actuatable object on the touch-sensitive surface unit, where the action corresponding to each intensity-sensitive actuatable object is performed as a result of the characteristic intensity of the contact satisfying the intensity-based actuation criterion, and, for the non-intensity-sensitive actuatable objects, an action corresponding to the non-intensity-sensitive actuatable objects regardless of whether the input on the touch-sensitive surface unit corresponding to the non-intensity-sensitive actuatable objects satisfies the intensity-based actuation criterion. and performing an action corresponding to each non-intensity responsive actuatable object on the touch-sensitive surface unit when a characteristic intensity of the contact satisfies an intensity-based actuation criterion, the characteristic intensity of the contact resulting in an input corresponding to each non-intensity responsive actuatable object; wherein the characteristic intensity of the contact satisfies an intensity-based actuation criterion, and wherein an action corresponding to each non-intensity responsive actuatable object is not performed as a result of the characteristic intensity of the contact satisfying the intensity-based actuation criterion; and is configured to detect, while a user interface is displayed on the display unit, an input corresponding to a request to select a first actuatable object from among the plurality of actuatable objects, the characteristic intensity of the input not satisfying the intensity-based actuation criterion; and, in response to detecting the input, enable display of the first actuatable object with a first change from a first appearance in accordance with a determination that the first actuatable object is an intensity-responsive actuatable object, and enable display of the first actuatable object without displaying the first change in accordance with a determination that the first actuatable object is a non-intensity responsive actuatable object.

[0024] According to some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors that detect an intensity of contact with the touch-sensitive surface, the method including: detecting, while a user interface is displayed, an input by contact at a first location on the touch-sensitive surface corresponding to a first actuatable user interface object on the display; and, in response to detecting the contact input, changing an appearance of the first actuatable user interface object in accordance with a change in the detected intensity of contact on the touch-sensitive surface in accordance with a determination that the first actuatable user interface object is intensity-sensitive; and changing an appearance of the first actuatable user interface object a predetermined amount in accordance with a determination that the first actuatable user interface object is intensity-insensitive.

[0025] 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, wherein the processing unit is configured to: detect input by contact at a first location on the touch-sensitive surface unit corresponding to a first actuatable user interface object on the display unit while the user interface is displayed; and in response to detecting the input by contact, change an appearance of the first actuatable user interface object in accordance with a determination that the first actuatable user interface object is intensity-sensitive in accordance with a change in the detected intensity of contact on the touch-sensitive surface unit; and change an appearance of the first actuatable user interface object a predetermined amount in accordance with a determination that the first actuatable user interface object is intensity-insensitive.

[0026] According to some embodiments, a method is performed in an electronic device that includes a display, a touch-sensitive surface, and one or more sensors that detect an intensity of contact with the touch-sensitive surface. The method includes: displaying a user interface including a plurality of actuatable user interface objects; detecting, while the user interface is displayed, a first portion of an input by contact at a first location on the touch-sensitive surface corresponding to a first user interface object on the display; in response to detecting the first portion of the input, changing an appearance of the first user interface object by applying a first visual change to the first user interface object, the first visual change corresponding to a first user interface action; detecting a second portion of the input after changing the appearance of the first user interface object by applying the first visual change to the first user interface object; in response to detecting the second portion of the input, performing the first user interface action in accordance with a determination that the second portion of the input is consistent with the first user interface action; and in accordance with a determination that the second portion of the input includes an incremental change in a first parameter indicative of performance of the second user interface action, dynamically diminishing the first visual change as the first parameter incrementally changes without performing the first user interface action.

[0027] 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 user interface including a plurality of actuatable user interface objects; detect, while the user interface is displayed, a first portion of input by contact at a first position on the touch-sensitive surface unit corresponding to a first user interface object on the display unit; in response to detecting the first portion of input, apply a first visual change to the first user interface object, the first visual change corresponding to a first user interface action, thereby changing an appearance of the first user interface object; detect a second portion of input after changing the appearance of the first user interface object by applying the first visual change to the first user interface object; in response to detecting the second portion of input, perform the first user interface action in accordance with a determination that the second portion of input is consistent with the first user interface action; and in accordance with a determination that the second portion of input includes an incremental change in a first parameter indicative of performance of the second user interface action, dynamically fade the first visual change as the first parameter incrementally changes without performing the first user interface action.

[0028] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors that detect an intensity of contact with the touch-sensitive surface. The method includes: displaying a user interface including a plurality of actuatable user interface objects; detecting, while the user interface is displayed, a first portion of input by contact at a first location on the touch-sensitive surface corresponding to a first user interface object on the display; and, in response to detecting the first portion of the input by contact, changing an appearance of the first user interface object to indicate that an action corresponding to the first user interface object will be performed in response to detecting lift-off of the contact from the touch-sensitive surface, the change in appearance including applying the first change to the first user interface object; and detecting a second portion of the input by contact, the second portion of the input being a lift-off of the input. immediately following the first portion; and in response to detecting a second portion of the tactile input, in accordance with a determination that the second portion of the input includes an incremental change in the first input parameter and corresponds to the first gesture, changing an appearance of the first user interface object by dynamically attenuating the first change as the first input parameter incrementally changes and applying a second change corresponding to the first gesture; and in accordance with a determination that the second portion of the input includes an incremental change in the second input parameter and corresponds to the second gesture, changing an appearance of the first user interface object by dynamically attenuating the first change as the second input parameter incrementally changes and applying a third change corresponding to the second gesture.

[0029] 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 enabling display of a user interface including a plurality of actuatable user interface objects; detecting, while the user interface is displayed, a first portion of input by contact at a first location on the touch-sensitive surface unit corresponding to a first user interface object on the display unit; and, in response to detecting lift-off of the contact from the touch-sensitive surface unit, changing the appearance of the first user interface object to indicate that an action corresponding to the first user interface object will be performed. detecting a second portion of the tactile input, the second portion of the input immediately following the first portion of the input; and in response to detecting the second portion of the tactile input, in accordance with a determination that the second portion of the input includes an incremental change in the first input parameter and corresponds to the first gesture, changing the appearance of the first user interface object by dynamically attenuating the first change as the first input parameter incrementally changes and applying a second change corresponding to the first gesture; and in accordance with a determination that the second portion of the input includes an incremental change in the second input parameter and corresponds to the second gesture, changing the appearance of the first user interface object by dynamically attenuating the first change as the second input parameter incrementally changes and applying a third change corresponding to the second gesture.

[0030] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more sensors that detect an intensity of contact with the touch-sensitive surface. The method includes: displaying a first user interface including a plurality of actuatable user interface objects; detecting, while the first user interface is displayed, an input by contact at a first location on the touch-sensitive surface corresponding to a first actuatable user interface object on the display, the first actuatable user interface object being associated with a control function having three or more available values, a first value of the control function being selected as a current value for the control function; and, in response to detecting the input by contact, toggling the control function corresponding to the first actuatable user interface object between a first state based on the current value for the control function and a second state in accordance with a determination that the input satisfies a toggle criterion, the toggle criterion being satisfied. , not requiring a characteristic intensity of the contact on the touch-sensitive surface to satisfy a first intensity threshold; displaying a second user interface in accordance with a determination that the input satisfies a control adjustment criterion, the control adjustment criterion requiring a characteristic intensity of the contact on the touch-sensitive surface to satisfy the first intensity threshold for the control adjustment criterion to be satisfied, the second user interface including a second actuatable user interface object having three or more state options corresponding to three or more available values ​​for the control function; detecting movement of the contact across the touch-sensitive surface while the second user interface is displayed and detection of the contact continues; ceasing to detect the contact; and in response to detecting movement of the contact across the touch-sensitive surface, changing a current value for the control function based on the movement of the contact.

[0031] 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 enables display of a first user interface including a plurality of actuatable user interface objects; and while the first user interface is displayed, detects an input by contact at a first position on the touch-sensitive surface unit corresponding to the first actuatable user interface object on the display unit, the first actuatable user interface object being associated with a control function having three or more available values, a first value of the control function being selected as a current value for the control function; and, in response to detecting the input by contact, toggles the control function corresponding to the first actuatable user interface object between a first state based on the current value for the control function and a second state in accordance with a determination that the input satisfies a toggle criterion, the toggle criterion being selected when the touch-sensitive surface unit is in a non-operational state such that the toggle criterion is satisfied. the characteristic intensity of the contact on the touch-sensitive surface unit does not need to satisfy a first intensity threshold; and in accordance with a determination that the input satisfies a control adjustment criterion, the control adjustment criterion requiring the characteristic intensity of the contact on the touch-sensitive surface unit to satisfy the first intensity threshold, the second user interface including a second actuatable user interface object having three or more state options corresponding to three or more available values ​​for the control function; and while the second user interface is displayed and detection of the contact continues, detect movement of the contact across the touch-sensitive surface unit, cease detecting the contact; and in response to detecting movement of the contact across the touch-sensitive surface unit, change the current value for the control function based on the movement of the contact.

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

[0033] Thus, electronic devices that include 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 providing access to application content and functionality without first launching the application, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for accessing application content and functionality. [Brief explanation of the drawings]

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

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

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

[0037] [Figure 2] FIG. 1 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.

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

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

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

[0041] [Figure 4C] FIG. 10 illustrates an example of a dynamic intensity threshold, according to some embodiments. [Figure 4D] FIG. 10 illustrates an example of a dynamic intensity threshold, according to some embodiments. [Figure 4E] FIG. 10 illustrates an example of a dynamic intensity threshold, according to some embodiments.

[0042] [Figure 5A1] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5A2] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5A3] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5A4]FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5A5] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5A6] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5B1] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5B2] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5B3] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5B4] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5C1] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5C2] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5C3] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5C4] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5C5]FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5C6] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5D1] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5D2] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5D3] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5D4] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5D5] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5D6] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5D7] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5D8] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5E1] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5E2]FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5E3] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5E4] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5F1] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5F2] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5F3] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5F4] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5F5] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5F6] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5F7] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5G1] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5G2]FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5G3] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5H1] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5H2] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5I1] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5I2] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5I3] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5I4] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5I5] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5I6] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5I7] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5I8]FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments. [Figure 5I9] FIG. 1 illustrates an exemplary user interface for interacting with a notification associated with a corresponding application (e.g., to access a subset of the functionality and / or content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments.

[0043] [Figure 5J1] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5J2] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5K1] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5K2]FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5K3] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5K4] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5K5] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5K6] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5K7] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5K8] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5K9] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5K10] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5L1]FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5L2] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5L3] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5L4] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5L5] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5L6] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5L7] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5L8] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5L9] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5L10]FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5M1] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5M2] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5N1] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5N2] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5N3] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5N4] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5N5] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5N6] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5O1]FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5O2] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5P1] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments. [Figure 5P2] FIG. 1 illustrates an exemplary user interface for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content without first launching the corresponding application), in accordance with some embodiments.

[0044] [Figure 5Q1]FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q2] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q3] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q4] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q5] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q6]FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q7] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q8] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q9] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q10] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q11]FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q12] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q13] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q14] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q15] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q16]FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5Q17] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5R1] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5R2] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5R3] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5R4]FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5R5] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5R6] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5R7] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5S1] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5S2]FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5S3] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5S4] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments. [Figure 5S5] FIG. 1 illustrates a user interface for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for applications in the process of downloading), according to some embodiments.

[0045] [Figure 5T1] FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments. [Figure 5T2]FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments. [Figure 5T3] FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments. [Figure 5T4] FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments. [Figure 5T5] FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments. [Figure 5T6] FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments. [Figure 5T7]FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments. [Figure 5T8] FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments. [Figure 5T9] FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments. [Figure 5T10] FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments. [Figure 5T11] FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments. [Figure 5T12]FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments. [Figure 5T13] FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments. [Figure 5T14] FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments. [Figure 5T15] FIG. 1 illustrates a user interface for interacting with a menu of applications containing a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments.

[0046] [Figure 5U1] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5U2] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5U3]10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5U4] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5U5] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5U6] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5U7] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5V1] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5V2] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5V3] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5V4]10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5V5] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5V6] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5V7] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5V8] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5V9] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5V10] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5V11] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5V12]10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5V13] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5V14] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5W1] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5W2] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5W3] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5W4] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments. [Figure 5W5] 10A-10C illustrate user interfaces for quickly entering a rename and re-icon mode for an application folder (e.g., without first opening the folder) according to some embodiments.

[0047] [Figure 6A]10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6B] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6C] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6D] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6E] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6F] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6G] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6H] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6I] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6J] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6K] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6L]10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6M] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6N] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6O] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6P] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6Q] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6R] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6S] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6T] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6U] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6V] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6W]10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6X] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments. [Figure 6Y] 10A-10C illustrate exemplary user interfaces for changing the functionality of control affordances in accordance with some embodiments.

[0048] [Figure 7A] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7B] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7C] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7D] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7E] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7F] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7G] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7H] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7I] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7J]FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7K] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7L] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7M] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7N] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7O-1] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7O-2] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7P] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7Q] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7R] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7S] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7T] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7U] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7V]FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments. [Figure 7W] FIG. 10 illustrates an exemplary user interface for deleting content, according to some embodiments.

[0049] [Figure 8A] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8B] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8C] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8D] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8E] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8F] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8G] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8H] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8I] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8J] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8K] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8L] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8M] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8N] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8O] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8P] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8Q] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8R] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8S] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8T]1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8U] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8V] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8W] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8X] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8Y] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8Z] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8AA] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8AB] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8AC] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8AD] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8AE] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8AF] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8AG] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8AH] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments. [Figure 8AI] 1 illustrates an exemplary user interface for detecting input in a messaging interface in accordance with some embodiments.

[0050] [Figure 9A1] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A2] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A3] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A4] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A5] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A6] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A7] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A8] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A9] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A10] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A11] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A12] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A13] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A14] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A15] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A16] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A17] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A18] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A19] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A20] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A21] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A22] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A23] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A24] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9A25]FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments.

[0051] [Figure 9B1] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9B2] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9B3] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9B4] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9B5] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9B6] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9B7] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9B8] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9B9]FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 9B10] FIG. 1 illustrates an exemplary user interface for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments.

[0052] [Figure 9C1] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C2] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C3] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C4] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C5] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C6] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C7] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C8] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C9] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C10] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C11] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C12] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C13] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C14] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C15] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C16] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C17]10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C18] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments. [Figure 9C19] 10A-10C illustrate exemplary user interfaces for displaying a control settings interface for control functions for a remote device, according to some embodiments.

[0053] [Figure 10A] FIG. 1 is a flow diagram illustrating a method for interacting with a notification associated with a corresponding application (e.g., launching an application associated with the notification from the notification or displaying an expanded version of the notification based on detected user input), according to some embodiments. [Figure 10B] FIG. 1 is a flow diagram illustrating a method for interacting with a notification associated with a corresponding application (e.g., launching an application associated with the notification from the notification or displaying an expanded version of the notification based on detected user input), according to some embodiments. [Figure 10C] FIG. 1 is a flow diagram illustrating a method for interacting with a notification associated with a corresponding application (e.g., launching an application associated with the notification from the notification or displaying an expanded version of the notification based on detected user input), according to some embodiments. [Figure 10D] FIG. 1 is a flow diagram illustrating a method for interacting with a notification associated with a corresponding application (e.g., launching an application associated with the notification from the notification or displaying an expanded version of the notification based on detected user input), according to some embodiments.

[0054] [Figure 11]FIG. 1 is a functional block diagram of an electronic device for interacting with a notification associated with a corresponding application (e.g., launching an application associated with the notification from the notification or displaying an expanded version of the notification based on user input), according to some embodiments.

[0055] [Figure 12A] FIG. 1 is a flow diagram illustrating a method for interacting with an application launch icon (e.g., launching an application or displaying a contextual content object associated with an application based on detected user input) according to some embodiments. [Figure 12B] FIG. 1 is a flow diagram illustrating a method for interacting with an application launch icon (e.g., launching an application or displaying a contextual content object associated with an application based on detected user input) according to some embodiments. [Figure 12C] FIG. 1 is a flow diagram illustrating a method for interacting with an application launch icon (e.g., launching an application or displaying a contextual content object associated with an application based on detected user input) according to some embodiments. [Figure 12D] FIG. 1 is a flow diagram illustrating a method for interacting with an application launch icon (e.g., launching an application or displaying a contextual content object associated with an application based on detected user input) according to some embodiments. [Figure 12E] FIG. 1 is a flow diagram illustrating a method for interacting with an application launch icon (e.g., launching an application or displaying a contextual content object associated with an application based on detected user input) according to some embodiments. [Figure 12F]FIG. 1 is a flow diagram illustrating a method for interacting with an application launch icon (e.g., launching an application or displaying a contextual content object associated with an application based on detected user input) according to some embodiments.

[0056] [Figure 13] FIG. 1 is a functional block diagram of an electronic device for interacting with an application launch icon (e.g., launching an application or displaying a contextual content object associated with an application based on detected user input) in accordance with some embodiments.

[0057] [Figure 14A] FIG. 1 is a flow diagram illustrating a method for interacting with a menu of applications, including applications in the process of downloading (e.g., presenting menu options for downloading applications based on detected user input), according to some embodiments. [Figure 14B] FIG. 1 is a flow diagram illustrating a method for interacting with a menu of applications, including applications in the process of downloading (e.g., presenting menu options for downloading applications based on detected user input), according to some embodiments. [Figure 14C] FIG. 1 is a flow diagram illustrating a method for interacting with a menu of applications, including applications in the process of downloading (e.g., presenting menu options for downloading applications based on detected user input), according to some embodiments.

[0058] [Figure 15] FIG. 1 is a functional block diagram of an electronic device for interacting with a menu of applications, including applications in the process of downloading (e.g., presenting menu options for downloading applications based on detected user input), in accordance with some embodiments.

[0059] [Figure 16A] FIG. 1 is a flow diagram illustrating a method for interacting with a menu of applications that includes a folder of applications (e.g., selectively presenting application launch options for corresponding applications in the folder (e.g., applications with unread notifications) based on detected user input), according to some embodiments. [Figure 16B] FIG. 1 is a flow diagram illustrating a method for interacting with a menu of applications that includes a folder of applications (e.g., selectively presenting application launch options for corresponding applications in the folder (e.g., applications with unread notifications) based on detected user input), according to some embodiments. [Figure 16C] FIG. 1 is a flow diagram illustrating a method for interacting with a menu of applications that includes a folder of applications (e.g., selectively presenting application launch options for corresponding applications in the folder (e.g., applications with unread notifications) based on detected user input), according to some embodiments.

[0060] [Figure 17] FIG. 1 is a functional block diagram of an electronic device for interacting with a menu of applications including a folder of applications (e.g., selectively presenting application launch options for corresponding applications in the folder (e.g., applications with unread notifications) based on user input), in accordance with some embodiments.

[0061] [Figure 18A] FIG. 10 is a flow diagram illustrating a method for changing the functionality of a control affordance, according to some embodiments. [Figure 18B] FIG. 10 is a flow diagram illustrating a method for changing the functionality of a control affordance, according to some embodiments. [Figure 18C]FIG. 10 is a flow diagram illustrating a method for changing the functionality of a control affordance, according to some embodiments. [Figure 18D] FIG. 10 is a flow diagram illustrating a method for changing the functionality of a control affordance, according to some embodiments.

[0062] [Figure 19] FIG. 1 is a functional block diagram of an electronic device for changing the functionality of a control affordance, according to some embodiments.

[0063] [Figure 20A] FIG. 1 is a flow diagram illustrating a method for deleting content, according to some embodiments. [Figure 20B] FIG. 1 is a flow diagram illustrating a method for deleting content, according to some embodiments. [Figure 20C] FIG. 1 is a flow diagram illustrating a method for deleting content, according to some embodiments. [Figure 20D1] FIG. 1 is a flow diagram illustrating a method for deleting content, according to some embodiments. [Figure 20D2] FIG. 1 is a flow diagram illustrating a method for deleting content, according to some embodiments. [Figure 20E] FIG. 1 is a flow diagram illustrating a method for deleting content, according to some embodiments. [Figure 20F] FIG. 1 is a flow diagram illustrating a method for deleting content, according to some embodiments. [Figure 20G] FIG. 1 is a flow diagram illustrating a method for deleting content, according to some embodiments.

[0064] [Figure 21] FIG. 1 is a functional block diagram of an electronic device according to some embodiments.

[0065] [Figure 22A] FIG. 1 is a flow diagram illustrating a method for detecting input in a messaging interface according to some embodiments. [Figure 22B] FIG. 1 is a flow diagram illustrating a method for detecting input in a messaging interface according to some embodiments. [Figure 22C] FIG. 1 is a flow diagram illustrating a method for detecting input in a messaging interface according to some embodiments. [Figure 22D] FIG. 1 is a flow diagram illustrating a method for detecting input in a messaging interface according to some embodiments. [Figure 22E] FIG. 1 is a flow diagram illustrating a method for detecting input in a messaging interface according to some embodiments. [Figure 22F] FIG. 1 is a flow diagram illustrating a method for detecting input in a messaging interface according to some embodiments. [Figure 22G] FIG. 1 is a flow diagram illustrating a method for detecting input in a messaging interface according to some embodiments.

[0066] [Figure 23] FIG. 1 is a functional block diagram of an electronic device according to some embodiments.

[0067] [Figure 24A1] FIG. 1 is a flow diagram illustrating a method for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 24A2] FIG. 1 is a flow diagram illustrating a method for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 24A3] FIG. 1 is a flow diagram illustrating a method for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments.

[0068] [Figure 24B1] FIG. 1 is a flow diagram illustrating a method for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 24B2] FIG. 1 is a flow diagram illustrating a method for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 24B3] FIG. 1 is a flow diagram illustrating a method for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments.

[0069] [Figure 25] FIG. 1 is a functional block diagram of an electronic device according to some embodiments.

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

[0071] [Figure 27A1] FIG. 1 is a flow diagram illustrating a method for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 27A2] FIG. 1 is a flow diagram illustrating a method for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 27A3] FIG. 1 is a flow diagram illustrating a method for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 27A4] FIG. 1 is a flow diagram illustrating a method for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 27A5] FIG. 1 is a flow diagram illustrating a method for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments.

[0072] [Figure 27B1] FIG. 1 is a flow diagram illustrating a method for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 27B2]FIG. 1 is a flow diagram illustrating a method for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments. [Figure 27B3] FIG. 1 is a flow diagram illustrating a method for displaying intensity-sensitive and non-intensity-sensitive user interface objects according to some embodiments.

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

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

[0075] [Figure 30A] FIG. 10 is a flow diagram illustrating a method for displaying a control settings interface for a control function for a remote device, according to some embodiments. [Figure 30B] FIG. 10 is a flow diagram illustrating a method for displaying a control settings interface for a control function for a remote device, according to some embodiments. [Figure 30C] FIG. 10 is a flow diagram illustrating a method for displaying a control settings interface for a control function for a remote device, according to some embodiments. [Figure 30D] FIG. 10 is a flow diagram illustrating a method for displaying a control settings interface for a control function for a remote device, according to some embodiments. [Figure 30E] FIG. 10 is a flow diagram illustrating a method for displaying a control settings interface for a control function for a remote device, according to some embodiments.

[0076] [Figure 31] FIG. 1 is a functional block diagram of an electronic device according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

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

[0078] In some embodiments, in systems where the trackpad or touchscreen display is sensitive to 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) that indicates the intensity of the contact within that range. This provides the user with a continuous response to the force or pressure of their contact, thereby providing the user with richer and more intuitive visual and / or tactile feedback. For example, such continuous force response gives the user the experience of being able to preview an action with a light press and / or to enter a predetermined user interface state corresponding to that action with a deeper press.

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

[0080] In some embodiments, for devices with touch-sensitive surfaces that are sensitive to a range of contact intensities, the devices provide additional functionality by allowing users to perform complex actions with a single, continuous contact.

[0081] In some embodiments, for devices with touch-sensitive surfaces that are sensitive to a range of contact intensities, the devices provide 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 pressure 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 on an application icon on the home screen to launch the corresponding application) without accidentally activating the additional functionality. It is also easy for a user to discover, understand, and use the intensity-based input and its added functionality (e.g., by pressing a notification, contextual content object, mini-application object, folder icon, downloading icon, and / or application icon in a background user interface (e.g., a notification center user interface, a home screen, a widget view, etc.), a user can access a subset of content, functionality, and menu options from the corresponding application without first launching the corresponding application and without leaving the current context (e.g., another application and / or the background user interface).

[0082] A number of different techniques for operating a user interface are described herein. Using one or more of these techniques (optionally in combination) helps provide a user interface that intuitively provides additional information and functionality to the user. Using one or more of these techniques (optionally in combination) reduces the number, range, and / or type of inputs from the user, providing a more efficient human-machine interface. This allows users to use devices with touch-sensitive surfaces faster and more efficiently. For battery-operated devices, these improvements conserve power and increase the time between battery charges.

[0083] Figures 1A, 1B, 2, and 3 below provide an example device description. Figures 4A and 4B provide an example user interface description for portable multifunction device 100, according to some embodiments. Figures 4C-4E show examples of dynamic intensity thresholds, according to some embodiments.

[0084] 5A1-5I9 illustrate exemplary user interfaces for interacting with notifications associated with corresponding applications (e.g., for accessing a subset of the functionality and content of the corresponding application from the notification without first activating the corresponding application), according to some embodiments.

[0085] 5J1-5P2 show exemplary user interfaces for displaying contextual content objects (e.g., mini-application objects) associated with corresponding applications (e.g., for accessing a subset of the functionality and content of the corresponding applications from the contextual content objects without first launching the corresponding applications) in accordance with some embodiments.

[0086] 5Q1-5S5 illustrate user interfaces for interacting with a menu of applications, including applications in the process of downloading (e.g., providing a menu of options for quickly invoking one of several download-related quick actions for an application in the process of downloading), according to some embodiments.

[0087] 5T1-5T15 illustrate user interfaces for interacting with a menu of applications including a folder of applications (e.g., selectively providing a menu for quickly launching a corresponding application that has unread notifications from a folder containing multiple applications without first opening the folder), according to some embodiments.

[0088] 5U1-5W5 show user interfaces for quickly entering a rename and reconfigure mode for an application folder (eg, without first opening the folder) according to some embodiments.

[0089] 10A-10D are flow diagrams illustrating a method of interacting with a notification associated with a corresponding application (e.g., to launch the corresponding application or to access enhanced notification content), according to some embodiments. FIGS. 12A-12F are flow diagrams illustrating a method of interacting with an application launch icon associated with a corresponding application (e.g., to launch the corresponding application or to present contextual content associated with the corresponding application (e.g., in a contextual content object) without first launching the corresponding application), according to some embodiments. FIGS. 14A-14C are flow diagrams illustrating a method of interacting with a menu of an application (e.g., presenting selectable options for actions on the corresponding application (e.g., when the corresponding application is in the process of downloading and / or after the download is complete)), according to some embodiments. FIGS. 16A-16C are flow diagrams illustrating a method of interacting with a menu of an application including a folder of applications (e.g., presenting selectable options for selectively launching applications (e.g., applications with unread notifications) from a folder containing one or more applications), according to some embodiments. The user interfaces of FIGS. 5A1-5W5 are used to illustrate the processes of FIGS. 10A-10D, 12A-12F, 14A-14C, and 16A-16C.

[0090] Figures 6A-6Y below show exemplary user interfaces for changing the functionality of a control affordance. Figures 18A-18D are flow diagrams illustrating a method for changing the functionality of a control affordance. The user interfaces of Figures 6A-6Y are used to illustrate the processes of Figures 18A-18D.

[0091] Figures 7A-7W below show exemplary user interfaces for deleting content. Figures 20A-20G are flow diagrams illustrating a method for deleting content. The user interfaces of Figures 7A-7W are used to illustrate the processes of Figures 20A-20G.

[0092] Figures 8A-8AI below show exemplary user interfaces for detecting input in a messaging interface. Figures 22A-22G are flow diagrams illustrating methods for detecting input in a messaging interface. The user interfaces of Figures 8A-8AI are used to illustrate the processes of Figures 22A-22G.

[0093] 9A1-9A25 below illustrate exemplary user interfaces for displaying intensity-sensitive and non-intensity-sensitive user interface objects, according to some embodiments. FIGS. 24A1-24A3 are flow diagrams illustrating methods for displaying intensity-sensitive and non-intensity-sensitive user interface objects, according to some embodiments. FIGS. 24B1-24B3 are flow diagrams illustrating methods for displaying intensity-sensitive and non-intensity-sensitive user interface objects, according to some embodiments. The user interfaces of FIGS. 9A1-9A25 are used to illustrate the processes of FIGS. 24A1-24A3 and 24B1-24B3.

[0094] Figures 9B1-9B10 below show exemplary user interfaces for displaying intensity-sensitive and non-intensity-sensitive user interface objects, according to some embodiments. Figures 27A1-27A5 are flow diagrams illustrating methods for displaying intensity-sensitive and non-intensity-sensitive user interface objects, according to some embodiments. Figures 27B1-27B3 are flow diagrams illustrating methods for displaying intensity-sensitive and non-intensity-sensitive user interface objects, according to some embodiments. The user interfaces of Figures 9B1-9B10 are used to illustrate the processes of Figures 27A1-27A5 and 27B1-27B3.

[0095] 9C1-9C19 show exemplary user interfaces for displaying a control settings interface for a control function for a remote device, according to some embodiments. Figures 30A-30E are flow diagrams illustrating a method for displaying a control settings interface for a control function for a remote device, according to some embodiments. The user interfaces of Figures 9C1-9C19 are used to illustrate the processes of Figures 30A-30E. Exemplary Devices

[0096] 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 as not to unnecessarily obscure aspects of the embodiments.

[0097] In this specification, terms such as "first," "second," etc. are used to describe various elements in some examples, 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 being described. Although a first contact and a second contact are both contacts, they are not the same contact unless the context clearly dictates otherwise.

[0098] The terminology used in the description of the various embodiments set forth 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 embodiments set forth and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. As used herein, it should also be understood that the term "and / or" refers to and includes any and all possible combinations of one or more of the associated listed items. It should be further understood that the terms "includes," "including," "comprises," and / or "comprising," when used herein, specify the presence of 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.

[0099] 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.

[0100] 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 and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices by Apple Inc. (Cupertino, California). Other portable electronic devices, such as laptop or tablet computers with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads), 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 with a touch-sensitive surface (e.g., touchscreen displays and / or touchpads).

[0101] In the following discussion, we describe an electronic device that includes a display and a touch-sensitive surface, however, 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.

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

[0103] 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 corresponding information displayed on the device are optionally adjusted and / or changed for each application and / or within the corresponding application. In this way, the common physical architecture (such as the touch-sensitive surface) of the device optionally supports various applications with user interfaces that are intuitive and transparent to the user.

[0104] Attention is now directed to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display system 112, according to some embodiments. Touch-sensitive display system 112 may conveniently be 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 optical 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 at device 100 (e.g., generating tactile output at 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.

[0105] As used herein and in the claims, the term “tactile output” refers to a physical displacement of a device relative to its previous position, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that is 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., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement is interpreted by the user as a tactile sensation corresponding 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 “downclick” or “upclick” of a physical actuator button. In some cases, a user will feel a tactile sensation such as a “downclick” or “upclick” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that has been physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. While such user interpretation of touch depends on the user's personal sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device or a component of the device that would produce the described sensory perception for a typical (or average) user.

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

[0107] 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 solid-state 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.

[0108] 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 operate or execute various software programs and / or instruction sets stored in memory 102 to perform various functions for device 100 and to process data.

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

[0110] RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. 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. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. RF circuitry 108 optionally communicates via wireless communication with networks such as the Internet (also known as the World Wide Web (WWW)), intranets and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)), and other devices. The wireless communication optionally uses any of a plurality 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-HSPA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), and the like.Standards include, but are not limited to, code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth®, Wireless Fidelity (Wi-Fi)® (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP)), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), instant messaging and presence services (e.g., Instant Messaging and Presence Leveraging Extensions (SIMPLE)), and protocols for mobile devices (e.g., cellular phones). Messaging and Presence Service (IMPS), and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

[0111] Audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuit 110 receives audio data from peripherals interface 118, converts the audio data into electrical signals, and transmits the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves audible to humans. Audio circuit 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuit 110 converts the electrical signals into audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is optionally retrieved from and / or transmitted to memory 102 and / or RF circuit 108 by peripherals interface 118. In some embodiments, audio circuit 110 also includes 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, such as an output-only headphone or a headset with both an output (e.g., single or double ear headphones) and an input (e.g., a microphone).

[0112] I / O subsystem 106 couples input / output peripherals on device 100, such as touch-sensitive display system 112 and other input or control devices 116, to 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 and send electrical signals from and 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, infrared port, USB port, stylus, and / or pointer device such as a mouse. The one or more buttons (e.g., 208 in FIG. 2) optionally include 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).

[0113] Touch-sensitive display system 112 provides an input and output interface between the device and a user. Display controller 156 receives and / or sends electrical signals 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 user interface objects. As used herein, the term "affordance" refers to a user-interactive graphical user interface object (e.g., a graphical user interface object configured to respond to input thereto). Examples of user-interactive graphical user interface objects include, but are not limited to, a button, a slider, an icon, a selection menu item, a switch, a hyperlink, or other user interface control.

[0114] Touch-sensitive display system 112 has a touch-sensitive surface, sensor, or set of sensors that receive input from a user based on haptic and / or tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and / or instruction sets in memory 102) detect contacts (and any movement or breaking of contact) on touch-sensitive display system 112 and translate the detected contacts into dialog 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 an exemplary embodiment, the point of contact between touch-sensitive display system 112 and the user corresponds to the user's finger or stylus.

[0115] Touch-sensitive display system 112 optionally uses liquid crystal display (LCD), light emitting polymer display (LPD), or light emitting diode (LED) technology, although other display technologies are used in other embodiments. Touch-sensitive display system 112 and display controller 156 optionally detect contact and any movement or disruption 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 acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch-sensitive display system 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® by Apple Inc. (Cupertino, California).

[0116] Touch-sensitive display system 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen video resolution exceeds 400 dpi (e.g., 500 dpi, 800 dpi, or higher). A user optionally contacts touch-sensitive display system 112 using any suitable object or accessory, 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 coarse finger-based input into precise pointer / cursor position or commands to perform the user's desired action.

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

[0118] 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 generating, managing, and distributing electrical power within a portable device.

[0119] 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 charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. 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, the 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 touchscreen is enabled for use as a viewfinder for still and / or video image acquisition. In some embodiments, another light sensor is placed on the front of the device to capture an image of the user (e.g., for taking a selfie, for video conferencing while the user sees other video conferencing participants on the touchscreen, etc.).

[0120] 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, electric 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 located on or proximate to the 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, which is located on the front of device 100.

[0121] Device 100 also optionally includes one or more proximity sensors 166. FIG. 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, the proximity sensor turns off and disables touch-sensitive display system 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

[0122] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows tactile output generators 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 acoustic components, and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals on the device into tactile output). Tactile output generator(s) 167 receive tactile feedback generation instructions from haptic feedback module 133 and generate tactile outputs on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is disposed on or proximate 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 disposed on the back of device 100, opposite touch-sensitive display system 112, which is disposed on the front of device 100.

[0123] 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. In addition to accelerometer(s) 168, 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.

[0124] 1A and 3 , memory 102 stores device / global internal state 157. Device / global internal state 157 includes one or more of the following: active application state, which indicates which applications, if any, are currently active; display state, which indicates which applications, views, or other information occupy various regions of touch-sensitive display system 112; sensor state, which includes information obtained from the device's various sensors and other input or control devices 116; and position and / or orientation information regarding the device's position and / or orientation.

[0125] 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.

[0126] Communications module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by RF circuitry 108 and / or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE®, etc.) is adapted to connect to other devices directly or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector identical to, similar to, and / or compatible with the 30-pin connector used in some of the iPhone®, iPod Touch®, and iPad® devices by Apple Inc. (Cupertino, California). In some embodiments, the external port is a Lightning connector identical to, similar to, and / or compatible with the Lightning connector used in some iPhone®, iPod Touch®, and iPad® devices by Apple Inc. (Cupertino, California).

[0127] Contact / motion module 130 optionally detects contact with touch-sensitive display system 112 (in cooperation with display controller 156) and 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 detecting contact (e.g., by a finger or stylus), such as determining whether contact has occurred (e.g., detecting a finger down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a proxy for the force or pressure of the contact), determining whether there is contact movement and tracking of the movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has ended (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 are optionally applied to a single touch (e.g., a single finger touch or a stylus touch) or to multiple simultaneous touches (e.g., "multi-touch" / multiple finger touches). In some embodiments, contact / motion module 130 and display controller 156 detect contacts on the touchpad.

[0128] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or strength of the detected contact). Thus, gestures are optionally detected by detecting particular contact patterns. For example, detecting a finger tap gesture involves detecting a finger down event, followed by detecting 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 the touch-sensitive surface involves detecting a finger down event, followed by detecting one or more finger drag events, followed by detecting a finger up (lift-off) event. Similarly, taps, swipes, drags, and other gestures are optionally detected with respect to a stylus by detecting particular contact patterns for the stylus.

[0129] In some embodiments, detecting a finger tap gesture depends on the length of time between detecting a finger down event and detecting a finger up event, but is independent of the strength between the finger contact that detects the finger down event and the finger contact that detects the finger up event. In some embodiments, a tap gesture is detected according to determining that the length of time between the finger down event and the finger up event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4, or 0.5 seconds), independent of whether the strength of the finger contact during the tap meets a predetermined intensity threshold (higher than a nominal contact detection intensity threshold), such as a light or deep pressure intensity threshold. In this manner, a finger tap gesture may satisfy input criteria that are configured to be met even if the characteristic intensity of the contact does not meet the predetermined intensity threshold. For clarity, finger contact in a tap gesture typically needs to meet the nominal contact detection intensity threshold for a finger down event to be detected. Below this threshold, the contact is not detected. A similar analysis applies to detecting tap gestures with a stylus or other contact. If the device is configured to detect contact of a finger or stylus hovering over the touch-sensitive surface, the standard contact-detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch-sensitive surface.

[0130] The same concept applies in an analogous manner to other types of gestures. For example, swipe gestures, pinch gestures, de-pinch gestures, and / or press and hold gestures are optionally detected based on the fulfillment of criteria independent of the contact intensity included in the gesture. For example, swipe gestures are detected based on the amount of movement of one or more contacts, pinch gestures are detected based on the movement of two or more contacts toward each other, de-pinch gestures are detected based on the movement of two or more contacts away from each other, and press and hold gestures are detected based on the duration of the contacts on the touch-sensitive surface less than a threshold amount of movement. Thus, a statement that a gesture recognition criterion is configured to be fulfilled if the contacts in the gesture have an intensity below a corresponding intensity threshold means that the gesture recognition threshold may be fulfilled even if the contact(s) in the gesture do not reach the corresponding intensity threshold. However, it should be understood that this description does not exclude the gesture recognition threshold being met in situations where one or more of the contacts in the gesture meet or exceed a corresponding intensity threshold. For example, a tap gesture is configured to be detected when finger down and finger up events are detected within a predetermined period of time, regardless of whether the contacts exceed or fall below the corresponding intensity threshold during the predetermined period, and a swipe gesture is configured to be detected when the contact movement exceeds a predetermined magnitude, even if the contact exceeds the corresponding intensity threshold at the end of the contact movement.

[0131] The contact intensity threshold, duration threshold, and movement threshold may, in some circumstances, be combined in various different combinations to create heuristics for distinguishing between two or more different gestures directed at the same input element or region, thereby enabling multiple different interaction with the same input element to provide a more robust set of user interactions and responses. A statement that a particular set of gesture recognition criteria is configured to be satisfied when contacts in the gesture have an intensity below a corresponding intensity threshold does not preclude simultaneous evaluation of other intensity-dependent gesture recognition criteria, and may identify other gestures that do not have criteria that are satisfied when the gesture includes contacts with an intensity above a corresponding intensity threshold. For example, in some circumstances, a first gesture recognition criterion for a first gesture (configured to be satisfied when the gesture has an intensity below a corresponding intensity threshold) conflicts with a second gesture recognition criterion for a second gesture (which is dependent on the gesture reaching a corresponding intensity threshold). In such a conflict, a gesture is optionally not recognized as satisfying the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are satisfied first. For example, if the contact reaches the corresponding intensity threshold before moving a predetermined amount, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves a predetermined amount before reaching the corresponding intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such a situation, the first gesture recognition criteria for the first gesture are still configured to be satisfied even if the contact during the gesture has an intensity below the corresponding intensity, because if the contact remains below the corresponding intensity threshold until the end of the gesture (e.g., a swipe gesture with the contact not increasing in intensity above the corresponding intensity threshold), the gesture would be recognized as a swipe gesture according to the first gesture recognition criteria.Thus, certain gesture recognition criteria that are configured to be satisfied when the intensity of the contact remains below a corresponding intensity threshold are dependent on the intensity of the contact relative to the intensity threshold in the sense that (A) in some circumstances, the intensity of the contact relative to the intensity threshold (e.g., for a tap gesture) is ignored, and / or (B) in some circumstances, the certain gesture recognition criteria (e.g., for a deep press gesture) will not be satisfied if a competing set of intensity-dependent gesture recognition criteria (e.g., for a long press gesture) recognizes an input as corresponding to an intensity-dependent gesture before the certain gesture recognition criteria recognizes a gesture corresponding to the input (e.g., for a long press gesture that competes for recognition with a deep press gesture).

[0132] 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 modifying 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, video, animation, etc.

[0133] 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, from an application or the like, one or more codes specifying the graphics to be displayed, along with coordinate data and other graphic characteristic data, as necessary, and then generates screen image data and outputs it to display controller 156.

[0134] 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.

[0135] 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).

[0136] 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 photo / video metadata, and to applications that provide location-based services such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0137] The 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, ●Videoconferencing 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 stocks 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 creator module 150 for creating user-created widgets 149-6; ● Search module 151, • a video and music player module 152, optionally consisting of a video player module and a music player module; ● Memo module 153, Map module 154, and / or ●Online video module 155.

[0138] 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.

[0139] In cooperation 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 application internal state 192 of contact module 137 in memory 370) for managing an address book or contact list, including adding name(s) to the address book, deleting name(s) from the address book, associating phone number(s), email address(es), postal address(es), or other information with names, associating images with names, 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, etc.

[0140] In cooperation with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions for entering a 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 noted above, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0141] 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, videoconferencing module 139 includes executable instructions for initiating, conducting, and terminating a videoconference between a user and one or more other participants in accordance with the user's instructions.

[0142] In cooperation with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, email client module 140 contains executable instructions for composing, sending, receiving, and managing emails in response to user instructions. In cooperation with image management module 144, email client module 140 greatly facilitates composing and sending emails that include still or video images captured by camera module 143.

[0143] In cooperation with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for entering text strings corresponding to instant messages, modifying previously entered characters, sending instant messages (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 (APNs), or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments, such as those 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, APNs, or IMPS).

[0144] In cooperation 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 player module 146, the training support module 142 includes executable instructions for creating workouts (e.g., including time, distance, and / or calorie burn goals), communicating with training sensors (in the sports device and the smartwatch), receiving training sensor data, calibrating sensors used to monitor workouts, selecting and playing music for workouts, and displaying, storing, and transmitting workout data.

[0145] In cooperation 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, camera module 143 includes executable instructions for capturing still images or video (including video streams), storing them in memory 102, modifying characteristics of the still images or video, and / or deleting the still images or video from memory 102.

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

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

[0148] In cooperation 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, calendar module 148 includes executable instructions for creating, displaying, modifying, and storing calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.

[0149] 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, widget module 149 is optionally a mini-application downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5), or a mini-application created by a user (e.g., user-created widget 149-6). 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).

[0150] 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, widget creator module 150 contains executable instructions for creating widgets (e.g., turning user-specified portions of a web page into widgets).

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

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

[0153] In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 contains executable instructions for creating and managing notes, to-do lists, and the like, in accordance with user instructions.

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

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

[0156] Each of the above-identified modules and applications corresponds to an executable instruction set for performing one or more of the functions and methods described herein (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., instruction sets) need not be implemented as separate software programs, procedures, or modules; thus, various subsets of these modules are optionally combined or otherwise 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.

[0157] 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. Using the touchscreen and / or touchpad as the primary input control device for operation of device 100 optionally reduces the number of physical input control devices (pushbuttons, dials, etc.) on device 100.

[0158] The predefined set of functions, performed exclusively via the touchscreen and / or touchpad, optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 to a main menu, home menu, or 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.

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

[0160] Event sorter 170 receives event information and determines which application 136-1 and application view 191 for application 136-1 to deliver the event information to. 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) to be displayed on touch-sensitive display system 112 when the application is active or running. In some embodiments, device / global internal state 157 is used by event sorter 170 to determine which application(s) is currently active, and application internal state 192 is used by event sorter 170 to determine which application(s) is / are currently active.

[0161] 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 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.

[0162] 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). Peripherals 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). The information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.

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

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

[0165] 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.

[0166] 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 occur. The application view (of the corresponding 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 appropriate inputs is optionally determined based at least in part on the hit view of the initial touch that initiates the touch-based gesture.

[0167] Hit view determination module 172 receives information related to 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-event. In most situations, the hit view is the lowest-level view in which the contributing sub-event occurs (i.e., the first sub-event in the sequence of sub-events that form the event or potential event). Once a hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

[0168] Active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive the particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive the 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 determines that all actively participating views should receive the particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the region associated with a particular view, views higher in the hierarchy remain actively participating views.

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

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

[0171] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each containing instructions for processing touch events that occur within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module, such as a User Interface 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 a data updater 176, an object updater 177, a 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 corresponding event handlers 190. Also, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in the corresponding application view 191.

[0172] 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 also includes at least a subset of metadata 183 and event delivery instructions 188 (optionally including sub-event delivery instructions).

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

[0174] 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, sub-events within Event 187 include, for example, touch start, touch end, touch movement, touch cancellation, 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 predetermined phase on the displayed object, a first lift-off (touch end) for a predetermined phase, a second touch (touch start) for a predetermined phase on the displayed object, and a second lift-off (touch end) for a predetermined phase. In another example, the definition of Event 2 (187-2) is a drag on the displayed object. A drag includes, for example, a touch (or contact) to a predetermined stage 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 about one or more associated event handlers 190.

[0175] In some embodiments, event definition 187 includes a definition of the event for each user interface object. In some embodiments, event comparator 184 performs a hit test to determine the user interface object 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, if a touch is detected on touch-sensitive display system 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 to activate. For example, event comparator 184 selects the event handler associated with the sub-event and the object that triggers the hit test.

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

[0177] 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-ended state and thereafter ignores the next sub-event of the touch-based gesture. In this situation, any other event recognizers that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

[0178] 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 lists that indicate how configurable properties, flags, and / or event recognizers interact or can interact with each other. In some embodiments, metadata 183 includes lists that indicate whether configurable properties, flags, and / or sub-events are delivered to various levels in the view or programmatic hierarchy.

[0179] In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and postponing sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a flag associated with the recognized event, and the event handler 190 associated with the flag catches the flag and performs predefined processing.

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

[0181] 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.

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

[0183] It should be understood that the foregoing description of 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, although not all of them are initiated on a touchscreen. 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, etc. on a touchpad, pen stylus input, device movement, verbal commands, 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.

[0184] FIG. 2 illustrates portable multifunction device 100 with a touchscreen (e.g., touch-sensitive display system 112 of FIG. 1A ) according to some embodiments. The touchscreen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as other 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 the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upward and / or downward), and / or rolling of a finger in contact with device 100 (right to left, left to right, upward and / or downward). In some implementations or situations, accidental contact with a graphic does not select the graphic, for example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon optionally does not select the corresponding application.

[0185] 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 in a set of applications optionally running on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on a touchscreen display.

[0186] In some embodiments, device 100 includes a touchscreen display, a menu button 204, a push button 206 for powering the device on / off and locking the device, volume control button(s) 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and a docking / charging external port 124. Push button 206 is optionally used to turn power on / off on the device by pressing and holding the button down for a predetermined time, to lock the device by pressing and releasing the button before the predetermined time has elapsed, and / or to unlock the device or initiate an unlocking process. In some embodiments, device 100 also accepts verbal input for enabling or disabling certain 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.

[0187] 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 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia playback 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, memory 370, and one or more communication buses 320 for interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communication between system components. Device 300 includes input / output (I / O) interface 330, which includes 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(s) 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(s) 165 described above with reference to FIG. 1A ). Memory 370 includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices, and optionally includes non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, ​​word processing module 384, website creation module 386, disc authoring module 388, and / or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

[0188] 3 are optionally stored in one or more of the memory devices described above. Each of the above-identified modules corresponds to an instruction set that performs 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; 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.

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

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

[0191] 4A are merely exemplary. For example, in some embodiments, icon 422 for video and music player module 152 is labeled "Music" or "Music Player." Other labels are optionally used for various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to the particular application icon.

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

[0193] FIG. 4B shows an example user interface on a device (e.g., device 300 of FIG. 3 ) that includes a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3 ) that is separate from a 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). According to 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 should be understood that similar methods are optionally used for the other user interfaces described herein.

[0194] Additionally, while the following examples are described primarily with reference to finger input (e.g., finger touches, finger tap gestures, finger swipe gestures, etc.), it should be understood that in some embodiments, one or more of those 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 touch), 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 detecting a contact followed by no longer detecting the contact). Similarly, when multiple user inputs are detected simultaneously, it will be understood that multiple computer mice are optionally being used simultaneously, or that a mouse and a finger contact are optionally being used simultaneously.

[0195] As used herein, the term “focus selector” is an input element that indicates the current portion of the user interface with which the user is interacting. In implementations that include a cursor or other location marker, the cursor functions as the “focus selector,” such that when 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 ) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations that include a touchscreen display (e.g., touch-sensitive display system 112 of FIG. 1A or the touchscreen of FIG. 4A ) that allows direct interaction with user interface elements on the touchscreen display, contact detected on the touchscreen functions as the “focus selector,” such that when 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 without a corresponding cursor movement or contact movement on the touchscreen display (e.g., by using the tab or arrow keys to move focus from one button to another), and in these implementations the focus selector moves to follow the movement of focus between different regions of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally a user interface element (or a contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user intends to interact).For example, while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of a focus selector (e.g., a cursor, touch, or selection box) on a corresponding button indicates that the user intends to activate that corresponding button (rather than other user interface elements shown on the device's display).

[0196] 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., a finger contact or a stylus contact) on the touch-sensitive surface, or a 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 distinct values ​​and more typically including hundreds of distinct values ​​(e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors positioned beneath or adjacent to the touch-sensitive surface are optionally used to measure 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 the 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 proxies 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 an intensity threshold has been exceeded (e.g., the intensity threshold is stated 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 an 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 to access additional device functionality that may not otherwise be easily accessible to the user in devices of reduced size with limited area for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0197] In some embodiments, contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by the user (e.g., 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 actuation thresholds of a particular physical actuator and may be adjusted without modifying the physical hardware of device 100). For example, the mouse “click” threshold of a trackpad or touchscreen display can be set to any of a wide range of pre-defined thresholds without modifying 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 at once via a system-level click “intensity” parameter).

[0198] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that 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 predetermined number of intensity samples or a set of intensity samples collected within a predetermined period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) for a predetermined event (e.g., after detecting the contact, before detecting lift-off of the contact, before or after detecting the start of contact movement, 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 value of the intensity of the contact, the average value of the intensity of the contact, the top 10% of the intensity of the contact, half the maximum intensity of the contact, 90% 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 that does not exceed the first threshold results in a first action being performed, a contact having a characteristic intensity that exceeds the first intensity threshold but not the second intensity threshold results in a second action being performed, and a contact having a characteristic intensity that exceeds 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).

[0199] In some embodiments, a portion of a 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 position to an end position where the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end position may be based on only a portion of the swipe contact (e.g., only the portion of the swipe contact at the end position) rather than the entire continuous swipe contact. In some embodiments, a smoothing algorithm may be applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm 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 filter out small increases or decreases in the intensity of the swipe contact for purposes of determining the characteristic intensity.

[0200] The user interface diagrams described herein may include one or more intensity thresholds (e.g., a touch detection intensity threshold IT0, a light pressure intensity threshold IT L , deep pressure intensity threshold IT D (For example, the threshold is, at least initially, L higher), and / or one or more other intensity thresholds (e.g., IT L Lower Intensity Threshold IT H)). This intensity chart is typically not part of the displayed user interface, but is provided to aid in interpretation of the charts. In some embodiments, the light pressure 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 pressure intensity threshold corresponds to an intensity that will cause the device to perform an action different from an action typically associated with a physical mouse button or a trackpad click. In some embodiments, if a contact is detected with a characteristic intensity below the light pressure intensity threshold (e.g., and above the standard contact-detection intensity threshold IT0, below which the contact is no longer detected), the device will move the focus selector according to the movement of the contact on the touch-sensitive surface without performing an action associated with the light or deep intensity thresholds. Generally, unless otherwise specified, these intensity thresholds are consistent across different sets of user interface charts.

[0201] In some embodiments, the device's response to an input detected by the device is determined by criteria based on the intensity of the contact during the input. For example, for some "light press" inputs, the intensity of the contact during the input exceeds a first intensity threshold, triggering a first response. In some embodiments, the device's response to an input detected by the device is determined by criteria including both the intensity of the contact during the input and time-based criteria. For example, for some "deep press" inputs, the intensity of the contact during the input exceeds a second intensity threshold that is greater than the first intensity threshold for the light press, triggering 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 ms in duration (e.g., 40 ms, 100 ms, or 120 ms, depending on the magnitude of the second intensity threshold). This delay time helps avoid accidental deep press inputs. As another example, for some "deep press" inputs, there is a period of reduced sensitivity that occurs after the first intensity threshold is met. During the period of reduced sensitivity, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep pressure inputs. As opposed to other deep pressure inputs, the response to the detection of a deep pressure input is not determined by time-based criteria.

[0202] 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, input timing, running applications, rate at which intensity is applied, number of current inputs, user history, environmental factors (e.g., ambient noise), position of the focus selector, etc. Exemplary factors are described in U.S. Patent Application Serial Nos. 14 / 399,606 and 14 / 624,296, which are incorporated herein by reference in their entireties.

[0203] For example, FIG. 4C illustrates a dynamic intensity threshold 480 that varies over time based in part on the intensity of touch input 476 over time. Dynamic intensity threshold 480 is the sum of two components: a first component 474 that decays over time from when touch input 476 is first detected until after a predetermined delay time p1, and a second component 478 that tracks the intensity of touch input 476 over time. The initial high intensity threshold of first component 474 reduces the inadvertent triggering of a "deep press" response while also allowing for an immediate "deep press" response if touch input 476 provides sufficient intensity. Second component 478 reduces the unintended triggering of a "deep press" response through gradual intensity variations of the touch input. In some embodiments, if touch input 476 meets dynamic intensity threshold 480 (e.g., at point 481 in FIG. 4C ), a "deep press" response is triggered.

[0204] FIG. 4D illustrates another dynamic intensity threshold 486 (e.g., intensity threshold I D ) Figure 4D also shows two other intensity thresholds (first intensity threshold I H and a second intensity threshold I L 4D, a touch input 484 reaches a first intensity threshold I before time p2. H and a second intensity threshold I L , but a response is not provided until delay time p2 has passed time 482. Also in FIG. 4D, the dynamic intensity threshold 486 decays over time, and the decay is proportional to the time (second intensity threshold I L This type of dynamic intensity threshold begins at time 488 after a predetermined delay time p1 has elapsed at time 482 (when the response associated with the first intensity threshold I H or the second intensity threshold I L a dynamic intensity threshold I immediately after or simultaneously with the triggering of a response associated with a lower intensity threshold such as D This reduces the unintended triggering of responses associated with

[0205] FIG. 4E illustrates yet another dynamic intensity threshold 492 (e.g., intensity threshold I D ) is shown. In FIG. 4E, the intensity threshold I LThe response associated with the intensity threshold I is triggered after a delay time p2 has elapsed since the touch input 490 was first detected. At the same time, the dynamic intensity threshold 492 decays after a predetermined delay time p1 has elapsed since the touch input 490 was first detected. Thus, the intensity threshold I L A decrease in the intensity of touch input 490 after triggering a response associated with the touch input 490, followed by an increase in the intensity of touch input 490 without releasing touch input 490, may cause the intensity of touch input 490 to exceed another intensity threshold, e.g., intensity threshold I. L Even if the intensity threshold I D A response associated with the

[0206] Light pressure intensity threshold IT L From an intensity below the threshold IT L and deep pressure intensity threshold IT D Increasing the characteristic intensity of contact to an intensity between 0 and 100 may be referred to as a "light press" input. D From an intensity below the threshold IT D An increase in the characteristic intensity of a contact to an intensity above the contact detection intensity threshold IT0 is sometimes referred to as a "deep press" input. L An increase in the characteristic intensity of the contact to an intensity between ITO and ITO may be referred to as detecting a contact on the touch surface. A decrease in the characteristic intensity of the contact from an intensity above the contact-detection intensity threshold IT0 to an intensity below the contact-detection intensity threshold IT0 may be referred to as detecting lift-off of the contact from the touch surface. In some embodiments, IT0 is zero. In some embodiments, IT0 is greater than zero. In some figures, shaded circles or ellipses are used to represent the intensity of the 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.

[0207] 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 on a respective contact (or contacts), where the respective pressure inputs are detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a pressure input intensity threshold. In some embodiments, the respective actions are performed in response to detecting an increase in intensity of the respective contact above a pressure input intensity threshold (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 above a pressure input intensity threshold and a subsequent decrease in intensity of the contact below the pressure input intensity threshold, and 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).

[0208] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as “jitter,” and the device defines or selects a hysteresis intensity threshold that has a predetermined relationship to the pressure input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the pressure input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the pressure input intensity threshold). Thus, in some embodiments, the pressure input includes a respective increase in the intensity of the contact above the pressure input intensity threshold and a subsequent decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the pressure input intensity threshold, and a respective action is performed in response to detecting the subsequent decrease in the intensity of the respective contact below the hysteresis intensity threshold (e.g., a respective action is performed by an “upstroke” of a respective pressure input). Similarly, in some embodiments, a pressure input is detected only when 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 the detection of the 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).

[0209] For ease of explanation, descriptions of actions performed in response to a pressure input associated with a pressure input intensity threshold or in response to a gesture including that pressure input are optionally triggered in response to detecting an increase in the intensity of the contact above the pressure input intensity threshold, an increase in the intensity of the contact from an intensity below a hysteresis intensity threshold to an intensity above the pressure input intensity threshold, a decrease in the intensity of the contact below the pressure input intensity threshold, or a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the pressure input intensity threshold. Additionally, in examples described as performing an action in response to detecting a decrease in the intensity of the contact below a pressure 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 and lower than the pressure input intensity threshold. As previously mentioned, in some embodiments, the triggering of these responses also depends on whether a time-based criterion has been met (e.g., a delay time has elapsed between meeting a first intensity threshold and a second intensity threshold). User Interface and Related Processes

[0210] Attention now turns to embodiments of user interfaces (“UIs”) 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.

[0211] For ease of explanation, some of the embodiments will be 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 a respective contact or a point associated with a respective contact), or a centroid of two or more contacts detected on touch-sensitive display system 112. However, similar operations are optionally performed on a device with display 450 and separate touch-sensitive surface 451 in response to detection of a contact on touch-sensitive surface 451 while the illustrated user interface, along with a focus selector, is displayed on display 450.

[0212] 5A1-5I9 show exemplary user interfaces for interacting with notifications associated with corresponding applications (e.g., to access a subset of the functionality and content of the corresponding application from the notification without first launching the corresponding application), according to some embodiments. Input on a notification, according to some embodiments, launches the corresponding application associated with the notification or causes an expanded version of the notification to be displayed, providing the user with a subset of the content and / or functionality from the corresponding application without first launching the application.

[0213] 5A1-5A6 illustrate various exemplary user interfaces in which notifications are presented, according to some embodiments.

[0214] 5A1 shows a wake screen user interface 5002 that is displayed when device 100 is activated from a screen-off state (e.g., a sleep state) to a screen-on state (e.g., a wake state) in an unlocked mode (e.g., indicated by an "unlocked" indicator 5004). A number of notifications (e.g., a notification 5006 for a calendar invitation, a notification 5008 for a new instant message, and a notification 5010 for a voicemail message) are displayed on wake screen user interface 5002. Each notification includes notification content (e.g., an excerpt from a communication, a summary of the event or communication, etc.) and specific information identifying the respective application that corresponds to the notification.

[0215] FIG. 5A2 shows a wake screen user interface 5012 that is displayed when device 100 is activated from a screen-off state (e.g., a sleep state) to a screen-on state (e.g., a wake state) in locked mode (e.g., indicated by a “lock” indicator 5014). Numerous notifications (e.g., notification 5016 for a calendar invitation, notification 5018 for a new instant message, and notification 5020 for a voicemail message) are displayed on wake screen user interface 5012. Each notification includes notification content (e.g., an excerpt from a communication, a summary of the event or communication, etc.) and specific information identifying the respective application corresponding to the notification. In some embodiments, device 100 displays a first form of notification (e.g., notification 5006 or notification 5008) with more notification content when the device is in unlocked mode (as shown in FIG. 5A1) and displays a second form of notification (e.g., notification 5016 or notification 5018) with less notification content when the device is in locked mode (e.g., as shown in FIG. 5A2).

[0216] FIG. 5A3 shows a notification (eg, banner 5022 for a new email message) displayed above a home screen user interface 5024 (eg, similar to home screen user interface 400 shown in FIG. 4A).

[0217] 5A4 shows a notification screen 5026 (e.g., a notification center user interface) that is displayed while device 100 is in a locked mode (e.g., indicated by "lock" indicator 5014). A number of notifications (e.g., notifications 5028 and 5030 for two new instant messages, notification 5032 for a new voicemail, and notification 5034 for a new email message) are displayed in a vertical stack on notification screen 5026.

[0218] FIG. 5A5 shows a notification screen 5036 (e.g., a notification center user interface) displayed while device 100 is in unlocked mode (e.g., indicated by “unlocked” indicator 5004). Numerous notifications (e.g., notifications 5038 and 5040 for two new instant messages, notification 5042 for a new voicemail, and notification 5044 for a new email message) are displayed in a vertical stack on notification screen 5036. Each notification includes notification content (e.g., an excerpt from a communication, a summary of the event or communication, etc.) and specific information identifying the respective application corresponding to the notification. In some embodiments, device 100 displays a first form of notification (e.g., notification 5028, notification 5030, or notification 5034) with less notification content when the device is in locked mode (e.g., as shown in FIG. 5A4) and displays a second form of notification (e.g., notification 5038, notification 5040, or notification 5044) with more notification content when the device is in unlocked mode (e.g., as shown in FIG. 5A5). In FIG. 5A5, notification 5038 about an instant message (displayed while the device is in unlocked mode) includes the textual content of the instant message as well as a thumbnail image 5046 of any attached images included in the instant message.

[0219] FIG. 5A6 illustrates a notification (e.g., alert 5048) displayed on an application's user interface (e.g., application user interface 5050). An alert is a type of notification that requests the user to take an action (e.g., confirm a ride request or cancel a ride request). Alerts are also sometimes used when immediate user attention is required, such as when a failure is detected (e.g., failure to connect to a peripheral device or server) or when a user-requested task is not completed successfully (e.g., failure to send a message).

[0220] 5B1-5B4 illustrate a process for launching an application from a notification associated with the application (eg, in response to a tap input on the notification) according to some embodiments.

[0221] FIG. 5B1 shows notification screen 5026 displaying a number of notifications (eg, notifications 5028, 5030, 5032, and 5034) while device 100 is in a locked state.

[0222] FIG. 5B2 illustrates that a contact (eg, contact 5052) is detected on notification 5028 and, in response to detecting the contact, notification 5028 is selected.

[0223] 5B3 and 5B4 illustrate that the characteristic strength of contact 5052 (indicated by "Strength of Contact" on an intensity meter shown next to device 100 in the figures) must exceed a predetermined threshold strength (e.g., a hint strength threshold IT) before lift-off of the contact is detected. H ), device 100 indicates that it will begin a process to launch an instant messaging application (eg, a message application) that corresponds to notification 5028.

[0224] FIG. 5B3 shows that upon detecting the wrist-off of contact 5052, device 100 dims notification screen 5026 and displays an authentication user interface (e.g., password user interface 5054) on dimmed notification screen 5026.

[0225] 5B4 shows that device 100 is unlocked upon receiving correct authentication information from password user interface 5054. In the unlocked mode, device 100 launches a message application and displays a message application user interface (e.g., conversation screen 5056). The user interface (e.g., conversation screen 5056) includes the content of the notification (e.g., the message text (e.g., the text of message 5062), the sender name "Alice") and additional content (e.g., an image (e.g., image 5058) corresponding to one or more previous messages between Alice and the user (e.g., message 5060) and an attached image included in message 5062).

[0226] 5C1-5C6 illustrate a process for displaying a second form of notification having enlarged notification content in response to an input (e.g., a press input) on a first form of notification having standard notification content, according to some embodiments.

[0227] Figure 5C1 shows the same notification screen as Figure 5B1. In Figure 5C1, notification screen 5026 displays a number of notifications (e.g., notifications 5028, 5030, 5032, and 5034) while device 100 is in the locked state.

[0228] FIG. 5C2 illustrates that a contact (eg, contact 5064) is detected on notification 5028 and, in response to detecting the contact, notification 5028 is selected.

[0229] 5C3 and 5C4 illustrate the relationship between the characteristic intensity of contact 5064 and a predetermined threshold intensity (e.g., a hint intensity threshold IT H), device 100 applies dynamic changes to the user interface according to the current value of the characteristic intensity. For example, device 100 dynamically increases (or decreases) the amount of blurring and dimming applied to notification screen 5026 according to the increase (or decrease) in the characteristic intensity of contact 5064, with notification 5028 overlaid on blurred and dimmed notification screen 5026. As shown in FIGS. 5C3 and 5C4, when the contact intensity increases above IT H and a first higher intensity threshold (e.g., a light pressure intensity threshold IT L ), the amount of blur and dimming applied to the notification screen 5026 increases accordingly. L ), dropping off the contact returns the user interface to its original state (eg, the state shown in FIG. 5C1).

[0230] FIG. 5C5 illustrates a first intensity threshold (e.g., a light pressure intensity threshold IT) for a characteristic intensity of contact 5064. L ), an enlarged form of the notification (e.g., notification 5066) is displayed on a blurred and dimmed notification screen 5026. Additionally, in some embodiments, the appearance of the notification screen 5026 is maintained (e.g., does not change according to the current characteristic intensity of contact 5064) as it was the first time the characteristic intensity exceeded the first intensity threshold. As shown in FIG. 5C5, the enlarged form of the notification (e.g., notification 5066) includes content and additional functionality (e.g., selectable options for performing actions related to the notification or application) from the originally displayed form of the notification (e.g., notification 5028) and / or content not included in the originally displayed form of the notification. For example, notification 5066 includes a "Reply" button 5068 for launching a "Reply" user interface for creating a reply to the message shown in the notification, and a "Delete" button 5070 for deleting the message shown in the notification. Notification 5066 optionally includes a preview of an attached image from the message shown in the notification.

[0231] 5C6 shows that the enlarged notification (e.g., notification 5066) remains displayed on the blurred and darkened notification screen after liftoff of contact 5064 is detected. Another input (e.g., a tap input) subsequently detected on the enlarged notification (e.g., notification 5066) outside the area occupied by buttons 5068 and 5070 initiates a process to launch the Messages application (e.g., as shown in FIGS. 5B3 and 5B4).

[0232] 5D1-5E4 illustrate a process in which moving a contact beyond a threshold distance cancels the display of an enlarged notification, according to some embodiments.

[0233] Figure 5D1 shows the same notification screen as Figures 5B1 and 5C1. In Figure 5D1, notification screen 5026 displays a number of notifications (e.g., notifications 5028, 5030, 5032, and 5034) while device 100 is in the locked state.

[0234] FIG. 5D2 illustrates that a contact (eg, contact 5072) is detected on notification 5028 and, in response to detecting the contact, notification 5028 is selected.

[0235] 5D3 and 5D4 illustrate the relationship between the characteristic intensity of contact 5072 and a predetermined threshold intensity (e.g., a hint intensity threshold IT H ), device 100 applies dynamic changes to the user interface according to the current value of the characteristic intensity. For example, device 100 dynamically increases (or decreases) the amount of blurring and dimming applied to notification screen 5026 according to the increase (or decrease) in the characteristic intensity of contact 5072, with notification 5028 overlaid on blurred and dimmed notification screen 5026. As shown in FIGS. 5D3 and 5D4, when the contact intensity increases above IT H and a first higher intensity threshold (e.g., a light pressure intensity threshold IT L), the amount of blur and dimming applied to notification screen 5026 increases accordingly. Before the characteristic intensity of contact 5072 exceeds the first intensity threshold, dropping the contact returns the user interface to its original state (e.g., the state shown in FIG. 5D1).

[0236] 5D5 shows that movement of contact 5072 is detected before the characteristic intensity of contact 5072 exceeds a first intensity threshold. If the amount of movement is less than the first movement threshold (e.g., 10 pixels), device 100 continues to dynamically change the amount of blurring and dimming applied to notification screen 5026 according to the current value of the characteristic intensity of contact 5072. For example, the amount of blurring and dimming is greater in notification screen 5026 in FIG. 5D5 compared to notification screen 5026 in FIG. 5D4.

[0237] FIG. 5D6 illustrates that as soon as the amount of movement made by contact 5072 becomes greater than the first movement threshold, the device cancels the hint effect (e.g., blurring and darkening of notification screen 5026) brought about according to the current contact intensity, and notification screen 5026 is restored to its original brightness and luminance. In addition, device 100 recognizes the gesture provided by contact 5072 as a drag gesture. Thus, device 100 moves notification 5028 according to the movement of contact 5072 (e.g., notification 5028 is dragged to the left by contact 5072). As shown in FIG. 5D6, as soon as the intensity of contact 5072 exceeds the first intensity threshold (e.g., IT L ) but no enlarged notification is presented (as opposed to the case shown in FIG. 5C5, for example).

[0238] FIG. 5D6 shows that as contact 5072 continues to move, notification 5028 is dragged further to the left, and a quick response action affordance (eg, "delete" affordance 5074) appears from behind notification 5028.

[0239] As shown in FIGS. 5D6 and 5D7, once a threshold movement amount by contact 5072 is detected, the user interface does not respond to further changes in the characteristic intensity of contact 5072 and / or the characteristic intensity that matches the first intensity threshold.

[0240] 5D8 shows that after the quick response action affordance ("Delete" affordance 5074) appears, the quick response action affordance and, optionally, notification 5028 along with the remainder of notification screen 5026 remain displayed after lift-off of contact 5072 is detected. Selection of "Delete" affordance 5074 with another input (e.g., a tap input) deletes notification 5028 and / or the message shown in notification 5028.

[0241] 5D5-5D8, after dragging notification 5028 and revealing "delete" affordance 5074, movement of contact 5072 in the opposite direction (e.g., from left to right) returns notification 5028 to its original position and re-hides "delete" affordance 5074. Additionally, while not shown in FIGS. 5D5-5D8, movement of contact 5072 in the opposite direction (e.g., from left to right) initiated while notification 5028 is in its original position drags notification 5028 to the right and reveals a different quick response action affordance (e.g., the "flag" affordance or the "reply" affordance).

[0242] Figures 5E1-5E4 show movement of contact 5072 in the vertical direction. Figure 5E1 is a continuation of Figure 5D3 and is the same as Figure 5D4.

[0243] 5E1 and 5E2, movement of contact 5072 in the vertical direction is detected (e.g., as shown in FIG. 5E2) before the characteristic intensity of contact 5072 exceeds a first intensity threshold. If the amount of movement is less than a second movement threshold (e.g., 10 pixels or another threshold number of pixels), device 100 continues to dynamically change the amount of blurring and dimming of notification screen 5026 according to the current value of the characteristic intensity of contact 5072.

[0244] FIG. 5E3 illustrates that as soon as the amount of movement made by contact 5072 becomes greater than the second movement threshold, the device cancels the hint effect (e.g., blurring and darkening of notification screen 5026) brought about according to the current contact intensity, and notification screen 5026 is restored to its original brightness and luminance. In addition, device 100 recognizes the gesture provided by contact 5072 as a scrolling gesture. Thus, device 100 scrolls notification screen 5026 according to the movement of contact 5072 (e.g., notification 5028 is scrolled upward by contact 5072, along with another notification in notification screen 5026). As illustrated in FIG. 5E3, the intensity of contact 5072 increases as the intensity of contact 5072 increases beyond the first intensity threshold (e.g., IT L ) but no enlarged notification is presented (as opposed to the case shown in FIG. 5C5, for example).

[0245] As shown in FIGS. 5E1-5E3, once a threshold movement amount is detected, the user interface does not respond to further changes in the characteristic intensity of contact 5072 and / or the characteristic intensity that matches the first intensity threshold.

[0246] FIG. 5E4 shows that after notification screen 5026 has been scrolled, notification screen 5026 remains in a scrolling state even after liftoff of contact 5072 is detected.

[0247] Although not shown in FIGS. 5E1-5E4, moving contact 5072 in the opposite direction (e.g., downward) after scrolling the notification screen upward causes the notification screen to scroll downward again.

[0248] Additionally, in some embodiments (not shown in FIGS. 5E1-5E4), instead of scrolling the entire notification screen, movement of contact 5072 scrolls the notification content within notification 5028. In some embodiments (not shown in FIGS. 5E1-5E4), scrolling of the notification content takes priority before scrolling of the notification screen. In other words, movement of the contact causes the notification content to scroll first, and if the movement of the contact continues without allowing the notification content to scroll any further according to the movement of the contact, scrolling of the notification screen begins.

[0249] In some embodiments (not shown in FIGS. 5E1-5E4), if the touchdown location of the contact is within the notification, moving the contact scrolls only the notification content. In such embodiments, scrolling of the notification screen occurs when the initial touchdown location of the contact is outside the content area of ​​the notification (e.g., outside the notification, on the header portion of the notification, or outside or straddling the border of the notification screen), and the contact moves vertically within the notification screen.

[0250] Although the examples shown in Figures 5D1-5E4 are shown for notifications shown when device 100 is in locked mode, canceling the hint state (e.g., blurring and dimming the background user interface) and scrolling the background user interface in accordance with dragging and / or contact movement of a notification also applies to notifications shown when device 100 is in unlocked mode (e.g., notifications with limited notification content).

[0251] 5F1-5F7 illustrate a process for displaying a second form of notification with enlarged notification content in response to an input (e.g., a press input) on a first form of notification with standard notification content, according to some embodiments. In contrast to the process illustrated in FIGS. 5C1-5C6, here the device is in unlocked mode and limited functionality and limited notification content are provided in the second form of notification.

[0252] In FIG. 5F1, notification screen 5036 displays a number of notifications (eg, notifications 5038, 5040, 5042, and 5044) while device 100 is in the unlocked state.

[0253] FIG. 5F2 illustrates that a contact (eg, contact 5076) is detected on notification 5038, and that in response to detecting the contact, notification 5038 is selected.

[0254] FIG. 5F3 illustrates the relationship between the characteristic intensity of contact 5076 and a predetermined threshold intensity (e.g., a hint intensity threshold IT H ), indicates that device 100 applies dynamic changes to the user interface according to the current value of the characteristic intensity. For example, with notification 5038 overlaid on blurred and dimmed notification screen 5036, device 100 dynamically increases (or decreases) the amount of blurring and dimming applied to notification screen 5036 according to the increase (or decrease) in the characteristic intensity of contact 5076. H and a first higher intensity threshold (e.g., a light pressure intensity threshold IT L ), the amount of blur and dimming applied to notification screen 5036 increases accordingly. Before the characteristic intensity of contact 5076 exceeds the first intensity threshold, dropping the contact returns the user interface to its original state (e.g., the state shown in FIG. 5F1).

[0255] FIG. 5F4 illustrates a first intensity threshold (e.g., a light pressure intensity threshold IT L), an enlarged form of the notification (e.g., notification 5078) is displayed on the blurred and dimmed notification screen 5036. Additionally, in some embodiments, the appearance of the notification screen 5036 is maintained (e.g., does not change according to the current characteristic intensity of contact 5076) when the characteristic intensity exceeds the first intensity threshold for the first time.

[0256] As shown in FIG. 5F4, the expanded form of a notification (e.g., notification 5078) includes content from the initially displayed form of the notification (e.g., notification 5038) (e.g., message text (e.g., the text of message 5062, the sender name "Alice") and additional functionality (e.g., selectable options for performing actions related to the notification or application), and / or content not included in the initially displayed form of the notification. For example, notification 5078 includes a "Reply" button 5082 for launching a "Reply" user interface for creating a reply to the message shown in the notification. Notification 5078 may include one or more previous messages (e.g., a "Reply" button 5082) between Alice and the user. Notification 5078 further includes an image (e.g., image 5058) corresponding to thumbnail 5046 included in notification 5028 (e.g., message 5060) and notification 5028 (image 5058 is an attachment included in message 5062). Notification 5078 further includes a header area 5080 (e.g., an area for displaying a conversation log) and a control area (e.g., an area for displaying control affordances (e.g., "Reply" affordance 5082)) that are separate from the content area. Header area 5080 includes information identifying the message application (e.g., an application icon and application name) and information identifying the sender of the message (e.g., avatar 5084 of sender "Alice").

[0257] Although not shown in Figures 5F1-5F5, the enlarged notification (e.g., notification 5078) remains displayed on the blurred and darkened notification screen after liftoff of contact 5076 is detected. Another input (e.g., a tap input) subsequently detected on the enlarged notification (e.g., notification 5078) outside the area occupied by affordance 5082 (e.g., a tap input on the notification content area or header area) launches the Messages application (e.g., as shown in Figure 5B4).

[0258] 5F5-5F7 show that a second press input by the same contact (e.g., contact 5076) on reply affordance 5082 before lift-off activates reply affordance 5082 and displays the reply user interface. FIG. 5F5 shows that contact 5076 moves from its original position to a position on reply affordance 5082 before lift-off. FIG. 5F6 shows that while contact 5076 is in a position on reply affordance 5082, an increase in the characteristic intensity of contact 5076 is detected, and the characteristic intensity increases beyond a corresponding intensity threshold (e.g., a light pressure intensity threshold IT L ) exceeding the corresponding intensity threshold. FIG. 5F5 also illustrates that the characteristic intensity of contact 5076 may have dropped below the corresponding intensity threshold (e.g., the characteristic intensity of contact 5076 may have dropped below the corresponding intensity threshold during the movement of contact 5076 from its original position to a position on reply affordance 5082) before the characteristic intensity of contact 5076 exceeded the corresponding intensity threshold. L If an increase in intensity above a corresponding intensity threshold is detected (in other words, a second pressure input is detected while contact 5076 is substantially stationary), contact 5076 does not move more than the threshold amount (e.g., is substantially stationary).

[0259] 5F7 shows that, based on liftoff of contact 5076, reply affordance 5082 is activated and a reply user interface (e.g., reply user interface 5090) is displayed. In some embodiments, the reply user interface (e.g., reply user interface 5090) is displayed over a blurred and dimmed notification screen 5036. In some embodiments, the reply user interface is updated in real time (e.g., message bubble 5088 indicates that Alice is composing a message). The reply user interface includes a soft keyboard 5092 and a message input field for displaying a draft message (e.g., "Oh?") entered by the user.

[0260] 5G1-5G3 show that a tap input detected outside of enlarged notification 5078 dismisses notification 5078 (and its shortened form, notification 5038). FIG. 5G1 shows enlarged notification 5078 overlaid on blurred and darkened notification screen 5036, for example, after liftoff of contact 5076 from the state shown in FIG. 5F4.

[0261] FIG. 5G2 shows that a new contact 5096 has been detected outside of enlarged notification 5078. FIG. 5G3 shows that, upon liftoff of contact 5096, notification screen 5036 is restored to its original brightness and intensity. In addition, notification 5038 and enlarged notification 5078 have been removed from the user interface and are no longer displayed. Other notifications that were not removed (e.g., notifications 5040, 5042, and 5044) are displayed in restored notification screen 5036.

[0262] 5H1 and 5H2 show that after the state shown in FIG. 5G1, a tap input detected within the enlarged notification 5078 (e.g., a tap input detected within the content area of ​​the enlarged notification 5078) launches the messaging application.

[0263] As shown in FIG. 5H1 , new contact 5098 is detected within the content area of ​​enlarged notification 5078. FIG. 5H2 shows that, based on liftoff of contact 5098, device 100 launches the message application, and a user interface of the message application (e.g., application user interface 5100) replaces enlarged notification 5078 and notification screen 5036 on touchscreen display 112. Tapping on the enlarged notification causes the message application to launch in a user interface in the message application that corresponds to the notification content (e.g., a user interface including a conversation log for message communications between the user and sender “Alice”) rather than a default user interface that would be displayed if the message application were launched by tapping on a message application icon on the home screen (e.g., the last user interface shown when the user previously exited the message application, or a user interface including an index of conversations the user has had with other users).

[0264] 5I1-5I9 illustrate another example where an enlarged notification is presented in response to a detected press on a notification about a ride-sharing application, providing a subset of content and functionality from the ride-sharing application without first launching the application.

[0265] In FIG. 5I1, a first form of notification (eg, banner 5104) is displayed over a background user interface (eg, email inbox user interface 5102 of an email application).

[0266] FIG. 5I2 illustrates a case in which a contact 5106 is detected on a first form of notification (e.g., banner 5104) and the characteristic intensity of the contact 5106 is greater than or equal to the hint threshold IT H, a de-emphasis visual effect (e.g., blurring and dimming of the background user interface (e.g., user interface 5102)) is applied to the background user interface, while notification 5104 visually lifts off the background user interface without the de-emphasis visual effect. H and IT L and indicates that the amount of de-emphasis visual effect dynamically changes (e.g., increases (or decreases)) according to changes in the characteristic intensity of contact 5106. Applying the de-emphasis visual effect provides the user with a hint of an alternative way in which they can access a subset of the application's content and functionality without leaving the current context.

[0267] FIG. 5I4 illustrates the characteristic intensity of contact 5106 exceeding a first intensity threshold IT L 5I3 , an expanded form of the notification (e.g., expanded notification 5108) is displayed over a de-emphasized background user interface (e.g., application user interface 5102). As shown in FIG. 5I3 , expanded notification 5108 includes a header portion 5110 that includes information identifying the corresponding application associated with the notification (e.g., the application icon and application name for the ride-sharing application “Rides”). Expanded notification 5108 also includes a content area (e.g., content area 5112) that displays notification content (e.g., text and graphics related to the content of the notification). The notification content shown in the expanded form of the notification includes content that was not shown in the originally displayed form of the notification (e.g., map 5114 and further details about the ride-sharing provider that were not included in notification 5104).

[0268] In some embodiments, the content included in the enlarged notification 5108 is dynamically updated. For example, the location of the car icon 5116 in the map 5114 indicates the real-time location of the car that accepted the ride request and is constantly updated while the enlarged notification 5108 is displayed on the device 100.

[0269] In some embodiments, the content region 5112 in the expanded notification 5108 is scrollable. Figures 5I5 and 5I6 show that one or more scroll inputs (e.g., provided by contacts 5120 and 5126 moving upward within the content region) cause the content region to scroll upward to reveal a control region containing additional content and one or more control affordances (e.g., control affordances 5122, 5124, 5128, and 5130).

[0270] FIG. 5I7 shows that an update regarding the arrival of a rideshare has been received and a pop-up banner alert 5132 is displayed within the expanded notification 5108. Additionally, a car icon 5116 shows the driver's current location on the map 5114.

[0271] 5I8 and 5I9 show that a tap input (e.g., by contact 5134) is detected on control affordance 5122 for initiating a call to the rideshare driver (e.g., as shown in FIG. 5I8), and that in response to the tap input, device 100 initiates a call to the rideshare driver, and an enlarged notification 5108 displays phone user interface 5136 during the call. Control affordance 5122 changes its appearance to indicate that a call is in progress once the call is connected.

[0272] Although not shown in Figures 5I1-5I9, a tap input detected within the content area of ​​magnified notification 5108 (e.g., outside of any control affordances) launches a rideshare application, with the rideshare application's user interface replacing the display of magnified notification 5108 and background user interface 5102. Additionally, a tap input detected outside magnified notification 5108 causes the notification to disappear (e.g., both notification 5104 and magnified notification 5108 are no longer displayed) and the background user interface (e.g., application user interface 5102) to be restored to its original brightness and intensity.

[0273] 5J1-5P2 illustrate exemplary user interfaces for displaying a contextual content object (e.g., a mini-application object) associated with a corresponding application (e.g., to provide access to a subset of the corresponding application's functionality and content from the contextual content object without first launching the corresponding application), according to some embodiments. The contextual content object is presented alongside a menu of selectable options for activating one or more features of the corresponding application. The contextual content object responds to user input to display more information and functionality from the corresponding application without launching the application, according to some embodiments.

[0274] 5J1 and 5J2 illustrate a process for launching an application via a tap input on an application icon in a menu of applications, according to some embodiments.

[0275] 5J1, a user interface (e.g., home screen 5202) includes an array of application icons representing various applications installed on device 100. A contact (e.g., contact 5204) is detected on one of the application icons (e.g., application icon 424 associated with a messaging application) and the characteristic intensity of contact 5204 exceeds detection threshold intensity IT0 and hint intensity threshold IT H If the value falls below , the application icon is selected.

[0276] FIG. 5J2 shows that, upon liftoff of contact 5204, device 100 launches the messages application and replaces the display of home screen 5202 with a user interface for the messages application (e.g., user interface 5208 displaying a list of the user's contacts with whom the user has previously conversed in the messages application (e.g., a list of conversations the user has had with other users in the messages application)).

[0277] 5K1-5K4 illustrate a process in which a press, instead of a tap, is detected on a message application icon, causing the press to display a contextual content object and a menu of options instead of launching the message application.

[0278] 5K1, home screen 5202 is displayed. A contact (e.g., contact 5206) is detected on one of the application icons (e.g., application icon 424 associated with a messaging application) and the characteristic intensity of contact 5206 exceeds detection threshold intensity IT0 and hint intensity threshold IT H If the value falls below , the application icon is selected.

[0279] 5K2 and 5K3 illustrate the relationship between the characteristic intensity of the contact 5206 and the predetermined threshold intensity (e.g., the hint intensity threshold IT H), device 100 applies dynamic changes to the user interface according to the current value of the characteristic intensity. For example, with application icons 424 superimposed on blurred and dimmed home screen 5202, device 100 dynamically increases (or decreases) the amount of blurring and dimming applied to home screen 5202 according to an increase (or decrease) in the characteristic intensity of contact 5206. In addition, a menu platter (e.g., platter 5208) appears between application icons 424 and home screen 5202, and the size of the platter changes (e.g., expands or contracts) according to the change in the characteristic intensity of contact 5206. As shown in FIGS. 5K2 and 5K3, when the contact intensity increases above IT H and a first higher intensity threshold (e.g., a light pressure intensity threshold IT L ), the amount of blur and dimming applied to home screen 5202 increases accordingly, and the size of platter 5208 increases accordingly. Before the characteristic intensity of contact 5206 exceeds the first intensity threshold, dropping the contact returns the user interface to its original state (e.g., the home screen shown in FIG. 5K1 with no application icon 424 selected).

[0280] FIG. 5K4 illustrates a first intensity threshold (e.g., a light pressure intensity threshold IT) for a characteristic intensity of contact 5206. L), a contextual content object (e.g., mini application object or widget 5210) associated with a message application is displayed on blurred and dimmed home screen 5202. The contextual content object includes context-selected content that is automatically selected based on the current context of device 100. For example, mini application object 5210 is a widget that includes a grid of people selected based on the number of messages sent between the user and the user's contacts (e.g., mini application object 5210 includes avatars or aliases (e.g., avatars 5224, 5226, 5228, and 5230) of the four people with whom the user has had the most instant messaging communications during the past week). In some embodiments, each avatar or alias also includes a badge (e.g., badges 5232 and 5234) that indicates the number of unread instant messaging communications from the person represented by the respective avatar or alias. For example, badge 5232 indicates that there are eight unread messages from Issac, and badge 5234 indicates that there are four unread messages from Miles. If a new message is received at device 100 from the person represented in mini application object 5210 while mini application object 5210 is displayed, the badges are updated.

[0281] In addition to the contextually selected content, mini-application object 5210 also includes an "add widget" affordance (e.g., affordance 5222) for adding mini-application object 5210 to another user interface (e.g., a mini-application object screen or a widget screen) configured to provide a number of mini-application objects associated with various applications installed on device 100. In some embodiments, affordance 5222 is displayed only if mini-application object 5210 is not already present in a user interface (e.g., a mini-application object screen or a widget screen) configured to host a number of mini-application objects associated with various applications installed on device 100.

[0282] Additionally, a menu of selectable options (e.g., menu 5212) is displayed concurrently with the contextual content object (e.g., mini-application object 5210). The menu of selectable options includes options (e.g., options 5214, 5216, 5218, 5220) that, when activated, are configured to launch the message application into a respective user interface of the message application to perform a respective function associated with the message application. For example, selection of option 5214 displays a new message user interface for the user to compose a new message, and selection of options 5216, 5218, and 5220 each displays a conversation interface for a message conversation between the user and the person(s) shown in the option (e.g., S. Ramanujan, Mom, and G. Hardy, respectively).

[0283] Additionally, in some embodiments, the appearance of home screen 5202 is maintained (eg, does not change according to the current characteristic intensity of contact 5206) the first time the characteristic intensity exceeds the first intensity threshold.

[0284] 5K4, the contextual content object (e.g., mini-application object 5210) includes contextually selected content from the messages application (e.g., the user's avatar, a small messages application icon, and the application name), and, optionally, additional functionality (e.g., avatars 5224, 5226, 5228, and 5230 respond to tap or deep press inputs to perform various actions related to mini-application object 5210 and / or the messages application). For example, tapping on avatar 5224 launches a conversation user interface for launching the messages application, reviewing previous messages, and composing replies to messages shown in the conversation user interface.

[0285] 5K5-5K7 illustrate a process for adding contextual content objects to a user interface configured to display respective contextual content objects associated with various applications of a plurality of applications installed on device 100.

[0286] FIG. 5K5 shows that the contextual content object (e.g., mini-application object 5210) remains displayed on blurred and darkened home screen 5202 after lift-off of contact 5206 is detected. Another input (e.g., a tap input by contact 5236) is subsequently detected on an “add widget” affordance (e.g., affordance 5222) displayed within (or in some way concurrently with) the contextual content object (e.g., mini-application object 5206).

[0287] FIG. 5K6 illustrates an animation being presented indicating the addition of a contextual content object (e.g., mini-application object 5210) to a user interface configured to display respective contextual content objects associated with various applications of a plurality of applications installed on device 100 based on lift-off of contact 5236. For example, a mini-application object screen (e.g., mini-application object screen or widget screen 5238) is shown sliding in from the left of the display and partially covering home screen 5202, and mini-application object 5210 is shown jumping in from its original position into a slot in mini-application object screen 5238. As shown in FIG. 5K6, mini-application object screen 5238 already includes two mini-application objects (e.g., next appointment mini-application object 5240 associated with a calendar application and calendar mini-application object 5242 associated with the calendar application).

[0288] FIG. 5K7 shows that once mini-application object 5210 is added to mini-application object screen 5238, mini-application object screen 5238 slides back to the left and becomes invisible. The user interface is restored to the state it was in before the "Add Widget" affordance was activated (e.g., the state shown in FIG. 5K4). As shown in FIG. 5K7, once mini-application object 5210 is added to mini-application object screen 5238, the "Add Widget" affordance is no longer displayed on mini-application object 5210. Instead, an indicator (e.g., the text "Added" or a check mark) is displayed to indicate that mini-application object 5210 has already been added to the mini-application object screen. In some embodiments, the indicator (e.g., the text "Added" or a check mark) is displayed only briefly immediately after mini-application object 5210 is added to mini-application object screen 5238. In some embodiments (not shown), when a mini application object 5210 is added to the mini application object screen 5238 in response to activation of the “Add Widget” affordance, the device 100 displays the mini application object screen 5238 including the newly added mini application object 5210 in place of the home screen 5202.

[0289] 5K8-5L3 illustrate that different portions of a contextual content object (eg, mini-application object 5210) have different responses to pressure input (eg, a light pressure input or a deep pressure input).

[0290] 5K8-5K10 illustrate a light press input (e.g., a light press intensity threshold IT) on a first portion of the mini-application object 5210. L5248) has been detected and indicates that further information of a first type is to be displayed.

[0291] Figure 5K8 shows that contact 5248 is detected on a portion of mini-application object 5210 outside of any avatars contained in mini-application object 5210. Figure 5K9 shows that if the characteristic intensity of contact 5248 exceeds a corresponding intensity threshold (e.g., a light pressure intensity threshold), an additional row of avatars / aliases (e.g., avatars 5252, 5254, 5256, and 5258) is displayed. These additional avatars / aliases are for people selected based on the number of messages sent between the user and the user's contacts (e.g., mini-application object 5210 currently includes additional avatars or aliases (e.g., avatars 5252, 5254, 5256, and 5258) for the four people with whom the user had the next most instant messaging communications during the past week). Figure 5K10 shows that based on the liftoff of contact 5248, the additional avatars and aliases (e.g., avatars 5252, 5254, 5256, and 5258) remain displayed in mini-application object 5210.

[0292] 5L1-5L3 illustrate a light press input (e.g., a light press intensity threshold IT) on a second portion of the mini-application object 5210. L 5260) has been detected and indicates that further information of a second type is to be displayed.

[0293] FIG. 5L1 shows that contact 5260 is detected on a portion of mini-application object 5210 that displays one of the avatars included in mini-application object 5210 (e.g., contact 5260 is detected on avatar 5230). FIG. 5L2 shows that if the characteristic intensity of contact 5260 exceeds a corresponding intensity threshold (e.g., a light pressure intensity threshold), the last communication (e.g., message 5262) ​​from the person represented by the selected avatar (e.g., avatar 5230) is displayed in mini-application object 5210. FIG. 5L3 shows that the last communication (e.g., message 5262) ​​is removed from mini-application object 5210 based on liftoff of contact 5260. The user can press on another avatar to view the last communication from the person represented by that avatar. FIG. 5L1 shows that an additional avatar is also displayed in response to a press input by contact 5260, although this is optional or not performed in some embodiments.

[0294] 5L4 and 5L5 illustrate that a tap input (e.g., by contact 5264) detected outside of mini-application object 5210 and menu 5212 causes mini-application object 5210 and menu 5212 to disappear from home screen 5202. Home screen 5202 is restored to its original brightness and brightness.

[0295] 5L6-5L8 show that a swipe input (e.g., with contact 5266 moving from left to right) on home screen 5202 causes home screen 5202 to scroll to the right and mini-application object screen 5238 to appear from the left. FIG. 5L8 shows that mini-application object screen 5238 now replaces home screen 5202 and occupies the entire display 112.

[0296] 5L8, mini-application object screen 5238 includes a number of mini-application objects each associated with a corresponding application (e.g., mini-application object 5268 associated with a messages application, mini-application object 5240 associated with a calendar application, and mini-application object 5242 associated with a calendar application). In some embodiments, each mini-application object includes an affordance for displaying more information about the mini-application object (e.g., a "show more" affordance).

[0297] 5L9-5M2 illustrate that different portions of a contextual content object (eg, mini-application object 5268) have different responses to input (eg, tap input).

[0298] 5L9 and 5L10 illustrate that a tap input (e.g., by contact 5272) detected on a first portion of mini application object 5268 (e.g., a tap input detected on avatar 5230) causes device 100 to launch a message application and display a first user interface of the message application (e.g., a conversation user interface for a message conversation between the user and the person represented by selected avatar 5230). In FIG. 5L9, mini application object 5268 is displayed on mini application object screen 5238. Contact 5272 is detected on avatar 5230 of mini application object 5268. The characteristic intensity of contact 5272 is measured using a light pressure intensity threshold IT L5L10, upon lift-off of contact 5272, device 100 launches a message application and replaces mini-application object screen 5238 with a conversation user interface (e.g., conversation user interface 5274) of the message application. The conversation user interface (e.g., conversation user interface 5274) displays a message conversation between the user and the person represented by the selected avatar (e.g., avatar 5230). The conversation interface displays one or more previous messages (e.g., messages 5276, 5278, and 5280) sent between the user and the person represented by the selected avatar. The conversation interface also includes a soft keyboard 5282 and a text entry field for composing a message to the person represented by the selected avatar.

[0299] 5M1 and 5M2 illustrate that a tap input (e.g., by contact 5284) detected on a second portion of mini-application object 5268 (e.g., a tap input detected on the header portion) causes device 100 to launch a message application and display a second user interface of the message application (e.g., a conversation list user interface for listing message conversations the user has had with other users). In FIG. 5M1, mini-application object 5268 is displayed on mini-application object screen 5238. Contact 5284 is detected on the header portion of mini-application object 5268. The characteristic intensity of contact 5284 is measured against a light pressure intensity threshold IT L5M2, based on lift-off of contact 5284, device 100 launches the message application and replaces mini-application object screen 5238 with a conversation list user interface (e.g., conversation list user interface 5286) of the message application. The conversation list user interface (e.g., conversation list user interface 5286) displays a list of message conversations between the user and the user's other contacts. The user can navigate to the conversation user interface for each person by selecting the corresponding list item in conversation list user interface 5286 (e.g., a tap input on the conversation list item for Genevive would cause the device to display the conversation user interface shown in FIG. 5L10).

[0300] 5N1-5N4 illustrate a process in which a deep press is detected on a contacts application icon and the deep press causes a contextual content object and a menu of options for the contacts application to be displayed on the home screen.

[0301] 5N1, home screen 5288 is displayed. A contact (e.g., contact 5290) is detected over one of the application icons (e.g., application icon 445 associated with a contacts application (e.g., also referred to as an address book application)) and the characteristic intensity of contact 5290 exceeds detection threshold intensity IT0 and hint intensity threshold IT H If the value falls below , the application icon is selected.

[0302] 5N2 and 5N3 illustrate the relationship between th...

Claims

1. An electronic device comprising a display device and one or more input devices, displaying a control user interface on the display device, the control user interface including a plurality of control affordances; Detecting a first portion of a first input for a first control affordance of the plurality of control affordances; in response to detecting the first portion of the first input, switching a function of a control corresponding to the first control affordance in accordance with a determination that the first portion of the first input includes an end of the first input and that the first portion of the first input satisfies a control toggle criterion, the control toggle criterion not requiring that a characteristic value of the first input satisfy a first input threshold in satisfying the control toggle criterion; displaying one or more change options for the control corresponding to the first control affordance prior to detecting the end of the first input in accordance with determining that the first portion of the first input satisfies an extended control criterion, the extended control criterion requiring that a characteristic value of the first input satisfy the first input threshold value in satisfying the extended control criterion; detecting, in accordance with a determination that the first portion of the first input satisfies the extended control criterion, a second portion of the first input that includes a movement of the first input from a first position corresponding to the first control affordance to a second position corresponding to a first change option of the one or more change options for the control corresponding to the first control affordance while the one or more change options for the control are displayed, whereby the end of the first input is detected; and after detecting the second portion of the first input, modifying a functionality of the control corresponding to the first control affordance according to the first modification option.

2. The method of claim 1 , wherein the first change option toggles the functionality of the control that corresponds to the first control affordance.

3. Changing a function of the control corresponding to the first control affordance in accordance with the first change option includes: modifying the function according to the first modification option in response to determining that the function is on when the second portion of the first input is detected; and in response to a determination that the function is off when the second portion of the first input is detected, turning on the function with a modification in accordance with the first modification option; The method of claim 1 or 2, comprising:

4. The method of claim 1 , wherein the first change option changes a mode of the control that corresponds to the first control affordance.

5. modifying the control corresponding to the first control affordance in accordance with the first modification option includes setting restoration criteria for the control, the restoration criteria including conditions for restoring the changes made to the control; 5. The method of claim 1, further comprising: restoring the control corresponding to the first control affordance to a previous state of the control in accordance with a determination that the restoration criterion is met.

6. determining a state of the control corresponding to the first control affordance in accordance with a determination that the property value of the first portion of the first input satisfies the extended control criterion; displaying a first set of change options for the control corresponding to the first control affordance in accordance with determining that the state of the control corresponding to the first control affordance is a first state; displaying a second set of change options for the control corresponding to the first control affordance, the second set of change options being different from the first set of change options, in accordance with determining that the state of the control corresponding to the first control affordance is a second state; The method of any one of claims 1 to 5, comprising:

7. 7. The method of claim 1, further comprising: displaying a current value of a parameter of the control simultaneously with the one or more change options for the control corresponding to the first control affordance in accordance with a determination that the first portion of the first input satisfies the extended control criteria.

8. the first control affordance is a first application affordance corresponding to a first application, a second application affordance corresponding to the first application is displayed in a second user interface distinct from the control user interface; when a display action option criterion is met, one or more action options for the first application are displayed in response to an input to the second application affordance; 8. The method of claim 1, wherein the one or more change options for the control corresponding to the first control affordance include at least a subset of the action options for the first application.

9. The method of claim 1 , wherein the one or more change options for the control corresponding to the first control affordance include at least one network connection activation option.

10. The method of claim 1 , wherein the control user interface is partially overlaid on a portion of a second user interface that is different from the control user interface.

11. The method of claim 1 , wherein each control affordance of the plurality of control affordances corresponds to a system setting.

12. The method of claim 1 , wherein the first control affordance includes at least a subset of action options for a flashlight application.

13. A display device; one or more input devices; one or more processors; Memory, One or more programs; An electronic device comprising:

13. An electronic device, comprising: 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 the method of any one of claims 1 to 12.

14. 13. A computer program comprising instructions which, when executed by an electronic device comprising a display device and one or more input devices, cause the electronic device to perform the method of any one of claims 1 to 12.

Citation Information

Patent Citations

  • Electronic device and method for implementing a user interface

    JP2011530101A

  • Terminal and method for setting menu environments in the terminal

    US20130339909A1

  • Input unit, method for controlling same, and electronic device provided with input unit

    WO2010032598A1