Device, method and medium for manipulating user interface objects

Abstract

The present application relates to devices, methods, and media for manipulating user interface objects. According to some embodiments, a method includes, at an electronic device having a display and a touch-sensitive surface: simultaneously displaying a background user interface and a first version of a notification associated with a first application on the display, wherein the first version of the notification has a first size, the first version of the notification includes a first content, and the first version of the notification is overlaid on the background user interface; while displaying the first version of the notification associated with the first application overlaid on the background user interface, detecting a first input, including detecting a first contact at a position on the touch-sensitive surface corresponding to the first version of the notification; in response to detecting the first input, manipulating the user interface object according to the first input.

Description

[0001] This application is a divisional application of the invention patent application with the application date of August 9, 2016, application number 201680022696.5, and name “Device, method and graphical user interface for manipulating user interface objects using visual and / or tactile feedback”. Technical Field

[0002] This document generally relates to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that detect input for manipulating a user interface. Background Art

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

[0004] Exemplary manipulations 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 a user interface object, as well as associating metadata with one or more user interface objects or otherwise manipulating the user interface. Exemplary user interface objects include digital images, videos, text, icons, and control elements (such as buttons), as well as other graphics.

[0005] In some cases, a user will need to perform such manipulations on user interface objects in: a file management program (e.g., Finder from Apple Inc. (Cupertino, California)); a messaging application (e.g., Messages from Apple Inc. (Cupertino, California)); an image management application (e.g., Photos from Apple Inc. (Cupertino, California)); a camera application (e.g., Camera from Apple Inc. (Cupertino, California)); a mapping application (e.g., Maps from Apple Inc. (Cupertino, California)); a note-taking application (e.g., Notes from Apple Inc. (Cupertino, California)); a digital content (e.g., video and music) management application (e.g., Music and iTunes from Apple Inc. (Cupertino, California)); a news application (e.g., News from Apple Inc. (Cupertino, California)); a phone application (e.g., Inc. (Cupertino, California)); email applications (e.g., Mail from Apple Inc. (Cupertino, California)); browser applications (e.g., Safari from Apple Inc. (Cupertino, California)); drawing applications; presentation applications (e.g., Keynote from Apple Inc. (Cupertino, California)); word processing applications (e.g., Pages from Apple Inc. (Cupertino, California)); spreadsheet applications (e.g., Numbers from Apple Inc. (Cupertino, California)); reader applications (e.g., iBooks from Apple Inc. (Cupertino, California)); video creation applications (e.g., iMovie from Apple Inc. (Cupertino, California)); and / or geolocation applications (e.g., Find Friends and Find iPhone from Apple Inc. (Cupertino, California)).

[0006] However, existing methods for performing these manipulations are cumbersome and inefficient. Furthermore, existing methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-powered devices. Summary of the Invention

[0007] Therefore, electronic devices need to have faster, more efficient methods and interfaces for manipulating user interfaces. Such methods and interfaces optionally supplement or replace conventional methods for manipulating user interfaces. Such methods and interfaces reduce the number, range, and / or variety of inputs from the user and produce a more efficient human-computer interface. For battery-powered devices, such methods and interfaces save power and increase the time between battery charges.

[0008] The above-mentioned defects and other problems associated with the user interface of an electronic device with a touch-sensitive surface can be reduced or eliminated by means of the disclosed device. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a laptop, tablet computer, or handheld device). In some embodiments, the device is a personal electronic device (e.g., a wearable electronic device, such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also referred to as a "touch screen" or "touch screen display"). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, a program or instruction set stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily by contacting and manipulating the touch-sensitive surface with a stylus and / or finger and using gestures. In some embodiments, these functions optionally include image editing, drawing, presenting, word processing, spreadsheet creation, playing games, making phone calls, video conferencing, sending and receiving emails, instant messaging, exercise support, digital photography, digital video recording, web browsing, digital music playback, notes, and / or digital video playback. Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0009] According to some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact on the touch-sensitive surface. The device simultaneously displays on the display: a background user interface; and a first version of notifications associated with a first application, wherein: the first version of the notification has a first size, the first version of the notification includes first content, and the first version of the notification is overlaid on the background user interface. While displaying the first version of the notification associated with the first application overlaid on the background user interface, the device detects a first portion of a first input, the process including detecting a first contact at a location on the touch-sensitive surface corresponding to the first version of the notification. In response to detecting the first portion of the first input: based on determining that the first portion of the first input satisfies an application launch criterion, wherein the application launch criterion does not require that the characteristic intensity of the first contact on the touch-sensitive surface satisfy a preview intensity threshold to satisfy the application launch criterion, the device initiates a process for launching the first application, wherein launching the first application includes stopping displaying the background user interface and displaying a user interface associated with the first application; and based on determining that the first portion of the first input satisfies a notification extension criterion, wherein the notification extension criterion requires that the characteristic intensity of the first contact on the touch-sensitive surface satisfy a preview intensity threshold to satisfy the notification extension criterion, the device displays a second version of the notification, wherein: the second version of the notification has a second size larger than the first size, the second version of the notification includes extended notification content that is not displayed in the first version of the notification, and the second version of the notification is overlaid on the background user interface.

[0010] According to some embodiments, there is an electronic device comprising: a display unit configured to display a user interface; a touch-sensitive surface unit configured to receive user contact; one or more sensor units configured to detect intensity of contact with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit simultaneously enables display of the following items on the display unit: a background user interface; and a first version of a notification associated with a first application, wherein the first version of the notification has a first size, includes first content, and is overlaid on the background user interface. While displaying the first version of the notification associated with the first application overlaid on the background user interface, the processing unit detects a first portion of a first input, the process comprising detecting a first contact at a location on the touch-sensitive surface unit corresponding to the first version of the notification. In response to detecting the first portion of the first input: based on determining that the first portion of the first input satisfies application launch criteria, wherein 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 to satisfy the application launch criteria, the processing unit initiates a process for launching the first application, wherein launching the first application comprises ceasing to display the background user interface and displaying a user interface associated with the first application. In response to detecting the first portion of the first input: based on determining that the first portion of the first input satisfies a notification expansion standard, wherein the notification expansion standard requires that the characteristic intensity of the first contact on the touch-sensitive surface satisfies a preview intensity threshold to satisfy the notification expansion standard, the processing unit enables display of a second version of the notification, wherein: the second version of the notification has a second size that is larger than the first size, the second version of the notification includes expanded notification content that is not displayed in the first version of the notification, and the second version of the notification is overlaid on the background user interface.

[0011] In accordance with some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contact on the touch-sensitive surface. The method includes: displaying a user interface on a display including multiple application icons corresponding to different applications among multiple applications; while displaying the user interface including the multiple application icons, detecting a first input, which includes detecting a first contact on a touch-sensitive surface at a location corresponding to a first application icon among the multiple application icons, the first application icon being associated with the first application among the multiple applications; in response to detecting the first input: based on determining that the first input satisfies an application launch criterion, wherein the application launch criterion does not require that a characteristic intensity of the first contact on the touch-sensitive surface satisfy a first intensity threshold to satisfy the application launch criterion: launching the first application; and replacing display of the user interface including the multiple application icons with the user interface of the first application; and based on determining that the first input satisfies a menu presentation criterion, wherein the menu presentation criterion requires that a characteristic intensity of the first contact on the touch-sensitive surface satisfy a first intensity threshold to satisfy the menu presentation criterion, simultaneously displaying a contextual content object and a corresponding enable representation associated with the contextual content object, wherein: the contextual content object includes contextually selected content that has been automatically selected from the first application based on the current context of the electronic device; and the corresponding enable representation is configured to add the contextual content object to the user interface including information for the multiple applications when activated.

[0012] 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 one or more user contacts; one or more sensor units configured to detect the intensity of contacts with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: enable display of a user interface on a display unit, the user interface including multiple application icons corresponding to different applications among multiple applications; when enabling display of the user interface including the multiple application icons, detect a first input, which includes detecting a first contact on the touch-sensitive surface unit at a position corresponding to a first application icon among the multiple application icons on the touch-sensitive surface unit, the first application icon being associated with the first application among the multiple applications; in response to detecting the first input: based on determining that the first input satisfies an application launch criterion, wherein the application launch criterion does not require a characteristic intensity of the first contact on the touch-sensitive surface to satisfy a first intensity threshold to satisfy the application launch criterion: launch the first application; and replace the display of the user interface including the multiple application icons with the user interface of the first application; and based on determining that the first input satisfies a menu presentation criterion, wherein the menu presentation criterion requires a characteristic intensity of the first contact on the touch-sensitive surface to satisfy a first intensity threshold to satisfy the menu presentation criterion, simultaneously enable display of a contextual content object and a corresponding enable representation associated with the contextual content object, wherein: the contextual content object includes contextually selected content that has been automatically selected from the first application based on the current context of the electronic device; and the corresponding enable representation is configured to add the contextual content object to the user interface including information for the multiple applications when activated.

[0013] According to some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contacts on the touch-sensitive surface. The method includes: displaying a user interface on the display, the user interface including a plurality of user interface objects corresponding to different applications of a plurality of applications, wherein the plurality of user interface objects include a first user interface object corresponding to a first application that is in the process of being downloaded; while displaying the user interface including the plurality of user interface objects, detecting a first input, which includes detecting a first contact at a location on the touch-sensitive surface corresponding to the first user interface object; and in response to detecting the first input: based on determining that the first user interface object corresponds to an application that has not been fully downloaded and the first input satisfies menu presentation criteria, wherein the menu presentation criteria requires that a characteristic intensity of the contact in the detected input satisfies a first intensity threshold to satisfy the menu presentation criteria, displaying one or more first selectable options that, when activated, are configured to perform an action with respect to downloading the first application.

[0014] 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 contact; one or more sensor units configured to detect intensity of contact with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: enable display of a user interface on the display unit, the user interface including a plurality of user interface objects corresponding to different applications among a plurality of applications, wherein the plurality of user interface objects include a first user interface object corresponding to a first application that is in the process of being downloaded; when enabling display of the user interface including the plurality of user interface objects, detect a first input, which includes detecting a first contact at a location on the touch-sensitive surface unit corresponding to the first user interface object; and in response to detecting the first input: based on determining that the first user interface object corresponds to an application that has not been fully downloaded and the first input satisfies menu presentation criteria, wherein the menu presentation criteria require that a characteristic intensity of the contact in the detected input satisfies a first intensity threshold to satisfy the menu presentation criteria, enable display of one or more first selectable options that, when activated, are configured to perform an action with respect to downloading the first application.

[0015] According to some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contacts on the touch-sensitive surface. The method includes: displaying a user interface on the display, wherein: the user interface includes a folder icon corresponding to an application folder containing a plurality of application icons, the plurality of application icons corresponding to different applications in a plurality of applications, and the plurality of applications including one or more applications with one or more unread notifications; while displaying the user interface including the folder icon, detecting a first input, which includes 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: based on determining that the first input satisfies menu presentation criteria, wherein the menu presentation criteria requires that a characteristic intensity of the contact in the detected input satisfies a first intensity threshold to satisfy the menu presentation criteria, displaying one or more selectable options, the options being configured to, when activated, launch a corresponding application in the plurality of applications in the application folder that has unread notifications.

[0016] 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 contact; one or more sensor units configured to detect intensity of contact with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: enable display of a user interface on the display unit, wherein: the user interface includes a folder icon corresponding to an application folder including a plurality of application icons, the plurality of application icons corresponding to different applications from a plurality of applications, and the plurality of applications including one or more applications with one or more unread notifications; upon enabling display of the user interface including the folder icon, detect a first input, which includes 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: based on determining that the first input satisfies a menu presentation criterion, wherein the menu presentation criterion requires that a characteristic intensity of the contact in the detected input satisfies a first intensity threshold to satisfy the menu presentation criterion, enable display of one or more selectable options, wherein the options are configured to, when activated, launch a corresponding application from the plurality of applications in the application folder with the unread notifications.

[0017] According to some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contact with the touch-sensitive surface. The method includes: displaying a control user interface including a plurality of control enable representations; detecting a first input on the display via contact at a location on the touch-sensitive surface corresponding to a first control enable representation of the plurality of control enable representations; in response to detecting the first input: switching a function of a control corresponding to the first control enable representation based on determining that the first input satisfies a control switching criterion, wherein the control switching criterion does not require a characteristic intensity of the contact to satisfy a first intensity threshold to satisfy the control switching criterion; and displaying one or more modification options for the control corresponding to the first control enable representation based on determining that the first input satisfies an enhanced control criterion, wherein the enhanced control criterion requires a characteristic intensity of the contact to satisfy the first intensity threshold to satisfy the enhanced control criterion; while displaying the one or more modification options for the control corresponding to the first control enable representation, detecting a second input for activating a first modification option of the one or more modification options; and modifying the control corresponding to the first control enable representation based on the activated first modification option.

[0018] 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 contact; one or more sensor units configured to detect the 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 is configured to: enable display of a control user interface including multiple control enable indications; detect a first input on the display unit through contact at a position on the touch-sensitive surface unit corresponding to a first control enable indication among the multiple control enable indications; in response to detecting the first input: switch the function of the control corresponding to the first control enable indication based on determining that the first input satisfies a control switching criterion, wherein the control switching criterion does not require the characteristic intensity of the contact to satisfy a first intensity threshold to satisfy the control switching criterion; and enable display of one or more modification options corresponding to the first control enable indication for control based on determining that the first input satisfies an enhanced control criterion, wherein the enhanced control criterion requires the characteristic intensity of the contact to satisfy a first intensity threshold to satisfy the enhanced control criterion; when enabling display of one or more modification options corresponding to the first control enable indication for control, detect a second input for activating a first modification option among the one or more modification options; and modify the control corresponding to the first control enable indication based on the activated first modification option.

[0019] According to some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contact with the touch-sensitive surface. The method includes: displaying a user interface including: an editable content area having a plurality of characters and a content deletion control; detecting a deletion input, which includes detecting a contact at a location on the touch-sensitive surface corresponding to the content deletion control on the display; and in response to detecting the deletion input, deleting content in the editable content area based on a duration and a characteristic intensity of the contact, including: deleting the content in the editable content area by sequentially deleting a plurality of sub-units of content of a first type of sub-units of content at a rate that does not vary based on the characteristic intensity of the contact based on determining that the contact is maintained for a first time period without the characteristic intensity of the contact increasing above a first intensity threshold; deleting the content in the editable content area by sequentially deleting a plurality of sub-units of content of a second type of sub-units of content at a rate that does not vary based on the characteristic intensity of the contact based on determining that the contact is maintained for a second time period longer than the first time period without the characteristic intensity of the contact increasing above the first intensity threshold; and deleting the content in the programmable content area by sequentially deleting a plurality of sub-units of content at a rate that varies based on the characteristic intensity of the contact based on determining that the characteristic intensity of the contact increases above the first intensity threshold.

[0020] 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 user contact; one or more sensor units configured to detect the intensity of contact with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: enable display of a user interface comprising: an editable content area having a plurality of characters, and a content deletion control; detect a deletion input comprising detecting a contact at a location on the touch-sensitive surface unit corresponding to the content deletion control on the display unit; in response to detecting the deletion input, delete content in the editable content area based on a duration and a characteristic intensity of the contact, comprising: deleting the content in the editable content area by sequentially deleting a plurality of sub-unit contents of a first type of sub-unit content at a rate that does not vary based on the characteristic intensity of the contact based on determining that the contact is maintained for a first time period without the characteristic intensity of the contact increasing to above a first intensity threshold; deleting the content in the editable content area by sequentially deleting a plurality of sub-unit contents of a second type of sub-unit content at a rate that does not vary based on the characteristic intensity of the contact based on determining that the contact is maintained for a second time period longer than the first time period without the characteristic intensity of the contact increasing to above the first intensity threshold; and deleting the content in the programmable content area by sequentially deleting a plurality of sub-unit contents at a rate that varies based on the characteristic intensity of the contact based on determining that the characteristic intensity of the contact increases to above the first intensity threshold.

[0021] In accordance with some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contact with the touch-sensitive surface. The method includes: displaying a message interface on a display, the interface including conversation transcript text and a message input area, wherein the message input area includes an enable indication for sending a message; when the message input area contains message content, detecting a first input by contact at a position in the touch-sensitive surface corresponding to the enable indication for sending the message; determining a characteristic intensity of the contact in the first input; in response to detecting the first input: initiating a process of sending the message content to a remote device based on determining that the first input satisfies a sending criterion, wherein the sending criterion does not require the characteristic intensity of the contact to satisfy a first intensity threshold to satisfy the sending criterion; and based on determining that the contact satisfies a message impact criterion, wherein the message impact criterion requires the characteristic intensity of the contact to satisfy a first intensity threshold to satisfy the message impact criterion, displaying multiple message impact effect options for changing an animation displayed when a message is received at the remote device; while displaying the multiple message impact effect options, detecting a second input by contact for sending the message content according to a selected message impact effect option from the multiple impact effect options; and in response to detecting the second input, initiating a process of sending the message content to the remote device with the first message impact effect option based on determining that the second input is received at a position on the touch-sensitive surface corresponding to the first message impact effect option from the multiple impact effect options.

[0022] 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 contact; one or more sensor units for detecting the intensity of contact with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: enable display of a message interface on the display unit, the interface including conversation transcription text and a message input area, wherein the message input area includes an enable indication for sending a message; when the message input area contains message content, detect a first input made by contact at a position in the touch-sensitive surface unit corresponding to the enable indication for sending a message; determine a characteristic intensity of the contact in the first input; in response to detecting the first input: initiating a process of sending the message content to a remote device based on determining that the first input satisfies a sending criterion, wherein the sending criterion does not require the characteristic intensity of the contact to satisfy a first intensity threshold to satisfy the sending criterion; and initiating a process of sending the message content to a remote device based on determining that the contact satisfies a message impact criterion. The method comprises the steps of: detecting a touch screen touch screen and transmitting the message content to the remote device according to the present invention; detecting a touch screen touch screen and transmitting the message content to the remote device according to the present invention; detecting a touch screen touch screen and transmitting the message content to the remote device according to the present invention; and in response to detecting the second input, initiating a process of sending the message content to the remote device with the first message impact effect option based on determining that the second input is received at a position on the touch-sensitive surface unit corresponding to the first message impact effect option of the multiple impact effect options.

[0023] According to some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contact with the touch-sensitive surface. The method includes: displaying a user interface on the display, the user interface including a plurality of activatable objects, including a first activatable object having a first visual appearance, wherein the device is configured to: for intensity-responsive activatable objects, perform an operation corresponding to the intensity-responsive activatable object based on a characteristic intensity of an input on the touch-sensitive surface corresponding to the intensity-responsive activatable object, such that when the characteristic intensity of a contact providing an input corresponding to the corresponding intensity-responsive activatable object on the touch-sensitive surface satisfies an intensity-based activation criterion, the operation corresponding to the corresponding intensity-responsive activatable object is performed as a result of the characteristic intensity of the contact satisfying the intensity-based activation criterion; and for non-intensity-responsive activatable objects, perform the operation corresponding to the non-intensity-responsive activatable object regardless of whether the input on the touch-sensitive surface corresponding to the non-intensity-responsive activatable object satisfies the intensity-based activation criterion. the touch-sensitive surface, wherein the characteristic intensity of the contact providing the input corresponding to the corresponding non-intensity-responsive activatable object satisfies the intensity-based activation criteria, the operation corresponding to the corresponding non-intensity-responsive activatable object is not performed as a result of the characteristic intensity of the contact satisfying the intensity-based activation criteria; when a user interface is displayed on the display, an input corresponding to a request for selecting a first activatable object from a plurality of activatable objects is detected, wherein the characteristic intensity of the input fails to satisfy the intensity-based activation criteria during the input; and in response to detecting the input: based on determining that the first activatable object is an intensity-responsive activatable object, displaying the first activatable object with a first transformation from its first visual appearance; and based on determining that the first activatable object is a non-intensity-responsive activatable object, displaying the first activatable object without displaying the first transformation.

