DEVICE, METHOD, AND GRAPHICAL USER INTERFACE FOR PROVIDING HAPTAL FEEDBACK - Patent application

Abstract

To provide a method for providing visual sense and / or visual feedback to allow a user to more efficiently and intuitively perform operation of a user interface object, and an electronic device with improved interface.SOLUTION: An electronic device detects an alert event, and delays provision of feedback showing the alert event until determining whether the electronic device is in a first use context or a second use context in response to detection of the alert event. The device provides a first feedback showing the alert event according to the determination that the electronic device is in the first use context in accordance with the determination as to whether the electronic device is in the first use context or the second use context, and provides second feedback showing the alert event according to the determination that the electronic device is in the second use context different from the first use context.SELECTED DRAWING: Figure 5H

Description

[Technical Field]

[0001] This application relates generally to electronic devices with touch-sensitive surfaces, including, but not limited to, electronic devices with touch-sensitive surfaces that generate tactile outputs that provide tactile feedback to a user. [Background technology]

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

[0003] Exemplary operations include adjusting the position and / or size of one or more user interface objects, activating a button, or opening a file / application represented by a user interface object, associating metadata with one or more user interface objects, or otherwise manipulating the user interface. Exemplary user interface objects include digital images, video, text, icons, and control elements such as buttons and other graphics. In some situations, a user may need to perform such operations on user interface objects in a file management program (e.g., Finder from Apple Inc. of Cupertino, California), an image management application (e.g., Photos from Apple Inc. of Cupertino, California), a digital content (e.g., video and music) management application (e.g., iTunes from Apple Inc. of Cupertino, California), a drawing application, a presentation application (e.g., Keynote from Apple Inc. of Cupertino, California), a word processing application (e.g., Pages from Apple Inc. of Cupertino, California), or a spreadsheet application (e.g., Numbers from Apple Inc. of Cupertino, California).

[0004] Haptic feedback, typically in combination with visual feedback, is often used to attempt to make manipulation of user interface objects more efficient and intuitive for users. However, conventional methods of providing haptic feedback are not as useful as they could be. Summary of the Invention

[0005] Thus, there is a need for electronic devices with improved methods and interfaces for providing visual and / or tactile feedback that make manipulation of user interface objects more efficient and intuitive for users. Such methods and interfaces, optionally complement or replace conventional methods for providing visual and / or tactile feedback. Such methods and interfaces reduce the number, extent, and / or type of inputs from a user by helping the user understand the connection between the input provided and the device's response to that input, thereby creating a more efficient human-machine interface.

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

[0007] According to some embodiments, a method is performed in an electronic device including a display, a touch-sensitive surface, and one or more tactile output generators. The method includes displaying on the display a user interface including a first adjustable control and a second adjustable control, and detecting movement of a first contact across the touch-sensitive surface in a drag gesture. The method further includes adjusting the first adjustable control in accordance with the movement of the first contact in the drag gesture according to a determination that the drag gesture was performed while the focus selector is in a position corresponding to the first adjustable control, and outputting a first plurality of tactile outputs using the one or more tactile output generators. Each tactile output of the first plurality of tactile outputs is triggered based on the ongoing adjustment of the first adjustable control, and the first plurality of tactile outputs has a first distribution of tactile outputs as the first adjustable control is adjusted. The method further includes, in accordance with determining that a drag gesture was performed while the focus selector is in a position corresponding to the second adjustable control, adjusting the second adjustable control in accordance with movement of the first contact in the drag gesture, and outputting a second plurality of tactile outputs using one or more tactile output generators, wherein each tactile output of the second plurality of tactile outputs is triggered based on the ongoing adjustment of the second adjustable control, and the second plurality of tactile outputs has a second distribution of tactile outputs that differs from the first distribution of tactile outputs when the second adjustable control is adjusted.

[0008] In some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, one or more sensors configured to detect an intensity of contact with the touch-sensitive surface, and one or more tactile output generators. The method includes detecting a contact on the touch-sensitive surface while displaying a first user interface on the display, detecting a first increase in a characteristic intensity of the contact on the touch-sensitive surface, generating, with the one or more tactile output generators, a first tactile output having a first tactile output profile in response to detecting the first increase in the characteristic intensity of the contact on the touch-sensitive surface, the first tactile output profile including output parameters that vary according to proximity of the characteristic intensity of the contact to satisfying a first intensity criterion, and detecting a second increase in the characteristic intensity of the contact on the touch-sensitive surface while generating the tactile output having the first tactile output profile. The method further includes, in response to detecting a second increase in the characteristic intensity of the contact on the touch-sensitive surface, generating a second tactile output having a second tactile output profile different from the first tactile output profile in accordance with a determination that the characteristic intensity of the contact on the touch-sensitive surface meets the first intensity criterion, and, in accordance with a determination that the characteristic intensity of the contact on the touch-sensitive surface does not meet the first intensity criterion, continuing to generate the first tactile output having the first tactile output profile and varying an output parameter in accordance with the second increase in the characteristic intensity of the contact based on the proximity of the characteristic intensity of the contact to meeting the first intensity criterion.

[0009] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more tactile output generators. The method includes displaying, on the display, a user interface including a plurality of user interface objects, and detecting a touch input on the touch-sensitive surface by a contact that moves a focus selector in a first direction on the display from a first user interface object of the plurality of user interface objects. In response to detecting the touch input, the method further includes generating, by the one or more tactile output generators, a sequence of tactile outputs corresponding to the movement of the focus selector in the first direction in accordance with a determination that the first user interface object is selected when the focus selector moves in the first direction, and ceasing to generate the sequence of tactile outputs corresponding to the movement of the focus selector in the first direction in accordance with a determination that the first user interface object is not selected when the focus selector moves in the first direction.

[0010] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more tactile output generators. The method includes displaying on the display a first user interface including a plurality of icons of a first type and at least one icon of a second type different from the first type, and detecting contact movement across the touch-sensitive surface in a drag gesture while a focus selector is over a first icon of the first type. The method further includes, in response to detecting contact movement across the touch-sensitive surface in a drag gesture while the focus selector is over the first icon, moving the first icon across the display according to the first contact movement in the drag gesture, and outputting, using the one or more tactile output generators, one or more tactile outputs of the first type in response to determining that the first icon moved over one or more other icons of the first type during the drag gesture, wherein each tactile output of the first type has a first tactile output profile. The method further includes, in response to detecting movement of the contact across the touch-sensitive surface in a drag gesture while the focus selector is over the first icon, displaying, at the end of the drag gesture, a second user interface corresponding to the second type of icon in accordance with a determination that the drag gesture moved the first icon over the second type of icon, and outputting, with the one or more tactile output generators, a second type of tactile output having a second tactile output profile different from the first tactile output profile.

[0011] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, and one or more tactile output generators. The method includes displaying a first user interface on the display including a plurality of icons and detecting a first input by contact on the touch-sensitive surface while a focus selector is over a first icon among the plurality of icons, the first icon having a first size. The method further includes, in response to detecting the first input by contact on the touch-sensitive surface, displaying a preview of an object corresponding to the first icon in accordance with a determination that the first input satisfies a preview display criterion, the preview having a second size larger than the first size, and outputting, using the one or more tactile output generators, a first type of tactile output having a first tactile output profile. The method further includes, in response to detecting the first input by contact on the touch-sensitive surface, in accordance with a determination that the first input satisfies a scrolling criterion different from the preview display criterion, ceasing to display the preview of the object corresponding to the first icon, ceasing to output the first type of tactile output using the one or more tactile output generators, and scrolling the plurality of icons.

[0012] According to some embodiments, a method is performed in an electronic device that includes a display, a touch-sensitive surface, one or more device orientation sensors, and one or more tactile output generators. The method includes receiving a number of communications, detecting a change in position and / or orientation of the electronic device using the one or more device orientation sensors after receiving the number of communications, and generating, with the one or more tactile output generators, a tactile output having a tactile output profile that includes output parameters that increase as the number of received communications increases.

[0013] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, one or more sensors, an audio system, and one or more tactile output generators. The method includes receiving an incoming communication, determining using the one or more sensors that the electronic device is in a first usage context, and in response to receiving the incoming communication, providing first feedback indicative of the incoming communication, wherein providing the first feedback indicative of the incoming communication includes providing, using the audio system, a first ongoing audio output for the incoming communication, the first ongoing audio output corresponding to the first usage context, and providing, using the one or more tactile output generators, a first ongoing tactile output for the incoming communication, the first ongoing tactile output having a first tactile output profile corresponding to the first usage context. The method further includes, while providing the first ongoing audio output and the first ongoing tactile output for the incoming communication, detecting, using one or more sensors, that the electronic device is in a second usage context different from the first usage context, and in response to detecting that the electronic device is in the second usage context, providing second feedback indicative of the incoming communication different from the first feedback, wherein providing the second feedback indicative of the incoming communication includes providing, using one or more tactile output generators, a second ongoing tactile output for the incoming communication, wherein the second ongoing tactile output has a second tactile output profile corresponding to the second usage context.

[0014] According to some embodiments, a method is performed in an electronic device comprising a display, a touch-sensitive surface, one or more sensors, and an audio system and / or one or more tactile output generators. The method includes detecting an alert event. The method also includes, in response to receiving the alert event, delaying providing feedback indicative of the alert event until determining whether the electronic device is in a first usage context or a second usage context distinct from the first usage context; and, in response to determining whether the electronic device is in the first usage context or the second usage context, providing first feedback indicative of the alert event in accordance with a determination that the electronic device is in the first usage context, the first feedback including a first audio output and / or a first tactile output; and providing second feedback indicative of the alert event in accordance with a determination that the electronic device is in the second usage context distinct from the first usage context, the second feedback including a second audio output distinct from the first audio output and / or a second tactile output distinct from the first tactile output.

[0015] According to some embodiments, an electronic device includes a display, a touch-sensitive surface, optionally one or more sensors that detect intensity of contact with the touch-sensitive surface, one or more tactile output generators, optionally one or more device orientation sensors, optionally an audio system, one or more processors, a memory, and one or more programs, the one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that perform or cause to be performed any of the operations of the methods described herein. According to some embodiments, a computer-readable storage medium has instructions stored therein that, when executed by an electronic device that includes a display, a touch-sensitive surface, optionally one or more sensors that detect intensity of contact with the touch-sensitive surface, one or more tactile output generators, optionally one or more device orientation sensors, and optionally an audio system, cause the device to perform or cause to be performed any of the operations of the methods described herein. According to some embodiments, a graphical user interface on an electronic device comprising a display, a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface, one or more tactile output generators, optionally one or more device orientation sensors, optionally an audio system, memory, and one or more processors running one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described herein, and the elements are updated in response to input as described in any of the methods described herein. According to some embodiments, the electronic device includes a display, a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface, one or more tactile output generators, optionally one or more device orientation sensors, optionally an audio system, and means for performing or causing to be performed the operations of any of the methods described herein.According to some embodiments, an information processing apparatus for use in an electronic device comprising a display, a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface, one or more tactile output generators, optionally one or more device orientation sensors, and optionally an audio system, includes means for performing or causing to be performed the operations of any of the methods described herein.

[0016] In this manner, electronic devices comprising a display, a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface, one or more tactile output generators, optionally one or more device orientation sensors, and optionally an audio system provide improved methods and interfaces for providing tactile feedback to users, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can complement or replace conventional methods of providing tactile feedback to users. [Brief explanation of the drawings]

[0017] For a better understanding of the various embodiments described, reference should be made to the following Detailed Description of the Preferred Embodiments in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout the drawings, in which:

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

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

[0020] [Figure 1C] FIG. 10 is a block diagram illustrating a tactile output module according to some embodiments.

[0021] [Figure 2] 1 illustrates a portable multifunction device with a touch screen according to some embodiments.

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

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

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

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

[0026] [Figure 4F] 10 illustrates a set of sample tactile output patterns according to some embodiments. [Figure 4G] 10 illustrates a set of sample tactile output patterns according to some embodiments. [Figure 4H] 10 illustrates a set of sample tactile output patterns according to some embodiments. [Figure 4I] 10 illustrates a set of sample tactile output patterns according to some embodiments. [Figure 4J] 10 illustrates a set of sample tactile output patterns according to some embodiments. [Figure 4K] 10 illustrates a set of sample tactile output patterns according to some embodiments.

[0027] [Figure 5A] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5B-1] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5B-2] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5C-1] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5C-2] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5C-3] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5D-1] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5D-2] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5E-1] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5E-2] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5F] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5G] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5H] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5I] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5J] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5K] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5L] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5M] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5N] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5O] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5P] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5Q] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5R-1] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5R-2] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5R-3] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5R-4] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5S-1] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5S-2] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5T]1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5U] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5V] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5W] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5X-1] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5X-2] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5X-3] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5Y] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5Z] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5AA] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments. [Figure 5BB] 1 illustrates an exemplary user interface that provides haptic feedback according to some embodiments.

[0028] [Figure 5CC] 1 illustrates an exemplary operation of an electronic device according to some embodiments. [Figure 5DD] 1 illustrates an exemplary operation of an electronic device according to some embodiments. [Figure 5EE] 1 illustrates an exemplary operation of an electronic device according to some embodiments. [Figure 5FF] 1 illustrates an exemplary operation of an electronic device according to some embodiments. [Figure 5GG] 1 illustrates an exemplary operation of an electronic device according to some embodiments. [Figure 5HH] 1 illustrates an exemplary operation of an electronic device according to some embodiments. [Figure 5II] 1 illustrates an exemplary operation of an electronic device according to some embodiments. [Figure 5JJ] 1 illustrates an exemplary operation of an electronic device according to some embodiments. [Figure 5KK] 1 illustrates an exemplary operation of an electronic device according to some embodiments. [Figure 5LL] 1 illustrates an exemplary operation of an electronic device according to some embodiments. [Figure 5MM] 1 illustrates an exemplary operation of an electronic device according to some embodiments. [Figure 5NN] 1 illustrates an exemplary operation of an electronic device according to some embodiments. [Figure 5OO] 1 illustrates an exemplary operation of an electronic device according to some embodiments.

[0029] [Figure 6A] FIG. 10 is a flow diagram illustrating a method for outputting a tactile output based on ongoing adjustment of an adjustable control, according to some embodiments. [Figure 6B] FIG. 10 is a flow diagram illustrating a method for outputting a tactile output based on ongoing adjustment of an adjustable control, according to some embodiments. [Figure 6C] FIG. 10 is a flow diagram illustrating a method for outputting a tactile output based on ongoing adjustment of an adjustable control, according to some embodiments.

[0030] [Figure 7A] FIG. 10 is a flow diagram illustrating a method for providing a tactile output in response to a detected increase in a characteristic intensity of a contact, according to some embodiments. [Figure 7B] FIG. 10 is a flow diagram illustrating a method for providing a tactile output in response to a detected increase in a characteristic intensity of a contact, according to some embodiments. [Figure 7C]FIG. 10 is a flow diagram illustrating a method for providing a tactile output in response to a detected increase in a characteristic intensity of a contact, according to some embodiments. [Figure 7D] FIG. 10 is a flow diagram illustrating a method for providing a tactile output in response to a detected increase in a characteristic intensity of a contact, according to some embodiments.

[0031] [Figure 8A] FIG. 10 is a flow diagram illustrating a method for generating a sequence of tactile outputs corresponding to movement of a focus selector according to some embodiments. [Figure 8B] FIG. 10 is a flow diagram illustrating a method for generating a sequence of tactile outputs corresponding to movement of a focus selector according to some embodiments. [Figure 8C] FIG. 10 is a flow diagram illustrating a method for generating a sequence of tactile outputs corresponding to movement of a focus selector according to some embodiments.

[0032] [Figure 9] FIG. 10 is a flow diagram illustrating a method for outputting a tactile output in response to detecting contact movement, according to some embodiments.

[0033] [Figure 10] 1 is a flow diagram illustrating a method for providing output according to touch-detected input in a user interface including multiple icons, according to some embodiments;

[0034] [Figure 11A] FIG. 10 is a flow diagram illustrating a method of generating a tactile output comprising an output parameter that increases as the number of communications received increases, according to some embodiments. [Figure 11B] FIG. 10 is a flow diagram illustrating a method of generating a tactile output comprising an output parameter that increases as the number of communications received increases, according to some embodiments.

[0035] [Figure 12A]FIG. 10 is a flow diagram illustrating a method for providing different feedback indicative of an incoming communication depending on device context, according to some embodiments. [Figure 12B] FIG. 10 is a flow diagram illustrating a method for providing different feedback indicative of an incoming communication depending on device context, according to some embodiments. [Figure 12C] FIG. 10 is a flow diagram illustrating a method for providing different feedback indicative of an incoming communication depending on device context, according to some embodiments. [Figure 12D] FIG. 10 is a flow diagram illustrating a method for providing different feedback indicative of an incoming communication depending on device context, according to some embodiments.

[0036] [Figure 13A] FIG. 10 is a flow diagram illustrating a method for providing different feedback indicating an alert event depending on device context, according to some embodiments. [Figure 13B] FIG. 10 is a flow diagram illustrating a method for providing different feedback indicating an alert event depending on device context, according to some embodiments. [Figure 13C] FIG. 10 is a flow diagram illustrating a method for providing different feedback indicating an alert event depending on device context, according to some embodiments. [Figure 13D] FIG. 10 is a flow diagram illustrating a method for providing different feedback indicating an alert event depending on device context, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0037] Many electronic devices provide feedback upon detecting an input in a graphical user interface and provide an indication of the effect the input has on device operation. Electronic devices also provide feedback to inform the user about incoming and received communications. The methods described herein provide haptic feedback that helps the user understand the effect of the detected input on device operation and provides information to the user about the state of the device.

[0038] Below, Figures 1A-1B, 2, and 3 provide a description of an exemplary device. Figures 4A-4B and 5A-5BB illustrate an exemplary user interface providing haptic feedback. Figures 5CC-500 illustrate an exemplary operation of an electronic device providing audio and / or tactile feedback. Figures 6A-6C illustrate a flow diagram of a method for outputting a tactile output based on the progressive adjustment of an adjustable control. Figures 7A-7D illustrate a flow diagram of a method for generating a tactile output in response to a detected increase in a characteristic intensity of a contact. Figures 8A-8C illustrate a flow diagram of a method for generating a sequence of tactile outputs corresponding to movement of a focus selector. Figure 9 illustrates a flow diagram of a method for outputting a tactile output in response to detecting movement of a contact. Figure 10 illustrates a flow diagram of a method for providing an output according to an input detected by a contact in a user interface including a plurality of icons. Figures 11A-11B illustrate a flow diagram of a method for generating a tactile output including an output parameter that increases as the number of received communications increases.

[0033] Figures 12A-12D show a flow diagram of a method for providing different feedback indicating an incoming communication depending on device context. Figures 13A-13D show a flow diagram of a method for providing different feedback indicating an alert event depending on device context. The user interfaces of Figures 5A-5BB and example operations shown in Figures 5CC-5OO are used to explain the processes of Figures 6A-6C, 7A-7D, 8A-8C, 9, 10, 11A-11B, 12A-12D, and 13A-13D. Exemplary Devices

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

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

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

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

[0043] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile telephone, that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad), 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 having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad).

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

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

[0046] Various applications running on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed for each application and / or within each application. In this way, the common physical architecture (such as the touch-sensitive surface) of the device optionally supports various applications with user interfaces that are intuitive and transparent to the user.

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

[0048] As used herein and in the claims, the term “tactile output” refers to a physical displacement of a device relative to its previous position, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user upon sensing the user's contact. For example, in a situation where a device or a component of the device is in contact with a touch-sensitive user surface (e.g., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement is interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of the touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a “downclick” or “upclick” of a physical actuator button. In some cases, the user will feel a tactile sensation such as a “downclick” or “upclick” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement. As another example, movement of the touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. While such user interpretation of touch depends on the user's personal sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.The use of tactile output to provide haptic feedback to the user enhances the usability of the device, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and additionally reduces the device's power usage and improves battery life by allowing the user to use the device more quickly and efficiently.

[0049] In some embodiments, the tactile output pattern specifies characteristics of the tactile output, such as the amplitude of the tactile output, the shape of the moving waveform of the tactile output, the frequency of the tactile output, and / or the duration of the tactile output.

[0050] When tactile outputs having different tactile output patterns are generated by a device (e.g., via one or more tactile output generators that move a movable mass to generate the tactile output), the tactile outputs can cause different tactile sensations when a user holds or touches the device. While a user's sensations are based on their perception of the tactile output, most users can distinguish changes in the waveform, frequency, and amplitude of the tactile force generated by the device. Thus, the waveform, frequency, and amplitude can be adjusted to indicate to the user that different operations have been performed. In this manner, tactile output having tactile output patterns designed, selected, and / or engineered to simulate the properties (e.g., size, material, weight, stiffness, smoothness, etc.), behavior (e.g., vibration, displacement, acceleration, rotation, magnification, etc.), and / or interaction (e.g., collision, adhesion, repulsion, attraction, friction, etc.) of objects in a given environment (e.g., a user interface including graphical features and objects, a simulated physical environment having virtual boundaries and virtual objects, a real physical environment having physical boundaries and physical objects, and / or any combination of the above) can provide a user with useful feedback that, in some circumstances, reduces input errors and increases efficiency in the user's operation of the device. Additionally, the tactile output is optionally generated to correspond to feedback unrelated to simulated physical properties, such as input thresholds or object selection. Such tactile output can provide a user with useful feedback that, in some circumstances, reduces input errors and increases efficiency in the user's operation of the device.

