Patent Grant
10955956
This relates generally to electronic devices with displays and intensity-sensitive input regions, including but not limited to electronic devices with displays and intensity-sensitive off-display input regions.
Many electronic devices with displays include mechanical buttons, such as mechanical home buttons, volume buttons, and power buttons. But mechanical buttons provide little, if any, feedback to a user beyond a fixed down click and a fixed up click. Some devices have solid state home buttons on the display-side of the devices to replace the mechanical home buttons. A display-side solid state home button is coupled with tactile output generators that generate tactile outputs to simulate various types of mechanical button clicks when the solid state home button is activated by a press input. The solid state home button is a close analog of a mechanical home button and is designated for a very limited set of functions triggered by a few types of press inputs. Display-side solid state buttons also take up valuable space on the display-side of the device, reducing available display area for visual information on a portable electronic device.
Accordingly, there is a need for electronic devices with improved methods and interfaces for providing visual, haptic, and/or audio feedback during interaction with an off-display input region (e.g., an intensity-sensitive side button or surface), which make manipulation of user interfaces more efficient and intuitive for a user. There is also a need for electronic devices with improved methods and interfaces for providing additional functionality without cluttering up the display with more virtual controls or crowding the surface of the device with more hardware controls. Such methods and interfaces optionally complement or replace conventional methods for providing additional function controls and providing feedback during interaction with a device using a button. Such methods and interfaces reduce the number and extent of the inputs required from a user by helping the user to understand the connection between provided inputs and device responses to the inputs and reducing user input mistakes, thereby creating a more efficient human-machine interface.
The above deficiencies and other problems associated with user interfaces for electronic devices with buttons are reduced or eliminated by the disclosed devices, which include one or more intensity-sensitive input regions (e.g., off-display intensity-sensitive buttons or surfaces located on peripheral sides of the device). In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the device is a personal electronic device (e.g., a wearable electronic device, such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen” or “touch-screen display”). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and/or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions optionally include image editing, drawing, presenting, word processing, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music playing, note taking, and/or digital video playing. Executable instructions for performing these functions are, optionally, included in a non-transitory computer readable storage medium or other computer program product configured for execution by one or more processors.
In accordance with some embodiments, a method is performed at an electronic device with a display and a first input region that is separate from the display. The method includes: detecting a first portion of a first input on the first input region; in response to detecting the first portion of the first input: in accordance with a determination that the first portion of the first input meets first criteria, wherein the first criteria include a set of criteria that are met when the first input is detected on the first input region without a characteristic intensity of the first input increasing above a first intensity threshold, providing a first output that indicates a current state of a first attribute of the device without altering the first attribute of the device; detecting a second portion of the input, including detecting an increase in intensity of the first input; and in response to detecting the second portion of the first input: in accordance with a determination that the second portion of the first input meets second criteria before an end of the first input is detected, wherein the second criteria include a set of criteria that are met when the characteristic intensity of the first input increases above the first intensity threshold, performing a first operation that alters the first attribute of the device; and in accordance with a determination that the second portion of the first input does not meet the second criteria, forgoing performing the first operation that alters the first attribute of the device.
In accordance with some embodiments, a method is performed at an electronic device with a display, and a first input region that is separate from the display. The method includes: detecting a first portion of a first input on the first input region; in response to detecting the first portion of the first input on the first input region: in accordance with a determination that the first portion of the first input meets first criteria, wherein the first criteria include a set of criteria that are met when the first input is detected on the first input region without a characteristic intensity of the first input increasing above a first intensity threshold, displaying, on the display, a precursor object of a user interface object that includes one or more selectable options; while displaying the precursor object on the display, detecting a second portion of the first input on first input region, including detecting an increase in intensity of the first input above the first intensity threshold; and in response to detecting the increase in intensity of the first input during the second portion of the first input, revealing the user interface object on the display by an amount that varies in accordance with a current intensity of the first input.
In accordance with some embodiments, a method is performed at an electronic device with a display, an input region that is distinct from the display and includes a first sub-region and a second sub-region. The method includes: detecting an input on the input region; in response to detecting the input on the input region: in accordance with a determination that the input meets first criteria, wherein the first criteria require an increase in intensity of the input above a first intensity threshold while the input is detected in the first sub-region of the input region, in order for the first criteria to be met, modifying a first parameter of the device in a first manner; in accordance with a determination that the input meets second criteria that are distinct from the first criteria, wherein the second criteria require an increase in intensity of the input above the first intensity threshold while the input is detected in the second sub-region of the input region that is distinct from the first sub-region, in order for the second criteria to be met, modifying the first parameter of the device in a second manner that is distinct from the first manner; and in accordance with a determination that the input did not increase above the first intensity threshold, forgoing modifying the first parameter of the device in the first manner and forgoing modifying the first parameter of the device in the second manner.
In accordance with some embodiments, a method is performed at an electronic device with a display, one or more cameras, and a plurality of tactile output generators including a first tactile output generator at a first location in the device and a second tactile output generator at a second location in the device. The method includes: while the device is in a media capture mode of operation, performing a respective task: detecting that one or more objects in a field of view of the one or more cameras of the device meet first criteria; and in response to detecting that the one or more objects in the field of view of the one or more cameras meet the first criteria, generating, with one or more of the plurality of tactile output generators, a tactile output prompting movement of the field of view of the one or more cameras in a respective direction, wherein generating the tactile output prompting movement of the field of view of the one or more cameras in the respective direction includes: in accordance with a determination, based on the one or more objects in the field of view of the camera, that the field of view of the camera needs to be shifted in a first direction to continue performing the respective task, generating a first tactile output that prompts movement of the field of view of the one or more cameras in the first direction; and in accordance with a determination, based on the one or more objects in the field of view of the camera, that the field of view of the camera needs to be shifted in a second direction, different from the first direction, to continue performing the respective task, generating a second tactile output, different from the first tactile output, that prompts movement of the field of view of the one or more cameras in the second direction.
In accordance with some embodiments, a method is performed at an electronic device with a display, and an input region that is associated with a tactile output generator. The method includes: detecting an input on the input region; in response to detecting the input on the input region: in accordance with a determination that first criteria are met by the input on the input region, wherein the first criteria include a requirement that is met when a first input metric exceeds a first threshold in order for the first criteria to be met, generating a first tactile output with the tactile output generator associated with the input region; and after generating the first tactile output: in accordance with a determination that the input meets second criteria, wherein the second criteria include a requirement that is met when the first input metric exceeds a second threshold that is greater than the first threshold in order for the second criteria to be met, performing an operation; and in accordance with a determination that a cancellation input has been detected prior to the input meeting the second criteria, forgoing performance of the operation; and in accordance with a determination that the first criteria are not met by the input on the input region, forgoing generating the first tactile output.
In accordance with some embodiments, a method is performed at an electronic device with a display, an input region that is distinct from the display, and one or more tactile output generators for generating tactile outputs. The method includes: detecting a press input on the input region with a finger; and in response to detecting the press input on the input region: in accordance with a determination that the input region is not separated from the finger by an interstitial material, generating a first tactile output; and in accordance with a determination that the input region is separated from the finger by a first interstitial material, generating a second tactile output that is different from the first tactile output.
In accordance with some embodiments, a method is performed at an electronic device with a display that is disposed on a front-side of the device, an input region that is disposed on one or more peripheral-sides of the device adjacent to the front-side of the device, and one or more tactile output generators for generating tactile outputs. The method includes: detecting an input on the input region; in response to detecting the input on the input region: in accordance with a determination that the input by the contact on the input region meets first criteria, wherein the first criteria require an increase in intensity of the input above a first intensity threshold in order for the first criteria to be met, performing a first operation and generating a first tactile output with a first tactile output profile; and in accordance with a determination that the input on the input region meets second criteria that are distinct from the first criteria, wherein the second criteria require that the input includes movement of a contact along a first direction across the input region in order for the second criteria to be met, performing a second operation different from the first operation and generating a second tactile output with a second tactile output profile that is distinct from the first tactile output profile.
In accordance with some embodiments, an electronic device includes a display, a touch-sensitive surface, one or more intensity-sensitive input regions (e.g., side buttons), one or more sensors to detect intensities of contacts with the touch-sensitive surface and the input regions, optionally, one or more tactile output generators for generating localized tactile outputs at the input regions and/or whole device tactile outputs throughout multiple regions of the device, one or more processors, memory, and one or more programs; the one or more programs are stored in the memory and configured to be executed by the one or more processors and the one or more programs include instructions for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, a computer readable storage medium has stored therein instructions which when executed by an electronic device with a display, a touch-sensitive surface, one or more intensity-sensitive input regions (e.g., side buttons), one or more sensors to detect intensities of contacts with the touch-sensitive surface and the input regions, and optionally, one or more tactile output generators for generating localized tactile outputs at the input regions and/or whole device tactile outputs throughout multiple regions of the device, cause the device to perform or cause performance of the operations of any of the methods described herein. In accordance with some embodiments, a graphical user interface on an electronic device with a display, a touch-sensitive surface, one or more intensity-sensitive input regions (e.g., side buttons), one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally, one or more tactile output generators for generating localized tactile outputs at the input regions and/or whole device tactile outputs throughout multiple regions of the device, a memory, and one or more processors to execute one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described herein, which are updated in response to inputs, as described in any of the methods described herein. In accordance with some embodiments, an electronic device includes: a display, a touch-sensitive surface, one or more intensity-sensitive input regions (e.g., side buttons), one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally, one or more tactile output generators for generating localized tactile outputs at the input regions and/or whole device tactile outputs throughout multiple regions of the device; and means for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a display and a touch-sensitive surface, one or more intensity-sensitive input regions (e.g., side buttons), one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally, one or more tactile output generators for generating localized tactile outputs at the input regions and/or whole device tactile outputs throughout multiple regions of the device, includes means for performing or causing performance of the operations of any of the methods described herein.
Thus, electronic devices with displays, touch-sensitive surfaces, one or more intensity-sensitive input regions (e.g., side buttons), one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally, one or more tactile output generators for generating localized tactile outputs at the input regions and/or whole device tactile outputs throughout multiple regions of the device, optionally one or more device orientation sensors, and optionally an audio system, are provided with improved methods and interfaces for providing feedback to a user during interaction with an off-display input region, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for facilitating interactions with the device and providing haptic feedback to a user.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
FIGS. 4F1-4F4 and 4G1-4G4 illustrate a set of sample tactile output patterns in accordance with some embodiments.
FIGS. 5A1-5A8 illustrate exemplary user interfaces for providing haptic and visual feedback for button interactions corresponding to querying and/or modifying a current state of a device attribute in accordance with some embodiments.
FIGS. 5B1-5B11 illustrate exemplary user interfaces for providing haptic and visual feedback for button interactions corresponding to modifying a device parameter in different manners in accordance with some embodiments.
FIGS. 5C1-5C20 and 5D1-5D24 illustrate exemplary user interfaces for providing haptic and visual feedback for different types of button interactions corresponding to presenting and interacting with a retractable menu in accordance with some embodiments.
FIGS. 5E1-5E5 and 5F1-5F6 illustrate exemplary user interfaces for providing haptic and visual feedback for guiding device movement to perform a respective task when the device is in a media capture mode of operation in accordance with some embodiments.
FIGS. 5G1-5G5 and 5H1-5H5 illustrate exemplary user interfaces for providing haptic and visual feedback for warning a user of impending performance of an operation in accordance with some embodiments.
FIGS. 5I1-5I6 illustrate providing, for each respective type of button interaction, tactile outputs that have varying tactile output profiles depending on the presence of an interstitial material between the input region and the user's finger in accordance with some embodiments.
Many electronic devices with displays include mechanical buttons, such as mechanical home buttons, for triggering device functions and navigating between user interfaces. Some devices have solid state home buttons that mimics mechanical home buttons by providing localized tactile outputs in response to press inputs detected on the solid state home buttons. But mechanical buttons and solid state home button are suitable for activating only a couple of fixed functions, and provide little feedback beyond simple button clicks. Methods described herein provide visual, haptic, and/or audio feedback during a variety of user interactions with an intensity-sensitive off-screen input region (e.g., a side button or surface) that make manipulation of user interfaces more efficient and intuitive for a user.
The methods, devices, and GUIs described herein providing novel and improved ways of triggering device functions and using haptic and visual feedback to improve device-user interactions, including:
Reference will now be made in detail to 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 described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments 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.
It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact, unless the context clearly indicates otherwise.
The terminology used in the description of the various described embodiments 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 described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
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 communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Example embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch-screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch-screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display, a touch-sensitive surface, and one or more off-display intensity-sensitive input regions is described. It should be understood, however, 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.
The device typically supports a variety of applications, such as one or more of the following: a note taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout 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.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface or the one or more intensity-sensitive off-display input regions. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface or intensity-sensitive off-display input regions) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display, a trackpad, an intensity-sensitive side button, or a solid state button) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button, a “detent” of a physical scroll-wheel or dial, and/or a “snap” of a mechanical switch or toggle, etc. In some cases, a user will feel a tactile sensation, such as an “down click” or “up click”, a “detent”, or a “snap”, even when there is no movement of an input region that is physically pressed or swiped by the user's finger movements, before the movement of the input region is detected, and/or when the movement of the input region is drastically different from the movement that a physical mechanical button, scroll-wheel or dial, or switch would undergo to produce the tactile sensations that the user perceives through the input region. As another example, movement of the touch-sensitive surface (e.g., a touch-sensitive display, a trackpad, an intensity-sensitive side button, or a solid state button) is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”, “detent”, or “flip and snap of a toggle or switch”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user. Using tactile outputs to provide haptic feedback to a user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, a tactile output pattern specifies characteristics of a tactile output, such as the amplitude of the tactile output, the shape of a movement waveform of the tactile output, the frequency of the tactile output, the mode of motion of the tactile output (e.g., linear oscillations in x direction, y-direction, or z-direction; or angular oscillations around x-axis, y-axis, or z-axis, etc.), and/or the duration of the tactile output.
When tactile outputs with different tactile output patterns are generated by a device, the tactile outputs may invoke different haptic sensations in a user holding or touching the device and/or the input region. The device optionally includes one or more whole device tactile output generators (e.g., a moveable mass that is coupled to the housing of the device) to generate tactile outputs at many different locations on the device at the same time. The device may also include one or more localized tactile output generators (e.g., a surface oscillator that oscillates or vibrates around a fixed pivot in various directions underneath the input region or other tactile output generator that is capable of generating tactile outputs that are directed specifically toward the input region) to generate localized tactile outputs. The localized vibrations have varying amplitudes at different locations on the device with greater amplitudes on the input region or a sub-portion thereof where a user's finger will typically rest while interacting with the input region and with lower amplitudes at other places (e.g., outside of the input region) where a user's hand will not typically rest while interacting with the input region.
While the sensation of the user is based on the user's perception of the tactile output, most users will be able to identify changes in waveform, frequency, mode of motion, and amplitude of tactile outputs generated by the device. Thus, the waveform, frequency, mode of motion, and amplitude can be adjusted to indicate to the user that different types of inputs have been detected on the input region (e.g., an intensity-sensitive side button, a solid state button, a touch pad, or a touch-screen), and/or different operations have been performed. As such, tactile outputs with tactile output patterns that are designed, selected, and/or engineered to simulate characteristics (e.g., size, material, weight, stiffness, smoothness, etc.); behaviors (e.g., oscillation, displacement, acceleration, rotation, expansion, etc.); and/or interactions (e.g., collision, adhesion, repulsion, attraction, friction, etc.) of objects in a given environment (e.g., a user interface that includes graphical features and objects, a simulated physical environment with virtual boundaries and virtual objects, a real physical environment with physical boundaries and physical objects, and/or a combination of any of the above) will, in some circumstances, provide helpful feedback to users that reduces input errors and increases the efficiency of the user's operation of the device. Additionally, tactile outputs are, optionally, generated to correspond to feedback that is unrelated to a simulated physical characteristic, such as an input threshold or a selection of an object. Such tactile outputs will, in some circumstances, provide helpful feedback to users that reduces input errors and increases the efficiency of the user's operation of the device.
In some embodiments, a tactile output with a suitable tactile output pattern serves as a cue for the occurrence of an event of interest in a user interface or behind the scenes in a device. Examples of the events of interest include activation of an affordance (e.g., a real or virtual button, or toggle switch) provided on the device or in a user interface, success or failure of a requested operation, reaching or crossing a boundary in a user interface, entry into a new state, switching of input focus between objects, activation of a new mode, reaching or crossing an input threshold, detection or recognition of a type of input or gesture, etc. In some embodiments, tactile outputs are provided to serve as a warning or an alert for an impending event or outcome that would occur unless a redirection or interruption input is timely detected. Tactile outputs are also used in other contexts to enrich the user experience, improve the accessibility of the device to users with visual or motor difficulties or other accessibility needs, and/or improve efficiency and functionality of the user interface and/or the device.
Tactile outputs are optionally accompanied with audio outputs and/or visible user interface changes, which further enhance a user's experience when the user interacts with a user interface and/or the device, and facilitate better conveyance of information regarding the state of the user interface and/or the device, and which reduce input errors and increase the efficiency of the user's operation of the device. In some embodiments, an accompanying audio enhances the effect of the tactile output and makes the haptic sensation experienced by a user more salient and/or realistic. The tactile output profile of a tactile output is optionally extended to include an audio profile for an accompanying audio output that is generated to supplement the tactile output. The audio profile for an accompanying audio output of a tactile output includes characteristics of the audio output such as timing (e.g., timing offsets from the corresponding tactile output), amplitude (e.g., amplitude specified in predefined values or a ratio or correlation between the amplitude of the audio output and one or more characteristics of the tactile output), frequency (e.g., frequency specified in predefined values or in terms of a relationship with one or more characteristics of the tactile output), shape of a waveform (e.g., a predefined waveform or a waveform specified in terms of a relationship with one or more characteristics of the tactile output). The accompany audio output for a tactile output is distinct from regular device audio output (e.g., audio alerts or media output generated by the device independent of generation of a tactile output).
In some embodiments, multiple different tactile output generators (e.g., whole device tactile output generators, and/or localized tactile output generators located at different locations on the device) coordinate their individual outputs (e.g., with timing coordination, amplitude coordination, and wave pattern coordination, or a combination of the above) to convey a sense of direction around the device (e.g., up, down, left, right, front, back, clockwise, counter-clockwise, etc.), which further enhance a user's experience when the user interacts with a user interface and/or the device, and facilitate better conveyance of information regarding the state of the user interface and/or the device, and which reduce input errors and increase the efficiency of the user's operation of the device. In some embodiments, the tactile output profile of a tactile output to be generated by a respective tactile output generator is extended to identify other tactile output generators and specify the respective manner by which the respective tactile output generator will coordinate with these other tactile output generators to generate coordinated tactile outputs for a respective purpose (e.g., indicate a direction to a user).
FIG. 4F1 provides a set of sample tactile output patterns that may be used, either individually or in combination, either as is or through one or more transformations (e.g., modulation, amplification, truncation, etc.), to create suitable haptic feedback in various scenarios and for various purposes, such as those mentioned above and those described with respect to the user interfaces and methods discussed herein. FIGS. 4F2-4F4 are expanded views of the graphs shown in FIG. 4F1. This example of a palette of tactile outputs shows how a set of three waveforms and eight frequencies can be used to produce an array of tactile output patterns. In addition to the tactile output patterns shown in this figure, each of these tactile output patterns is optionally adjusted in amplitude by changing a gain value for the tactile output pattern, as shown, for example for FullTap 80 Hz, FullTap 200 Hz, MiniTap 80 Hz, MiniTap 200 Hz, MicroTap 80 Hz, and MicroTap 200 Hz in FIG. 4G1, which are each shown with variants having a gain of 1.0, 0.75, 0.5, and 0.25. FIGS. 4G2-4G4 are expanded views of the graphs shown in FIG. 4G1. As shown in FIG. 4G1, changing the gain of a tactile output pattern changes the amplitude of the pattern without changing the frequency of the pattern or changing the shape of the waveform. In some embodiments, changing the frequency of a tactile output pattern also results in a lower amplitude as some tactile output generators are limited by how much force can be applied to the moveable mass and thus higher frequency movements of the mass are constrained to lower amplitudes to ensure that the acceleration needed to create the waveform does not require force outside of an operational force range of the tactile output generator (e.g., the peak amplitudes of the FullTap at 230 Hz, 270 Hz, and 300 Hz are lower than the amplitudes of the FullTap at 80 Hz, 100 Hz, 125 Hz, and 200 Hz).
In FIG. 4F1, each column shows tactile output patterns that have a particular waveform. The waveform of a tactile output pattern represents the pattern of physical displacements relative to a neutral position (e.g., xzero) versus time that a moveable mass goes through to generate a tactile output with that tactile output pattern. For example, a first set of tactile output patterns shown in the left column in FIG. 4F1 (e.g., tactile output patterns of a “FullTap”) each have a waveform that includes an oscillation with two complete cycles (e.g., an oscillation that starts and ends in a neutral position and crosses the neutral position three times). A second set of tactile output patterns shown in the middle column in FIG. 4F1 (e.g., tactile output patterns of a “MiniTap”) each have a waveform that includes an oscillation that includes one complete cycle (e.g., an oscillation that starts and ends in a neutral position and crosses the neutral position one time). A third set of tactile output patterns shown in the right column in FIG. 4F1 (e.g., tactile output patterns of a “MicroTap”) each have a waveform that includes an oscillation that include one-half of a complete cycle (e.g., an oscillation that starts and ends in a neutral position and does not cross the neutral position). The waveform of a tactile output pattern also includes a start buffer and an end buffer that represent the gradual speeding up and slowing down of the moveable mass at the start and at the end of the tactile output. The example waveforms shown in FIG. 4F1-4G4 include xmin and xmax values which represent the maximum and minimum extent of movement of the moveable mass. For larger electronic devices with larger moveable masses, there may be larger or smaller minimum and maximum extents of movement of the mass. The example shown in FIGS. 4F1-4G4 describes movement of a mass in 1 dimension, however similar principles would also apply to movement of a moveable mass in two or three dimensions.
As shown in FIG. 4F1, each tactile output pattern also has a corresponding characteristic frequency that affects the “pitch” of a haptic sensation that is felt by a user from a tactile output with that characteristic frequency. For a continuous tactile output, the characteristic frequency represents the number of cycles that are completed within a given period of time (e.g., cycles per second) by the moveable mass of the tactile output generator. For a discrete tactile output, a discrete output signal (e.g., with 0.5, 1, or 2 cycles) is generated, and the characteristic frequency value specifies how fast the moveable mass needs to move to generate a tactile output with that characteristic frequency. As shown in FIG. 4F1, for each type of tactile output (e.g., as defined by a respective waveform, such as FullTap, MiniTap, or MicroTap), a higher frequency value corresponds to faster movement(s) by the moveable mass, and hence, in general, a shorter time to complete the tactile output (e.g., including the time to complete the required number of cycle(s) for the discrete tactile output, plus a start and an end buffer time). For example, a FullTap with a characteristic frequency of 80 Hz takes longer to complete than FullTap with a characteristic frequency of 100 Hz (e.g., 35.4 ms vs. 28.3 ms in FIG. 4F1). In addition, for a given frequency, a tactile output with more cycles in its waveform at a respective frequency takes longer to complete than a tactile output with fewer cycles its waveform at the same respective frequency. For example, a FullTap at 150 Hz takes longer to complete than a MiniTap at 150 Hz (e.g., 19.4 ms vs. 12.8 ms), and a MiniTap at 150 Hz takes longer to complete than a MicroTap at 150 Hz (e.g., 12.8 ms vs. 9.4 ms). However, for tactile output patterns with different frequencies this rule may not apply (e.g., tactile outputs with more cycles but a higher frequency may take a shorter amount of time to complete than tactile outputs with fewer cycles but a lower frequency, and vice versa). For example, at 300 Hz, a FullTap takes as long as a MiniTap (e.g., 9.9 ms).
As shown in FIG. 4F1, a tactile output pattern also has a characteristic amplitude that affects the amount of energy that is contained in a tactile signal, or a “strength” of a haptic sensation that may be felt by a user through a tactile output with 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 moveable mass from a neutral position when generating the tactile output. In some embodiments, the characteristic amplitude of a tactile output pattern is adjustable, e.g., by a fixed or dynamically determined gain factor (e.g., a value between 0 and 1), in accordance with various conditions (e.g., customized based on user interface contexts and behaviors) 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-speed metric) measures a characteristic of an input (e.g., a rate of change of a characteristic intensity of a contact in a press input or a rate of movement of the contact across a touch-sensitive surface) during the input that triggers generation of a tactile output. In some embodiments, a user-interface-based metric (e.g., a speed-across-boundary metric) measures a characteristic of a user interface element (e.g., a speed of movement of the element across a hidden or visible boundary in a user interface) during the user interface change that triggers generation of the tactile output. In some embodiments, the characteristic amplitude of a tactile output pattern may be modulated by an “envelope” and the peaks of adjacent cycles may have different amplitudes, where one of the waveforms shown above is further modified by multiplication by an envelope parameter that changes over time (e.g., from 0 to 1) to gradually adjust amplitude of portions of the tactile output over time as the tactile output is being generated.
Although specific frequencies, amplitudes, and waveforms are represented in the sample tactile output patterns in FIG. 4F1 for illustrative purposes, tactile output patterns with other frequencies, amplitudes, and waveforms may be used for similar purposes. For example, waveforms that have between 0.5 to 4 cycles can be used. Other frequencies in the range of 60 Hz-400 Hz may be used as well.
In
The top haptic audio pattern “Click A1 audio” is also played in conjunction with “Click A” Soft MiniTap (230 Hz) to simulate a first down-click in a “soft” first click, as shown in
In
The bottom haptic audio pattern “Click A2 audio” is also played in conjunction with “Click A” Soft MiniTap (230 Hz) to simulate a second down-click in a “soft” second click that follows the first click within a predetermined period of time (e.g., as the second click in a double click input), as shown in
In
The top haptic audio pattern “Click B1 audio” is also played in conjunction with “Click B” Soft MiniTap (270 Hz) to simulate a first down-click in a “soft” first click, as shown in
In
The bottom haptic audio pattern “Click B2 audio” is also played in conjunction with “Click B” Soft MiniTap (270 Hz) to simulate a second down-click in a “soft” second click that follows the first click within a predetermined period of time (e.g., as the second click in a double click input), as shown in
In
The top haptic audio pattern “Click C1 audio” is also played in conjunction with “Click C” Soft MiniTap (300 Hz) to simulate a first down-click in a “soft” first click, as shown in
In
The bottom haptic audio pattern “Click C2 audio” is also played in conjunction with “Click C” Soft MiniTap (300 Hz) to simulate a second down-click in a “soft” second click that follows the first click within a predetermined period of time (e.g., as the second click in a double click input), as shown in
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
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 the peripherals interface 118, is, optionally, controlled by memory controller 122.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU(s) 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.
In some embodiments, peripherals interface 118, CPU(s) 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication optionally uses any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence 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.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
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 peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled with any (or none) of the following: a keyboard, infrared port, USB port, stylus, and/or a pointer device such as a mouse. The one or more buttons (e.g., 208,
Touch-sensitive display system 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch-sensitive display system 112. Touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term “affordance” is a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to inputs directed toward the graphical user interface object). Examples of user-interactive graphical user interface objects include, without limitation, a button, slider, icon, selectable menu item, switch, hyperlink, or other user interface control.
Touch-sensitive display system 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch-sensitive display system 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch-sensitive display system 112. In an example embodiment, a point of contact between touch-sensitive display system 112 and the user corresponds to a finger of the user or a stylus.
Touch-sensitive display system 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch-sensitive display system 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch-sensitive display system 112. In an example embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.
Touch-sensitive display system 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen video resolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally makes contact with touch-sensitive display system 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch-sensitive display system 112 or an extension of the touch-sensitive surface formed by the touch screen.
In some embodiments, in addition to the touch screen and/or touchpad, device 100 optionally include one or more off-display touch-sensitive input regions that are separate from the touch-screen and/or touch pad. In some embodiments, the off-display touch-sensitive input regions are positioned on one or more peripheral-sides of the device that is adjacent to the display-side of the device. A touch-sensitive surface of the touch-sensitive input regions are optionally perpendicular to the display of the device. In some embodiments, in addition to being able to detect different levels of intensity of a contact with the input region, the input region is also configured to detect movement in one or more directions across the surface of the input region. In some embodiments, the device will recognize different types of inputs (e.g., press inputs, scroll inputs, and toggle inputs) on the input region based on the movement direction and intensity of the contact detected on the input region, and the device will generate localized tactile outputs at the input region to simulate the haptic feedback provided by a mechanical input device, such as a switch, a slider, a dial, a wheel, or a button. In some embodiments, the off-display touch-sensitive input region is distinct in nature from a touchpad in that, the location and movement of a contact on the off-display touch-sensitive input region does not directly correspond to a location and movement of a focus selector on the display in the manner that the location and movement of a contact on the touchpad would correspond to a location and movement of a focus selector on the display. In fact, frequently, a focus selector is not displayed or required on the display when an off-display input region is used by a user to interact with the device and manipulate a user interface shown on the display. In many cases, the focus of an input on the input region is preset to a location, an object, or a function prior to detection of the input on the input region, and/or based on the type of the input that is detected, as opposed to an exact location of a contact detected on the input region.
Device 100 also includes power system 162 for powering 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, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, haptic feedback module (or set of instructions) 133, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 stores device/global internal state 157, as shown in
Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. In some embodiments, the external port is a Lightning connector that is the same as, or similar to and/or compatible with the Lightning connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif.
Contact/motion module 130 optionally detects contact with touch-sensitive display system 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact (e.g., by a finger or by a stylus), such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts or stylus contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event. Similarly, tap, swipe, drag, and other gestures are optionally detected for a stylus by detecting a particular contact pattern for the stylus.
In some embodiments, detecting a finger tap gesture depends on the length of time between detecting the finger-down event and the finger-up event, but is independent of the intensity of the finger contact between detecting the finger-down event and the finger-up event. In some embodiments, a tap gesture is detected in accordance with a determination that the length of time between the finger-down event and the finger-up event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4 or 0.5 seconds), independent of whether the intensity of the finger contact during the tap meets a given intensity threshold (greater than a nominal contact-detection intensity threshold), such as a light press or deep press intensity threshold. Thus, a finger tap gesture can satisfy particular input criteria that do not require that the characteristic intensity of a contact satisfy a given intensity threshold in order for the particular input criteria to be met. For clarity, the finger contact in a tap gesture typically needs to satisfy a nominal contact-detection intensity threshold, below which the contact is not detected, in order for the finger-down event to be detected. A similar analysis applies to detecting a tap gesture by a stylus or other contact. In cases where the device is capable of detecting a finger or stylus contact hovering over a touch sensitive surface, the nominal contact-detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch sensitive surface.
The same concepts apply in an analogous manner to other types of gestures. For example, a swipe gesture, a pinch gesture, a depinch gesture, and/or a long press gesture are optionally detected based on the satisfaction of criteria that are either independent of intensities of contacts included in the gesture, or do not require that contact(s) that perform the gesture reach intensity thresholds in order to be recognized. For example, a swipe gesture is detected based on an amount of movement of one or more contacts; a pinch gesture is detected based on movement of two or more contacts towards each other; a depinch gesture is detected based on movement of two or more contacts away from each other; and a long press gesture is detected based on a duration of the contact on the touch-sensitive surface with less than a threshold amount of movement. As such, the statement that particular gesture recognition criteria do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met means that the particular gesture recognition criteria are capable of being satisfied if the contact(s) in the gesture do not reach the respective intensity threshold, and are also capable of being satisfied in circumstances where one or more of the contacts in the gesture do reach or exceed the respective intensity threshold. In some embodiments, a tap gesture is detected based on a determination that the finger-down and finger-up event are detected within a predefined time period, without regard to whether the contact is above or below the respective intensity threshold during the predefined time period, and a swipe gesture is detected based on a determination that the contact movement is greater than a predefined magnitude, even if the contact is above the respective intensity threshold at the end of the contact movement. Even in implementations where detection of a gesture is influenced by the intensities of contacts performing the gesture (e.g., the device detects a long press more quickly when the intensity of the contact is above an intensity threshold or delays detection of a tap input when the intensity of the contact is higher), the detection of those gestures does not require that the contacts reach a particular intensity threshold so long as the criteria for recognizing the gesture can be met in circumstances where the contact does not reach the particular intensity threshold (e.g., even if the amount of time that it takes to recognize the gesture changes).
Contact intensity thresholds, duration thresholds, and movement thresholds are, in some circumstances, combined in a variety of different combinations in order to create heuristics for distinguishing two or more different gestures directed to the same input element or region so that multiple different interactions with the same input element are enabled to provide a richer set of user interactions and responses. The statement that a particular set of gesture recognition criteria do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met does not preclude the concurrent evaluation of other intensity-dependent gesture recognition criteria to identify other gestures that do have a criteria that is met when a gesture includes a contact with an intensity above the respective intensity threshold. For example, in some circumstances, first gesture recognition criteria for a first gesture—which do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the first gesture recognition criteria to be met—are in competition with second gesture recognition criteria for a second gesture—which are dependent on the contact(s) reaching the respective intensity threshold. In such competitions, the gesture is, optionally, not recognized as meeting the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are met first. For example, if a contact reaches the respective intensity threshold before the contact moves by a predefined amount of movement, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves by the predefined amount of movement before the contact reaches the respective intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such circumstances, the first gesture recognition criteria for the first gesture still do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the first gesture recognition criteria to be met because if the contact stayed below the respective intensity threshold until an end of the gesture (e.g., a swipe gesture with a contact that does not increase to an intensity above the respective intensity threshold), the gesture would have been recognized by the first gesture recognition criteria as a swipe gesture. As such, particular gesture recognition criteria that do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met will (A) in some circumstances ignore the intensity of the contact with respect to the intensity threshold (e.g. for a tap gesture) and/or (B) in some circumstances still be dependent on the intensity of the contact with respect to the intensity threshold in the sense that the particular gesture recognition criteria (e.g., for a long press gesture) will fail if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognize an input as corresponding to an intensity-dependent gesture before the particular gesture recognition criteria recognize a gesture corresponding to the input (e.g., for a long press gesture that is competing with a deep press gesture for recognition).
Graphics module 132 includes various known software components for rendering and displaying graphics on touch-sensitive display system 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing, to camera 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, 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 replication.
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 includes executable instructions to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers and/or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, Apple Push Notification Service (APNs) or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 146, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (in sports devices and smart watches); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.
In conjunction with touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, and/or delete a still image or video from memory 102.
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 to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
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, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
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, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.
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 modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
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, the widget creator module 150 includes executable instructions to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction 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 for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back 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 (trademark of Apple Inc.).
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 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.
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 on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes executable instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen 112, or on an external display connected wirelessly or via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video.
Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display system 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display system 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral 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 more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views, when touch-sensitive display system 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
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 a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (i.e., the first sub-event in the sequence of sub-events that form an event or potential event). Once the 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.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver module 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of 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, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 includes one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective 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 at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event 187 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display system 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display system 112, when a touch is detected on touch-sensitive display system 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event 187 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module 145. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input-devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
In some embodiments, the tactile output module includes haptic feedback module 133. In some embodiments, haptic feedback module 133 aggregates and combines tactile outputs for user interface feedback from software applications on the electronic device (e.g., feedback that is responsive to user inputs that correspond to displayed user interfaces and alerts and other notifications that indicate the performance of operations or occurrence of events in user interfaces of the electronic device). Haptic feedback module 133 includes one or more of: waveform module 123 (for providing waveforms used for generating tactile outputs), mixer 125 (for mixing waveforms, such as waveforms in different channels), compressor 127 (for reducing or compressing a dynamic range of the waveforms), low-pass filter 129 (for filtering out high frequency signal components in the waveforms), and thermal controller 131 (for adjusting the waveforms in accordance with thermal conditions). In some embodiments, haptic feedback module 133 is included in haptic feedback controller 161 (
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 a tactile output is to be generated and initiates the process for generating the corresponding tactile output). In some embodiments, trigger module 121 generates trigger signals for initiating generation of waveforms (e.g., by waveform module 123). For example, trigger module 121 generates trigger signals based on preset timing criteria. In some embodiments, trigger module 121 receives trigger signals from outside haptic feedback module 133 (e.g., in some embodiments, haptic feedback module 133 receives trigger signals from hardware input processing module 199 located outside haptic feedback module 133) and relays the trigger signals to other components within haptic feedback module 133 (e.g., waveform module 123) or software applications that trigger operations (e.g., with trigger module 121) based on activation of the hardware input device (e.g., a home button, a side button, a power button, etc.). In some embodiments, trigger module 121 also receives tactile feedback generation instructions (e.g., from haptic feedback module 133,
Waveform module 123 receives trigger signals (e.g., from trigger module 121) as an input, and in response to receiving trigger signals, provides waveforms for generation of one or more tactile outputs (e.g., waveforms selected from a predefined set of waveforms designated for use by waveform module 123, such as the waveforms described in greater detail below with reference to FIGS. 4F1-4G4).
Mixer 125 receives waveforms (e.g., from waveform module 123) as an input, and mixes together 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 that at least partially overlaps with the first waveform in a second channel) mixer 125 outputs a combined waveform that corresponds to a sum of the two or more waveforms. In some embodiments, mixer 125 also modifies one or more waveforms of the two or more waveforms to emphasize particular waveform(s) over the rest of the two or more waveforms (e.g., by increasing a scale of the particular waveform(s) and/or decreasing a scale of the rest of the waveforms). In some circumstances, mixer 125 selects one or more waveforms to remove from the combined waveform (e.g., the waveform from the oldest source is dropped when there are waveforms from more than three sources that have been requested to be output concurrently by tactile output generator 167)
Compressor 127 receives waveforms (e.g., a combined waveform from mixer 125) as an input, and modifies the waveforms. In some embodiments, compressor 127 reduces the waveforms (e.g., in accordance with physical specifications of tactile output generators 167 (
Low-pass filter 129 receives waveforms (e.g., compressed waveforms from compressor 127) as an input, and filters (e.g., smooths) the waveforms (e.g., removes or reduces high frequency signal components in the waveforms). For example, in some instances, compressor 127 includes, in compressed waveforms, extraneous signals (e.g., high frequency signal components) that interfere with the generation of tactile outputs and/or exceed performance specifications of tactile output generator 167 when the tactile outputs are generated in accordance with the compressed waveforms. Low-pass filter 129 reduces or removes such extraneous signals in the waveforms.
Thermal controller 131 receives waveforms (e.g., filtered waveforms from low-pass filter 129) as an input, and adjusts the waveforms in accordance with thermal conditions of device 100 (e.g., based on internal temperatures detected within device 100, such as the temperature of haptic feedback controller 161, and/or external temperatures detected by device 100). For example, in some cases, the output of haptic feedback controller 161 varies depending on the temperature (e.g. haptic feedback controller 161, in response to receiving same waveforms, generates a first tactile output when haptic feedback controller 161 is at a first temperature and generates a second tactile output when haptic feedback controller 161 is at a second temperature that is distinct from the first temperature). For example, the magnitude (or the amplitude) of the tactile outputs may vary depending on the temperature. To reduce the effect of the temperature variations, the waveforms are modified (e.g., an amplitude of the waveforms is increased or decreased based on the temperature).
In some embodiments, haptic feedback module 133 (e.g., trigger module 121) is coupled to hardware input processing module 199. In some embodiments, other input controller(s) 160 in
In some embodiments, the tactile output module includes haptic feedback controller 161 (e.g., haptic feedback controller 161 in
In some embodiments, as shown in
In some embodiments, the tactile output module includes amplifier 163. In some embodiments, amplifier 163 receives waveforms (e.g., from haptic feedback controller 161) and amplifies the waveforms prior to sending the amplified waveforms to tactile output generator(s) 167 (e.g., any one or more of tactile output generators 167 (
In some embodiments, the tactile output module includes sensor 169, which is coupled to tactile output generator 167. Sensor 169 detects states or state changes (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 tactile outputs). 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., a position, a displacement, and/or a movement of one or more parts in tactile output generator 167) to haptic feedback controller 161 and, in accordance with the information provided by sensor 169 about the state of tactile output generator 167, haptic feedback controller 161 adjusts the waveforms output from haptic feedback controller 161 (e.g., waveforms sent to tactile output generator 167, optionally via amplifier 163).
Device 100 optionally also includes one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch-screen display. In some embodiments, the home button is removed and its functions are invoked by a predefined gesture on the touch-sensitive display (e.g., an upward swipe gesture from the bottom edge of the touch-screen display).
In some embodiments, device 100 includes the touch-screen display, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In some embodiments, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensities of contacts on touch-sensitive display system 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100. In some embodiments, the volume buttons 208 and the push button 206 are replaced by an intensity-sensitive input region that is coupled with localized tactile output generators that provide tactile outputs for simulating the feel of a physical button, wheel, switch or other hardware input devices in response to different types of touch inputs.
Both the cover element 222 and the trim 224 can be formed with any suitable opaque, transparent, and/or translucent material. For example, the cover element 222 can be made of glass, plastic, or sapphire and the trim 224 may be made of a metal or plastic. In some embodiments, one or more additional layers (not shown) can be positioned below the cover element 222. For example, an opaque ink layer can be disposed below the cover element 222 when the cover element 222 is made of a transparent material. The opaque ink layer can conceal the other components in the input device stack 220 so that the other components are not visible through the transparent cover element 222.
A first circuit layer 226 can be disposed below the cover element 222. Any suitable circuit layer may be used. For example, the first circuit layer 226 may be a circuit board or a flexible circuit. The first circuit layer 226 can include one or more circuits, signal lines, and/or integrated circuits. In one embodiment, the first circuit layer 226 includes a biometric sensor 228. Any suitable type of biometric sensor can be used. For example, in one embodiment the biometric sensor is a capacitive fingerprint sensor that captures at least one fingerprint when a user's finger (or fingers) approaches and/or contacts the cover element 222.
The first circuit layer 226 may be attached to the bottom surface of the cover element 222 with an adhesive layer 230. Any suitable adhesive can be used for the adhesive layer. For example, a pressure sensitive adhesive layer may be used as the adhesive layer 230.
A compliant layer 232 is disposed below the first circuit layer 226. In one embodiment, the compliant layer 232 includes an opening 234 formed in the compliant layer 232. The opening 234 exposes the top surface of the first circuit layer 226 and/or the biometric sensor 228 when the device stack 220 is assembled. In the illustrated embodiment, the compliant layer 232 is positioned around an interior perimeter of the trim 224 and/or around a peripheral edge of the cover element 222. Although depicted in a circular shape, the compliant layer 232 can have any given shape and/or dimensions, such as a square or oval. The compliant layer 232 is shown as a continuous compliant layer in
A second circuit layer 238 is positioned below the first circuit layer 226. A flexible circuit and a circuit board are examples of a circuit layer that can be used in the second circuit layer 238. In some embodiments, the second circuit layer 238 can include a first circuit section 240 and a second circuit section 242. The first and second circuit sections 240, 242 can be electrically connected one another other.
The first circuit section 240 can include a first set of one or more intensity sensor components that are included in an intensity sensor. In some embodiments, the first circuit section 240 can be electrically connected to the first circuit layer 226. For example, when the first circuit layer 226 includes a biometric sensor 228, the biometric sensor 228 may be electrically connected to the first circuit section 240 of the second circuit layer 238.
The second circuit section 242 can include additional circuitry, such as signal lines, circuit components, integrated circuits, and the like. In one embodiment, the second circuit section 242 may include a board-to-board connector 244 to electrically connect the second circuit layer 238 to other circuitry in the electronic device. For example, the second circuit layer 238 can be operably connected to a processing device using the board-to-board connector 244. Additionally, or alternatively, the second circuit layer 238 may be operably connected to circuitry that transmits signals (e.g., sense signals) received from the intensity sensor component(s) in the first circuit section 240 to a processing device. Additionally, or alternatively, the second circuit layer 238 may be operably connected to circuitry that provides signals (e.g., drive signals, a reference signal) to the one or more intensity sensor components in the first circuit section 240.
In some embodiments, the first circuit section 240 of the second circuit layer 238 may be attached to the bottom surface of the first circuit layer 226 using an adhesive layer 236. In a non-limiting example, a die attach film may be used to attach the first circuit section 240 to the bottom surface of the first circuit layer 226.
A third circuit layer 246 is disposed below the first circuit section 240 of the second circuit layer 238. The third circuit layer 246 may include a second set of one or more intensity sensor components that are included in an intensity sensor. The third circuit layer 246 is supported by and/or attached to a support element 248. In one embodiment, the support element 248 is attached to the trim 224 to produce an enclosure for the other components in the device stack 220. The support element 248 may be attached to the trim 224 using any suitable attachment mechanism.
The first set of one or more intensity sensor components in the first circuit section 240 and the second set of one or more intensity sensor components in the third circuit layer 246 together form an intensity sensor. The intensity sensor can use any suitable intensity sensing technology. Example sensing technologies include, but are not limited to, capacitive, piezoelectric, piezoresistive, ultrasonic, and magnetic.
In the examples shown in
Each electrode in the first set of one or more electrodes 250 is aligned in at least one direction (e.g., vertically) with a respective electrode in the second set of one or more electrodes 252 to produce one or more capacitors. When a force input is applied to the cover element 222 (e.g., the input surface of the input device), at least one electrode in the first set 250 moves closer to a respective electrode in the second set 252, which varies the capacitance of the capacitor(s). A capacitance signal sensed from each capacitor represents a capacitance measurement of that capacitor. A processing device (not shown) is configured to receive the capacitance signal(s) and correlate the capacitance signal(s) to an amount of intensity applied to the cover element 222. In some embodiments, the force sensor can replace a switch element and different intensity thresholds can be used to determine activation events.
In some embodiments, such as the embodiment shown in
Button 710 includes permanent magnet 726 attached to a lower surface of button 710. The permanent magnet 726 may be rigidly attached to button 710, such that permanent magnet 726 moves or displaces in concert with button 710.
Button 710 rotates relative to body 730 about a pair of pivots 727 (or, in some embodiments, a single pivot). The pair of pivots 727 are attached to body 730 and positioned on each of first and second projections 733, 737, both of which are part of upper body 732. Each of the two pivots 727 are positioned between a respective projection 733, 737 and a lower surface of button 710. Thus, the pair of pivots 727 are below button 710 (or other input structure) and its input surface 712. More specifically, one pivot 727 is positioned between the first projection 733 and a first lower end of the button, and another pivot 727 is positioned between the second projection 737 and a second lower end of the button 710. One pivot 727 is disposed on the first projection 733 and another pivot 727 is disposed on the second projection 737. The pivot(s) 727 may rotate with respect to body 730 or may be stationary while permitting button 710 to rotate relative to the body 730.
Input surface 712 of the button/input structure 710 may be touched, pressed, swiped in one or more directions, or otherwise interacted with by a user. In some embodiments, input surface 710 may translate, deflect, bend, or otherwise move a relatively small distance in response to user input and/or in response to a movement of permanent magnet 726. In other embodiments, input surface 712 does not translate, deflect, bend, or otherwise move in response to a user input. Input may be detected through various intensity sensors (e.g., force sensors, touch sensors, or combination of the two). Such sensors are not shown for simplicity's sake.
Button 710 may include one or more steps or shelves. The one or more shelves may aid in fitting the button to a host electronic device, such as fitting the button 710 within an opening along an exterior of a host electronic device. The one or more shelves may receive a gasket, the gasket engaging one or more shelves.
With attention to
First shelf 718 of button 710 is typically wider and/or longer than collar 716. In some embodiments, first shelf 718 is of similar or identical width to first upper portion 713. First shelf 718 may have the same shape as either or both of upper portion 713 and collar 716, or may have a different shape.
Second shelf 720 of button 710 is generally wider and/or longer than first shelf 718. The second shelf 720 may have a similar shape as one or more of first upper portion 713, collar 716, and first shelf 718 of button 710, or may be differently-shaped. Second shelf 720 is positioned below first shelf 718. Second shelf 720 is positioned between first shelf 718 and connector 722.
Generally, the first shelf, collar, and second shelf cooperate to define a grove, annulus, or the like extending around a perimeter of button 710. A gasket or other seal may be seated in this groove.
Connector 722 is positioned below second shelf 720 and connects button 710 to permanent magnet 726. Connector 722 may be positioned at a central portion of the upper surface of permanent magnet 726. Connector 722 may be connected to permanent magnet 726 along substantially all of the length of an upper surface of permanent magnet 726. The permanent magnet may be rigidly connected to button 710 by way of connector 722. In some embodiments, permanent magnet 726 extends into a space within body 730. That is, the body may be hollow or may have multiple projections defining a space receiving at least part of permanent magnet 730.
Body 730 includes upper body 732 and lower body 736. Each of first projection 733 and second projection 737 are part of upper body 732; the first and second projections define a volume or space therebetween in which part of permanent magnet 726 rests. Upper body 732 and lower body 736 are separated by a region of reduced width configured to receive electromagnet 770. The body may be attached to an enclosure of the electronic device, or a structure within the enclosure.
Electromagnet 770 is configured to attach to body 730 and positioned relative to permanent magnet 726 such that a magnetic field generated by electromagnet 770 is received by permanent magnet 726 sufficient to displace or move permanent magnet 726. Electromagnet 770 encircles body 730 (specifically, the first and second projections 733, 737 and is positioned between upper body 732 and lower body 736. More specifically, electromagnet 770 is positioned to fit around a region of reduced width formed between upper body 732 and lower body 736. Electromagnet 770 has sidewall 776. Generally, electromagnet 770 is located below button 710 (or other input structure) and its input surface 712.
The positioning of permanent magnet 726 relative to electromagnet 770 modifies the operation (e.g., actuation) of button 710. More specifically, the magnetic interaction between electromagnet 770 and permanent magnet 726 is influenced by the relative positioning of permanent magnet 726 with respect to the electromagnet. In the embodiment of
In some embodiments, permanent magnet 726 may be replaced by a second electromagnet, or may be supplemented by a second electromagnet. Using an electromagnet in place of, or in addition to, permanent magnet 726 may facilitate fine control of the magnetic force exerted on button 710 (or other input structure), thereby likewise providing fine control of the force of the haptic output. It should be appreciated that haptic output via button 710 or other input structure may be increased by increasing the field strength of the second electromagnet or decreased by decreasing its field strength. Likewise, field strength of first electromagnet 770 may be varied to vary haptic output force even when permanent magnet 726 is used instead of a second electromagnet.
Further, it should be noted that such variations in field strength generally vary haptic output strength, but not travel; a distance traveled by the input structure (e.g., button 710) and associated input surface varies with the distance of the pivot point from the input surface, as discussed above. Increases in both haptic output strength and travel distance may increase saliency and/or perceptibility of a haptic output.
With attention to
Button 710 is attached to permanent magnet 726 by way of connector 722; in many embodiments, the ends of connector 722 define pivots 727. Button 710 is configured to pivot on body 730 by way of the pair of pivots 727. In other embodiments, the connector and pivot(s) may be separate elements. Body 730, permanent magnet 726, and electromagnet 770 may be disposed within a host electronic device.
Electromagnet 770, which may encircle at least a portion of permanent magnet 726, generates a magnetic field which interacts with permanent magnet 726, in turn pivoting button 710 between a neutral, unactuated first button position and an actuated, second button position.
When no electric current is flowing through the wire windings of electromagnet 770, no magnetic field is generated by electromagnet 770 and permanent magnet 726 is in a neutral position that is approximately in the middle of the electromagnet's interior volume 777, as shown in
The permanent magnet 726, when influenced by the magnetic field, moves from its neutral position (as shown in
The button/permanent magnet centerline 719 and major axis 739 intersect at pivot point 725. Pivot point 725 is positioned at the bottom of pivot 727; pivot 727 is not visible in
The direction of rotation about pivot point 725 may change with the direction of current passing through electromagnet 770; thus, button 710 and permanent magnet 726 may both rotate in two directions (e.g., clockwise or counterclockwise about the pivot point 725). As previously mentioned, permanent magnet 726 and button 710 generally move in opposite directions while rotating about the pivot point 725 and any associated pivot(s) 727.
A user receives haptic feedback from button 710 actuation in that the input surface 712 of button 710 pivots with button 710. A user touching input surface 712 may sense the pivoting or actuation of button 710. Furthermore, the user may be able to see the pivoting of button 710 from the neutral, unactuated first position to the actuated, second position.
Button 710 (or other input structure) may include intensity sensors (e.g., force sensor 717) below input surface 712 and within upper portion 713; the force sensor is shown in
The output signal generated by force sensor 717 allows the processor (e.g., via the tactile output controller 161 in
The processor also may control any of several inputs to electromagnet 770 to vary the magnetic field generated by electromagnet 770. For example, the processor may control the current running through the wire of actuator 770. Generally, an increased current will result in an increase in magnetic field strength, thereby moving permanent magnet 726 more quickly and increasing the haptic output's strength.
The processor may control additional aspects of electromagnet 770. For example, upon receipt of force sensor's 717 signal, the processor may power up the electromagnet and/or alter the state of the electromagnet so as to ready electromagnet 770 to generate a magnetic field to actuate button 710. Such a scenario may occur if the electromagnet is consistently powered on but at a level that generates a magnetic field of a size and/or strength that does not pivot permanent magnet 726. Upon receipt of the output signal from force sensor 717, the processor may control electromagnet 770 to move from stand-by status to a full power-on mode, thereby actuating button 710 by moving permanent magnet 726. In some embodiments, input device 701 may be configured to actuate (e.g., the button moves) only upon receiving an input exceeding a threshold force level, below which no actuation is triggered.
In some embodiments, motion of permanent magnet 726 within electromagnet 770 may be sensed by measuring the back electromotive force (EMF) of the electromagnet.
Generally, the EMF induced in the electromagnet will vary with a magnitude of permanent magnet's 726 travel. Further, as a user presses harder on input surface 712 or otherwise more rigidly constrains the input surface with his or her finger, the permanent magnet's travel reduces. Thus, if a user has a “stiff’ input, input structure 710 (e.g., button) travel is constrained and this may be sensed by measuring the back EMF of electromagnet 770 via a sensor. A user may provide a stiff input if the user is exerting high force on input surface 712, is wearing gloves, has dry skin, a calloused finger, and so on. Generally, conditions that yield a stiff input also reduce sensitivity to haptic output. Accordingly, when the back EMF of the electromagnet 770 is exceeds a threshold, a processing unit of input device 701 may direct additional power to the electromagnet 770 to increase the force and perceptibility of haptic output.
Button 710 may be positioned in an opening along an exterior surface of an electronic device, such that the button presents an input surface to a user. Button 710 may be conformal with the exterior surface, or may project from the exterior surface of a host electronic device. In one embodiment, button 710 is oblong and fits along an exterior edge of an electronic device, such as a mobile phone.
Button 710 may actuate (e.g., move) in any of several ways. In the embodiment of
In one embodiment, although button 710 may actuate, the actuation is not required to register a button input to an electronic device, such as to register a button input by a processor of an electronic device. Stated another way, the physical movement or actuation of button 710 is not required to register a button on or off input. Instead, button actuation is effected to provide a type of haptic feedback to the user.
Button 710 may have a variety of shapes, including defining a curved or convex input surface 712, and/or may be rectangular, square, and so on. As another example, input surface 712 may be substantially flat. Input surface 712 and/or other parts of button 710 may include texture such as bumps, ridges, or the like. Button 710 may have readjusted, beveled, or flat edges. Generally, the smaller the curvature of input surface 712, the greater the shear (e.g., transverse displacement) of the user's skin contacting the input surface and thus the greater the perceptibility of the haptic output. Accordingly, travel of planar input surfaces 712 may be more easily perceived by a user than the same travel of a curved input surface. The curvature of the input surface 712 may be selected to impart a particular haptic output or particular perceptibility of a haptic output.
Generally, if the curvature of input surface 712 equals the curvature of an arc segment along which input surface 712 travels during rotation of the input structure 710 about the pivot, the skin of a user's finger in contact with the input surface 712 experiences purely tangential motion from the input surface. The “arc segment” is the portion of a circle through which a point on the input surface moves while the input structure rotates. Put another way, if every point of input surface 712 lies on a single arc circumscribed by the entirety of input surface 712 while haptic output is provided, then the curvature of the input surface equals the curvature of an arc segment. Put still another way, if the distance from pivot 727 to every point of the input surface within the rotational plane is equal, then the curvature of the input surface 712 matches the curvature of the arc segment during rotation. Purely tangential motion of the input surface 712 against a user's skin yields a high degree of skin shear and a unique feeling of haptic output. Generally, such haptic output is indistinguishable or near-indistinguishable from a “click” or depress of a typical button that moves in the direction of an input force.
By changing the curvature of input surface 712, the feel of the haptic output may be varied. The more the curvature of the input surface varies from the arc segment along which the input surface 712 travels during rotation, the more the haptic output feels like a “rocking” (e.g., for simulating a “toggle” operations) motion to a user as opposed to a “clicking” or depressing/collapsing motion. The curvature of the input surface 712 may be tuned to provide particular haptic outputs, as desired or necessary.
Each of the above identified elements in
Attention is now directed towards embodiments of user interfaces (“UI”) that are, optionally, implemented on portable multifunction device 100.
It should be noted that the icon labels illustrated in
As shown in
Although many of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures, etc.), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse based input or a stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
As used herein, the term “focus selector” is an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector,” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface is the force or pressure (force per unit area) of a contact (e.g., a finger contact or a stylus contact) on the touch-sensitive surface, or to a substitute (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 distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath 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., a weighted average or a sum) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be readily accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch-screen display can be set to any of a large range of predefined thresholds values without changing the trackpad or touch-screen display hardware. Additionally, in some implementations a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
As used in the specification and claims, the term “characteristic intensity” of a contact is a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, a value produced by low-pass filtering the intensity of the contact over a predefined period or starting at a predefined time, or the like. In some embodiments, the duration of the contact is used in determining 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 operation has been performed by a user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second intensity threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more intensity thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective option or forgo performing the respective operation) rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact transitioning from a start location and reaching an end location (e.g., a drag gesture), at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location may be based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm may be applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The user interface figures described herein optionally include various intensity diagrams that show the current intensity of the contact on the touch-sensitive surface relative to one or more intensity thresholds (e.g., a contact detection intensity threshold IT0, a hint intensity threshold ITH (e.g., that is higher than IT0), a light press intensity threshold ITL (e.g., that is at least initially higher than ITH), a deep press intensity threshold ITD (e.g., that is at least initially higher than ITL), and/or one or more other intensity thresholds (e.g., an intensity threshold ITH that is lower than ITL)). This intensity diagram is typically not part of the displayed user interface, but is provided to aid in the interpretation of the figures. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold IT0 below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
In some embodiments, the response of the device to inputs detected by the device depends on criteria based on the contact intensity during the input. For example, for some “light press” inputs, the intensity of a contact exceeding a first intensity threshold during the input triggers a first response. In some embodiments, the response of the device to inputs detected by the device depends on criteria that include both the contact intensity during the input and time-based criteria. For example, for some “deep press” inputs, the intensity of a contact exceeding a second intensity threshold during the input, greater than the first intensity threshold for a light press, 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 in duration (e.g., 40, 100, 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 to avoid accidental recognition of deep press inputs. As another example, for some “deep press” inputs, there is a reduced-sensitivity time period that occurs after the time at which the first intensity threshold is met. During the reduced-sensitivity time period, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep press inputs. For other deep press inputs, the response to detection of a deep press input does not depend on time-based criteria.
In some embodiments, one or more of the input intensity thresholds and/or the corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, application running, rate at which the intensity is applied, number of concurrent inputs, user history, environmental factors (e.g., ambient noise), focus selector position, and the like. Example factors are described in U.S. patent application Ser. Nos. 14/399,606 and 14/624,296, which are incorporated by reference herein in their entireties.
For example,
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold ITL to an intensity between the light press intensity threshold ITL and the deep press intensity threshold ITD is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold ITD to an intensity above the deep press intensity threshold ITD is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold IT0 to an intensity between the contact-detection intensity threshold IT0 and the light press intensity threshold ITL is sometimes referred to as detecting the contact on the touch-surface. A decrease of 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 is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, IT0 is zero. In some embodiments, IT0 is greater than zero. In some illustrations, a shaded circle or oval is used to represent intensity of a contact on the touch-sensitive surface. In some illustrations, a circle or oval without shading is used represent a respective contact on the touch-sensitive surface without specifying the intensity of the respective contact.
In some embodiments, described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., the respective operation is performed on a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., the respective operation is performed on an “up stroke” of the respective press input).
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., the respective operation is performed on an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the description of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. As described above, in some embodiments, the triggering of these responses also depends on time-based criteria being met (e.g., a delay time has elapsed between a first intensity threshold being met and a second intensity threshold being met).
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on an electronic device, such as portable multifunction device 100 or device 300, with a display, a touch-sensitive surface, one or more tactile output generators for generating tactile outputs (e.g., one or more localized tactile output generators and/or one or more whole device tactile output generators), one or more sensors to detect intensities of contacts with the touch-sensitive surface and one or more input regions of the device (e.g., one or more off-display side buttons).
FIGS. 5A1-5H15 illustrate exemplary user interfaces for providing tactile outputs and visual feedback in response to multiple types of inputs on an intensity-sensitive input region (e.g., an off-display input regions 455, 456, and 457) of the device in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in
FIGS. 5A1-5A8 illustrate exemplary user interfaces for providing haptic and visual feedback for button interactions corresponding to querying and/or modifying a current state of a device attribute in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in
FIG. 5A1 illustrates device 100 in a display-off state. For example, after a period of inactivity, the device automatically turns off the display 112 to conserve power. In some embodiments, the device is locked when the display is turned off and requires authentication (e.g., via facial recognition or biometric inputs) to be unlocked. No user interface is displayed on the screen when the device is in the display-off state. In some embodiments, the device displays a wake screen user interface (e.g., wake screen user interface 501) as an initial interface that is displayed when the device transitions from the display-off state to a display-on state (e.g., in response to occurrence of an event or detection of a user input).
FIG. 5A2 illustrates that, when a new notification (e.g., notification 502 for a newly received message) is generated at device 100, the device transitions from the display-off state to the display-on state, and displays the new notification 502 on wake screen user interface 501. The wake screen user interface displays an existing unread notification 504 that was generated at an earlier time, but has not been read or interacted with by the user. The wake screen user interface 501 displays the current time. The wake screen user interface 501 is dismissed when an upward wipe gesture (e.g., a home-display gesture) is detected at the bottom edge of the touch-screen 112, and a home screen user interface or a user interface of a last displayed application replaces the wake screen user interface 501 on the screen. In some embodiments, the device navigates to a mini application user interface in response to a horizontal swipe gesture detected on the touch-screen, without displaying the home screen or the last displayed application user interface.
FIG. 5A3 illustrates that, after a period of inactivity by the user since the receipt of new notification 502, the device has returned to the display-off state, without changing the read/unread statuses of notifications 502 and 504. In FIG. 5A3, a touch input by contact 506 is detected on input region 456. In accordance with the detection of the touch input by contact 506 (e.g., intensity of contact 506 exceeds contact detection intensity threshold IT0), without requiring the intensity of contact 506 to exceed a light press intensity threshold ITL, the device generates localized tactile outputs 508 at input region 456 to indicate a current value or state (e.g., “Present, as opposed to “Not Present”) of a predefined device attribute (e.g., the presence/absence of unread notifications at the device). In some embodiments, tactile outputs 508 further indicate the number of unread notifications (e.g., two) present at the device based on one or more characteristics of the tactile outputs (e.g., the tactile outputs 508 are a tactile output sequence with a corresponding number of identical, discrete tactile outputs at input region 456). In some embodiments, the device generates tactile outputs 508 only after contact 506 has been maintained on input region 456 for at least a threshold amount of time T, to reduce accidental triggering of the device's response regarding the presence/absence of unread notifications. In some embodiments, the device does not transition from the display-off state to the display-on state when the intensity of the input by contact 506 remains below the hint intensity threshold ITH and the light press intensity threshold ITL. In some embodiments, the device does not transition from the display-off state to the display-on state when the device detects that the device is inside of a pocket (e.g., based on inputs from an ambient light sensor). Forgoing turning on the display when responding to the user's query of device attribute information conserves energy and better maintains user privacy (e.g., the device provides the information that the user needs when the device remains concealed inside the user's pocket).
FIG. 5A4 illustrates that, in some embodiments, wake screen user interface 501 gradually fades in (e.g., in a shaded state) in when an intensity of the input by contact 506 on input region 456 increases above the hint intensity threshold ITH. The visibility of wake screen user interface along with the unread notifications 502 and 504 dynamically changes in accordance with a current intensity of contact 506 on input region 456. In some embodiments, tactile outputs 508 is provided in conjunction with the visual feedback (e.g., visual display of the unread notifications 502 and 504 and/or a count thereof) displayed on the screen. In some embodiments, no tactile output indicating the presence/count of unread notifications is provided until the intensity of contact 506 exceeds the hint intensity threshold ITH. In some embodiments, the device forgoes requiring that the contact be maintained on input region 456 for at least a threshold amount of time T and provides the device attribute regarding unread notifications to the user if the intensity of the contact exceeds the hint intensity threshold ITH before the time threshold T is met.
In FIGS. 5A3 and 5A4, the device generates visual feedback and haptic feedback regarding the current value or state of a device attribute, namely, the presence of unread notifications, of the device, without changing the current value or state of the device attribute, because the intensity of the input by contact 506 has not exceeded a first intensity threshold (e.g., the light press intensity threshold ITL). In some embodiments, when termination of the input by contact 506 (e.g., lift-off of contact 506 from input region 456) is detected without the intensity of contact 506 having exceeded the first intensity threshold, the device transitions back to the display-off state (e.g., following the state shown in FIG. 5A4) and notifications 502 and 504 maintains their unread statuses.
FIG. 5A5 illustrates that, before termination of the input by contact 506 is detected, intensity of contact 506 on input region 456 increases above the first intensity threshold (e.g., the light press intensity threshold ITL). In response to detecting that the intensity of contact 506 has increased above the first intensity threshold, device 100 completes its transition to the display-on state, and displays notifications 502 and 504 on wake screen user interface 501. The device also changes the read/unread statuses of notifications 502 and 504 from “unread” to “read.” In some embodiments, the device generates localized tactile output 510 (e.g., with a tactile output profile that is different from the tactile output profile for tactile outputs 508) to indicate the changes made to the read/unread statuses of notifications 502 and 504, and the change in the current state of the device parameter, namely, the presence/absence of unread notifications, from “Present” to “Not Present”.
In some embodiments, if the unread notifications displayed on wake screen user interface 501 has corresponding long versions, when intensity of input by contact 506 increases above a second intensity threshold (e.g., a deep press intensity threshold ITD), the device replaces notifications 502 and 504 with corresponding long versions 502′ and 504′ of the notifications, as shown in FIG. 5A6. The long versions of the notifications include additional content (e.g., an attached image, or a voicemail recording) or functionality (e.g., a playback button) that were not included in notifications 502 and 504. In some embodiments, the device optionally generates another localized tactile output 512 (e.g., with a tactile output profile that is distinct from the respective tactile output profiles of tactile outputs 508 and 510) at input region 456 in response to the intensity of the input by contact 512 exceeding the second intensity threshold.
FIG. 5A7 illustrates that, after a period of inactivity by the user, the device returns to the display-off state. The notifications 502 and 504 are cleared from the wake screen user interface (e.g., saved to notification history or cleared) because they are no longer “unread” notifications as a result of the interactions shown in FIGS. 5A5 and 5A6. FIG. 5A8 illustrates, that when another input by contact 514 is detected on input region 456, and the device-query criteria for providing the current value or state of the predefined device attribute (e.g., the presence/absence of unread notifications) of the device are met by the input by contact 514 (e.g., intensity of contact 514 exceeded the hint intensity threshold ITH), the device responds by displaying the wake screen user interface without any unread notifications (e.g., the wake screen user interface 501 fades in by an amount in accordance with the intensity of contact 514), and by forgoing generation of any localized tactile outputs at input region 456, to indicate that there is currently no unread notifications present at the device. In some embodiments, the device provides a predefined failure tactile output (e.g., a weak tactile output with a distinct tactile output profile (e.g., a failure buzz)) to indicate that the current value of the predefined device attribute is “Not Present.” When the current value of the predefined device attribute is “Not Present,” the device does not change the value of the device attribute to “Present” in response to an increase in intensity of the input by contact 514 above the first intensity threshold (e.g., the light press intensity threshold). In some embodiments, for a different device attribute with a toggle state (e.g., the ringer ON/OFF state) or a continuously modifiable state (e.g., the volume level), the device toggles the current value or state of the device attribute (e.g., from ON to OFF, or from OFF to ON) or continues to change the current value of the device attribute (e.g., to increment the volume level by a respective amount) in response to an increase in intensity of the input by contact 514 above the first intensity threshold (e.g., the light press intensity threshold).
FIGS. 5B1-5B11 illustrate exemplary user interfaces for providing haptic and visual feedback for button interactions corresponding to modifying a device parameter in different manners in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in
In FIG. 5B1, user interface 516 of a browser application is displayed on touch-screen 112. In FIG. 5B2, a touch input by contact 518 is detected on input region 456 (e.g., in this example, input regions 456 and 457 primarily serve as the volume up and volume down buttons of the device, respectively). In response to detecting the input by contact 518 on input region 456 (e.g., intensity of contact 518 exceeds the detection intensity threshold IT0), and without requiring the intensity of the input by contact 518 to exceed a first intensity threshold (e.g., the light press intensity threshold ITL), the device displays volume control 520 (e.g., a slider control) with indicator 522 (e.g., a slider indicator) indicating a current value of the device's volume setting. In some embodiments, the background user interface 516 is darkened and blurred underneath volume control 520, and the amount of darkening and blurring is changed (e.g., increased or decreased) dynamically in accordance with the current intensity of contact 518. In some embodiments, as the intensity of contact 518 remains below the first intensity threshold (e.g., the light press intensity threshold ITL), the current value of the volume setting does not change. In other words, the light touch on input region 456 causes the device to provide the current value or state of a predefined device attribute (e.g., the device volume level), without changing the current value or state of the predefined device attribute. In some embodiments, the device displays visual feedback (e.g., an animated arrow pointing upward) that indicates the direction in which the device attribute will be changed if a press input is detected on the input region 456 that is currently touched by the user. In some embodiments, the device determines which device parameter (e.g., presence/absence of unread notification vs. device volume setting) is being queried by a particular light touch input on input region 456 in accordance with context information (e.g., if the device is in the display-off state, the device responds with notification status, and if the device is in the display-on state, the device responds with the current volume), without requiring presence of a focus selector on the display.
FIG. 5B3 illustrates that, when the intensity of input by contact 518 has increased above the first intensity threshold (e.g., the light press intensity threshold ITL), the device increases the current volume of the device (e.g., because the input region 456 corresponds to the volume up function of the device) by a respective amount. In some embodiments, each time that the intensity of input by contact 518 increases above the first intensity threshold (e.g., a dynamic intensity threshold that is determined in accordance with the methods shown in
FIG. 5B4 illustrates that, when intensity of contact 518 increases above the first intensity threshold for a number of times, or the intensity of contact 518 has been maintained above the first intensity threshold for an extended period of time, the device has increased the volume level of the device to a maximum value of the device volume. In response to the volume level of the device reaching the maximum value, the device generates localized tactile output 526 at input region 456 (e.g., the tactile output is synchronized with the increase of intensity above the first intensity threshold or the satisfaction of the time threshold for maintaining the intensity above the first intensity threshold) to indicate that a maximum value of the volume setting has been reached. In some embodiments, in addition to or in lieu of the localized tactile output 526 generated at input region 456, the device provides a whole device tactile output 528 to indicate that the maximum value of the volume level has been reached.
FIGS. 5B5 and 5B6 illustrate that, in some embodiments, if an additional press input by the same contact or a different contact (e.g., contact 530) is detected on input region 456, and the intensity of the contact (e.g., contact 530) exceeds the first intensity threshold, the device displays (e.g., redisplays) volume control 520 showing the current volume level at the maximum value, but forgoes generating at least one (e.g., one or both) of localized tactile output 526 and whole tactile output 528, to indicate that no further change has been made to the volume level in response to the light press input on input region 456. In some embodiments, the device generates a failure tactile output (e.g., a whole device failure buzz 532 as opposed to localized tactile output at input region 456) to indicate that no further change can be made to the volume level in response to the light press input on input region 456, as shown in FIG. 5B6.
FIG. 5B7 illustrates that, another input by contact 534 is detected on input region 457 (e.g., the input region currently corresponds to a volume down function of the device) after termination of the input by contact 518 or the input by contact 530. In response to the input by contact 534 on input region 457, the device displays volume control 520 without modifying the volume level when the intensity of the input by contact 534 has not exceeded the first intensity threshold, and decreases the volume level by a respective amount each time the intensity of the input by contact 534 increases above the first intensity threshold. In some embodiments, the device displays visual feedback (e.g., an animated arrow pointing downward) that indicates the direction in which the device attribute will be changed if a press input is detected on the input region 457 that is currently touched by the user. In FIG. 5B7, the device decreased the current device volume in response to detecting the increase of the intensity of contact 534 above the first intensity threshold. The device further generates a localized tactile output 536 at input region 457 to indicate that the criteria for decreasing the volume level has been met by the input, and that the volume level has been decreased accordingly. In some embodiments, the tactile output profile for localized tactile output 536 is different from the tactile output profile for localized tactile output 524 in FIG. 5B3, to reflect the difference in the direction of the changes in the volume level.
FIGS. 5B8-5B9 illustrates that, after a decrease in intensity of the input by contact 534 on input region 457 (as shown in FIG. 5B8), the intensity of the input by contact 534 increases above a second intensity threshold (e.g., a deep press intensity threshold ITD). In response to detecting that the intensity of the input by contact 534 has exceeded the second intensity threshold, the device resets the volume level of the device to a preset value corresponding to input region 457 (e.g., a minimum value corresponding to muting the volume of the device), as shown in FIG. 5B9. In conjunction with resetting the volume level to mute, the device also generates a localized tactile output (e.g., tactile output 538 with a tactile output profile that is different from the tactile output profiles for tactile outputs 524, 536, and 526) at input region 457 to indicate that a minimum value of the volume level has been reached. In some embodiments, the device also generates a whole device tactile output 540 in conjunction with localized tactile output 538 to indicate that the volume has been muted in response to the deep press input by contact 534. FIG. 5B9 illustrates the scenario where the input is detected on the input region 457 that is used as volume down button. If the contact 534 had been detected on input region 456 (e.g., the input region used as the volume up button) instead, the device would reset the volume level of the device to a preset value corresponding to input region 456 (e.g., a maximum volume level), in response to detecting the intensity of the input exceeding the second intensity threshold, and the device would generate corresponding localized tactile output at input region 456 and whole device tactile output to indicate the abrupt resetting of the volume level. In some embodiments, in addition to or in lieu of a requirement that the intensity of the contact increases above the deep press intensity threshold in order to reset the volume level to a preset maximum or minimum value, the device requires that the contact intensity be maintained above the light press intensity threshold for at least a threshold amount of time T in order to reset the volume level to a preset maximum or minimum value.
FIGS. 5B10 and 5B11 illustrate that the same set of input regions 456 and 457 correspond to multiple device parameters (e.g., including at least the volume level setting and the screen brightness setting). The device toggles or switches the currently selected device parameter of the input regions to a next device parameter in the multiple device parameters in response to simultaneous press inputs detected on both input regions 546 and 457. In FIG. 5B10, after lift-off of contact 534 from input region 457 and upon initial touch down of two contacts 542 and 544 on input regions 456 and 457 (e.g., intensities of both contacts 542 and 544 are below the first intensity threshold (e.g., the light press intensity threshold ITL)), respectively, the device redisplays volume control 520 on the display to indicate the currently selected device parameter for the input regions, and to indicate the current value of the device volume setting. In FIG. 5B11, upon detecting an increase in intensity of both contacts 542 and 544 above the first intensity threshold (e.g., the light press intensity threshold ITL), the device switches the currently selected device parameter corresponding to the input regions 456 and 457 to the display brightness setting. In response to the simultaneous light press inputs by contact 542 and 544 on input regions 456 and 457, the device replaces the display of volume control 520 with display of brightness control 550. Brightness control 550 is a slider control with an indicator indicating the current brightness setting of the display. In conjunction with replacing display of volume control 520 with brightness control 550, the device generates localized tactile output 546 and 548 (e.g., with the same tactile output profile as each other, and different tactile output profile from those of tactile outputs 524, 526, 536, 538) at input regions 456 and 457, respectively, to indicating that the device has switched to another parameter of the multiple device parameters as the currently controlled device parameter for the input regions 456 and 457. After termination of the inputs by contacts 542 and 544, the device responds to press inputs on input regions 456 and 457 to adjust the brightness setting of the device in a manner similar to that described with respect to the volume setting in FIGS. 5B1-5B10. In response to another simultaneous light press inputs on input regions 456 and 457, the device switches the currently controlled device parameter for the input regions back to the volume setting (e.g., if the input regions only correspond to two device parameters) or switches to the next device parameter of the multiple device parameters.
FIGS. 5C1-5C20 illustrate exemplary user interfaces for providing haptic and visual feedback for different types of button interactions corresponding to presenting and interacting with a retractable menu in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in
FIG. 5C1 illustrates device 100 displaying a user interface of a browser application. Device 100 includes input region 455 (e.g., a power button disposed on a peripheral side of the device adjacent to the edge of the display) that is coupled with a localized tactile output generator for generating localized tactile outputs at input region 455.
In FIG. 5C2, device 100 detects contact 552 on input region 455. In response to detecting contact 552 (e.g., intensity of contact 552 exceeds contact detection intensity threshold IT0), the device displays precursor object 554 corresponding to a retractable menu next to input region 455. In some embodiments, precursor object 554 is animated (e.g., with movement or changing visual characteristic) to prompt the user to press harder on input region 455 (e.g., exerting more pressure in the direction toward the display). If the user simply rests his/her finger on input region 455, the device maintains display of precursor object 554, without displaying the menu. The device ceases to display precursor object 554 if lift-off of contact 552 is detected before the menu is revealed. In some embodiments, the device darkens and blurs the currently displayed user interface underneath precursor object 554 to focus the user's attention on precursor object 554.
FIGS. 5C3-5C5 illustrate that, as intensity of input by contact 552 increases and then decreases, the device reveals a menu with multiple selectable options by an amount that changes dynamically with the intensity of contact 552. As shown in FIG. 5C3, when intensity of input by contact 552 increases, a portion of menu 556 is revealed (e.g., sliding in onto the display from the side of the display adjacent to input region 455) showing a first selectable option 558 (e.g., an option to turn on/off the Do Not Disturb mode of the device). As the intensity of input by contact 552 continues to increase, additional portions of menu 556 is revealed (e.g., menu sliding in further in the direction of the force/pressure exerted by the user's finger on input region 455) showing a second selectable option 560 (e.g., an option to turn off the device). In FIG. 5C5, as the intensity of input by contact 552 decreases again, menu 556 retracts toward the edge of the display adjacent to input region 455. If lift-off of contact 552 is detected, menu 556 retracts completely and ceases to be displayed. In some embodiments, before menu 556 is fully expanded to show all available options on the menu, if a tap input (e.g., by another contact on the touch-screen) is detected on one of the options in the menu that are currently visible on the display, the selected option will be invoked, and the device performs an operation corresponding to the selected option (e.g., turn on “Do Not Disturb” mode, or turn off the device).
FIGS. 5C6-5C7 illustrate that, if before lift-off of contact 552, the device detects that the intensity of the input by contact 552 increases above a first intensity threshold (e.g., a light press intensity threshold ITL), the device fully displays menu 556 and maintains display of menu 556 after lift-off of contact 552. The fully displayed menu 556 includes a third selectable option 562 (e.g., an option to use a payment function of the device). In some embodiments, the fully displayed menu 556 also includes indicator 5641 to indicate availability of additional functions through menu 556 with an enhanced press input (e.g., a deep press input or a long press input on input region 455). Examples of these additional functions are discussed with respect to FIGS. 5G1-5G5 and 5H1-5H5. As shown in FIG. 5C6, in conjunction with the detection of the light press input by contact 552 and full display of menu 556, the device generates localized tactile output 566 at input region 455. In some embodiments, localized tactile output 566 is synchronized with intensity of contact 552 reaching the first intensity threshold. In some embodiments, the menu overshoots and snaps back to its fully opened state after the first intensity threshold is reached, and the device synchronizes the tactile output 566 with the final settlement of the menu in its fully open state. FIG. 5C7 illustrates the fully opened state of menu 556 after lift-off of contact 552 has been detected. Each option in the fully displayed menu 556 is selectively activatable by a tap input at a location on the touch-screen corresponding to the option.
FIGS. 5C8-5C9 illustrate that, a tap input by contact 5661 on the first selectable option 558 causes the device to activate the “Do Not Disturb” mode of the device. In FIG. 5C9, the device generates a whole device tactile output (e.g., tactile output 5601) and displays a notification (e.g., notification 5621) to indicate to the user that “Do Not Disturb” mode has been turned on in response to the tap input by contact 5663. In this example, option 558 is a toggle button, and the device turns off the “Do Not Disturb” mode if option 558 is tapped again. The notification 5621 ceases to be displayed after a preset time period.
FIGS. 5C10-5C12 illustrate scrolling a selection indicator (e.g., selection indicator 568) through the multiple selectable options (e.g., options 558, 560, and 562) to change a currently selected option in menu 556. In FIG. 5C10, the device detects contact 564 on input region 455, and downward movement of contact 564 along the longitudinal direction of the elongated input region 455. In response to detecting the start of the downward swipe input by contact 564 on input region 455 (e.g., without requiring an intensity of the contact reaching a hint intensity threshold or a light press intensity threshold), the device displays selection indicator 568 at a location of the currently selected option (e.g., option 558) in menu 556. The selection indicator may take on different forms (e.g., as a spotlight, a highlight, a cursor, a special visual effect applied to a selected option, etc.) in different embodiments. In FIG. 5C11, as the downward swipe input by contact 564 on input region 455 continues, the device changes the currently selected option to the second option 560 in menu 556, and moves selection indicator 568 to the location of the second option 560. In FIG. 5C12, as the downward swipe input by contact 564 on input region 455 continues further, the device changes the currently selected option to the third option 562 in menu 556, and moves selection indicator 568 to the location of the third option 562. In FIGS. 5C10-5C12, the swipe input is provided by a continuously maintained contact 564. The same effect shown in FIGS. 5C10-5C12 can also be achieved using multiple consecutive short downward swipes on input region 455. As shown in FIGS. 5C10-5C12, the device generates localized tactile output 5663 on input region 455 during the swipe input by contact 564. In some embodiments, the localized tactile output is focused on the current location of the contact 564 along input region 455. In some embodiments, the localized tactile output is a continuous sequence of identical discrete tactile outputs with fixed durations, simulating a haptic feedback of a rough surface or the weight of a mechanical scroll wheel. In some embodiments, the switching from one selectable option to the next selectable option is triggered by the movement of contact 564 meeting preset movement criteria (e.g., a distance threshold), and the device generates a respective discrete tactile output in conjunction with satisfaction of the preset movement criteria and the switching of the currently selected option, to simulate a detent produced by a mechanical scroll wheel or dial. Although a downward swipe is used in the example shown in FIGS. 5C10-5C12, the device switches the currently selected option in the reverse direction in menu 556, in response to an upward swipe input on input region 455 and provides corresponding localized tactile outputs at input region 455.
In FIG. 5C13, while option 562 is the currently selected option in menu 556, the device detects a light press input (e.g., an input with an intensity exceeding a hint intensity threshold or light press intensity threshold) by contact 570 on input region 455. In response to the light press input, the device activates the function corresponding to the currently selected option 562 (e.g., a payment function). In response to detecting the light press input, the device generates localized tactile output 572 to indicate satisfaction of the intensity requirement and the activation of the selected option. In some embodiments, the device also highlights the selected option when it is activated. The tactile output 572 indicating activation of the selected option has a distinct tactile output profile from the tactile output 566 indicating switching of the selected option and/or the scrolling of the selection indicator.
FIGS. 5C14-5C17 illustrate scrolling through a number of selectable options in a menu of payment options (e.g., menu 574 including multiple selectable payment cards 576, 582, 588, etc.) using swipe inputs (e.g., upward and downward swipes) along the longitudinal direction of the elongated input region 455. As shown in FIG. 5C14, after the payment option 562 is activated by a light press input by contact 570, the device replaces display of menu 556 with display of menu 574. A default payment card 576 (e.g., the last used payment card) is the currently selected option in menu 574 before any additional input is detected. An enlarged image of the currently selected payment option (e.g., an image 578 of the currently selected card 576) is optionally displayed with menu 574. In FIG. 5C15, the device detects a downward swipe input by contact 580 along the longitudinal direction of input region 455, and in response to detecting the downward swipe input, the device scrolls forward in the list of payment options in menu 574 and selects the next payment card 582 in menu 574. The currently selected payment card 582 is enlarged, and an enlarged image 584 of the currently selected card is displayed. In FIG. 5C16, the device detects a continuation of the downward swipe input by contact 580 along the longitudinal direction of input region 455, and in response to detecting the continuation of the downward swipe input, the device scrolls forward in the list of payment options in menu 574 and selects the next payment card 588 in menu 574. The currently selected payment card 588 is enlarged, and an enlarged image 590 of the currently selected card is displayed. In some embodiments, the list of payment options is implemented as a circular list, and the user can continue to scroll through the list and return to the first payment option 574 by one or more additional downward swipes on input region 455. In FIG. 5C17, the device detects an upward swipe input by contact 580 (e.g., reversal of the downward movement by contact 580 along the longitudinal direction of the elongated input region 455). In response to the upward swipe input by contact 580, the device scrolls backward in the list of payment options in menu 574 and selects the previous payment card 582 in menu 574 again.
As shown in FIGS. 5C14-5C17, the device generates localized tactile output on input region 455 during the swipe inputs by contact 580. In some embodiments, the localized tactile outputs are focused on the current location of contact 580 along input region 455 (e.g., with most energy of each tactile output focused directly under the finger contact, and the focuses of a sequence of tactile outputs moving downward or upward with the finger contact during the downward or upward swipe). In some embodiments, the localized tactile output is a continuous sequence of identical discrete tactile outputs with fixed durations, simulating a haptic feedback of a rough surface or the weight of a mechanical scroll wheel. In some embodiments, the localized tactile output 586 provided during a downward swipe input and the localized tactile output 592 provided during an upward swipe have different tactile output profiles to indicate a difference in the swipe directions. For example, the tactile outputs provided in response to a downward swipe each include a pattern with a large peak followed by a small peak; while the tactile outputs provided in response to an upward swipe each includes a pattern with a small peak followed by a large peak. In some embodiments, the switching from one selectable option to the next selectable option is triggered by the movement of contact 564 meeting preset movement criteria (e.g., a distance threshold), and the device generates a respective discrete tactile output in conjunction with satisfaction of the preset movement criteria and the switching of the currently selected option, to simulate a detent produced by a mechanical scroll wheel or dial. Similarly, the device switches the currently selected option in the reverse direction in menu 574, in response to an upward swipe input on input region 455 and provides corresponding discrete localized tactile outputs (e.g., with a different tactile output profile from that of the discrete localized tactile outputs 586) at input region 455.
In FIG. 5C18, while payment option 582 is the currently selected payment option, a tap input on input region 455 confirms selection of payment option 582, e.g., as indicated by further highlighting of the payment card image 584 and payment option 582 in menu 574. In some embodiments, a tap input is not necessary (e.g., in the case of actions less critical than payment), and the currently selected option is usable directly without further confirmation. In some embodiments, the device generates localized tactile output 596 to indicate confirmation of the selection of the payment option 582.
In FIG. 5C19, while the payment option 582 is selected and confirmed, the device is brought into proximity with (e.g., within a preset distance of) a point of sale device (e.g., POS device 598) (e.g., with the user holding the device and making contact with the peripheral sides of the device at input regions 455, 456, and 457). In response to detecting POS device 598 within the preset distance, device 100 initiates a countdown (e.g., a countdown corresponding to a preset cancellation period) before the payment operation is executed using the currently selected payment card 582. During the countdown, if the device moves away from POS device 598, the payment operation is canceled. If the device is maintained within the preset distance of the POS device, the payment operation is executed at the end of the countdown. In some embodiments, if the actual execution of the payment operation takes a finite amount of time and is cancellable within a period of time after the execution of the payment operation is stated, the device optionally starts the execution of the payment operation at a time when cancellation of the payment operation can still be performed successfully before the end of the countdown. As shown in FIG. 5C19, the device displays a countdown in the form of a completion meter 593 (e.g., indicating 70% completion, or 30% remaining of the total cancellation period). In some embodiments, the device displays prompt 591 requiring the user to maintain the device within the preset threshold distance of the POS device 598 if the user wishes to complete the payment operation, rather than cancelling it.
In FIG. 5C19, the device provides a sequence of coordinated tactile outputs 597 during the countdown period where cancellation of the operation is still permitted. In some embodiments, the coordinated tactile outputs 597 are generated in repeated sequences around the input regions 455, 456, and 457. In some embodiments, the amplitudes of the tactile outputs 597 at the different input regions around the peripheral sides of the device indicates a respective direction (e.g., a clockwise direction, with input region 457 having the lowest tactile output strength (e.g., with localized tactile output 597-1), input region 456 having the intermediate tactile output strength (e.g., with localized tactile output 597-2), and input region 455 having the highest tactile output strength (e.g., with localized tactile output 597-3)). In some embodiments, the timing of the tactile outputs at the different input regions are also offset by different amounts from a common reference time (e.g., with the tactile output (e.g., localized tactile output 597-1) at input region 457 having the earliest start time, followed by the tactile output (e.g., localized tactile output 597-2) at input region 456, followed by the tactile output (e.g., localized tactile output 597-3) at input region 455). In some embodiments, the timing of the tactile outputs at the different input regions around the peripheral sides of the device corresponds to a respective direction (e.g., a clockwise direction, a rightward direction, etc.) relevant to the current usage scenario (e.g., corresponding to the movement direction of the countdown indicator). In some embodiments, the manner of coordination (e.g., in terms of relative strengths, timing, and tactile output patterns) between the individual tactile outputs 597 provided at the different input regions 455, 456, and 457 is specified in the tactile output profiles of the tactile outputs, and the coordination is controlled by a central controller (e.g., haptic feedback controller 161 in
FIG. 5C20 illustrates that, when the countdown is concluded, the device executes or completes the payment operation, and cancellation of the operation is no longer available by moving the device away from the POS device 598. In some embodiments, the device provides a whole device tactile output 595 to indicate execution or completion of the payment operation. A dismissal affordance 587 is optionally provided on the display to dismiss menu 574.
FIGS. 5D1-5D24 illustrate exemplary user interfaces for providing haptic and visual feedback for different types of button interactions corresponding to presenting and interacting with a retractable menu (e.g., a clipboard) in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in
FIG. 5D1 illustrates a user interface (e.g., user interface 516) of an application (e.g., same as that shown in FIG. 5C1). Upon detection of contact 585 on input region 455, the device displays precursor object 554 that corresponds to retractable menu 556 (e.g., same as that shown in FIG. 5C2), as shown in FIG. 5D2. The device detects movement of contact 585 in a direction across the elongated input region 455 (e.g., from the display-side of the device to the backside of the device), as shown in FIGS. 5D2-5D3. In response to detecting the movement of contact 585 in the horizontal direction across the elongated input region 455, the device displays a different precursor object 583 corresponding to another retractable menu (e.g., a clipboard), as shown in FIG. 5D3. In addition, the device provides a localized tactile output 581 (e.g., with a tactile output profile that is different from the tactile output profiles of tactile outputs 508, 510, 512, 524, 526, 536, 538, 546, 548, 566, 5663, 572, 586, 592, 596, 597, and/or 589) in response to detecting the movement of contact 585 in the horizontal direction across input region 455, to indicate the toggling/switching of the menu currently controlled by the input region 455. In some embodiments, the device toggles the precursor object that is displayed (e.g., precursor object 554 for menu 556 and precursor object 583 for menu 577) in response to a horizontal swipe input on input region 455, regardless of the direction of the horizontal swipe input (e.g., from display-side to backside, or from backside to display-side) detected across the elongated input region 455. This is distinct from the behavior of a physical toggle button where only one swipe direction is effective for each toggle state of the button. In some embodiments, the input region 455 corresponds to a circular list of three or more menus, and the device scrolls through the respective precursor objects of the three or more menus in response to multiple horizontal swipes across the input region 455 and provides a corresponding localized tactile output (e.g., a tactile output with the same tactile output profile as tactile output 581) to indicate the switching of the precursor object and associated menu.
FIGS. 5D4-5D5 illustrate that, as intensity of the input by contact 579 increases, the device reveals increasing areas of menu 577 (e.g., a clipboard of objects such as content items (e.g., images, web links, documents, text, etc.) that now corresponds to input region 455. Menu 577 is displayed over user interface 516 without blurring and darkening of user interface 516 (e.g., in contrast to the case of menu 556 in FIG. 5C3). For a clipboard menu, the underlying user interface remains fully visible, such that the user can clearly see the objects and possible drop-off locations in the user interface during a copy and paste operation involving object(s) in the clipboard.
In FIGS. 5D6-5D8, while menu 577 remains partially revealed as a result of sustained contact 579 detected on input region 455 and before intensity of contact 579 increases above a first intensity threshold (e.g., the light press intensity threshold ITL), contact 575 is detected at a location on the touch screen that corresponds to image 573 in user interface 516 (e.g., a location outside of menu 577). In response to detecting contact 575 meeting preset selection criteria (e.g., long press criteria based on a time threshold being met by contact 575, or light press criteria based on an intensity threshold being met by contact 575), the device selects image 573. Then, in accordance with subsequent movement of contact 575 across the touch-screen to a location within menu 577, a representation (e.g., thumbnail 571) of the selected image 573 is dragged into menu 577, as shown in FIG. 5D7.
In FIG. 5D8, after thumbnail 571 is dragged into menu 577, the device detects lift-off of contact 575. In response to detecting lift-off of contact 575, the device inserts thumbnail 571 into menu 577, and a copy of image 573 becomes an object in the clipboard corresponding to menu 577. In some embodiments, the device generates whole device tactile output 569 to indicate insertion of image 573 into the clipboard.
In FIG. 5D9, after image 573 is inserted into the clipboard by the drag and drop input by contact 575, the device detects lift-off of contact 579 before intensity of contact 579 ever increased above the first intensity threshold (e.g., the light press intensity threshold ITL). In response to detecting the termination of input by contact 579, the device retracts menu 577, and user interface 516 is no longer obscured by menu 577. In the above process illustrated in FIGS. 5D3-5D9, an object is added into menu 577 without the menu being fully displayed. In some embodiments, an object can also be added to the menu by a drag and drop input when the menu has fully snapped opened due to a prior light press input.
In FIG. 5D10, another user interface 567 is displayed, e.g., as a result of launching another application (e.g., launched from the home screen or from an application-switcher user interface that had replaced display of user interface 516 in FIG. 5D9).
In FIGS. 5D11-5D12, an input by contact 565 is detected on input region 455. Upon detection of contact 565, precursor object 583 corresponding to menu 577 is displayed next to input region 455 (as shown in FIG. 5D11). When intensity of contact 565 increases, menu 577 gradually slides onto the display in the direction of the force/pressure exerted by the user's finger on input region 455. Thumbnail image 571 appears as the first item displayed in menu 577, as shown in FIG. 5D12.
FIGS. 5D13-5D14 illustrate that a drag input by contact 563 has selected and dragged a copy of thumbnail image 571 onto user interface 567. While contact 563 is maintained on touch screen 112 holding the copy of thumbnail image 571, lift-off of contact 565 is detected. In response to detecting lift-off of contact 565 from input region 455, the device ceases to display menu 577, while contact 563 continues to hold onto the copy of thumbnail image 571 over user interface 567.
In FIG. 5D15, when lift-off of contact 563 is detected, image corresponding to thumbnail 571 is dropped into a drop-off location selected in accordance with the lift-off position of contact 563 and available drop-off positions on user interface 567. In some embodiments, the device generates a whole device tactile output 559 to indicate settlement of the image into its final position on user interface 567.
FIGS. 5D16-5D17 illustrate that, a press input by contact 557 (e.g., with contact intensity exceeding the first intensity threshold (e.g., a light press intensity threshold ITL)) is detected on input region 455, and as a result, the device fully expands menu 577 over user interface 567. When intensity of contact 557 exceeded the first intensity threshold and the menu is snapped open, the device generates localized tactile output 553 to indicate that menu-display criteria are met and that the menu display will be maintained after lift-off of contact 557 from input region 455. When menu 577 is fully open, scroll indicator 555 is displayed in menu 577 to indicate that additional items are in menu 577 which can be revealed in response to a scroll input.
FIGS. 5D18-5D19 illustrates that, after menu 577 is fully opened, two consecutive downward swipe inputs by contact 551 and 547, respectively, are detected on input region 455. In response to the downward swipe inputs detected on input region 455, menu 577 is scrolled in a direction corresponding to the direction of the swipe input (e.g., scrolling to the right when the swipe is downward, and scrolling to the left when the swipe is upward), as indicated by the movement of scroll indicator 555. In addition to the visual feedback, the device also generates localized tactile outputs 549 and 545, respectively, on input region 455, in response to detecting swipe inputs by contacts 551 and 547. The localized tactile outputs 549 and 545 have the same tactile output profile which is designed to simulate rotation of a scroll wheel in response to the swipe inputs and/or the roughness of the input region under the finger contact. In some embodiments, a selection indicator moves forward and backward through the list of selectable options (e.g., content items) in menu 577 to indicate a currently selected option in response to downward and upward swipe inputs detected on input region 455, and a tap input on input region activates the currently selected option indicated by the selection indicator.
In FIGS. 5D20-5D22, while menu 577 remains open after having been scrolled, the device detects contact 543 at a location corresponding to an object 541 in menu 577. In accordance with selection and dragging of object 541 by contact 543 across an edge of touch-screen 112 (e.g., outside of a permissible on-screen drop-off location), the device removes object 541 from menu 577. Upon lift-off of contact 543, the device generates whole device tactile output 539 to indicate that deletion of object 541 from menu 577 has been completed.
In FIGS. 5D23-5D24, a tap input by contact 537 is detected outside of menu 577, and the device dismisses menu 577 from over user interface 567.
FIGS. 5E1-5E5 illustrate exemplary user interfaces for providing haptic and visual feedback for guiding device movement to perform a respective task when the device is in a media capture mode of operation in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in
In FIG. 5E1, user interface 535 is a camera user interface in a panorama capturing mode. The device detects presence of user's contact (e.g., contact 527 on the left side of the device, and contact 525 on the right side of the device) on all three input regions 455, 456, and 457 (e.g., the device is held in a user's hand, with the user making contact with input regions 455, 456, and 457). Although simultaneous contact with all input regions are shown in FIGS. 5E1-5E5, localized tactile outputs are generated on two or more of the input regions at various times during the process illustrated herein, even if contact is not maintained at all times with all input regions during the process. In addition, generation of tactile outputs at input regions 455, 456, and 457, in some cases, are in response to criteria being met by objects detected in the field of view of the camera, do not require touch inputs to be detected on input regions 455, 456, 457.
As shown in FIG. 5E1, at the beginning of the panorama capturing process, panel 533 displays a portion of the panorama image that has already been captured (e.g., partial image 529) and movement prompt 531 (e.g., an arrow) pointing in the direction of device movement required to complete the panorama image. Underneath panel 533, the currently field of view of the camera is displayed. The field of view of the camera is continuously updated during the panorama capturing based on the current location of the device relative to the outside environment.
In FIG. 5E2, as the device is moved rightward and the panorama capturing is in progress, the device detects that the device is deviating from horizontal movement, and the movement of the device needs to shift upward (e.g., the arrow is below the center line of panel 533), in order for the content of the panorama image captured at different points during movement of the device to line up properly (e.g., the top of the mountain in consecutive frames of the camera's image stream should occupy the same vertical location in the frames). In accordance with a determination that the device has deviated from horizontal movement, and that the device needs to be shifted upward to return objects in the field of view into proper positions for continuing the panorama image capturing, the device generates a coordinated tactile output (e.g., coordinated tactile output 523) using localized tactile output generators at input regions 456 and 457 on the left side of the device. In accordance with an extended tactile output profile for coordinated tactile output 523, the localized tactile output generator at input region 457 (e.g., the lower input region on the left side of the device) generates a sequence of discrete tactile outputs 523-1 with a first amplitude (e.g., a lower amplitude) and a gap between consecutive ones of the discrete tactile outputs 523-1 (e.g., as indicated by a series of small circular objects propagating from the lower input region, with each small circular object representing a respective discrete tactile output and with a distance of each respective small circular object from the lower input region corresponding an amount of time that has elapsed since a respective discrete tactile output represented by the respective small circular object was generated). Further in accordance with an extended tactile output profile for coordinated tactile output 523, the localized tactile output generator at input region 456 (e.g., the higher input region on the left side of the device) generates a sequence of discrete tactile outputs 523-2 with a second amplitude (e.g., a higher amplitude) and a gap between consecutive ones of the discrete tactile outputs (e.g., as indicated by a series of large circular objects propagating from the higher input region, with each large circular object representing a respective discrete tactile output and with a distance of each respective large circular object from the higher input region corresponding an amount of time that has elapsed since a respective discrete tactile output represented by the respective large circular object was generated). Further, in accordance with the extended tactile output profile, the device offsets the timing of localized tactile outputs 523-1 and localized tactile outputs 523-2 generated at the lower input region 457 and the higher input region 456, such that a coordinated sequence of discrete tactile outputs 523 are generated at the two input regions. For example, an example coordinated sequence is “2L-5H-2L-5H-2L-5H- . . . ”, where “2L” represents the lower strength (e.g., amplitude=2) tactile output generated at the lower input region 457, and “5H” represents the higher strength tactile output (e.g., amplitude=5) generated at the higher input region 456. Based on the coordinated tactile output sequence 523, the device prompts the user to shift the device upward (e.g., in the direction going from the region with the weaker tactile output 523-1 to the region with the stronger tactile output 523-2). In some embodiments, the coordinated tactile output sequence is continuously generated at input regions 456 and 457 until the device ceases to detect the deviation in the downward direction (e.g., until the user has moved the device upward and the rightward horizontal movement of the device is restored).
In FIG. 5E3, as the device continues to move rightward and the panorama capturing progresses toward completion, the device detects that the device is deviating from horizontal movement, and the movement of the device needs to shift downward (e.g., the arrow is above the center line of panel 533), in order for the content of the panorama image captured at different points during movement of the device to line up properly (e.g., the top of the mountain in consecutive frames of the camera's image stream should occupy the same vertical location in the frames). In accordance with a determination that the device has deviated from horizontal movement, and that the device needs to be shifted upward to return objects in the field of view into proper positions for continuing the panorama image capturing, the device generates a coordinated tactile output (e.g., coordinated tactile output 521) using localized tactile output generators at input regions 456 and 457 on the left side of the device. In accordance with an extended tactile output profile for the coordinated tactile output 521, the localized tactile output generator at input region 457 (e.g., the lower input region on the left side of the device) generates a sequence of discrete tactile outputs 521-1 with a third amplitude (e.g., a higher amplitude) and a gap between consecutive ones of the discrete tactile outputs 521-1 (e.g., as indicated by a series of large circular objects propagating from the lower input region, with each large circular object representing a respective discrete tactile output and with a distance of each respective large circular object from the lower input region corresponding an amount of time that has elapsed since a respective discrete tactile output represented by the respective large circular object was generated). Further in accordance with an extended tactile output profile for the coordinated tactile output 521, the localized tactile output generator at input region 456 (e.g., the higher input region on the left side of the device) generates a sequence of discrete tactile outputs 521-2 with a fourth amplitude (e.g., a lower amplitude) and a gap between consecutive ones of the discrete tactile outputs (e.g., as indicated by a series of small circular objects propagating from the higher input region, with each small circular object representing a respective discrete tactile output and with a distance of each respective small circular object from the higher input region corresponding an amount of time that has elapsed since a respective discrete tactile output represented by the respective small circular object was generated). Further in accordance with the extended tactile output profile, the device offsets the timing of the localized tactile outputs 521-1 and the localized tactile outputs 521-2 generated at the lower input region 457 and the higher input region 456, such that a coordinated sequence of discrete tactile outputs are generated at the two input regions. For example, an example tactile output sequence is “2H-5L-2H-5L-2H-5L . . . ”, where “2H” represents the lower strength (e.g., amplitude=2) tactile output generated at the higher input region 456, and “5L” represents the higher strength tactile output (e.g., amplitude=5) generated at the lower input region 457. Based on the coordinated tactile output sequence 521, the device prompts the user to shift the device downward (e.g., in the direction going from the region with the weaker tactile output 521-2 to the region with the stronger tactile output 521-1). In some embodiments, the coordinated tactile output sequence is continuously generated at input regions 456 and 457 until the device ceases to detect the deviation in the upward direction (e.g., until the user has moved the device downward and the rightward horizontal movement of the device is restored).
In FIG. 5E4, as the device continues to move rightward and the device detects that panorama capturing is close to completion (e.g., the horizontal movement of the device meets a predefined near-completion linear or angular displacement threshold). The device detects that the horizontal movement is stalled and/or that the device needs to move further rightward in order to complete the panorama image. In accordance with a determination that the device has deviated required rightward movement, and that the device needs to be moved rightward to continuing the panorama image capturing, the device generates a coordinated tactile output (e.g., coordinated tactile output 519) using localized tactile output generators at input region 456 on the left side of the device and input region 455 on the right side of the device. In accordance with an extended tactile output profile for coordinated tactile output 519, the localized tactile output generator at input region 456 (e.g., the upper input region on the left side of the device) generates a sequence of discrete tactile outputs 519-1 with a fifth amplitude (e.g., a lower amplitude) and a gap between consecutive ones of the discrete tactile outputs 519-1 (e.g., as indicated by a series of small circular objects propagating from the input region 456 on the left side of the device, with each small circular object representing a respective discrete tactile output and with a distance of each respective small circular object from the input region 456 corresponding an amount of time that has elapsed since a respective discrete tactile output represented by the respective small circular object was generated). Further in accordance with an extended tactile output profile for coordinated tactile output 519, the localized tactile output generator at input region 455 (e.g., the input region on the right side of the device) generates a sequence of discrete tactile outputs 519-2 with a sixth amplitude (e.g., a higher amplitude) and a gap between consecutive ones of the discrete tactile outputs (e.g., as indicated by a series of large circular objects propagating from the right input region 455, with each large circular object representing a respective discrete tactile output and with a distance of each respective large circular object from the right input region 455 corresponding an amount of time that has elapsed since a respective discrete tactile output represented by the respective larger circular object was generated). Further, in accordance with the extended tactile output profile, the device offsets the timing of localized tactile outputs 519-1 and localized tactile outputs 519-2 generated at the left input region 456 and the right input region 455, such that a coordinated sequence of discrete tactile outputs is generated at the two input regions. For example, an example tactile output sequence is “2L-5R-2L-5R-2L-5R . . . ”, where “2L” represents the lower strength (e.g., amplitude=2) tactile output generated at the left input region 456, and “5R” represents the higher strength tactile output (e.g., amplitude=5) generated at the right input region 455. Based on the coordinated tactile output sequence 519, the device prompts the user to shift the device rightward (e.g., in the direction going from the region with the weaker tactile output 519-1 to the region with the stronger tactile output 519-2). In some embodiments, the coordinated tactile output sequence is continuously generated at input regions 456 and 455 until the device's rightward motion is restored and/or the panorama is completed.
In FIG. 5E5, once the device has been moved rightward by the required amount, panorama capturing is completed. In response to detecting completion of the panorama image, the device ceases to display panel 533 over the field of view of the camera in the camera user interface 535. The panorama image 515 is saved into the photo library. In addition, the device optionally generates localized tactile output 517 (e.g., not part of the coordinated tactile output 519) at input region 455 to indicate that panorama capturing is completed.
FIGS. 5F1-5F6 illustrate exemplary user interfaces for providing haptic and visual feedback for guiding device movement to perform a respective task when the device is in a media capture mode of operation in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in
In FIG. 5F1, a camera user interface 513 is displayed, with a field of view of the camera capturing three subjects dancing (e.g., a man, a woman, and a girl). In FIG. 5F2, while the user holds the device (e.g., with contacts 511 and 509 on input regions 455, 456, and 457), the device detects a light press input by contact 509 (e.g., contact intensity exceeding a first intensity threshold (e.g., a hint intensity threshold ITH)) on input region 455 (e.g., also serving as a power button of the device). In response to detecting the light press input by contact 509 on input region 455, the device initiates a face detection and/or autofocus function of the camera application, and displays three indicators 505-1, 505-2, 505-3 around the faces of the three subjects that have been identified in the field of view of the camera. In addition, in conjunction with the face detection and autofocus function being activated, the device generates localized tactile output 507 (e.g., a series of weak taps) at input region 455 to indicate that autofocus and face detection has been triggered and ongoing as long as the intensity of contact 509 is maintained above the first intensity threshold (e.g., the hint intensity threshold ITH).
In FIG. 5F3, the device detects an increase in intensity of contact 509 above a second intensity threshold (e.g., the light press intensity threshold ITL) that is greater than the first intensity threshold (e.g., the hint intensity threshold ITH). In response to detecting the intensity of contact 509 increasing above the second intensity threshold, the device activates a video capturing function of the camera application, e.g., as indicated by the change in button 503. Face detection and autofocus continue in the field of view of the camera on user interface 513 as the subjects and the camera move around relative to one another. In response to detecting the intensity of contact 509 exceeding the second intensity threshold, the device generates localized tactile output 625 at input region 455 to indicate activation of the input region by contact 509 and activation the video capturing function of the camera as a result.
FIGS. 5F4-5F5 illustrate that, during the video capturing process, the device continuously monitors the location of the faces that are identified in the field of view, and generates a warning when the detected faces are about to move out of the field of view. Although simultaneous contact (e.g., contact 511 and 509) with all input regions are shown in FIGS. 5F4-5F6, localized tactile outputs are generated on two or more of the input regions at various times during the process illustrated herein, even if contact is not maintained at all times with all input regions during the process. In addition, generation of tactile outputs at input regions 455, 456, and 457, in some cases, are in response to criteria being met by objects detected in the field of view of the camera, do not require touch inputs to be detected on input regions 455, 456, 457.
In FIG. 5F4, when the device detects that one of the subjects' face (e.g., the girl's face) has moved to the left edge of the field of view of the camera, the device generates a coordinated tactile output (e.g., coordinated tactile output 601) using the lower input region 457 on the left side of the device and the input region 455 on the right side of the device. In accordance with a determination that an object on the lower left side of the field of view is about to go out of frame, and that the device needs to be shifted leftward to move the object away from the left edge of the field of view to continue the video capturing, the device generates a coordinated tactile output in accordance with an extended tactile output profile for coordinated tactile output 601. In accordance with the extended tactile output profile for coordinated tactile output 601, the localized tactile output generator at input region 457 (e.g., the lower input region on the left side of the device) generates a sequence of discrete tactile outputs 601-2 with a first amplitude (e.g., a higher amplitude) and a gap between consecutive ones of the discrete tactile outputs 601-2 (e.g., as indicated by a series of large circular objects propagating from the lower input region 457, with each large circular object representing a respective discrete tactile output and with a distance of each respective large circular object from the lower left input region corresponding an amount of time that has elapsed since a respective discrete tactile output represented by the respective large circular object was generated). Further in accordance with an extended tactile output profile for coordinated tactile output 601, the localized tactile output generator at input region 455 (e.g., the input region on the right side of the device) generates a sequence of discrete tactile outputs 601-1 with a second amplitude (e.g., a lower amplitude) and a gap between consecutive ones of the discrete tactile outputs (e.g., as indicated by a series of small circular objects propagating from the right input region, with each small circular object representing a respective discrete tactile output and with a distance of each respective small circular object from the right input region corresponding an amount of time that has elapsed since a respective discrete tactile output represented by the respective small circular object was generated). Further, in accordance with the extended tactile output profile, the device offsets the timing of localized tactile outputs 601-1 and localized tactile outputs 601-2 generated at the right input region 455 and the lower left input region 457, such that a coordinated sequence of discrete tactile outputs is generated at the two input regions. For example, an example tactile output sequence is “2R-5LL-2R-5LL-2R-5LL . . . ”, where “2R” represents the lower strength (e.g., amplitude=2) tactile output generated at the right input region 455, and “5LL” represents the higher strength tactile output (e.g., amplitude=5) generated at the lower left input region 457. Based on the coordinated tactile output sequence 601, the device prompts the user to shift the device leftward (e.g., in the direction going from the region with the weaker tactile output 601-1 to the region with the stronger tactile output 601-2). In some embodiments, the coordinated tactile output sequence is continuously generated at input regions 455 and 457 until the device detects that the object corresponding to indicator 505-3 is no longer near the left edge of the field of view of the camera (e.g., the object is completely off the screen, or is moved back in frame) (e.g., due to movement of the device and/or movement of the object corresponding to indicator 505-3).
In FIG. 5F5, when the device detects that one of the subjects' face (e.g., the woman's face) has moved to the right edge of the field of view of the camera, the device generates a coordinated tactile output (e.g., coordinated tactile output 603) using the upper input region 456 on the left side of the device and the input region 455 on the right side of the device. In accordance with a determination that an object on the upper right side of the field of view is about to go out of frame, and that the device needs to be shifted rightward to move the object away from the right edge of the field of view to continue the video capturing, the device generates a coordinated tactile output in accordance with an extended tactile output profile for the coordinated tactile output 603. In accordance with the extended tactile output profile for coordinated tactile output 603, the localized tactile output generator at input region 455 (e.g., the input region on the right side of the device) generates a sequence of discrete tactile outputs 603-1 with a first amplitude (e.g., a higher amplitude) and a gap between consecutive ones of the discrete tactile outputs 603-1 (e.g., as indicated by a series of large circular objects propagating from the right input region 455, with each large circular object representing a respective discrete tactile output and with a distance of each respective large circular object from the right input region corresponding an amount of time that has elapsed since a respective discrete tactile output represented by the respective large circular object was generated). Further in accordance with an extended tactile output profile for coordinated tactile output 603, the localized tactile output generator at input region 456 (e.g., the upper input region on the left side of the device) generates a sequence of discrete tactile outputs 603-2 with a second amplitude (e.g., a lower amplitude) and a gap between consecutive ones of the discrete tactile outputs (e.g., as indicated by a series of small circular objects propagating from the upper left input region, with each small circular object representing a respective discrete tactile output and with a distance of each respective small circular object from the upper left input region corresponding an amount of time that has elapsed since a respective discrete tactile output represented by the respective small circular object was generated). Further in accordance with the extended tactile output profile, the device offsets the timing of the localized tactile outputs 603-1 and the localized tactile outputs 603-2 generated at the right input region 455 and the upper left input region 456, such that a coordinated sequence of discrete tactile outputs are generated at the two input regions. For example, an example tactile output sequence is “2UL-5R-2UL-5R-2UL-5R . . . ”, where “2UL” represents the lower strength (e.g., amplitude=2) tactile output generated at the upper left input region 456, and “5R” represents the higher strength tactile output (e.g., amplitude=5) generated at the right input region 455. Based on the coordinated tactile output sequence 603, the device prompts the user to shift the device rightward (e.g., in the direction going from the region with the weaker tactile output 603-2 to the region with the stronger tactile output 603-1). In some embodiments, the coordinated tactile output sequence is continuously generated at input regions 455 and 456 until the device detects that the object corresponding to indicator 505-2 is no longer near the right edge of the field of view of the camera (e.g., the object is completely off the screen, or is moved back in frame) (e.g., due to movement of the device and/or movement of the object corresponding to indicator 505-2).
FIG. 5F6 illustrates that, when all of the detected subjects are well in frame, video capturing continues (e.g., with user's finger resting on the input regions 455, 456, and 457) and the device does not generate any coordinated tactile output to prompt movement of the device.
FIGS. 5G1-5G5 illustrate exemplary user interfaces for providing haptic and visual feedback for warning a user of impending performance of an operation in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in
In FIG. 5G1, menu 556 has been displayed in response to a prior light press input (e.g., in accordance with a process analogous to that shown in FIGS. 5C1-5C7). As show in FIG. 5G1, in addition to multiple selectable options (e.g., options 558, 560, and 562), indicator 5641 is displayed in menu 556 to indicate availability of an additional function (e.g., an emergency calling function) that can be triggered in response to an enhanced press input (e.g., a press input with an enhanced duration and/or intensity requirement).
In FIG. 5G2, as intensity of contact 605 on input region 455 increases above a light press intensity threshold ITL and continues to increase toward a deep press intensity threshold ITD, the device generates first localized tactile output 607 (e.g., a sequence of weak clicks) to indicate that a threshold intensity for triggering an emergency calling function of the device is about to be reached. In some embodiments, the strength of the localized tactile output is dynamically changed in accordance with a current intensity of the input by contact 605. In some embodiments, the device also changes the appearance of the indicator 5641 to indicate that the intensity of contact 605 is increasing toward the threshold intensity for triggering the emergency calling function.
In FIG. 5G3, the device detects that an intensity of the input by contact 605 has increased above the deep press intensity threshold ITS (e.g., warning-initiation criteria have been met). In response to detecting that the intensity of the input by contact 605 has exceeded the deep press intensity threshold ITD, the device starts a countdown for the emergency calling function and generates a first coordinated tactile output (e.g., coordinated tactile output 609) using localized tactile output generators located at input regions 455, 456, and 457, as a warning to the user that emergency services will be called at the end of the countdown (e.g., the countdown corresponding to a cancellation period) if a cancellation input is not received before the end of the countdown. In some embodiments, the coordinated tactile output 609 generated at the different input regions (e.g., localized tactile outputs 609-1, 609-2, and 609-3) are identical and synchronized. In some embodiments, the localized tactile outputs generated at the different input regions are offset in timing, to create a cycle of movement around the device. In some embodiments, the amplitudes of the tactile outputs continuously increase over time during the countdown period. As shown in FIG. 5G3, after the warning-initiation criteria are met by the increase in intensity of contact 605 above the deep press intensity threshold, notification 611 is displayed to indicate that emergency calling will be performed at the end of a 5 seconds countdown, and that intensity of the input needs to be maintained above the deep press intensity threshold ITS during the countdown period (e.g., a combined threshold of an intensity threshold and a time threshold need to be satisfied) in order to meet the operation-execution criteria to perform the emergency calling function. If the intensity threshold is not met or if the input terminates before the end of the countdown period, the emergency calling operation will not be performed and the warning tactile outputs will be stopped. In some embodiments, the appearance of indicator 5641 is changed (e.g., flashes or pulsates) to indicate that operation-execution criteria are about to be met and emergency calling function is about to be performed. In some embodiments, in addition to the localized tactile outputs and the visual feedback for indicating the impending performance of the emergency calling function, the device also generates a continuous and escalating (e.g., with increasing amplitudes) whole device tactile output (e.g., tactile output 613) to further enhance the effect of the warning.
In FIG. 5G4, when the countdown period is over and the operation-execution criteria for performing the emergency calling function are met (e.g., the combined intensity and duration threshold is met by the input by contact 605), the device stops generating the warning feedback (e.g., localized tactile outputs 609, notification 611, and whole device tactile output 613), and makes the call to emergency services. As shown in FIG. 5G4, notification 617 indicates that the emergency call is in progress. In some embodiments, the device generates a whole device tactile output (e.g., tactile output 615) to indicate that the emergency calling function is performed and in progress. At this point, cancellation of the emergency call operation is no longer permitted.
In FIG. 5G5, the call is connected, and the device ceases to generate any tactile output. Notification 619 is displayed to indicate that the call is connected, and a call termination affordance (e.g., button 621) is displayed. A tap input by contact 623 on the call termination affordance terminates the emergency call, and the user interface is restored to the state shown in FIG. 5G1.
FIGS. 5H1-5H5 illustrate exemplary user interfaces for providing haptic and visual feedback for warning a user of impending performance of an operation (e.g., activating a voice-based digital assistant) in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in
In FIG. 5H1, a user interface (e.g., wake screen user interface 501) is displayed. In FIG. 5H2, menu 556 has been displayed in response to a light press input by contact 627 (e.g., in accordance with a process analogous to that shown in FIGS. 5C1-5C7). A localized tactile output (e.g., localized tactile output 629) is generated to indicate that the light press intensity threshold has been met by the input. As show in FIG. 5H2, in addition to multiple selectable options (e.g., options 558, 560, and 562), indicator 5641 is displayed in menu 556 to indicate availability of an additional function (e.g., a digital assistant function) that can be triggered in response to an enhanced press input (e.g., a press input with an enhanced duration and/or intensity requirement).
In FIG. 5H3, when the intensity of the input by contact 627 is maintained above the light press intensity threshold ITL for at least a threshold amount of time T, the device generates a coordinated tactile output (e.g., tactile output 631) using localized tactile output generators at input regions 455 and 456. In some embodiments, the localized tactile output 631-1 and 631-2 are each a sequence of discrete tactile outputs, and the timing of the two sequences of discrete tactile outputs are slightly offset (e.g., by an amount corresponding to the gap between two consecutive discrete tactile outputs in one of the sequences) from each other. In some embodiments, in response to detecting that the intensity of the input by contact 627 is maintained above the light press intensity threshold ITL for at least a threshold amount of time T, the device starts to gather the computing resources to start the digital assistant.
In some embodiments, before the digital assistant is fully ready to accept and respond to voice input, the device displays visual feedback 633 and 637 (e.g., text greetings (e.g., “What can I help you with?” “Go ahead, I am listening . . . ”), an animation (e.g., animated waveforms), etc.) to indicate that the digital assistant is getting ready, as shown in FIGS. 5H3 and 5H4. In FIG. 5H4, before the digital assistant is fully ready to receive voice input and provide voice-based responses, the device continues to generate the localized tactile outputs 631 on the input regions 455 and 456. In some embodiments, the user does not need to maintain the intensity of the input above the light press intensity threshold ITL after the digital assistant has been triggered and the tactile outputs 631 are generated. In some embodiments, if a cancellation input (e.g., lift-off of contact 627) is detected before the digital assistant is fully activated and ready to respond to user's voice input, the device cease to generate the localized tactile outputs 631, and restores the user interface 501.
FIG. 5H5, the device detects that no cancellation input is detected before the digital assistant is fully activated and ready to respond to user's voice input, the device cease to generate the localized tactile outputs 631 and displays the digital assistant user interface 639. In some embodiments, in response to detecting that the digital assistant is fully activated and ready to respond to user's voice input and that no cancellation input is detected before the digital assistant is fully activated and ready to respond to user's voice input, the device ceases to generate localized tactile outputs 631, and generates whole device tactile output 641 to indicate that the digital assistant is fully ready to respond to the user's voice input.
FIGS. 5I1-5I6 illustrate providing, for each respective type of button interaction, tactile outputs that have varying tactile output profiles depending on the presence an interstitial material between the input region and the user's finger in accordance with some embodiments. These figures are used to illustrate the processes described below, including the processes in
For illustrative purposes, only two types of materials (e.g., material of case 643, and material of case 645) are used as example interstitial materials in FIGS. 5I1-5I6. In actual usage scenarios, many different types of interstitial materials are possible, and each correspond to respective ways of modifying the tactile output profile of a base tactile output (e.g., the tactile output generated when there is no interstitial material present) to produce consistent (e.g., nearly identical) haptic sensations on the user's finger through the different types of interstitial materials.
In some embodiments, depending on the actual material (e.g., the material category (e.g., leather, plastic, silicone, fabric, etc.), or actual properties of the material (e.g., elasticity, density, thickness, stiffness, etc.)) that is present between the input region and the user's finger, the type of input (e.g., the actual intensity of the input, or whether the input is a finger-rest input, a light press input, a deep press input, a horizontal swipe input, or a vertical swipe input on the input region) that is detected, and/or the type of tactile output (e.g., the waveform, the amplitude, the frequency, etc.) that is generated, the device uses different strategies to modify the tactile output profiles of the tactile outputs that are to be generated at the corresponding input regions with presence of an interstitial material (e.g., a case, or a glove, or clothing). FIGS. 5I1-5I6 illustrate qualitative modifications to the tactile output profiles for different interstitial materials, different types of inputs, and different types of tactile outputs. These qualitative modifications are not meant to be exhaustive and may be varied in various embodiments, depending on the actual usage scenario.
In FIG. 5I1, a press input with an intensity exceeding a hint intensity threshold ITH is detected on input region 455, and the device generates a localized tactile output in response to detecting the press input. In the left portion of FIG. 5I1, tactile output 649 is generated. The tactile output profile (e.g., a sequence of two discrete waveforms) of the tactile output 649 is provided in the bottom of the left portion of FIG. 5I1. In response to this press input, the device optionally performs an operation (e.g., displaying unread notifications on a darkened wake screen user interface as shown in FIG. 5A4, selecting an item in a menu as shown in FIG. 5C13, autofocusing on detected faces as shown in FIG. 5F2) in conjunction with generating the localized tactile output at input region 455.
In the middle portion of FIG. 5I1, device 100 (e.g., including input region 455) is covered by case 643. The device detects the same press input provided by the user (e.g., the intensity of the input is optionally determined while taking into consideration of the presence of the interstitial material between the user's finger and the input region 455) on the input region 455. In response to detecting the same press input, the device performs the same operation regardless of whether an interstitial material is present. But in accordance with a determination that an interstitial material (e.g., material one) is present, the device generates localized tactile output 653 with a modified tactile output profile. The modified tactile output profile of tactile output 653 is shown at the bottom of the middle portion of FIG. 5I1. In this example, the amplitude of the two discrete waveforms in the tactile output profile are modified (e.g., amplitude is increased by 50%) to overcome the dampening effect of the case 643, and to produce movement on the interstitial material over the input region on that is substantially similar to the movement of the input region caused by the tactile output 649 without presence of the interstitial material 643.
In the right portion of FIG. 5I1, device 100 (e.g., including input region 455) is covered by case 645. The device detects the same press input provided by the user (e.g., the intensity of the input is optionally determined while taking into consideration of the presence of the interstitial material between the user's finger and the input region 455) on the input region 455. In response to detecting the same press input, the device performs the same operation regardless of whether an interstitial material is present. But in accordance with a determination that an interstitial material (e.g., material two) is present, the device generates localized tactile output 657 with a modified tactile output profile. The modified tactile output profile of tactile output 657 is shown at the bottom of the right portion of FIG. 5I1. In this example, the amplitude of the two discrete waveforms in the tactile output profile are modified (e.g., amplitude is increased by 50%) to overcome the dampening effect of the case 645. In addition, a secondary waveform is generated with a slight time offset from the original waveform is added to the original waveform in the modified tactile output profile, to overcome the blurring effect of the fluffy material of the case. Based on the modified tactile output profile, the tactile output 657 produces movement on the interstitial material over the input region that is substantially similar to the movement of the input region caused by the tactile output 649 without presence of the interstitial material.
In the examples shown in FIG. 5I2, the interstitial materials are wrapped around the user's finger instead of being wrapped around the device. In the left portion of FIG. 5I2, there is no interstitial material present between the user's finger and the input region of the device. When the device detects a press input by contact 665 with an intensity above the hint intensity threshold, the device generates tactile output 667, with the same tactile output profile as that of tactile output 649 in FIG. 5I1. In the middle portion of FIG. 5I2, the same interstitial material used in case 643 is wrapped around the user's finger. As a result, when the device detects the same press input made by contact 669 through the interstitial material, the device generates a tactile output 671 with a modified tactile output profile to compensate for damping and distortion of the tactile output due to the presence of the interstitial material. In this example, the modified tactile output profile is the same as the tactile output profile of tactile output 653 that was generated when the same interstitial material was used in the case 643. In the right portion of FIG. 5I2, the same interstitial material used in case 645 is wrapped around the user's finger. As a result, when the device detects the same press input made by contact 673 through the interstitial material, the device generates a tactile output 675 with a modified tactile output profile to compensate for damping and distortion of the tactile output due to the presence of the interstitial material. In this example, the modified tactile output profile is the same as the tactile output profile of tactile output 657 that was generated when the same interstitial material was used in the case 645. In some embodiments, the tactile output profile of a tactile output is optionally modified differently depending on whether the interstitial material is used in a case wrapped around the device or used in a glove wrapped around the user's finger.
In FIG. 5I3, a press input with an intensity exceeding a light press intensity threshold ITL is detected on input region 455, and the device generates a localized tactile output in response to detecting the light press input. In the left portion of FIG. 5I3, tactile output 679 is generated. The tactile output profile (e.g., a sequence of two discrete waveforms (e.g., a stronger waveform followed by a weaker waveform)) of the tactile output 679 is provided in the bottom of the left portion of FIG. 5I3. In response to this light press input, the device optionally performs an operation (e.g., modifies read/unread status of notifications on wake screen user interface as shown in FIG. 5A5, modifying a value of a device parameter as shown in FIGS. 5B3 and 5B7, switching to a different parameter control as shown in FIG. 5B11, fully displaying a menu as shown in FIGS. 5C6 and 5D17, activating a video capturing mode as shown in FIG. 5F3, activating a digital assistant as shown in FIG. 5H3) in conjunction with generating the localized tactile output at input region 455.
In the middle portion of FIG. 5I3, device 100 (e.g., including input region 455) is covered by case 643. The device detects the same light press input provided by the user (e.g., the intensity of the input is optionally determined while taking into consideration of the presence of the interstitial material between the user's finger and the input region 455) on the input region 455. In response to detecting the same light press input, the device performs the same operation regardless of whether an interstitial material is present. But in accordance with a determination that an interstitial material (e.g., material one) is present, the device generates a localized tactile output 683 with a modified tactile output profile. The modified tactile output profile of tactile output 683 is shown at the bottom of the middle portion of FIG. 5I3. In this example, the amplitudes of the two discrete waveforms in the tactile output profile are modified differently (e.g., amplitude of waveform one is increased by 50%, amplitude of waveform two is increased by 40%) to overcome the dampening effect of the case 643, and to produce movement on the interstitial material over the input region on that is substantially similar to the movement of the input region caused by the tactile output 679 with presence of the interstitial material.
In the right portion of FIG. 5I3, device 100 (e.g., including input region 455) is covered by case 645. The device detects the same press input provided by the user (e.g., the intensity of the input is optionally determined while taking into consideration of the presence of the interstitial material between the user's finger and the input region 455) on the input region 455. In response to detecting the same press input, the device performs the same operation regardless of whether an interstitial material is present. But in accordance with a determination that an interstitial material (e.g., material two) is present, the device generates localized tactile output 687 with a modified tactile output profile. The modified tactile output profile of tactile output 687 is shown at the bottom of the right portion of FIG. 5I3. In this example, the amplitudes of the two discrete waveforms in the tactile output profile are modified differently (e.g., amplitude of the first waveform is modified by 45% and the amplitude of the second waveform are both increased by 40%) to overcome the dampening effect of the case 645. In addition, a secondary waveform is generated with a slight time offset from the original waveform is added to the original waveform in the modified tactile output profile, to overcome the blurring effect of the fluffy material of the case. Based on the modified tactile output profile, the tactile output 687 produces movement on the interstitial material over the input region that is substantially similar to the movement of the input region caused by the tactile output 679 without presence of the interstitial material.
In some embodiments, the tactile output profile of a tactile output is optionally modified the same way regardless of whether the interstitial material is used in a case wrapped around the device or used in a glove wrapped around the user's finger. In some embodiments, the tactile output profile of a tactile output is optionally modified differently depending on whether the interstitial material is used in a case wrapped around the device or used in a glove wrapped around the user's finger.
In FIG. 5I4, a press input with an intensity exceeding a deep press intensity threshold ITS is detected on input region 455, and the device generates a localized tactile output in response to detecting the deep press input. In the left portion of FIG. 5I4, tactile output 693 is generated. The tactile output profile (e.g., a discrete waveform with a stronger segment in the middle flanked by two weaker segments) of the tactile output 693 is provided in the bottom of the left portion of FIG. 5I4. In response to this deep press input, the device optionally performs an operation (e.g., displaying expanded versions of notifications on wake screen user interface as shown in FIG. 5A6, resetting a device parameter as shown in FIG. 5B9, starting a warning period of making an emergency call as shown in FIG. 5G3) in conjunction with generating the localized tactile output at input region 455.
In the middle portion of FIG. 5I4, device 100 (e.g., including input region 455) is covered by case 643. The device detects the same deep press input provided by the user (e.g., the intensity of the input is optionally determined while taking into consideration of the presence of the interstitial material between the user's finger and the input region 455) on the input region 455. In response to detecting the same deep press input, the device performs the same operation regardless of whether an interstitial material is present. But in accordance with a determination that an interstitial material (e.g., material one) is present, the device generates localized tactile output 697 with a modified tactile output profile. The modified tactile output profile of tactile output 697 is shown at the bottom of the middle portion of FIG. 5I4. In this example, the amplitude and the shape of the waveform in the tactile output profile are modified (e.g., amplitude of the central portion of the waveform is increased by 60%, amplitude of the side portions of the waveform is increased by 40%, and a secondary waveform is added to the central portion of the original waveform and is slightly offset from the original waveform) to overcome the dampening effect of the case 643, and to produce movement on the interstitial material over the input region on that is substantially similar to the movement of the input region caused by the tactile output 697 without presence of the interstitial material.
In the right portion of FIG. 5I4, device 100 (e.g., including input region 455) is covered by case 645. The device detects the same deep press input provided by the user (e.g., the intensity of the input is optionally determined while taking into consideration of the presence of the interstitial material between the user's finger and the input region 455) on the input region 455. In response to detecting the same deep press input, the device performs the same operation regardless of whether an interstitial material is present. But in accordance with a determination that an interstitial material (e.g., material two) is present, the device generates localized tactile output 701 with a modified tactile output profile. The modified tactile output profile of tactile output 701 is shown at the bottom of the right portion of FIG. 5I4. In this example, the amplitude and the shape of the waveform in the tactile output profile are modified (e.g., amplitude of the first waveform is increased by 40% and the amplitude of the second waveform is increased by 60%, and a secondary waveform is added to the entire original waveform and is slightly offset from the original waveform) to overcome the dampening effect of the case 645. Based on the modified tactile output profile, the tactile output 687 produces movement on the interstitial material over the input region that is substantially similar to the movement of the input region caused by the tactile output 693 without presence of the interstitial material.
In some embodiments, the tactile output profile of a tactile output is optionally modified the same way regardless of whether the interstitial material is used in a case wrapped around the device or used in a glove wrapped around the user's finger. In some embodiments, the tactile output profile of a tactile output is optionally modified differently depending on whether the interstitial material is used in a case wrapped around the device or used in a glove wrapped around the user's finger.
In FIG. 5I5, a long press input with an intensity exceeding a light press intensity threshold ITL and a duration of at least T is detected on input region 455, and the device generates a localized tactile output in response to detecting the long press input. In the left portion of FIG. 5I5, tactile output 705 is generated. The tactile output profile (e.g., a sequence of three discrete waveforms) of the tactile output 705 is provided in the bottom of the left portion of FIG. 5I5. In response to this long press input, the device optionally performs an operation (e.g., activating a digital assistant as shown in FIG. 5H3) in conjunction with generating the localized tactile output at input region 455.
In the middle portion of FIG. 5I5, device 100 (e.g., including input region 455) is covered by case 643. The device detects the same long press input provided by the user (e.g., the intensity of the input is optionally determined while taking into consideration of the presence of the interstitial material between the user's finger and the input region 455) on the input region 455. In response to detecting the same long press input, the device performs the same operation regardless of whether an interstitial material is present. But in accordance with a determination that an interstitial material (e.g., material one) is present, the device generates localized tactile output 709 with a modified tactile output profile. The modified tactile output profile of tactile output 709 is shown at the bottom of the middle portion of FIG. 5I5. In this example, the amplitude of the waveform in the tactile output profile are modified (e.g., amplitude of the three discrete waveforms is increased by 50%) to overcome the dampening effect of the case 643, and to produce movement on the interstitial material over the input region on that is substantially similar to the movement of the input region caused by the tactile output 705 without presence of the interstitial material.
In the right portion of FIG. 5I5, device 100 (e.g., including input region 455) is covered by case 645. The device detects the same long press input provided by the user (e.g., the intensity of the input is optionally determined while taking into consideration of the presence of the interstitial material between the user's finger and the input region 455) on the input region 455. In response to detecting the same long press input, the device performs the same operation regardless of whether an interstitial material is present. But in accordance with a determination that an interstitial material (e.g., material two) is present, the device generates a localized tactile output 713 with a modified tactile output profile. The modified tactile output profile of tactile output 713 is shown at the bottom of the right portion of FIG. 5I5. In this example, the amplitude and the shape of the waveform in the tactile output profile are modified (e.g., amplitude of the three discrete waveforms is increased by 50%) to overcome the dampening effect of the case 645. In addition, a secondary sequence of three discrete waveforms with lower amplitude (e.g., 30% strength) is added to the original sequence in the original tactile output profile. Based on the modified tactile output profile, the tactile output 713 produces movement on the interstitial material over the input region that is substantially similar to the movement of the input region caused by the tactile output 705 without presence of the interstitial material.
In some embodiments, the tactile output profile of a tactile output is optionally modified the same way regardless of whether the interstitial material is used in a case wrapped around the device or used in a glove wrapped around the user's finger. In some embodiments, the tactile output profile of a tactile output is optionally modified differently depending on whether the interstitial material is used in a case wrapped around the device or used in a glove wrapped around the user's finger.
In FIG. 5I6, a long finger-rest input with an intensity below the hint intensity threshold ITH and a duration of at least T is detected on input region 455, and the device generates a localized tactile output in response to detecting the long finger-rest input. In the left portion of FIG. 5I6, tactile output 717 is generated. The tactile output profile (e.g., a sequence of three discrete waveforms with increasing amplitudes) of the tactile output 717 is provided in the bottom of the left portion of FIG. 5I6. In response to this long finger-rest input, the device optionally performs an operation (e.g., checking the presence/absence of unread notifications without modifying the status of the notifications as shown in FIG. 5A3) in conjunction with generating the localized tactile output at input region 455.
In the middle portion of FIG. 5I6, device 100 (e.g., including input region 455) is covered by case 643. The device detects the same long finger-rest input provided by the user (e.g., the intensity of the input is optionally determined while taking into consideration of the presence of the interstitial material between the user's finger and the input region 455) on the input region 455. In response to detecting the same long finger-rest input, the device performs the same operation regardless of whether an interstitial material is present. But in accordance with a determination that an interstitial material (e.g., material one) is present, the device generates localized tactile output 721 with a modified tactile output profile. The modified tactile output profile of tactile output 721 is shown at the bottom of the middle portion of FIG. 5I6. In this example, the amplitude of the waveform in the tactile output profile are modified by different amounts (e.g., amplitudes of the three discrete waveforms are increased by 40%, 50%, and 60%, respectively) to overcome the dampening effect of the case 643, and to produce movement on the interstitial material over the input region on that is substantially similar to the movement of the input region caused by the tactile output 717 without presence of the interstitial material.
In the right portion of FIG. 5I6, device 100 (e.g., including input region 455) is covered by case 645. The device detects the same long finger-rest input provided by the user (e.g., the intensity of the input is optionally determined while taking into consideration of the presence of the interstitial material between the user's finger and the input region 455) on the input region 455. In response to detecting the same long finger-rest input, the device performs the same operation regardless of whether an interstitial material is present. But in accordance with a determination that an interstitial material (e.g., material two) is present, the device generates localized tactile output 725 with a modified tactile output profile. The modified tactile output profile of tactile output 725 is shown at the bottom of the right portion of FIG. 5I6. In this example, the amplitude and the shape of the waveform in the tactile output profile are modified (e.g., amplitudes of the three discrete waveforms are increased by 50%, 60%, and 50%, respectively, and the frequencies of the waveforms are doubled) to overcome the dampening effect of the case 645. Based on the modified tactile output profile, the tactile output 725 produces movement on the interstitial material over the input region that is substantially similar to the movement of the input region caused by the tactile output 717 without presence of the interstitial material.
In some embodiments, the tactile output profile of a tactile output is optionally modified the same way regardless of whether the interstitial material is used in a case wrapped around the device or used in a glove wrapped around the user's finger. In some embodiments, the tactile output profile of a tactile output is optionally modified differently depending on whether the interstitial material is used in a case wrapped around the device or used in a glove wrapped around the user's finger.
In the examples above, the inputs detected on the input region do not include movement of the contacts. However, in various embodiments, when an interstitial material is present between the user's finger and the input region of the device, and the device generates a localized tactile output in response to a swipe input detected on the input region (e.g., in the horizontal direction across the input region, or in the vertical direction along the input region), the device makes corresponding modifications to tactile output profiles of localized tactile outputs generated at the input region. The modifications are determined based on the characteristics of the original tactile output profile and the characteristics of the interstitial material, such that the movement of the interstitial material (e.g., a portion of the interstitial material proximate to or adjacent to the input region) generated by the modified tactile output is substantially similar to movement of the input region on the device generated by the original tactile output without presence of the interstitial material (e.g., the modified tactile output produces a similar haptic sensation (e.g., as measured by vibration strengths, frequencies, etc.) on the finger through the interstitial material as that produced by the original tactile output directly on the finger).
Method 6000 provides a mechanism for a user to query the device regarding a current state of a preset attribute of the device by a touch input without altering the attribute of the device, while preserving the option to alter the attribute with a continuation of the current input. In particular, the device generates an output to indicate the current state of the preset attribute (e.g., a current volume level, whether the ringer is on, whether there are unread notifications, etc.) without altering the current state of the attribute in response to an initial portion of a touch input on an off-display input region of the device (e.g., a side-button region) when device-query criteria are met, and proceeds to alter the current state of the preset attribute when a continuation of the input meets device-adjustment criteria. Providing a light-weight mechanism for a user to obtain a current state of a device attribute without altering the device attribute and allowing the user to directly alter the device attribute by continuing the same input (e.g., with an increase in contact intensity) after seeing the current state of the device attribute enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide inputs required to achieve an intended outcome and reducing user mistakes when operating/interacting with the device, and by reducing the number of steps to perform an action), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. In some embodiments, the current state of the device attribute is provided via a tactile output without unnecessarily powering up the display and/or other functions of the device, which further reduces power usage and improves the battery life of the device when the user frequently checks the current state of the device attribute without intending to alter the device attribute.
The method 6000 is performed at an electronic device (e.g., device 300,
In accordance with method 6000 and with reference to
In accordance with method 6000 and with reference to
In some embodiments, in response to detecting the first portion of the first input by the contact and in accordance with a determination that the first portion of the first input by the contact does not meet the first criteria, the device forgoes providing the first output. For example, when a user rests a finger on the side button or lightly presses on the side button, the display is lit and a user interface object corresponding to the attribute of the device, e.g., a volume control, a ringer control, or a notification summary for unread notifications, is displayed. The attribute of the device has multiple possible states (e.g., discrete configurations, values, and/or statuses, or values in a continuous range of values) that the device can take on in accordance automated device adjustments, triggered by external events, and/or in accordance with user's prior manual adjustments. In some embodiments, the user interface object is optionally an interactive control object that can react to user inputs, e.g., a swipe input or press input to adjust a slider or toggle a button shown on the user interface object. In some embodiments, the user interface object merely displays a visual indication of the state of the attribute. In some embodiments, in addition to or instead of the visual indication of the state of the attribute, the device output a local tactile output at the side button using the local tactile output generators located at the side button, or a whole-device tactile output using the internal actuators located inside of the device. When the first output that indicates the current state of the first attribute of the device, the current state of the first attribute is not altered, e.g., when the volume control is initially displayed in response to the first portion of the input, the volume control shows the current volume level without altering the current volume level; when the ringer control is displayed, the current ringer on/off setting is not altered; when the notification summary is initially displayed, it shows the number of unread notifications and optionally the senders of the notifications without content of the notifications; when a tactile output is generated to indicate that there are one or more unread notifications, the read/unread status of the unread notifications are not altered and the number of unread notifications at the device is not changed. In some embodiments, when the device has at least one unread notification, the device generates a tactile output with a first tactile output pattern (e.g., a double buzz, or a buzz with a tactile output profile that corresponds to the total number of unread notifications) in response to the first portion of the input, and when the device has no unread notification, the device generates no tactile output, or a tactile output with a second tactile output pattern (e.g., a single buzz or a lighter buzz). In some embodiments, the tactile output is generated without activating the display if the display is off at the time that the first portion of the input is detected.
In accordance with method 6000 and with reference to
In accordance with method 6000 and with reference to
In accordance with method 6000 and with reference to
In accordance with method 6000 and with reference to
In accordance with method 6000 and with reference to
In accordance with method 6000 and with reference to
In accordance with method 6000 and with reference to
In accordance with method 6000 and with reference to
In accordance with method 6000 and with reference to
In accordance with method 6000 and with reference to
In accordance with method 6000 and with reference to
In accordance with method 6000 and with reference to
It should be understood that the particular order in which the operations in
Method 7000 relates to displaying a precursor (e.g., a visual indicator) of a user interface object with multiple selectable options (e.g., a menu) in response to a first portion of a touch input (e.g., with a low intensity) detected on an off-screen input region, and revealing the user interface object by a varying amount that corresponds to varying intensity of the touch input during a second portion of the touch input once the intensity of the input has increased above an intensity threshold. Displaying the precursor object before the intensity reaches the intensity threshold and revealing varying amount of the user interface object in accordance with the varying intensity of the input enhance the operability of the device and make the user-device interface more efficient (e.g., by providing dynamic visual feedback that directly corresponds to the intensity of the user's input, and helping the user to provide inputs required to achieve an intended outcome and reducing user mistakes when operating/interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
The method 7000 is performed at an electronic device (e.g., device 300,
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
In accordance with method 7000 and with reference to
It should be understood that the particular order in which the operations in
Method 8000 relates to modifying a parameter of the device in one of two distinct manners (e.g., a first manner and a second manner distinct from the first manner) in response to a press input on an off-display input region (e.g., a side button region) in accordance with whether the input is detected on a first sub-region or a second sub-region of the input region. Modifying the parameter in different manners in accordance with a determination of which one of two sub-regions of the input region is activated by the press input enhances the operability of the device and makes the user-device interface more efficient (e.g., by reducing number of inputs required to achieve an intended result), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. In addition, forgoing modifying the parameter in the different manners in accordance with a determination of the input on the input region did not meet the intensity threshold (e.g., the input is not a press input) enhances the operability of the device and makes the user-device interface more efficient (e.g., by reducing user mistakes when operating/interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
The method 8000 is performed an electronic device (e.g., device 300,
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
In accordance with method 8000 and with reference to
It should be understood that the particular order in which the operations in
Method 9000 relates providing localized tactile outputs using tactile output generators located at different locations of the device to guide and prompt movement of the device in order to continue performance of a respective task (e.g., completing a panorama picture, navigating to a destination, searching for an object), where the respective task is performed during a media capturing mode of operation of the device, and the tactile output generators are selectively activated to prompt the movement of the device in a respective direction in accordance with a direction by which one or more objects in the field of view of the camera need to be shifted in order to continue performance of the task. Using localized tactile outputs to guide and prompt the user to move the device in a respective direction based on the direction by which an object in the field of view of the camera needs to be shifted to continue performance of the task enhances the operability of the device and makes the user-device interface more efficient (e.g., by providing improved feedback to help the user to provide required inputs to achieve an intended outcome, and by reducing user mistakes when operating/interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
The method 9000 is performed at an electronic device (e.g., device 300,
In accordance with method 9000 and with reference to
While performing the respective task, the device detects (9006) that one or more objects (e.g., predefined objects, visual markers, features, landmarks, etc.) in a field of view of the one or more cameras of the device meet first criteria (e.g., device-shifting criteria). For example, in FIGS. 5E2 and 5E3, the mountains in field of view deviate from horizontal movement. In FIG. 5E4, movement of the mountains in the field of view is stalled or stopped before completion of the panorama image. In FIGS. 5F4 and 5F5, faces 505-3 and 505-3 are about to move out of frame. In some embodiments, the first criteria are used to determine whether movement of the field of view of the cameras is required in order to satisfy the requirements for performing the respective task. Depending on the respective task, the requirements may be different. For example, when capturing a panorama image, the requirement is for the field of view to shift horizontally (e.g., parallel to the ground), and the first criteria are met when the device detects a deviation from the horizontal movement as determined based on changing positions of one or more objects in the field of view of the camera. In another example, when providing turn-by-turn navigation instructions on a vehicle, one of the requirements is to have the field of view of the camera on a correct lane based on the next turn (e.g., right lane for an upcoming right turn, and left lane for an upcoming left turn), and the first criteria are met when the device detects that vehicle is not in the correct lane (e.g., based on the road markings identified in the field of view of the cameras). In another example, when capturing an image for a photo ID, the requirement is that a subject's head needs to fit within a predefined box in the image; and the first criteria are met when the device detects that the subjects head is not within the predefined box (e.g., off-center or too large) in the field of view of the camera.
In response to detecting that the one or more objects in the field of view of the one or more cameras meet the first criteria (9006), the device generates, with one or more of the plurality of tactile output generators, a tactile output (e.g., tactile output 523 in FIG. 5E2, tactile output 524 in FIG. 5E3, tactile output 519 in FIG. 5E4, tactile output 601 in FIG. 5F4, tactile output 603 in FIG. 5F5) prompting movement of the field of view of the one or more cameras in a respective direction (e.g., through moving (e.g., translation in 2D, translation in 3D, rotation, panning, pivoting, tilting, or combinations of the above, etc.) the device as a whole or a part of the device that includes the camera(s)), wherein generating the tactile output prompting movement of the field of view of the one or more cameras in the respective direction includes: in accordance with a determination, based on the one or more objects in the field of view of the camera, that the field of view of the camera needs to be shifted in a first direction (e.g., leftward, clockwise, upward, forward, in the northwest direction, closer to user, or a combination of two or more of the above, etc.) to continue performing the respective task (e.g., to continue capturing of the panorama image, to continue providing turn by turn navigation instructions on the vehicle, to continue searching for the particular object in the surrounding environment (e.g., pairing smart home devices), to continue capturing of the image of the object or person with the predefined framing and alignment requirements (e.g., for biometric authentication, for certain artistic composition), to continue providing vehicle steering guidance (e.g., reverse parking, releasing/pickup load on target, etc.), to continue providing guidance for remote navigation control for controlling unmanned vehicles (e.g., an aerial drone), to continue providing guidance for camera-assisted surgery, etc.), generating a first tactile output (e.g., the first tactile output is provided by the first tactile output generator, and is localized at the first location of in the device (e.g., a left edge of the device)) that prompts movement of the field of view of the one or more cameras in the first direction (e.g., tactile output 523 in FIG. 5E2 upward prompts movement of the field of view; or tactile output 601 in FIG. 5F4 prompts leftward movement of the field of view); and in accordance with a determination, based on the one or more objects in the field of view of the camera, that the field of view of the camera needs to be shifted in a second direction (e.g., rightward, counter-clockwise, downward, backward, in the southeast direction, farther away from the user, or a combination of two or more of the above, etc.), different from the first direction, to continue performing the respective task, generating a second tactile output (e.g., the second tactile output is provided by the second tactile output generator, and is localized at the second location of in the device (e.g., a right edge of the device)), different from the first tactile output, that prompts movement of the field of view of the one or more cameras in the second direction (e.g., tactile output 521 in FIG. 5E3 prompts downward movement of the field of view and tactile output 519 in FIG. 5E4 prompts forward movement of the field of view; or tactile output 603 in FIG. 5F5 prompts rightward movement of the field of view).
In accordance with method 9000 and with reference to
In accordance with method 9000 and with reference to
In accordance with method 9000 and with reference to
In accordance with method 9000 and with reference to
In accordance with method 9000 and with reference to
In accordance with method 9000 and with reference to
In accordance with method 9000 and with reference to
In accordance with method 9000 and with reference to
In accordance with method 9000 and with reference to
In accordance with method 9000 and with reference to
It should be understood that the particular order in which the operations in
Method 10000 relates to generating a warning tactile output when first criteria are met by an input on an input region but second criteria are not met by the input, and performing an operation when the second criteria (e.g., with an enhanced requirement relative to the first criteria) are met by the input. Providing the warning tactile output using a tactile output generator associated with the input region before the second criteria are met enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide required inputs to achieve an intended outcome, and reducing user mistakes when operating/interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. In addition, forgoing generating the tactile output when the first criteria are not met, and forgoing performing the operation when a cancellation input is detected before the second criteria are met enhance the operability of the device and make the user-device interface more efficient (e.g., by reducing user mistakes when operating/interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
The method 10000 is performed at an electronic device (e.g., device 300,
In accordance with method 10000 and with reference to
In accordance with method 10000 and with reference to
In accordance with method 10000 and with reference to
In accordance with method 10000 and with reference to
In accordance with method 10000 and with reference to
In accordance with method 10000 and with reference to
In accordance with method 10000 and with reference to
In accordance with method 10000 and with reference to
In accordance with method 10000 and with reference to
In accordance with method 10000 and with reference to
In accordance with method 10000 and with reference to
In accordance with method 10000 and with reference to
In accordance with method 10000 and with reference to
It should be understood that the particular order in which the operations in
Method 11000 relates to changing characteristics of a tactile output (e.g., embodied in a tactile output profile of the tactile output, including amplitude, pattern, frequency, accompanying audio, coordination between other concurrently generated tactile outputs, etc.) in accordance with whether there is an interstitial material present between the input object (e.g., the user's finger) and the input region of the device on which the input is detected. Changing the characteristics of the tactile output in accordance with presence/absence of the interstitial material and, optionally, in accordance with the properties of the interstitial material enables the device to provide consistent haptic feedback to the user when the device is operated under a variety conditions (e.g., wrapped in various types of cases, operated by gloved fingers, or operated through clothing). Providing consistent haptic feedback under different operating conditions enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide required inputs to achieve an intended outcome, and reducing user mistakes when operating/interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.}
The method 11000 is performed at an electronic device (e.g., device 300,
In accordance with method 11000 and with reference to
In accordance with method 11000 and with reference to
In accordance with method 11000 and with reference to
In accordance with method 11000 and with reference to
In accordance with method 11000 and with reference to
In accordance with method 11000 and with reference to
In accordance with method 11000 and with reference to
In accordance with method 11000 and with reference to
In accordance with method 11000 and with reference to
In accordance with method 11000 and with reference to
In accordance with method 11000 and with reference to
It should be understood that the particular order in which the operations in
Method 12000 relates to generating tactile outputs with different tactile output profiles in responds to different types of touch inputs detected on an off-screen input region on a peripheral-side of the device adjacent to the display, including a press input on the input region and a swipe input across the input region (e.g., a swipe input in a horizontal direction across an elongated input region or a swipe input in a vertical direction along the elongated input region). Providing different haptic feedback (via tactile outputs with different tactile output profiles) in response to different types of inputs detected on the input region enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide required inputs to achieve an intended outcome, and reducing user mistakes when operating/interacting with the device), which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.}
The method 12000 is performed at an electronic device (e.g., device 300,
In accordance with method 12000 and with reference to
In response to detecting the input on the input region (12004): in accordance with a determination that the input by the contact (e.g., light press input by contact 506 in FIG. 5A5, light press input by contact 518 in FIG. 5B3, light press input by contact 534 in FIG. 5B7, light press input by contact 552 in FIG. 5C6, light press input by contact 557 in FIG. 5D17, light press input by contact 509 in FIG. 5F3, or light press input by contact 627 in FIG. 5H2) on the input region meets first criteria (e.g., button-press criteria), wherein the first criteria (e.g., the button-press criteria) require an increase in intensity of the input above a first intensity threshold (e.g., a light press intensity threshold that is greater than a contact detection threshold and less than a deep press intensity threshold) in order for the first criteria to be met, the device performs a first operation (e.g., displaying a menu of selectable options, displaying a control object for controlling a device parameter (e.g., volume, ringer setting, etc.)) and generating a first tactile output (e.g., tactile output 510 in FIG. 5A5, tactile output 524 in FIG. 5B3, tactile output 536 in FIG. 5B7, tactile output 566 in FIG. 5C6, tactile output 553 in FIG. 5D17, tactile output 625 in FIG. 5F3, or tactile output 629 in FIG. 5H2) with a first tactile output profile (e.g., to simulate actuation of a button in a direction perpendicular to a region of input region at the contact location). In some embodiments, the first tactile output is generated during a down-press phase of the input. In some embodiments, the first tactile output is generated during a release phase of the input. In some embodiments, a pair of tactile outputs are generated, one for the down-press and one for the release.
In response to detecting the input on the input region (12004): in accordance with a determination that the input on the input region (e.g., input by contact 585 in FIGS. 5D2-5D3, input by contact 564 in FIGS. 5C10-5C12, input by contact 580 in FIG. 5C15-5C17, input by contact 551 in FIGS. 5D18-5D19, input by contact 547) meets second criteria that are distinct from the first criteria (e.g., the second criteria are one of button-toggle criteria or button-slide criteria), wherein the second criteria (e.g., one of button-toggle criteria or button-slide criteria) require that the input includes movement of a contact along a first direction across the input region (e.g., in a direction across an elongated touch-sensitive region on the peripheral-side of the device (for button-toggle criteria), or in a direction along the elongated touch-sensitive region on the peripheral-side of the device (for button-slide criteria)) in order for the second criteria to be met, the device performs a second operation (e.g., turning on/off the ringer) different from the first operation and generating a second tactile output (e.g., tactile output 581 in FIG. 5D3, tactile output 5663 in FIGS. 5C10-5C12, tactile outputs 586 and 592 in FIGS. 5C15-5C17, tactile outputs 549 and 545 in FIGS. 5D18-5D19) with a second tactile output profile that is distinct from the first tactile output profile (e.g., a tactile output to simulate toggling of a switch that toggles in response to lateral movement or force (e.g., in a button-toggle input), or a tactile output to simulate sliding of a slider that moves in response to lateral movement or force (e.g., in a button slide input)).
In accordance with method 12000 and with reference to
In accordance with method 12000 and with reference to
In accordance with method 12000 and with reference to
In accordance with method 12000 and with reference to
In accordance with method 12000 and with reference to
In accordance with method 12000 and with reference to
In accordance with method 12000 and with reference to
In accordance with method 12000 and with reference to
In accordance with method 12000 and with reference to
In accordance with method 12000 and with reference to
In accordance with method 12000 and with reference to
In accordance with method 12000 and with reference to
In accordance with method 12000 and with reference to
In accordance with method 12000 and with reference to
In accordance with method 12000 and with reference to
It should be understood that the particular order in which the operations in
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best use the invention and various described embodiments with various modifications as are suited to the particular use contemplated.
This application claims priority to U.S. Provisional Application Ser. No. 62/668,187, filed May 7, 2018, which is incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 9082269 | Olsson et al. | Jul 2015 | B2 |
| 20100156818 | Burrough et al. | Jun 2010 | A1 |
| 20120023524 | Suk | Jan 2012 | A1 |
| 20140049521 | Gil et al. | Feb 2014 | A1 |
| 20150020109 | Higa | Jan 2015 | A1 |
| 20150058723 | Cieplinski et al. | Feb 2015 | A1 |
| 20150062052 | Bernstein et al. | Mar 2015 | A1 |
| 20150067495 | Bernstein et al. | Mar 2015 | A1 |
| 20150067496 | Missig et al. | Mar 2015 | A1 |
| 20150067497 | Cieplinski et al. | Mar 2015 | A1 |
| 20150067513 | Zambetti et al. | Mar 2015 | A1 |
| 20150067519 | Missig et al. | Mar 2015 | A1 |
| 20150067559 | Missig et al. | Mar 2015 | A1 |
| 20150067560 | Cieplinski et al. | Mar 2015 | A1 |
| 20150067563 | Bernstein et al. | Mar 2015 | A1 |
| 20150067596 | Brown et al. | Mar 2015 | A1 |
| 20150067601 | Bernstein et al. | Mar 2015 | A1 |
| 20150067602 | Bernstein et al. | Mar 2015 | A1 |
| 20150067605 | Zambetti et al. | Mar 2015 | A1 |
| 20150135109 | Zambetti et al. | May 2015 | A1 |
| 20150138126 | Westerman | May 2015 | A1 |
| 20150138155 | Bernstein et al. | May 2015 | A1 |
| 20150143273 | Bernstein et al. | May 2015 | A1 |
| 20150149899 | Bernstein et al. | May 2015 | A1 |
| 20150149964 | Bernstein et al. | May 2015 | A1 |
| 20150149967 | Bernstein et al. | May 2015 | A1 |
| 20150153929 | Bernstein et al. | Jun 2015 | A1 |
| 20150378519 | Brown et al. | Dec 2015 | A1 |
| 20160004427 | Zambetti et al. | Jan 2016 | A1 |
| 20160004428 | Bernstein et al. | Jan 2016 | A1 |
| 20160004429 | Bernstein et al. | Jan 2016 | A1 |
| 20160004430 | Missig et al. | Jan 2016 | A1 |
| 20160004431 | Bernstein et al. | Jan 2016 | A1 |
| 20160004432 | Bernstein et al. | Jan 2016 | A1 |
| 20160011771 | Cieplinski | Jan 2016 | A1 |
| 20160041750 | Cieplinski et al. | Feb 2016 | A1 |
| 20160210025 | Bernstein et al. | Jul 2016 | A1 |
| 20160225568 | Chen | Aug 2016 | A1 |
| 20160259413 | Anzures et al. | Sep 2016 | A1 |
| 20160259497 | Foss et al. | Sep 2016 | A1 |
| 20160259498 | Foss et al. | Sep 2016 | A1 |
| 20160259499 | Kocienda et al. | Sep 2016 | A1 |
| 20160259518 | King et al. | Sep 2016 | A1 |
| 20160259519 | Foss et al. | Sep 2016 | A1 |
| 20160259527 | Kocienda et al. | Sep 2016 | A1 |
| 20160259528 | Foss et al. | Sep 2016 | A1 |
| 20160291770 | Kocienda | Oct 2016 | A1 |
| 20170046024 | Dascola | Feb 2017 | A1 |
| 20170046025 | Dascola et al. | Feb 2017 | A1 |
| 20170075520 | Bauer et al. | Mar 2017 | A1 |
| 20170075562 | Bauer et al. | Mar 2017 | A1 |
| 20170075563 | Bauer et al. | Mar 2017 | A1 |
| 20170212673 | Bernstein et al. | Jul 2017 | A1 |
| 20170357317 | Chaudhri et al. | Dec 2017 | A1 |
| 20170357319 | Chaudhri et al. | Dec 2017 | A1 |
| 20170357320 | Chaudhri et al. | Dec 2017 | A1 |
| 20170357358 | Teutschler et al. | Dec 2017 | A1 |
| 20180024681 | Bernstein et al. | Jan 2018 | A1 |
| 20180039368 | Choi et al. | Feb 2018 | A1 |
| 20180059809 | McClendon | Mar 2018 | A1 |
| 20180067554 | Chaudhri et al. | Mar 2018 | A1 |
| 20180067555 | Chaudhri et al. | Mar 2018 | A1 |
| 20180067622 | Chaudhri et al. | Mar 2018 | A1 |
| 20180188920 | Bernstein et al. | Jul 2018 | A1 |
| 20180275862 | Khoe et al. | Sep 2018 | A1 |
| 20180364883 | Khoe et al. | Dec 2018 | A1 |
| 20180364904 | Bernstein et al. | Dec 2018 | A1 |
| 20190018562 | Bernstein et al. | Jan 2019 | A1 |
| 20190042075 | Bernstein et al. | Feb 2019 | A1 |
| 20190042078 | Bernstein et al. | Feb 2019 | A1 |
| 20190050055 | Chaudhri et al. | Feb 2019 | A1 |
| 20190065043 | Zambetti et al. | Feb 2019 | A1 |
| 20190065240 | Kong | Feb 2019 | A1 |
| 20190073003 | Xu | Mar 2019 | A1 |
| 20190138189 | Missig | May 2019 | A1 |
| 20190146643 | Foss et al. | May 2019 | A1 |
| 20190163358 | Dascola et al. | May 2019 | A1 |
| 20190171354 | Dascola et al. | Jun 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| WO 2007103631 | Sep 2007 | WO |
| Entry |
|---|
| Pediredla, “Understanding 3D Touch From a Development Perspective”, http://blog.hedgehoglab.com/understanding-3d-touch-develepment, Feb. 8, 2016, 10 pages. |
| Invitation to Pay Additional Fees, dated Oct. 7, 2019, received in International Patent Application No. PCT/US2019/031078, which corresponds with U.S. Appl. No. 16/403,329, 30 pages. |
| International Search Report and Written Opinion, dated Dec. 2, 2019, received in International Patent Application No. PCT/US2019/031078, which corresponds with U.S. Appl. No. 16/403,329, 32 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20190339804 A1 | Nov 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62668187 | May 2018 | US |