[0024] 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 the intensity of contact with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: enable display of a user interface on the display unit, the user interface including a plurality of activatable objects including a first activatable object having a first visual appearance, wherein the processing unit is configured to: for an intensity-responsive activatable object, perform an operation corresponding to the intensity-responsive activatable object based on a characteristic intensity of an input corresponding to the intensity-responsive activatable object on the touch-sensitive surface unit, such that when a characteristic intensity of a contact providing an input corresponding to the respective intensity-responsive activatable object on the touch-sensitive surface unit satisfies an intensity-based activation criterion, the operation corresponding to the respective intensity-responsive activatable object is performed as a result of the characteristic intensity of the contact satisfying the intensity-based activation criterion; and for a non-intensity-responsive activatable object, perform the operation corresponding to the non-intensity-responsive activatable object regardless of whether the input corresponding to the non-intensity-responsive activatable object on the touch-sensitive surface unit satisfies the intensity-based activation criterion. An operation corresponding to an activatable object, such that when a characteristic intensity of a contact providing an input corresponding to a corresponding non-intensity-responsive activatable object on a touch-sensitive surface unit satisfies an intensity-based activation criterion, the operation corresponding to the corresponding non-intensity-responsive activatable object is not performed as a result of the characteristic intensity of the contact satisfying the intensity-based activation criterion; when a user interface is displayed on a display unit, an input corresponding to a request for selecting a first activatable object from a plurality of activatable objects is detected, wherein the characteristic intensity of the input fails to satisfy the intensity-based activation criterion during the input; and in response to detecting the input: based on determining that the first activatable object is an intensity-responsive activatable object, display of the first activatable object having a first transformation from its first visual appearance is enabled; and based on determining that the first activatable object is a non-intensity-responsive activatable object, display of the first activatable object is enabled without displaying the first transformation.

[0025] In accordance with some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contact with the touch-sensitive surface: while displaying a user interface, detecting input by contact at a first location on the touch-sensitive surface corresponding to a first activatable user interface object on the display; and in response to detecting the input by contact: based on determining that the first activatable user interface object is intensity-responsive, changing the visual appearance of the first activatable user interface object based on a change in the detected intensity of the contact on the touch-sensitive surface; and based on determining that the first activatable user interface object is non-intensity-responsive, changing the visual appearance of the first activatable user interface object by a predetermined amount.

[0026] 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 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 configured to: when displaying the user interface, detect input made by contact at a first position on the touch-sensitive surface unit corresponding to a first activatable user interface object on the display unit; and in response to detecting the input made by contact: based on determining that the first activatable user interface object is intensity-responsive, change the visual appearance of the first activatable user interface object according to a change in the detected intensity of the contact on the touch-sensitive surface unit; and based on determining that the first activatable user interface object is non-intensity-responsive, change the visual appearance of the first activatable user interface object by a predetermined amount.

[0027] In accordance with some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contact with the touch-sensitive surface. The method includes: displaying a user interface comprising a plurality of activatable user interface objects; while displaying the user interface, detecting a first portion of input made 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 a visual appearance of the first user interface object by applying a first visual transformation to the first user interface object, wherein the first visual transformation corresponds to a first user interface operation; after changing the visual appearance of the first user interface object by applying the first visual transformation to the first user interface object, detecting a second portion of the input; and in response to detecting the second portion of the input: performing the first user interface operation based on a determination that the second portion of the input conforms to the first user interface operation; and in response to determining that the second portion of the input comprises a gradual change in a first parameter indicative of performance of the second user interface operation, dynamically reducing the first visual transformation as the first parameter gradually changes without performing the first user interface operation.

[0028] 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 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 activatable user interface objects; while displaying the user interface, detect a first portion of input made 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 the input: change the visual appearance of the first user interface object by applying a first visual transformation to the first user interface object, wherein the first visual transformation corresponds to a first user interface operation; after changing the visual appearance of the first user interface object by applying the first visual transformation to the first user interface object, detect a second portion of the input; and in response to detecting the second portion of the input: perform the first user interface operation based on determining that the second portion of the input conforms to the first user interface operation; and in response to determining that the second portion of the input includes a gradual change in a first parameter indicating performance of the second user interface operation, dynamically reduce the first visual transformation as the first parameter gradually changes without performing the first user interface operation.

[0029] In accordance with some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting intensity of contact with the touch-sensitive surface. The method includes: displaying a user interface comprising a plurality of activatable user interface objects; while displaying the user interface, detecting a first portion of input by contact at a first location on a touch-sensitive surface corresponding to a first user interface object on the display; in response to detecting the first portion of input by contact: changing a visual appearance of the first user interface object to indicate that an operation corresponding to the first user interface object will be performed in response to detecting lift-off of the contact from the touch-sensitive surface, wherein the change in visual appearance comprises applying a first transformation to the first user interface object; detecting a second portion of input by contact, wherein the second portion of the input follows the first portion of the input; and in response to detecting the second portion of input by contact: based on determining that the second portion of the input comprises a gradual change in a first input parameter and corresponds to a first gesture, changing the visual appearance of the first user interface object by dynamically reducing the first transformation as the first input parameter gradually changes and applying a second transformation corresponding to the first gesture; and based on determining that the second portion of the input comprises a gradual change in a second input parameter and corresponds to a second gesture, changing the visual appearance of the first user interface object by dynamically reducing the first transformation as the second input parameter gradually changes and applying a third transformation corresponding to the second gesture.

[0030] 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 the intensity of contact with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit and the one or more sensor units, the processing unit configured to: enable display of a user interface including multiple activatable user interface objects; while displaying the user interface, detect a first part of input made 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 part of input made by contact: change the visual appearance of the first user interface object to indicate that an action will be performed in response to detecting the lifting of the contact from the touch-sensitive surface. An operation corresponding to a user interface object, wherein the change in visual appearance includes applying a first transformation to a first user interface object; detecting a second portion of input performed by contact, wherein the second portion of the input follows the first portion of the input; and in response to detecting the second portion of the input performed by contact: based on determining that the second portion of the input includes a gradual change in a first input parameter and corresponds to a first gesture, changing the visual appearance of the first user interface object by dynamically reducing the first transformation as the first input parameter gradually changes and applying a second transformation corresponding to the first gesture; and based on determining that the second portion of the input includes a gradual change in a second input parameter and corresponds to a second gesture, changing the visual appearance of the first user interface object by dynamically reducing the first transformation as the second input parameter gradually changes and applying a third transformation corresponding to the second gesture.

[0031] According to some embodiments, a method is performed on an electronic device having a display, a touch-sensitive surface, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface. The method includes: displaying a first user interface that includes a plurality of activatable user interface objects; while displaying the first user interface, detecting input by contact at a first location on the touch-sensitive surface that corresponds to a first activatable user interface object on the display, wherein: the first activatable user interface object is associated with a control function having three or more available values; and a first value of the control function is selected as a current value for the control function; in response to detecting the input by contact: determining that the input satisfies a switching criterion, wherein the switching criterion does not require a characteristic intensity of the contact on the touch-sensitive surface to satisfy a first intensity threshold to satisfy the switching criterion, Switching a control function corresponding to a first activatable user interface object between a first state and a second state; and based on determining that the input satisfies a control adjustment criterion, wherein the control adjustment criterion requires that a characteristic intensity of the contact on the touch-sensitive surface satisfies a first intensity threshold to satisfy the control adjustment criterion, displaying a second user interface, which includes a second activatable user interface object having three or more state options corresponding to three or more available values ​​for the control function; and while displaying the second user interface and continuing to detect contact: detecting movement of the contact across the touch-sensitive surface; stopping detecting the contact; and in response to detecting movement of the contact across the touch-sensitive surface, changing a current value of the control function based on the movement of the contact.

[0032] 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 the intensity of contact with the touch-sensitive surface unit; and a processing unit coupled to the display unit, the touch-sensitive surface unit, and the one or more sensor units. The processing unit is configured to: enable display of a first user interface, which includes multiple activatable user interface objects; when displaying the first user interface, detect input made by contact at a first position on the touch-sensitive surface unit corresponding to a first activatable user interface object on the display unit, wherein: the first activatable user interface object is associated with a control function having three or more available values; and the first value of the control function is selected as the current value for the control function; in response to detecting the input made by contact: based on determining that the input satisfies a switching criterion, wherein the switching criterion does not require the characteristic intensity of the contact on the touch-sensitive surface unit to satisfy a first intensity threshold to satisfy the switching criterion, based on the current value for the control function switching a control function corresponding to a first activatable user interface object between a first state and a second state; and based on determining that the input satisfies a control adjustment criterion, wherein the control adjustment criterion requires that a characteristic intensity of contact on the touch-sensitive surface unit satisfies a first intensity threshold to satisfy the control adjustment criterion, enabling display of a second user interface, which includes a second activatable user interface object having three or more state options corresponding to three or more available values ​​for the control function; and while displaying the second user interface and continuing to detect contact: detecting movement of the contact across the touch-sensitive surface unit; stopping detecting the contact; and in response to detecting movement of the contact across the touch-sensitive surface unit, changing a current value of the control function based on the movement of the contact.

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

[0034] Thus, electronic devices having a display, a touch-sensitive surface, and optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface are provided with faster, more efficient methods and interfaces for providing access to the content of an application and exercising its functionality without first launching the application, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can supplement or replace conventional methods for accessing the content of an application and exercising its functionality. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0036] Figure 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display according to some embodiments.

[0037] Figure 1Bis a block diagram illustrating example components for event processing according to some embodiments.

[0038] Figure 2 A portable multifunction device with a touch screen according to some embodiments is shown.

[0039] Figure 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments.

[0040] Figure 4A An exemplary user interface for an application menu on a portable multifunction device according to some embodiments is shown.

[0041] Figure 4B An exemplary user interface is shown for a multifunction device having a touch-sensitive surface separate from the display according to some embodiments.

[0042] Figures 4C to 4E Examples of dynamic intensity thresholds are shown according to some embodiments.

[0043] Figures 5A1 to 5I9 An exemplary user interface is shown according to some embodiments for interacting with notifications associated with a corresponding application (e.g., to access functionality and / or content subsets of the corresponding application from the notification without first activating the corresponding application).

[0044] Figure 5J1 to Figure 5P2 An exemplary user interface is shown according to some embodiments for displaying contextual content objects (e.g., mini-app objects) associated with a corresponding application (e.g., to provide access to functionality and content subsets of the corresponding application without having to first activate the corresponding application).

[0045] Figure 5Q1 to Figure 5S5 A user interface is shown according to some embodiments for interacting with an application menu that includes an application that is in the process of downloading (e.g., providing an options menu for quickly invoking one of several download-related quick actions relative to the application that is in the process of downloading).

[0046] Figures 5T1 to 5T15 A user interface is shown according to some embodiments for interacting with an application menu that includes an application folder (e.g., selectively providing a menu for quickly launching corresponding applications with unread notifications from a folder containing multiple applications without having to first open the folder).

[0047] Figures 5U1 to 5W5 A user interface is shown for quickly entering a renaming and icon reconfiguration mode for an application folder (e.g., without having to open the folder first) according to some embodiments.

[0048] Figures 6A to 6Y An exemplary user interface for modifying the functionality of a control enable representation is shown according to some embodiments.

[0049] 7A to 7W An exemplary user interface for deleting content is shown according to some embodiments.

[0050] Figures 8A to 8AI An exemplary user interface for detecting input at a messaging interface is shown according to some embodiments.

[0051] Figures 9A1 to 9A25 An exemplary user interface for displaying intensity-responsive and non-intensity-responsive user interface objects is shown according to some embodiments.

[0052] Figures 9A1 to 9B10 An exemplary user interface for displaying intensity-responsive and non-intensity-responsive user interface objects is shown according to some embodiments.

[0053] Figures 9C1 to 9C19 An exemplary user interface is shown for a control settings interface for displaying control functions of a remote device according to some embodiments.

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

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

[0056] 12A to 12F is a flowchart illustrating a method for interacting with an application launch icon (e.g., launching an application or displaying a contextual content object associated with the application based on detected user input) according to some embodiments.

[0057] Figure 13 This is a functional block diagram of an electronic device for interacting with an application launch icon (e.g., launching an application or displaying contextual content objects associated with the application based on detected user input) according to some embodiments.

[0058] 14A to 14Cis a flowchart illustrating a method for interacting with an application menu that includes an application that is in the process of downloading (e.g., presenting menu options relative to a downloading application based on detected user input) according to some embodiments.

[0059] Figure 15 is a functional block diagram of an electronic device for interacting with an application menu that includes an application that is in the process of downloading (e.g., presenting menu options relative to downloading the application based on detected user input) according to some embodiments.

[0060] 16A to 16C is a flowchart illustrating a method for interacting with an application menu that includes an application folder (e.g., selectively presenting application launch options for corresponding applications within the folder (e.g., applications with unread notifications) based on detected user input) according to some embodiments.

[0061] Figure 17 is a functional block diagram of an electronic device for interacting with an application menu that includes an application folder (e.g., selectively presenting application launch options for corresponding applications within the folder (e.g., applications with unread notifications) based on user input) according to some embodiments.

[0062] 18A to 18D is a flowchart illustrating a method for modifying the functionality of a control enable representation according to some embodiments.

[0063] Figure 19 This is a functional block diagram of an electronic device for modifying the functionality of a control enable representation according to some embodiments.

[0064] Figures 20A to 20G is a flow chart illustrating a method of deleting content, according to some embodiments.

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

[0066] Figures 22A to 22G is a flowchart illustrating a method of detecting input at an instant messaging interface according to some embodiments.

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

[0068] Figures 24A1 to 24A3 is a flow diagram illustrating a method of displaying intensity-responsive and non-intensity-responsive user interface objects, according to some embodiments.

[0069] Figures 24B1 to 24B3is a flow diagram illustrating a method of displaying intensity-responsive and non-intensity-responsive user interface objects, according to some embodiments.

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

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

[0072] Figures 27A1 to 27A5 is a flow diagram illustrating a method of displaying intensity-responsive and non-intensity-responsive user interface objects, according to some embodiments.

[0073] Figures 27B1 to 27B3 is a flow diagram illustrating a method of displaying intensity-responsive and non-intensity-responsive user interface objects, according to some embodiments.

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

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

[0076] Figures 30A to 30E is a flowchart illustrating a method of displaying a control settings interface for control functions of a remote device according to some embodiments.

[0077] Figure 31 is a functional block diagram of an electronic device according to some embodiments. DETAILED DESCRIPTION

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

[0079] In some embodiments, in systems where the trackpad or touch screen display is sensitive to a range of intensities of contacts that includes more than one or two specific intensity values ​​(e.g., not just a simple on / off binary intensity determination), the user interface provides a response (e.g., a visual and / or tactile cue) that indicates the intensity of contacts within the range. This provides the user with a continuous response to the force or pressure of the user's contact that provides the user with richer and more intuitive visual and / or tactile feedback. For example, such a continuous force response gives the user the experience of being able to press lightly to preview an operation and / or press deeply to a predefined user interface state corresponding to the operation.

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

[0081] In some embodiments, for a device with a touch-sensitive surface that is sensitive to a range of intensities of contact, the device provides additional functionality by allowing a user to perform complex operations with a single continuous contact.

[0082] In some embodiments, for a device with a touch-sensitive surface that is sensitive to a range of intensities of contact, the device provides additional functionality that supplements conventional functions. For example, the additional functionality provided by intensity-based input (e.g., user interface previews and / or navigation shortcuts provided by light press and / or deep press gestures) is seamlessly integrated with the conventional functionality provided by conventional tap and swipe gestures. The user can continue to use conventional gestures to perform conventional functions (e.g., tapping an application icon on the home screen to launch the corresponding application) without accidentally activating additional functionality. However, the user can also easily discover, understand, and use intensity-based input and its added functionality (e.g., pressing a notification, contextual content object, mini-application object, folder icon, download icon, and / or application icon on a background user interface (e.g., a notification center user interface, a home screen, a desktop widget view, etc.) allows the user to access content, functionality, a subgroup of menu options from the corresponding application without having to first launch the corresponding application and without having to leave the current context (e.g., another application and / or background user interface)).

[0083] This article describes many different methods for manipulating user interfaces. Using one or more of these methods (optionally in combination with one another) helps provide a user interface that intuitively provides additional information and functionality to the user. Using one or more of these methods (optionally in combination with one another) reduces the number, range, and / or type of input from the user and provides a more efficient human-computer interface. This enables users to use devices with touch-sensitive surfaces more quickly and efficiently. For battery-powered devices, these improvements save power and increase the time between battery charges.

[0084] under, Figure 1A to Figure 1B 、 Figure 2 and Figure 3 A description of an exemplary apparatus is provided. Figures 4A to 4B A description of an exemplary user interface on portable multifunction device 100 according to some embodiments is provided. Figures 4C to 4E Examples of dynamic intensity thresholds are shown according to some embodiments.

[0085] Figures 5A1 to 5I9 An exemplary user interface is shown for interacting with notifications associated with a corresponding application (e.g., to access functionality and content subsets of the corresponding application from the notification without first activating the corresponding application) according to some embodiments.

[0086] Figure 5J1 to Figure 5P2 An exemplary user interface is shown according to some embodiments for displaying contextual content objects (e.g., mini-application objects) associated with a corresponding application (e.g., to access functionality and content subsets of the corresponding application from the contextual content objects without having to first activate the corresponding application).

[0087] Figure 5Q1 to Figure 5S5 A user interface is shown according to some embodiments for interacting with an application menu that includes an application that is in the process of downloading (e.g., providing an options menu for quickly invoking one of several download-related quick actions relative to the application that is in the process of downloading).

[0088] Figures 5T1 to 5T15 A user interface is shown according to some embodiments for interacting with an application menu that includes an application folder (e.g., selectively providing a menu for quickly launching corresponding applications with unread notifications from a folder containing multiple applications without having to first open the folder).

[0089] Figures 5U1 to 5W5 A user interface is shown for quickly entering a renaming and reconfiguring mode for an application folder (e.g., without having to open the folder first) according to some embodiments.

[0090] 10A to 10D is a flowchart illustrating a method of interacting with a notification associated with a corresponding application (e.g., to launch the corresponding application or access extended notification content) according to some embodiments. 12A to 12F is a flowchart illustrating a method according to some embodiments of interacting with an application launch icon associated with a corresponding application (e.g., to launch the corresponding application or present contextual content associated with the corresponding application (e.g., in a contextual content object) without first launching the corresponding application). 14A to 14C is a flowchart illustrating a method of interacting with an application menu (e.g., presenting selectable options for actions for a corresponding application (e.g., while the corresponding application is in the process of downloading and / or after the download is complete)) according to some embodiments. 16A to 16C is a flowchart illustrating a method for interacting with an application menu that includes an application folder (e.g., presenting a selectable option for selectively launching an application (e.g., an application with unread notifications) from a folder containing one or more applications) according to some embodiments. Figures 5A1 to 5W5 The user interface in 10A to 10D 、 12A to 12F 、 14A to 14C and 16A to 16C in the process.

[0091] under, Figures 6A to 6Y An exemplary user interface for modifying the functionality of a control affordance is shown. 18A to 18B is a flow chart illustrating a method for modifying the functionality of a control affordance. Figures 6A to 6Y The user interface in 18A to 18D in the process.

[0092] under, 7A to 7W An exemplary user interface for deleting content is shown. Figures 20A to 20G is a flowchart illustrating a method of deleting content. 7A to 7W The user interface in Figures 20A to 20G in the process.

[0093] under, Figures 8A to 8AI An exemplary user interface for detecting input at an instant messaging interface is shown. Figures 22A to 22G is a flow chart illustrating a method of detecting input at an instant messaging interface. Figures 8A to 8AI The user interface in Figures 22A to 22G in the process.