[0051] In some embodiments, a tactile output having an appropriate tactile output pattern serves as a cue to the occurrence of an event of interest later in the scene within a user interface or device. Examples of events of interest include activation of an affordance provided on the device or within the user interface (e.g., a real button, a virtual button, or a toggle switch), the success or failure of a requested action, reaching or crossing a boundary within the user interface, entering a new state, switching input focus between objects, activating a new mode, reaching or crossing an input threshold, detection or recognition of a type of input or gesture, etc. In some embodiments, a tactile output is provided to serve as a warning or alert to an impending event or outcome that will occur unless a redirection or interrupting input is detected in a timely manner. Tactile output is also used in other contexts to enhance the user experience, improve device accessibility to users with visual or motor impairments or other accessibility needs, and / or improve the efficiency and functionality of the user interface and / or device. The tactile output is optionally accompanied by an audio output and / or a visible user interface change, which further enhances the user's experience when interacting with the user interface and / or device, further facilitates conveying information about the state of the user interface and / or device, and reduces input errors and increases efficiency in the user's operation of the device.

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

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

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

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

[0056] RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to electromagnetic signals or electromagnetic signals to electrical signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well-known circuits for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. RF circuitry 108 optionally communicates via wireless communication with networks and other devices, such as the Internet (also called 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)).The wireless communication optionally includes a Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11n), Voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

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

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

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

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

[0061] Touch-sensitive display system 112 optionally uses liquid crystal display (LCD), light emitting polymer display (LPD), or light emitting diode (LED) technology, although other display technologies are used in other embodiments. Touch-sensitive display system 112 and display controller 156 optionally use any of several now known or later developed touch sensing technologies to detect contact and any movement or disruption thereof, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements that determine one or more points of contact with touch-sensitive display system 112. In some embodiments, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, California.

[0062] Touch-sensitive display system 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen video resolution exceeds 400 dpi (e.g., 500 dpi, 800 dpi, or higher). A user optionally contacts touch-sensitive display system 112 using any suitable object or accessory, such as a stylus, finger, or the like. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which may be less precise than stylus-based input due to the larger area of ​​finger contact on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor position or commands that perform the user's desired action.

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

[0064] Device 100 also includes a power system 162 that provides power to the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with generating, managing, and distributing electrical power within a portable device.

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

[0066] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor(s) 165 optionally include one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor(s) 165 receive contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is disposed on or proximate to the touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display system 112, which is located on the front of device 100.

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

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

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

[0070] In some embodiments, the software components stored in memory 102 include an operating system 126, a communications module (or instruction set) 128, a touch / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a haptic feedback module (or instruction set) 133, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and applications (or instruction sets) 136. Additionally, in some embodiments, as shown in Figures 1A and 3, memory 102 stores device / global internal state 157. Device / global internal state 157 includes one or more of: active application state, which indicates which applications, if any, are currently active; display state, which indicates what applications, views, or other information are occupying various areas of touch-sensitive display system 112; sensor state, which includes information obtained from the device's various sensors and other input or control devices 116; and location and / or position information regarding the location and / or orientation of the device.

[0071] Operating system 126 (e.g., an embedded operating system such as iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or VxWorks) includes various software components and / or drivers that control and manage overall system tasks (e.g., memory management, storage device control, power management, etc.) and facilitate communication between various hardware and software components.

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

[0073] Contact / motion module 130 optionally detects contact with touch-sensitive display system 112 (in cooperation with display controller 156) and with other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes software components that perform various operations related to detecting contact (e.g., by a finger or stylus), such as determining if contact has occurred (e.g., detecting a finger-down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining if there is contact movement and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining if the contact has stopped (e.g., detecting a finger-up event or an interruption of contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point represented by the set of contact data optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These operations are optionally applied to a single contact (e.g., a single finger contact or a stylus contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contacts on a touchpad.

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

[0075] In some embodiments, detecting a finger tap gesture (e.g., on touch-sensitive display system 112) depends on the length of time between detecting a finger-down event and detecting a finger-up event, but is not related to the intensity of the finger contact between detecting the finger-down event and detecting the finger-up event. In some embodiments, a tap gesture is detected according to determining that the length of time between the finger-down event and the finger-up event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4, or 0.5 seconds), 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 or deep pressure intensity threshold. Thus, a finger tap gesture can satisfy certain input criteria that do not require the characteristic intensity of the contact to meet a given intensity threshold for the particular input criteria to be met. For clarity, the finger contact in a tap gesture generally needs to meet a nominal contact-detection intensity threshold below which the contact is not detected, for a finger-down event to be detected. A similar analysis applies to detecting tap gestures or other contacts with a stylus. In cases where the device is capable of detecting contact of a finger or stylus hovering over the touch-sensitive surface, the nominal contact-detection intensity threshold is optional and does not correspond to physical contact between the finger or stylus and the touch-sensitive surface.

[0076] In a similar manner, the same concepts apply to other types of gestures. For example, swipe gestures, pinch gestures, de-pinch gestures, and / or long press gestures (e.g., on touch-sensitive display system 112) are optionally detected based on meeting criteria that are either unrelated to the intensity of the contacts included in the gesture or that do not require the contact(s) performing the gesture to reach an intensity threshold to be recognized. For example, swipe gestures are detected based on the amount of movement of one or more contacts, pinch gestures are detected based on the movement of two or more contacts toward each other, de-pinch gestures are detected based on the movement of two or more contacts away from each other, and long press gestures are detected based on the duration of contacts on the touch-sensitive surface that are less than a threshold amount of movement. Thus, a statement that a particular gesture recognition criterion does not require the intensity of a contact(s) to meet a respective intensity threshold in order for the particular gesture recognition criterion to be met means that the particular gesture recognition criterion can be met when the contact(s) in the gesture do not reach their respective intensity threshold, and can also be met in situations where one or more of the contacts in the gesture do not reach or exceed their respective intensity threshold. In some embodiments, a tap gesture is detected based on determining that a finger-down event and a finger-up event are detected within a predetermined time period, regardless of whether the contacts are above or below their respective intensity thresholds during the predetermined time period, and a swipe gesture is detected based on determining that a movement of the contact is greater than a predefined magnitude, even if the contact exceeds its respective intensity threshold at the end of the movement of the contact.Even in implementations in which gesture detection is affected by the intensity of the contact performing the gesture (e.g., the device detects long presses more quickly when the intensity of the contact exceeds an intensity threshold, or the device is slower to detect tap inputs when the intensity of the contact is higher), detection of those gestures does not require the contact to reach a particular intensity threshold, as long as the criteria for recognizing the gesture can be met in situations in which the contact does not reach the particular intensity threshold (e.g., even if the amount of time required to recognize the gesture varies).

[0077] The contact intensity threshold, duration threshold, and movement threshold may, in some circumstances, be combined in various different combinations to create heuristics that distinguish between two or more different gestures directed at the same input element or region, thereby enabling multiple different interactions with the same input element to provide a richer set of user interactions and responses. A statement that a particular set of gesture recognition criteria does not require that the intensity of a contact(s) meet a respective intensity threshold for that particular gesture recognition criterion to be satisfied does not preclude the simultaneous evaluation of other intensity-dependent gesture recognition criteria that identify other gestures with criteria that are satisfied when the gesture includes a contact having an intensity above a respective intensity threshold. For example, in some circumstances, a first gesture recognition criterion for a first gesture that does not require that the intensity of a contact(s) meet a respective intensity threshold for that first gesture recognition criterion to be satisfied competes with a second gesture recognition criterion for a second gesture that depends on the contact(s) reaching a respective intensity threshold. In such a competition, a gesture is optionally not recognized as satisfying the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are satisfied first. For example, if the contact reaches the respective intensity threshold before moving the predefined amount of movement, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves the predefined amount of movement before reaching the respective intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such a situation, the first gesture recognition criteria for the first gesture still do not require that the intensity of the contact(s) meet the respective intensity threshold for the first gesture recognition criteria to be satisfied, because if the contact remains below the respective intensity threshold until the end of the gesture (e.g., a swipe gesture with contact that does not increase in intensity above the respective intensity threshold), the gesture is recognized by the first gesture recognition criteria as a swipe gesture.In this way, certain gesture recognition criteria that do not require the intensity of the contact(s) to meet a respective intensity threshold in order for the particular gesture recognition criterion to be satisfied are still dependent on the intensity of the contact with respect to the intensity threshold in the sense that (A) in some circumstances, they ignore the intensity of the contact with respect to the intensity threshold (e.g., for a tap gesture), and / or (B) in some circumstances, the particular gesture recognition criterion (e.g., for a long press gesture) will not function if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognizes an 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 competes with a deep press gesture for recognition).

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

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

[0080] The haptic feedback module 133 includes various software components that generate instructions (e.g., instructions used by the haptic feedback controller 161) that use the tactile output generator(s) 167 to create tactile outputs at one or more locations on the device 100 in response to user interaction with the device 100.

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

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

[0083] Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: • a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ●Video conferencing module 139, ● an email client module 140; ● Instant messaging (IM) module 141; ●Training support module 142, a camera module 143 for still and / or video images, ● Image management module 144; ● Browser module 147, ●Calendar module 148, • a widget module 149 optionally including one or more of a weather widget 149-1, a stock price widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets acquired by the user, as well as user-created widgets 149-6; a widget creation module 150 that creates user-created widgets 149-6; ● Search module 151, • a video and music player module 152, optionally comprising a video player module and a music player module; ● Memo module 153, Map module 154, and / or ●Online video module 155.

[0084] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA® enabled applications, encryption, digital rights management, voice recognition, and voice duplication.

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

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

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

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

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

[0090] In cooperation with the RF circuitry 108, the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154, and the music player module 152, the training support module 142 contains executable instructions to create workouts (e.g., with time, distance, and / or calorie burn goals), communicate with training sensors (in the sports device and the smartwatch), receive training sensor data, calibrate sensors used to monitor workouts, select and play music for workouts, and display, store, and transmit workout data.

[0091] Camera module 143, in conjunction with touch-sensitive display system 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact module 130, graphics module 132, and image management module 144, includes executable instructions to capture still images or video (including video streams) and store them in memory 102, modify characteristics of the still images or video, and / or delete the still images or video from memory 102.

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

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

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

[0095] Widget modules 149, in conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, are optionally mini-applications downloaded and used by users (e.g., weather widget 149-1, stock quotes widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5), or mini-applications created by users (e.g., user-created widget 149-6). In some embodiments, widgets include Hypertext Markup Language (HTML) files, Cascading Style Sheets (CSS) files, and JavaScript files. In some embodiments, widgets include Extensible Markup Language (XML) files and JavaScript files (e.g., Yahoo! Widgets).

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

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

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

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

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

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

[0102] Each of the identified modules and applications corresponds to executable instruction sets that perform one or more of the functions described above and methods described in the present application (e.g., computer-implemented methods and other information processing methods described herein). The modules (i.e., instruction sets) need not be implemented as separate software programs, procedures, or modules; thus, various subsets of the modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.

[0103] In some embodiments, device 100 is a device in which operation of a predefined set of functions on the device is performed exclusively through a touchscreen and / or touchpad. By using the touchscreen and / or touchpad as the primary input control device for operation of device 100, the number of physical input control devices (pushbuttons, dials, etc.) on device 100 is optionally reduced.

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

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

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

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

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

[0109] In some embodiments, event monitor 171 sends requests to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or for longer than a predetermined period of time).

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

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

[0112] Another aspect of a user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of each application) in which touches are detected optionally correspond to program 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 recognized as appropriate inputs is optionally determined based at least in part on the hit view of the initial touch that initiates the touch-based gesture.

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

[0114] Active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive the particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive the particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that contain the physical location of the sub-event are actively participating views, and therefore, all actively participating views should receive the particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the region associated with a particular view, views higher in the hierarchy remain actively participating views.

[0115] 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 recognizers determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information obtained by each event receiver module 182 in an event queue.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0129] It should be understood that the foregoing description of event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 using input devices, although not all of them are initiated on the touchscreen. For example, mouse movements and mouse button presses, optionally in conjunction with one or more keyboard presses or holds, contact movements such as tapping, dragging, scrolling on a touchpad, pen stylus input, device movement, verbal commands, detected eye movements, biometric input, and / or any combination thereof are optionally utilized as inputs corresponding to sub-events that define the event to be recognized.

[0130] 1C is a block diagram illustrating a tactile output module, according to some embodiments. In some embodiments, I / O subsystem 106 (e.g., haptic feedback controller 161 (FIG. 1A) and / or other input controller(s) 160 (FIG. 1A) includes at least some of the example components shown in FIG. 1C. In some embodiments, peripherals interface 118 includes at least some of the example components shown in FIG. 1C.

[0131] In some embodiments, the tactile output module includes a haptic feedback module 133. In some embodiments, the haptic feedback module 133 collects and combines tactile output for user interface feedback from software applications on the electronic device (e.g., feedback in response to user input corresponding to a displayed user interface, and alerts and other notifications indicating the performance of an action or the occurrence of an event in the user interface of the electronic device). The haptic feedback module 133 includes one or more of: a waveform module 123 (which provides the waveforms used to generate the tactile output); a mixer 125 (which mixes waveforms, such as waveforms for different channels); a compressor 127 (which reduces or compresses the dynamic range of the waveforms); a low-pass filter 129 (which filters out high-frequency signal components in the waveforms); and a thermal controller 131 (which adjusts the waveforms according to thermal conditions). In some embodiments, the haptic feedback controller 161 ( FIG. 1A ) includes the haptic feedback module 133. In some embodiments, a separate unit of haptic feedback module 133 (or a separate implementation of haptic feedback module 133) is also included in an audio controller (e.g., audio circuit 110 of FIG. 1A) and used to generate audio signals. In some embodiments, a single haptic feedback module 133 is used to generate audio signals and generate waveforms for tactile outputs.

[0132] In some embodiments, haptic feedback module 133 also includes trigger module 121 (e.g., a software application, operating system, or other software module that determines to generate a tactile output and initiates the process of generating a corresponding tactile output). In some embodiments, trigger module 121 generates a trigger signal that initiates the generation of a waveform (e.g., by waveform module 123). For example, trigger module 121 generates the trigger signal based on a preset timing criteria. In some embodiments, trigger module 121 receives a trigger signal from an external haptic feedback module 133 (e.g., in some embodiments, haptic feedback module 133 receives a trigger signal from hardware input processing module 146 located external to haptic feedback module 133) and relays the trigger signal to other components within haptic feedback module 133 (e.g., waveform module 123) or to a software application that triggers an action (e.g., using trigger module 121) based on the activation of a user interface element (e.g., an application icon or an affordance within an application) or a hardware input device (e.g., a home button or an intensity-sensitive input surface such as an intensity-sensitive touchscreen). In some embodiments, trigger module 121 also receives tactile feedback generation instructions (e.g., from haptic feedback module 133, FIGS. 1A and 3). In some embodiments, trigger module 121 generates a trigger signal in response to haptic feedback module 133 (or trigger module 121 within haptic feedback module 133) receiving a tactile feedback instruction (e.g., from haptic feedback module 133, FIGS. 1A and 3).

[0133] Waveform module 123 receives a trigger signal as an input (e.g., from trigger module 121) and, in response to the received trigger signal, provides a waveform for generation of one or more tactile outputs (e.g., a waveform selected from a predetermined set of waveforms designed for use by waveform module 123, such as the waveforms described in more detail below with reference to Figures 4F-4G).

[0134] Mixer 125 receives waveforms (e.g., from waveform module 123) as inputs and combines the waveforms. For example, when mixer 125 receives two or more waveforms (e.g., a first waveform in a first channel and a second waveform in a second channel that at least partially overlaps the first waveform), mixer 125 outputs a combined waveform corresponding to the sum of the two or more waveforms. In some embodiments, mixer 125 also modifies one or more of the two or more waveforms (e.g., by increasing the scale of the particular waveform(s) and / or decreasing the scale of the rest of the waveforms) to emphasize the particular waveform(s) over the rest of the two or more waveforms. In some situations, mixer 125 selects one or more waveforms to remove from the combined waveform (e.g., excluding the waveform from the oldest source when there are waveforms from more than three sources requested to be output simultaneously by tactile output generator 167).

[0135] Compressor 127 receives as input a waveform (e.g., a composite waveform from mixer 125) and modifies the waveform. In some embodiments, compressor 127 reduces the waveform (e.g., according to the physical specifications of tactile output generator 167 (FIG. 1A) or 357 (FIG. 3)) such that the tactile output corresponding to the waveform is reduced. In some embodiments, compressor 127 limits the waveform, such as by imposing a predefined maximum amplitude on the waveform. For example, compressor 127 reduces the amplitude of portions of the waveform that exceed a predetermined amplitude threshold while maintaining the amplitude of portions of the waveform that do not exceed the predetermined amplitude threshold. In some embodiments, compressor 127 reduces the dynamic range of the waveform. In some embodiments, compressor 127 dynamically reduces the dynamic range of the waveform such that the composite waveform remains within the performance specifications (e.g., force and / or movable mass displacement limits) of tactile output generator 167.

[0136] Low pass filter 129 receives as an input a waveform (e.g., the compressed waveform from compressor 127) and filters (e.g., smooths) the waveform (e.g., removes or reduces high frequency signal components in the waveform). For example, in some instances, compressor 127 may include extraneous signals (e.g., high frequency signal components) in the compressed waveform that interfere with the generation of a tactile output and / or exceed the performance specifications of tactile output generator 167 when a tactile output is generated according to the compressed waveform. Low pass filter 129 reduces or removes such extraneous signals in the waveform.

[0137] Thermal controller 131 receives a waveform (e.g., a filtered waveform from low-pass filter 129) as an input and adjusts the waveform according to the thermal conditions of device 100 (e.g., based on the temperature of haptic feedback controller 161 and / or an internal temperature detected within device 100, such as an external temperature detected by device 100). For example, in some cases, the output of haptic feedback controller 161 varies with temperature (e.g., haptic feedback controller 161 generates a first tactile output when haptic feedback controller 161 is at a first temperature and a second tactile output when haptic feedback controller 161 is at a second temperature distinct from the first temperature, in response to receiving the same waveform). For example, the magnitude (or amplitude) of the tactile output may vary with temperature. The waveform is modified (e.g., increasing or decreasing the amplitude of the waveform based on temperature) to reduce the effect of temperature changes.

[0138] In some embodiments, haptic feedback module 133 (e.g., trigger module 121) is coupled to hardware input processing module 146. In some embodiments, other input controller(s) 160 of FIG. 1A includes hardware input processing module 146. In some embodiments, hardware input processing module 146 receives input from hardware input device 145 (e.g., other input or control device 116 of FIG. 1A, such as a home button or an intensity-sensitive input surface such as an intensity-sensitive touchscreen). In some embodiments, hardware input device 145 is any of touch-sensitive display system 112 (FIG. 1A), keyboard / mouse 350 (FIG. 3), touchpad 355 (FIG. 3), one of other input or control devices 116 (FIG. 1A), or an input device such as an intensity-sensitive home button. In some embodiments, hardware input device 145 consists of an intensity-sensitive home button and is not touch-sensitive display system 112 (FIG. 1A), keyboard / mouse 350 (FIG. 3), or touchpad 355 (FIG. 3). In some embodiments, in response to input from hardware input processing module 145 (e.g., an intensity-sensitive home button or a touchscreen), hardware input processing module 146 provides one or more trigger signals to haptic feedback module 133 to indicate that a user input that meets predetermined input criteria has been detected, such as an input corresponding to a home button "click" (e.g., a "down click" or an "up click"). In some embodiments, haptic feedback module 133, in response to an input corresponding to a home button "click," provides a waveform corresponding to a home button "click" to simulate the haptic feedback of pressing a physical home button.

[0139] In some embodiments, the tactile output module includes a haptic feedback controller 161 (haptic feedback controller 161 in FIG. 1A ) that controls the generation of the tactile output. In some embodiments, the haptic feedback controller 161 is coupled to a plurality of tactile output generators, selects one or more of the plurality of tactile output generators, and sends waveforms to the selected one or more tactile output generators to generate the tactile output. In some embodiments, the haptic feedback controller 161 aligns the tactile output request corresponding to the activation of the hardware input device 145 with the tactile output request corresponding to the software event (e.g., the tactile output request from the haptic feedback module 133) (e.g., by increasing the scale of the particular waveform(s) and / or decreasing the scale of the remainder of the waveforms, e.g., to prioritize the tactile output corresponding to the activation of the hardware input device 145 over the tactile output corresponding to the software event), and modifies one or more of the two or more waveforms to emphasize the particular waveform(s) over the remainder of the two or more waveforms.

[0140] In some embodiments, as shown in FIG. 1C , the output of haptic feedback controller 161 is coupled to an audio circuit of device 100 (e.g., audio circuit 110, FIG. 1A ) and provides an audio signal to the audio circuit of device 100. In some embodiments, haptic feedback controller 161 provides both the waveform used to generate the tactile output and the audio signal used to provide the audio output in conjunction with generating the tactile output. In some embodiments, haptic feedback controller 161 modifies the audio signal and / or waveform (used to generate the tactile output) so that the audio output and the tactile output are synchronized (e.g., by delaying the audio signal and / or waveform). In some embodiments, haptic feedback controller 161 includes a digital-to-analog converter (DAC) used to convert the digital waveform to an analog signal, which is received by amplifier 163 and / or tactile output generator 167.

[0141] In some embodiments, tactile output module includes amplifier 163. In some embodiments, amplifier 163 receives a waveform (e.g., from haptic feedback controller 161) and amplifies the waveform before sending the amplified waveform to tactile output generator 167 (e.g., either tactile output generator 167 (FIG. 1A) or 357 (FIG. 3)). For example, amplifier 163 amplifies the received waveform to a signal level according to the physical specifications of tactile output generator 167 (e.g., the voltage and / or current required by tactile output generator 167 to generate a tactile output, such that the signal sent to tactile output generator 167 generates a tactile output that corresponds to the waveform received from tactile feedback controller 161) and sends the amplified waveform to tactile output generator 167. In response, tactile output generator 167 generates a tactile output (e.g., by reciprocating the movable mass one or more distances relative to a neutral position of the movable mass).

[0142] In some embodiments, tactile output module includes sensor 169 coupled to tactile output generator 167. Sensor 169 detects a state or change in state (e.g., mechanical position, physical displacement, and / or movement) of tactile output generator 167 or one or more components of tactile output generator 167 (e.g., one or more moving parts, such as a membrane, used to generate the tactile output). In some embodiments, sensor 169 is a magnetic field sensor (e.g., a Hall Effect sensor) or other displacement and / or movement sensor. In some embodiments, sensor 169 provides information (e.g., position, displacement, and / or movement of one or more parts in tactile output generator 167) to tactile feedback controller 161, and tactile feedback controller 161 adjusts a waveform output from tactile feedback controller 161 (e.g., a waveform sent to tactile output generator 167, optionally via amplifier 163) according to the information about the state of tactile output generator 167 provided by sensor 169.

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

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

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

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

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

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

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

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

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

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

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

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

[0155] As used herein and in the claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact or a stylus contact) on the touch-sensitive surface, or a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four different values ​​and more typically includes hundreds (e.g., at least 256) different values. The intensity of a contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors beneath or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average or sum) to determine an estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure of the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is stated in units corresponding to the surrogate measure). In some implementations, the surrogate measure of the force or pressure of the contact is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of contact as a property of user input allows a user to access additional device functionality that may not otherwise be easily accessible by a user in devices of reduced size that have limited area for displaying affordances (e.g., on a touch-sensitive display) and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical control such as a knob or button).