[0094] under, Figures 9A1 to 9A25 An exemplary user interface for displaying intensity-responsive and non-intensity-responsive user interface objects is shown according to some embodiments. Figures 24A1 to 24A3 is a flow diagram illustrating a method of displaying intensity-responsive and non-intensity-responsive user interface objects, according to some embodiments. Figures 24B1 to 24B3 is a flow diagram illustrating a method of displaying intensity-responsive and non-intensity-responsive user interface objects, according to some embodiments. Figures 9A1 to 9A25 The user interface in Figures 24A1 to 24A3 and Figures 24B1 to 24B3 in the process.

[0095] under, Figures 9A1 to 9B10 An exemplary user interface for displaying intensity-responsive and non-intensity-responsive user interface objects is shown according to some embodiments. Figures 27A1 to 27A5 is a flow diagram illustrating a method of displaying intensity-responsive and non-intensity-responsive user interface objects, according to some embodiments. Figures 27B1 to 27B3 is a flow diagram illustrating a method of displaying intensity-responsive and non-intensity-responsive user interface objects, according to some embodiments. Figures 9A1 to 9B10 The user interface in Figures 27A1 to 27A5 and Figures 27B1 to 27B3 in the process.

[0096] Figures 9C1 to 9C19 An exemplary user interface of a control settings interface for displaying control functions of a remote device according to some embodiments is shown. Figures 30A to 30Eis a flowchart illustrating a method of displaying a control settings interface for control functions of a remote device according to some embodiments. Figures 9C1 to 9C19 The user interface in Figures 30A to 30E in the process.

[0097] Exemplary devices

[0098] Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. Numerous specific details are shown in the following detailed description to provide a full understanding of the various described embodiments. However, it will be apparent to those skilled in the art that the various described embodiments can be practiced without these specific details. In other cases, well-known methods, processes, components, circuits, and networks are not described in detail so as not to unnecessarily obscure aspects of the embodiments.

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

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

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

[0102] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch, available from Apple Inc. (Cupertino, California). iPod and Device. Other portable electronic devices, such as laptops or tablets with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads), are 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., touch screen displays and / or touch pads).

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

[0104] The device typically supports a variety of applications, such as one or more of the following applications: a note-taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disk editing application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a fitness 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.

[0105] Various applications executed on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or varied for different applications and / or adjusted and / or varied within the corresponding applications. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and clear to the user.

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

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

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

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

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

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

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

[0113] The audio circuit 110, the speaker 111, and the microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electrical signals into sound waves audible to humans. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals into audio data and transmits the audio data to the peripheral device interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripheral device interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., Figure 2 The headset jack provides an interface between the audio circuit 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset with both output (e.g., single or dual ear headphones) and input (e.g., a microphone).

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

[0115] The touch-sensitive display system 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch-sensitive display system 112 and / or sends electrical signals to the touch-sensitive display system 112. The touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some visual outputs or all of the visual outputs correspond to user interface objects. As used herein, the term "indicator" refers to a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to input directed to a graphical user interface object). Examples of user-interactive graphical user interface objects include, but are not limited to, buttons, sliders, icons, selectable menu items, switches, hyperlinks, or other user interface controls.

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

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

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

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

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

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

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

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

[0124] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1A A tactile output generator is shown coupled to the tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices, such as a speaker or other audio component, and / or an electromechanical device that converts energy into linear motion, such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts an electrical signal into a tactile output on the device). The tactile output generator 167 receives tactile feedback generation instructions from the tactile feedback module 133 and generates tactile output on the device 100 that can be felt by the user of the device 100. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112) and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward toward the surface of the device 100) or laterally (e.g., back and forth in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generator sensor is located on the back of the device 100, opposite the touch-sensitive display system 112 located on the front of the device 100.

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

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

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

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

[0129] The contact / motion module 130 optionally detects contact with the touch-sensitive display system 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to the detection of contact (e.g., by a finger or by a stylus), such as determining whether contact has occurred (e.g., detecting a finger press event), determining the strength of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there has been movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has ceased (e.g., detecting a finger lift event or contact break). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of a contact point optionally includes determining a rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single finger contact or stylus contact) or multiple points of simultaneous contact (e.g., "multi-touch" / multi-finger contact). In some embodiments, contact / motion module 130 and display controller 156 detect contact on a touchpad.

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

[0131] In some embodiments, detecting a finger tap gesture relies on the length of time between detecting a finger press event and a finger lift event, but is independent of the intensity of the finger contact between detecting the finger press event and the finger lift event. In some embodiments, a tap gesture is detected based on determining that the length of time between the finger press event and the finger lift event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4, or 0.5 seconds), regardless of whether the intensity of the finger contact during the tap meets a given intensity threshold (greater than a nominal contact detection intensity threshold), such as a light press or deep press intensity threshold. Thus, a finger tap gesture may meet input criteria that are configured to be met even when the characteristic intensity of the contact does not meet a given intensity threshold. For clarity, the finger contact in a tap gesture is generally required to meet a nominal contact detection intensity threshold in order to detect a finger press event, below which the contact cannot be detected. Similar analysis applies to detecting tap gestures by a stylus or other contact. Where the device is configured to detect contact by a finger or stylus that hovers over a touch-sensitive surface, the nominal contact detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch-sensitive surface.

[0132] The same concepts apply in a similar manner to other types of gestures. For example, a swipe gesture, a pinch gesture, a cancel pinch gesture, and / or a long press gesture are optionally detected based on satisfying criteria that are independent of the intensity of the contacts included in the gesture. For example, a swipe gesture is detected based on an amount of movement of one or more contacts; a pinch gesture is detected based on movement of two or more contacts toward each other; a cancel pinch gesture is detected based on movement of two or more contacts away from each other; and a long press gesture is detected based on a duration of contacts on the touch-sensitive surface that have less than a threshold amount of movement. Thus, the statement that the gesture recognition criteria are configured to be satisfied when the contacts in the gesture have an intensity that is less than a corresponding intensity threshold means that the gesture recognition criteria can be satisfied even if the contacts in the gesture do not reach the corresponding intensity threshold. However, it should be understood that this statement does not preclude the gesture recognition criteria from being satisfied when one or more contacts in the gesture reaches or exceeds the corresponding intensity threshold. For example, a tap gesture is configured to be detected when finger down and finger up events are detected within a predefined time period, regardless of whether the contact during the predefined time period is above or below a corresponding intensity threshold, and a swipe gesture is configured to be detected when the contact moves greater than a predefined amount, even if the contact is above the corresponding intensity threshold at the end of the contact movement.

[0133] In some cases, the intensity thresholds, duration thresholds, and movement thresholds for contacts are combined into a variety of different combinations to create heuristics for distinguishing between two or more different gestures for the same input element or region, enabling multiple different interactions with the same input element to provide a richer set of user interactions and responses. The statement that a particular set of gesture recognition criteria is configured to be satisfied when a contact in a gesture has an intensity below a corresponding intensity threshold does not preclude the simultaneous evaluation of other intensity-dependent gesture recognition criteria to identify other gestures with criteria that are satisfied when the gesture includes a contact with an intensity above the corresponding intensity threshold. For example, in some cases, a first gesture recognition criterion for a first gesture (which is configured to be satisfied when the gesture has an intensity below a corresponding intensity threshold) competes with a second gesture recognition criterion for a second gesture (which depends on the gesture reaching the corresponding intensity threshold). In such a competition, if the second gesture recognition criterion for the second gesture is first met, the gesture is optionally not recognized as meeting the first gesture recognition criterion for the first gesture. For example, if the contact reaches the corresponding intensity threshold before the contact moves a predefined amount, a deep press gesture is detected instead of a swipe gesture. In contrast, if the contact moves the predefined amount before the contact reaches the corresponding intensity threshold, a swipe gesture is detected instead of a deep press gesture. Even in such a case, the first gesture recognition criteria for the first gesture is still configured to be satisfied when the contact in the gesture has an intensity below the corresponding intensity because if the contact remains below the corresponding intensity threshold until the gesture ends (e.g., a swipe gesture with an intensity of the contact that does not increase above the corresponding intensity threshold), the gesture would have been recognized as a swipe gesture by the first gesture recognition criteria. Thus, a particular gesture recognition criterion that is configured to be satisfied when the intensity of the contact remains below a corresponding intensity threshold will (A) in some circumstances ignore the intensity of the contact relative to the intensity threshold (e.g., for a tap gesture) and / or (B) in some circumstances still rely on the intensity of the contact relative to the intensity threshold, in the sense that if a set of competing intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognizes the input as corresponding to an intensity-dependent gesture before the particular gesture recognition criterion recognizes the gesture corresponding to the input (e.g., for a long press gesture that is competing with a deep press gesture for recognition), then the particular gesture recognition criterion (e.g., for a long press gesture) will fail to be met.

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

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

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

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

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

[0139] Application 136 optionally includes the following modules (or instruction sets), or a subset or superset thereof:

[0140] ● Contacts module 137 (sometimes called address book or contact list);

[0141] ● Telephone module 138;

[0142] ● Video conferencing module 139;

[0143] ● Email client module 140;

[0144] Instant messaging (IM) module 141;

[0145] ●Fitness support module 142;

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

[0147] Image management module 144;

[0148] ●Browser module 147;

[0149] ●Calendar module 148;

[0150] Widget module 149, which optionally includes one or more of the following: weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5 and other widgets obtained by the user, and user-created widgets 149-6;

[0151] A widget creator module 150 for making user-created widgets 149-6;

[0152] ●Search module 151;

[0153] • Video and music player module 152, which optionally consists of a video player module and a music player module;

[0154] ●Notepad module 153;

[0155] ● Map module 154; and / or

[0156] ●Online video module 155.

[0157] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

[0158] In combination with the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, and the text input module 134, the contacts module 137 includes executable instructions for managing an address book or contact list (e.g., stored in the application internal state 192 of the contacts module 137 in memory 102 or memory 370), including: adding names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses, 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 communications via telephone 138, video conferencing 139, email 140, or IM 141; and so on.

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

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

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

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

[0163] In combination 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 fitness support module 142 includes executable instructions for: creating a workout (e.g., with time, distance, and / or calorie burn goals); communicating with fitness sensors (in sports equipment and smart watches); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting and playing fitness music; and displaying, storing, and transmitting fitness data.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0196] When a corresponding event recognizer 180 determines that a sequence of sub-events does not match any event in event definitions 186, the corresponding event recognizer 180 enters the event not possible, event failed, or event ended state, after which subsequent sub-events of the touch-based gesture are ignored. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

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

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

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

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

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

[0202] It should be understood that the above discussion of event handling for user touches on a touch-sensitive display also applies to other forms of user input utilizing input devices to operate the multifunction device 100, and not all user input is initiated on the touch screen. For example, mouse movement and mouse button presses, optionally in combination with single or multiple keyboard presses or holds; contact movement on a touchpad, such as taps, drags, scrolls, etc.; stylus input; movement of the device; spoken commands; detected eye movements; biometric input; and / or any combination thereof, may be utilized as input corresponding to a sub-event defining an event to be recognized.

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

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

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

[0206] Figure 33 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. The device 300 does not have to be portable. In some embodiments, the device 300 is a laptop, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a gaming system, or a control device (e.g., a home controller or an industrial controller). The device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuits (sometimes called chipsets) that interconnect system components and control communications between system components. The device 300 includes an input / output (I / O) interface 330 having a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above referenced devices). Figure 1A The tactile output generator 167 described above), sensor 359 (e.g., optical sensor, acceleration sensor, proximity sensor, touch sensitive sensor and / or similar sensor as described above) Figure 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 310. In some embodiments, memory 370 stores data related to portable multifunction device 100 ( Figure 1A ), or a subset thereof. In addition, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while portable multifunction device 100( Figure 1A )'s memory 102 optionally does not store these modules.

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

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

[0209] Figure 4A An exemplary user interface for an applications menu on portable multifunction device 100 is shown 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:

[0210] • One or more signal strength indicators 402 of one or more wireless communications (such as cellular signals and Wi-Fi signals);

[0211] ●Time 404;

[0212] Bluetooth indicator 405;

[0213] Battery status indicator 406;

[0214] A tray 408 with common application icons, such as:

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

[0216] o An icon 418 of the email client module 140 labeled "Mail," which optionally includes an indicator 410 of the number of unread emails;

[0217] o An icon 420 labeled "Browser" for the browser module 147; and

[0218] o An icon 422 labeled “iPod” for the video and music player module 152 (also referred to as the iPod (trademark of Apple Inc.) module 152); and

[0219] Icons for other applications, such as:

[0220] o Icon 424 labeled "Messages" of the IM module 141;

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

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

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

[0224] ○ Icon 432 labeled “Online Video” of the online video module 155;

[0225] ○ Icon 434 labeled “Stock Market” of the Stock Market desktop applet 149-2;

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

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

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

[0229] o An icon 442 labeled “Fitness Support” of the fitness support module 142;

[0230] o An icon 444 of the Notes module 153 labeled "Notes"; and

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

[0232] It should be pointed out that Figure 4A The icon labels shown in FIG are merely examples. For example, in some embodiments, icon 422 of video and music player module 152 is labeled "Music" or "Music Player." Other labels are optionally used for various application icons. In some embodiments, the label of a respective application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

[0233] Figure 4B A touch-sensitive surface 451 (eg, a tablet or touchpad 355, Figure 3 ) of a device (e.g., device 300, Figure 3Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 357) for detecting intensity of contacts on touch-sensitive surface 451, and / or one or more tactile output generators 359 for generating tactile output for a user of device 300.

[0234] Figure 4B A touch-sensitive surface 451 (eg, a tablet or touchpad 355, Figure 3 ) of a device (e.g., device 300, Figure 3 Although many of the examples that follow will be given with reference to input on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 453) corresponding to the main axis (for example, Figure 4B According to these embodiments, the device detects contact with the touch-sensitive surface 451 at a location that corresponds to a corresponding location on the display (e.g., Figure 4B 460 and 462 in (e.g., in Figure 4B , 460 corresponds to 468 and 462 corresponds to 470). Thus, on a touch-sensitive surface (e.g., Figure 4B 451) and a display of a multi-function device (e.g. Figure 4B When the user interface 450 in FIG. 1 is separated, the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

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

[0236] As used herein, the term "focus selector" is an input element that indicates the current portion of a user interface that a user is interacting with. In some implementations that include a cursor or other positional marker, the cursor acts as a "focus selector" such that when the cursor rests over a particular user interface element (e.g., a button, window, slider, or other user interface element), the focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, a specific user interface element is adjusted according to the detected input. In the case that a touch screen display (e.g., a touch screen display) that enables direct interaction with user interface elements on the touch screen display is included (e.g., Figure 1A touch-sensitive display system 112 or Figure 4A In some implementations (such as touch screens in a user interface), a contact detected on the touch screen acts as a "focus selector" such that when input (e.g., a press input by a contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted according to the detected input. In some implementations, focus moves from one area of ​​the user interface to another area of ​​the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another); in these implementations, the focus selector moves in accordance with the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the touch screen display) that is controlled by the user to convey the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user intends to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).

[0237] As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact or a stylus contact) on the touch-sensitive surface, or to a surrogate (surrogate) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four different values ​​and more typically includes hundreds of different values ​​(e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some implementations, the force measurements from multiple force sensors are combined (e.g., weighted averaged or summed) to determine an estimated force of the contact. Similarly, the pressure-sensitive tip of the stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in pressure units). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functionality that the user cannot easily access on a smaller device with limited real estate for displaying indications (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).

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

[0239] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted off, before or after contact begins to move, before contact ends, before or after contact is detected to increase in intensity, and / or before or after contact is detected to decrease in intensity). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the intensity of the contact, the mean value of the intensity of the contact, the average value of the intensity of the contact, the value at the top 10% of the intensity of the contact, the half-maximum value of the intensity of the contact, the 90% maximum value of the intensity of the contact, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is the average value 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 the user has performed an operation. 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 whose characteristic intensity does not exceed the first threshold results in a first operation, a contact whose characteristic intensity exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second operation, and a contact whose characteristic intensity exceeds the second threshold results in a third operation. In some embodiments, the comparison between the characteristic intensity and the one or more intensity thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding option or give up performing the corresponding operation), rather than to determine whether to perform the first operation or the second operation.

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

[0241] The user interface diagrams described herein optionally include various intensity diagrams that illustrate the intensity of contacts on the touch-sensitive surface relative to one or more intensity thresholds (e.g., contact detection intensity threshold IT0, light press intensity threshold IT1, and contact detection intensity threshold IT2). L , deep press intensity threshold IT D (For example, at least initially above IT L ) and / or one or more other intensity thresholds (e.g., L Low intensity threshold IT H )). This intensity graph is not typically part of the displayed user interface, but is provided to help explain the graph. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from the operation typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected having a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact detection intensity threshold IT0, contacts below the nominal contact detection intensity threshold are no longer detected), the device will move the focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing the operation associated with the light press intensity threshold or the deep press intensity threshold. Generally speaking, unless otherwise stated, these intensity thresholds are consistent between different groups of user interface figures.

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

[0243] In some embodiments, one or more of the input intensity thresholds and / or corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, application running, rate at which intensity is applied, number of simultaneous inputs, user history, environmental factors (e.g., ambient noise), focus selector position, 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.

[0244] For example, Figure 4C A dynamic intensity threshold 480 is shown that varies over time based in part on the intensity of the touch input 476 over time. The dynamic intensity threshold 480 is the sum of two components, where a first component 474 decays over time after a predefined delay time p1 from when the touch input 476 is initially detected, and a second component 478 tracks the intensity of the touch input 476 over time. The initial high intensity threshold of the first component 474 reduces situations where a "deep press" response is accidentally triggered, while still allowing an immediate "deep press" response if the touch input 476 provides sufficient intensity. The second component 478 reduces the unintentional triggering of a "deep press" response through gradual intensity fluctuations of the touch input. In some embodiments, when the touch input 476 meets the dynamic intensity threshold 480 (e.g., at Figure 4C ), a “deep press” response is triggered.

[0245] Figure 4D Another dynamic intensity threshold 486 (eg, intensity threshold I D ). Figure 4D Two other intensity thresholds are also shown: a first intensity threshold I H and the second intensity threshold I L .exist Figure 4D Although the touch input 484 meets the first intensity threshold I before time p2, H and the second intensity threshold I L , but does not provide any response until the delay time p2 has elapsed at time 482. In addition, Figure 4D In the example, the dynamic intensity threshold 486 decays over time, wherein the decay begins at time 488 (when the trigger is triggered with the second intensity threshold I) after a predefined delay time p1 has elapsed from time 482. L This type of dynamic intensity threshold reduces the amount of time that occurs immediately after triggering with a lower intensity threshold such as the first intensity threshold I H Or the second intensity threshold I L The response associated with the dynamic intensity threshold I D Unexpected triggering of the associated response.

[0246] Figure 4E Yet another dynamic intensity threshold 492 (eg, intensity threshold I D ).exist Figure 4E In the example, after a delay time p2 has elapsed from when the touch input 490 was initially detected, the trigger is triggered with the intensity threshold I L At the same time, the dynamic intensity threshold 492 decays after a predefined delay time p1 has elapsed from when the touch input 490 was initially detected. Thus, the intensity of the touch input 490 is attenuated between the trigger and intensity threshold values ​​I without releasing the touch input 490. L The associated response then decreases and a subsequent increase in the intensity of the touch input 490 can trigger a change in the touch input 490 with respect to the threshold intensity I D The associated response (e.g., at time 494) is performed even when the intensity of touch input 490 is below another intensity threshold, e.g., intensity threshold I L hour.