[0156] In some embodiments, contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by the user (e.g., whether the user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a particular physical actuator and may be adjusted without modifying the physical hardware of device 100). For example, the mouse “click” threshold of a trackpad or touchscreen display may be set to any of a wide range of pre-defined thresholds without modifying the trackpad or touchscreen display hardware. Furthermore, in some implementations, a user of the device is provided with a software setting to adjust one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once via a system-level click “intensity” parameter).

[0157] As used herein and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of that contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined number of intensity samples or a set of intensity samples collected within a predetermined period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) for a given event (e.g., after detecting the contact, before detecting lift-off of the contact, before or after detecting the start of contact movement, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The characteristic intensity of a contact is optionally based on one or more of the maximum intensity of the contact, the mean value of the intensity of the contact, the average value of the intensity of the contact, the top 10% of the intensity of the contact, half the maximum intensity of the contact, 90% of the maximum intensity of the contact, a value generated by low-pass filtering the intensity of the contact starting over a predefined period or at a predefined time, etc. In some embodiments, the duration of the contact is used to determine the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an action is performed by the user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact having a characteristic intensity that does not exceed the first threshold results in a first action being performed, a contact having a characteristic intensity that exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second action being performed, and a contact having a characteristic intensity that exceeds the second intensity threshold results in a third action being performed. In some embodiments, the comparison between the characteristic intensity and one or more intensity thresholds is not used to determine whether to perform the first or second action, but rather to determine whether to perform one or more operations (e.g., to perform a respective option or to forgo performing a respective operation).

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

[0159] The user interface diagrams described herein may optionally be configured with one or more intensity thresholds (e.g., a touch-detection intensity threshold IT0, a light press intensity threshold IT1, and a light press intensity threshold IT2). L , deep pressure intensity threshold IT D (e.g., IT, at least initially L higher than 0.15), and / or one or more other intensity thresholds (e.g., IT L An intensity threshold lower than IT H), showing the current intensity of the contact on the touch-sensitive surface relative to the intensity of the contact. This intensity chart is typically not part of the displayed user interface, but is provided to aid in interpretation of the diagrams. In some embodiments, the light pressure intensity threshold corresponds to the intensity at which the device performs an operation typically associated with clicking a physical mouse button or trackpad. In some embodiments, the deep pressure intensity threshold corresponds to the intensity at which the device performs an operation different from the operation typically associated with clicking a physical mouse button or trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light pressure intensity threshold (e.g., and above a nominal contact-detection intensity threshold IT0, below which the contact is no longer detected), the device moves the focus selector according to the movement of the contact on the touch-sensitive surface without performing the operation associated with the light pressure intensity threshold or the deep pressure intensity threshold. Generally, unless otherwise specified, these intensity thresholds are consistent across different sets of user interface diagrams.

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

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

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

[0163] FIG. 4D illustrates another dynamic intensity threshold 486 (e.g., intensity threshold I D ) Figure 4D also shows two other intensity thresholds: a first intensity threshold I H and a second intensity threshold I L In FIG. 4D, the touch input 484 reaches the first intensity threshold I before time p2. H and a second intensity threshold I L , but no response is provided until a delay time p2 has elapsed at time 482. Also in FIG. 4D, the dynamic intensity threshold 486 is set after a predefined delay time p1 has elapsed from time 482 (a second intensity threshold I L This type of dynamic intensity threshold decays over time, with the decay starting at time 488 (when the response associated with the first intensity threshold I H or the second intensity threshold I L Immediately after or simultaneously triggering a response associated with a lower intensity threshold, such as a dynamic intensity threshold I D and reducing the accidental triggering of related responses.

[0164] FIG. 4E illustrates yet another dynamic intensity threshold 492 (e.g., intensity threshold I D ) is shown. In FIG. 4E, the intensity threshold I LThe response associated with the intensity threshold I is triggered after a delay time p2 from when the touch input 490 is first detected. At the same time, the dynamic intensity threshold 492 decays after a predefined delay time p1 from when the touch input 490 is first detected. Thus, without releasing the touch input 490, the intensity threshold I L A decrease in the intensity of touch input 490 followed by an increase in the intensity of touch input 490 after triggering a response associated with the intensity threshold I 1 is generated when the intensity of touch input 490 exceeds another intensity threshold, e.g., intensity threshold I 1 . L Even when the intensity threshold I D A response related to the

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

[0166] In some embodiments described herein, one or more operations are performed in response to detecting a gesture including the respective pressure input, or in response to detecting the respective pressure input performed on the respective contact (or contacts), where the respective pressure inputs are detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a pressure input intensity threshold. In some embodiments, the respective operations are performed in response to detecting an increase in intensity of the respective contact above a pressure input intensity threshold (e.g., the respective operations are performed on the “downstroke” of the respective pressure input). In some embodiments, the pressure input includes an increase in intensity of the respective contact above a pressure input intensity threshold and a subsequent decrease in intensity of the contact below the pressure input intensity threshold, and the respective operations are performed in response to detecting a subsequent decrease in intensity of the respective contact below the pressure input threshold (e.g., the respective operations are performed on the “upstroke” of the respective pressure input).

[0167] In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as “jitter,” and the device defines or selects a hysteresis intensity threshold that has a predetermined relationship to the pressure input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below the pressure input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the pressure input intensity threshold). Thus, in some embodiments, the pressure input includes an increase in the intensity of each contact above the pressure input intensity threshold and a subsequent decrease in the intensity of the contact below the hysteresis intensity threshold corresponding to the pressure input intensity threshold, and a respective operation is performed in response to detecting a subsequent decrease in the intensity of each contact below the hysteresis intensity threshold (e.g., a respective operation is performed on the “upstroke” of a respective pressure input). Similarly, in some embodiments, a pressure input is detected only when the device detects an increase in the intensity of the contact from an intensity below the hysteresis intensity threshold to an intensity above the pressure input intensity threshold, and optionally a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and a corresponding action is performed in response to detection of the pressure input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact, as the case may be).

[0168] For ease of explanation, descriptions of operations performed in response to a pressure input associated with a pressure input intensity threshold or in response to a gesture including a pressure input are optionally triggered in response to detecting an increase in the intensity of the contact above the pressure input intensity threshold, an increase in the intensity of the contact from an intensity below a hysteresis intensity threshold to an intensity above the pressure input intensity threshold, a decrease in the intensity of the contact below the pressure input intensity threshold, or a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to the pressure input intensity threshold. Additionally, in examples described as performing an operation in response to detecting a decrease in the intensity of the contact below a pressure input intensity threshold, the operation is optionally performed in response to detecting a decrease in the intensity of the contact below a hysteresis intensity threshold corresponding to and lower than the pressure input intensity threshold. As described above, in some embodiments, the triggering of such responses also depends on time-based criteria being met (e.g., a delay time elapsed between the first intensity threshold being met and the second intensity threshold being met).

[0169] 4F-4H provide a set of sample tactile output patterns that can be used individually or in combination, either through one or more transformations (e.g., modulation, amplification, truncation, etc.), to create suitable tactile feedback for a variety of scenarios and purposes, such as those mentioned or described above with respect to the user interfaces and methods discussed herein. This example palette of tactile outputs shows how a set of three waveforms and eight frequencies can be used to generate an array of tactile output patterns. In addition to the tactile output patterns shown in this figure, each of these tactile output patterns can optionally be adjusted in amplitude by changing the gain value for the tactile output pattern, as shown, for example, by changing the gains of 1.0, 0.75, 0.5, and 0.25 for full tap 80 Hz, full tap 200 Hz, mini tap 80 Hz, mini tap 200 Hz, micro tap 80 Hz, and micro tap 200 Hz, respectively, as shown in FIGS. 4I-4K. As shown in Figures 4I-4K, changing the gain of the tactile output pattern changes the amplitude of the pattern without changing the frequency of the pattern or the shape of the waveform. In some embodiments, because some tactile output generators are limited by how much force they can apply to a moving mass, changing the frequency of the tactile output pattern also results in a smaller amplitude, thereby constraining mass movement at higher frequencies to smaller amplitudes to ensure that the accelerations required to create the waveform do not require forces outside the operating force range of the tactile output generator (e.g., the peak amplitudes of full taps at 230 Hz, 270 Hz, and 300 Hz are lower than the amplitudes of full taps at 80 Hz, 100 Hz, 125 Hz, and 200 Hz).

[0170] 4F-4K show tactile output patterns having particular waveforms. The waveform of a tactile output pattern represents the neutral position (e.g., x) relative to the time that the moving mass passes through to generate the tactile output in that tactile output pattern. zero) represent patterns of physical displacement relative to the moving mass. For example, a first set of tactile output patterns (e.g., "full tap" tactile output patterns) shown in FIG. 4F each have waveforms that include two complete cycles of vibration (e.g., vibrations that start and end at a neutral position and cross the neutral position three times). A second set of tactile output patterns (e.g., "mini tap" tactile output patterns) shown in FIG. 4G each have waveforms that include one complete cycle of vibration (e.g., vibrations that start and end at a neutral position and cross the neutral position once). A third set of tactile output patterns (e.g., "micro tap" tactile output patterns) shown in FIG. 4H each have waveforms that include half of one complete cycle of vibration (e.g., vibrations that start and end at a neutral position and do not cross the neutral position). The waveforms of the tactile output patterns also include start and end buffers that represent a gradual speed-up and slow-down of the moving mass at the beginning and end of the tactile output. The exemplary waveforms shown in FIGS. 4F-4K are x, which represent the maximum and minimum limits of movement of the moving mass. max value and x min values. For larger electronic devices with larger movable masses, the minimum and maximum limits of mass movement may be larger or smaller. While the examples shown in Figures 4F-4K illustrate movement of a mass in one dimension, similar principles may apply to movement of a movable mass in two or three dimensions.

[0171] As shown in FIGS. 4F-4H, each tactile output pattern also has a corresponding characteristic frequency that affects the "pitch" of the tactile sensation a user feels from a tactile output having that characteristic frequency. For continuous tactile outputs, the characteristic frequency represents the number of cycles (e.g., cycles per second) completed within a given time period by the moving mass of the tactile output generator. For discrete tactile outputs, a discrete output signal (e.g., at 0.5 cycles, 1 cycle, or 2 cycles) is generated, and the characteristic frequency value specifies how fast the moving mass must move to generate a tactile output at that characteristic frequency. As shown in FIGS. 4F-4H, for each type of tactile output (defined by its respective waveform, such as full tap, mini tap, or micro tap), a higher frequency value corresponds to a faster movement(s) by the moving mass and therefore generally a shorter time to complete the tactile output (e.g., the time to complete the number of cycles required for the discrete tactile output, including start and end buffer times). For example, a full tap with a characteristic frequency of 80 Hz takes longer to complete than a full tap with a characteristic frequency of 100 Hz (e.g., 35.4 ms vs. 28.3 ms in Figure 4F). Furthermore, at a given frequency, tactile outputs with more cycles of that waveform at each frequency take longer to complete than tactile outputs with fewer cycles of that waveform at the same respective frequency. For example, a 150 Hz full tap takes longer to complete than a 150 Hz mini-tap (e.g., 19.4 ms vs. 12.8 ms), which in turn take longer to complete than a 150 Hz micro-tap (e.g., 12.8 ms vs. 9.4 ms). However, this regularity may not hold for tactile output patterns at different frequencies (e.g., a tactile output with more cycles but a higher frequency may take less time than a tactile output with fewer cycles but a lower frequency, and vice versa). For example, at 300 Hz, a full tap takes the same time as a mini-tap (e.g., 9.9 ms).

[0172] As shown in FIGS. 4F-4H , a tactile output pattern also has a characteristic amplitude that affects the amount of energy contained in the tactile signal, or the “intensity” of the tactile sensation that a user may feel through a tactile output having that characteristic amplitude. In some embodiments, the characteristic amplitude of a tactile output pattern refers to an absolute or normalized value that represents the maximum displacement of the moving mass from a neutral position when generating a tactile output. In some embodiments, the characteristic amplitude of a tactile output pattern is adjustable by a fixed or dynamically determined gain factor (e.g., a value between 0 and 1), for example, according to various conditions (e.g., customized based on the context and behavior of the user interface) and / or preconfigured metrics (e.g., input-based metrics and / or user-interface-based metrics). In some embodiments, an input-based metric (e.g., an intensity-change metric or an input-velocity metric) measures a characteristic of the input (e.g., the rate of change of the characteristic intensity of the contact in a pressure input, or the velocity of movement of the contact across the touch-sensitive surface) during the input that triggers the generation of the tactile output. In some embodiments, a user interface-based metric (e.g., a boundary crossing speed metric) measures a characteristic of a user interface element (e.g., the speed of movement of an element crossing a hidden or visible boundary in the user interface) during a user interface change that triggers the generation of a tactile output. In some embodiments, the characteristic amplitude of the tactile output pattern may be modulated by an "envelope," where peaks in adjacent cycles may have different amplitudes, one of which waveforms is further modulated by multiplying it by an envelope parameter that varies over time (e.g., from 0 to 1) to gradually adjust the amplitude of portions of the tactile output over time while the tactile output is being generated.

[0173] For illustrative purposes, specific frequencies, amplitudes, and waveforms are depicted in the sample tactile output patterns in Figures 4F-4H, but tactile output patterns having other frequencies, amplitudes, and waveforms may be used for similar purposes. For example, waveforms of 0.5 to 4 cycles may be used. Other frequencies in the range of 60 Hz to 400 Hz may also be used.

[0174] In some embodiments, tactile outputs including one or more of vibration 150Hz, microtap 150Hz, minitap 150Hz, and full tap 150Hz are used for ringtones and / or alerts (to indicate an incoming call or text message).

[0175] For illustrative purposes, only specific frequencies, amplitudes, and waveforms are shown in the sample tactile output patterns in Figures 4F-4K, but tactile output patterns having other frequencies, amplitudes, and waveforms may be used for similar purposes. For example, waveforms of 0.5 to 4 cycles may be used. Other frequencies in the range of 60 Hz to 400 Hz may also be used. User Interface and Related Processing

[0176] Attention is now directed to embodiments of user interfaces (“UI”) and associated processing that may be implemented on an electronic device such as portable multifunction device 100 or device 300, which includes a display, a touch-sensitive surface, optionally one or more tactile output generators that generate tactile output, and optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface.

[0177] 5A-5BB show exemplary user interfaces that provide haptic feedback, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 6A-6C, 7A-7D, 8A-8C, 9, 10, 11A-11B, and 12A-12D. For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device having touch-sensitive display system 112. In such embodiments, the focus selector is optionally a respective finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., the face centroid of each contact or a point associated with each contact), or the face centroid of two or more contacts detected on touch-sensitive display system 112. However, similar operations, along with a focus selector, are optionally performed on a device having display 450 and separate touch-sensitive surface 451 in response to detecting contacts on touch-sensitive surface 451 while displaying the user interface shown in the figures on display 450.

[0178] 5A-5E illustrate exemplary user interfaces with adjustable controls, according to some embodiments.

[0179] 5A, user interface 5002 includes a first adjustable control 5004 and a second adjustable control 5006. For example, user interface 5002 is a user interface for a music player application, with first adjustable control 5004 being a playback position adjustment control and second adjustable control 5006 being a volume adjustment control. In some embodiments, user interface 5002 includes a previous track control 5008 (e.g., to start playback from the beginning of the current track and / or previous track), a pause / play control 5010 (e.g., to pause and / or play the current track), and a next track control 5012 (e.g., to play the next track).

[0180] 5B-1, 5B-2, 5C-1, 5C-2, and 5C-3 show the portion 5014 of the user interface 5002 shown in dotted lines in FIG. 5A.

[0181] 5B-1, the contact moves in a drag gesture across first adjustable control 5004 from a first position indicated by focus selector 5016a to a second position indicated by focus selector 5016b along the path indicated by arrow 5018. For example, the drag gesture moves playhead 5020 forward along playback position slider 5021 to adjust the playback position within the media file (e.g., an audio track).

[0182] FIG. 5B-2 illustrates tactile outputs generated when the drag gesture illustrated in FIG. 5B-2 occurs, according to some embodiments. Each line shown along row 5020 corresponding to the first adjustable control 5004 in FIG. 5B-1 represents a discrete tactile output (e.g., a haptic event that causes a tap sensation experienced by a contact, such as a finger, at the location indicated by the focus selector 5016). The length of the line in row 5022 (e.g., line 5023) represents the amplitude of the tactile output event, and the spacing between lines in row 5022 indicates the distribution of the tactile output along the adjustable control (e.g., corresponds to the frequency with which tactile output events occur when the focus selector is moved across the adjustable control at a constant velocity). When a contact is dragged across row 5022 along the path indicated by arrow 5018, a series of tactile outputs corresponding to the first adjustable control 5004 (e.g., tactile outputs represented by the lines shown in brackets 5024) is provided. The tactile outputs corresponding to the first adjustable control 5004 are evenly spaced, with each tactile output in the series having the same amplitude.

[0183] 5C-1, the contact moves in a drag gesture across the second adjustable control 5006 from a first position indicated by focus selector 5026a to a second position indicated by focus selector 5026b along the path indicated by arrow 5028. For example, the drag gesture moves the volume control 5030 in the volume slider 5032 forward, increasing the sound level at which the media is played.

[0184] FIG. 5C-2 illustrates a series of tactile outputs generated when the drag gesture illustrated in FIG. 5C-1 occurs, according to some embodiments. Each line shown along row 5034 corresponding to the second adjustable control 5006 in FIG. 5C-1 represents a discrete tactile output. The length of the lines in row 5034 increases from left to right, indicating that the amplitude of the tactile output events increases as the focus selector moves from left to right. As a contact is dragged across row 5034 along the path indicated by arrow 5028, a series of tactile outputs corresponding to the second adjustable control 5006 (e.g., tactile outputs represented by the lines shown within brackets 5036) are provided. As shown in 5C-2, the tactile outputs corresponding to the second adjustable control 5006 occur at evenly spaced intervals and gradually increase in amplitude.

[0185] FIG. 5C-3 illustrates a series of tactile outputs generated when the drag gesture illustrated in FIG. 5C-1 occurs, according to some embodiments. Each line shown along row 5040 corresponding to the second adjustable control 5006 in FIG. 5C-1 represents a discrete tactile output. The spacing between the lines in row 5040 decreases from left to right, indicating that the distribution of tactile output events along the second adjustable control 5006 (e.g., corresponding to the frequency at which tactile output events occur when the focus selector is moved at a constant velocity across the adjustable control) increases as the focus selector moves from left to right. As a contact is dragged across row 5040 along the path indicated by arrow 5028, a series of tactile outputs corresponding to the second adjustable control 5006 (e.g., tactile outputs represented by the lines shown within brackets 5040) are provided. As shown in FIG. 5C-3, the tactile outputs corresponding to the second adjustable control 5006 have the same amplitude and occur at gradually decreasing time intervals.

[0186] In some embodiments, tactile outputs are provided for the previous track control 5008, the pause / play control 5010, and / or the next track control 5012, as shown, for example, at 5042, 5044, 5046, and 5048 in 5C-2 and 5C-3. For example, in some embodiments, when an input is detected in the previous track control 5008, a single tap is provided as shown at 5042. In some embodiments, when an input is detected in the next track control 5012, a single tap is provided as shown at 5048. In some embodiments, some tactile outputs provided by the controls are based on some state of the controls. For example, in some embodiments, a two-state control such as pause / play control 5010 provides a tactile output having a first tactile output profile (e.g., a tactile output including a first intensity) when the state of the control changes from pause to play, as shown at 5044, and provides a second tactile output profile (e.g., a tactile output of a second intensity greater than the first intensity and / or including a spring vibration effect) when the state of the control changes from play to pause, as shown at 5046.

[0187] 5D-1 and 5D-2 illustrate tactile outputs provided at the endpoints of the adjustable control 5004. In some embodiments, one or more endpoint tactile outputs are provided when the endpoint of the adjustable control is reached. In this manner, the user may be provided with feedback indicating, for example, a minimum or maximum point reached by the adjustable control, such as the beginning or end of a media file. For example, when the playhead 5020 is dragged to the left endpoint 5050 of the playback position slider 5021, as indicated by the focus selector 5052 shown in FIG. 5D-1, a tactile output 5054 is provided, as shown in FIG. 5D-2. Compared to other tactile outputs of the adjustable control 5004 (such as the tactile output shown in bracket 5056), the left endpoint tactile output 5058 has at least one different characteristic, such as a higher amplitude. When the playhead 5020 is dragged to the right endpoint 5060 of the playback position slider 5021, a right endpoint tactile output 5062 is provided. Compared to the other tactile outputs of adjustable control 5004 (such as the tactile output shown in bracket 5056), right end tactile output 5062 has a higher amplitude.

[0188] 5E-1 and 5E-2 show tactile outputs provided at chapter markers for media content. In FIG. 5E-1, a contact moves in a drag gesture across adjustable control 5070 from a first position indicated by focus selector 5072a to a second position indicated by focus selector 5072b along the path indicated by arrow 5074. For example, the drag gesture moves playhead 5076 forward along playback position slider 5078 to adjust the playback position within a media file (e.g., an audiobook).

[0189] FIG. 5E-2 illustrates a series of tactile outputs generated when the drag gesture illustrated in FIG. 5E-1 occurs, according to some embodiments. Each line shown along row 5084 corresponding to the second adjustable control 5070 in FIG. 5E-1 represents a discrete tactile output. Lines at positions in row 5084 corresponding to chapter markers (e.g., line 5080) are longer than lines that do not correspond to chapter markers (e.g., line 5082), indicating that the amplitude of the tactile output event is greater at the chapter marker locations than at locations that do not correspond to chapter markers. As a contact is dragged across row 5084 along the path indicated by arrow 5074, a series of tactile outputs corresponding to the adjustable control 5070 is provided, including high-amplitude tactile outputs corresponding to chapter markers 5086, 5088, 5090, and 5092.

[0190] 5F-5K illustrate tactile outputs that vary based on the characteristic intensity of a contact. In FIG. 5F, a contact is detected on touch-sensitive display system 112 at the location indicated by focus selector 5100. The location of focus selector 5100 within user interface 5102 (e.g., an email inbox interface) corresponds to a content item (e.g., a preview of email content). The characteristic intensity of the contact, as indicated by intensity meter 5104, exceeds detection threshold intensity IT0 and hint threshold intensity IT H falls below.

[0191] In FIG. 5G, the characteristic intensity of the contact indicated by focus selector 5100 is adjusted to a hint threshold intensity level IT, as shown by intensity meters 5104a, 5104b, 5104c, and 5104d, which correspond to user interfaces 5102a, 5102b, 5102c, and 5102d, respectively. H After the pressure threshold strength level IT OP The tactile output provided as the characteristic intensity of the contact increases is illustrated by tactile output graph 5106.

[0192] In user interface 5102a, the contact is at a location indicated by focus selector 5100, which corresponds to panel 5108 containing a representation of content. For example, the representation of content may be a short preview of an email in an email inbox. The characteristic intensity of the contact indicated by focus selector 5100 is greater than or equal to the hint threshold intensity level IT, as shown in 5104a. H 5104b, the intensity level increases from an initial intensity level below a light pressure intensity threshold level IT L When the tactile output profile is near the IT L For example, as shown in 5110, as the characteristic intensity of the contact increases between time t0 and time t1, the characteristic of the tactile output increases (e.g., the amplitude and / or distribution of the tactile output of the vibrotactile output increases from zero, or the peak amplitude of a sequence of discrete tactile outputs gradually increases as the intensity of the contact increases). H From IT L The user interface transitions that occur when the number of rows increases to 1 are shown in more detail in FIG. 5H.