[0247] The contact characteristic strength is lower than the light press strength threshold IT L The intensity increases to between the light press intensity threshold IT L and deep press intensity threshold IT D The intensity between the two is sometimes referred to as a "light press" input. D The intensity of the deep press increases to above the deep press intensity threshold ITD The intensity of the contact feature increases from an intensity below the contact detection intensity threshold IT0 to an intensity between the contact detection intensity threshold IT0 and the light press intensity threshold IT0. L A decrease in the characteristic intensity of a contact from an intensity above the contact detection intensity threshold IT0 to an intensity below the contact detection intensity threshold IT0 is sometimes referred to as detecting liftoff of the contact from the touch surface. In some embodiments, IT0 is zero. In some embodiments, IT0 is greater than zero. In some illustrations, shaded circles or ellipses are used to represent the intensity of a contact on the touch-sensitive surface. In some illustrations, unshaded circles or ellipses are used to represent corresponding contacts on the touch-sensitive surface without specifying the intensity of the corresponding contacts.

[0248] In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting an increase in the strength of the contact (or multiple contacts) to above a press input strength threshold. In some embodiments, the corresponding operation is performed in response to detecting an increase in the strength of the corresponding contact to above the press input strength threshold (e.g., the corresponding operation is performed on a "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in the strength of the corresponding contact to above the press input strength threshold and a subsequent decrease in the strength of the contact to below the press input strength threshold, and the corresponding operation is performed in response to detecting a subsequent decrease in the strength of the corresponding contact to below the press input strength threshold (e.g., the corresponding operation is performed on an "up stroke" of the corresponding press input).

[0249] In some embodiments, the device employs intensity hysteresis to avoid unintended input, sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold that has a predefined relationship to a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in the intensity of the corresponding contact to above the press input intensity threshold and a subsequent decrease in the intensity of the contact to below a hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases below the hysteresis intensity threshold (e.g., performing the corresponding operation on an "up stroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects that the intensity of the contact increases from an intensity equal to or less than a hysteresis intensity threshold to an intensity equal to or greater than a press input intensity threshold and, optionally, the intensity of the contact subsequently decreases to an intensity equal to or less than the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, depending on the circumstances).

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

[0251] User interface and associated processes

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

[0253] For ease of explanation, some embodiments will be discussed with reference to operations performed on a device having a touch-sensitive display system 112. In such embodiments, the focus selector is optionally: a corresponding finger or stylus contact detected on the touch-sensitive display system 112, a representative point corresponding to a finger or stylus contact (e.g., the centroid of the corresponding contact or a point associated with the corresponding contact), or the centroids of two or more contacts. However, similar operations are optionally performed on a device having a display 450 and a separate touch-sensitive surface 451 in response to detecting a contact on the touch-sensitive surface 451 while displaying the user interface shown in the figure together with the focus selector on the display 450.

[0254] Figures 5A1 to 5I9 An exemplary user interface is shown for interacting with a notification associated with a corresponding application (e.g., to access a subset of functionality and content of the corresponding application from the notification without first activating the corresponding application) in accordance with some embodiments. In accordance with some embodiments, input on a notification launches the corresponding application associated with the notification or causes display of an expanded version of the notification to provide the user with a subset of content and / or functionality from the corresponding application without first launching the application.

[0255] Figures 5A1 to 5A6 Various exemplary user interfaces for presenting notifications above are shown according to some embodiments.

[0256] Figure 5A1 A wake screen user interface 5002 is shown that is displayed when the device 100 is activated from a screen-off state (e.g., a dormant state) to a screen-on state (e.g., a wake state) in unlocked mode (e.g., as indicated by an “unlock” indicator 5004). A number of notifications (e.g., notification 5006 for a calendar invitation, notification 5008 for a new instant message, and notification 5010 for a voicemail message) are displayed on the wake screen user interface 5002. Each notification includes notification content (e.g., an excerpt from a communication, a summary of an event or communication, etc.) and identification information that identifies the corresponding application corresponding to the notification.

[0257] Figure 5A2A wake screen user interface 5012 is shown that is displayed when the 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 lock mode (e.g., as indicated by a “lock” indicator 5014). A number of notifications (e.g., notification 5016 for calendar invitations, notification 5018 for new instant messages, and notification 5020 for voicemail messages) are displayed on the wake screen user interface 5012. Each notification includes notification content (e.g., an excerpt from a communication, a summary of an event or communication, etc.) and identification information that identifies the corresponding application corresponding to the notification. In some embodiments, the device 100 displays a first version of notifications (e.g., notification 5006 or notification 5008) with more notification content when the device is in unlock mode (e.g., notification 5006 or notification 5008). Figure 5A1 ), and displaying a second version of the notification (e.g., notification 5016 or notification 5018) with less notification content when the device is in lock mode (e.g., as shown in Figure 5A2 shown).

[0258] Figure 5A3 Shown in the home screen user interface 5024 (e.g., similar to Figure 4A A notification (e.g., a banner 5022 for a new email message) is displayed above the home screen user interface 400 shown.

[0259] Figure 5A4 Notification screen 5026 (e.g., a notification center user interface) is shown displayed when device 100 is in locked mode (e.g., as indicated by “lock” indicator 5014). A number of notifications are displayed in a vertical stack on notification screen 5026 (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).

[0260] Figure 5A5 5004 ). Notice screen 5036 (e.g., a notification center user interface) is shown displayed when device 100 is in unlocked mode (e.g., as indicated by “unlocked” indicator 5004). A number of notifications are displayed in a vertical stack on notification screen 5036 (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). Each notification includes notification content (e.g., an excerpt from a communication, a summary of an event or communication, etc.) and identification information that identifies the corresponding application corresponding to the notification. In some embodiments, device 100 displays a first version of notifications (e.g., notification 5028, notification 5030, or notification 5034) with less notification content when the device is in locked mode (e.g., as indicated by “unlocked” indicator 5004). Figure 5A4), and displaying a second version of notifications with more notification content (e.g., notification 5038, notification 5040, or notification 5044) when the device is in unlock mode (as shown) Figure 5A5 shown). Figure 5A5 In addition to the text content of the instant message, the notification 5038 for the instant message (displayed when the device is in unlocked mode) also includes a thumbnail 5046 for the image attachment included in the instant message.

[0261] Figure 5A6 A notification (e.g., alert 5048) is shown displayed above an application's user interface (e.g., application user interface 5050). An alert is a type of notification that requests a user to perform an action (e.g., confirm a ride request or cancel a ride request). Alerts are also sometimes used to request a user's immediate attention, such as when a failure has been detected (e.g., a failure to connect to a peripheral device or server) or when a task requested by the user has not been successfully completed (e.g., a failure to send a message).

[0262] Figures 5B1 to 5B4 A process for launching an application from a notification associated with the application (e.g., in response to a tap input on the notification) is shown according to some embodiments.

[0263] Figure 5B1 Notification screen 5026 is shown displaying a number of notifications (e.g., notifications 5028, 5030, 5032, and 5034) while device 100 is in a locked state.

[0264] Figure 5B2 It is shown that a contact (e.g., contact 5052) is detected on notification 5028; and in response to detecting the contact, notification 5028 is selected.

[0265] Figures 5B3 to 5B4 shows that when the characteristic intensity of contact 5052 (as indicated by the "Intensity of Contact" in the intensity meter shown next to device 100 in the figure) does not increase above a predetermined threshold intensity (e.g., prompt intensity threshold IT) before lift-off of the contact is detected H ), device 100 initiates a process for launching an instant messaging application (e.g., a message application) corresponding to notification 5028.

[0266] Figure 5B3 It is shown that upon detecting lift-off of contact 5052 , device 100 momentarily dims notification screen 5026 and displays a verification user interface (eg, passcode user interface 5054 ) over the dimmed notification screen 5026 .

[0267] Figure 5B4Device 100 is shown unlocked upon receiving correct verification information from passcode user interface 5054. In unlocked mode, device 100 launches a messaging application and displays a user interface for the messaging application (e.g., conversation screen 5056). The user interface (e.g., conversation screen 5056) includes the content of the notification (e.g., message text (e.g., the text of message 5062), the sender's name "Alice") and additional content (e.g., one or more previous messages between Alice and the user (e.g., message 5060), and an image corresponding to the image attachment included in message 5062 (e.g., image 5058)).

[0268] Figures 5C1 to 5C6 A process for displaying a second version of a notification with expanded notification content in response to input (e.g., a press input) on a first version of a notification with standard notification content is shown according to some embodiments.

[0269] Figure 5C1 Shown with Figure 5B1 Same notification screen. Figure 5C1 , notification screen 5026 is shown displaying a number of notifications (e.g., notifications 5028, 5030, 5032, and 5034) while device 100 is in a locked state.

[0270] Figure 5C2 A contact (e.g., contact 5064) is shown detected on notification 5028, and in response to detecting the contact, notification 5028 is selected.

[0271] Figure 5C3 and Figure 5C4 It is shown that once the characteristic intensity of contact 5064 increases to above a predetermined threshold intensity (eg, prompt intensity threshold IT H ), device 100 applies dynamic changes to the user interface based on the current value of the feature intensity. For example, when notification 5028 is overlaid on a blurred and dimmed notification screen 5026, device 100 dynamically increases (or decreases) the amount of blur and dimming applied to notification screen 5026 based on the increase (or decrease) in the feature intensity of contact 5064. Figure 5C3 and Figure 5C4 As shown, as the contact strength is in the range IT H and a first higher intensity threshold (eg, a light press intensity threshold IT L ) increases, the amount of blur and dimming applied to notification screen 5026 will correspondingly increase. L ), liftoff of the contact returns the user interface to its original state (e.g., Figure 5C1 status shown).

[0272] Figure 5C5 It is shown that once the characteristic intensity of contact 5064 exceeds the first intensity threshold (e.g., light press intensity threshold IT L ), an expanded version of the notification (e.g., notification 5066) is displayed above the blurred and dimmed notification screen 5026. Additionally, in some embodiments, once the feature intensity has exceeded the first intensity threshold for a first time, the appearance of the notification screen 5026 is maintained (e.g., does not change based on the current feature intensity of contact 5064). Figure 5C5 As shown, the expanded version of the notification (e.g., notification 5066) includes content from the initial displayed version of the notification (e.g., notification 5028) as well as additional functionality (e.g., selectable options for performing actions with respect to the notification or application) and / or content not included in the initial displayed version of the notification. For example, notification 5066 includes a "Reply" button 5068 for launching a "Reply" user interface to compose a reply to the message represented in the notification, and a "Delete" button 5070 for deleting the message represented in the notification. Notification 5066 optionally includes a preview of an image attachment from the message represented in the notification.

[0273] Figure 5C6 The expanded notification (e.g., notification 5066) is shown remaining displayed on the blurred and dimmed notification screen after lift-off of contact 5064 is detected. Another input (e.g., a tap input) subsequently detected on the expanded notification (e.g., notification 5066) outside the area occupied by buttons 5068 and 5070 begins the process for launching the messaging application (e.g., as shown in FIG. Figure 5B3 and 5B4 shown).

[0274] Figures 5D1 to 5E4 A process is shown according to some embodiments in which contact movement beyond a threshold distance cancels the display of an expanded notification.

[0275] Figure 5D1 Shown with Figure 5B1 and Figure 5C1 Same notification screen. Figure 5D1 , notification screen 5026 is shown displaying a number of notifications (e.g., notifications 5028, 5030, 5032, and 5034) while device 100 is in a locked state.

[0276] Figure 5D2 Shown is that a contact (e.g., contact 5072) is detected on notification 5028; and in response to detecting the contact, notification 5028 is selected.

[0277] Figure 5D3 and Figure 5D4It is shown that once the characteristic intensity of contact 5072 increases to above a predetermined threshold intensity (eg, prompt intensity threshold IT H ), device 100 applies dynamic changes to the user interface based on the current value of the characteristic intensity. For example, when notification 5028 is overlaid on a blurred and dimmed notification screen 5026, device 100 dynamically increases (or decreases) the amount of blur and dimming applied to notification screen 5026 based on the increase (or decrease) in the characteristic intensity of contact 5072. Figure 5D3 and Figure 5D4 As shown, as the contact strength is in the range IT H and a first higher intensity threshold (eg, a light press intensity threshold IT L ) increases within the range that the blur and dimming applied to notification screen 5026 increases accordingly. Before the characteristic intensity of contact 5072 crosses the first intensity threshold, lifting off of the contact returns the user interface to its original state (e.g., Figure 5D1 status shown).

[0278] Figure 5D5 5072 crosses the first intensity threshold. When the amount of movement is less than the first movement threshold (e.g., 10 pixels), device 100 continues to dynamically change the amount of blur and dimming applied to notification screen 5026 based on the current value of the characteristic intensity of contact 5072. Figure 5D4 The notification screen is 5026 times darker than the amount of blur and dimming in Figure 5D5 The notification screen 5026 is larger.

[0279] Figure 5D6 It is shown that as soon as the amount of movement made by contact 5072 is greater than the first movement threshold, the device cancels the prompt effect provided according to the strength of the current contact (e.g., blurring and dimming of notification screen 5026) and restores notification screen 5026 to its original clarity and brightness. In addition, device 100 recognizes the gesture provided by contact 5072 as a drag gesture. Therefore, device 100 moves notification 5028 according to the movement of contact 5072 (e.g., dragging notification 5072 to the left through contact 5072). Figure 5D6 As shown, although the intensity of contact 5072 is greater than the first intensity threshold (eg, IT L ), but does not render the expanded version of the notification (e.g. Figure 5C5 The opposite is shown).

[0280] Figure 5D6 It is shown that as contact 5072 continues to move, notification 5028 is dragged further to the left and a quick response action enable representation (e.g., "Delete" enable representation 5074) is revealed from behind notification 5028.

[0281] like Figures 5D6 to 5D7 As shown, once a threshold amount of movement by contact 5072 has been detected, the user interface does not respond to further changes in the characteristic intensity of contact 5072 and / or the characteristic intensity satisfying the first intensity threshold.

[0282] Figure 5D8 It is shown that after the quick-response action affordance (“delete” affordance 5074) has been revealed, the quick-response action affordance and optionally notification 5028, as well as the remainder of notification screen 5026, remain displayed after lift-off of contact 5072 is detected. Selection of “delete” affordance 5074 by another input (e.g., a tap input) causes notification 5028 and / or the message represented in notification 5028 to be deleted.

[0283] Although Figures 5D5 to 5D8 , but movement of contact 5072 in the opposite direction (e.g., from left to right) after dragging notification 5028 and revealing “Delete” affordance 5074 returns notification 5028 to its original position and again hides “Delete” affordance 5074. Figures 5D5 to 5D8 Not shown, but movement of contact 5072 in the opposite direction (e.g., from left to right) that begins while notification 5028 is in its original position drags notification 5072 to the right and reveals a different quick response action enable indicator (e.g., a “flag” enable indicator or a “reply” enable indicator).

[0284] Figures 5E1 to 5E4 Movement of contact 5072 in the vertical direction is shown. Figure 5E1 from Figure 5D3 Continue and Figure 5D4 same.

[0285] exist Figures 5E1 to 5E2 , before the characteristic intensity of contact 5072 crosses the first intensity threshold, movement of contact 5072 in the vertical direction is detected (e.g., as Figure 5E2 When 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 based on the current value of the characteristic intensity of contact 5072.

[0286] Figure 5E3It is shown that as soon as the amount of movement made by contact 5072 is greater than the second movement threshold, the device cancels the prompt effect provided according to the strength of the current contact (e.g., blurring and dimming of notification screen 5026) and restores notification screen 5026 to its original clarity and brightness. In addition, device 100 recognizes the gesture provided by contact 5072 as a scroll gesture. Therefore, device 100 scrolls notification screen 5026 according to the movement of contact 5072 (e.g., scrolling notification 5028 and other notifications in notification screen 5026 upward through contact 5072). Figure 5E3 As shown, although the intensity of contact 5072 is greater than the first intensity threshold (eg, IT L ), but does not render the expanded version of the notification (e.g. Figure 5C5 The opposite is shown).

[0287] like Figures 5E1 to 5E3 As shown, once a threshold amount of movement has been detected, the user interface does not respond to further changes in the characteristic intensity of contact 5072 and / or the characteristic intensity satisfying the first intensity threshold.

[0288] Figure 5E4 It is shown that after notification screen 5026 has been scrolled, notification screen 5026 remains in the scrolled state after lift-off of contact 5072 is detected.

[0289] Although Figures 5E1 to 5E4 Not shown, but movement of contact 5072 in the opposite direction (eg, in a downward direction) after scrolling the notification screen upward scrolls the notification screen downward again.

[0290] Additionally, in some embodiments ( Figures 5E1 to 5E4 In some embodiments (not shown), instead of scrolling the entire notification screen, movement of contact 5072 causes the notification content within scrolling notification 5028 to scroll. Figures 5E1 to 5E4 (not shown), scrolling notification content is prioritized over scrolling notification screen. In other words, movement of contact first scrolls notification content, and if movement of contact continues when there is no more notification content to scroll based on movement of contact, scrolling of notification screen begins.

[0291] In some embodiments ( Figures 5E1 to 5E4 In some embodiments, the contact moves vertically within the notification screen when the initial landing position 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 across the border of the notification screen).

[0292] Although Figures 5D1 to 5E4The examples shown are illustrated using notifications shown while device 100 is in locked mode, but the cancellation of the alert state (e.g., blurring and dimming of the background user interface) and the dragging of the notification and / or scrolling of the background user interface in accordance with movement of the contact also apply to notifications shown while device 100 is in unlocked mode (e.g., notifications including restricted notification content).

[0293] Figures 5F1 to 5F7 A process for displaying a second version of a notification with expanded notification content in response to an input (e.g., a press input) on a first version of a notification with standard notification content is shown in accordance with some embodiments. In contrast to the process shown in Figures FC1 through FC6 , here the device is in unlocked mode and limited functionality and limited notification content are provided in the second version of the notification.

[0294] exist Figure 5F1 , notification screen 5036 displays a number of notifications (e.g., notifications 5038, 5040, 5042, and 5044) when device 100 is in an unlocked state.

[0295] Figure 5F2 Shown is that a contact (e.g., contact 5076) is detected on notification 5038; and in response to detecting the contact, notification 5038 is selected.

[0296] Figure 5F3 It is shown that once the characteristic intensity of contact 5076 increases to above a predetermined threshold intensity (eg, prompt intensity threshold IT H ), device 100 applies dynamic changes to the user interface based on the current value of the characteristic intensity. For example, when notification 5038 is overlaid on the blurred and dimmed notification screen 5036, device 100 dynamically increases (or decreases) the amount of blur and dimming applied to notification screen 5036 based on the increase (or decrease) in the characteristic intensity of contact 5076. As the intensity of the contact changes within the range IT H and a first higher intensity threshold (eg, a light press intensity threshold IT L ) increases within the first intensity threshold, which correspondingly increases the amount of blur and dimming applied to notification screen 5036. Before the characteristic intensity of contact 5076 crosses the first intensity threshold, lifting off of the contact returns the user interface to its original state (e.g., Figure 5F1 status shown).

[0297] Figure 5F4 It is shown that once the characteristic intensity of contact 5076 exceeds the first intensity threshold (e.g., light press intensity threshold IT L), an expanded version of the notification (e.g., notification 5078) is displayed over the blurred and dimmed notification screen 5036. Additionally, in some embodiments, once the feature intensity has exceeded the first intensity threshold for the first time, the appearance of notification screen 5036 is maintained (e.g., does not change based on the current feature intensity of contact 5076).

[0298] like Figure 5F4 As shown, the expanded version of the notification (e.g., notification 5078) includes content from the initial display version of the notification (e.g., notification 5038) (e.g., message text (e.g., the text of message 5062), the sender's name "Alice"), as well as additional functionality (e.g., selectable options for performing actions with respect to the notification or application) and / or content not included in the initial display version of the notification. For example, notification 5078 includes a "Reply" button 5082 for launching a "Reply" user interface for composing a reply to the message represented in the notification. Notification 5078 also includes one or more previous messages between Alice and the user (e.g., message 5060), as well as an image (e.g., image 5058) corresponding to thumbnail 5046 included in notification 5028 (image 5058 is an attachment included in message 5062). Notification 5078 also includes a header area 5080 that is distinct from the content area (e.g., the area displaying the conversation log) and the control area (e.g., the area displaying control affordances (e.g., "Reply" affordance 5082)). The header area 5080 includes information identifying the message application (eg, an application icon and an application name) and information identifying the sender of the message (eg, an avatar 5084 of the sender "Alice").

[0299] Although Figures 5F1 to 5F5 Not shown, but the expanded notification (e.g., notification 5078) remains displayed on the blurred and dimmed notification screen after lift-off of contact 5076 is detected. Another input (e.g., a tap input) is subsequently detected on the expanded 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) to launch the messaging application (e.g., Figure 5B4 shown).

[0300] Figures 5F5 to 5F7 It is shown that before lifting off the reply enable indication 5082, a second press input by the same contact (e.g., contact 5076) activates the reply enable indication 5082 and causes the reply user interface to be displayed. Figure 5F5 Contact 5078 is shown moving from its original position to a position on reply enable indication 5082 prior to lift-off. Figure 5F65082, an increase in the characteristic intensity of contact 5078 is detected, and the characteristic intensity exceeds a corresponding intensity threshold (e.g., a light press intensity threshold IT). L ). Figure 5F5 It is also shown that before the characteristic intensity of contact 5076 exceeds the corresponding intensity threshold, the characteristic intensity of contact 5076 is below the corresponding intensity threshold (for example, the characteristic intensity of contact 5076 is below IT during the period when contact 5076 moves from its original position to the position on reply enable indication 5082). L ). When the intensity increase is detected to be above the corresponding intensity threshold, contact 5082 has not moved more than the threshold amount (e.g., is substantially stationary) (in other words, the second press input is detected when contact 5076 is substantially stationary).