[0193] The characteristic strength of the contact is at the light pressure strength threshold level IT L , a tactile output including a second tactile output profile, such as a discrete tap, is generated. For example, at time t1, as shown in 5104b, the characteristic intensity of the contact increases above a first intensity criterion (e.g., a light pressure intensity threshold level IT L , an increase above 5112 is met, a first discrete tap is generated, as shown at 5112. In some embodiments, if the characteristic intensity of the contact meets a light pressure intensity threshold level IT L, a preview of the information corresponding to panel 5108 is shown in preview area 5114 of user interface 5102b. For example, preview area 5114 is a preview platter displayed in or on user interface 5102b. In this example, preview area 5114 of user interface 5102b displays a longer (e.g., extended) preview of the email that corresponds to the shorter preview of the email shown in panel 5108 of user interface 5102a. In some embodiments, user interface 5102b is blurred except for preview area 5114, as shown at 5116.

[0194] The characteristic intensity of the contact indicated by focus selector 5100 is adjusted to a light pressure threshold intensity level IT, as shown at 5104b. L 5104c, the intensity increases from above the deep pressure intensity threshold level IT D When the tactile output profile is reached, the tactile output profile is increased by 100%. D t1 to t2. For example, as shown in 5118, as the characteristic intensity of the contact increases between time t1 and time t2, the characteristic tactile output increases (e.g., the amplitude and / or frequency of the vibrotactile output increases from zero, or the peak amplitude of a sequence of discrete tactile outputs gradually increases as the intensity of the contact increases). In some embodiments, the characteristic intensity of the contact increases with intensity I L Intensity I increases from D , the preview area 5114 gradually expands from a first area (e.g., as shown in 5102b) to a second area (e.g., approaching a full-screen view of the content, as shown in 5102c).

[0195] The characteristic strength of the contacts meets a second strength criterion (e.g., a deep pressure strength threshold level IT D , a tactile output comprising a fourth tactile output profile is generated. For example, at time t2, as shown in 5104c, the characteristic intensity of the contact increases above the deep pressure intensity threshold level IT D, a second discrete tap is generated, as shown at 5120. In some embodiments, when the characteristic intensity of the contact increases above a deep pressure intensity threshold level IT D , the preview area 5114 is no longer displayed, and instead the user interface 5102c corresponding to the previously previewed content is displayed (e.g., an email is shown in the user interface for viewing emails).

[0196] The characteristic strength of the contact is at the overpressure strength threshold level IT OP , a tactile output comprising a fifth tactile output profile is generated. For example, at time t3, as shown in 5104d, the characteristic intensity of the contact increases above the overpressure intensity threshold level IT OP , a third discrete tap is generated, as shown at 5122. In some embodiments, if the characteristic intensity of the contact increases above an overpressure intensity threshold level IT OP When the characteristic intensity of the contact increases above the contact detection threshold level IT0, the previously displayed user interface is re-displayed. In some embodiments, the re-displayed user interface is the user interface that was displayed when the characteristic intensity of the contact was first detected (e.g., when the characteristic intensity of the contact rose above the contact detection threshold level IT0). For example, as shown in user interface 5102a, the email inbox, including a short preview of the email, is re-displayed in user interface 5102d.

[0197] 5H illustrates a user interface transition corresponding to an increase in the intensity of the detected contact from intensity level I0 to intensity level I1 (as shown in the area surrounded by dotted line 5124 in FIGS. 5G and 5H). In FIG. 5H, the characteristic intensity of the contact indicated by focus selector 5100 increases to a hint threshold intensity level IT, as shown in intensity meters 5104a, 5104a-2, 5104a-3, and 5104b, which correspond to user interfaces 5102a, 5102a-2, 5102a-3, and 5102b, respectively. H After the light pressure threshold intensity level IT L increases until it exceeds

[0198] In some embodiments, user interfaces 5102a-2 and 5102a-3 may be configured to detect whether the characteristic intensity of the contact indicated by focus selector 5100 is greater than or equal to a hint threshold intensity level IT H Above the light pressure threshold intensity level IT L In user interface 5102a, focus selector 5100 is in a position corresponding to panel 5108 containing a representation of content (e.g., a short preview of an email in an email inbox). H It has exceeded and increased, L , the user interface except for panel 5108 becomes blurred, the area of ​​panel 5108 increases, the size of the content in panel 5108 increases, and / or the size of the content in the user interface outside of panel 5108 decreases. The blurring and resizing effect continues for a period of time t as shown by intensity meters 5104a-2 and 5104a-3 and user interfaces 5102a-2 and 5102a-3, respectively. 0.3 and time t 0.6 increases as the characteristic strength of the contact between

[0199] In FIG. 5I, the characteristic intensity of the contact indicated by focus selector 5100 is a light pressure threshold intensity level IT L In user interface 5126a, the contact is at the location indicated by focus selector 5100, which corresponds to panel 5108 containing a representation of content. At time t, the characteristic intensity of the contact indicated by focus selector 5100 reaches a hint threshold intensity level IT, as shown in user interface 5126a and intensity meter 5128a. H At time t1, the characteristic intensity of the contact, as shown on user interface 5126b and intensity meter 5128b, falls below the hint threshold intensity level IT HAt time t2, the characteristic intensity of the contact indicated by focus selector 5100 increases above a threshold intensity level IT, as indicated on user interface 5126c and intensity meter 5128c. L When the characteristic intensity of the contact increases after time t0, a tactile output is generated that includes a first output profile (e.g., the characteristic intensity of the tactile output increases as shown at 5110). H It has exceeded and increased, L As the touch approaches the light pressure intensity threshold level IT, the user interface 5126b, excluding the panel 5108, becomes blurred, the area of ​​the panel 5108 increases, the size of the content in the panel 5108 increases, and / or the size of the content in the user interface outside the panel 5108 decreases. At time t, a discrete tap is generated as shown at 5112. When the characteristic intensity of the contact approaches the light pressure intensity threshold level IT, L , as shown in intensity level meter 5128c at time t2, a preview of the information corresponding to panel 5108 is shown in preview area 5114 of user interface 5126c. As shown in user interface 5126d and intensity meter 5128d, thereafter (e.g., at time t3), the characteristic intensity of the contact indicated by focus selector 5100 increases above a threshold intensity level IT L When the characteristic intensity of the contact indicated by the focus selector 5100 falls below a threshold intensity level IT L In accordance with a determination that a decrease in the characteristic intensity of the contact is detected after increasing above , the tactile output including the first output profile is discontinued and preview region 5114 is maintained on the display, as shown in user interface 5126d.

[0200] In FIG. 5J, the characteristic intensity of the contact indicated by focus selector 5100 is a light pressure threshold intensity level IT LIn user interface 5130a, the contact is at the location indicated by focus selector 5100, which corresponds to panel 5108 containing a representation of content. At time t, the characteristic intensity of the contact indicated by focus selector 5100 reaches a hint threshold intensity level IT, as shown in user interface 5130a and intensity meter 5132a. H At time t1, the characteristic intensity of the contact falls below the hint threshold intensity level IT, as shown on user interface 5130b and intensity meter 5132b. H The characteristic strength of the contact increases above IT H It has exceeded and increased, L As time t approaches, the user interface except for panel 5108 becomes blurred, the area of ​​panel 5108 increases, the size of the content in panel 5108 increases, and / or the size of the content in the user interface outside of panel 5108 decreases. At time t, the characteristic intensity of the contact indicated by focus selector 5100, as shown on user interface 5130c and intensity meter 5132c, approaches a threshold intensity level IT L without reaching the threshold intensity level IT H , and continues to increase beyond the threshold intensity level IT. As the characteristic intensity of the contact increases after time t0, a tactile output comprising a first output profile is generated (e.g., the characteristic tactile output increases as shown at 5110). Thereafter (e.g., at time t3), the characteristic intensity of the contact indicated by focus selector 5100 decreases, as shown in user interface 5130d and intensity meter 5132d. The decrease in the characteristic intensity of the contact indicates that the characteristic intensity of the contact meets the intensity criteria (e.g., exceeds the threshold intensity level IT L tactile output including the first output profile is adjusted to a threshold intensity level IT of the characteristic intensity of the contact in accordance with a determination that the characteristic intensity of the contact has been detected before the characteristic intensity of the contact increases above a threshold intensity level IT LAs the characteristic intensity of the contact decreases, the area of ​​panel 5108 decreases, the size of the content of panel 5108 decreases, and / or the size of the content of the user interface outside of panel 5108 increases, as shown, for example, in user interface 5130d.

[0201] In some embodiments, the set of tactile output profiles shown in FIG. 5K may be generated based on a characteristic intensity of contact with touch-sensitive display system 112 exceeding an overpressure intensity threshold level IT OP At times t0-t3, the characteristic intensity of the contact increases above the hint threshold intensity level IT, as shown at 5134a, 5134b, 5134c, and 5134d, respectively. H After the pressure intensity threshold level IT OP Between times t0 and t3, a tactile output having increasing parameters (e.g., amplitude and / or distribution of the tactile output) is provided, as shown at 5136. At time t4, the characteristic intensity of the contact increases to above the overpressure intensity threshold level IT, as shown at 5134e. OP , a discrete tap occurs as shown at 5138. When the characteristic intensity of the touch increases above the intensity threshold level IT, as shown at 5134f. OP , a tactile output having fixed parameters (eg, a fixed amplitude and / or distribution of the tactile output) is provided, as shown at 5140.

[0202] 5L-5N illustrate a series of tactile outputs corresponding to the selection and movement of an application icon and the movement of the selected application icon. In FIG. 5L, contact is detected on touch-sensitive display system 112 at a location indicated by focus selector 5150. In some embodiments, application icon 5152 is selected pursuant to a determination that the selection criteria have been met (e.g., focus selector 5150 is at a location corresponding to application icon 5152 for an amount of time that exceeds a threshold duration, e.g., 1 second). In some embodiments, once application icon 5152 is selected, movement of focus selector 5150 across touch-sensitive display system 112 moves application icon 5152, as shown in FIGS. 5M and 5N. In some embodiments, once application icon 5152 is not selected, movement of focus selector 5150 across touch-sensitive display system 112 moves multiple application icons within user interface 5154, as shown in FIG. 5O.

[0203] 5M , a selected application icon is moved over another application icon. At an initial time T=t0, a contact is detected on touch-sensitive display system 112 when focus selector 5150 is at a position corresponding to application icon 5152. At a later time T=t1, focus selector 5150 remains at application icon 5152 for an amount of time that results in selection of application icon 5152. In some embodiments, a tactile output is generated at the time the application icon becomes selected to provide an indication to the user that the application icon has been selected. For example, as shown in tactile output graph 5156, discrete tap 5158 is generated at time t1, when application icon 5152 becomes selected. In some embodiments, a series of tactile outputs (e.g., a series of taps 5157, such as a series of taps including a lower amplitude than the amplitude of discrete tap 5158) is generated while application icon 5152 is selected, as shown at times t1-t4 in tactile output graph 5156. In some embodiments, one or more visual indications are displayed while the application icon 5152 is selected, such as highlighting the application icon 5152 (e.g., a shaded application icon 5152 as shown in user interfaces 5154b, 5154c, and 5154d) and animating one or more application icons in the user interface 1514 (e.g., a vibrating animation as shown in 5160).

[0204] When application icon 5152 is selected, it is "picked up" by focus selector 5150 such that application icon 5152 moves in accordance with the movement of focus selector 5150. At time T=t2, focus selector 5150 and application icon 5152 are moving left toward stocks application icon 5160. At time T=t3, application icon 5152 passes over stocks application icon 5160. In some embodiments, when application icon 5152 overlaps stocks application icon 5160 (e.g., to a predetermined degree), discrete tap 5164 is generated to indicate to the user that application icon 5152 is passing over stocks application icon 5160 (e.g., as shown at t3 in tactile output graph 5156).

[0205] At time T=t4, lift-off of the contact from the touch-sensitive surface is detected. In response to lift-off of the contact, application icon 5152 is deselected. In some embodiments, once the application icon is no longer selected, discrete tap 5166 is generated to indicate to the user that deselection of application icon 5152 has occurred (e.g., as shown at t4 in tactile output graph 5156).

[0206] 5N , the selected application icon is moved into a folder. At an initial time T=t0, when focus selector 5150 is in a position corresponding to application icon 5153, a contact is detected on touch-sensitive display system 112, as shown in user interface 5180a. At a later time T=t1, focus selector 5150 remains over application icon 5178 for an amount of time that results in selection of application icon 5178, as shown in user interface 5180b. In some embodiments, a tactile output is generated at the time the application icon becomes selected to provide an indication to the user that the application icon has been selected. For example, as shown in tactile output graph 5168, discrete tap 5170 is generated at time t1, when application icon 5178 becomes selected. In some embodiments, a series of tactile outputs (e.g., a series of taps 5167, such as a series of taps including an amplitude lower than the amplitude of discrete tap 5170) is generated while application icon 5178 is selected, as shown in tactile output graph 5168 starting at time t1.

[0207] At time T=t2, focus selector 5150 and application icon 5178 move to the left, passing over map application icon 5182, as shown in user interface 5180c. In some embodiments, as shown in graph 5168, a discrete tap 5172 is generated at time t2 to indicate that application icon 5178 has passed over map application icon 5182.

[0208] At time T=t3, application icon 5178 enters a region corresponding to folder icon 5184, which contains stocks application icon 5186 and news application icon 5188, as shown in user interface 5180d. In some embodiments, as shown in graph 5168, discrete tap 5174 is generated at time t3 to indicate that application icon 5178 has entered a region corresponding to folder 5184. In some embodiments, discrete tap 5174 is different (e.g., has a larger amplitude) than discrete tap 5172, which occurs when application icon 5178 passes over maps application icon 5182, to provide an indication that application icon 5178 has encountered a user interface object other than an application icon (e.g., application icon 5178 has encountered folder 5184 rather than another application icon).

[0209] At time T=t4, after application icon 5178 hovers over folder 5184 for a predetermined time, an expanded view of folder 5184 is displayed, as shown in user interface 5180e. In some embodiments, once folder 5184 is displayed, the user interface displayed in 5180d is no longer displayed. In some embodiments, as shown at time t4 in graph 5168, discrete tap 5176 is generated to indicate to the user that application icon 5178 has moved into folder 5184. In some embodiments, discrete tap 5176 associated with displaying application icon 5178 in folder 5184 is different (e.g., has a greater amplitude) than discrete tap 5172, which occurs when application icon 5178 passes over map application icon 5182.

[0210] 5O, no user interface object is selected, so no tactile output is generated as the contact moves across the touch-sensitive surface. At an initial time T=t0, when focus selector 5150 is in a position corresponding to application icon 5152, a contact is detected on touch-sensitive display system 112, as shown in user interface 5192a. At a later time T=t 0.5 At time T=t1, focus selector 5150 has moved to a new position along the path indicated by arrow 5194, as shown in user interface 5192b. Because focus selector 5150 does not remain at application icon 5152 for the amount of time that would have caused application icon 5152 to be selected, application icon 5152 is not selected. Thus, in response to movement of focus selector 5150 along the path indicated by arrow 5194, multiple application icons, including application icon 5152, move along the path indicated by arrow 5194. At time T=t1, in response to movement of focus selector 5150 along the path indicated by arrow 5196, multiple application icons, including application icon 5152, have moved left, as shown in user interface 5192c. Tactile output graph 5198 illustrates that when an application icon is not selected, no tactile output occurs in response to the movement of a contact across touch-sensitive display system 112.

[0211] Figures 5P-5R show image previews that are displayed as a contact moves along the set of image thumbnails, and a series of tactile outputs that correspond to the movement of the contact along the set of image thumbnails. Figures 5R-1, 5R-2, 5R-3, 5R-4, 5S-1, and 5S-2 show portion 5208 of user interface 5002, as shown by the dotted lines in Figures 5P and 5Q.

[0212] In Figure 5P, a contact is detected by touch-sensitive display system 112 at the location indicated by focus selector 5204. In some embodiments, pursuant to a determination that the preview display criteria are met (e.g., focus selector 5204 is at the location corresponding to image thumbnail 5206a for an amount of time that exceeds a threshold duration, e.g., 1 second), a preview 5206b of the image corresponding to image thumbnail 5206a is displayed, as shown in Figure 5Q. In some embodiments, preview 5206b of the image corresponding to image thumbnail 5206a is a larger view of the image than image thumbnail 5206a. In some embodiments, preview 5206b of the image corresponding to image thumbnail 5206a is displayed below and / or above the location of focus selector 5204. In some embodiments, a tactile output is generated when the preview display criteria are met.

[0213] In some embodiments, once the preview display criteria are met, moving the contact to a location corresponding to another image thumbnail causes a preview of the image corresponding to the other image thumbnail to be displayed, as shown in FIGS. 5R-1, 5R-2, and 5R-3.

[0214] In FIG. 5R-1, the preview display criteria are met, and image preview 5206b corresponding to image thumbnail 5206a is displayed. The contact moves from a first position indicated by focus selector 5204a along a path indicated by arrow 5210 to a second position indicated by focus selector 5204b in FIG. 5R-2. The second position indicated by focus selector 5204b corresponds to the position of image thumbnail 5212a. In accordance with a determination that the contact has moved to the second position, image preview 5212b corresponding to image thumbnail 5212a is displayed. The contact moves from the second position indicated by focus selector 5204b along a path indicated by arrow 5214 to a third position indicated by focus selector 5204c in FIG. 5R-3. The third position indicated by focus selector 5204c corresponds to the position of image thumbnail 5214a. In accordance with a determination that the contact has moved to the third position, image preview 5216b corresponding to image thumbnail 5216a is displayed.

[0215] 5R-4 illustrates tactile outputs provided as a contact moves across touch-sensitive display system 112 to the positions indicated by focus selectors 5204a, 5204b, and 5204c. Points 5218a, 5218b, and 5218c represent discrete tactile outputs that occur when the contact is at the positions indicated by focus selectors 5204a, 5204b, and 5204c, respectively. In this manner, a series of discrete tactile outputs are output as the contact moves across a series of image thumbnails. In some embodiments, a discrete tactile output occurs each time the contact moves over a different image thumbnail.

[0216] In some embodiments, if the preview display criteria are not met, no tactile output is generated. In Figure 5S-1, the preview display criteria are not met (the contact is not at the position indicated by focus selector 5204a for an amount of time that exceeds the threshold duration). Therefore, no preview is displayed. When the contact moves across touch-sensitive display system 112 to the positions indicated by 5204b and 5204c, respectively, no preview is displayed, as shown in Figure 5S-1, and no tactile output occurs, as shown in Figure 5S-2.

[0217] 5T-5U illustrate previews 5220 and 5224 displayed when preview criteria are met and contact is moved across touch-sensitive display system 112 (e.g., vertically) from a first position indicated by focus selector 2226a to a second position indicated by focus selector 2226b, according to some embodiments. In accordance with a determination that the preview display criteria are met, a tactile output is generated (e.g., a discrete tactile output is generated when the contact is at the position indicated by focus selector 2226a and a discrete tactile output is generated when the contact is at the position indicated by focus selector 2226b). In some embodiments, when scrolling criteria different from the preview display criteria are met, movement of the contact moving across touch-sensitive display system 112 (e.g., moving the contact vertically) from the first position indicated by focus selector 2226a to the second position indicated by focus selector 2226b causes multiple image thumbnails displayed in user interface 5202 to scroll (e.g., scroll vertically), as shown in FIGS. 5V-5W.

[0218] 5X-1-5X-3 show simulated object 5232 used to represent communications received by device 100, according to some embodiments. In some embodiments, simulated object 5232 is, for example, a virtual sphere "rolling" across the surface of device 100. The tactile output indicates the movement of simulated object 5232 across device 100 and / or collisions between simulated object 5232 and virtual boundaries, such as boundaries corresponding to one or more edges of touch-sensitive display system 112. The movement of simulated object 5232 and / or collisions between simulated object 5232 and virtual boundaries give the user the impression of some notification of communications received by device 100 (e.g., communications received by device 100 since the user last activated and / or woken up the device).

[0219] In FIG. 5X-1 , device 100 is held flat in user's hand 5230. As the user's hand tilts device 100 from the flat position shown in FIG. 5X-1 to the tilted position shown in FIG. 5X-2, simulated object 5232 moves in response to the device's movement, eventually to the upright position shown in FIG. 5X-3. For example, movement of device 100 to the upright position shown in FIG. 5X-3 causes simulated objects 5232a, 5232b, 5232c, and 5232d to move along paths 5234a, 5234b, 5234c, and 5234d, respectively. In some embodiments, as simulated object 5232 moves along path 5234, device 100 outputs a series of tactile outputs to simulate the movement of object 5232 (e.g., such that the user has the sensation of a virtual sphere rolling across device 100 in response to the tilt occurring between FIG. 5X-1 and FIG. 5X-3). In some embodiments, each time each simulated object 5232 reaches the edge of the touch-sensitive display system y112 of device 100 (e.g., each simulated object 5232 reaches the end of its respective path 5234 as shown in FIG. 5X-3), device 100 outputs a tactile output that simulates a collision of each simulated object 5232 with the edge of the touch-sensitive display system 112 (e.g., so that the user has the sensation of a virtual sphere bouncing off the lower edge 5236 of the touch-sensitive display system 112).

[0220] In some embodiments, each simulated object 5232 has a quality that depends on at least one property of the corresponding notification. For example, simulated objects 5232a, 5232b, and 5232d correspond to received email messages that are not marked "urgent," while simulated object 5232c (shown shaded) corresponds to a received email message that is marked "urgent." A simulated object corresponding to a non-urgent notification has a first property (e.g., a first simulated weight), and a simulated object corresponding to an emergency notification has a second property that is different from the first property (e.g., a second simulated weight that is greater than the first simulated weight, such that a greater tactile output is generated when simulated object 5232c collides with edge 5236). Examples of simulated qualities of simulated objects that vary according to communication type include, for example, speed, acceleration, size, weight, and / or viscosity. Examples of notification properties include, for example, the urgency assigned by the communication sender, the priority assigned to the communication by the user, the type of notification (e.g., text message, phone call, email, calendar invite, reminder, and / or third party application notification), and / or the number of notifications of a type.

[0221] 5Y illustrates a simulated surface texture with which a simulated object 5232 interacts, according to some embodiments. In FIG. 5Y, the simulated surface features 5240 are, for example, virtual bumps, virtual divots, or other texture features. In some embodiments, the number, arrangement, and / or location of the surface features differs from the example illustration of FIG. 5Y.

[0222] Device 100 outputs tactile outputs to simulate collisions of simulated object 5232 with surface features 5240. For example, when device 100 is tilted as shown in FIG. 5Y, simulated objects 5232a, 5232b, 5232c, and 5232d move from right edge 5242 to left edge 5244 along paths 5246a, 5246b, 5246c, and 5246d, respectively. As simulated object 5232a moves along path 5246a, simulated object 5232a encounters surface features 5240a, 5240b, 5240c, 5240d, etc. Each time simulated object 5232 encounters a respective surface feature 5240, device 100 generates a tactile output that provides the user with an impression of an interaction between simulated object 5232a and the respective surface feature 5240. For example, a tactile output may be provided to give the user the impression of one or more simulated objects (eg, virtual spheres) rolling over one or more surface features (eg, virtual bumps).

[0223] 5Z, 5AA and 5BB show tap-based tactile, vibration and audio outputs corresponding to different usage contexts of a device according to some embodiments.

[0224] In some embodiments, the tap-based tactile output is a sequence of discrete tactile output patterns that reach full amplitude and / or maximum velocity within a first number of cycles of the moving mass relative to the actuator (e.g., 1, 2, or 3), and is optionally actively damped to stop moving relative to the actuator instead of gradually oscillating around a rest position (e.g., such as the full-tap, mini-tap, and / or micro-tap described above with reference to FIGS. 4F-4K). Tap-based tactile outputs optionally allow for finer and more accurate control of the parameters of the tactile output than vibration outputs, but provide lower amplitude or shorter tactile outputs (per unit energy) than vibration outputs. In some embodiments, with tap-based tactile outputs, the position of the moving mass is actively monitored to ensure the tap-based tactile output is within precise operating parameters, whereas with vibration outputs, the position of the moving mass is not actively monitored because the operating parameters are less precise. In some embodiments, the vibratory output is a vibratory tactile output that gradually increases in amplitude over a second number of cycles of the mass moving relative to the actuator (e.g., 5, 10, 15), and then gradually decreases in amplitude over multiple cycles of the mass moving relative to the actuator. The vibratory output optionally allows for longer and higher amplitude tactile outputs (e.g., per unit of energy input), instead of the finer control provided by tap-based tactile outputs.

[0225] 5Z , device 100 is operating in a first usage context, e.g., in a user's hand 5230. Device 100 is receiving an incoming communication (a phone call from Neil). In some embodiments, device 100 outputs a tap-based tactile output, a vibration output, and / or an audio output (e.g., a ringtone) to alert the user of the incoming communication. While device 100 is in the user's hand 5230, device 100 outputs a first ongoing tactile output (e.g., a series of discrete taps, as shown in the graph labeled "Tap-Based Tactile Output"), a first ongoing vibration output (e.g., vibrations occurring at periodic intervals, as shown in the graph labeled "Vibration Output"), and a first ongoing audio output (e.g., an audio waveform, as shown in the graph labeled "Audio Output").

[0226] In FIG. 5AA, device 100 is operating in a second usage context, for example, in a user's pocket 5250. When device 100 receives an incoming communication while in the user's pocket 5250, device 100 outputs a second ongoing tap-based tactile output. The series of discrete taps shown in the tap-based tactile output graph of FIG. 5AA occurs at a higher frequency than the series of discrete taps shown in FIG. 5Z. When device 100 receives an incoming communication while in the user's pocket 5250, device 100 outputs a second ongoing vibration output. The vibrations in the vibration output graph of FIG. 5AA occur at shorter intervals than the vibrations in FIG. 5Z. When device 100 receives an incoming communication while in the user's pocket 5250, device 100 outputs a second ongoing audio output. The audio waveform in the audio output graph of FIG. 5AA has a higher amplitude than the amplitude of the audio waveform in FIG. 5Z. In this way, the audibility of the audio output is increased so that the user can hear it despite any reduction in sound absorption and / or sound transmission caused by the second context (e.g., reduction in sound absorption and / or sound transmission caused by the pocket in which device 100 is operating).

[0227] In FIG. 5BB, device 100 is operating in a third usage context, for example, lying on table 5252. When device 100 receives an incoming communication while on table 5252, device 100 outputs a third ongoing tap-based tactile output. The series of discrete taps shown in the tap-based tactile output graph of FIG. 5BB occurs at a lower frequency than both the series of discrete taps shown in FIG. 5Z and the series of discrete taps shown in FIG. 5AA. When device 100 receives an incoming communication while on table 5252, device 100 does not generate a vibration output. When device 100 receives an incoming communication while on table 5252, device 100 outputs a third ongoing audio output. The audio waveform in the audio output graph of FIG. 5BB periodically decays, as shown at 5254.

[0228] In some embodiments, device 100 uses one or more sensors to determine when the usage context has changed (e.g., from a user's pocket 5250, as shown in FIG. 5AA, to a user's hand 5230, as shown in FIG. 5Z). When device 100 is in a user's pocket 5250, the user may desire a louder audio output, more frequent vibration bursts, and / or higher frequency taps to compensate for the sound-deadening effect of storage in pocket 5250. When device 100 is in the user's hand 5230 (e.g., when the user removes device 100 from pocket 5250 and holds the device outdoors), the user may desire a quieter output, less frequent vibration bursts, and / or lower frequency taps to avoid excessive noise. When device 100 is lying flat on a table 5252, the user may desire a dampened audio output, no vibration, and / or very low frequency taps to avoid excessive rattle of device 100 on the table.

[0229] 5CC-5OO illustrate exemplary operations of electronic device 100 providing audio and / or tactile feedback according to some embodiments.

[0230] FIG. 5CC shows electronic device 100 detecting an alert event (e.g., electronic device 100 generating and / or receiving instructions to generate an alert in response to an incoming call, the passage of a preselected time interval, or the arrival of a particular time) and updating (5456) its display accordingly (e.g., displaying a user interface corresponding to telephone module 138).

[0231] 5CC also shows that audio and / or tactile feedback is not provided until after electronic device 100 determines (5458) the usage context of electronic device 100. For example, in some embodiments, when electronic device 100 updates its display (5456), electronic device 100 ceases providing audio and / or tactile feedback (and then provides audio and / or tactile feedback thereafter once the determination is made).

[0232] After detecting the alert event, electronic device 100 determines a usage context of electronic device 100 (5458). In some embodiments, electronic device 100 determines whether electronic device 100 is in a first usage context (e.g., a context in which a user of electronic device 100 is determined to be paying attention to electronic device 100, such as a situation in which electronic device 100 is being held by a user and actively receiving user input) or a second usage context (e.g., a context in which a user of electronic device 100 is determined to be not paying attention to electronic device 100, such as a situation in which electronic device 100 is being held by a user and actively receiving user input). For example, electronic device 100 determines which usage context electronic device 100 is in between the first usage context and the second usage context (e.g., electronic device 100 is in one of only two usage contexts, including the first usage context and the second usage context). In some embodiments, electronic device 100 determines which of three or more usage contexts electronic device 100 is in, including a first usage context and a second usage context. In some embodiments, it is determined that a user is paying attention to the device based on one or more sensor inputs (e.g., according to a determination that the user's face is within the field of view of the device's camera, according to a determination that the device's user's gaze is directed toward the device's display based on image data from the device's camera, according to a determination that the device has been or is being lifted based on the device's accelerometer or gyroscope, or according to a determination that the device has been or is being removed from a pocket, bag, or other enclosure based on a proximity sensor or camera).In some embodiments, it is determined that the user is not paying attention to the device based on one or more sensor inputs (e.g., according to a determination that the user's face is not within the field of view of the device's camera; according to a determination based on image data from the device's camera that the device's user's gaze is not directed at the device's display; according to a determination based on the device's accelerometer or gyroscope that the device is detected as remaining stationary for more than a threshold amount of time indicating that it is not being held by the user; and / or according to a determination based on the device's proximity sensor or camera that the device was or is in a pocket, bag, or other enclosure).

[0233] In accordance with a determination that the electronic device 100 is in a first usage context (e.g., a context in which a user of the electronic device 100 is determined to be paying attention to the electronic device 100), the electronic device 100 provides (5460) a first feedback (e.g., a first audio output and / or a first tactile output) to indicate an alert event.

[0234] In response to a determination that the electronic device 100 is in a second usage context (e.g., a context in which it is determined that the user of the electronic device 100 is not paying attention to the electronic device 100), the electronic device 100 provides (5462) second feedback (e.g., a second audio output and / or a second tactile output) to indicate the alert event.

[0235] The second feedback is separate from the first feedback (e.g., the second audio output is separate from the first audio output and / or the second tactile output is separate from the first tactile output). For example, while electronic device 100 is in the second usage context (e.g., a user of electronic device 100 is not paying attention to electronic device 100), electronic device 100 provides the second audio output and / or the second tactile output to attract the user's attention, and while device 100 is in the first usage context (e.g., a user of electronic device 100 is paying attention to electronic device 100), electronic device 100 provides reduced audio and / or tactile feedback (e.g., the first audio output and / or the first tactile output) because the volume of the second audio output and / or the amplitude of the second tactile output are not needed to attract the user's attention. Because the user is already paying attention to the electronic device 100, a first audio output having a lower volume than the second audio output and / or a first tactile output having a lower amplitude than the second tactile output is provided while the electronic device 100 is in the first usage context.

[0236] 5DD illustrates that, in some embodiments, following initiation of providing the second feedback (5462), electronic device 100 again determines (5464) the usage context of electronic device 100. For example, while electronic device 100 is providing the second feedback, electronic device 100 continues to monitor whether electronic device 100 has transitioned from the second usage context to the first usage context (e.g., while electronic device 100 is providing the second feedback, electronic device 100 repeats determining whether a user who was not paying attention to the device is now paying attention to the device).

[0237] FIG. 5DD also shows that, pursuant to a determination that the electronic device 100 remains in the second usage context, the electronic device 100 continues to provide the second feedback (e.g., while the electronic device 100 remains in the second usage context, the electronic device 100 continues to provide the second feedback until a feedback termination criterion is met, such as outputting a ringtone at a predetermined number of times or at a predetermined time interval).

[0238] FIG. 5DD further shows that, in accordance with determining that electronic device 100 has transitioned from the second usage context to the first usage context, electronic device 100 transitions from providing second feedback (5462) to providing first feedback (5460) (e.g., electronic device 100 stops providing second feedback and starts providing first feedback).

[0239] FIG. 5EE illustrates a second feedback provided by electronic device 100. The second feedback includes a second audio output and / or a second tactile output (e.g., a second tap-based tactile output and / or a second vibration output). The second audio output has a second audio amplitude (greater than the first audio amplitude of the first audio output shown in FIG. 5FF). In FIG. 5EE, the second tactile output includes a plurality of discrete tactile output components 5470 (e.g., tap-based tactile output components) having a second tactile output amplitude (e.g., the full taps shown in FIGS. 4F and 4I) and a second time interval. In FIG. 5EE, the second tactile output also includes a vibration output.

[0240] FIG. 5FF illustrates a first feedback provided by electronic device 100. The first feedback includes a first audio output and / or a first tactile output (e.g., a first tap-based tactile output and / or a second vibration output). The first audio output has a first audio amplitude that is less than the second audio amplitude of the second audio output (as shown in FIG. 5EE). In FIG. 5FF, the first tactile output includes a plurality of discrete tactile output components 5472 (e.g., tap-based tactile outputs) having a first tactile output amplitude that is less than the second tactile output amplitude (e.g., mini-taps or micro-taps shown in FIGS. 4G-4H and 4J-4K) and a first time interval that is shorter than the second time interval (e.g., the first tactile output has a higher frequency of the discrete tap-based tactile output than the second tactile output). In FIG. 5FF, the first tactile output does not include a vibration output. However, in some other embodiments, the first tactile output includes a vibration output.

[0241] FIG. 5GG illustrates electronic device 100 transitioning from providing second feedback to first feedback, according to some embodiments. In FIG. 5GG, the tap-based tactile output changes from a second tap-based tactile output (having a second tap-based tactile output amplitude) to a first tap-based tactile output (having a first tap-based tactile output amplitude that is less than the second tap-based tactile output amplitude). FIG. 5GG also illustrates electronic device 100 transitioning from providing a vibration output as part of the second tactile output to ceasing to provide the vibration output, such that the first tactile output does not include the vibration output. FIG. 5GG further illustrates electronic device 100 transitioning from providing a second audio output having a second audio amplitude to providing a first audio output having a first audio amplitude that is less than the second audio amplitude. As shown in FIG. 5GG, the audio output gradually changes (e.g., linearly or nonlinearly) from the second amplitude to the first amplitude over a first time period t1. The tactile output (including the tap-based tactile output) changes from the second tactile output to the first tactile output over a second period t2 that is shorter than the first period t1. In some embodiments, as shown in FIG. 5GG, electronic device 100 transitions from determining that electronic device 100 has transitioned from the second usage context to the first usage context to providing the first audio output over a period of time t1' from determining that electronic device 100 has transitioned from the second usage context to the first usage context, and transitions from determining that electronic device 100 has transitioned from the second usage context to the first usage context to providing the first tactile output over a period of time t2' that is shorter than the period of time t1'. Instead of immediately transitioning from providing the second audio output to providing the first audio output, electronic device 100 gradually transitions from providing the second audio output to providing the first audio output over a period of time, thereby providing a smooth audio transition from the second audio output to the first audio output and providing an improved user experience.

[0242] 5HH-5KK illustrate exemplary tap-based tactile outputs for a first and second use context according to some embodiments.

[0243] 5HH illustrates that tap-based tactile output 5502 is provided while electronic device 100 is in a second usage context (e.g., a context in which a user of the device is determined to be not paying attention to the device) and tap-based tactile output 5504 is provided while electronic device 100 is in a first usage context (e.g., a context in which a user of the device is determined to be paying attention to the device). Tap-based tactile output 5502 includes multiple tap-based tactile output components having a second tactile output amplitude (e.g., full taps as shown in FIGS. 4F and 4I) and a second time interval. Tap-based tactile output 5504 includes multiple tap-based tactile output components having a first tactile output amplitude (e.g., mini- or micro-taps as shown in FIGS. 4G-4H and 4J-4K) that is smaller than the second tactile output amplitude and the same second time interval.

[0244] FIG. 5HH also illustrates the transition from providing tap-based tactile output 5502 to providing tap-based tactile output 5504 as electronic device 100 transitions from the second usage context to the first usage context.

[0245] 5II shows that tap-based tactile output 5512 is provided while electronic device 100 is in a second use context (e.g., a context in which a user of the device is determined to be not paying attention to the device) and tap-based tactile output 5514 is provided while electronic device 100 is in a first use context (e.g., a context in which a user of the device is determined to be paying attention to the device). Tap-based tactile output 5512 includes a plurality of tap-based tactile output components 5516 having a second tactile output amplitude (e.g., the full taps shown in FIGS. 4F and 4I) and a second time interval. Tap-based tactile output 5514 includes a plurality of tap-based tactile outputs having a first time interval that is shorter than the second time interval (e.g., tap-based tactile output 5514 has a higher frequency of tap-based tactile output components than tap-based tactile output 5512). Specifically, tap-based tactile output 5514 includes a plurality of tap-based tactile output components 5516, and also includes a plurality of tap-based tactile output components 5518 (e.g., mini-taps or micro-taps shown in Figures 4G-4H and 4J-4K) between tap-based tactile output components 5516, each having a first tactile output amplitude that is less than a second tactile output amplitude.

[0246] FIG. 5II also shows the transition from providing tap-based tactile output 5512 to providing tap-based tactile output 5514 as electronic device 100 transitions from the second usage context to the first usage context.

[0247] 5JJ illustrates that tap-based tactile output 5522 is provided while electronic device 100 is in a second use context (e.g., a context in which a user of the device is determined to be not paying attention to the device) and tap-based tactile output 5524 is provided while electronic device 100 is in a first use context (e.g., a context in which a user of the device is determined to be paying attention to the device). Tap-based tactile output 5522 includes multiple tap-based tactile output components 5526 and 5528 having a second tactile output amplitude (e.g., the full taps shown in FIGS. 4F and 4I). Tap-based tactile output 5524 includes multiple tap-based tactile output components 5526 and also multiple tap-based tactile output components 5530, 5532, and 5534 having a first tactile output amplitude that is less than the second tactile output amplitude (e.g., the mini-taps or micro-taps shown in FIGS. 4G-4H and 4J-4K). Specifically, tap-based tactile output component 5528 having the second tactile output amplitude is replaced with tap-based tactile output component 5532 having the first tactile output amplitude (e.g., tap-based tactile output 5524 does not include tap-based tactile output component 5528).

[0248] FIG. 5JJ also illustrates the transition from providing tap-based tactile output 5522 to providing tap-based tactile output 5524 as electronic device 100 transitions from the second usage context to the first usage context.

[0249] 5KK illustrates that tap-based tactile output 5542 is provided while electronic device 100 is in a second use context (e.g., a context in which a user of the device is determined to be not paying attention to the device) and tap-based tactile output 5544 is provided while electronic device 100 is in a first use context (e.g., a context in which a user of the device is determined to be paying attention to the device). Tap-based tactile output 5542 includes multiple tap-based tactile output components 5526 and 5528 having a second tactile output amplitude (e.g., the full taps shown in FIGS. 4F and 4I). Tap-based tactile output 5544 includes multiple tap-based tactile output components 5526 (e.g., full taps). Tap-based tactile output component 5528 is excluded from tap-based tactile output 5544.

[0250] FIG. 5KK also shows the transition from providing tap-based tactile output 5542 to providing tap-based tactile output 5544 as electronic device 100 transitions from the second usage context to the first usage context.

[0251] 5LL illustrates that a filter is used to obtain a first audio output from a second audio output (e.g., the first audio output corresponds to an output obtained by applying the filter to the second audio output). In some embodiments, the filter is a low-pass filter. In some embodiments, the filter is a high-pass filter, a band-pass filter, or any other filter (e.g., a digital filter).

[0252] FIG. 5LL also shows that depending on the content of the second audio output, a different filter (e.g., low-pass filter 1 with cutoff frequency f1, low-pass filter 2 with cutoff frequency f2 different from cutoff frequency f1, or low-pass filter 3 with cutoff frequency f3 different from cutoff frequencies f1 and f2) is selected.

[0253] In some embodiments, the content of the second audio output is determined based on the frequency content of the second audio output, for example, low pass filter 1 (with a high cutoff frequency) is selected for an audio output with predominantly high frequency content, and low pass filter 2 (with a low cutoff frequency) is selected for an audio output with predominantly low frequency content.

[0254] In some embodiments, the content of the second audio output is determined based on the type of alert event (e.g., whether the alert event is associated with an incoming call, an alarm, or a timer). For example, as shown in FIG. 5LL, low pass filter 1 is used to derive the first audio output from the second audio output when the second audio output is associated with an incoming call, low pass filter 2 is used to derive the first audio output from the second audio output when the second audio output is associated with an alarm, and low pass filter 3 is used to derive the first audio output from the second audio output when the second audio output is associated with a timer.

[0255] While Figure 5LL describes applying filters to audio output, filters can be applied to tactile output in a similar manner, and for the sake of brevity, such details are omitted here.

[0256] 5MM shows that the audio outputs (e.g., the second audio output and the first audio output) include multiple audio output tracks (e.g., audio output track 1, audio output track 2, and audio output track 3). FIG. 5MM also shows that during a transition from electronic device 100 providing the second audio output to providing the first audio output, a particular audio output track (e.g., audio output track 2) is removed. For example, the amplitude of audio output track 2 is gradually (e.g., linearly or non-linearly) reduced until audio output track 2 is made inaudible (e.g., muted) entirely. Optionally, another audio output track (e.g., audio output track 3) is made inaudible (e.g., muted) simultaneously or subsequently. In some embodiments, the audio output includes more than three audio output tracks.

[0257] 5NN illustrates that while electronic device 100 transitions from providing a second audio output to providing a first audio output, the amplitude of a particular audio output track (e.g., audio output track 2) is reduced without completely silencing the particular audio output track (e.g., the reduced amplitude of the particular audio output track is greater than zero). FIG. 5NN also illustrates that after reducing the amplitude of the particular audio output track (e.g., audio output track 2), the amplitude of another audio output track (e.g., audio output track 3) is reduced. In some embodiments, the audio output includes more than three audio output tracks. In some embodiments, the amplitude of yet another audio output track is reduced simultaneously or subsequently (e.g., if the audio output includes four audio output tracks, the amplitude of the fourth audio output track is reduced simultaneously with or subsequent to the reduction in the amplitude of the third audio output track).

[0258] 500 shows that during a transition from electronic device 100 providing a second audio output to providing a first audio output, audio output track 1 is provided. Subsequently, audio output track 1 is muted and audio output track 2 is provided. After that, audio output track 2 is muted and audio output track 3 is provided. This gradual switching between audio tracks provides a smooth transition between the second audio output (e.g., audio output including audio output track 1) and the first audio output (e.g., audio output including audio output track 3).

[0259] In some embodiments, as shown in Figure 5OO, audio output track 1 has a first amplitude A1, audio output track 2 has a second amplitude A2 that is less than the first amplitude A1, and audio output track 3 has a third amplitude A3 that is less than the second amplitude A2. Thus, as electronic device 100 transitions from audio output track 1 to audio output track 2 and then to audio output track 3, the volume of the audio output produced by electronic device 100 gradually decreases.

[0260] In some embodiments, audio output track 1 corresponds to a first instrument, audio output track 2 corresponds to a second instrument, and audio output track 3 corresponds to a third instrument.

[0261] In some embodiments, the second audio output includes audio output track 1, audio output track 2, and audio output track 3. During the transition from electronic device 100 providing the second audio output to providing the first audio output, electronic device 100 successively mutes audio output track 1 and audio output track 2 (e.g., electronic device 100 first mutes audio output track 1 while maintaining audio output track 2 and audio output track 3, and then mutes audio output track 2 while maintaining audio output track 3).

[0262] 6A-6C are flow diagrams illustrating method 600 for outputting a tactile output based on ongoing adjustments of an adjustable control, according to some embodiments. Method 600 is performed in an electronic device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1A) that includes a display, a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface, and one or more tactile output generators. In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on or integrated into the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations of method 600 are optionally combined, and / or the order of some operations is optionally changed.

[0263] As described below, method 600 provides an intuitive way to adjust values ​​using adjustable controls. The method provides tactile outputs to the user so that the user better understands the effect of manipulating the controls while making the adjustments, thereby creating a more efficient human-machine interface.

[0264] The device displays (602) on a display (e.g., touch-sensitive display system 112) a user interface (e.g., a media playback interface such as user interface 5002 shown in FIG. 5A) that includes a first adjustable control (e.g., playback position adjustment control 5004) and a second adjustable control (e.g., volume adjustment control 5006).

[0265] The device detects movement (604) of a first contact across the touch-sensitive surface in a drag gesture (e.g., along the path indicated by arrow 5018 as shown in Figures 5B-1 and 5B-2, along the path indicated by arrow 5028 as shown in Figures 5C-1, 5C-3, and 5C-3, or along the path indicated by arrow 5074 as shown in Figures 5E-1 and 5E-2).

[0266] pursuant to a determination that a drag gesture was performed while the focus selector (e.g., focus selector 5016 as shown at 5016a and 5016b in FIGS. 5B-1 and 5B-2) was in a position corresponding to the first adjustable control 5004 (e.g., the drag gesture was performed by a contact indicated by focus touch selector 5016 on touch-sensitive display 112 while the contact was in a position corresponding to the first draggable icon 5020 for the first slider 5021, or the drag gesture was performed by a contact indicated by focus touch selector 5016 on touch-sensitive display 112 while the contact was in a position corresponding to the first draggable icon 5020 for the first slider 5021). The drag gesture (performed by a contact on the touch-sensitive surface while the first adjustable control 5004 is in a position corresponding to the first adjustable control 5020) causes the device to adjust (606) the first adjustable control 5004 according to the movement of the first contact in the drag gesture (e.g., moving the first draggable icon 5020 across the touch-sensitive display 112 to adjust the value of a parameter corresponding to the first adjustable control 5004, such as a playback position parameter) and outputs (606) a first plurality of tactile outputs (e.g., as represented by the row of lines shown at 5022) using one or more tactile output generators 167. Each tactile output (e.g., as represented by the lines shown at 5023) in the first plurality of tactile outputs is triggered based on the progressive adjustment of the first adjustable control 5004 (e.g., based on the progression of the first draggable icon 5020 across the display, such as when the focus selector 5016 is in a respective predetermined position within a first slider on the display). The first plurality of tactile outputs has a first distribution of tactile outputs (e.g., a first spatial distribution of tactile output triggers along the path of the first draggable icon) when the first adjustable control 5021 is adjusted.

[0267] pursuant to a determination that a drag gesture was performed while the focus selector (e.g., focus selector 5026 as shown at 5026a and 5026b in FIGS. 5C-1, 5C-2, and 5C-3) was in a position corresponding to the second adjustable control 5006 (e.g., the drag gesture was performed by a contact indicated by focus touch selector 5026 on touch-sensitive display 112 while the contact was in a position corresponding to the second draggable icon 5030 for the second slider 5032, or the drag gesture was performed by a cursor or other pointer moving over the second slider 5032). The drag gesture (performed by a contact on the touch-sensitive surface while the second adjustable control 5006 is in a position corresponding to the second draggable icon 5030 relative to the volume slider 5032) causes the device to adjust (608) the second adjustable control 5006 according to the movement of the first contact in the drag gesture (e.g., moving the second draggable icon 5030 across the display 112 to adjust the value of a parameter corresponding to the second adjustable control 5006, such as the volume level) and outputs (608) a second plurality of tactile outputs (e.g., as represented by the row of lines shown at 5034) using one or more tactile output generators. Each tactile output in the second plurality of tactile outputs is triggered based on the progress of adjusting the second adjustable control (e.g., based on the progress of the second draggable icon 5030 along the volume slider 5032, such as when the focus selector 5026 is in a respective predetermined position within the second slider on the display). The second plurality of tactile outputs has a second distribution of tactile outputs that is different (e.g., smaller or larger) than the first distribution of tactile outputs when the second adjustable control is adjusted. For example, the density of tactile output triggers along the path of the second draggable icon 5030 (e.g., the density of tactile output triggers along the volume slider 5032) is less than the density of tactile output triggers along the path of the first draggable icon 5020 (e.g., the density of tactile output triggers along the playback position slider 5021), or vice versa.In some embodiments, as shown in FIGS. 5B-2 and 5C-3, the positions 5038 along the volume slider 5032 that trigger tactile outputs are spaced more widely than the positions 5022 along the progress bar 5021 that trigger tactile outputs.

[0268] When the second adjustable control is adjusted, a second plurality of tactile outputs having a second distribution of tactile outputs different from the first distribution of tactile outputs is output, thereby providing feedback to the user as to the type of control being used, which control of the plurality of controls is being used, and / or the degree of adjustment being made. Providing improved feedback to the user increases usability of the device (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), provides a more efficient user-device interface, and reduces power usage and improves battery life of the device by allowing the user to use the device more quickly and efficiently.

[0269] In some embodiments, the first adjustable control 5004 is a progress control 5021 that selects a position within the content (e.g., a content scrubber control having a draggable progress icon 5020 configured to adjust the playback position of the media content being played), and the second control 5006 is a volume control 5032 that controls the volume of the content being played (e.g., a control having a draggable volume slider icon 5030 configured to adjust the volume at which the media content is played) (610). In some embodiments, the content includes, for example, audio and / or video content.

[0270] In some embodiments, the first plurality of tactile outputs 5022 includes an end point tactile output 5058, shown in FIG. 5D-2, that is provided pursuant to determining that the first adjustable control 5020 has reached an end point (e.g., end point 5050, shown in FIG. 5D-1) (612). In some embodiments, when the draggable icon 5020 reaches an end of the scrubber, such as the end of the progress control 5021, different feedback (e.g., a tactile output with a larger amplitude and / or other difference in its tactile output profile from previous outputs in the first plurality of tactile outputs) is provided. In some embodiments, a second adjustable control 5006, such as volume control 5006, does not have different feedback at the end of the volume scrubber.

[0271] Providing tactile feedback at the end of the control that is distinct from tactile feedback provided at other portions of the control provides the user with feedback about the range of adjustment available from the control. Providing improved feedback to the user increases operability of the device (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device, notifying the user when further inputs will no longer produce adjustments in the control, and reducing user errors), makes the user-device interface more efficient, and also reduces power usage and improves battery life of the device by allowing the user to use the device more quickly and efficiently.

[0272] In some embodiments, for each tactile output (e.g., represented by a line shown at 5023) in the first plurality of tactile outputs (e.g., represented by the row of lines 5022), the respective tactile output is triggered (614) when the focus selector 5016 is at a corresponding predetermined position on the display. For example, a first tactile output in the first plurality of tactile outputs is triggered when the focus selector is at a first predetermined position on the display (e.g., as shown at 5016a), a second tactile output in the first plurality of tactile outputs is triggered when the focus selector is at a second predetermined position on the display adjacent to the first predetermined position on the display (e.g., as shown at 5016b), a third tactile output in the first plurality of tactile outputs is triggered when the focus selector is at a third predetermined position on the display adjacent to the second predetermined position on the display, etc. Similarly, in some embodiments, for each tactile output of the second plurality of tactile outputs (e.g., as represented by the row of lines 5034), the respective tactile output is triggered when the focus selector is at a corresponding predetermined position on the display.

[0273] In some embodiments, the first adjustable control is a progress control, and at least a portion of the predetermined locations on the display correspond to chapter markers for the media content whose playback is being adjusted with the progress control (616). For example, FIG. 5E-1 shows a progress control 5078. FIG. 5E-2 shows a series 5084 of lines (e.g., 5080, 5084) representing locations on the display where tactile outputs will be triggered. Series 5084 includes tactile output trigger locations corresponding to chapter markers (e.g., line 5080). In some embodiments, the tactile output trigger locations corresponding to chapter markers have one or more distinct characteristics from tactile output trigger locations that do not correspond to trigger markers. For example, line 5080 corresponding to a chapter marker is a longer line than line 5082 that does not correspond to a chapter marker, indicating, for example, that a tactile output having a greater amplitude will be output at the location on the display indicated by line 5080. In some embodiments, the chapter markers are chapter markers for, for example, audio tracks, audiobook chapters, and / or video chapters.

[0274] As a user scrolls through content, outputting a tactile output that includes distinct characteristics at tactile output trigger locations that correspond to chapter markers provides the user with feedback about the scrolling progress and information that can be used to more accurately navigate to a desired portion of the content. Providing improved visual feedback to the user enhances device usability (e.g., by helping the user quickly and accurately align on a desired destination within the content), makes the user-device interface more efficient, and reduces device power usage and improves battery life by allowing the user to use the device more quickly and efficiently.

[0275] In some embodiments, each tactile output in the first plurality of tactile outputs and the second plurality of tactile outputs has a corresponding tactile output profile 618. In some embodiments, the tactile output profile includes one or more characteristics of a given tactile output, such as the amplitude of the output, the shape of the motion waveform in the output, the duration of the output (e.g., a discrete tap output or a continuous ongoing output), characteristics of the object being simulated by the output (e.g., the size, material, and / or mass of the simulated object, such as a simulated ball rolling on a simulated surface), the number of objects being simulated by the output, and / or characteristics of the motion of the simulated objects.

[0276] In some embodiments, each tactile output of the first plurality of tactile outputs has a first respective tactile output profile, and each tactile output of the second plurality of tactile outputs has a second respective tactile output profile that is different from the first respective tactile output profile (620). For example, in the plurality of tactile outputs represented by the row of lines shown at 5034 in FIG. 5C-2, increasing lengths of the lines represent, for example, increasing amplitudes. A first tactile output of the plurality of tactile outputs represented at 5034 (e.g., a tactile output generated when the focus selector is in the position shown at 5026a) has a first tactile output profile (e.g., a first amplitude), and a second tactile output of the plurality of tactile outputs (e.g., a tactile output generated when the focus selector is in the position shown at 5026b) has a second tactile output profile (e.g., a second amplitude greater than the first amplitude).

[0277] In some embodiments, the amplitude of the tactile output in the first plurality of tactile outputs is constant and the amplitude of the tactile output in the second plurality of tactile outputs is variable (622). For example, the amplitude in the second plurality of tactile outputs increases, decreases, oscillates, and / or is variable according to a step function. In some embodiments, the second control adjusts the magnitude of a parameter of the content (e.g., volume), and the magnitude of the tactile output increases as the magnitude of the parameter increases. In some embodiments, the row of lines 5022 representing the tactile output in FIG. 5B-2 is an example of a constant amplitude of the tactile output, and the row of lines 5034 in FIG. 5C-2 is an example of a variable amplitude of the tactile output.

[0278] Outputting tactile outputs having a constant amplitude for a first plurality of tactile outputs (e.g., corresponding to a first adjustable control) and a variable amplitude for a second plurality of tactile outputs (e.g., corresponding to a second adjustable control) provides feedback to the user as to the type of control being used, which control of the plurality of controls is being used, and / or the degree of adjustment being made. Providing improved feedback to the user increases usability of the device (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), makes the user-device interface more efficient, and also reduces power usage and improves battery life of the device by allowing the user to use the device more quickly and efficiently.

[0279] In some embodiments, the amplitudes of the tactile outputs in the first plurality of tactile outputs vary in a first manner (e.g., increasing, decreasing, oscillating, and / or varying according to a step function), and the amplitudes of the tactile outputs in the second plurality of tactile outputs vary in a second manner that is different from the first manner (624).

[0280] In some embodiments, a tactile output in the first plurality of tactile outputs is accompanied by a corresponding audio output (626).

[0281] In some embodiments, the audio output has audio parameters that are variable (628). In some embodiments, as the tactile output parameters (e.g., amplitude, frequency (which causes the tactile output to vibrate), and / or distribution of the tactile output) change, the audio parameters (e.g., amplitude and / or frequency) change. For example, as the tactile parameter increases, the audio parameter increases, and as the tactile parameter decreases, the audio parameter decreases.

[0282] In some embodiments, the user interface includes a play / pause toggle control 5010 (e.g., a virtual play / pause button) (630). The device detects input by a second contact on the touch-sensitive surface while the focus selector is in a position corresponding to the play / pause toggle control 5010 (as shown in the paused state in FIG. 5B-1 and the play state in FIG. 5C-1 ). For example, when a cursor or other pointer is over the play / pause button on the display, the device detects a tap gesture by contact on the touch-sensitive display at the play / pause button or detects a tap gesture by contact on the touch-sensitive surface. In some embodiments, in response to detecting input by the second contact, and following a determination that the input corresponds to a request to play the media content (e.g., the play / pause button is toggled from pause to play), the device plays the media content, displays the play / pause toggle control in a play state, and outputs, using one or more tactile output generators, at least one tactile output having a first tactile output profile (e.g., a tactile output represented by the box 5044 in FIG. 5C-2 ). Pursuant to determining that the input corresponds to a request to pause the media content (e.g., the play / pause button is toggled from play to pause), the device pauses the media content, displays the play / pause toggle control in a paused state, and outputs, using one or more tactile output generators, at least one tactile output having a second tactile output profile different from the first tactile output profile (e.g., a tactile output represented by a box at 5046 in FIG. 5C-3). For example, switching from pause to play may result in a "boingy" tactile output (e.g., a tactile output having a periodic step function or sinusoidally varying amplitude that, in some embodiments, is decayed over time), while switching from play to pause may result in a different "non-boingy" tactile output (e.g., tactile outputs having an unchanged amplitude), or vice versa.

[0283] By outputting a tactile output having a first tactile output profile when a request to change a first state of a multi-state control (e.g., a play / pause toggle control) is received (e.g., to play media content), and a second tactile output profile when a request to change a second state of the multi-state control (e.g., to pause content) is received, the device provides the user with feedback regarding which control among the multi-state controls is being manipulated and the nature of the control (e.g., by providing an indication that the control is a multi-state control). Providing improved feedback to the user enhances device operability (e.g., by assisting the user in providing appropriate inputs when manipulating / interacting with the device and reducing user errors), makes the user-device interface more efficient, and reduces device power usage and improves battery life by allowing the user to use the device more quickly and efficiently. In some embodiments, the improved feedback allows the user to manipulate a control, such as a play / pause toggle control, on the device's display without powering it on.

[0284] It should be understood that the particular order described of the operations in Figures 6A-6C is merely an example, and that the described order is not intended to indicate the only order in which the operations may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. Additionally, it should be noted that other processing details described herein with respect to the other methods described herein (e.g., methods 700, 800, 900, 1000, 1100, 1200, and 1300) are also applicable in a similar manner to method 600 described above with respect to Figures 6A-6C. For example, the contacts, gestures, user interface objects, tactile outputs, focus selectors, and animations described above with respect to method 600 optionally have one or more characteristics of the contacts, gestures, user interface objects, tactile outputs, focus selectors, and animations described herein with respect to the other methods described herein (e.g., methods 700, 800, 900, 1000, 1100, 1200, and 1300). For the sake of brevity, those details will not be repeated here.

[0285] 7A-7D are flow diagrams illustrating a method 700 for providing a tactile output in response to a detected increase in a characteristic intensity of a contact, according to some embodiments. Method 700 is performed in an electronic device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1A) that includes a display, a touch-sensitive surface, one or more sensors configured to detect the intensity of a contact on the touch-sensitive surface, and one or more tactile output generators. In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on or integrated into the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations of method 700 are optionally combined, and / or the order of some operations is optionally changed.

[0286] As described below, method 700 provides feedback when a user input is received. The feedback gives the user an intuitive sense of the intensity of contact with the touch-sensitive surface. The method helps the user understand the connection between the input and the device response to the input, thereby producing a more efficient human-machine interface.

[0287] While displaying a first user interface on the display, the device detects a contact on the touch-sensitive surface (702). For example, the device detects a contact at a location indicated by focus selector 5100, as shown in FIG. 5F.

[0288] The device detects (704) a first increase in the characteristic intensity of the contact on the touch-sensitive surface. For example, the characteristic intensity of the contact as indicated by focus selector 5100 increases above hint intensity threshold level IT, as indicated by intensity level meter 5104a shown in FIG. 5H. H , as indicated by the intensity level meter 5104a-2, the hint intensity threshold level IT H , as indicated by intensity level meter 5104a-3, until the threshold intensity level IT H continues to grow beyond this.

[0289] In response to detecting a first increase in the characteristic intensity of the contact on the touch-sensitive surface, the device generates (706) using one or more tactile output generators a first tactile output having a first tactile output profile. The first tactile output profile is, for example, a profile that includes a periodic output and / or an output (and / or a distribution of tactile outputs) that includes an amplitude that, optionally, increases and / or decreases monotonically (e.g., according to a linear, exponential, logarithmic, and / or step function) as the characteristic intensity increases. The first tactile output profile includes output parameters that vary (dynamically) according to the proximity of the characteristic intensity of the contact to meeting a first intensity criterion (e.g., the amplitude of the first tactile output profile increases as the characteristic intensity approaches a first intensity threshold). For example, the first tactile output may be a signal that indicates a first intensity threshold level IT as indicated by intensity level meter 5104a. H , as indicated by the intensity level meter 5104a-2. H tactile output graph 5106 of FIG. 5H, as shown at 5110, until the characteristic intensity of the contact exceeds the hint intensity threshold level IT, as indicated by intensity level meter 5104a-3. H continues to grow beyond this.

[0290] Generating a tactile output having a tactile output profile that changes as the characteristic intensity of the contact increases provides the user with feedback about the intensity level being detected by the device based on the user's input, and provides the user with tactile feedback indicating that a harder press will cause the device to perform an action associated with the user interface element. Providing improved tactile feedback to the user improves device usability (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device) and makes the user-device interface more efficient.

[0291] While generating the tactile output having the first tactile output profile, the device detects (708) a second increase in the characteristic intensity of the contact on the touch-sensitive surface. For example, the characteristic intensity of the contact as indicated by focus selector 5100 increases above a light pressure intensity threshold level IT, as indicated by intensity level meter 5104a shown in FIG. 5G. L , and then reaches the light pressure intensity threshold level IT, as indicated by the intensity level meter 5104b shown in FIG. 5G. L In response to detecting a second increase in the characteristic intensity of the contact on the touch-sensitive surface (710), the characteristic intensity of the contact on the touch-sensitive surface meets a first intensity criterion (e.g., the characteristic intensity of the contact exceeds a light pressure intensity threshold IT L In accordance with a determination that the characteristic intensity of the contact on the touch-sensitive surface increases above an intensity threshold such as a light pressure intensity threshold, the device generates a second tactile output (e.g., a tap such as a short duration "mini-tap") having a second tactile output profile that differs from the first tactile output profile. For example, the second tactile output is a tap such as that represented by bar 5112 of tactile output graph 5106 of FIG. 5G. In some embodiments, the intensity criterion includes a time-varying component (e.g., as described above with reference to FIGS. 4C-4E). In accordance with a determination that the characteristic intensity of the contact on the touch-sensitive surface does not satisfy the first intensity criterion, the device continues to generate the first tactile output having the first tactile output profile and (dynamically) varies output parameters based on the proximity of the characteristic intensity of the contact to satisfying the first intensity criterion in accordance with the second increase in the characteristic intensity of the contact. For example, as shown in intensity level meter 5104a-3 of FIG. 5H, the device may determine that the characteristic intensity of the contact does not satisfy the first intensity criterion. L In accordance with the determination that the threshold is below 0, the device continues to generate the first tactile output 5110.

[0292] In some embodiments, in response to detecting a second increase in the characteristic intensity of the contact on the touch-sensitive surface, the device determines (712) whether the characteristic intensity of the contact on the touch-sensitive surface meets a first intensity criterion.

[0293] In some embodiments, the first tactile output continues while detecting a second increase in the characteristic intensity of the contact until at least a first intensity criterion is met (714). In some embodiments, the first tactile output is an ongoing output such as a sinusoidal output, a repetitive stream of step function pulses (e.g., <0.1 second intervals), or another function with periodic or repetitive properties that continues until at least a first intensity criterion is met.

[0294] In some embodiments, the second tactile output is a discrete tactile output (e.g., a single tap such as the tap represented by bar 5112 shown in tactile output graph 5106 of FIG. 5G) (716). In some embodiments, the second tactile output profile has a higher amplitude than at least a portion of the first tactile output profile, e.g., such that the amplitude of the second tactile output is greater than the first tactile output when a first intensity criterion (e.g., a light pressure intensity threshold) is met. For example, as shown in FIG. 5G, the amplitude of the tap represented by bar 5512 in tactile output graph 5106 is higher than the highest amplitude of the tactile output shown at 5110.

[0295] In some embodiments, in accordance with determining that the characteristic intensity of the contact on the touch-sensitive surface meets the first intensity criterion, the device stops outputting (718) the first tactile output (e.g., stops the continuous tactile output).

[0296] In some embodiments, after detecting a second increase in the characteristic intensity of the contact, the device detects (720) a decrease in the characteristic intensity of the contact. The device detects (720) a decrease in the characteristic intensity of the contact when the characteristic intensity of the contact on the touch-sensitive surface exceeds a first intensity criterion (e.g., a light pressure intensity threshold IT L), the device ceases generating the first tactile output (e.g., providing feedback to the user to indicate that the characteristic intensity of the contact has already met the first intensity criterion) pursuant to a determination that a decrease in the characteristic intensity of the contact is detected before the characteristic intensity of the contact on the touch-sensitive surface meets the first intensity criterion. Pursuant to a determination that a decrease in the characteristic intensity of the contact is detected before the characteristic intensity of the contact on the touch-sensitive surface meets the first intensity criterion, the device continues to generate the first tactile output having the first tactile output profile and continues to vary the output parameters according to the proximity of the characteristic intensity of the contact to meeting the first intensity criterion (e.g., providing feedback to the user to indicate that the characteristic intensity of the contact has not yet met the first intensity criterion). For example, as shown in FIG. 5J , the characteristic intensity of the contact may be measured by intensity level meter 5132c, as indicated by light pressure intensity threshold IT L , and then decreases to a lower intensity level as shown by intensity level meter 5132d. L , the device continues to generate first tactile output 5110 and continues to vary the amplitude of tactile output 5110 as the characteristic intensity of the contact decreases.

[0297] In some embodiments, while the first tactile output is being generated, the device displays (722) an animation that changes according to the proximity of the characteristic intensity of the contact to meeting the first intensity criteria. In some embodiments, the changes in the animation parallel the changes in the tactile output (e.g., the parameters of the animation change as the output parameters of the first tactile output profile change). In some embodiments, the animation is a continuous animation that dynamically adjusts according to the characteristic intensity of the contact. In some embodiments, the animation is a "hint" animation that dynamically obscures user interface objects other than the selected first interface object (e.g., by increasing the blur radius of the objects) as the intensity approaches a "peak" intensity threshold that displays a preview region corresponding to the selected first user interface object. For example, as the characteristic intensity of contact 5100 increases from time t0 to time t, as indicated by intensity level meters 5104a, 5104a-2, and 5104a-3, 0.6 , the background of the user interface is animated to become increasingly blurred (as shown by the transition from 5102a to 5102a-2 and 5102a-3), as shown in FIG. 5H.

[0298] In some embodiments, the animation includes animating a sequence of images of the background according to the characteristic intensity of the first contact. In some embodiments, the change includes varying Z-depth, focus, radial position relative to the contact, color, contrast, or brightness of one or more objects in the background, wherein the dynamic change in the appearance of the background of the first user interface is based at least in part on the characteristic intensity of the first contact (e.g., directly, linearly, non-linearly proportional, or at a ratio determined based on the characteristic intensity of the contact).

[0299] In some embodiments, the dynamic change in the appearance of the background of the first user interface is based at least in part on the position of the first focus selector 5100 on the display (e.g., distortion of the background pattern is more pronounced for portions of the background pattern closer to the focus selector). For example, the virtual mesh is pushed back more at locations closer to the contact than at locations closer to the edge of the touch screen 112.

[0300] In some embodiments, the output parameter of the first tactile output varies nonlinearly according to the proximity of the characteristic intensity of the contact to meeting the first intensity criterion (724). For example, the output parameter of the first tactile output varies exponentially, logarithmically, and / or as an increasing step function (e.g., a series of taps).

[0301] In some embodiments, after generating the first tactile output, the device generates a tactile output with an intensity greater than a threshold intensity included in the first intensity criteria (e.g., the characteristic intensity of the contact is greater than or equal to a light pressure threshold IT L A third increase in the characteristic intensity of the contact on the touch-sensitive surface is detected (726) until the characteristic intensity of contact 5100 increases above an intensity threshold, such as a deep pressure intensity threshold IT D From an intensity level below the deep pressure intensity threshold IT, as shown by the intensity level meter 5104c, D In response to detecting a third increase in the characteristic intensity of the contact on the touch-sensitive surface, the device uses one or more tactile output generators to detect a second intensity criterion (e.g., when the characteristic intensity of the contact exceeds a deep pressure threshold IT D5G, the device generates a third tactile output having a third tactile output profile that varies according to the proximity of the characteristic intensity of the contact to satisfying a criterion (including criteria that increase above an intensity threshold such as 5104b, 5104c, etc.) (e.g., the amplitude of the third tactile output profile increases linearly or non-linearly). In some embodiments, the third tactile output is generated after the second tactile output ("mini-tap") has been generated or has terminated (e.g., as shown in 5112). For example, the device generates tactile output 5118, as shown in FIG. 5G, including a tactile output that increases as the characteristic intensity of contact 5100 increases from 5104b to 5104c.

[0302] In some embodiments, while the third tactile output is generated, the device displays (728) an animation that varies according to the proximity of the characteristic intensity of the contact to meeting the second intensity criterion. L and deep pressure threshold IT D , an animation of expanding preview area 5100 (e.g., a preview area corresponding to a selected user interface object) occurs (e.g., in some embodiments, a light press threshold IT L (instead of the animation that would obscure other user interface objects, as occurs below ).

[0303] In some embodiments, in accordance with determining that the characteristic intensity of the contact on the touch-sensitive surface satisfies the second intensity criterion, the device generates (730) a fourth tactile output having a fourth tactile output profile (e.g., a single tap of longer duration than the second tactile output). In some embodiments, the second intensity criterion is determined to be a value greater than or equal to the deep pressure intensity threshold IT D In some embodiments, the third tactile output is a continuous tactile output that changes dynamically as the intensity of the contact changes, and the fourth tactile output is a discrete tactile output that is generated when the contact meets the second intensity criterion. For example, if the characteristic intensity of contact 5100 increases above a deep pressure intensity threshold IT as indicated by intensity meter 5104c, D, a fourth tactile output is generated (eg, as a single tap represented by bar 5120 of tactile output graph 5106).

[0304] In some embodiments, the third tactile output profile (eg, function) is different from the first tactile output profile (732).

[0305] In some embodiments, in response to determining that the characteristic intensity of the contact on the touch-sensitive surface meets the third intensity criterion, the device generates (734) a fifth tactile output having a fifth tactile output profile, where the fifth tactile output has a duration that is shorter than the duration of the first tactile output (e.g., the fifth tactile output is a tap output). In some embodiments, the fifth tactile output is generated at a depth threshold IT , as indicated by intensity level meter 5104d in FIG. 5G. D The overpressure intensity threshold IT is greater than OP A third intensity criterion is met when the characteristic intensity of the contact increases above the overpressure intensity threshold IT , as shown at 5104d. For example, a tap input, as represented by bar 5122 in tactile output graph 5106, occurs when the characteristic intensity of the contact exceeds the overpressure intensity threshold IT , as shown at 5104d. OP It is generated when the value increases beyond .

[0306] In some embodiments, the first intensity criterion is whether the characteristic intensity of the contact exceeds a first intensity threshold (e.g., a light pressure intensity threshold IT L ) and the second intensity criterion is met when the characteristic intensity of the contact exceeds a second intensity threshold (e.g., a deep pressure threshold IT ) that is greater than the first intensity threshold (736). D ), and a third intensity criterion is met when the characteristic intensity of the contact exceeds a third intensity threshold (e.g., an overpressure intensity threshold IT) that is greater than the second intensity threshold. OP ) . In some embodiments, the device ceases generating (736) the continuous tactile output while the characteristic intensity of the contact is between the second intensity threshold and the third intensity threshold. For example, as shown in FIG. 5G, when the characteristic intensity of contact 5100 exceeds IT Dand IT0, no tactile output is generated between time t2 and time t3. In some embodiments, no tactile output (and no corresponding animation) is generated while the characteristic intensity of the contact is between the second and third intensity thresholds. In some embodiments, in contrast to the variable / dynamic tactile output that occurs as the first intensity threshold is approached (e.g., first tactile output 5110) and the variable / dynamic tactile output that occurs as the second intensity threshold is approached (e.g., third tactile output 5118), there is no variable / dynamic tactile output as the third intensity threshold is approached. In some embodiments, in contrast to the changing animation that occurs as the first intensity threshold is approached and the changing animation that occurs as the second intensity threshold is approached, there is no changing animation as the third intensity threshold is approached.

[0307] In some embodiments, while displaying the animation that varies according to the proximity of the characteristic intensity of the contact to meeting the second intensity criterion, the device detects (738) a fourth increase in the characteristic intensity of the contact on the touch-sensitive surface. In response to detecting the fourth increase in the characteristic intensity of the contact, the device determines whether the characteristic intensity of the contact on the touch-sensitive surface meets the second intensity criterion (e.g., whether the characteristic intensity of the contact exceeds the deep pressure threshold IT as indicated by intensity level meter 5104c shown in FIG. 5G). D In response to a determination that the characteristic intensity of the contact on the touch-sensitive surface meets a third intensity criterion (e.g., the characteristic intensity of the contact exceeds an overpressure threshold IT , as indicated by intensity level meter 5104d), the device displays a second user interface that is distinct from the first user interface (e.g., the device displays user interface 5102c that is distinct from user interface 5102a), and OP In accordance with a determination that the number of active users exceeds 5102d, the device redisplays the first user interface (eg, the device redisplays the user interface shown in 5102a as shown in user interface 5102d).

[0308] It should be understood that the particular order described of the operations in Figures 7A-7D is merely an example, and that the described order is not intended to indicate the only order in which the operations may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. Additionally, it should be noted that other processing details described herein with respect to the other methods described herein (e.g., methods 600, 800, 900, 1000, 1100, 1200, and 1300) are also applicable in a similar manner to method 700 described above with respect to Figures 7A-7D. For example, the contacts, gestures, user interface objects, tactile outputs, intensity thresholds, focus selectors, and animations described above with respect to method 700 optionally have one or more characteristics of the contacts, gestures, user interface objects, tactile outputs, intensity thresholds, focus selectors, and animations described herein with respect to the other methods described herein (e.g., methods 600, 800, 900, 1000, 1100, 1200, and 1300). For the sake of brevity, those details will not be repeated here.

[0309] 8A-8C are flow diagrams illustrating a method 800 for generating a sequence of tactile outputs corresponding to movement of a focus selector, according to some embodiments. Method 800 is performed in an electronic device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1A) that includes a display, a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface, and one or more tactile output generators. In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on or integrated into the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations of method 800 are optionally combined, and / or the order of some operations is optionally changed.

[0310] As described below, when user interaction with a user interface object is detected, method 800 provides feedback to give the user an intuitive sense of whether the user interface object was selected for movement. The method helps the user understand the connection between input and device response to the input, thereby producing a more efficient human-machine interface.

[0311] The device displays (802) a user interface that includes a plurality of user interface objects (eg, user interface objects 5152 and 5162 shown in user interfaces 5154a-5154e of FIG. 5M).

[0312] The device detects touch input on the touch-sensitive surface with a contact that moves focus selector 5150 from a first user interface object of the plurality of user interface objects in a first direction on the display (804). For example, the device detects a drag gesture with the contact on the touch-sensitive display that begins while the contact is on the first user interface object (e.g., focus selector 5150 is on first user interface object 5152), or the device detects a drag gesture with the contact on the touch-sensitive surface that begins while a cursor or other pointer is on the first user interface object on the display.

[0313] In response to detecting touch input (806), in accordance with a determination that the first user interface object is selected when the focus selector is moved in a first direction (e.g., as shown in FIG. 5M), the device generates, via one or more tactile output generators, a sequence of tactile outputs corresponding to the movement of the focus selector in the first direction (e.g., a sequence of tactile outputs 5157 as shown in tactile output graph 5156 of FIG. 5M). In accordance with a determination that the first user interface object is not selected when the focus selector is moved in the first direction (e.g., as shown in FIG. 5O), the device ceases generating the sequence of tactile outputs corresponding to the movement of the focus selector in the first direction (e.g., as shown in tactile output graph 5198 of FIG. 5O).

[0314] In some embodiments, in response to detecting the touch input, the device moves the first user interface object in accordance with movement of the focus selector (808), regardless of whether the first user interface object is selected. For example, when the first user interface object is a first application launch icon in a multi-page springboard and the springboard is in normal navigation mode, touch input with a contact beginning on the first application launch icon scrolls the page in a first direction (e.g., leftward), the first application launch icon moves with the remainder of the page without selecting the first application launch icon and without providing a sequence of tactile outputs. As shown in FIG. 5O, movement of the focus selector 5150 along the path indicated by arrow 5194 causes the springboard (e.g., including multiple user interface objects) to move such that the first application launch icon (user interface object 5152) moves (from a first position shown in user interface 5192a, to a second position shown in user interface 5192b, and then to a third position shown in user interface 5192c). In contrast, when the springboard is in icon reconfiguration mode, touch input with a contact beginning on a first application launch icon selects the first application launch icon and moves the icon in a first direction while providing a sequence of tactile outputs. For example, in FIG. 5M, a contact at the location indicated by focus selector 5150 selects first application launch icon 5152 and moves the first application launch icon (as shown in user interfaces 5154a-5154e).

[0315] In some embodiments, in response to detecting touch input, following a determination that the first user interface object has been selected (e.g., in response to a fixation input (e.g., a press and hold) while the focus selector is in a position corresponding to the first user interface object), the device moves (810) the first user interface object relative to (e.g., over and / or between) at least one other user interface object in the plurality of user interface objects. For example, as shown in user interfaces 5154a-5154e of FIG. 5M, first user interface object 5152 moves over user interface object 5162. In some embodiments, once selected, the first user interface object moves relative to all of the other objects in the plurality of user interface objects.

[0316] In some embodiments, in response to detecting touch input, following a determination that the first user interface object has been selected, the device displays 812 a preview of another object corresponding to the first user interface object (e.g., a thumbnail image, such as a thumbnail of an image from a set of images (e.g., a row and / or grid)). For example, as shown in FIG. 5Q, when user interface object 5204 is selected, thumbnail image 5206b is shown as a preview of user interface object 5204.

[0317] In some embodiments, as the first user interface object moves, the device generates (814) a discrete tactile output corresponding to the movement of the first object relative to at least one other user interface object in the plurality of user interface objects (e.g., a discrete tactile output is generated as an application icon passes over another application icon). For example, as shown in tactile output graph 5156, discrete tactile output 5164 is generated at time t3 to indicate that user interface object 5152 has moved over user interface object 5162 (as shown in user interface 5154d). In some embodiments, a discrete tactile output (e.g., tactile output 5164) is generated as the icon passes over the other icon, and an ongoing sequence of tactile outputs (e.g., series of tactile outputs 5157) corresponding to the movement of the icon is also generated.

[0318] In some embodiments, as the first user interface object moves, the device generates (816) discrete tactile outputs corresponding to the movement of other user interface objects in response to the movement of the first user interface object (e.g., other application icons are repositioned and / or snapped into place as the first object moves around the UI). For example, in user interface 5154e of FIG. 5M , user interface object 5162 has been snapped into the position where user interface object 5152 was previously located (as shown in user interface 5154a). At time t4, when user interface object 5162 is snapped into its new position, discrete tactile output 5166 is generated. In some embodiments, the discrete tactile output (e.g., 5166) is generated while an ongoing sequence of tactile outputs (e.g., 5157) corresponding to the movement is being generated.

[0319] In some embodiments, in response to selecting the first user interface object, the device generates (818) a tactile output corresponding to the selection of the first user interface object that differs from the sequence of tactile outputs corresponding to the movement of the first user interface object (e.g., a tap or series of taps having a greater amplitude, a higher frequency, a higher density, and / or other different tactile output profile).

[0320] In some embodiments, in response to detecting the touch input, the device moves (820) a second user interface object within the plurality of user interface objects together with the first user interface object in accordance with a determination that the first user interface object is not selected (e.g., scrolling without providing a tactile output when the first object is not selected). For example, in FIG. 5O , first user interface object 5152 is not selected by the touch indicated by focus selector 5150, and movement of focus selector 5150 along the path indicated by arrow 5194 causes second user interface object 5162 to move together with first user interface object 5152. In some embodiments, the first user interface object moves together with all other objects.

[0321] In some embodiments, in response to detecting a first portion of the touch input (e.g., while the focus selector is at a position corresponding to the first user interface object), the device selects (822) the first user interface object and generates an ongoing tactile output indicating that the user interface is in a first state (e.g., an icon reconfiguration mode) in which the first user interface object is selected. For example, in FIG. 5M , focus selector 5150 is at a position corresponding to user interface object 5152 (e.g., for more than a threshold time period), causing user interface object 5152 to be selected. The device generates ongoing tactile output 5157, including a series of taps, as shown in tactile output graph 5156, to indicate that user interface object 5152 has been selected. In some embodiments, the ongoing tactile output continues as long as the device is in the first state. In some embodiments, the ongoing tactile output continues as long as the device is in the first state and contact continues to be detected on the touch-sensitive surface. In some embodiments, the ongoing tactile output stops when contact is no longer detected on the touch-sensitive surface.

[0322] In some embodiments, while the touch input is detected and while the first user interface object is selected, the device detects (824) a change in the state of the user interface from a first state (e.g., when the application launch icon is moving among other application launch icons in an application springboard, as shown in FIG. 5M) to a second state (e.g., when the application launch icon is moved into a folder or folder icon, or when the application launch icon is moved to a location corresponding to another application launch icon, thereby automatically creating a folder). For example, in FIG. 5N, the user interface changes from a first state in which the application launch icon (e.g., user interface object 5178) is moving among other application launch icons (e.g., moving over application launch icon 5182) to a second state in which application launch icon 5178 is moving to a location corresponding to folder icon 5184. In response to detecting a change in the state of the user interface from a first state to a second state, the device changes from an ongoing first-state tactile output (e.g., an ongoing tactile output indicating that a first user interface object has been selected and the user interface is in a first state, such as series of taps 5167 shown in tactile output graph 5168) to one or more second-state tactile outputs (e.g., series of taps 5169 shown in tactile output graph 5168) that differ from the ongoing first-state tactile output, indicating that a change in the state of the user interface from the first state to the second state has occurred. In some embodiments, the one or more second-state tactile outputs have a different output profile than the ongoing first-state tactile output (e.g., the second-state tactile output has a lower tactile output amplitude, tactile output density, and / or tactile output frequency).

[0323] In some embodiments, outputting a tactile output for one or more second states includes outputting an ongoing sequence of tactile outputs (e.g., a series of taps 5169 shown in tactile output graph 5168) while the second state is active in the first user interface (828).

[0324] In some embodiments, changing the state of the user interface from the first state to the second state includes displaying a second user interface superimposed on the first user interface (e.g., a folder user interface 5184 is shown, for example, on top of or instead of the springboard user interface 5180d) (830).

[0325] In some embodiments, changing the state of the user interface from the first state to the second state includes replacing the display of the first user interface with the second user interface (e.g., a folder UI replacing the array of application launch icons in a springboard UI) (832).

[0326] It should be understood that the particular order described of the operations in Figures 8A-8C is merely an example, and that the described order is not intended to indicate the only order in which the operations may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. Additionally, it should be noted that other processing details described herein with respect to the other methods described herein (e.g., methods 600, 700, 900, 1000, 1100, 1200, and 1300) are also applicable in a similar manner to method 800 described above with respect to Figures 8A-8C. For example, the contacts, gestures, user interface objects, tactile outputs, focus selectors, and animations described above with respect to method 800 optionally have one or more characteristics of the contacts, gestures, user interface objects, tactile outputs, focus selectors, and animations described herein with respect to the other methods described herein (e.g., methods 600, 700, 900, 1000, 1100, 1200, and 1300). For the sake of brevity, those details will not be repeated here.

[0327] 9 is a flow diagram illustrating a method 900 for outputting a tactile output in response to detecting contact movement, according to some embodiments. Method 900 is performed in an electronic device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1A) that includes a display, a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface, and one or more tactile output generators. In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on or integrated into the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations of method 900 are optionally combined, and / or the order of some operations is optionally changed.

[0328] As described below, the method 900 provides feedback when a user's movement of an icon is detected, giving the user an intuitive sense of the icon's movement. The method helps the user understand the connection between input and device response to the input, thereby creating a more efficient human-machine interface.

[0329] The device 902 displays a first user interface (e.g., an application springboard) that includes a plurality of icons of a first type (e.g., application launch icons) and at least one icon of a second type (e.g., a folder icon) that is different from the first type. For example, the user interface 5180a is an application springboard that includes a plurality of application launch icons, including application launch icons 5178 and 5182 and a folder icon 5184.

[0330] While the focus selector is over a first icon of a first type (e.g., icon 5178), the device detects (904) movement of contact 5150 across the touch-sensitive surface in a drag gesture. (For example, contact 5150 moves across the first user interface from a first position at time t1 shown in user interface 5180b, to a second position at time t2 shown in diagram 5180c, and then to a third position at time t3 shown in diagram 5180d.) For example, the device detects a drag gesture by the contact on the touch-sensitive display while the contact is over the first draggable icon, or detects a drag gesture by the contact on the touch-sensitive surface while a cursor or other pointer is over the first draggable icon on the display.

[0331] In response to detecting movement of the contact across the touch-sensitive surface in a drag gesture while the focus selector is over the first icon (906), the device moves the first icon across the display (908) in accordance with the movement of the first contact in the drag gesture (e.g., icon 5178 moves from a first position at time t1 shown in user interface 5180b, to a second position at time t2 shown in user interface 5180c, to a third position at time t3 shown in user interface 5180d). In some embodiments, in response to determining that the first icon moved over one or more other icons of a first type during the drag gesture, the device outputs (910) one or more tactile outputs of a first type using one or more tactile output generators, each tactile output of the first type having a first tactile output profile. For example, when first icon 5178 moves over icon 5182, tactile output 5172 is generated, as shown in user interface 5180c. Upon completion of the drag gesture, in accordance with a determination that the drag gesture moved the first icon over an icon of a second type, the device displays (912) a second user interface corresponding to the icon of the second type (e.g., displaying a user interface for a folder corresponding to a folder icon), and the device outputs, using one or more tactile output generators, a tactile output of the second type, where the tactile output of the second type has a second tactile output profile that is different from the first tactile output profile. For example, as shown in user interface 5180d, first icon 5178 moves over folder icon 5184, and in response, user interface 5180e including an enlarged folder corresponding to folder icon 5184 is displayed and tactile output 5169 (and / or 5176) is generated. In some embodiments, user interface 5180e for the folder is superimposed on the first user interface (e.g., a springboard user interface as shown in 5180d). In some embodiments, the user interface 5180e for the folder 5184 replaces the display of the first user interface 5180d.In some embodiments, the second type of tactile output (e.g., the series of taps 5169) is a continuous output while the second user interface is displayed, while the first type of tactile output is a discrete tap output (e.g., the tap output represented by the bar 5172) as the first icon 5178 moves over another icon 5182 of the first type.

[0332] In some embodiments, the drag gesture occurs while the first user interface is in a user interface reconfiguration mode. In some embodiments, a continuous tactile output 5167 (e.g., a continuous output 5168 having a different output profile, such as a different tactile output amplitude, tactile output density, and / or tactile output frequency) is provided while the first user interface is in a user interface reconfiguration mode that is separate from the first type of tactile output (e.g., a discrete tap output, e.g., 5172) and separate from the second type of tactile output. In some embodiments, the user interface reconfiguration mode is entered in response to detecting a fixation input (e.g., a press and hold input) while the focus selector is over the first icon.

[0333] In some embodiments, a tactile output is also provided when other icons in the first user interface rearrange to fill the gap caused by the movement of the first icon.

[0334] It should be understood that the particular order described of the operations in FIG. 9 is merely an example, and that the described order is not intended to indicate the only order in which the operations may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that other processing details described herein with respect to the other methods described herein (e.g., methods 600, 700, 800, 1000, 1100, 1200, and 1300) are also applicable in a similar manner to method 900 described above with respect to FIG. 9. For example, the contacts, gestures, user interface objects, tactile outputs, focus selectors, and animations described above with respect to method 900 optionally have the characteristics of one or more of the contacts, gestures, user interface objects, tactile outputs, focus selectors, and animations described herein with respect to the other methods described herein (e.g., methods 600, 700, 800, 1000, 1100, 1200, and 1300). For the sake of brevity, those details will not be repeated here.

[0335] 10 is a flow diagram illustrating a method 1000 for providing output according to input detected by contact in a user interface including a plurality of icons, according to some embodiments. Method 1000 is performed in an electronic device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1A) that includes a display, a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface, and one or more tactile output generators. In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on or integrated into the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations of method 1000 are optionally combined, and / or the order of some operations is optionally changed.

[0336] As described below, the method 1000 provides feedback as the user interacts with the icons, giving the user an intuitive sense of icon interaction. The method helps the user understand the connection between input and device response to the input, thereby creating a more efficient human-machine interface.

[0337] The device displays 1002 a first user interface (e.g., a photo management application) that includes a plurality of icons (e.g., thumbnail image icons of larger digital images, documents, or other content). For example, the device displays a photo management application as shown in user interface 5202 of FIG. 5P, which includes a plurality of thumbnail image icons, including thumbnail image icon 5206a.

[0338] The device detects a first input by a contact on the touch-sensitive surface while the focus selector is over a first icon having a first size in the plurality of icons (1004). For example, the device detects input by contact 5204 on the touch-sensitive display while the contact is over first icon 5206a, or the device detects input by contact on the touch-sensitive surface while a cursor or other pointer is over the first icon on the display.

[0339] In response to detecting a first input by contact on the touch-sensitive surface (1006), and in accordance with a determination that the first input satisfies preview display criteria (1008), the device displays a preview of the object corresponding to the first icon having a second size larger than the first size (e.g., a preview of a larger digital image as shown at 5206b in FIG. 5Q), and the device outputs a first type of tactile output having a first tactile output profile (e.g., a spring effect) using one or more tactile output generators. In some embodiments, the preview display criteria include criteria that are met if at least a first portion of the first input by contact is a fixed input, such as a tap-and-hold gesture. In some embodiments, in accordance with a determination that the first input satisfies scrolling criteria (1010) that are different from the preview display criteria, the device ceases displaying the preview of the object corresponding to the first icon, ceases outputting the first type of tactile output using the one or more tactile output generators, and scrolls the plurality of icons. For example, scrolling occurs as shown in FIGS. 5V-5W. In some embodiments, the scrolling criteria include criteria that are met if at least a first portion of the first input by contact is a movement input, such as a drag gesture, a swipe gesture, and / or a finger roll gesture.

[0340] In some embodiments, while displaying a preview of an object corresponding to a first icon (e.g., 5206b shown in FIGS. 5Q and 5R-1), the device detects a second input by contact (e.g., movement of the contact along the path indicated by arrow 5210 from the position indicated by focus selector 5204a to the position indicated by focus selector 5204b). In response to detecting the second input, the device moves the focus selector from the first icon to a second icon in the plurality of icons, displays a preview of the object corresponding to the second icon having a second size larger than the first size (e.g., a preview of a larger digital image as shown at 5212b in FIG. 5R-2), and outputs a second type of tactile output (e.g., a “tick” as represented by point 5218b in FIG. 5R-4). In some embodiments, the second input uses the same continuous contact with the touch-sensitive surface as the first input.

[0341] It should be understood that the particular order described of the operations in FIG. 10 is merely an example, and that the described order is not intended to indicate the only order in which the operations may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein. In addition, it should be noted that other processing details described herein with respect to the other methods described herein (e.g., methods 600, 700, 800, 900, 1100, 1200, and 1300) are also applicable in a similar manner to method 1000 described above with respect to FIG. 10. For example, the contacts, gestures, user interface objects, tactile outputs, focus selectors, and animations described above with respect to method 1000 optionally have the characteristics of one or more of the contacts, gestures, user interface objects, tactile outputs, focus selectors, and animations described herein with respect to the other methods described herein (e.g., methods 600, 700, 800, 900, 1100, 1200, and 1300). For the sake of brevity, those details will not be repeated here.

[0342] 11A-11B are flow diagrams illustrating a method 1100 of providing haptic feedback, according to some embodiments. Method 1100 is performed in an electronic device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1A) that includes a display, a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface, and one or more tactile output generators. In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on or integrated into the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations of method 700 are optionally combined, and / or the order of some operations is optionally changed.

[0343] As described below, method 1100 provides an intuitive way to provide an indication of several communications received by a device. A user may need to check several received notifications without activating the device, for example, when activating the device would be inappropriate or undesirable. Additionally, a user may want to evaluate several communications received by the device without individually reviewing the notifica...

Claims

1. 1. A method comprising: An electronic device comprising a display, a touch-sensitive surface, and one or more tactile output generators, displaying a user interface on the display, the user interface including a plurality of user interface objects; detecting touch input on the touch-sensitive surface by a contact that moves a focus selector from a first user interface object of the plurality of user interface objects in a first direction on the display; In response to detecting the touch input, generating, with the one or more tactile output generators, a sequence of one or more tactile outputs corresponding to movement of the focus selector in the first direction in accordance with determining that the first user interface object is selected when the focus selector is moved in the first direction; moving the first user interface object in the first direction while ceasing to generate the sequence of one or more tactile outputs corresponding to the movement of the focus selector in the first direction in accordance with a determination that the first user interface object is not selected when the focus selector is moved in the first direction.

2. 2. The method of claim 1, further comprising, in response to detecting the touch input, moving the first user interface object in accordance with the movement of the focus selector, regardless of whether the first user interface object is selected.

3. 2. The method of claim 1, further comprising: in response to detecting the touch input, moving the first user interface object relative to at least one other user interface object in the plurality of user interface objects in accordance with a determination that the first user interface object is selected.