[0301] Figure 5F7 It is shown that upon lift-off of contact 5076, reply enable indication 5082 is activated immediately 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 above the 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 entered by the user (e.g., "Oh?").

[0302] Figure 5G1 to Figure 5G3 A tap input detected outside of expanded notification 5078 is shown dismissing notification 5078 (and its abbreviated version - notification 5038 ). Figure 5G1 An expanded notification 5078 is shown overlaid on a blurred and dimmed notification screen 5036, e.g., after contact 5076 is removed from the notification screen 5036. Figure 5F4 The state shown is after lifting off.

[0303] Figure 5G2 It is shown that a new contact 5096 is detected outside the expanded notification 5078. Figure 5G3 It is shown that upon lifting of contact 5096, notification screen 5036 is restored to its original clarity and brightness. In addition, notification 5038 and expanded notification 5078 are dismissed from the user interface and are no longer displayed. Other notifications that have not been dismissed (e.g., notifications 5040, 5042, and 5044) are displayed in the restored notification screen 5036.

[0304] Figures 5H1 to 5H2 Shown in Figure 5G1 Following the illustrated state, a tap input detected within the expanded notification 5078 (eg, a tap input detected within the content area of ​​the expanded notification 5078) launches the messaging application.

[0305] like Figure 5H1 As shown, new contact 5098 is detected within the content area of ​​expanded notification 5078. Figure 5H2 It is shown that upon lift-off of contact 5098, device 100 immediately launches the messaging application, and the user interface of the messaging application (e.g., application user interface 5100) replaces expanded notification 5078 and notification screen 5036 on touch screen display 112. A tap input on the expanded notification launches the messaging application into a user interface in the messaging application that corresponds to the content of the notification (e.g., a user interface that includes a conversation log for messaging communications between the user and sender "Alice"), rather than a default user interface that is displayed when the messaging application is launched by a tap input on the messaging application icon on the home screen (e.g., launching to the last user interface that was shown when the user previously left the messaging application or a user interface that includes indexes of conversations the user had with other users).

[0306] Figures 5I1 to 5I9 Another example is shown in which an expanded notification is presented in response to a press input detected on a notification for a ridesharing application and provides a subset of content and functionality from the ridesharing application without first launching the ridesharing application.

[0307] exist Figure 5I1 , a first version of the notification (e.g., banner 5104) is displayed above a background user interface (e.g., an email inbox user interface 5102 of an email application).

[0308] Figure 5I2 It shows that contact 5106 is detected on the first version of the notification (e.g., banner 5104), and when the characteristic intensity of contact 5106 exceeds the prompt threshold IT H , a diminishing visual effect is applied to the background user interface (e.g., blurring and dimming of the background user interface (e.g., user interface 5102)), while notification 5104 is visually lifted off the background user interface and there is no diminishing visual effect. Figure 5I3 shows that the characteristic intensity of contact 5106 is in the range IT H and IT L The amount of the attenuated visual effect is dynamically changed (e.g., increased (or decreased)) based on changes in the characteristic intensity of contact 5106. By applying the attenuated visual effect, the user is provided with a hint of an alternative way to access the content and functional subset of the application without leaving the current context.

[0309] Figure 5I3 It shows that when the characteristic intensity of contact 5106 exceeds the first intensity threshold IT LWhen the user is prompted to enter the notification, the expanded version of the notification (e.g., expanded notification 5108) is displayed above the reduced background user interface (e.g., application user interface 5102). Figure 5I3 As shown, expanded notification 5108 includes a header portion 5110 that includes information identifying the corresponding application associated with the notification (e.g., an 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 subject of the notification). The notification content shown in the expanded version of the notification includes content that was not displayed in the initial displayed version of the notification (e.g., a map 5114 and additional details about the ride provider were not included in notification 5104).

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

[0311] In some embodiments, the content area 5112 in the expanded notification 5108 is scrollable. Figures 5I5 to 5I6 One or more scrolling inputs (e.g., provided by contacts 5120 and 5126 within the content area and moving upward) are shown causing the content area to scroll upward to reveal additional content and a control area including one or more control enable indications (e.g., control enable indications 5122, 5124, 5128, and 5130).

[0312] Figure 5I7 An update regarding the arrival of the ride is shown received, and a pop-up banner alert 5132 is displayed within the expanded notification 5108. Additionally, a car icon 5116 indicates the driver's current location in the map 5114.

[0313] Figure 5I8 and Figure 5I9 Detection of a tap input (e.g., by contact 5134) on control affordance 5122 for initiating a call to a passenger driver (e.g., as shown in FIG. Figure 5I8 ), and in response to the tap input, device 100 initiates a call to the passenger driver, and expanded notification 5108 displays call user interface 5136 during the call. Once the call is connected, control affordance 5122 changes its appearance to indicate that the call is in progress.

[0314] Although Figures 5I1 to 5I95108 (e.g., outside of any control affordances) launches the rideshare application, and the rideshare application's user interface replaces display of expanded notification 5108 and background user interface 5102. Additionally, a tap input detected outside of expanded notification 5108 dismisses the notification (e.g., no longer displays both notification 5104 and expanded notification 5108) and restores the background user interface (e.g., application user interface 5102) to its original brightness and clarity.

[0315] Figure 5J1 to Figure 5P2 An exemplary user interface is shown for displaying contextual content objects (e.g., mini-application objects) associated with a respective application (e.g., to provide access to functionality and content subsets of the respective application from the contextual content objects without first activating the respective application) in accordance with some embodiments. The contextual content objects are presented concurrently with a menu of selectable options for activating one or more functionality of the respective application. In accordance with some embodiments, the contextual content objects respond to user input for displaying more information or functionality from the respective application without launching the application.

[0316] Figure 5J1 to Figure 5J2 A process for launching an application through a tap input on an application icon in an application menu is shown according to some embodiments.

[0317] exist Figure 5J1 In FIG, a user interface (e.g., home screen 5202) includes an array of application icons representing different 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 the messaging application), and a characteristic intensity of contact 5204 is above a detection threshold intensity IT0 and below a prompt intensity threshold IT1. H , select the application icon.

[0318] Figure 5J2 It is shown that after contact 5204 is lifted, device 100 launches the messaging application and replaces the display of home screen 5202 with the user interface of the messaging application (e.g., user interface 5208 that displays a list of user contacts with whom the user has had previous conversations in the messaging application (e.g., a list of other people with whom the user has had conversations in the messaging application)).

[0319] Figures 5K1 to 5K4 A process is shown in which, instead of a tap input, a press input is detected on a messaging application icon, and the press input causes display of a contextual content object and an options menu instead of launching the messaging application.

[0320] exist Figure 5K1 , home screen 5202 is displayed. A contact (e.g., contact 5206) is detected on an application icon (e.g., application icon 424 associated with a messaging application), and the characteristic intensity of contact 5206 is above the detection threshold intensity IT0 and below the prompt intensity threshold IT0. H , select the application icon.

[0321] Figure 5K2 to Figure 5K3 It is shown that once the characteristic intensity of contact 5206 increases above a predetermined threshold intensity (eg, prompt intensity threshold IT H ), device 100 applies dynamic changes to the user interface based on the current value of the characteristic intensity. For example, when application icon 424 is overlaid on the blurred and dimmed home screen 5202, device 100 dynamically increases (or decreases) the amount of blur and dimming applied to home screen 5202 based on the increase (or decrease) in the characteristic intensity of contact 5206. In addition, a menu disk (e.g., disk 5208) emerges from between application icon 424 and home screen 5202, and the size of the disk changes (e.g., grows or shrinks) based on the change in the characteristic intensity of contact 5206. Figure 5K2 and 5K3 As shown, as the contact strength is in the range IT H and a first higher intensity threshold (eg, a light press intensity threshold IT L ), correspondingly increasing the amount of blur and dimming applied to home screen 5202, and also correspondingly increasing the size of disk 5208. Before the characteristic intensity of contact 5206 crosses the first intensity threshold, lift-off of the contact returns the user interface to its original state (e.g., Figure 5K1 The home screen shown has application icon 424 unselected).

[0322] Figure 5K4 It is shown that once the characteristic intensity of contact 5202 exceeds the first intensity threshold (e.g., light press intensity threshold IT L), a contextual content object associated with the messaging application (e.g., a mini-app object or widget 5210) is displayed above the blurred and dimmed home screen 5202. The contextual content object includes contextually selected content that has been automatically selected based on the current context of the device 100. For example, the mini-app object 5210 is a widget that includes a grid of several people selected based on the number of messages that have been sent between the user and the user's contacts (e.g., the mini-app object 5210 includes avatars or aliases of the four people with whom the user has had the highest number of instant messaging communications in the last week (e.g., avatars 5224, 5226, 5228, and 5230)). In some embodiments, the corresponding avatar or alias also includes a flag (e.g., flags 5232 and 5234) indicating the number of unread instant messaging communications from the person represented by the corresponding avatar or alias. For example, flag 5232 indicates that there are eight unread messages from Isaac, and flag 5234 indicates that there are four unread messages from Miles. When a new message is received at device 100 from the person represented in mini-app object 5210, the flag is updated when mini-app object 5210 is displayed.

[0323] In addition to the contextually selected content, mini-app object 5210 also includes an “Add Widget” affordance (e.g., affordance 5222) for adding mini-app object 5210 to another user interface (e.g., a mini-app object screen or a widget screen) configured to host a number of mini-app objects associated with different applications installed on device 100. In some embodiments, affordance 5222 is only displayed if mini-app object 5210 does not already exist in a user interface (e.g., a mini-app object screen or a widget screen) configured to host a number of mini-app objects associated with different applications installed on device 100.

[0324] In addition, a selectable options menu (e.g., menu 5212) is displayed simultaneously with the contextual content object (e.g., mini-app object 5210). The selectable options menu includes options (e.g., options 5214, 5216, 5218, 5220) that, when activated, are configured to launch the messaging application into the messaging application's corresponding user interface for performing corresponding functions associated with the messaging application. For example, selection of option 5214 causes a new message user interface to be displayed for the user to compose a new message; and selection of options 5214, 5218, and 5220, respectively, causes a conversation interface to be displayed for a messaging conversation between the user and the person represented in the option (e.g., S. Ramanujan, Mom, and G. Hardy, respectively).

[0325] Additionally, in some embodiments, once the feature intensity has exceeded the first intensity threshold for a first time, the appearance of the home screen 5202 is maintained (e.g., does not change based on the current feature intensity of the contact 5206).

[0326] like Figure 5K4 As shown, the contextual content object (e.g., mini-app object 5210) includes content selected from the messaging application based on the context (e.g., the user's avatar, the mini-messaging application icon, the application name) and optionally additional functionality (e.g., avatars 5224, 5226, 5228, and 5230 respond to tap inputs or deep press inputs for performing various actions with respect to mini-app object 5210 and / or the messaging application). For example, tapping avatar 5224 launches the messaging application and displays a conversation user interface for viewing previous messages and composing a reply to a message represented in the conversation user interface.

[0327] Figures 5K5 to 5K7 A process for adding contextual content objects to a user interface configured to display respective contextual content objects associated with different ones of a plurality of applications installed on device 100 is shown.

[0328] Figure 5K5 Contextual content object (e.g., mini-app object 5210) is shown remaining displayed on blurred and dimmed home screen 5202 after lift-off of contact 5206 is detected. Another input (e.g., a tap input by contact 5236) is then detected on an "Add Widget" affordance (e.g., affordance 5222) displayed within (or otherwise displayed concurrently with) the contextual content object (e.g., mini-app object 5206).

[0329] Figure 5K6 5236 is shown, immediately after the lift-off of contact 5236, an animation is presented showing that a contextual content object (e.g., mini-app object 5210) is being added to a user interface configured to display corresponding contextual content objects associated with different applications among the plurality of applications installed on device 100. For example, a mini-app object screen (e.g., mini-app object screen or desktop widget screen 5238) is shown sliding in from the left side of the display and partially covering home screen 5202, and mini-app object 5210 is shown jumping from its original position into a slot in mini-app object screen 5238. Figure 5K6As shown, the mini-app objects screen 5238 already includes two mini-app objects (e.g., a "Next" mini-app object 5240 associated with the calendar application, and a calendar mini-app object 5242 associated with the calendar application).

[0330] Figure 5K7 5238, mini-app objects screen 5238 slides back to the left and disappears. This restores the user interface to the state before activating the "Add Widget" affordance (e.g., Figure 5K4 status shown). Figure 5K7 As shown, once mini-app object 5210 has been added to mini-app object screen 5238, the "Add Widget" affordance is no longer displayed with mini-app object 5210. Instead, an indicator (e.g., the text "Added" or a check mark) is displayed to indicate that mini-app object 5210 has been added to the mini-app object screen. In some embodiments, the indicator (e.g., the text "Added" or the check mark) is displayed only briefly after mini-app object 5210 is added to mini-app object screen 5238. In some embodiments (not shown), when mini-app object 5210 is being added to mini-app object screen 5238 in response to activation of the "Add Widget" affordance, device 100 displays mini-app object screen 5238 including the newly added mini-app object 5238 in place of home screen 5202.

[0331] Figures 5K8 to 5L3 It is shown that different portions of a contextual content object (eg, mini-app object 5210 ) have different responses to a press input (eg, a light press input or a deep press input).

[0332] Figures 5K8 to 5K10 Detection of a light press input on a first portion of mini-app object 5210 (eg, by a touch input having a pressure above a light press intensity threshold IT) is shown. L of the characteristic intensity of contact 5248), thereby causing additional information of the first type to be displayed.

[0333] Figure 5K8 Contact 5248 is shown detected on a portion of mini-app object 5210, outside of any avatar included in mini-app object 5210. Figure 5K95254, 5256, and 5258). These additional avatars / aliases are for people selected based on the number of messages that have been sent between the user and the user's contacts (e.g., mini-app object 5210 now includes additional avatars or aliases (e.g., avatars 5252, 5254, 5256, and 5258) for the four people with whom the user has had the next highest number of instant messaging communications in the last week). Figure 5K10 It is shown that after lift-off of contact 5248, additional avatars and aliases (e.g., avatars 5252, 5254, 5256, and 5258) remain displayed in mini-app object 5210.

[0334] Figures 5L1 to 5L3 Detection of a light press input on the second portion of mini-app object 5210 (eg, by a touch input having a pressure above a light press intensity threshold IT) is shown. L of the characteristic intensity of contact 5260), thereby causing additional information of the second type to be displayed.

[0335] Figure 5L1 Contact 5260 is shown as being detected on a portion of mini-app object 5210 that displays one avatar included in mini-app object 5210 (eg, contact 5260 is detected on avatar 5230 ). Figure 5L2 It is shown that when the characteristic intensity of contact 5260 exceeds a corresponding intensity threshold (e.g., a light press intensity threshold), the last communication (e.g., message 5262) ​​from the person represented by the selected avatar (e.g., avatar 5230) is displayed in the mini-app object 5210. Figure 5L3 It is shown that upon lift-off of contact 5260, the last communication (e.g., message 5262) ​​is removed from mini-app object 5210. The user can press another avatar to view the last communication from the person represented by that avatar. Figure 5L1 Additional avatars are shown also being displayed in response to a press input via contact 5260, but this is optional or not implemented in some embodiments.

[0336] Figures 5L4 to 5L5 A tap input detected outside of the mini-app object 5210 and menu 5212 (e.g., by contact 5264) is shown dismissing the mini-app object 5210 and menu 5212 from the home screen 5202. The home screen 5202 is restored to its original brightness and clarity.

[0337] Figures 5L6 to 5L8A swipe input on home screen 5202 (e.g., by contact 5266 moving from left to right) is shown scrolling home screen 5202 to the right and bringing in mini-app objects screen 5238 from the left. Figure 5L8 It is shown that the mini-app objects screen 5238 now replaces the main screen 5202 and takes up the entire display 112.

[0338] like Figure 5L8 As shown, mini-app objects screen 5238 includes a number of mini-app objects that are each associated with a respective application (e.g., mini-app object 5268 associated with the messaging application, mini-app object 5240 associated with the calendar application, and mini-app object 5242 associated with the calendar application). In some embodiments, each mini-app object includes an affordance (e.g., a "Show More" affordance) for displaying additional information in the mini-app object.

[0339] Figures 5L9 to 5M2 It is shown that different portions of a contextual content object (e.g., mini-app object 5268) have different responses to input (e.g., a tap input).

[0340] Figures 5L9 to 5L10 It is shown that a tap input detected (e.g., by contact 5272) on a first portion of mini-app object 5268 (e.g., a tap input detected on avatar 5230) causes device 100 to launch a messaging application and display a first user interface of the messaging application (e.g., a conversation user interface for a messaging conversation between the user and the person represented by the selected avatar 5230). Figure 5L9 , mini-app object 5268 is displayed in mini-app object screen 5238. Contact 5272 is detected on avatar 5230 in mini-app object 5268. The characteristic intensity of contact 5272 does not increase above the light press intensity threshold IT L . Figure 5L10 It is shown that after lifting of contact 5272, device 100 launches the messaging application and replaces mini-app object screen 5238 with a conversation user interface of the messaging application (e.g., conversation user interface 5274). 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 input field for composing a message to the person represented by the selected avatar.

[0341] Figure 5M1 to Figure 5M2 It is shown that a tap input detected on a second portion of mini-app object 5268 (e.g., by contact 5284) (e.g., a tap input detected on a header portion) causes device 100 to launch a messaging app and display a second user interface of the messaging app (e.g., a conversation list user interface for listing messaging conversations that the user has with other users). Figure 5M1 , mini-app object 5268 is displayed in mini-app object screen 5238. Contact 5284 is detected on the header portion of mini-app object 5268. The characteristic intensity of contact 5284 does not increase above the light press intensity threshold IT. L . Figure 5M2 It is shown that after the lift-off of contact 5284, the device 100 launches the messaging application and replaces the mini-app object screen 5238 with the conversation list user interface of the messaging application (e.g., conversation list user interface 5286). The conversation list user interface (e.g., conversation list user interface 5286) displays a list of messaging conversations between the user and the user's other contacts. The user can navigate to the conversation user interface for the corresponding person by selecting the corresponding list item in the conversation list user interface 5286 (e.g., a tap input on the conversation list item for Genevive will cause the device to display Figure 5L10 Session UI shown).

[0342] Figures 5N1 to 5N4 A process is shown in which a deep press input is detected on a contacts application icon and causes a contextual content object and an options menu for the contacts application to be displayed above a home screen.