4. 4. The method of claim 3, further comprising: in response to detecting the touch input, displaying a preview of another object corresponding to the first user interface object in accordance with a determination that the first user interface object is selected.

5. 4. The method of claim 3, comprising generating, when the first user interface object is moved, a discrete tactile output corresponding to the movement of the first user interface object relative to the at least one other user interface object in the plurality of user interface objects.

6. 4. The method of claim 3, comprising generating, in response to the movement of the first user interface object, a discrete tactile output corresponding to the movement of another user interface object when the first user interface object is moved.

7. 2. The method of claim 1, comprising, in response to selecting the first user interface object, generating a tactile output corresponding to the selection of the first user interface object that is different from the sequence of one or more tactile outputs corresponding to movement of the first user interface object.

8. 2. The method of claim 1, further comprising: in response to detecting the touch input, moving a second user interface object within the plurality of user interface objects together with the first user interface object in accordance with a determination that the first user interface object is not selected.

9. In response to detecting a first portion of the touch input, selecting the first user interface object; generating a tactile output indicating that the user interface is in a first state in which the first user interface object is selected; The method of claim 1 , comprising:

10. detecting a change in a state of the user interface from the first state to a second state while the touch input is detected and while the first user interface object is selected; 10. The method of claim 9, comprising: in response to detecting the change in the state of the user interface from the first state to the second state, changing from generating a first state tactile output to generating one or more second state tactile outputs that differ from the first state tactile output to indicate that the change in the state of the user interface from the first state to the second state has occurred.