[0343] exist Figure 5N1 , home screen 5288 is displayed. A contact (e.g., contact 5290) is detected on an application icon (e.g., application icon 445 associated with a contacts application (e.g., also referred to as a contacts application)), and a characteristic intensity of contact 5290 is above a detection threshold intensity IT0 and below a prompt intensity threshold IT1. H , select the application icon.

[0344] Figure 5N2 to Figure 5N3 It is shown that once the characteristic intensity of contact 5290 increases to above a predetermined threshold intensity (eg, prompt intensity threshold IT H), device 100 applies dynamic changes to the user interface based on the current value of the characteristic intensity. For example, when application icon 445 is overlaid on the blurred and dimmed home screen 5288, device 100 dynamically increases (or decreases) the amount of blur and dimming applied to home screen 5288 based on the increase (or decrease) in the characteristic intensity of contact 5290. In addition, a menu disk (e.g., disk 5292) emerges from between application icon 445 and home screen 5288, and the size of the disk changes (e.g., grows or shrinks) based on the change in the characteristic intensity of contact 5290. Figure 5N1 and 5N2 As shown, as the contact strength is in the range IT H and a first higher intensity threshold (eg, a light press intensity threshold IT L ), correspondingly increasing the amount of blur and dimming applied to home screen 5288, and also correspondingly increasing the size of disk 5292. Before the characteristic intensity of contact 5290 crosses the first intensity threshold, lift-off of the contact returns the user interface to its original state (e.g., Figure 5N1 The home screen shown has application icon 445 unselected).

[0345] Figure 5N4 It is shown that once the characteristic intensity of contact 5290 exceeds the first intensity threshold (e.g., light press intensity threshold IT L ), a contextual content object associated with the contacts application (e.g., a mini-app object or widget 5294) is displayed above the blurred and dimmed home screen 5288. The contextual content object includes contextually selected content that has been automatically selected based on the current context of the device 100. For example, the mini-app object 5294 is a widget that includes a grid of several people selected based on the number of communications (e.g., instant messages, email messages, phone calls, VoIP calls, etc.) that have occurred between the user and the user's contacts (e.g., mini-app object 5294 includes avatars or aliases (e.g., avatars 5296, 5298, 5300, and 5302)) with which the user has had the highest number of communications (e.g., various types of communications) in the last week). In some embodiments, the corresponding avatar or alias also includes a flag (e.g., flags 5304a to d) indicating the number of communications that have occurred between the user and the person represented by the corresponding avatar or alias. For example, flag 5304a indicates that there were eight communications between Isaac and the user, and flag 5304c indicates that there were four communications between Miles and the user last week. When a new communication from the person represented in mini-app object 5294 is received at device 100, the flags are updated when mini-app object 5294 is displayed.

[0346] In addition, a selectable options menu (e.g., menu 5309) is displayed simultaneously with the contextual content object (e.g., mini-app object 5294). The selectable options menu includes options that, when activated, are configured to launch the contacts application to the corresponding user interface of the contacts application for performing corresponding functions associated with the contacts application. For example, selection of the option "Create New Contact" causes a new contact user interface to be displayed to allow the user to create a new contact card; selection of the option "Search Contacts" causes a search interface to be displayed; selection of the option "Recent Communications" causes a user interface to be displayed that displays various types of recent communications; and selection of the option "Show My Information" causes the user's own contact card to be displayed.

[0347] like Figure 5N4 As shown, the contextual content object (e.g., mini-app object 5294) includes content selected from the contacts application based on the context (e.g., the user's avatar, the mini contacts application icon, the application name) and optionally additional functionality (e.g., avatars 5296, 5298, 5300, and 5302 respond to tap inputs or press inputs for performing various actions with respect to mini-app object 5294 and / or the contacts application). For example, tapping avatar 5296 launches the contacts application and displays a contact card for viewing contact information of the person represented by the selected avatar (e.g., Isaac) and initiating various types of communications with the person.

[0348] In some embodiments, the placement of the mini-app objects and the options menu is based on the location of the corresponding app icons on the home screen. For example, if there is more space below the app icon, the mini-app object is placed below the app icon, and the options menu is placed below the mini-app object, e.g., Figure 5K4 If there is more space above the app icon, place the mini-app object above the app icon and place the options menu above the mini-app object, for example, as shown in the example above. Figure 5W4 In some embodiments, as shown in the example of Figure 5N4 As shown, when the combined size of the mini-app object and the options menu to be displayed with the app icon is too large for both the space above the app icon and the space below the app icon, the app icon is moved slightly up or down to accommodate the mini-app object and the options menu when a deep press input is detected on the app icon. Figure 5N4As shown, the application icon 445 is moved upward by approximately half the height of the icon, and a mini-application object is displayed below the application icon 445. An options menu 5309 is displayed below the mini-application object 5294.

[0349] Figure 5N5 and Figure 5N6 It is shown that while contact 5290 is maintained on touch screen 112, movement of contact 5290 is detected. As contact 5290 moves from application icon 445 to the option "Show My Info" in options menu 5306, tactile feedback is provided as contact 5290 passes through each option in options menu 5306. Figure 5N6 5290 while the contact is over the option "Show My Info," the user's own contact card is shown being displayed (e.g., in contact card user interface 5311). In some embodiments (not shown), contact card user interface 5311 is overlaid on a portion of a blurred and dimmed version of home screen 5288. In some embodiments, contact card user interface 5311 replaces home screen 5288 and mini-app object 5294 and menu 5309 on the display.

[0350] Figures 5O1 to 5P2 It is shown that different portions of a contextual content object (eg, mini-app object 5240 ) have different responses to a press input (eg, a light press input or a deep press input).

[0351] Figures 5O1 to 5O2 Detection of a light press input on a first portion of mini-app object 5240 (eg, by a touch input having a pressure above a light press intensity threshold IT) is shown. L of the characteristic intensity of contact 5308), thereby causing additional information of the first type to be displayed.

[0352] Figure 5O1 Contact 5308 is shown detected on a portion of mini-app object 5240 that displays details of the next upcoming calendar event. Mini-app object 5240 is displayed in mini-app object screen 5238 along with one or more other mini-app objects associated with other applications.

[0353] Figure 5O2 It is shown that when the characteristic intensity of contact 5308 exceeds a corresponding intensity threshold (e.g., a light press intensity threshold), mini-app object 5240 is expanded (e.g., shown as expanded mini-app object 5310) and displays additional details about the next upcoming calendar event. Figure 5O2As shown, a map (e.g., map 5312) is displayed in addition to the text details of the event. In addition, selectable options (e.g., selectable options 5314, 5216, 5318, and 5320) for activating additional functionality of the calendar application are also displayed in the extended mini-app object 5310 (e.g., option 5314 is for getting directions to the location of the event, option 5316 is for stopping the alarm for the event, option 5318 is for displaying an instant messaging interface for sending messages to the invitees of the event, and option 5320 is for deleting the event). In some embodiments, these functions are activated from the mini-app object without launching the calendar application. In some embodiments, activating an option in the options menu causes the calendar application to be launched, and after the calendar application is launched, the user interface in the calendar application corresponding to the selected option is displayed as the initial user interface. As shown Figure 5O2 As shown, expanded mini-app object 5312 is overlaid on a blurred and dimmed version of mini-app screen 5238. In some embodiments, expanded mini-app object 5312 is displayed within mini-app object screen 5238 and replaces mini-app object 5240. In some embodiments, when lift-off of contact 5308 is detected, expanded mini-app object 5310 is dismissed and the mini-app object screen is restored (e.g., restored to the Figure 5O1 ). In some embodiments, when lift-off of contact 5308 is detected, expanded mini-app object 5310 remains overlaid on the blurred and dimmed version of mini-app object screen 5238. Another input (e.g., detecting a tap outside of expanded mini-app object 5310 or a tap on the “close” affordance displayed within expanded mini-app object 5310) can dismiss expanded mini-app object 5310 and restore mini-app object screen 5238 to its original brightness and clarity. Dismissing expanded mini-app object 5310 does not remove mini-app object 5240 from mini-app object screen 5238.

[0354] Figure 5P1 to Figure 5P2 Detection of a light press input on the second portion of mini-app object 5240 (eg, by a touch input having a pressure greater than a light press intensity threshold IT) is shown. L of the characteristic intensity of contact 5312), thereby causing additional information of the second type to be displayed.

[0355] Figure 5P1 It is shown that contact 5314 is detected on a portion (eg, a blank portion or a header portion) of mini-app object 5240 for displaying details of the next incoming event. Figure 5P2Shown is that when the characteristic intensity of contact 5314 exceeds a corresponding intensity threshold (e.g., a light press intensity threshold), mini-app object 5240 is expanded (e.g., in Figure 5P2 5316, 5318, and 5320). Figure 5P2 As shown, in addition to the event displayed in the expanded mini-application object 5272 (e.g., "Coffee with Jon"), two other events (e.g., "Team Meeting" and "Dinner with Mom") are also displayed. Figure 5P2 As shown, expanded mini-app object 5272 is displayed within mini-app object screen 5238 and replaces mini-app object 5240. In some embodiments, expanded mini-app object 5272 is overlaid on a blurred and dimmed version of mini-app screen 5238. In some embodiments, when lift-off of contact 5314 is detected, expanded mini-app object 5272 is dismissed and the mini-app object screen is restored (e.g., restored to the Figure 5P1 In some embodiments (not shown), when lift-off of contact is detected, expanded mini-app object 5272 remains overlaid on the blurred and dimmed version of mini-app object screen 5238. Another input (e.g., detecting a tap outside of expanded mini-app object 5272 or a tap on a “close” affordance displayed within expanded mini-app object 5272) can dismiss expanded mini-app object 5272 and restore mini-app object screen 5238 to its original brightness and clarity.

[0356] In some embodiments, the mini-app objects shown in the mini-app object screen (e.g., Figure 5P2 5268) and a mini-app object (e.g., a message app icon 424) displayed simultaneously with an app icon (e.g., messaging app icon 424) and an options menu (e.g., menu 5212) displayed above the home screen. Figure 5K4 The mini-app object 5210 for a given application is identical to the mini-app object 5210 for the home screen, except that the portion displaying the "Add Widget" affordance 5222 is identical. According to some embodiments, the mini-app object for a given application has the same functionality and behavior in response to user input detected on the mini-app object (e.g., a tap input or a light press input on various portions of the mini-app object), regardless of whether the mini-app object is displayed in the mini-app object screen or above the home screen.

[0357] In some embodiments, the mini-app object shown above the home screen is a representation of a corresponding mini-app object that has been added to the mini-app object screen. For example, the mini-app object shown above the home screen may provide a subset of the functionality or content shown in the corresponding mini-app object that has been added to the mini-app object screen. For example, in response to the same input on the mini-app object, the amount of additional information displayed in the mini-app object shown above the home screen may be less than the amount of additional information displayed in the corresponding mini-app object that has been added to the mini-app object screen (e.g., due to space constraints on the home screen). In some embodiments, when the mini-app object is displayed in the mini-app object screen, rather than when it is displayed above a dimmed version of the home screen, the mini-app object can scroll to reveal additional content and selectable options for additional functionality from the corresponding application.

[0358] Although Figures 5J1 to 5P2 The examples shown in the examples are shown in only one environment at a time (e.g., in a mini-app object screen or overlaid on a reduced version of a background user interface (e.g., a home screen or another screen showing app icons)), but some or all of the responses and behaviors shown in that environment are optionally also implemented in other environments where mini-app objects are displayed. For the sake of brevity, not all combinations of environments and behaviors are exhaustively enumerated herein.

[0359] Figure 5Q1 to Figure 5S5 A user interface is shown for quickly invoking one of several download-related quick actions relative to an application that is in the process of downloading, according to some embodiments.

[0360] Figure 5Q1 to Figure 5Q6 A process for displaying a menu of options related to downloading an application according to some embodiments is shown.

[0361] Figure 5Q1 A user interface (e.g., home screen 5402) is displayed that includes a plurality of application icons (e.g., application icon 5404 for launching a message application, application icon 5406 for launching a calendar application, etc.) and one or more download icons representing applications in the process of downloading (e.g., download icon 5408 representing a game application in the process of downloading, and download icon 5410 representing a sketch application in the process of downloading). Figure 5Q1 As shown, download icon 5408 indicates that downloading of the gaming application is in progress. Figure 5Q1Also shown is a download icon 5410 indicating that the download of the sketch application has stopped. Other possible states of the download icon include a paused state (e.g., due to lack of authorization or approval from the server) or a waiting state (e.g., due to lack of download bandwidth or unavailability of the server, etc.).

[0362] Figure 5Q2 A contact (eg, contact 5412 ) is shown detected on download icon 5408 . Figure 5Q2 to Figure 5Q4 Indicates that the characteristic intensity of contact 5412 is in the range IT H and IT L changes between (e.g., in the range IT H and IT L 5408 ), device 100 dynamically applies a reduced visual effect (e.g., dynamically applies a blur and dimming effect) on home screen 5402 based on the current value of the feature intensity of contact 5412, including all application icons on home screen 5402 except download icon 5408. Additionally, when the feature intensity of contact 5412 is above the cue intensity threshold, disk 5414 is displayed between download icon 5408 and reduced home screen 5402. The size of disk 5414 dynamically changes (e.g., dynamically increases) based on the change in the feature intensity of contact 5412 (e.g., based on the increase in the feature intensity of contact 5412).

[0363] Figure 5Q5 shows that when the characteristic intensity of contact 5412 increases to above the corresponding intensity threshold (e.g., light press intensity threshold IT L ), the device 100 displays a selectable options menu (e.g., menu 5416) above the reduced home screen 5402 simultaneously with the download icon 5408. In some embodiments, the selectable options menu includes corresponding options related to downloading the application represented by the download icon 5408. Figure 5Q5 As shown, menu 5416 includes option 5418 for prioritizing the download of the game application over one or more other applications (e.g., a sketching application) that are also in the process of downloading. Menu 5416 also includes option 5420 for stopping the download of the game application. Menu 5416 also includes option 5422 for canceling the download of the game application. Menu 5416 also includes option 5424 for sharing the game application with other users.

[0364] Figure 5Q6 It is shown that after the contact 5412 is lifted, the menu 5416 remains displayed above the weakened home screen 5402.

[0365] Figure 5Q7 to Figure 5Q8Selection and activation of option 5424 (e.g., by a tap input on option 5424 (e.g., by contact 5426)) is shown causing device 100 to display a sharing user interface (e.g., sharing card 5428). Figure 5Q8 , a share card 5428 is displayed above the reduced home screen 5402. In some embodiments, menu 5416 ceases to be displayed when share card 5428 is displayed. The share card includes options for sharing the game application via a number of communication methods (e.g., via a wireless connection, instant message, email, reminder, etc.) or in various other ways (e.g., copying a link, sending as a gift, etc.). In some embodiments, selection of option 5424 causes an application store application (e.g., an AppStore application) to be launched and a page showing the game application to be displayed in the initial user interface of the application store application.

[0366] Figure 5Q9 It is shown that after the download of the game application is completed, the download icon 5408 is replaced by an application icon 5408' representing the game application in the home screen 5402. A tap input on the application icon 5408' launches the game application.

[0367] Figure 5Q9 to Figure 5Q11 A press input (eg, via contact 5432 ) on the download icon 5410 is shown causing the device 100 to display a menu 5434 including corresponding options related to downloading the application represented by the download icon 5410 .

[0368] like Figure 5Q10 As shown, when the feature intensity of contact 5432 increases above the prompt intensity threshold, device 100 applies a weakened visual effect on home screen 5402, except on download icon 5410. The amount of the weakened visual effect is dynamically changed based on the current value of the feature intensity of contact 5432. A disk 5434 is displayed between download icon 5410 and the weakened home screen 5402. H and IT L The size of disk 5434 changes dynamically with the characteristic strength of contact 5432 as it varies within a range between.

[0369] Figure 5Q11 54. When the characteristic intensity of contact 5432 increases above the light press intensity threshold, a menu of selectable options (e.g., menu 5434) is presented above the reduced home screen 5402 along with the download icon 5410. Figure 5Q11As shown, menu 5434 includes option 5436 for prioritizing the download of the sketch application over one or more other applications that are also in the process of downloading. Menu 5434 also includes option 5438 for resuming the download of the sketch application. Menu 5434 also includes option 5440 for canceling the download of the sketch application. Menu 5434 also includes option 5442 for sharing the sketch application with other users. In some embodiments, if the download icon represents the only application in the process of downloading on device 100, the option for prioritizing the download (e.g., option 5436) is optionally omitted from menu 5434. In this example, the download of the sketch application had been stopped before the press input was detected, so the option for resuming the download is replaced with the option for stopping the download.

[0370] like Figure 5Q7 and Figure 5Q11 As shown, the options menu presented in response to a press input on a download icon is a universal menu common to all download icons, the only difference being that the option for stopping the download and the option for resuming the download are switched depending on the current status of the download for the specific application icon receiving the press input.

[0371] Figure 5Q12 Movement of contact 5432 to option 5438 (eg, an option to resume downloading) is shown to be detected prior to lift-off of contact 5432. Figure 5Q13 Shown when the lift-off of contact 5432 is detected, option 5438 (e.g., an option for resuming downloading) is activated, and the download of the sketch application is resumed. Additionally, selection and activation of option 5438 (or any other option) causes menu 5434 to be dismissed and home screen 5402 to be restored.

[0372] Figure Q14 shows that when the download of the sketch application is complete, the download icon 5410 is replaced with the application icon 5410'. A tap input on the application icon 5410' launches the sketch application.

[0373] Figures 5Q15 to 5Q17 It is shown that a press input on an application icon for an application causes display of a contextual content object associated with the application and an application-specific menu of selectable options.

[0374] like Figure 5Q15 As shown, a press input (via contact 5446) is detected on the application icon 5408' for the game application. When the characteristic intensity of contact 5446 is within the range IT H and IT LWhen the display is displayed, the device 100 dynamically reduces the home screen 5402 except for the application icons 5408'. A tray 5444 is displayed between the application icons 5408' and the reduced home screen 5402.

[0375] Figure 5Q16 54. When the characteristic intensity of contact 5446 exceeds the light press intensity threshold, a mini-app object 5448 is displayed simultaneously with the app icon 5408' above the reduced home screen 5402. The mini-app object 5448 includes avatars of several of the user's gaming friends. In some embodiments, a tap input on one of these avatars initiates a communication (e.g., instant messaging or communication supported by the gaming application) with the person represented by the avatar. Figure 5Q16 As shown, a menu of selectable options (e.g., menu 5450) for activating various functions in the game application is also presented together with mini-application object 5448. Menu 5450 includes an option 5452 for launching a frequently played game in the game application, an option 5454 for displaying a scoreboard with the highest scores of games played in the game application, an option 5456 for displaying a list of the user's favorite games or frequently played games, and an option 5458 for sharing the game application. In some embodiments, the selectable options displayed in menu 5450 launch the game application when activated and display a user interface corresponding to the function represented by the option as the initial user interface of the game application. In some embodiments, the selectable options displayed in menu 5450 provide access to the functions available within the game application when activated without launching the game application and without leaving the current context (e.g., home screen).

[0376] Figure 5Q17 It is shown that when the lift-off of contact 5446 is detected, mini-app object 5448 and menu 5450 remain displayed above the weakened home screen 5402. Subsequent input (e.g., a tap input, a light press input, and / or a deep press input) can be used to select a menu option or activate an area in the mini-app object to present more information related to the gaming application, present more content from the gaming application, present more functions from the gaming application, or execute one or more functions of the gaming application. A tap input outside of mini-app object 5448, app icon 5408', and menu 5450 dismisses mini-app object 5448 and menu 5450 and restores home screen 5402.

[0377] Figures 5R1 to 5R4100 ).

[0378] Figure 5R2 It is shown that a press input (via contact 5460) is detected on the application icon 5410' for the sketch application. When the characteristic intensity of contact 5460 is within the range IT H and IT L When the display is displayed, the device 100 dynamically reduces the home screen 5402 except for the application icons 5410'. The tray 5408 is displayed between the application icons 5410' and the reduced home screen 5402.

[0379] Figure 5R3 54. When the characteristic intensity of contact 5460 exceeds the light press intensity threshold, a menu of selectable options (e.g., menu 5462) for activating various functions in the sketch application is shown, presented above the weakened home screen 5402 along with the application icon 5410'. Menu 5462 includes an option 5464 for displaying a user interface with a new sketch, an option 5466 for displaying a previous sketch made using the sketch application, an option 5468 for displaying a list of the user's favorite sketches, and an option 5470 for sharing the sketch application. In some embodiments, the selectable options displayed in menu 5462, when activated, launch the sketch application and display a user interface corresponding to the function represented by the option as the initial user interface of the sketch application. In some embodiments, the selectable options displayed in menu 5462, when activated, provide access to functions available within the sketch application without launching the sketch application and without leaving the current context (e.g., the home screen).

[0380] Figure 5R4 It is shown that when lift-off of contact 5460 is detected, menu 5462 remains displayed over the reduced home screen 5402. Subsequent input (e.g., a tap input, a light press input, and / or a deep press input) can be used to select a menu option to perform one or more functions of the sketching application and launch the sketching application into a corresponding user interface associated with the one or more functions.

[0381] Figures 5R5 to 5R6 A tap input outside of application icon 5410 ′ and menu 5462 (eg, through contact 5472 ) is shown dismissing menu 5462 and restoring Home screen 5402 .

[0382] Figure 5R6 to Figure 5R7 A tap input (eg, through contact 5474 ) on an application icon (eg, application icon 5410 ′) displayed in home screen 5402 is shown launching the application represented by the application icon (eg, the sketch application). Figure 5R7 The sketch application is shown launched immediately after contact 5474 is lifted from application icon 5410'. The initial user interface of the sketch application is optionally a user interface for creating a new sketch. In some embodiments, the sketch application is launched and displays a user interface representing the last state of the sketch application when the user last left the sketch application.

[0383] Figures 5S1 to 5S3 A tap input (e.g., through contact 5478) on a download icon (e.g., download icon 5408) that is in a downloading state (e.g., an active download of application data is in progress) is shown to stop the download of the application. Figure 5S3 As shown, the download icon 5408" represents the gaming application in a stopped state.

[0384] Figures 5S3 to 5S5 A tap input (e.g., through contact 5480) on a download icon (e.g., download icon 5410) that is in a stopped state (e.g., active downloading of application data is stopped) is shown to resume the active downloading of application data. Figure 5S5 As shown, download icon 5410" represents the sketch application in an active downloading state.

[0385] Figures 5T1 to 5T15 A user interface is shown for quickly launching a corresponding application with unread notifications from a folder containing multiple applications without having to first open the folder according to some embodiments.

[0386] Figures 5T1 to 5T5 A process is shown for displaying a menu of selectable options in response to a press input detected on an application folder icon.

[0387] like Figure 5T1As shown, home screen 5502 includes a plurality of application icons and one or more application folder icons (e.g., application folder icon 5504). Application folder icon 5504 represents an application folder that includes one or more application icons for launching corresponding applications installed on device 100. In some embodiments, a badge (e.g., badge 5506) is displayed on the application folder icon (e.g., application folder icon 5504) to indicate the total number (e.g., nine) of all unread notifications associated with the applications represented within the application folder (e.g., the "Fav-1" folder).

[0388] Figures 5T2 to 5T4 It is shown that a press input (made by contact 5508) is detected on the application folder icon 5504. When the characteristic intensity of contact 5508 increases above the prompt intensity threshold IT H , the device 100 dynamically reduces the home screen 5502 while providing a tray 5510 (e.g., as shown in FIG. 5 ) between the application folder icons 5504 and the reduced home screen 5502. Figures 5T3 to 5T4 For example, when the characteristic intensity of contact 5508 is within the range IT H and IT L If the characteristic intensity of contact 5508 exceeds the light press intensity threshold IT L If lift-off of contact 5508 is previously detected, device 100 restores home screen 100 to its original state (eg, original clarity and brightness).

[0389] Figure 5T5 shows that when the characteristic intensity of contact 5508 exceeds the light press intensity threshold IT L , the device 100 displays a menu of selectable options (e.g., menu 5512) simultaneously with the application folder icon 5504. Figure 5T5 As shown, menu 5512 includes selectable options for each of launching a corresponding application represented in an application folder (e.g., folder "Fav-1") that has at least one unread notification. Figure 5T5As shown, menu 5512 includes three selectable options for launching three applications with unread notifications, respectively, and an option for renaming the application folder. In the current example, menu 5512 includes a first option (e.g., option 5514) for launching a messaging application in the application folder, and the messaging application has five unread notifications. Menu 5512 also includes a second option (e.g., option 5516) for launching a mail application in the application folder, and the mail application has three unread notifications. Menu 5512 also includes a third option (e.g., option 5518) for launching a music application in the application folder, and the music application has one unread notification. In this example, in addition to the three applications represented in menu 5512, the application folder "Fav-1" represented by folder icon 5504 also includes several other applications. However, because these other applications currently do not have any unread notifications, menu 5512 does not include a corresponding option for launching each of these other applications. In some embodiments, an identifier for identifying the application (e.g., a mini-app icon and application name) is included in each option for launching a corresponding application, along with a count of unread notifications currently associated with the application.

[0390] In this example, the maximum number of application launch options that can be displayed in menu 5512 is four. However, because only three applications in the folder have unread notifications when menu 5512 is displayed, only three application launch options are displayed in menu 5512. In some embodiments, the application launch options for applications with unread notifications are sorted in menu 5512 according to the number of unread notifications associated with each application with unread notifications.

[0391] Figure 5T6 55. It is shown that while menu 5512 is displayed, two more notifications are received by the applications in application folder "Fav-1". In response to receiving the new notifications, device 100 updates marker 5506 to reflect the updated total number of unread notifications for the applications in the application folder. Figure 5T6 As shown, if any of the applications represented by the application launch options in menu 5512 receives additional new notifications, the count of unread notifications displayed in the application launch options will also be updated. Figure 5T6As shown, the messaging application has received one additional new message, and the total number of unread notifications for the messaging application has increased to six. Therefore, option 5514 for launching the messaging application is updated to reflect that the total number of unread notifications for the messaging application is now six. In some embodiments, if an application that is not represented in menu 5512 receives one or more new notifications while menu 5512 is displayed, an application launch option for that application is optionally added to menu 5512 in real time. In some embodiments, to avoid confusing the user and to keep the user interface stable, the application launch option for the application that is not currently represented in menu 5512 is not added to menu 5512 until menu 5512 is closed and displayed again in response to another press input.

[0392] Figures 5T7 to 5T8 55. It is shown that when a tap input (e.g., by contact 5522) is detected outside of menu 5512 and application icons 5504 on the weakened home screen 5502, menu 5512 is dismissed. When contact 5522 is released, home screen 5502 is restored to its original state. Figure 5T8 As shown, the application folder "Fav-1" now has a total of twelve unread notifications.

[0393] Figure 5T9 It is shown that another press input is detected (via contact 5524) on the application folder icon 5504. When the characteristic intensity of contact 5524 increases above the prompt intensity threshold IT H , the device 100 dynamically de-emphasizes the home screen 5502 while providing a tray 5526 between the application folder icons 5504 and the reduced home screen 5502, as shown in FIG. Figure 5T10 to Figure 5T11 For example, when the characteristic intensity of contact 5524 is in the range IT H and IT L If the characteristic intensity of contact 5524 exceeds the light press intensity threshold IT L If lift-off of contact 5524 is previously detected, device 100 restores home screen 100 to its original state (e.g., original clarity and brightness).

[0394] Figure 5T12 shows that when the characteristic intensity of contact 5524 exceeds the light press intensity threshold IT L When the device 100 displays a menu of selectable options (e.g., menu 5528) and application folder icon 5504 at the same time. Figure 5T12As shown, menu 5524 includes selectable options for each of launching a corresponding application represented in an application folder (e.g., folder "Fav-1") that has at least one unread notification. Figure 5T12 As shown, menu 5528 includes four selectable options for respectively launching four applications with unread notifications, and an option for renaming the application folder. In the current example, menu 5528 includes a first option (e.g., option 5530) for launching the App Store application in the application folder, and the App Store application has one unread notification (which is a reminder). Menu 5528 also includes a second option (e.g., option 5532) for launching the messaging application in the application folder, and the messaging application has six unread notifications. Menu 5528 also includes a third option (e.g., option 5534) for launching the mail application in the application folder, and the mail application has three unread notifications. Menu 5528 also includes a fourth option (e.g., option 5536) for launching the music application in the application folder, and the music application has one unread notification. Menu 5528 also includes a rename option (e.g., option 5538) for renaming the folder.

[0395] In the example, in addition to the four applications represented in menu 5528, the application folder "Fav-1" represented by folder icon 5504 also includes several other applications. In fact, one of the other applications also has an unread notification. However, because the maximum number of application launch options that can be included in menu 5528 is four, the application launch option for one of the five applications with unread notifications is not included in menu 5528. In some embodiments, when preferring which application launch options to include in menu 5528, reminders take precedence over regular notifications (for example, because reminders request user action); and for notifications of the same type, the application launch options are sorted based on the total count of unread notifications for each application. In some embodiments, for applications with the same number and type of unread notifications, the application launch options of the applications are sorted according to the timestamp of the most recent notification that has been received for the corresponding application.

[0396] Figure 5T13 It is shown that when lift-off of contact 5524 is detected, menu 5528 remains displayed on the weakened home screen 5502. Figure 5T14 Another tap input is shown detected (e.g., through contact 5540) on one of the application launch options (e.g., option 5532 for launching the messaging application). Figure 5T15It is shown that when contact 5540 is lifted, device 100 launches the messaging application, and the messaging application's user interface (e.g., conversation list user interface 5542) replaces application icon 5504, menu 5528, and reduced home screen 5502 on touch screen 112.

[0397] Figures 5U1 to 5W5 A user interface is shown for quickly entering a renaming and reconfiguring mode for an application folder without having to first open the folder, according to some embodiments.

[0398] Figures 5U1 to 5U7 The general process for editing the folder name and folder contents of an application folder is shown.

[0399] Figure 5U1 Home screen 5502 is shown including a plurality of application icons and one or more application folder icons (e.g., application folder icon 5504). A tap input (e.g., by contact 5544) is detected on application folder icon 5504. When contact 5544 is lifted, application folder 5504 opens to show its contents. Figure 5U2 Folder 5504 is shown in an intermediate state (eg, represented as folder 5504') where it is ejected from its original location and expanded. Figure 5U1 An expanded folder 5546 is shown displayed on the reduced home screen 5502. The expanded folder 5546 includes respective application icons for several applications (e.g., application icons 424, 418, 480, 484, and 438).

[0400] Figures 5U4 to 5U5 55 shows that a long press input (e.g., by contact 5550) is detected on one of the application icons (e.g., application icon 438 for the weather application) in the expanded folder 5546. When contact 5550 satisfies the time threshold for the long press input, the icon reconfiguration mode is activated, as shown in FIG. Figure 5U5 In icon reconfiguration mode, in some embodiments, a delete enable indication (e.g., an "x" symbol) is displayed on each application icon, and activating the delete enable indication on the corresponding application icon deletes the application corresponding to the application icon from device 100. Figure 5U5 Also shown is a folder name 5548 (eg, "Fav-1") for an application folder displayed by expanded folder 5546. Folder name 5548 is initially displayed in a non-editable state.

[0401] Figures 5U6 to 5U7Another tap input is shown detected on folder name 5548 (e.g., by contact 5552). In response to detecting the tap input on folder name 5548, device 100 displays folder name 5546 in an editable state and displays soft keyboard 5555, with expanded folder 5546 and folder name 5552 on the reduced home screen 5502.

[0402] A subsequent contact (e.g., contact 5554) on a corresponding application icon in expanded folder 5546 may drag the corresponding application icon to another location (e.g., to a location outside of expanded folder 5546). In some embodiments, selection of an application icon dismisses soft keyboard 5555 but does not terminate icon reconfiguration mode.

[0403] Figure 5V1 to Figure 5V5 A process is shown for displaying an options menu with an application launch option for an application with unread notifications and an option to rename a folder.

[0404] like Figure 5V1 As shown, the folder "Fav-1" now has a total of three unread notifications (as indicated by marker 5506 on folder icon 5504). Figure 5V2 to Figure 5V4 55. A press input is shown detected on folder icon 5504 (eg, via contact 5556), and in response to the IT H and IT L The characteristic intensity of contact 5556 varies within a range to display intermediate prompt states. Figure 5V5 Shown in response to detecting that the characteristic intensity of contact 5556 exceeds the light press intensity threshold IT L Instead, a menu of selectable options (e.g., menu 5558) is displayed. Figure 5V5 As shown, in this example, only three applications in the folder "Fav-1" currently have unread notifications. Two applications each have one reminder (e.g., the Mail application and the App Store application each have one reminder), and their corresponding application launch options (e.g., options 5560 and 5562) are listed first in menu 5558. The reminder for the Mail application is more recent than the reminder for the App Store application, so the application launch option for the Mail application is listed before the application launch option for the App Store application. One of the three applications (e.g., the Music application) has periodic notifications, and its application launch option is listed last (e.g., option 5564).

[0405] like Figure 5V5 As shown, menu 5558 includes options for renaming the folder (e.g., option 5566). Figure 5V6 to Figure 5V8 Selection of the Rename option is shown to immediately place the application folder into reconfiguration mode with the folder name editable.

[0406] like Figure 5V6 As shown, a tap input (e.g., through contact 5568) is detected on option 5566 for renaming the folder. Figure 5V7 An application folder is shown popping up from the reduced home screen 5502 and expanding when contact 5568 is lifted to reveal its contents. Figure 5V8 55. Expanded folder 5546 is shown displayed on reduced home screen 5502. The expanded folder includes application icons in reconfiguration mode. In some embodiments, icons outside of expanded folder 5546 (e.g., in reduced home screen 5502) are also in reconfiguration mode. In other words, selection of the rename option places the home screen (including all application icons on the home screen) in reconfiguration mode. Application icons in reconfiguration mode can be moved and repositioned on home screen 5502. Figure 5V8 Also shown is that when contact 5568 is lifted, folder name 5552 is displayed in an editable state and soft keyboard 5555 is displayed with expanded folder 5546 on the reduced home screen 5502.

[0407] Figure 5V9 to Figure 5V10 Input received via the soft keyboard 5555 (e.g., via a tap input on a character key (e.g., via contact 5570 on the letter "E" on the keyboard 5555)) is shown editing the folder name 5552. Figure 5V10 As shown in the figure, the folder name changes from "Fav-1" to "Fav-ONE". Figure 5V9 to Figure 5V10 Also shown is that when input is received from the soft keyboard 5555 to edit the folder name, the application icons in the expanded folder 5546 remain in the reconfiguration mode.

[0408] Figure 5V11 55. Device 100 is shown as ceasing to display folder name 5552 in an editable state and ceasing to display soft keyboard 5555 in response to detecting a selection input (e.g., by contact 5572) on a corresponding application icon in expanded folder 5546. The application icons in expanded folder 5546 remain displayed in the reconfiguration mode.

[0409] Figure 5V12 to Figure 5V14An application icon (e.g., application icon 438) is shown being dragged from within expanded folder 5546 to outside of expanded folder 5546 and dropped on home screen 5502. Folder icon 5504 is restored on home screen 5502 (now represented by folder icon 5504'") and the folder no longer contains application icon 438. Following the input for dragging application icon 438 to home screen 5502, the application icons on home screen 5502 remain in icon reconfiguration mode.

[0410] Figures 5W1 to 5W3 Another application icon (e.g., application icon 5408′ for a gaming application) is shown being repositioned in response to a drag input through contact 5574. After application icon 5408′ is repositioned to the bottom of home screen 5502, input for exiting icon reconfiguration mode (e.g., a press input on home button 204) is received. Figure 5W3 The display home screen has been restored and icon reconfiguration mode has terminated.

[0411] Figures 5W4 to 5W5 It is shown that a press input (e.g., through contact 5576) on the game application icon 5408' causes the mini-application object 5448 and menu 5578 to be displayed. Figure 5W5 As shown, because there is more space above the application icon 5408′, the mini application object 5448 is displayed above the application icon 5408′, and the menu 5578 is displayed above the mini application object 5448, which is the same as Figure 5Q17 The opposite is shown.

[0412] Figures 6A to 6Y Figures 1 and 2 illustrate exemplary user interfaces for modifying the functionality of control affordances according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including 18A to 18D Although some of the examples that follow will be given with reference to input on a touch screen display (where the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from the display 450, such as Figure 4B shown.

[0413] In some embodiments, the device is an electronic device having an independent display (e.g., display 450) and an independent touch-sensitive surface (e.g., touch-sensitive surface 451). In some embodiments, the device is a portable multifunction device 100, the display is a touch-sensitive display system 112, and the touch-sensitive surface includes a tactile output generator 167 ( Figure 1AFor ease of explanation, the reference will be discussed with reference to the operation performed on a device having a touch-sensitive display system 112. Figures 6A to 6Y In such embodiments, the focus selector is optionally: a corresponding finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., the centroid of the corresponding contact or a point associated with the corresponding contact), or the centroid of two or more contacts detected on touch-sensitive display system 112. However, optionally, in response to detecting a finger or stylus contact on touch-sensitive surface 451, the focus selector is selected. Figures 6A to 6Y The described contact simultaneously displays on the monitor 450, such as Figures 6A to 6Y The user interface shown performs similar operations on devices with a display 450, a separate touch-sensitive surface 451, and a focus selector.

[0414] Figure 6A An initial user interface 601 (e.g., a lock screen and / or wake screen) according to some embodiments is shown, at which input for displaying a control user interface including multiple control indications is detected. In some embodiments, the control user interface is displayed in response to an input gesture such as a drag gesture (e.g., a drag gesture starting at or near the edge of display 100, such as the lower edge of display 100). For example, contact with touch-sensitive surface 112 is detected at a location indicated by focus selector 602. In some embodiments, indication 603 is displayed at or near the edge of display 100 (e.g., to provide a clue that input received at or near the edge of display 100 will display control user interface 608). The contact moves along the path indicated by arrow 604. In some embodiments, control user interface 608 is gradually revealed as the contact moves along the path indicated by arrow 604. The intensity of the contact feature is indicated by intensity meter 606. As indicated by intensity meter 606, when input for displaying the control user interface is detected, the intensity of the contact feature is higher than the contact detection intensity threshold IT0 and lower than the cue intensity threshold level IT. H , light press intensity threshold IT L and deep compression intensity threshold IT D .

[0415] Figure 6BA control user interface 608 according to some embodiments is shown. The control user interface 608 includes: control power indicators 612 (Airplane Mode), 614 (Wi-Fi), 616 (Bluetooth), 618 (Do Not Disturb Mode), 620 (Rotation Lock), 622 (Flashlight), 624 (Timer), 626 (Night Shift), 628 (Calculator), 630 (Camera), 632 (Apple TV Mirroring), and / or 634 (Brightness). In some embodiments, the control user interface 608 includes a control user interface deactivation indicator 636. When input is detected at the location corresponding to the control user interface deactivation indicator 636, the control user interface 608 stops displaying. In some embodiments, the control user interface 608 is a multi-page control panel user interface, and a page indicator 630 is used to indicate the currently displayed page of the multi-page control panel. In some embodiments, a control user interface is shown that partially or completely covers another user interface (e.g., an initial screen such as a lock screen and / or wake screen, a display including multiple application launch icons, and / or an application user interface) where input for displaying the control user interface is detected. In some implementations, as indicated at 638, the appearance of the user interface partially covered by the controlled user interface 608 is changed. For example, the partially covered user interface may be blurry and / or less bright compared to a previous user interface appearance.

[0416] As indicated by focus selector 640, contact input is detected at the location corresponding to Wi-Fi control indicator 614. In some embodiments, the appearance of one or more control indicators on the control user interface 608 indicates the state of the control indicator. For example, Wi-Fi control indicator 614 is shown in shadow to indicate that Wi-Fi is disabled. As indicated by intensity meter 606, the contact feature intensity is below the prompt pressure intensity threshold IT. H , light press intensity threshold IT L and deep compression intensity threshold IT D Based on the determination that the contact characteristic strength meets the control switching criteria (e.g., the contact characteristic strength is below the prompt press strength threshold IT), H ), corresponding to the Wi-Fi control indication 614, the Wi-Fi control switches from a disabled state to an enabled state.

[0417] Figure 6C This shows that Wi-Fi control has evolved from... Figure 6BThe control user interface 608 after the indicated disabled state is switched to the enabled state. In order to indicate that the Wi-Fi control has been switched to the enabled state, the appearance of the Wi-Fi control enable display 614 is changed (e.g., from a shadowed state to a non-shadowed state) and / or a notification 644 is displayed (e.g., "Wi-Fi: On").

[0418] As indicated by focus selector 642, input via touch is detected at the location corresponding to Wi-Fi control indication 614. The control switching criterion is determined based on whether the contact characteristic strength meets the contact switching criteria (e.g., the contact characteristic strength is below a prompt press strength threshold IT). H ), corresponding to the Wi-Fi control indication 614, the Wi-Fi control switches from an enabled state to a disabled state.

[0419] Figure 6D This shows that Wi-Fi control has evolved from... Figure 6C The control user interface 608 after the indicated disabled state is switched to the enabled state. To indicate that the Wi-Fi control has been switched to the enabled state, the appearance of the Wi-Fi control enable display 614 is changed (e.g., from an unshaded state to a shaded state) and / or a notification 644 is displayed (e.g., "Wi-Fi: Off").

[0420] Figures 6E to 6F The input for displaying modification options for Wi-Fi controls is shown. Figure 6E As indicated by focus selector 646, contact input is detected at the location corresponding to Wi-Fi control indicator 614. As indicated by intensity meter 606, the contact characteristic intensity is higher than the indication intensity threshold level IT. H In some embodiments, based on determining that the feature strength of the input has increased above a prompt strength threshold level IT H ,like Figure 6E As shown, the display (except for the Wi-Fi control indicator 614) is shown as blurred and / or shadowed. In some embodiments, the level of blurring and / or shadowing of the display (except for the Wi-Fi control indicator 614 and the user interface elements corresponding to the Wi-Fi control indicator 614) increases with the intensity of the contact features.

[0421] exist Figure 6F , the contact feature intensity satisfies the enhanced control criteria (e.g., increases above the light press intensity threshold level IT as indicated by the intensity meter 606). LIn response to the input, a modification options menu 648 is displayed, which includes modification options 650 ("Disconnect from home network"), 652 ("Turn off for 1 hour"), 654 ("Turn off until I leave here"), 656 ("Connect to another network"), and 658 ("Wi-Fi settings").

[0422] exist Figure 6G In the process, as indicated by focus selector 658, input via touch is detected at the location corresponding to modification option 654 (“Close until I leave here”).

[0423] exist Figure 6H In response to Figure 6G As shown, Wi-Fi control is (temporarily) disabled, e.g., as indicated by the shaded state of Wi-Fi control affordance 614 and notification 644 (e.g., “Wi-Fi: Off”). Input by contact is detected at a location corresponding to Wi-Fi control affordance 614, as indicated by focus selector 660.

[0424] exist Figure 6I , the contact feature intensity indicated by the focus selector 660 meets the enhanced control criteria (e.g., increases above the light press intensity threshold level IT as indicated by the intensity meter 606). L In response to the input, a modification options menu 662 is displayed, which includes modification options 664 ("Connect to home network"), 666 ("Connect to other network"), 668 ("Turn on until tomorrow"), 670 ("Turn on until I leave here"), and 672 ("Wi-Fi settings"). A tap input (not shown) outside of the modification options menu 662 dismisses the modification options menu 662 from the control user interface 608.

[0425] exist Figure 6J , as indicated by focus selector 674, input by contact is detected at a location corresponding to timer control enable indication 622. The contact feature strength satisfies the control switching criteria (e.g., the contact feature strength is below the prompt press strength threshold IT). H In response to this input, timer application 674 is displayed, as shown. Figure 6K As indicated.

[0426] exist Figure 6L , input by contact is detected at a location corresponding to timer control enable indication 622, as indicated by focus selector 676. The contact feature intensity satisfies the enhanced control criteria (e.g., increases above a light press intensity threshold level IT, as indicated by intensity meter 606). L Based on the determination that the timer associated with timer control indicator 622 is not running, the following is displayed: Figure 6M The user interface shown. Based on the determination that the timer associated with the timer control indicator 622 is running, the following is displayed: Figure 6N The user interface shown.

[0427] Figure 6M 678 for setting a timer according to some embodiments. In some embodiments, the user interface 678 for setting a timer is displayed, partially overlaying the user interface 601. In some embodiments, input at a location corresponding to the adjustable control 680 (e.g., contact indicated by the focus selector 676) sets the duration to the desired timer duration (e.g., by changing the height of the adjustable control 680 by vertically moving the focus selector 676). In some embodiments, as relative to Figure 6L As described, input is detected by contact at a location corresponding to timer control enable indication 622, and input detected at a location corresponding to adjustable control 680 is part of the same continuous contact. In some embodiments, in response to lift-off of the contact detected at a location corresponding to timer control enable indication 622 and / or adjustable control 680, user interface 678 is stopped from being displayed and / or the timer is set to the current value indicated by adjustable control 680. In some embodiments, as with respect to Figure 6L As described, a lifting-off of the contact detected at the position corresponding to the timer control indicator 622 occurs before an input corresponding to the position of the adjustable control 680 is detected. In some embodiments, an input for starting the timer is provided at the start control indicator 682 when the adjustable control 680 has been used to set the desired timer duration.

[0428] Figure 6N is a user interface 682 that indicates the progress of a running timer. For example, the user interface 682 indicates (e.g., using a progress bar 684 and / or displayed text) the time elapsed and / or the time remaining in an ongoing timer. In some embodiments, input at a location corresponding to the progress bar 684 (e.g., by contact as indicated by the focus selector 683) adjusts the time remaining in the timer (e.g., by changing the height of the progress bar 684 by vertically moving the focus selector 683). In some embodiments, input received at the pause control enable indication 686 pauses the timer. In some embodiments, as relative to Figure 6LAs described, input via contact is detected at the position corresponding to the timer control indicator 622, and the input via contact detected at the position corresponding to the progress bar 684 is a portion of the same continuous contact. In some embodiments, in response to the lifting of a contact detected at the position corresponding to the adjustable control 680 and / or the position corresponding to the progress bar 684, the display of the user interface 678 is stopped and / or the timer is set to the adjustment value indicated by the progress bar 684.

[0429] exist Figure 6O As indicated by focus selector 688, input via touch is detected at a location corresponding to camera control indication 630. The intensity of the touch characteristic meets control switching criteria (e.g., as indicated by intensity meter 606, the touch characteristic intensity is below the prompt press intensity threshold level IT). H ). In response to the input, the camera application user interface 690 is displayed.