11. 11. The method of claim 10, wherein generating the one or more second state tactile outputs comprises generating a sequence of one or more tactile outputs while the second state is an active state of the user interface.

12. The method of claim 10 , wherein the changing of the state of the user interface from the first state to the second state includes displaying a second user interface superimposed on the first user interface.

13. The method of claim 10 , wherein the changing of the state of the user interface from the first state to the second state includes replacing the display of a first user interface with a second user interface.

14. 1. An electronic device comprising: The display and a touch-sensitive surface; and one or more tactile output generators; one or more processors; Memory and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions that: displaying a user interface on the display, the user interface including a plurality of user interface objects; detecting touch input on the touch-sensitive surface with a contact that moves a focus selector from a first user interface object of the plurality of user interface objects in a first direction on the display; In response to detecting the touch input, pursuant to determining that the first user interface object is selected when the focus selector is moved in the first direction, generating, with the one or more tactile output generators, a sequence of one or more tactile outputs corresponding to movement of the focus selector in the first direction; and moving the first user interface object in the first direction while ceasing to generate the sequence of one or more tactile outputs corresponding to the movement of the focus selector in the first direction in accordance with a determination that the first user interface object is not selected when the focus selector is moved in the first direction.

15. 15. The electronic device of claim 14, wherein the one or more programs contain instructions for carrying out the method of any one of claims 2 to 13.

16. A computer program comprising: When executed by an electronic device comprising a display, a touch-sensitive surface, and one or more tactile output generators, the electronic device: displaying a user interface on the display, the user interface including a plurality of user interface objects; detecting touch input on the touch-sensitive surface by a contact that moves a focus selector from a first user interface object of the plurality of user interface objects in a first direction on the display; In response to detecting the touch input, pursuant to determining that the first user interface object is selected when the focus selector is moved in the first direction, generating, with the one or more tactile output generators, a sequence of one or more tactile outputs corresponding to movement of the focus selector in the first direction; moving the first user interface object in the first direction while ceasing to generate the sequence of one or more tactile outputs corresponding to the movement of the focus selector in the first direction in accordance with a determination that the first user interface object is not selected when the focus selector is moved in the first direction; A computer program containing instructions.

17. 17. A computer program according to claim 16, further comprising instructions which, when executed by the electronic device, cause the electronic device to carry out the method of any one of claims 2 to 13.

Images