[0430] Figure 6P The camera application user interface 690 is shown.

[0431] exist Figure 6Q As indicated by focus selector 688, input via contact is detected at a location corresponding to camera control indication 630. The contact characteristic strength meets enhanced control criteria (e.g., as indicated by intensity meter 606, the contact characteristic strength increases to above a light press strength threshold level IT). L In response to input, a menu of modification options 694 is displayed, which includes modification options 696 (“Selfie”), 698 (“Record Video”), 6100 (“Record Slow Motion”), and 6102 (“Take Photo”).

[0432] exist Figure 6R , as indicated by focus selector 688, the contact moves to a position corresponding to modification option 696 ("Selfie"). In response to the input, as indicated by focus selector 688, the contact moves to a position corresponding to modification option 696 ("Selfie"). Figure 6S As instructed, the camera application user interface 690 is displayed in selfie mode.

[0433] Figures 6T to 6U The input is shown, which is used to display one or more action options corresponding to an application icon in a springboard or home screen user interface that includes multiple application icons.

[0434] exist Figure 6T As indicated by focus selector 6106, input is received at the location corresponding to camera application icon 430. This occurs when display-action-option criteria are met (e.g., when the contact feature strength increases above a light press threshold IT). L (conditions that must be met at the time), such as Figure 6UAs shown, action options menu 6108 is displayed, which includes action options 6110 ("selfie"), 6112 ("record video"), 6114 ("record slow motion"), and 6116 ("take photo"). In some embodiments, modification options 696-6102 of camera control affordance 630 include at least a subset of action options 6110-6116 of the action menu corresponding to application icon 430.

[0435] Figures 6V to 6X The input for displaying modification options for flashlight controls is shown. Figure 6V , as indicated by focus selector 6110, an input by contact is detected at a location corresponding to flashlight control enable indication 622. As indicated by intensity meter 606, the contact feature intensity is above the prompt intensity threshold level IT H .

[0436] exist Figure 6W , the contact feature intensity satisfies the enhanced control criteria (e.g., increases above the light press intensity threshold level IT as indicated by the intensity meter 606). L In response to input, a modification options menu 6112 is displayed, which includes modification options 6114 (“High”), 6116 (“Medium”), and 6118 (“Low”) corresponding to high brightness, medium brightness, and low brightness, respectively.

[0437] exist Figure 6X In the middle, the contact indicated by the focus selector 6110 has been moved to the position corresponding to the modification option 6110 (“middle”).

[0438] exist Figure 6Y In response to Figure 6X The inputs shown indicate that the flashlight is turned on at medium brightness, such as in the non-shadow state of the flashlight control indicator 622 and / or as indicated by the light 6120 emitted by the device flashlight.

[0439] 7A to 7W Exemplary user interfaces for deleting content are shown according to some implementation schemes. The user interfaces in these figures are used to illustrate the processes described below, including... Figures 20A to 20G Although some of the following examples will be given with reference to input on a touch screen display (where the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from the display 450, such as Figure 4B shown.

[0440] In some embodiments, the device is an electronic device having a separate display (e.g., display 450) and a separate touch-sensitive surface (e.g., touch-sensitive surface 451). In some embodiments, the device is a portable multi-functional device 100, the display is a touch-sensitive display system 112, and the touch-sensitive surface includes a tactile output generator 167 on the display. Figure 1A For ease of explanation, the reference will be discussed with reference to the operation performed on a device having a touch-sensitive display system 112. 7A to 7W In such embodiments, the focus selector is optionally: a corresponding finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., the centroid of the corresponding contact or a point associated with the corresponding contact), or the centroid of two or more contacts detected on touch-sensitive display system 112. However, optionally, in response to detecting a finger or stylus contact on touch-sensitive surface 451, the focus selector is selected. 7A to 7W The described contact simultaneously displays on the monitor 450, such as 7A to 7W The user interface shown performs similar operations on devices with a display 450, a separate touch-sensitive surface 451, and a focus selector.

[0441] Figure 7A A user interface 702 is shown that includes an editable content area 704 that includes a plurality of characters. The user interface 702 also includes a content deletion control 706. Detecting a deletion input includes detecting a contact 708 at a location on the touch-sensitive surface 112 that corresponds to the content deletion control 708 (as indicated by the focus selector 710). The content deletion control 708 is, for example, a delete key in a keyboard 709. The contact feature strength is indicated by an intensity meter 712. Figure 7A In illustrative examples, as indicated by intensity meter 712, the contact characteristic intensity has increased to above the deep press intensity threshold ITD. Figures 7B to 7C Use Figure 7A Section 714 is used to show character-by-character deletion and word-by-word deletion.

[0442] Figure 7B The case of character-by-character deletion is shown. At a first time T=t1, a first character is deleted from the plurality of characters in the editable content area 704 of the region 714 at a position corresponding to the content insertion indicator 716. At a second time T=t2 later than the first time t1, a second character is deleted from the plurality of characters in the editable content area 704 at a position corresponding to the content insertion indicator 716. At a third time T=t3 later than the second time t2, a third character is deleted from the plurality of characters in the editable content area 704 at a position corresponding to the content insertion indicator 716.

[0443] Figure 7CThe diagram illustrates word-by-word deletion. At a first time T = t1, at the position corresponding to the content insertion indicator 716, the first word is deleted from multiple characters in the editable content area 704 of zone 714. At a second time T = t2, which is later than the first time t1, the second word is deleted from multiple characters in the editable content area 704 at the position corresponding to the content insertion indicator 716. At a third time T = t3, which is later than the second time t2, the third word is deleted from multiple characters in the editable content area 704 at the position corresponding to the content insertion indicator 716.

[0444] 7D to 7I is a diagram showing a heuristic method for determining the intensity of a D (For example, Figure 7A The deep press intensity threshold IT shown by the intensity meter 712 D Content deletion is determined based on the intensity of contact features associated with time thresholds T1 and T2. Time threshold T1 defines a first time period, and time threshold T2 defines a second time period that is longer than the first time period.

[0445] exist Figure 7D In the diagram, 720 indicates the intensity of the contact feature at the location corresponding to the content deletion control 708. Contact is maintained during a first time period T1 and continues during a second time period T2. The contact feature intensity does not increase above the deep press intensity threshold level IT. D Based on determining that contact has been maintained for the first time period T1, content is deleted from the editable content area 704 character by character at a rate that does not vary based on the characteristic strength of the contact (e.g., as Figure 7B Based on determining that contact has been maintained for a second time period T2, content is deleted word by word from the editable content area 704 at a rate that does not vary based on the contact feature strength (e.g., as shown). Figure 7C (As shown).

[0446] exist Figure 7E , 722 indicates the contact feature strength at the location corresponding to the content deletion control 708. The contact feature strength at time T ITD Increase to a level higher than the deep press intensity threshold (IT) D This occurs between the first time threshold T1 and the second time threshold T2. After it is determined that contact has been maintained on the touch-sensitive surface 112 within the first time period T1, the contact characteristic intensity increases to a level higher than the intensity threshold IT. D , deleting content from the editable content area 704 character by character at a rate that varies based on the contact feature strength (e.g., as Figure 7B(As shown). In some implementations, based on the determination that contact has been maintained during the second time period T2, instead of switching to word-by-word deletion, the content is continued to be deleted character by character.

[0447] exist Figure 7F In the diagram, 724 indicates the intensity of the contact feature at the location corresponding to the content deletion control 708. The contact feature intensity at time T... ITD Increase to a level higher than the deep press intensity threshold (IT) D This occurs after the second time period T2. Based on the determination that contact was maintained on the touch-sensitive surface 112 during the second time period T2, the contact characteristic intensity increases to above the intensity threshold level IT. D Content is deleted word-for-word from the editable content area 704 at a rate that varies based on the intensity of the contact feature (e.g., such as...). Figure 7C (As shown).

[0448] exist Figure 7G In the diagram, 726 indicates the intensity of the contact feature at the location corresponding to the content deletion control 708. The contact feature intensity at time T... ITD Increase to a level higher than the deep press intensity threshold (IT) D This occurs between the first time threshold T1 and the second time threshold T2. Based on the determination that contact has been maintained on the touch-sensitive surface 112 during the first time period T1 and before contact has been maintained on the touch-sensitive surface 112 during the second time period T2, the contact characteristic intensity increases to above the intensity threshold level IT. D Before the second time period T2 expires (e.g., at a rate varying based on the intensity of the contact feature), content is deleted word-for-word from the editable content area 704 (e.g., such as...). Figure 7C (As shown).

[0449] exist Figure 7H In the diagram, 728 indicates the intensity of the contact feature at the location corresponding to the content deletion control 708. At time T... ITD1 The contact characteristic intensity increases to a level higher than the deep press intensity threshold (IT). D And at time T ITD2 Reduce to below the deep press intensity threshold level IT D In T ITD2 Then, before the second time period T2 expires, continue deleting content word by word from the editable content area 704 (e.g., such as...). Figure 7C (As shown).

[0450] exist Figure 7I In the diagram, 730 indicates the intensity of the contact feature at the location corresponding to the content deletion control 708. This is based on the determination of the contact feature intensity during the time period T. tapLift-off of contact occurs before (e.g., a tap time threshold) elapses, deleting the single character from the editable content area 704.

[0451] exist Figure 7J In the diagram, 731 indicates the intensity of the contact feature at the location corresponding to the content deletion control 708. The contact feature intensity at time T... ITL Increase to a level higher than the light pressure intensity threshold I TL And at time T ITD Increase to a level higher than the deep press intensity threshold (IT) D In some embodiments, the contact characteristic strength is determined to be inc...

Claims

1. A method for manipulating a user interface object, comprising: At electronic devices with displays and touch-sensitive surfaces: Simultaneously displaying on said display: Background UI; and A first version of a notification associated with a first application, where: The first version of the notification has a first size, The first version of the notification includes first content, and The first version of notification is overlaid on the background user interface; While displaying the first panel of notifications associated with the first application overlaid on the background user interface, detecting a first input, including detecting a first contact at a location on the touch-sensitive surface corresponding to the first panel of notifications; In response to detecting the first input: initiating a process for launching the first application based on determining that the first input satisfies an application launch criterion, wherein the application launch criterion requires that a duration of the first input be below a threshold duration regardless of a characteristic intensity of the first contact, wherein launching the first application includes ceasing to display the background user interface and displaying a user interface associated with the first application; as well as, Based on determining that the first input includes a deep press input that satisfies the time-based criteria but does not satisfy the application launch criteria, displaying a second version of notifications, wherein: The second version of the notification has a second size that is larger than the first size, The second version of the notification includes extended notification content that is not displayed in the first version of the notification, and The second version of notification is overlaid on the background user interface; While displaying the second version of the notification overlaid on the background user interface, detecting a second input, including detecting a second contact on the touch-sensitive surface; and In response to detecting the second input: In accordance with determining that the second contact is detected at a location on the touch-sensitive surface corresponding to a portion of the background user interface surrounding the second version of the notification: ceasing to display the said second notice; and Maintaining display of the background user interface; and Based on determining that the second contact is detected at a location on the touch-sensitive surface corresponding to a content area in the second notification edition: Stop displaying the second version of the notification; Stop displaying the background user interface; and A process for launching the first application is initiated. The method of claim 1 , wherein the second version of the notification includes the first content.

3. The method of claim 1 or 2, wherein the extended notification content includes one or more of the following: an image, an audio clip, a video clip, a customized view, and interactive content that are not included in the first version of the notification.

4. The method according to claim 1 or 2, comprising: When displaying the second version of the notification, receiving information updates related to the notification; as well as In response to receiving the information update related to the notification, the second version of the notification is updated to reflect the information update related to the notification.

5. The method according to claim 1 or 2, wherein: The second version of the notification includes a content area and an action area. The content area includes the extended notification content, and The action area includes one or more selectable options that, when activated, are configured to perform an action with respect to the notification.

6. The method according to claim 5, comprising: While displaying the second version of the notification, detecting a second portion of the first input; In response to detecting the second portion of the first input: In response to determining that the second portion of the first input satisfies option activation criteria, performing the following operations, wherein the option activation criteria requires that a characteristic intensity of the first contact on the touch-sensitive surface satisfies a preview intensity threshold after the characteristic intensity of the first contact falls below a preview intensity threshold in order to satisfy the option activation criteria: ceasing to display the said second notice; and An action corresponding to a selectable option of the one or more selectable options is performed.

7. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions which, when executed by an electronic device having a display and a touch-sensitive surface, cause the electronic device to perform a method according to any one of claims 1-6.

8. An electronic device comprising: monitor; Touch-sensitive surfaces; one or more processors; Memory; and One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 1-6.

9. An electronic device, comprising: monitor; Touch-sensitive surfaces; and An apparatus for performing the method according to any one of claims 1 to 6.

Images