Patent Grant
10620708
This relates generally to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that generate tactile outputs to provide haptic feedback to a user.
The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Example touch-sensitive surfaces include touchpads and touch-screen displays. Such surfaces are widely used to manipulate user interfaces and objects therein on a display. Example user interface objects include digital images, video, text, icons, and control elements such as buttons and other graphics.
Haptic feedback, typically in combination with visual and/or audio feedback, is often used in an attempt to make manipulation of user interfaces and user interface objects more efficient and intuitive for a user, thereby improving the operability of electronic devices.
However, applications that provide different haptic feedback in response to a same gesture present challenges to users, which may lead to unintended operations. When devices perform unintended operations, the user needs to cancel such operations and provide inputs again. These manipulations are cumbersome and tedious. In addition, having to undo unintended operations and providing inputs again take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices. Thus, it would be desirable to have a framework for providing haptic feedback.
Accordingly, there is a need for electronic devices with faster, more efficient, and more consistent methods and interfaces for providing haptic feedback (typically in conjunction with visual and/or audio feedback), which in turn make manipulation of user interfaces more efficient and intuitive for a user. Such methods and interfaces optionally complement or replace conventional methods for providing haptic feedback. Such methods and interfaces reduce the number, extent, and/or nature of the inputs from a user by helping the user to understand the connection between provided inputs and device responses to the inputs, thereby creating a more efficient human-machine interface. In addition, such methods and interfaces provide a more consistent human-machine interface for a plurality of software applications. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.
The above deficiencies and other problems associated with user interfaces for electronic devices with touch-sensitive surfaces are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, 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, one or more input devices, and one or more tactile output generators. The method includes displaying, on the display, a user interface for a first software application. The user interface includes a plurality of elements to which user interaction models from a plurality of user interaction models provided by an application-independent module have been assigned, the plurality of elements including a first element to which a first user interaction model has been assigned, the plurality of elements having content provided by an application-specific module for the first software application. The first user interaction model defines how the user interface responds to inputs directed to the first element of the user interface. The method also includes, while displaying the user interface, detecting, via the one or more input devices, an input directed to the first element of the user interface. The method further includes, in response to detecting the input: updating the user interface on the display based on characteristics of the input; in accordance with a determination that the input meets tactile output criteria specified by the first user interaction model, generating a first tactile output corresponding to the input; and, in accordance with a determination that the input does not meet the tactile output criteria specified by the first user interaction model, forgoing generation of the first tactile output.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more tactile output generators. The method includes displaying, on the display, a user interface; and detecting an occurrence of a first condition that triggers a first user interface event that is associated with a tactile output. Generating the first user interface event includes displaying one or more changes to the user interface. The device will not be able to generate the tactile output associated with the first user interface event for a respective amount of time. The method also includes, in response to detecting the occurrence of the first condition, in accordance with a determination that the first user interface event corresponds to a first user interface event category: delaying generating the first user interface event for at least the respective amount of time; and, after delaying generating the first user interface event for at least the respective amount of time, displaying the one or more changes to the user interface and generating the tactile output that is associated with the first user interface event. The display of the one or more changes to the user interface is synchronized with the generation of the tactile output that is associated with the first user interface event.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more tactile output generators. The method includes, while the one or more tactile output generators are in a low-power state, receiving an indication that a user interaction has started. A respective portion of the user interaction is associated with a tactile output. The low-power state is a state in which tactile outputs are generated with a first amount of latency. The method also includes, in response to receiving the indication that the user interaction that is associated with the tactile output has started, in accordance with a determination that the indication meets tactile output generator preparation criteria, setting the one or more tactile output generators to a low-latency state at a first time. The low-latency state is a state in which the tactile outputs are generated with a second amount of latency that is lower than the first amount of latency. The method further includes, after setting the one or more tactile output generators to the low-latency state: in accordance with a determination that the user interaction has reached the respective portion of the user interaction that is associated with the tactile output before a predefined amount of time since the first time has elapsed and that the one or more tactile output generators are still in the low-latency state, generating the tactile output using the one or more tactile output generators with the second amount of latency; and, in accordance with a determination that a tactile output has not been generated for at least the predefined amount of time since the first time, transitioning the one or more tactile output generators from the low-latency state to the low-power state.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more tactile output generators. The method includes, while a first type of event is associated with a first tactile output and a second type of event that is distinct from the first type of event is associated with a second tactile output that is different from the first tactile output by an application-independent module, receiving first information from a first application; and, in response to receiving the first information from the first application, generating a response to the first information, including: in accordance with a determination that the first information corresponds to an application event of the first type, generating the first tactile output using the one or more tactile output generators; and, in accordance with a determination that the first information corresponds to an application event of the second type that is distinct from the first type, generating, using the one or more tactile output generators, the second tactile output that is different from the first tactile output. The method also includes, after generating the response to the first information, receiving second information from a second application that is distinct from the first application; and, in response to receiving the second information from the second application, generating a response to the second information, including: in accordance with a determination that the second information corresponds to an application event of the first type, generating the first tactile output using the one or more tactile output generators; and, in accordance with a determination that the second information corresponds to an application event of the second type, generating the second tactile output using the one or more tactile output generators.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more tactile output generators. The method includes receiving, at an application-independent module, from an application-specific module that is associated with a first application, information about an input directed to a user interface of the first application. An operation performed in the user interface of the first application in response to detecting the input is associated with a tactile output pattern specified by the application-specific module. The information about the input includes information indicating a magnitude of the operation performed in the user interface in response to detecting the input. The method also includes, in response to receiving the information about the input directed to the user interface of the first application, generating, via the one or more tactile output generators, a tactile output that corresponds to the operation performed in the user interface of the first application. The tactile output has the tactile output pattern specified by the application-specific module. The tactile output has an amplitude determined in accordance with the magnitude of the operation performed in the user interface of the first application in response to detecting the input.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more tactile output generators. The method includes displaying a user interface on the display; and, while displaying the user interface on the display and while the one or more tactile output generators are in a low-power state, detecting a first user interaction via the touch-sensitive surface. The method also includes, in response to detecting the first user interaction, setting the one or more tactile output generators to a low-latency state; and, after setting the one or more tactile output generators to the low-latency state, detecting a second user interaction that is part of a same sequence of user interactions as the first user interaction. The method further includes, in response to detecting the second user interaction, generating a tactile output that corresponds to the second user interaction.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more tactile output generators. The method includes receiving a first request for a first user interface operation. The first user interface operation is a first type of change in a respective user interface element that is associated with a first tactile output. The method also includes, in response to receiving the first request: performing the first user interface operation and generating the first tactile output. The method further includes, after performing the first user interface operation, receiving a second request for a second user interface operation that is associated with a second tactile output; and, in response to receiving the second request, in accordance with a determination that the second request for the second user interface operation comprises a request for an instance of the first type of change in the user interface that is associated with the second tactile output: determining a time interval from a point in time corresponding to a most recent prior instance of the first type of change in the respective user interface element for which a tactile output was generated to a point in time corresponding to the first type of change in the respective user interface element requested by the second request; in accordance with a determination that the time interval is less than a predefined time period, performing the second user interface operation without generating the second tactile output; and, in accordance with a determination that the time interval is greater than the predefined time period, performing the second user interface operation and generating the second tactile output.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more tactile output generators. The method includes, at an application-independent module, receiving user interface information from an application. The user interface information corresponds to one or more displayed user interface elements with one or more dimensions defined by an application-specific module of the application. The method also includes receiving an input directed toward one or more of the displayed user interface elements; and, at the application-independent module, determining one or more tactile outputs to be generated based on a magnitude of the input and the one or more dimensions defined by the applications-specific module; and, using the one or more tactile output generators, generating the determined one or more tactile outputs.
In accordance with some embodiments, an electronic device includes a display unit configured to display one or more user interfaces; one or more input device units configured to receive inputs; one or more tactile output generator units configured to generate one or more tactile outputs; and a processing unit coupled with the display unit, the one or more input device units, and the one or more tactile output generator units. The processing unit is configured to enable display, on the display unit, of a user interface for a first software application. The user interface includes a plurality of elements to which user interaction models from a plurality of user interaction models provided by an application-independent module have been assigned, the plurality of elements including a first element to which a first user interaction model has been assigned, the plurality of elements having content provided by an application-specific module for the first software application. The first user interaction model defines how the user interface responds to inputs directed to the first element of the user interface. The processing unit is also configured to, while enabling display of the user interface, detect, via the one or more input device units, an input directed to the first element of the user interface; and, in response to detecting the input: update the user interface on the display unit based on characteristics of the input; in accordance with a determination that the input meets tactile output criteria specified by the first user interaction model, enable generation of a first tactile output corresponding to the input; and, in accordance with a determination that the input does not meet the tactile output criteria specified by the first user interaction model, forgo enabling generation of the first tactile output.
In accordance with some embodiments, an electronic device includes a display unit configured to display one or more user interfaces; a touch-sensitive surface unit configured to receive touch inputs; one or more tactile output generator units configured to generate one or more tactile outputs; and a processing unit coupled with the display unit, the touch-sensitive surface unit, and the one or more tactile output generator units. The processing unit is configured to: enable display, on the display unit, of a user interface; and detect an occurrence of a first condition that triggers a first user interface event that is associated with a tactile output. Generating the first user interface event includes enabling display of one or more changes to the user interface. The device will not be able to generate the tactile output associated with the first user interface event for a respective amount of time. The processing unit is also configured to, in response to detecting the occurrence of the first condition, in accordance with a determination that the first user interface event corresponds to a first user interface event category, enable generation of the tactile output that is associated with the first user interface event; delay generating the first user interface event for at least the respective amount of time; and, after delaying generating the first user interface event for at least the respective amount of time, enable display of the one or more changes to the user interface. The display of the one or more changes to the user interface is synchronized with the generation of the tactile output that is associated with the first user interface event.
In accordance with some embodiments, an electronic device includes a display unit configured to display one or more user interfaces; a touch-sensitive surface unit configured to receive touch inputs; one or more tactile output generator units configured to generate one or more tactile outputs; and a processing unit coupled with the display unit, the touch-sensitive surface unit, and the one or more tactile output generator units. The processing unit is configured to: while the one or more tactile output generator units are in a low-power state, receive an indication that a user interaction has started. A respective portion of the user interaction is associated with a tactile output. The low-power state is a state in which tactile outputs are generated with a first amount of latency. The processing unit is also configured to, in response to receiving the indication that the user interaction that is associated with the tactile output has started, in accordance with a determination that the indication meets tactile output generator preparation criteria, set the one or more tactile output generator units to a low-latency state at a first time. The low-latency state is a state in which the tactile outputs are generated with a second amount of latency that is lower than the first amount of latency. The processing unit is further configured to, after setting the one or more tactile output generator units to the low-latency state: in accordance with a determination that the user interaction has reached the respective portion of the user interaction that is associated with the tactile output before a predefined amount of time since the first time has elapsed and that the one or more tactile output generator units are still in the low-latency state, enable generation of the tactile output using the one or more tactile output generator units with the second amount of latency; and, in accordance with a determination that a tactile output has not been generated for at least the predefined amount of time since the first time, transition the one or more tactile output generator units from the low-latency state to the low-power state.
In accordance with some embodiments, an electronic device includes a display unit configured to display one or more user interfaces; a touch-sensitive surface unit configured to receive touch inputs; one or more tactile output generator units configured to generate one or more tactile outputs; and a processing unit coupled with the display unit, the one or more input device units, and the one or more tactile output generator units. The processing unit is configured to, while a first type of event is associated with a first tactile output and a second type of event that is distinct from the first type of event is associated with a second tactile output that is different from the first tactile output by an application-independent module: receive first information from a first application; and, in response to receiving the first information from the first application, enable generation of a response to the first information, including: in accordance with a determination that the first information corresponds to an application event of the first type, enable generation of the first tactile output using the one or more tactile output generator units; and, in accordance with a determination that the first information corresponds to an application event of the second type that is distinct from the first type, enable generation, using the one or more tactile output generator units, of the second tactile output that is different from the first tactile output. The processing unit is also configured to, after enabling generation of the response to the first information, receive second information from a second application that is distinct from the first application; and, in response to receiving the second information from the second application, enable generation of a response to the second information, including: in accordance with a determination that the second information corresponds to an application event of the first type, enable generation of the first tactile output using the one or more tactile output generator units; and, in accordance with a determination that the second information corresponds to an application event of the second type, enable generation of the second tactile output using the one or more tactile output generator units.
In accordance with some embodiments, an electronic device includes a display unit configured to display one or more user interfaces; a touch-sensitive surface unit configured to receive touch inputs; one or more tactile output generator units configured to generate one or more tactile outputs; and a processing unit coupled with the display unit, the touch-sensitive surface unit, and the one or more tactile output generator units. The processing unit is configured to receive, at an application-independent module, from an application-specific module that is associated with a first application, information about an input directed to a user interface of the first application. An operation performed in the user interface of the first application in response to detecting the input is associated with a tactile output pattern specified by the application-specific module. The information about the input includes information indicating a magnitude of the operation performed in the user interface in response to detecting the input. The processing unit is also configured to, in response to receiving the information about the input directed to the user interface of the first application, enable generation, via the one or more tactile output generator units, of a tactile output that corresponds to the operation performed in the user interface of the first application. The tactile output has the tactile output pattern specified by the application-specific module. The tactile output has an amplitude determined in accordance with the magnitude of the operation performed in the user interface of the first application in response to detecting the input.
In accordance with some embodiments, an electronic device includes a display unit configured to display one or more user interfaces; a touch-sensitive surface unit configured to receive touch inputs; one or more tactile output generator units configured to generate one or more tactile outputs; and a processing unit coupled with the display unit, the touch-sensitive surface unit, and the one or more tactile output generator units. The processing unit is configured to: enable display of a user interface on the display unit; while enabling display of the user interface on the display unit and while the one or more tactile output generator units are in a low-power state, detect a first user interaction via the touch-sensitive surface unit; in response to detecting the first user interaction, set the one or more tactile output generator units to a low-latency state; after setting the one or more tactile output generator units to the low-latency state, detect a second user interaction that is part of a same sequence of user interactions as the first user interaction; and, in response to detecting the second user interaction, enable generation of a tactile output that corresponds to the second user interaction.
In accordance with some embodiments, an electronic device includes a display unit configured to display one or more user interfaces; a touch-sensitive surface unit configured to receive touch inputs; one or more tactile output generator units configured to generate one or more tactile outputs; and a processing unit coupled with the display unit, the touch-sensitive surface unit, and the one or more tactile output generator units. The processing unit is configured to receive a first request for a first user interface operation. The first user interface operation is a first type of change in a respective user interface element that is associated with a first tactile output. The processing unit is also configured to, in response to receiving the first request: perform the first user interface operation and enable generation of the first tactile output; and, after performing the first user interface operation, receive a second request for a second user interface operation that is associated with a second tactile output. The processing unit is further configured to, in response to receiving the second request, in accordance with a determination that the second request for the second user interface operation comprises a request for an instance of the first type of change in the user interface that is associated with a second tactile output: determine a time interval from a point in time corresponding to a most recent prior instance of the first type of change in the respective user interface element for which a tactile output was generated to a point in time corresponding to the first type of change in the respective user interface element requested by the second request; in accordance with a determination that the time interval is less than a predefined time period, perform the second user interface operation without enabling generation of the second tactile output; and, in accordance with a determination that the time interval is greater than the predefined time period, perform the second user interface operation and enable generation of the second tactile output.
In accordance with some embodiments, an electronic device includes a display unit configured to display one or more user interfaces; a touch-sensitive surface unit configured to receive touch inputs; one or more tactile output generator units configured to generate one or more tactile outputs; and a processing unit coupled with the display unit, the touch-sensitive surface unit, and the one or more tactile output generator units. The processing unit is configured to receive, at an application-independent module, user interface information from an application. The user interface information corresponds to one or more displayed user interface elements with one or more dimensions defined by an application-specific module of the application. The processing unit is also configured to receive an input directed toward one or more of the displayed user interface elements; determine, at the application-independent module, one or more tactile outputs to be generated based on a magnitude of the input and the one or more dimensions defined by the applications-specific module; and enable generation of the determined one or more tactile outputs using the one or more tactile output generator units.
In accordance with some embodiments, an electronic device includes a display, a touch-sensitive surface, optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, 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, and optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, 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, optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, 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, and optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface; and means for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a display and a touch-sensitive surface, and optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, includes means for performing or causing performance of the operations of any of the methods described herein.
Thus, electronic devices with displays, touch-sensitive surfaces and optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface are provided with faster, more efficient methods and interfaces for providing tactile outputs, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for providing tactile outputs.
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.
Many electronic devices have graphical user interfaces that allow certain manipulations of displayed user interface objects in response to certain touch inputs. However, various software applications may be configured to respond in an inconsistent manner (e.g., providing different haptic feedback) to a same input, which makes it more challenging for a user to learn how to interact with different software applications and/or what particular haptic feedbacks indicate. The disclosed embodiments address these limitations and disadvantages by providing a common framework for providing haptic feedback (and/or tactile outputs). Because instructions for providing tactile outputs are provided in electronic devices (e.g., in an operating system), software applications can be developed faster and made smaller, thereby improving the efficiency in storing and executing such software applications on electronic devices. In addition, various software applications respond to a same input in a consistent manner (e.g., by providing a consistent haptic feedback) using the common framework, thereby improving user experience with such electronic devices. For battery-operated devices, the disclosed methods and devices conserve battery power and increase the time between battery charges. Furthermore, software applications can subscribe to different features of the common framework, thereby allowing the software applications to customize responses to inputs without losing the consistency and advanced features of the common framework.
Below,
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 and a touch-sensitive surface 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. 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) 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 or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface 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”), 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, and/or the duration of the tactile output.
When tactile outputs with different tactile output patterns are generated by a device (e.g., via one or more tactile output generators that move a moveable mass to generate tactile outputs), the tactile outputs may invoke different haptic sensations in a user holding or touching the device. 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, and amplitude of tactile outputs generated by the device. Thus, the waveform, frequency and amplitude can be adjusted to indicate to the user that 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
As shown in
As shown in
Although specific frequencies, amplitudes, and waveforms are represented in the sample tactile output patterns in
The examples shown above in Table 1 are intended to illustrate a range of circumstances in which tactile outputs can be generated for different inputs and events. Table 1 should not be taken as a requirement that a device respond to each of the listed inputs or events with the indicated tactile output. Rather, Table 1 is intended to illustrate how tactile outputs vary and/or are similar for different inputs and/or events (e.g., based on the tactile output pattern, frequency, gain, etc.). For example Table 1 shows how an “event success” tactile output varies from an “event failure” tactile output and how a retarget tactile output differs from an impact tactile output.
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 (HSDPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, 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” refers to 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 some embodiments, 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 some embodiments, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, 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.
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 (e.g., on touch-sensitive display system 112) 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 input criteria that are configured to be met even when the characteristic intensity of a contact does not satisfy a given intensity threshold. 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 configured to detect 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 (e.g., on touch-sensitive display system 112) based on the satisfaction of criteria that are independent of intensities of contacts included in the gesture. For example, a swipe gesture is detected based on an amount of movement of one or more contacts; a pinch gesture is detected based on movement of two or more contacts 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 gesture recognition criteria are configured to be met when a contact in a gesture has an intensity below a respective intensity threshold means that the gesture recognition criteria are capable of being satisfied even if the contact(s) in the gesture do not reach the respective intensity threshold. It should be understood, however, that this statement does not preclude the gesture recognition criteria from being satisfied in circumstances where one or more of the contacts in the gesture do reach or exceed the respective intensity threshold. For example, a tap gesture is configured to be detected if 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 configured to be detected if 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.
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 are configured to be met when a contact in a gesture has an intensity below a respective intensity threshold 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 are configured to be met when a gesture has an intensity below a respective intensity threshold—are in competition with second gesture recognition criteria for a second gesture—which are dependent on the gesture 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 are still configured to be met when a contact in the gesture has an intensity below the respective intensity 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 are configured to be met when an intensity of a contact remains below a respective intensity threshold 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 (e.g., instructions used by haptic feedback controller 161) to produce tactile outputs using tactile output generator(s) 167 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 146 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 a user interface element (e.g., an application icon or an affordance within an application) or a hardware input device (e.g., a home button). 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
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 146. 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 167 (e.g., any 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).
In some embodiments, applications (e.g., application 1 (136-1)) send information (e.g., information 272) related to user interactions with device 100 to application-independent software module 260, which processes the information and sends the processed information (e.g., information 274, which is distinct from information 272) to haptic feedback module 133. In some embodiments, applications correspond to Client App illustrated in Appendices A and B.
In some embodiments, application-independent software module 260 is distinct and separate from applications, as shown in
In some embodiments, applications use various functions and objects described in Appendices A and B to communicate with application-independent software module 260.
In some embodiments, user interaction models are predefined classes (e.g., the UIView class defining an area on a display and the interfaces for managing the content in that area). At run time, a view object is prepared (e.g., an instance of the UIView class is created) to handle the rendering of content in a corresponding area and also handle interactions with the content. In some embodiments, the UIView class includes one or more subclasses, such as a UIControl class configured for implementing visual elements that are used for specific actions, a UITableView class configured for displaying and editing hierarchical lists of information, a UIDatePicker class configured for displaying a wheel of time to allow a user to select dates and/or times, a UISlider class configured for selecting a single value from a continuous range of values, and a UIScrollView class configured for displaying content that is larger than a corresponding display area. In some embodiments, the UITableView class, the UIDatePicker class, the UISlider class, and the UIScrollView class are subclasses of the UIControl class.
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, device 100 includes the touch-screen display, menu button 204 (sometimes called home 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 intensity 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, an application (e.g., an application core of the application, such as application core 1 (270-1)) generates a user interface by populating a user interface element (e.g., a slider) identified in the user interaction models with content provided by the application core (e.g., application core 1 (270-1) provides a range of the slider element and locations and/or values of major and minor tick marks).
In some embodiments, the application sends the user interface to graphics module 132 for display.
In some embodiments, the application receives information representing user interactions with device 100 from contact/motion module 130. In some embodiments, the application relays the information representing user interactions with device 100 to an application-independent software module or an instance thereof (e.g., 260-1), and the application-independent software module send the information or a subset thereof to haptic feedback module 133 for generating tactile outputs. In some embodiments, the application also sends information identifying one or more dimensions of a selected user interface. In some embodiments, the information representing user interactions with device 100 includes a magnitude (e.g., a speed) and/or a location of a user input.
In some embodiments, haptic feedback module 133 receives the information representing user interactions with device 100 directly from contact/motion module 130 (e.g., without going through the application).
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
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 stylus input). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple finger contacts, or a combination of finger contacts and stylus inputs are used simultaneously.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact or a stylus contact) on the touch-sensitive surface, or to a 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 refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 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 intensity 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 light press intensity threshold ITL, 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 (milliseconds) 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).
Although only specific frequencies, amplitudes, and waveforms are represented in the sample tactile output patterns in
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, and one or more sensors to detect intensities of contacts with the touch-sensitive surface.
User interface 500 in
For example,
For example,
At T=t2, user input 521 has moved to a position that activates selection of keyboard option affordance 526. In accordance with user input 521 activating selection of keyboard option affordance 526, tactile output 528 is generated (e.g., MicroTap High (270 Hz), gain: 0.4). In addition, a current selection indication (e.g., shading) is displayed on keyboard option affordance 526 to indicate that keyboard option affordance 526 is the currently selected keyboard option affordance. Accordingly, the current selection indication is no longer displayed on keyboard option affordance 524. In some embodiments, upon ceasing to detect user input 521 while the current selection indication is displayed on keyboard option affordance 526, the keyboard interface corresponding to keyboard option affordance 526 becomes the currently displayed keyboard interface.
At T=t3, user input 521 has moved toward keyboard option 525 but has not reached a position that corresponds to (e.g., activates selection of) keyboard option affordance 525. Accordingly, the current selection indication continues to be displayed on keyboard option affordance 526.
At T=t4, user input 521 has moved to a position that activates selection of keyboard option affordance 525. In accordance with user input 521 activating selection of keyboard option affordance 525, tactile output 529 is generated. In some embodiments, a tactile output is generated in accordance with a user input activating selection of a respective menu item affordance (e.g., one of keyboard option affordances 524, 525, 526) in a menu (e.g., keyboard interface menu 523). In some embodiments, a tactile output is generated in accordance with a user input activating selection of a respective menu item affordance that is distinct from a previously selected menu item. In some embodiments, tactile outputs generated in accordance with a user input activating selection of respective menu item affordances in keyboard interface menu 523 are of a same type. For example, tactile output 529, generated at T=t4 in accordance with user input 521 activating selection of keyboard option affordance 525, is a same type of tactile output (e.g., MicroTap High (270 Hz), gain: 0.4) as tactile output 528, generated at T=t3 in accordance with user input 521 activating selection of keyboard option affordance 526.
In
In some embodiments, while list element 572 is selected, the second portion of user input 571 is detected. For example, the second portion of user input 571 includes continued contact followed by upward movement of the contact (e.g., upward movement following the initial contact or long press gesture). At time T=t2, user interface 570c illustrates that, in accordance with upward movement of user input 571 during the second portion of user input 571, selected list element 572 is moved upwards. For example, selected list element 572 moves upward towards a position of unselected list element 573 (e.g., “New York”). Accordingly, selected list element 572 is displayed over at least a portion of unselected list element 573.
At time T=t3, user interface 570d illustrates continued upward movement of user input 571, detected during the third portion of user input 571, from the position of user input 571 as shown in user interface 570c corresponding to time T=t2. In accordance with the continued upward movement of user input 571, selected list element 572 moves into a predetermined snap position corresponding to the previous position of unselected list element 573 (e.g., as shown in user interface 570c). In some embodiments, the predetermined snap position corresponding to the previous position of selected list element 572 (e.g., as shown in user interface 570a) becomes vacant. In accordance with selected list element 572 moving into the predetermined snap position corresponding to the previous position of unselected list element 573, unselected list element 573 moves downward into the predetermined snap position corresponding to the previous position of selected list element 572 (e.g., unselected list element 573 and selected list element 572 are displayed as having switched positions). In some embodiments, in conjunction with selected list element 572 moving into the predetermined snap position previously corresponding to unselected list element 573, device 100 generates tactile output 574d (e.g., MicroTap High (270 Hz) with a gain of 1.0).
At time T=t4, device 100 has ceased to detect user input 571 (e.g., device 100 has detected the fourth portion of user input 571, the fourth portion of user input 571 including liftoff of the contact) while selected list element 572 is at the predetermined snap position as shown in user interface 570d corresponding to time T=t3. Accordingly, list element 572 settles into and is displayed (e.g., as an unselected list element) in the position previously occupied by list element 573, while list element 573 is displayed in the position previously occupied by list element 572 (e.g., as shown in user interface 570a). Optionally, in some embodiments, in response to list element 572 settling into the list of clocks, device 100 generates tactile output 574e (e.g., MicroTap High (270 Hz) with a gain of 0.6) to indicate that list element 572 has been dropped.
In response to the further movement of the third portion of user input 577 as illustrated in
In some embodiments, while application icon 582 is selected, the second portion of user input 581 is detected. For example, the second portion of user input 581 includes continued contact followed by movement of the contact to the left toward “Stocks” application icon 583. At time T=t2, user interface 580c illustrates that, in accordance with the movement of user input 581 during the second portion of user input 581, application icon 582 moves to the left and passes over application icon 583. Accordingly, application icon 582 is displayed over at least a portion of application icon 583.
At time T=t3, user interface 580d illustrates continued movement of user input 581 toward the left. In accordance with the continued movement of user input 581, application icon 582 moves into a predetermined snap position corresponding to the previous position of unselected application icon 583 (e.g., as shown in user interface 580c). In some embodiments, the predetermined snap position corresponding to the previous position of unselected application icon 583 (e.g., as shown in user interface 580a) becomes vacant. Accordingly, in some embodiments, unselected application icon 583 moves to the right into the predetermined snap position vacated by application icon 583. In some embodiments, in conjunction with selected application icon 582 moving into the predetermined snap position previously occupied by unselected application icon 583, device 100 generates tactile output 584d (e.g., MicroTap High (270 Hz) with a gain of 1.0).
At time T=t4, device 100 has ceased to detect user input 581 (e.g., device 100 has detected the fourth portion of user input 581 including liftoff of the contact) while selected application icon 582 is at the predetermined snap position as shown in user interface 580d corresponding to time T=t3. Accordingly, application icon 582 settles into and is displayed (e.g., as an unselected application icon in the array) in the position previously occupied by application icon 583, while application icon 583 is displayed in the position previously occupied by application icon 582 (e.g., application icon 582 and application icon 583 are displayed in switched positions). Optionally, in some embodiments, in response to application icon 582 setting into the array, device 100 generates tactile output 584e (e.g., MicroTap High (270 Hz) with a gain of 0.6) to indicate that application icon 582 has been dropped.
At time T=t2, the characteristic intensity of user input 591 crosses light press threshold intensity ITL. In accordance with the characteristic intensity of user input 591 crossing light press threshold intensity ITL, user interface 590c illustrates display of a preview of information corresponding to e-mail 592 (e.g., a short preview of content of e-mail 592). In some embodiments, device 100 generates tactile output 594b (e.g., a discrete tap, such as a MicroTap Custom (200 Hz) with a gain of 1.0) when the characteristic intensity of user input 591 reaches light press threshold intensity ITL.
In some embodiments, the characteristic intensity of user input 591 continues to increase between t2 and t3 toward deep press threshold intensity ITD. In some embodiments, as the characteristic intensity of user input 591 approaches deep press threshold intensity, device 100 generates tactile output 594c (e.g., as a tactile indication of the detected increase in the characteristic intensity of user input 591. In some embodiments, device 100 gradually increases a characteristic of tactile output 594c (e.g., an amplitude of tactile output 594c increases from zero) as shown in tactile output graph 594.
At time T=t3, the characteristic intensity of user input 591 crosses deep press threshold intensity ITD. In accordance with the characteristic intensity of user input 591 crossing deep press threshold intensity ITD, user interface 590d illustrates display of e-mail 592 (e.g., the preview of content of e-mail 592 expands to a full screen display of e-mail 592). In some embodiments, device 100 generates tactile output 594d (e.g., a discrete tap, such as a FullTap Custom (150 Hz) with a gain of 1.0) when the characteristic intensity of user input 591 reaches deep press threshold ITD.
In some embodiments, display of one or more user interface changes associated with a user interface event (e.g., a user interface event that is independent of direct manipulation of the user interface in response to a touch input) is delayed such that the one or more user interface changes is displayed concurrently with generation of a tactile output corresponding to the user interface event.
For example,
In another example,
In yet another example,
In some embodiments, in accordance with latency associated with generating tactile outputs, tactile output generator 5121 generates tactile outputs after a period of time after a tactile output trigger is received. The period of time between receipt of a tactile output trigger and generation of a corresponding tactile output varies in accordance with a state of tactile output generator 5121. For example, as illustrated in
FIGS. 5AAA-5CCC illustrate example user interfaces and timing for generating tactile outputs in accordance with user interface events for different types of user interface events (e.g., success, failure, and warning events).
FIG. 5AAA illustrates an example of one or more tactile outputs generated for success events. FIG. 5AAA includes user interface 5130 for entering authentication credentials for connecting to a wireless network (e.g., “HomeWireless”), displayed at time T=t0. At time T=t1, in accordance with a determination that authentication of the password entered in user interface 5130 was successful, user interface 5131 is displayed (e.g., indicating successful connection to the requested wireless network “HomeWireless”) and tactile output 5132 corresponding to a success event is generated (e.g., FullTap Medium (200 Hz) with a gain of 0.7 followed by a MiniTap High (270 Hz) with a gain of 1.0).
FIG. 5BBB illustrates an example of one or more tactile outputs generated for failure events. FIG. 5BBB includes user interface 5130 for entering authentication credentials for connecting to a wireless network (e.g., “HomeWireless”), displayed at time T=t0. At time T=t1, in accordance with a determination that authentication of the password entered in user interface 5130 failed, user interface 5133 is displayed (e.g., indicating that an incorrect password was entered for the requested wireless network “HomeWireless”) and tactile output 5134 corresponding to a failure event is generated (e.g., MiniTap High (270 Hz) with a gain of 0.75-0.85, followed by a FullTap Medium (200 Hz) with a gain of 0.65, followed by a FullTap Low (150 Hz) with a gain of 0.75).
FIG. 5CCC illustrates an example of one or more tactile outputs generated for warning events. FIG. 5CCC includes user interface 5135 for composing an e-mail message, as described above with reference to
FIGS. 5DDD-5GGG illustrate an example user interface for generating tactile outputs in accordance with magnitudes of operations performed in the user interface in response to user input, in accordance with some embodiments. In particular, FIGS. 5DDD-5GGG illustrate tactile outputs generated during variable rate scrubbing, in accordance with movement of a user input across boundaries.
FIG. 5DDD illustrates user interface 5140 for a media content player that includes slider control 5141, including adjustable progress indicator 5142 that indicates a current position in the content being played on the device. In some embodiments, user interface 5140 includes a plurality of other media content player controls for controlling playback of content in the media content player. FIG. 5DDD illustrates user input 5143, initially detected at a location on touch screen 112 that corresponds to an initial position of progress indicator 5142 in slider control 5141. FIG. 5DDD also illustrates movement of user input 5143 away from its initial location (e.g., user input 5143 includes a drag gesture that includes an initial contact followed by movement of the contact) corresponding to slider control 5141. In some embodiments, boundaries 5144, 5145, and 5146 separate areas of user interface 5140 that correspond to different scrubbing rates for adjusting the position of progress indicator 5142 in slider control 5141. In some embodiments, boundaries 5144, 5145, and 5146 are not typically displayed to a user. In some embodiments, while user input 5143 is above boundary 5144, the position of progress indicator 5142 in slider control 5141 moves by the same amount as a horizontal component of movement of user input 5143 on touch screen 112 that includes movement parallel to the slider control (sometimes referred to as “full-speed scrubbing”). In some embodiments, while user input 5143 is between boundary 5144 and boundary 5145, the position of progress indicator 5142 in slider control 5141 moves by an amount that is a fraction (e.g., one-half or equivalently 50%) of the horizontal component of movement of user input 5143 on touch screen 112 that is parallel to slider control 5141 (sometimes referred to as “half-speed scrubbing”). In some embodiments, while user input 5143 is between boundary 5145 and boundary 5146, the position of progress indicator 5142 in slider control 5141 moves by an amount that is a smaller fraction (e.g., one-quarter or equivalently 25%) of the horizontal component of movement of user input 5143 on touch screen 112 that is parallel to slider control 5141 (sometimes referred to as “quarter-speed scrubbing”). In some embodiments, while user input 5143 is below boundary 5146, the position of progress indicator 5142 in slider control 5141 moves by an amount that is an even smaller fraction (e.g., one-eighth or equivalently 12.5%) of the horizontal component of movement of user input 5143 on touch screen 112 that is parallel to slider control 5141 (sometimes referred to as “fine-speed scrubbing”). It is noted that the fractional scrubbing rates used here (50%, 25%, and 12.5%) are merely examples, and that different scrubbing rates that progressively decrease as vertical distance between a user input and slider control 5141 increases may also be used.
In some embodiments, device 100 generates tactile outputs in accordance with user input 5143 crossing respective boundaries. In some embodiments, the tactile outputs are generated in accordance with a characteristic of user input 5143 that corresponds to an operation in user interface 5140. For example, the tactile outputs are generated in accordance with a velocity of user input 5143 when crossing a respective boundary that corresponds to a change in a scrubbing rate. In some embodiments, a stronger tactile output is generated when user input 5143 crosses a respective boundary with a high velocity. In some embodiments, a lighter tactile output is generated when user input 5143 crosses a respective boundary with a low velocity.
FIG. 5EEE illustrates movement of user input 5143 downward and toward the right with respect to its initial position (e.g., as shown in FIG. 5DDD), away from slider control 5141 and crossing boundary 5144. In accordance with user input 5143 crossing boundary 5144, device 100 generates tactile output 5148. In accordance with a velocity of the movement of user input 5143 being above a moderate velocity threshold VM and below a high velocity threshold VH, as indicated by velocity of contact meter 5147, tactile output 5148 is generated as a moderate tactile output (e.g., MicroTap Medium (150 Hz) with a gain of 0.4).
FIG. 5FFF illustrates further movement of user input 5143 downward and toward the right with respect to its position as shown in FIG. 5EEE, further away from slider control 5141 and crossing boundary 5145. In accordance with user input 5143 crossing boundary 5145, device 100 generates tactile output 5149. In accordance with the velocity of the movement of user input 5143 being above a high velocity threshold VF, as indicated by velocity of contact meter 5147, tactile output 5149 is generated as a strong tactile output (e.g., MicroTap Medium (150 Hz) with a gain of 0.7).
FIG. 5GGG illustrates even further movement of user input 5143 downward and toward the right with respect to its position as shown in FIG. 5FFF, further away from slider control 5141 and crossing boundary 5146. In accordance with user input 5143 crossing boundary 5146, device 100 generates tactile output 5150. In accordance with the velocity of the movement of user input 5143 being below the moderate velocity threshold VM and above a movement detection threshold V0 (e.g., zero velocity), as indicated by velocity of contact meter 5147, tactile output 5150 is generated as a light tactile output (e.g., MicroTap Medium (150 Hz) with a gain of 0.1).
FIGS. 5HHH-5III illustrate timing diagrams for generating tactile outputs in accordance with detecting a continuous user interaction and in accordance with a state of one or more tactile output generates used to generate the tactile outputs. In particular, FIG. 5HHH illustrates slider 5160 having a position indicator 5161 in an initial position at time T=t0. A tactile output generator for generating one or more tactile outputs in accordance with position indicator 5161 of slider 5160 crossing a respective marker on slider 5160 is initially in a low-power state, as shown in generator state graph 5164. In accordance with a first portion of a user interaction that moves position indicator 5161 to the position shown at time T=t1, position indicator 5161 approaches but does not cross marker 5162. The tactile output generator remains in the low-power state (e.g., the state of the tactile output generator is maintained or not changed). At time T=t2, in accordance with a second portion of the user interaction, position indicator 5161 crosses marker 5162. Accordingly, generation of a tactile output is initiated at time t2, as shown in tactile output graph 5165. In some embodiments, in accordance with latency associated with the low-power state, tactile output 5163 is generated at time t=t4, after time period ΔTA (e.g., 200 ms) after the tactile output trigger is received at time t2. As shown in FIG. 5HHH, by time t4 (at which tactile output 5163 is generated), position indicator 5161 has moved past marker 5162 in accordance with continued movement of the user input.
In some embodiments, the state of the tactile output generator is changed in anticipation of generating a tactile output, such as in accordance with movement of a user input that approaches a threshold. For example, FIG. 5III illustrates slider 5160 having a position indicator 5161 in an initial position at time T=t0. A tactile output generator for generating one or more tactile outputs in accordance with position indicator 5161 of slider 5160 crossing a respective marker on slider 5160 is initially in a low-power state, as shown in generator state graph 5166. In accordance with a first portion of a user interaction that moves position indicator 5161 to the position shown at time T=t1, position indicator 5161 approaches but does not cross marker 5162. In some embodiments, in response to position indicator 5161 approaching marker 5162 (e.g., in anticipation of position indicator 5161 crossing marker 5162, for which a tactile output will be generated), the state of the tactile output generator is changed from the low-power state to the low-latency state (or alternatively, in some embodiments, the active state). At time T=t2, in accordance with a second portion of the user interaction, position indicator 5161 crosses marker 5162. Accordingly, generation of a tactile output is initiated at time t2, as shown in tactile output graph 5167. In some embodiments, in accordance with latency associated with the low-latency state, tactile output 5168 is generated at time t=t3, after time period ΔTB (e.g., 100-150 ms) after the tactile output trigger is received at time t2. In some embodiments, time period ΔTB associated with the low-latency state is less than time period ΔTA associated with the low-power state. As shown in FIG. 5III, the time t3 at which tactile output 5168 is generated occurs before time t4 at which tactile output 5163 is generated as shown in FIG. 5HHH. In some embodiments, in accordance with changing the state of the tactile output generator, tactile outputs are generated with lower latency. In addition, in FIG. 5III, position indicator 5161 has moved past marker 5162 in accordance with continued movement of the user input to a lesser extent than in FIG. 5HHH.
FIG. 5JJJ illustrates generation of a sequence of tactile outputs by an electronic device (e.g., portable multifunction device 100,
Similarly, at time t3, a third instance of the first type of tactile output is triggered, as shown in tactile output graph 5170a. In response, the device generates tactile output 5172 at a point in time following the trigger at t3 and before a subsequent trigger at t4 (e.g., in accordance with a determination that most recently generated tactile output 5171 of the first type of tactile output is at least the predetermined time from anticipated generation of tactile output 5172). At time t4, a fourth instance of the first type of tactile output is triggered, as shown in tactile output graph 5170a. In addition, at time t4, a first instance of a second type of tactile output is triggered, as shown in tactile output graph 5170b. In some embodiments, the device determines that anticipated generation of a tactile output of the first type in response to the trigger at t4 is within the predetermined time from generation of tactile output 5172 (e.g., the most recent instance of the first type of tactile output that was generated, determined with respect to the trigger for the first type of tactile output at t4). Accordingly, the device forgoes generation of the tactile output in response to the trigger for the first type of tactile output at t4. In some embodiments, the device generates tactile output 5176 in response to the trigger for the second type of tactile output at t4 (e.g., without regard to timing of tactile outputs of the first type). In some embodiments, the device generates tactile output 5176 in accordance with a determination that generation of tactile output 5176 will be at least a predetermined time from generation of a most recent instance of the second type of tactile output.
At time t5, a fifth instance of the first type of tactile output is triggered, as shown in tactile output graph 5170a. In response, the device generates tactile output 5173 at a point in time following the trigger at t5 and before a subsequent trigger at t6 (e.g., in accordance with a determination that most recently generated tactile output 5172 of the first type of tactile output is at least the predetermined time from anticipated generation of tactile output 5173). At time t6, a sixth instance of the first type of tactile output is triggered, as shown in tactile output graph 5170a. In some embodiments, the device determines that anticipated generation of a tactile output in response to the trigger at t6 will be at least the predetermined time from generation of tactile output 5173 (e.g., the most recent instance of the first type of tactile output that was generated). Accordingly, the device generates tactile output 5174 in response to the trigger at t6. Subsequently, at time t7, a seventh instance of the first type of tactile output is triggered. In some embodiments, the device determines that anticipated generation of a tactile output in response to the trigger at t7 is within a predetermined time from generation of tactile output 5174 (e.g., a most recent instance of the first type of tactile output that was generated). Accordingly, the device forgoes generation of the tactile output in response to the trigger at t7.
At time t8, an eighth instance of the first type of tactile output is triggered, as shown in tactile output graph 5170a. In addition, at time t8, a second instance of the second type of tactile output is triggered, as shown in tactile output graph 5170b. In some embodiments, the device determines that anticipated generation of a tactile output of the first type in response to the trigger at t8 is at least the predetermined time from generation of tactile output 5174 (e.g., the most recent instance of the first type of tactile output that was generated, determined with respect to the trigger for the first type of tactile output at t8). Accordingly, the device generates tactile output 5175 in response to the trigger for the first type of tactile output at t8. In addition, the device generates tactile output 5177 in response to the trigger for the second type of tactile output at t8 (e.g., without regard to timing of tactile outputs of the first type). In some embodiments, the device generates tactile output 5177 in accordance with a determination that anticipated generation of tactile output 5177 is at least a predetermined time from generation of a most recent instance of the second type of tactile output (e.g., tactile output 5176).
FIG. 5KKK illustrates a conceptual flow diagram of method 5180 for controlling a state of one or more tactile output generators (e.g., tactile output generator(s) 167,
In some embodiments, the application-independent module waits (5182) for input from an application-specific module (e.g., a trigger for generating a tactile output, such as a user input that is associated with a tactile output). In some embodiments, while the application-independent module is waiting for input, the tactile output generators are in an inactive state.
In some embodiments, the application-independent module receives (5184) an input from the application-specific module. In response to receiving the input from the application-specific module, the application-independent module determines (5186) whether to prepare one or more tactile output generators for generating tactile outputs (e.g., whether the input meets tactile output generation criteria).
In accordance with a determination that one or more tactile output generators should not be prepared (5186—No), the application-independent module returns to the wait state (5182) to wait for an additional input, and the tactile output generators are maintained in the inactive state.
In accordance with a determination that the one or more tactile output generators should be prepared (5186—Yes) (e.g., in anticipation of generating tactile outputs), the application-independent module determines (5188) whether to prepare the tactile output generators by setting the tactile output generators to a pre-warm state (e.g., associated with a lower latency than the inactive state) or an active state (e.g., associated with a lower latency than both the inactive state and the pre-warm state).
In accordance with a determination that the tactile outputs should be set to the pre-warm state (5188—Pre-Warm), the application-independent module prepares the tactile output generators by setting (5190) the tactile output generators to the pre-warm state. In accordance with a determination that the tactile outputs should be set to the active state (5188—Active), the application-independent module prepares the tactile output generators by setting (5192) the tactile output generators to the active state.
Next, in some embodiments, the application-independent module determines (5194) whether to return the tactile output generators from the pre-warm or active state to the inactive state (e.g., whether to exit the respective preparation state). In accordance with a determination to exit the preparation state (5194—Yes) (e.g., the electronic device is in a battery conservation mode of operation, or a predetermined timeout period has elapsed during which no tactile outputs were generated), the application-independent module returns to the wait state (5182). In accordance with a determination not to exit the preparation state (5194—No) (e.g., the predetermined timeout period has not elapsed since preparation of the tactile output generators was requested, or the predetermined time period has not elapsed since generation of a most recent prior tactile output), the application-independent module maintains the respective preparation state of the tactile output generators (e.g., the pre-warm state or the active state).
As described below, method 600 provides an enhanced way to provide tactile outputs using an application-independent software module. Providing tactile outputs using application-independent software based on information from application software provides common user interface framework that provides consistent user experience when various software applications are used. Providing a common user interface frame work to the user enhances the usability of such software applications and the device executing such software applications. In turn, this 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 and/or unintended operations when operating/interacting with the device). In addition, the method reduces the size of software applications and makes execution of such software applications faster. For battery-operated electronic devices, enabling a user to use software applications faster and more efficiently conserves power and increases the time between battery charges.
In some embodiments, the device stores (e.g., in memory) application software (e.g., a first software application, such as application 1 (136-1) in
The device displays (602), on the display, a user interface for a first software application (e.g., the user interface for a settings application shown in
In some embodiments, the device assigns (606) the first user interaction model to the first element using a predefined application programming interface (API). For example, the device assigns a particular user interaction model to the first element using an API for the application-independent software module.
The first user interaction model defines (608) how the user interface responds to inputs directed to the first element of the user interface. For example, the first user interaction model defines whether or not to generate a tactile output and/or a condition for generating the tactile output. In some embodiments, the first user interaction model also defines how the first element is visually updated in response to a user input (e.g., moving a slider thumb, flipping on or off a switch, etc.).
While displaying the user interface, the device detects (610), via the one or more input devices, an input directed to the first element of the user interface (e.g., input 509 directed to slider thumb 505 in
In response to detecting the input (612), the device updates (614) the user interface on the display based on characteristics of the input (e.g., magnitude of movement, direction of movement, start location, stop location, magnitude of intensity, rate of change of intensity). For example, a position of slider thumb 505 changes in response to a change to input 509, as shown in
In some embodiments, the device updates (616) the user interface on the display based on characteristics of the input and the first user interaction model.
Also in response to detecting the input (612), and in accordance with a determination that the input meets tactile output criteria specified by the first user interaction model, the device generates (618) a first tactile output corresponding to the input.
In some embodiments, the first element includes (620) a slider object (e.g., UISlider) generated at least in part based on information provided by the application-specific module for the first software application, and the first user interaction model specifies generating tactile outputs (e.g., the first tactile output) in accordance with user manipulation of the slider object with touch inputs.
In some embodiments, the device generates (622) a predefined modulation selection tactile output in response to a touch input that selects a modulation type for the slider object. For example, in
In some embodiments, the first user interaction model specifies (624) generating the first tactile output in accordance with a modulation type of the slider object and a parameter of the first software application modulated in accordance with user manipulation of the slider object with touch inputs. For example, as shown in
In some embodiments, the first user interaction model specifies (626) generating a distinct tactile output in accordance with a moveable portion of the slider object reaching an end position (e.g., in
In some embodiments, the first element includes (628) a switch object (e.g., UISwitch) generated at least in part based on information provided by the application-specific module for the first software application, and the first user interaction model specifies generating the first tactile output when the input corresponds to an action that changes a state of the switch object (e.g., the first input causes the switch to be flipped from a prior state to a new state different from the prior state, such as from off to on or vice versa as shown in
In some embodiments, the first element includes (630) a value selection object (e.g., using a UIPickerView class or a UIDatePicker class described in Appendix B or their instances) generated at least in part based on information provided by the application-specific module for the first software application, and the first user interaction model specifies generating the first tactile output when the input corresponds to an action that changes a value selected using the value selection object. For example, if the value selection object corresponds to a scrollable wheel or list having a sequence of different values, the device generates a sequence of tactile outputs as the first input causes the value selection objection to scroll through the sequence of different values (e.g., the wheel of time shown in
In some embodiments, the first element includes content that is refreshed (632) in response to a pull down gesture reaching a refresh threshold (e.g., using a UIRefreshControl class described in Appendix B or its instance). The first user interaction model specifies generating a predefined impact tactile output in accordance with a determination that the input corresponds to a pull down gesture reaching the refresh threshold (e.g., content is refreshed in response to a pull down gesture reaching a refresh threshold as shown in
In some embodiments, the first element includes (634) a region or object (e.g., using a UIZoomEdgeFeedbackGenerator class or a UIScrollView class described in Appendix B or their instances), the size of which changes in response to the input comprising a zoom gesture. The first user interaction model specifies generating a predefined size limit tactile output in accordance with a determination that the size of the region or object has reached a predefined limit (e.g., in accordance with a determination that the size of the region or object, or equivalently a zoom scaling factor, has reached a predefined limit). For example, the predefined size limit tactile output is generated in accordance with a determination that the size of the displayed web page has reached a predefined limit in response to a depinch gesture, as shown in
In some embodiments, the first element includes (636) a table (e.g., using a UITableView class described in Appendix B or its instance), having cells organized in rows and columns, generated at least in part based on information provided by the application-specific module for the first software application (e.g., a calendar application provides dates and times of interest and/or calendar entries for the calendar view illustrated in
In some embodiments, the first element includes (638) a table (e.g., using a UITableView class described in Appendix B or its instance), having cells organized in rows and columns, generated at least in part based on information provided by the application-specific module for the first software application. The first user interaction model specifies generating the first tactile output when two or more rows of the cells are reordered in response to the input. For example, a tactile output is generated when two or more entries in a list are reordered as shown in
In some embodiments, the input causes (640) the first software application to select an item, in a collection of distinct items (e.g., using a UICollectionView class described in Appendix B or its instance), to be moved to a predefined position within the first element, and the first user interaction model specifies generating the first tactile output in conjunction with the selected item being moved to the predefined position within the first element (e.g., a tactile output is generated when application icon 582 is moved to a predefined position, namely a position for an adjacent application icon 583 as shown in
In some embodiments, the first user interaction model specifies (642) generating the first tactile output when the input or an object manipulated in accordance with the input approaches a next predefined state (e.g., a force-press gesture), and generating a second tactile output, distinct from the first tactile output, when the input or an object manipulated in accordance with the input reaches the next predefined state (e.g., in
In accordance with a determination that the input does not meet the tactile output criteria specified by the first user interaction model, the device forgoes (644) generation of the first tactile output (e.g., as shown in
In some embodiments, the plurality of elements includes (646) a second element to which a second user interaction model from the plurality of user interaction models provided by the application-independent module has been assigned. While displaying the user interface, the device detects, via the one or more input devices, a second input directed to the second element of the user interface; and, in response to detecting the second input directed to the second element of the user interface: updates the user interface on the display based on characteristics of the detected second input; in accordance with a determination that the second input meets tactile output criteria specified by the second user interaction model, generates a second tactile output corresponding to the second input (e.g., a tap gesture or a horizontal swipe gesture on switch object 502 flips a state of switch object 502 and initiates generation of the second tactile output indicating that the state of switch object 502 has been flipped); and, in accordance with a determination that the second input does not meet the tactile output criteria specified by the second user interaction model, forgoes generation of the second tactile output (e.g., a vertical swipe gesture on switch object 502 does not flip the state of switch object 502 and the second tactile output is not generated).
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. For example, in accordance with some embodiments, the device displays, on the display, a user interface for a first software application. The user interface is generated by populating a first user interaction template from a plurality of user interaction templates provided by an application-independent module with content provided by an application-specific module for the first software application. The first user interaction template defines how the user interface responds to inputs directed to the user interface. While displaying the user interface, the device detects, via the one or more input devices, an input directed to the user interface. In response to detecting the input, the device updates the user interface on the display based on characteristics of the detected input (e.g., magnitude of movement, direction of movement, start location, stop location, magnitude of intensity, rate of change of intensity) and the first user interaction template; in accordance with a determination that the input meets tactile output criteria specified by the first user interaction template, generates a first tactile output corresponding to the input; and, in accordance with a determination that the input does not meet the tactile output criteria specified by the first user interaction template, forgoes generation of the first tactile output.
The operations in the information processing methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to
In accordance with some embodiments,
As shown in
In some embodiments, processing unit 708 is configured to enable display (e.g., using display enabling unit 702), on display unit 702, of a user interface for a first software application, wherein the user interface includes a plurality of elements to which user interaction models from a plurality of user interaction models provided by an application-independent module have been assigned (e.g., using assigning unit 716), the plurality of elements include a first element to which a first user interaction model has been assigned, and the plurality of elements have content provided by an application-specific module for the first software application. In some embodiments, the first user interaction model defines how the user interface responds to inputs directed to the first element of the user interface. While enabling display of the user interface, processing unit 708 is configured to detect (e.g., using detecting unit 712), via input device unit(s) 704, an input directed to the first element of the user interface. In response to detecting the input, processing unit 708 updates (e.g., using display enabling unit 710) the user interface on the display unit based on characteristics of the detected input. In accordance with a determination (e.g., made using determining unit 718) that the input meets tactile output criteria specified by the first user interaction model, processing unit 708 enables generation of a first tactile output corresponding to the input (e.g., using tactile output enabling unit 714). In accordance with a determination (e.g., made using determining unit 718) that the input does not meet the tactile output criteria specified by the first user interaction model, processing unit 708 forgoes enabling generation of the first tactile output (e.g., using tactile output enabling unit 714).
In some embodiments, processing unit 708 updates (e.g., using display enabling unit 710) the user interface on display unit 702 based on characteristics of the detected input and the first user interaction model. In some embodiments, processing unit 708 assigns (e.g., using assigning unit 716) the first user interaction model to the first element using a predefined application programming interface (API).
In some embodiments, the plurality of elements includes a second element to which a second user interaction model from the plurality of user interaction models provided by the application-independent module has been assigned (e.g., using assigning unit 716), and while displaying the user interface, processing unit 708 detects (e.g., using detecting unit 712), via the one or more input device units 704, a second input directed to the second element of the user interface. In response to detecting the second input directed to the second element of the user interface, processing unit 708 updates (e.g., using display enabling unit 710) the user interface on the display unit based on characteristics of the detected second input. In accordance with a determination (e.g., made using determining unit 718) that the second input meets tactile output criteria specified by the second user interaction model, processing unit 708 enables (e.g., using tactile output enabling unit 714) generation of a second tactile output corresponding to the second input, and in accordance with a determination (e.g., made using determining unit 718) that the second input does not meet the tactile output criteria specified by the second user interaction model, processing unit 708 forgoes enabling generation of the second tactile output.
In some embodiments, the first element includes a slider object generated at least in part based on information provided by the application-specific module for the first software application, and the first user interaction model specifies generating tactile outputs (e.g., using tactile output enabling unit 714) in accordance with user manipulation of the slider object with touch inputs. In some embodiments, processing unit 708 is further configured to enable generation of a predefined modulation selection tactile output (e.g., using tactile output enabling unit 714) in response to a touch input that selects a modulation type for the slider object.
In some embodiments, the first user interaction model specifies generating the first tactile output (e.g., using tactile output enabling unit 714) in accordance with a modulation type of the slider object and a parameter of the first software application modulated in accordance with user manipulation of the slider object with touch inputs.
In some embodiments, the first user interaction model specifies generating a distinct tactile output (e.g., using tactile output enabling unit 714) in accordance with a moveable portion of the slider object reaching an end position.
In some embodiments, the first element includes a switch object generated at least in part based on information provided by the application-specific module for the first software application, and the first user interaction model specifies generating the first tactile output (e.g., using tactile output enabling unit 714) when the first input corresponds to an action that changes a state of the switch object.
In some embodiments, the first element includes a value selection object generated at least in part based on information provided by the application-specific module for the first software application, and the first user interaction model specifies generating the first tactile output (e.g., using tactile output enabling unit 714) when the first input corresponds to an action that changes a value selected using the value selection object.
In some embodiments, the first element includes content that is refreshed in response to a pull down gesture reaching a refresh threshold, and the first user interaction model specifies generating a predefined impact tactile output (e.g., using tactile output enabling unit 714) in accordance with a determination (e.g., made using determining unit 718) that the first input corresponds to a pull down gesture reaching the refresh threshold.
In some embodiments, the first element includes a region or object, the size of which changes in response to the first input comprising a zoom gesture, and the first user interaction model specifies generating a predefined size limit tactile output (e.g., using tactile output enabling unit 714) in accordance with a determination (e.g., made using determining unit 718) that the size of the region or object has reached a predefined limit.
In some embodiments, the first element includes a table, having cells organized in rows and columns, generated at least in part based on information provided by the application-specific module for the first software application, and the first user interaction model specifies generating the first tactile output (e.g., using tactile output enabling unit 714) when the first input moves from any cell in the table to any other cell in the table, or moves from outside the table to a cell inside the table.
In some embodiments, the first element includes a table, having cells organized in rows and columns, generated at least in part based on information provided by the application-specific module for the first software application, and the first user interaction model specifies generating the first tactile output (e.g., using tactile output enabling unit 714) when two or more rows of the cells are reordered in response to the first input.
In some embodiments, the first input causes the first software application to select an item, in a collection of distinct items, to be moved to a predefined position within the first element, and the first user interaction model specifies generating the first tactile output (e.g., using tactile output enabling unit 714) in conjunction with the selected item being moved to the predefined position within the first element.
In some embodiments, the first user interaction model specifies generating (e.g., using tactile output enabling unit 714) the first tactile output when the first input or an object manipulated in accordance with the first input approaches a next predefined state, and generating a second tactile output, distinct from the first tactile output, when the first input or an object manipulated in accordance with the first input reaches the next predefined state.
The operations described above with reference to
As described below, method 800 provides an intuitive way to provide tactile outputs in conjunction with user interface events. Providing tactile outputs takes longer than updating a user interface. Thus, user interface events (e.g., time-flexible user interface events) are delayed so that the delayed user interface events are synchronized with generation of tactile outputs. Synchronizing generation of tactile outputs and user interface updates provides intuitive user interfaces. On the other hand, for time-critical user interface events, user interface events are not delayed, which maintains the responsiveness of the device for such time-critical user interface events. The method reduces the number, extent, and/or nature of the inputs from a user when interacting with user interfaces, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to interact with user interfaces faster and more efficiently conserves power and increases the time between battery charges.
The device displays (802), on the display, a user interface (e.g., user interface 5105 as illustrated for T=t0 in
The device detects (804) an occurrence of a first condition (e.g., a user input, a scheduled event such as an alarm or a timer, or an externally triggered event such as an incoming notification) that triggers a first user interface event that is associated with a tactile output (e.g., receiving a calendar event invitation as illustrated for T=t1 in
In some embodiments, the occurrence of the first condition includes (808) detected movement of the electronic device that meets predefined input pattern criteria (e.g., a pattern of shaking the device back and forth as illustrated in
The device will not be able to generate (810) the tactile output associated with the first user interface event for a respective amount of time (e.g., due to other tactile outputs being generated and/or the tactile output generators not being ready to generate the tactile output because the tactile output generators are in a low-power state). In some embodiments, the device is not configured to generate the tactile output associated with the first user interface event for the respective amount of time (e.g., it takes at least the respective amount of time, such as Tdelay illustrated in
In response to detecting the occurrence of the first condition, in accordance with a determination that the first user interface event corresponds to a first user interface event category (812) (e.g., the first user interface event is not in response to a user input such as an alert or other notification that is not direct manipulation of the user interface in response to touch input), the device delays (814) generating the first user interface event for at least the respective amount of time (e.g., in
In some embodiments, the device, when the respective amount of time is a first amount of time, delays (816) displaying the one or more changes to the user interface for the first amount of time, and when the respective amount of time is a second amount of time, delays displaying the one or more changes to the user interface for the second amount of time (e.g., the device delays displaying the one or more changes to the user interface based on the time it takes to generate a tactile output).
In some embodiments, the determination that the first user interface event corresponds to the first user interface event category includes (818) a determination that the first user interface event is a notification event that does not correspond to a user input currently detected on the touch-sensitive surface (e.g., receiving a calendar event invitation as illustrated for T=t1 in
In some embodiments, the determination that the first user interface event corresponds to the first user interface event category includes (820) a determination that the first user interface event is a notification event initiated in accordance with receiving electronically delivered information from an information source external to the electronic device (e.g., receiving a calendar event invitation as illustrated for T=t1 in
In some embodiments, the determination that the first user interface event corresponds to the first user interface event category includes (822) a determination that the first user interface event is a notification event initiated in accordance with receiving electronically delivered information from an application executed by the electronic device (e.g., receiving a calendar event invitation as illustrated for T=t1 in
In some embodiments, the determination that the first user interface event corresponds to the first user interface event category includes (824) a determination that the first user interface event is a notification event initiated in accordance with completion of a transaction initiated by a user of the electronic device (e.g., transmission of payment credentials via a short range wireless communication signal to a payment terminal such as an NFC payment, successful authorization of a payment via a biometric sensor such as a fingerprint sensor, or receiving authorization of a payment by a remote payment server as shown in
In some embodiments, the determination that the first user interface event corresponds to the first user interface event category includes (826) a determination that the first user interface event is provided to an application programming interface (API) with a value indicating that the one or more changes to the user interface can be delayed until the device is ready to generate the tactile output (e.g., the first user interface event is provided from an application to the application programming interface (and to application-independent software module 260 illustrated in
After delaying generating the first user interface event for at least the respective amount of time, the device displays (828) the one or more changes to the user interface and generating the tactile output that is associated with the first user interface event. The display of the one or more changes to the user interface is synchronized (830) with the generation of the tactile output that is associated with the first user interface event (e.g., so that the one or more changes to the user interface are displayed with the generation of the first tactile output as shown in
In some embodiments, in response to detecting the occurrence of the first condition, in accordance with a determination that the first user interface event corresponds to a second user interface event category (e.g., the first user interface event is in response to a user input, such as changes to the user interface that correspond to direct manipulation of the user interface in response to touch input), the device displays (832) the one or more changes to the user interface before the respective amount of time has elapsed and generates the tactile output that is associated with the one or more changes in the user interface after the respective amount of time has elapsed (e.g., in
In some embodiments, the first user interface event category includes (834) events where the respective amount of time for the one or more changes to the user interface is flexible (e.g., user interface events that are independent of immediately preceding user inputs). The second user interface event category includes events where the respective amount of time for the one or more changes to the user interface is inflexible (e.g., user interface events initiated by user inputs).
In some embodiments, the first user interface event category includes (836) events where the one or more changes to the user interface do not simulate direct manipulation of the user interface by user inputs (e.g., receiving a calendar event invitation as illustrated for T=t1 in
In some embodiments, the device detects (838) a user input on the touch-sensitive surface that triggers a second user interface event that is associated with a tactile output (e.g., user input 571 in
It should be understood that the particular order in which the operations in
The operations in the information processing methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to
In accordance with some embodiments,
As shown in
In some embodiments, processing unit 908 is configured to enable display (e.g., using display enabling unit 910), on display unit 902, of a user interface. Processing unit 908 detects (e.g., using detecting unit 912) an occurrence of a first condition that triggers a first user interface event that is associated with a tactile output, wherein generating the first user interface event includes enabling display (e.g., using display enabling unit 910) of one or more changes to the user interface. In some embodiments, the device (e.g., device 900) will not be able to generate the tactile output (e.g., using tactile output generator units 906) associated with the first user interface event for a respective amount of time, and in response to detecting (e.g., using detecting unit 912) the occurrence of the first condition, in accordance with a determination (e.g., made using determining unit 918) that the first user interface event corresponds to a first user interface event category, processing unit 908 enables generation (e.g., using tactile output enabling unit 916) and delays (e.g., using delay unit 914) generation of the first user interface event for at least the respective amount of time. After delaying (e.g., using delay unit 914) generation of the first user interface event for at least the respective amount of time, processing unit 908 enables display (e.g., using display enabling unit 910) of the one or more changes to the user interface, wherein the display of the one or more changes to the user interface is synchronized with the generation of the tactile output that is associated with the first user interface event.
In some embodiments, processing unit 908 is further configured to, when the respective amount of time is a first amount of time, delay (e.g., using delay unit 914) displaying the one or more changes to the user interface for the first amount of time, and when the respective amount of time is a second amount of time, delay (e.g., using delay unit 914) displaying the one or more changes to the user interface for the second amount of time.
In some embodiments, processing unit 908 is configured to, in response to detecting the occurrence of the first condition, in accordance with a determination (e.g., made using determining unit 918) that the first user interface event corresponds to a second user interface event category, enable display of the one or more changes to the user interface (e.g., using display enabling unit 910) before the respective amount of time has elapsed, wherein the tactile output (e.g., using tactile feedback unit 918) that is associated with the one or more changes in the user interface is generated after the respective amount of time has elapsed.
In some embodiments, the first user interface event category includes events where the timing of the one or more changes to the user interface is flexible, and the second user interface event category includes events where the timing of the one or more changes to the user interface is inflexible.
In some embodiments, the first user interface event category includes events where the one or more changes to the user interface do not simulate direct manipulation of the user interface by user inputs, and the second user interface event category includes events where the one or more changes to the user interface simulate direct manipulation of the user interface by user inputs.
In some embodiments, processing unit 908 is configured to detects a user input on touch-sensitive surface unit 904 that triggers a second user interface event that is associated with a tactile output, wherein generating the second user interface event includes enabling display (e.g., using display enabling unit 910) of one or more changes to the user interface. In response to detecting the user input on touch-sensitive surface unit 904, processing unit 908 is configured to enable display (e.g., using display enabling unit 910) of the one or more changes to the user interface for the second user interface event and enable generation of the tactile output (e.g., using tactile output enabling unit 916) that is associated with the second user interface event, wherein a first time interval between the display of the one or more changes to the user interface for the first user interface event and the generation of the tactile output that is associated with the first user interface event is less than a second time interval between the display of the one or more changes to the user interface for the second user interface event and the generation of the tactile output that is associated with the second user interface event.
In some embodiments, the occurrence of the first condition includes detected movement of electronic device 900 that meets predefined input pattern criteria and the one or more changes to the user interface include undoing a previously performed operation.
In some embodiments, the determination that the first user interface event corresponds to the first user interface event category includes a determination (e.g., made using determining unit 918) that the first user interface event is a notification event that does not correspond to a user input currently detected on touch-sensitive surface unit 904.
In some embodiments, the determination that the first user interface event corresponds to the first user interface event category includes a determination (e.g., made using determining unit 918) that the first user interface event is a notification event initiated in accordance with receiving electronically delivered information from an information source external to electronic device 900.
In some embodiments, the determination that the first user interface event corresponds to the first user interface event category includes a determination (e.g., made using determining unit 918) that the first user interface event is a notification event initiated in accordance with receiving electronically delivered information from an application executed by electronic device 900 and independent of any user input on touch-sensitive surface unit 904 that is detected at the same time as, or immediately preceding, the notification event.
In some embodiments, the determination that the first user interface event corresponds to the first user interface event category includes a determination (e.g., made using determining unit 918) that the first user interface event is a notification event initiated in accordance with completion of a transaction initiated by a user of electronic device 900.
In some embodiments, the determination that the first user interface event corresponds to the first user interface event category includes a determination (e.g., made using determining unit 918) that the first user interface event is provided to an application programming interface (API) with a value indicating that the one or more changes to the user interface can be delayed until device 900 is ready to generate the tactile output.
The operations described above with reference to
As described below, method 1000 provides an enhanced way to provide tactile outputs based on states of tactile output generators. Predicting an upcoming tactile output generation event and transitioning tactile output generators into a low-latency mode reduces the latency in generating tactile outputs, which makes the device more responsive to user inputs, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, placing the tactile output generators in the low-latency mode based on prediction of upcoming tactile output generation events conserves power over maintaining the tactile output generators in the low-latency mode all the time and increases the time between battery charges.
While the one or more tactile output generators are in a low-power state (e.g., at operation 5182, FIG. 5KKK), the device receives (1002) an indication that a user interaction has started (e.g., detecting a first portion of an input such as a touch on a touch sensitive surface or the beginning of a drag and drop operation as shown in FIG. 5III, or receiving a “prepare” request from a first software application in which the user interaction has started, such as at operation 5184, FIG. 5KKK).
A respective portion of the user interaction is associated (1004) with a tactile output (e.g., a portion of the user interaction that corresponds to an overlap of position indicator 5161 with marker 5162 is associated with a tactile output so that an overlap of position indicator 5161 and marker 5162 initiates a tactile output).
The low-power state is (1006) a state in which tactile outputs are generated with a first amount of latency (e.g., it will take at least a warm-up amount of time, such as ΔTA,
In some embodiments, the low-power state is (1008) a predefined inactive state of the one or more tactile output generators (e.g., “inactive” state,
In some embodiments, the user interaction that is associated with the tactile output includes (1010) location information corresponding to a touch input having a location on the touch-sensitive surface (e.g., a location of position indicator 5161 in
In some embodiments, the device determines (1012) a location of the tactile output in accordance with the location information for the user interaction (e.g., when the device includes multiple tactile output generators, the tactile output is generated using one or more tactile output generators located adjacent to the location of the user interaction).
In some embodiments, the one or more tactile output generators include (1014) two or more tactile output generators, each having a corresponding location, or location and size, and determining the location of the tactile output includes determining the location of the tactile output in accordance with the location information for the user interaction and the locations, or locations and sizes, of the two or more tactile output generators (e.g., as shown in
In response to receiving the indication that the user interaction that is associated with the tactile output has started, in accordance with a determination that the indication meets tactile output generator preparation criteria (e.g., at operation 5186—Yes, FIG. 5KKK), the device sets (1016) the one or more tactile output generators to a low-latency state (e.g., a pre-warmed state has a lower latency than an inactive state, and, in some embodiments, a higher latency than a ready state) at a first time (e.g., at T=t1 in FIG. 5III). The low-latency state is (1018) a state in which the tactile outputs are generated with a second amount of latency (e.g., ΔTB,
In some embodiments, the low-power state of the one or more tactile output generators has (1020) a lower power consumption than the low-latency state (e.g., the low-latency state is high-power state that consumes more power than the low-power state). The low-latency state has a lower latency for generating tactile outputs than the low-power state, as shown in
In some embodiments, the low-latency state is selected (1022) from a first low-latency state (e.g., a pre-warmed state with a reduced latency, such as a latency ΔTB that is lower than a latency ΔTA in the off or inactive state but is still perceptible to a user, as described herein with reference to
In some embodiments, the low-latency state is selected (1024) from the first low-latency state and the second low-latency state by an operating system of the device (e.g., operating system 126,
In some embodiments, the device issues (1026) from a first software application a command to set the one or more tactile output generators to the low-latency state. Setting the one or more tactile output generators to the low-latency state is performed in response to the command issued by the first software application to set the one or more tactile output generators to the low-latency state (e.g., information 272 from application 1 (136-1) in
In some embodiments, the device issues (1028) from a first software application (e.g., application 136-1,
In some embodiments, the device determines (1030), using an operating system of the electronic device, when to set the one or more tactile output generators to the low-latency state (e.g., operation 5186 in FIG. 5KKK).
In some embodiments, the operating system of the electronic device determines (1032) whether to set the one or more tactile output generators to the low-latency state in accordance with a state of the electronic device (e.g., if the device is in a battery conservation mode of operation, the operating system can decide whether to set the device into the low-latency state or not, so as to conserve power).
In some embodiments, the operating system of the electronic device determines (1034), in response to a first software application issuing a command to set the one or more tactile output generators to the low-latency state, whether to set the one or more tactile output generators to the low-latency state in accordance with historical information concerning prior commands by the first software application to set the one or more tactile output generators to the low-latency state (e.g., if an application requests to prepare too many times, without requesting a tactile output to be generated, the device ignores subsequent prepare requests).
After setting the one or more tactile output generators to the low-latency state (1036), in accordance with a determination that the user interaction has reached the respective portion of the user interaction that is associated with the tactile output before a predefined amount of time since the first time has elapsed and that the one or more tactile output generators are still in the low-latency state, the device generates (1038) the tactile output using the one or more tactile output generators with the second amount of latency (e.g., generating the tactile output takes less than the warm-up amount of time); and, in accordance with a determination that a tactile output has not been generated for at least the predefined amount of time since the first time (e.g., a timeout period), transitions (1040) the one or more tactile output generators from the low-latency state to the low-power state (e.g., an inactive state) (e.g., using a UIFeedbackGenerator prepare function described below in Appendix A), as described for example with reference to operation 5194, FIG. 5KKK.
In some embodiments, after setting the one or more tactile output generators to the low-latency state (1036), the device, in accordance with a determination that the user interaction has reached the respective portion of the user interaction that is associated with the tactile output after the predefined amount of time since the first time has elapsed and that the one or more tactile output generators have returned to the low-power state, generates (1042) the tactile output using the one or more tactile output generators with the first amount of latency (e.g., generating the tactile output takes at least the warm-up amount of time).
In some embodiments, in response to receiving the indication that the user interaction that is associated with the tactile output has started, in accordance with a determination that the indication does not meet tactile output generator preparation criteria (e.g., because the device is in a battery conservation mode of operation or because the first application has been requesting that the device prepare to generate tactile outputs too frequently), the device maintains (1044) the one or more tactile output generators in the low-power state and forgoes setting the one or more tactile output generators to the low-latency state (e.g., if the first software application has been asking to set the device into the ready state too frequently, or the device is in a battery conservation mode of operation, the operating system can ignore the request in order to conserve battery power), as described for example with reference to operation 5186—No, FIG. 5KKK.
It should be understood that the particular order in which the operations in
The operations in the information processing methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to
In accordance with some embodiments,
As shown in
In some embodiments, while one or more tactile output generator units 1106 are in a low-power state, processing unit 1108 is configured to receive (e.g., using receiving unit 1110) an indication that a user interaction has started, wherein a respective portion of the user interaction is associated with a tactile output, and the low-power state is a state in which tactile outputs are generated with a first amount of latency. In response to receiving the indication that the user interaction that is associated with the tactile output has started, in accordance with a determination (e.g., made using determining unit 1114) that the indication meets tactile output generator preparation criteria, processing unit 1108 sets (e.g., using state setting unit 1112) one or more tactile output generator units 1106 to a low-latency state at a first time, wherein the low-latency state is a state in which the tactile outputs are generated with a second amount of latency that is lower than the first amount of latency. After setting one or more tactile output generator units 1106 to the low-latency state, in accordance with a determination (e.g., made using determining unit 1114) that the user interaction has reached the respective portion of the user interaction that is associated with the tactile output before a predefined amount of time since the first time has elapsed and that one or more tactile output generator units 1106 are still in the low-latency state, processing unit 1108 enables generation of the tactile output using one or more tactile output generator units 1106 with the second amount of latency. In accordance with a determination that a tactile output has not been generated for at least the predefined amount of time since the first time, processing unit 1108 transitions one or more tactile output generator units 1106 from the low-latency state to the low-power state.
In some embodiments, processing unit 1108 is further configured to, after setting one or more tactile output generator units 1106 to the low-latency state, in accordance with a determination that the user interaction has reached the respective portion of the user interaction that is associated with the tactile output after the predefined amount of time since the first time has elapsed and that one or more tactile output generator units 1106 have returned to the low-power state, enable generation (e.g., using tactile output enabling unit 1116) of the tactile output using one or more tactile output generator units 1106 with the first amount of latency.
In some embodiments, the low-power state of one or more tactile output generator units 1106 has a lower power consumption than the low-latency state, and the low-latency state has a lower latency for generating tactile outputs than the low-power state.
In some embodiments, the low-power state is a predefined inactive state of one or more tactile output generator units 1106.
In some embodiments, the low-latency state is selected from a first low-latency state and a second low-latency state, wherein the first low-latency state consumes less power than the second low-latency state and has a higher latency than the second low-latency state.
In some embodiments, the low-latency state is selected from the first low-latency state and the second low-latency state by an operating system of device 1100 based on energy conservation protocols used by device 1100.
In some embodiments, processing unit 1108 is further configured to, in response to receiving the indication (e.g., using receiving unit 1110) that the user interaction that is associated with the tactile output has started, in accordance with a determination that the indication does not meet tactile output generator preparation criteria, maintain (e.g., using state setting unit 1112) one or more tactile output generator units 1106 in the low-power state and forgo setting one or more tactile output generator units 1106 to the low-latency state.
In some embodiments, the user interaction that is associated with the tactile output includes location information corresponding to a touch input having a location on touch-sensitive surface unit 1104 or a user interface object having a location on touch-sensitive surface unit 1104.
In some embodiments, processing unit 1108 is further configured to determine a location (e.g., using determining unit 1114) of the tactile output in accordance with the location information for the user interaction.
In some embodiments, one or more tactile output generator units 1106 include two or more tactile output generator units 1106, each having a corresponding location, or location and size, and determining the location of the tactile output includes determining (e.g., using determining unit 1114) the location of the tactile output in accordance with the location information for the user interaction and the locations, or locations and sizes, of two or more tactile output generator units 1106.
In some embodiments, processing unit 1108 is further configured to issue (e.g., using issuing unit 1118) from a first software application a command to set (e.g., using state setting unit 1112) one or more tactile output generator units 1106 to the low-latency state, wherein setting one or more tactile output generator units 1106 to the low-latency state is performed in response to the command issued by the first software application to set one or more tactile output generator units 1106 to the low-latency state.
In some embodiments, processing unit 1108 is further configured to issue (e.g., using issuing unit 1118) a command to set (e.g., using state setting unit 1112) one or more tactile output generator units 1106 to the low-latency state, and receive, at an operating system of electronic device 1100, the issued command and making a determination (e.g., using determining unit 1114) of whether to set one or more tactile output generator units 1106 to the low-latency state.
In some embodiments, processing unit 1108 is further configured to determine (e.g., using determining unit 1114), using an operating system of electronic device 1100, when to set (e.g., using state setting unit 1112) one or more tactile output generator units 1106 to the low-latency state. In some embodiments, processing unit 1108 is further configured to determine (e.g., using determining unit 1114), using the operating system of electronic device 1100, whether to set (e.g., using state setting unit 1112) one or more tactile output generator units 1106 to the low-latency state in accordance with a state of electronic device 1100.
In some embodiments, the operating system of electronic device 1100 determines (e.g., using determining unit 1114), in response to a first software application issuing a command to set one or more tactile output generator units 1106 to the low-latency state, whether to set one or more tactile output generator units 1106 to the low-latency state in accordance with historical information concerning prior commands by the first software application to set one or more tactile output generator units 1106 to the low-latency state.
The operations described above with reference to
As described below, method 1200 provides an enhanced way to provide tactile outputs using an application-independent software module. Providing tactile outputs using application-independent software based on information from application software provides common user interface framework that provides consistent user experience when various software applications are used. Providing a common user interface frame work to the user enhances the usability of such software applications and the device executing such software applications. In turn, this 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 and/or unintended operations when operating/interacting with the device). In addition, the method reduces the size of software applications and makes execution of such software applications faster. For battery-operated electronic devices, enabling a user to use software applications faster and more efficiently conserves power and increases the time between battery charges.
While a first type of event is associated with a first tactile output and a second type of event that is distinct from the first type of event is associated with a second tactile output that is different from the first tactile output by an application-independent module (e.g., application-independent software module 260,
After generating the response to the first information, the device receives (1212) second information from a second application (e.g., application 136-2,
In some embodiments, the first type of event is (1220) a success event (e.g., an event with the UIEventFeedbackTypeSuccess type, as described in Appendix A) and the second type of event is a failure event (e.g., an event with the UIEventFeedbackTypeError type, as described in Appendix A).
In some embodiments, the first information is received (1222) from an application-specific module for the first application (e.g., application 136-1, or a component of application 136-1 such as application core 270-1,
In some embodiments, generating the response to the first information includes (1224), in accordance with a determination that the first information corresponds to an application event of a third type (e.g., a warning event, such as a notification corresponding to display of an undo operation affordance as illustrated in FIG. 5CCC) that is associated with a fifth tactile output that is different from the first tactile output and the second tactile output and that is distinct from the first type and second type, generating, using the one or more tactile output generators, the fifth tactile output that is different from the first tactile output and the second tactile output; and generating the response to the second information includes, in accordance with a determination that the second information corresponds to an application event of the third type, generating the fifth tactile output using the one or more tactile output generators (e.g., using a UIEventFeedbackGenerator object (or class), including type UIEventFeedbackTypeWarning, as described in Appendix A), as described for example with reference to FIG. 5CCC.
In some embodiments, after generating the response to the first information and generating the response to the second information, the device changes (1226) the first tactile output associated with the first type of event by the application-independent module, including associating the first type of event with a third tactile output that is different from the first tactile output. For example, because the application-independent module determines which tactile output to generate for a respective type of event, by changing the association of an event type with a particular tactile output in the application-independent module, tactile outputs for multiple applications can be updated consistently. In addition, this facilitates changing tactile outputs for a particular event type as the changes need to be made only with the application-independent module instead of changing all of the applications that are configured to generate tactile outputs for the particular event type.
In some embodiments, after changing the tactile output associated with the first type of event by the application-independent module, the device receives (1228) third information from the first application; and, in response to receiving the third information from the first application, generating a response to the third information, including: in accordance with a determination that the third information corresponds to an application event of the first type (e.g., a success event), generating the third tactile output using the one or more tactile output generators. After generating the response to the third information, the device receives fourth information from the second application that is distinct from the first application; and, in response to receiving the fourth information from the second application, generating a response to the fourth information, including, in accordance with a determination that the fourth information corresponds to an application event of the first type (e.g., a success event), generating the third tactile output using the one or more tactile output generators. For example, once the application event of the first type (e.g., a success event) is associated with a new tactile output, namely the third tactile output, tactile outputs for the application event of the first type in both the first application and the second application are changed to match the third tactile output.
In some embodiments, the third information is received (1230) from an application-specific module for the first application (e.g., application core 1 (270-1) in
In some embodiments, after generating the response to the first information and generating the response to the second information, the device changes (1232) the tactile output associated with the second type of event by the application-independent module, including associating the second type of event with a fourth tactile output that is different from the second tactile output.
In some embodiments, after changing the tactile output associated with the second type of event by the application-independent module, the device receives (1234) fifth information from the first application; and, in response to receiving the fifth information from the first application, generates a response to the fifth information, including, in accordance with a determination that the fifth information corresponds to an application event of the second type (e.g., a failure event), generating the fourth tactile output using the one or more tactile output generators. After generating the response to the fifth information, the device receives sixth information from the second application that is distinct from the first application; and, in response to receiving the sixth information from the second application, generates a response to the sixth information, including, in accordance with a determination that the sixth information corresponds to an application event of the second type, generating the fourth tactile output using the one or more tactile output generators. For example, once the application event of the second type (e.g., a failure event) is associated with a new tactile output, namely the fourth tactile output, tactile outputs for the application event of the second type in both the first application and the second application are changed to match the fourth tactile output.
In some embodiments, the fifth information is received (1236) from an application-specific module for the first application (e.g., application core 1 (270-1) in
It should be understood that the particular order in which the operations in
The operations in the information processing methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to
The operations described above with reference to
In accordance with some embodiments,
As shown in
In some embodiments, while a first type of event is associated with a first tactile output and a second type of event that is distinct from the first type is associated with a second tactile output that is different from the first tactile output by an application-independent module, processing unit 1308 is configured to receive (e.g., using receiving unit 1310) first information from a first application. Processing unit 1308 is configured to, in response to receiving the first information from the first application, enable generation of a response (e.g., using response generation enabling unit 1312) to the first information, including, in accordance with a determination (e.g., made using determining unit 1314) that the first information corresponds to an application event of the first type, enabling generation of the first tactile output (e.g., using response generation enabling unit 1312) using one or more tactile output generator units 1306, and in accordance with a determination (e.g., made using determining unit 1314) that the first information corresponds to an application event of the second type that is distinct from the first type, enabling generation (e.g., using response generation enabling unit 1312), using one or more tactile output generator units 1306, of the second tactile output that is different from the first tactile output. Processing unit 1308 is configured to, after enabling generation of the response to the first information, receive (e.g., using receiving unit 1310) second information from a second application that is distinct from the first application. Processing unit 1308 is configured to, in response to receiving the second information from the second application, enable generation of a response (e.g., using response generation enabling unit 1312) to the second information, including, in accordance with a determination (e.g., made using determining unit 1314) that the second information corresponds to an application event of the first type, enabling generation of the first tactile output using one or more tactile output generator units 1306, and in accordance with a determination (e.g., made using determining unit 1314) that the second information corresponds to an application event of the second type, enabling generation of the second tactile output using one or more tactile output generator units 1306.
In some embodiments, processing unit 1308 is further configured to, after enabling generation of the response to the first information and enabling generation of the response to the second information, change the tactile output (e.g., using changing unit 1316) associated with the first type of event by the application-independent module, including associating the first type of event with a third tactile output that is different from the first tactile output.
In some embodiments, after changing the tactile output associated with the first type of event by the application-independent module, processing unit 1308 receives third information (e.g., using receiving unit 1310) from the first application. Processing unit 1308 is configured to, in response to receiving the third information from the first application, enable generation of a response (e.g., using response generation enabling unit 1312) to the third information, including, in accordance with a determination (e.g., made using determining unit 1314) that the third information corresponds to an application event of the first type, enabling generation of the third tactile output (e.g., using response generation enabling unit 1312) using one or more tactile output generator units 1306. Processing unit 1308 is configured to, after enabling generation of the response to the third information, receive fourth information (e.g., using receiving unit 1310) from the second application that is distinct from the first application. Processing unit 1308 is configured to, in response to receiving the fourth information from the second application, enable generation of a response (e.g., using response generation enabling unit 1312) to the fourth information, including, in accordance with a determination (e.g., made using determining unit 1314) that the fourth information corresponds to an application event of the first type, enabling generation of the third tactile output (e.g., using response generation enabling unit 1312) using one or more tactile output generator units 1306.
In some embodiments, the third information is received from an application-specific module for the first application, the fourth information is received from an application-specific module for the second application, and determining whether to generate the third tactile output is performed by the application-independent module.
In some embodiments, processing unit 1308 is configured to, after enabling generation of the response to the first information and enabling generation of the response to the second information, change (e.g., using changing unit 1316) the tactile output associated with the second type of event by the application-independent module, including associating the second type of event with a fourth tactile output that is different from the second tactile output.
In some embodiments, processing unit 1308 is configured to, after changing (e.g., using changing unit 1316) the tactile output associated with the second type of event by the application-independent module, receive fifth information (e.g., using receiving unit 1310) from the first application. Processing unit 1308 is configured to, in response to receiving the fifth information from the first application, enable generation of a response (e.g., using response generation enabling unit 1312) to the fifth information, including, in accordance with a determination (e.g., made using determining unit 1314) that the fifth information corresponds to an application event of the second type, enabling generation of the fourth tactile output (e.g., using response generation enabling unit 1312) using one or more tactile output generator units 1306. Processing unit 1308 is configured to, after enabling generation of the response to the fifth information, receive sixth information (e.g., using receiving unit 1310) from the second application that is distinct from the first application. Processing unit 1308 is configured to, in response to receiving the sixth information from the second application, enable generation of a response (e.g., using response generation enabling unit 1312) to the sixth information, including, in accordance with a determination (e.g., made using determining unit 1314) that the sixth information corresponds to an application event of the second type, enabling generation of the fourth tactile output (e.g., using response generation enabling unit 1312) using one or more tactile output generator units 1306.
In some embodiments, the fifth information is received from an application-specific module for the first application, the sixth information is received from an application-specific module for the second application, and determining whether to generate the fourth tactile output is performed by the application-independent module.
In some embodiments, the first information is received from an application-specific module for the first application, the second information is received from an application-specific module for the second application, and determining whether to generate the first tactile output or the second tactile output is performed by the application-independent module.
In some embodiments, enabling generation of the response (e.g., using response generation enabling unit 1312) to the first information includes, in accordance with a determination (e.g., made using determining unit 1314) that the first information corresponds to an application event of a third type that is associated with a fifth tactile output that is different from the first tactile output and the second tactile output and that is distinct from the first type and second type, enabling generation (e.g., using response generation enabling unit 1312), using one or more tactile output generator units 1306, of the fifth tactile output that is different from the first tactile output and the second tactile output. In some embodiments, enabling generation of the response to the second information includes, in accordance with a determination (e.g., made using determining unit 1314) that the second information corresponds to an application event of the third type, enabling generation (e.g., using response generation enabling unit 1312) of the fifth tactile output using one or more tactile output generator units 1306.
In some embodiments, the first type of event is a success event and the second type of event is a failure event.
As described below, method 1400 provides an enhanced way to provide tactile outputs using an application-independent software module. Providing tactile outputs using application-independent software based on information from application software provides common user interface framework that provides consistent user experience when various software applications are used. Providing a common user interface frame work to the user enhances the usability of such software applications and the device executing such software applications. In addition, the method provides an intuitive way to provide tactile outputs based on physics simulation of impact events. In turn, these features enhance the operability of the device and make the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes and/or unintended operations when operating/interacting with the device). Furthermore, the method reduces the size of software applications and makes execution of such software applications faster. For battery-operated electronic devices, enabling a user to use software applications faster and more efficiently conserves power and increases the time between battery charges.
The device receives (1402), at an application-independent module (e.g., application-independent software module 260,
An operation performed in the user interface of the first application in response to detecting the input is (1404) associated with a tactile output pattern specified by the application-specific module.
In addition, the information about the input includes (1406) information indicating a magnitude (e.g., speed or distance) of the operation performed in the user interface in response to detecting the input, as described in further detail herein with reference to FIGS. 5DDD-5GGG.
In some embodiments, the magnitude is (1408) provided by the first application.
In some embodiments, the magnitude is (1410) provided by an operating system of the electronic device (e.g., operating system 126,
In response to receiving the information about the input directed to the user interface of the first application, the device generates (1412), via the one or more tactile output generators, a tactile output that corresponds to the operation performed in the user interface of the first application.
The tactile output has (1414) the tactile output pattern specified by the application-specific module.
In addition, the tactile output has (1416) an amplitude determined (e.g., by the application-independent module) in accordance with the magnitude of the operation performed in the user interface of the first application in response to detecting the input (e.g., as provided by the application-specific module), as described in further detail herein with reference to FIGS. 5DDD-5GGG. For example, the tactile output is generated using UIImpactFeedbackGenerator.
In some embodiments, the amplitude of the tactile output is (1418) further determined in accordance with at least one of a velocity or mass of an object in a simulated collision or impact.
In some embodiments, the amplitude of the tactile output is (1420) further determined by applying a predefined physics model to one or more parameters of one or more displayed user interface elements or one or more parameters of a touch input.
In some embodiments, the tactile output is (1422) further characterized by a vibration frequency, wherein the vibration frequency is selected based on the tactile output pattern.
In some embodiments, the vibration frequency is (1424) less than 100 hertz.
It should be understood that the particular order in which the operations in
The operations in the information processing methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to
In accordance with some embodiments,
As shown in
In some embodiments, processing unit 1508 is configured to receive (e.g., using receiving unit 1510), at an application-independent module, from an application-specific module that is associated with a first application, information about an input directed to the user interface of the first application, wherein an operation performed in the user interface of the first application in response to detecting the input is associated with a tactile output pattern specified by the application-specific module, and the information about the input includes information indicating a magnitude of the operation performed in the user interface in response to detecting the input. Processing unit 1508 is configured to, in response to receiving the information about the input directed to the user interface of the first application, enable generation (e.g., using tactile output enabling unit 1512), via one or more tactile output generator units 1506, of a tactile output that corresponds to the operation performed in the user interface of the first application, wherein the tactile output has the tactile output pattern specified by the application-specific module, and the tactile output has an amplitude determined in accordance with the magnitude of the operation performed in the user interface of the first application in response to detecting the input.
In some embodiments, the tactile output is further characterized by a vibration frequency, wherein the vibration frequency is selected based on the tactile output pattern. In some embodiments, the vibration frequency is less than 100 hertz. In some embodiments, the amplitude of the tactile output is further determined (e.g., using determining unit 1514) in accordance with at least one of a velocity or mass of an object in a simulated collision or impact. In some embodiments, the amplitude of the tactile output is further determined (e.g., using determining unit 1514) by applying a predefined physics model to one or more parameters of one or more displayed user interface elements or one or more parameters of a touch input. In some embodiments, the magnitude is provided by the application. In some embodiments, the magnitude is provided by an operating system of electronic device 1500.
The operations described above with reference to
As described below, method 1600 provides an enhanced way to provide tactile outputs based on states of tactile output generators. Predicting an upcoming tactile output generation event and transitioning tactile output generators into a low-latency mode reduces the latency in generating tactile outputs, which makes the device more responsive to user inputs, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, placing the tactile output generators in the low-latency mode based on prediction of upcoming tactile output generation events conserves power over maintaining the tactile output generators in the low-latency mode all the time and increases the time between battery charges.
The device displays (1602) a user interface on the display.
While displaying the user interface on the display and while the one or more tactile output generators are in a low-power state (e.g., inactive,
In some embodiments, the first user interaction is (1606) touchdown of a contact on the touch-sensitive surface.
In some embodiments, the first user interaction is (1608) a change in a contact after detecting touchdown of the contact on the touch-sensitive surface.
In response to detecting the first user interaction, the device sets (1610) the one or more tactile output generators to a low-latency state (e.g., pre-warm or active,
After setting the one or more tactile output generators to the low-latency state, the device detects (1612) a second user interaction that is part of a same sequence of user interactions as the first user interaction (e.g., the first user interaction and the second user interaction correspond to a same continuously detected contact or set of contacts on the touch-sensitive surface).
In response to detecting the second user interaction, the device generates (1614) a tactile output that corresponds to the second user interaction (e.g., using a UIFeedbackGenerator Prepare function or a UIFeedbackGeneratorUserInteractionDriven option as described in Appendix B).
Referring again to operation 1612, in some embodiments, the first user interaction and the second user interaction are (1616) detected as part of a continuous touch input on the touch-sensitive surface (e.g., during which the touch input remains in contact with the touch-sensitive surface) that traverses a sequence of components of the user interface displayed on the display.
In some embodiments, the device scrolls (1618) a set of menu items in response to user input on the touch-sensitive surface, wherein the sequence of user interactions comprises a sequence of respective menu items in the set of menu items scrolling to or through a selection position in the user interface (e.g., as described in further detail herein with reference to
In some embodiments, the device scrolls (1620) a set of date component or time component items in response to user input on the touch-sensitive surface, wherein the sequence of user interactions comprises a sequence of date component or time component items scrolling to or through a selection position in the user interface (e.g., as described in further detail herein with reference to
Referring again to operation 1614, in some embodiments, a monitoring function tracks (1622) a progress of the sequence of user interactions. The one or more tactile output generators are changed to the low-latency state based on a determination that the monitoring function has entered a start state in which the monitoring function has started monitoring the sequence of user interactions. In addition, the tactile output is generated based on a determination that the monitoring function has entered a changed state (e.g., a changed state for or with respect to the sequence of user interactions).
In some embodiments, a monitoring function tracks (1624) a progress of the sequence of user interactions. The one or more tactile output generators are changed to the low-latency state based on a determination that the monitoring function has entered a changed state that precedes a changed state that corresponds to a tactile output (e.g., a changed state indicating movement of the contact). In addition, the tactile output is generated based on a determination that the monitoring function has entered the changed state that corresponds to a tactile output (e.g., a changed state indicating movement of the contact over a boundary or to a new drop target).
In some embodiments, the sequence of user interactions corresponds (1626) to a continuous touch input on the touch-sensitive surface that traverses a sequence of components of a user interface displayed on the display, and the device generates a sequence of two or more tactile outputs using identical waveforms (e.g., using UIRetargetFeedbackGenerator).
In some embodiments, the sequence of user interactions corresponds (1628) to a touch input on the touch-sensitive surface that traverses a sequence of soft keys (e.g., keys for selecting different versions of a same letter or character, such as a letter (e.g., “e”) with different diacritical marks) displayed on the display, and the device generates one or more tactile outputs that correspond to the touch input reaching predefined positions with respect to the sequence of soft keys (e.g., leading edges, or central positions, or both, of the keys).
In some embodiments, the sequence of user interactions includes (1630) a sequence of events corresponding to distinct phases of dragging an object, in the user interface displayed on the display, from an initial location to another location (e.g., using a UIDragFeedbackGenerator object), as described in further detail herein with reference to
In some embodiments, the distinct phases of dragging the object include (1632) an object lifting phase and an object dropping phase. In some embodiments, in response to a first respective user interaction, in the sequence of user interactions, the first respective user interaction corresponding to the object lifting phase, the device sets one or more tactile output generators to the low-latency state, and in response to a second respective user interaction, in the sequence of user interactions, the second respective user interaction corresponding to the object dropping phase, the device sets one or more tactile output generators to the low-power state (e.g., as described herein with reference to method 1000).
In some embodiments, the distinct phases of dragging the object include (1634) an object snapping phase, corresponding to the object snapping into place with respect to a user interface feature (e.g., a grid or an array, as described in further detail herein with reference to
In some embodiments, after generating the tactile output in response to detecting the second user interaction, the device forgoes (1636) generation of a subsequent tactile output in response to detecting a third user interaction that is part of the same sequence of user interactions as the first user interaction and the second user interaction, in accordance with a determination that the third user interaction occurred less than a predefined time duration from the second user interaction (e.g., as described in further detail herein with reference to
In some embodiments, the device detects (1638) an end of the sequence of user interactions. In response to detecting the end of the sequence of user interactions, the device sets the one or more tactile output generators to the low-power state.
In some embodiments, a monitoring function tracks (1640) a progress of the sequence of user interactions, and the one or more tactile output generators are set to the low-power state based on a determination that the monitoring function has entered an end state (e.g., an end state for, or with respect to, the sequence of user interactions).
It should be understood that the particular order in which the operations in
The operations in the information processing methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to
In accordance with some embodiments,
As shown in
In some embodiments, processing unit 1708 is configured to enable display (e.g., using display enabling unit 1710) of a user interface on display unit 1702. While enabling display of the user interface on display unit 1702 and while one or more tactile output generator units 1706 are in a low-power state, processing unit 1708 detects (e.g., using detecting unit 1712) a first user interaction via touch-sensitive surface unit 1704. Processing unit 1708 is configured to, in response to detecting the first user interaction, set one or more tactile output generator units 1706 to a low-latency state (e.g., using state setting unit 1714). Processing unit 1708 is configured to, after setting one or more tactile output generator units 1706 to the low-latency state, detect (e.g., using detecting unit 1712) a second user interaction that is part of a same sequence of user interactions as the first user interaction. Processing unit 1708 is configured to, in response to detecting the second user interaction, enable generation of a tactile output (e.g., using tactile output enabling unit 1716) that corresponds to the second user interaction.
In some embodiments, the first user interaction and the second user interaction are detected as part of a continuous touch input on touch-sensitive surface unit 1704 that traverses a sequence of components of the user interface displayed on display unit 1702.
In some embodiments, the first user interaction is touchdown of a contact on touch-sensitive surface unit 1704. In some embodiments, the first user interaction is a change in a contact after detecting touchdown of the contact on touch-sensitive surface unit 1704.
In some embodiments, a monitoring function tracks a progress of the sequence of user interactions. One or more tactile output generator units 1706 are changed (e.g., using state setting unit 1714) to the low-latency state based on a determination (e.g., made using determining unit 1718) that the monitoring function has entered a start state in which the monitoring function has started monitoring the sequence of user interactions, and the tactile output is generated (e.g., using tactile output enabling unit 1716) based on a determination (e.g., made using determining unit 1718) that the monitoring function has entered a changed state.
In some embodiments, a monitoring function tracks a progress of the sequence of user interactions. One or more tactile output generator units 1706 are changed (e.g., using state setting unit 1714) to the low-latency state based on a determination (e.g., made using determining unit 1718) that the monitoring function has entered a changed state that precedes a changed state that corresponds to a tactile output, and the tactile output is generated (e.g., using tactile output enabling unit 1716) based on a determination (e.g., made using determining unit 1718) that the monitoring function has entered the changed state that corresponds to a tactile output.
In some embodiments, processing unit 1708 is further configured to detect (e.g., using detecting unit 1712) an end of the sequence of user interactions. Processing unit 1708 is configured to, in response to detecting the end of the sequence of user interactions, set one or more tactile output generator units 1706 to the low-power state (e.g., using state setting unit 1714).
In some embodiments, a monitoring function tracks a progress of the sequence of user interactions, and one or more tactile output generator units 1706 are set (e.g., using state setting unit 1714) to the low-power state based on a determination (e.g., made using determining unit 1718) that the monitoring function has entered an end state.
In some embodiments, the sequence of user interactions corresponds to a continuous touch input on touch-sensitive surface unit 1704 that traverses a sequence of components of a user interface displayed on display unit 1702, and processing unit 1708 is further configured to enable generation of a sequence of two or more tactile outputs (e.g., using tactile output enabling unit 1716) using identical waveforms.
In some embodiments, processing unit 1708 is configured to, after enabling generation of the tactile output in response to detecting the second user interaction, forgo generation of a subsequent tactile output (e.g., using tactile output enabling unit 1716) in response to detecting (e.g., using detecting unit 1712) a third user interaction that is part of the same sequence of user interactions as the first user interaction and the second user interaction, in accordance with a determination (e.g., made using determining unit 1718) that the third user interaction occurred less than a predefined time duration from the second user interaction.
In some embodiments, processing unit 1708 enables scrolling of a set of menu items (e.g., using scroll enabling unit 1720) in response to user input on touch-sensitive surface unit 1704, wherein the sequence of user interactions comprises a sequence of respective menu items in the set of menu items scrolling to or through a selection position in the user interface.
In some embodiments, processing unit 1708 enables scrolling a set of date component or time component items (e.g., using scroll enabling unit 1720) in response to user input on touch-sensitive surface unit 1704, wherein the sequence of user interactions comprises a sequence of date component or time component items scrolling to or through a selection position in the user interface.
In some embodiments, the sequence of user interactions corresponds to a touch input on touch-sensitive surface unit 1704 that traverses a sequence of soft keys displayed on display unit 1702, and processing unit 1708 enables generation of one or more tactile outputs (e.g., using tactile output enabling unit 1716) that correspond to the touch input reaching predefined positions with respect to the sequence of soft keys.
In some embodiments, the sequence of user interactions includes a sequence of events corresponding to distinct phases of dragging an object, in the user interface displayed on display unit 1702, from an initial location to another location. In some embodiments, the distinct phases of dragging the object include an object lifting phase and an object dropping phase. In some embodiments, the distinct phases of dragging the object include an object snapping phase, corresponding to the object snapping into place with respect to a user interface feature, and the tactile output corresponds to the object snapping into place with respect to the user interface feature.
The operations described above with reference to
As described below, method 1800 provides an enhanced way to provide tactile outputs based on time intervals. Forgoing generation of tactile outputs based on time intervals from preceding tactile outputs reduces excessive generation of tactile outputs, thereby protecting tactile output generators. In addition, forgoing generation of tactile outputs based on time intervals from preceding tactile outputs reduces overloading the user with tactile outputs, thereby allowing the user to focus on more important tactile outputs. Thus, this protects the device and makes the user-device interface more efficient (e.g., by providing more important tactile outputs and reducing user mistakes and/or unintended operations when operating/interacting with the device).
The device receives (1802) a first request for a first user interface operation.
The first user interface operation is (1804) a first type of change in a respective user interface element that is associated with a first tactile output.
In response to receiving the first request (1806), the device performs (1808) the first user interface operation, and generates (1810) the first tactile output.
After performing the first user interface operation, the device receives (1812) a second request for a second user interface operation that is associated with a second tactile output.
In response to receiving the second request (1814), in accordance with a determination (1816) that the second request for the second user interface operation comprises a request for an instance of the first type of change in the user interface that is associated with the second tactile output, the operations described as followed are performed (e.g., as described in further detail herein with reference to FIG. 5JJJ).
The device determines (1818) a time interval from a point in time corresponding to a most recent prior instance of the first type of change in the respective user interface element for which a tactile output was generated to a point in time corresponding to the first type of change in the respective user interface element requested by the second request. In some embodiments, the time interval is measured from request times for the tactile outputs, times associated with user interface changes, or tactile output times (actual and projected).
In accordance with a determination (1820) that the time interval is less than a predefined time period, the device performs the second user interface operation without generating the second tactile output (e.g., as described in further detail herein with reference to the requests and tactile outputs in tactile output graph 5170a, FIG. 5JJJ).
In some embodiments, the time interval is (1822) determined from a beginning of the tactile output generated for the most recent prior instance of the first type of change in the respective user interface element to a beginning of the second tactile output. In some embodiments, the predefined time period is longer than a duration of the tactile output generated for the most recent prior instance of the first type of change in the respective user interface element.
In accordance with a determination (1824) that the time interval is greater than the predefined time period, the device performs the second user interface operation and generates the second tactile output (e.g., as described in further detail herein with reference to the requests and tactile outputs in tactile output graph 5170a, FIG. 5JJJ).
In some embodiments, in accordance (1826) a determination that the second request for the second user interface operation does not comprise a request for an instance of the first type of change in the respective user interface element, the device mixes the second tactile output with other tactile outputs generated by the one or more tactile output generators without regard to whether the time interval is less than the predefined time period (e.g., as described in further detail herein with reference to the requests and tactile outputs in tactile output graph 5170b, FIG. 5JJJ).
In some embodiments, after performing the second user interface operation, the device receives (1828) a third request for a third user interface operation that is associated with a third tactile output. In response to receiving the third request for the third user interface operation, in accordance with a determination that the third request for the third user interface operation comprises a request for an instance of the first type of change in the user interface that is associated with a third tactile output, the device determines a second time interval from a point in time corresponding to a most recent prior instance of the first type of change in the respective user interface element for which a tactile output was generated to a point in time corresponding to the first type of change in the respective user interface element requested by the third request. In accordance with a determination that the second time interval is less than the predefined time period, the device performs the third user interface operation without generating the third tactile output. In accordance with a determination that the second time interval is greater than the predefined time period, the device performs the third user interface operation and generates the third tactile output.
In some embodiments, the first and third tactile outputs are (1830) synchronized with first and third user interactions in a sequence of user interactions that correspond to a continuous touch input on the touch-sensitive surface (e.g., traversing a sequence of user interface elements, such as a sequence of menu items, date or time component items, or soft keys, in response to a continuous touch input). In some embodiments, the first, second, and third tactile outputs correspond to first, second, and third elements, respectively, in the sequence. In some embodiments, generation of a respective tactile output is synchronized with the continuous touch input traversing the corresponding respective user interface element. In some embodiments, however, if the input traverses the sequence too quickly, one or more of the tactile outputs are not generated. In some embodiments, even if, for example, the second tactile output is not generated, generation of the first and third tactile outputs is synchronized with the continuous touch input traversing the first and third element, respectively (e.g., without regard to whether the second tactile output is generated).
In some embodiments, in response to receiving the third request (1832), in accordance with a determination that the third request for the third user interface operation does not comprise an instance of the first type of change in the respective user interface element, the device mixes the third tactile output with other tactile outputs generated by the one or more tactile output generators without regard to whether the second time interval is less than the predefined time period (e.g., as described in further detail herein with reference to the requests and tactile outputs in tactile output graphs 5170a and 5170b, FIG. 5JJJ).
It should be understood that the particular order in which the operations in
The operations in the information processing methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to
In accordance with some embodiments,
As shown in
In some embodiments, processing unit 1908 is configured to receive (e.g., using receiving unit 1910) a first request for a first user interface operation, wherein the first user interface operation is a first type of change in a respective user interface element that is associated with a first tactile output. Processing unit 1908 is configured to, in response to receiving the first request, perform (e.g., using performing unit 1912) the first user interface operation, and enable generation of the first tactile output (e.g., using tactile output enabling unit 1914). Processing unit 1908 is configured to, after performing the first user interface operation, receive (e.g., using receiving unit 1910) a second request for a second user interface operation that is associated with a second tactile output. Processing unit 1908 is configured to, in response to receiving the second request, in accordance with a determination (e.g., made using determining unit 1916) that the second request for the second user interface operation comprises a request for an instance of the first type of change in the user interface that is associated with a second tactile output, determine a time interval (e.g., using determining unit 1916) from a point in time corresponding to a most recent prior instance of the first type of change in the respective user interface element for which a tactile output was generated to a point in time corresponding to the first type of change in the respective user interface element requested by the second request. Processing unit 1908 is configured to, in accordance with a determination (e.g., made using determining unit 1916) that the time interval is less than a predefined time period, perform the second user interface operation (e.g., using performing unit 1912) without enabling generation of the second tactile output; and, in accordance with a determination that the time interval is greater than the predefined time period, perform the second user interface operation (e.g., using performing unit 1912) and enable generation of the second tactile output (e.g., using tactile output enabling unit 1914).
In some embodiments, the time interval is determined (e.g., using determining unit 1916) from a beginning of the tactile output generated for the most recent prior instance of the first type of change in the respective user interface element to a beginning of the second tactile output, and the predefined time period is longer than a duration of the tactile output generated for the most recent prior instance of the first type of change in the respective user interface element.
In some embodiments, processing unit 1908 is configured to, in response to receiving the second request, in accordance with a determination (e.g., made using determining unit 1916) that the second request for the second user interface operation does not comprise a request for an instance of the first type of change in the respective user interface element, mix (e.g., using mixing unit 1918 and/or tactile output enabling unit 1914) the second tactile output with other tactile outputs generated by one or more tactile output generator units 1906 without regard to whether the time interval is less than the predefined time period.
In some embodiments, processing unit 1908 is configured to, after performing the second user interface operation, receive (e.g., using receiving unit 1910) a third request for third user interface operation that is associated with a third tactile output. Processing unit 1908 is configured to, in response to receiving the third request for a third user interface operation, in accordance with a determination (e.g., made using determining unit 1916) that the third request for the third user interface operation comprises a request for an instance of the first type of change in the user interface that is associated with a third tactile output, determine (e.g., using determining unit 1916) a second time interval from a point in time corresponding to a most recent prior instance of the first type of change in the respective user interface element for which a tactile output was generated to a point in time corresponding to the first type of change in the respective user interface element requested by the third request. Processing unit 1908 is configured to, in accordance with a determination (e.g., made using determining unit 1916) that the second time interval is less than the predefined time period, perform the third user interface operation (e.g., using performing unit 1912) without enabling generation of the third tactile output. Processing unit 1908 is configured to, in accordance with a determination (e.g., made using determining unit 1916) that the second time interval is greater than the predefined time period, perform the third user interface operation (e.g., using performing unit 1912) and enable generation of the third tactile output (e.g., using tactile output enabling unit 1914).
In some embodiments, processing unit 1908 is configured to, in response to receiving the third request, in accordance with a determination that the third request for the third user interface operation does not comprise an instance of the first type of change in the respective user interface element, mix (e.g., using mixing unit 1918 and/or tactile output enabling unit 1914) the third tactile output with other tactile outputs generated by one or more tactile output generator units 1906 without regard to whether the second time interval is less than the predefined time period.
In some embodiments, the first and third tactile outputs are synchronized (e.g., using synchronizing unit 1920, mixing unit 1918, and/or tactile output enabling unit 1914) with first and third user interactions in a sequence of user interactions that correspond to a continuous touch input on touch-sensitive surface unit 1904.
The operations described above with reference to
As described below, method 2000 provides an enhanced way to provide tactile outputs using an application-independent software module. Providing tactile outputs using application-independent software based on information from application software provides common user interface framework that provides consistent user experience when various software applications are used. Providing a common user interface frame work to the user enhances the usability of such software applications and the device executing such software applications. In addition, method 2000 provides an intuitive way to provide tactile outputs based on a magnitude of an input. Tactile outputs based on the magnitude of the input conform to user expectations for tactile outputs. In turn, these features enhance the operability of the device and make the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes and/or unintended operations when operating/interacting with the device). In addition, the method reduces the size of software applications and makes execution of such software applications faster. For battery-operated electronic devices, enabling a user to use software applications faster and more efficiently conserves power and increases the time between battery charges.
The device receives (2002), at an application-independent module (e.g., application-independent software module 260,
In some embodiments, the application-independent module comprises (2004), or is included in, an operating system of the electronic device (e.g., operating system 126,
The user interface information corresponds (2006) to one or more displayed user interface elements with one or more dimensions defined by an application-specific module of the application.
In some embodiments, the one or more dimensions of the user interface elements include (2008) an extent of a user interface element and an extent that the user interface element can be temporarily scrolled beyond an edge of a display region (e.g., an edge of the display), as described in further detail herein with reference to
In some embodiments, the one or more dimensions of the user interface elements include (2010) a maximum zoom size of a user interface element and an amount by which the user interface element can be temporarily zoomed beyond the maximum zoom size (e.g., the zooming beyond the maximum zoom size is maintained until the end of the input that caused the zooming beyond the maximum zoom size, at which point the user interface element returns to the maximum zoom size). In some embodiments, a tactile output is generated when the user interface element reaches the maximum zoom size, as described in further detail herein with reference to
In some embodiments, the one or more dimensions of the user interface elements include (2012) a minimum zoom size of a user interface element and an amount by which the user interface element can be temporarily zoomed beyond the minimum zoom size (e.g., the zooming beyond the minimum zoom size is maintained until the end of the input that caused the zooming beyond the minimum zoom size, at which point the user interface element returns to the minimum zoom size). In some embodiments, a tactile output is generated when the user interface element reaches the minimum zoom size, as described in further detail herein with reference to
Next, the device receives (2014) an input directed toward one or more of the displayed user interface elements (e.g., corresponding to changes in a position of a user input). In some embodiments, the device detects changes in the position of the input by receiving them from an application or from other channel(s) (e.g., a module that is updating the UI for the application).
Next, the device determines (2016), at the application-independent module, one or more tactile outputs to be generated based on a magnitude (e.g., distance, velocity, intensity, etc.) of the input and the one or more dimensions defined by the applications-specific module. In some embodiments, the device determines the one or more tactile outputs in accordance with changes to a position or scale of one or more of the displayed user interface elements, based on a magnitude (or more generally a parameter) of the input.
Next, the device generates (2018), using the one or more tactile output generators, the determined one or more tactile outputs (e.g., using a UIEdgeFeedbackGenerator class described in Appendix B or its instance).
In some embodiments, the application-independent module determines (2020) a magnitude of the one or more tactile outputs by applying a predefined physics model to one or more parameters of the received input (e.g., a magnitude of the velocity of the input).
In some embodiments, the application-independent module determines (2022) whether to generate a respective tactile output based on whether an edge of a respective element, of the displayed user interface elements, has passed a predefined boundary (e.g., as described in further detail herein with reference to
In some embodiments, the application-independent module determines (2024) whether to generate a respective tactile output based on whether a parameter (e.g., size) of a respective element, of the displayed user interface elements, has passed a predefined limit.
In some embodiments, the application-independent module determines (2026) whether to generate a respective tactile output based on whether an edge of a respective element, of the displayed user interface elements, has passed a predefined boundary, and whether a respective user touch input is detected (e.g., scrolling with a rubber band effect while a contact is detected, or performing a zoom in or zoom out operation while a contact is detected).
It should be understood that the particular order in which the operations in
The operations in the information processing methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to
In accordance with some embodiments,
As shown in
In some embodiments, processing unit 2108 is configured to receive, at an application-independent module, user interface information from an application (e.g., using information receiving unit 2110), wherein the user interface information corresponds to one or more displayed user interface elements with one or more dimensions defined by an application-specific module of the application. Processing unit 2108 is configured to receive (e.g., using input receiving unit 2112) an input directed toward one or more of the displayed user interface elements. Processing unit 2108 is configured to determine, at the application-independent module, one or more tactile outputs to be generated based on a magnitude of the input and the one or more dimensions defined by the applications-specific module (e.g., using determining unit 2114), and enable generation (e.g., using tactile output enabling unit 2116) of the determined one or more tactile outputs using one or more tactile output generator units 2106.
In some embodiments, the application-independent module comprises, or is included in, an operating system of electronic device 2100. In some embodiments, the application-independent module determines a magnitude of the one or more tactile outputs by applying a predefined physics model to one or more parameters of the received input.
In some embodiments, the application-independent module determines (e.g., using determining unit 2114) whether to generate a respective tactile output based on whether an edge of a respective element, of the displayed user interface elements, has passed a predefined boundary. In some embodiments, the application-independent module determines (e.g., using determining unit 2114) whether to generate a respective tactile output based on whether a parameter of a respective element, of the displayed user interface elements, has passed a predefined limit. In some embodiments, the application-independent module determines (e.g., using determining unit 2114) whether to generate a respective tactile output based on whether an edge of a respective element, of the displayed user interface elements, has passed a predefined boundary, and whether a respective user touch input is detected.
In some embodiments, the dimensions of the user interface elements include an extent of a user interface element and an extent that the user interface element can be temporarily scrolled beyond an edge of a display region. In some embodiments, the dimensions of the user interface elements include a maximum zoom size of a user interface element and an amount by which the user interface element can be temporarily zoomed beyond the maximum zoom size. In some embodiments, the dimensions of the user interface elements include a minimum zoom size of a user interface element and an amount by which the user interface element can be temporarily zoomed beyond the minimum zoom size.
The operations described above with reference to
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.
UIFeedbackGenerator (API)
Motivation
Architecture Overview
UIKit sits on top of CoreAudio to play audio and haptic feedback, and provides a high level API called UIFeedbackGenerator. It is a semantic layer, a representation of a user interaction that would result in haptic and/or audio feedback. It takes input from the user interface and processes that input to generate and play feedback.
For example, we want the same feedback when:
These three use cases are all represented by the same Selection feedback generator.
The list of feedback generators we plan to expose are:
This architecture allows UIKit to change how feedback generators feel across the entire system without changing each of the use sites. This design lets us iterate quickly on haptics for system-wide interactions. Adopting feedback generators is easy for clients and minimally invasive to their existing code, even for feedback generators that perform complex processing of inputs to determine the appropriate feedback to play. Finally, by providing a limited set of well-defined feedback generators, we can ensure some degree of consistency in how feedback is used across the entire system.
Detailed Design
The only feedback APIs we plan to expose are a handful of feedback generator classes inheriting from UIFeedbackGenerator.
Base Class—UIFeedbackGenerator
Objective-C
NS_CLASS_AVAILABLE_IOS(10_0)
@interface UIFeedbackGenerator: NSObject
UIFeedbackGenerator is the base abstract class for all our feedback generators. It cannot be directly instantiated.
Feedback Generator Preparation
When directly calling feedback generating methods on feedback generator classes, UIKit first needs to bring up the underlying software and hardware stack, which incur a significant latency before the feedback is actually played (around 200 ms). To alleviate this problem, the UIFeedbackGenerator base class contains the method prepare which is used to get everything ready for imminent feedback. This method can be called multiple times, and it's fine if no feedback is triggered after it. Once prepared, the latency is significantly lowered to around 60 ms.
When prepared, a feedback generator is using expensive software and hardware resources so it should be kept in that state for a limited duration. It will go back to an idle state after a short time or until the object is deallocated.
Objective-C
//prepare the feedback generator for imminent feedback
[feedbackGenerator prepare];
//do something on the feedback generator a little bit later
//with a minimal feedback latency
[feedbackGenerator something];
Swift
//prepare the feedback generator for imminent feedback feedbackGenerator.prepare( )
//do something on the feedback generator a little bit later
//with a minimal feedback latency
feedbackGenerator.something( )
Built-in Feedback Generators
Selection Feedback Generator
The UISelectionFeedbackGenerator is used when changing a selection.
Objective-C
NS_CLASS_AVAILABLE_IOS(10_0)
@interface UISelectionFeedbackGenerator: UIFeedbackGenerator
The client just needs to call-selectionChanged whenever the selection changes, which will trigger feedback to play.
Changing the selection in a menu.
Objective-C
UISelectionFeedbackGenerator*selectionFeedbackGenerator=
[[UISelectionFeedbackGenerator alloc] init];
//when the user starts interacting with the component,
//typically in the Began state of a gesture recognizer
[selectionFeedbackGenerator prepare];
//when the user selects something else as their finger moves around,
//typically in the Changed state of a gesture recognizer,
//when the selected row changes
[selectionFeedbackGenerator selectionChanged];
Swift
let selectionFeedbackGenerator=UISelectionFeedbackGenerator( )
//when the user starts interacting with the component,
//typically in the Began state of a gesture recognizer selectionFeedbackGenerator, prepare( );
//when the user selects something else as their finger moves around,
//typically in the Changed state of a gesture recognizer,
//when the selected row changes
selectionFeedbackGenerator.selectionChanged( );
Impact Feedback Generator
The UIImpactFeedbackGenerator is used for collisions and detents.
Objective-C
typedef NS_ENUM(NSInteger, UIImpactFeedbackStyle) {
UIImpactFeedbackGenerator generates feedback when items collide or cross a detent. The impact feedback generator is configured with a style representing the overall magnitude of the impact (roughly, the “mass” of the item).
The client calls-impactOccurred when an impact occurs.
An object crossing a detent and colliding.
Objective-C
UIImpactFeedbackGenerator*impactFeedbackGenerator=[[UIImpactFeedbackGenerator alloc] initWithStyle: UIImpactFeedbackGeneratorStyleHeavy];
//when you're about to hit something
[impactFeedbackGenerator prepare];
//perform these a little bit later
}
The UINotificationFeedbackGenerator is used for spontaneous notifications.
Objective-C
typedef NS_ENUM(NSInteger, UINotificationFeedbackType) {
UINotificationFeedbackGenerator generates feedback for spontaneous notifications, generally triggered by some asynchronous event occurring as a result of previous user interaction (e.g. shake to undo alert presents, Apple Pay payment succeeds).
The client simply calls-notificationOccurred: passing the type of the notification, which will trigger the appropriate feedback.
Displaying an alert controller with an error feedback.
Objective-C
UINotificationFeedbackGenerator*notificationFeedbackGenerator [[UINotificationFeedbackGenerator alloc] init];
[notification:FeedbackGenerator prepare];
//display an alert controller here
[notificationFeedbackGenerator
notificationOccurred:UINotificationFeedbackTypeError];
Swift
let notificationFeedbackGenerator=
UINotificationFeedbackGenerator( );
notificationFeedbackGenerator, prepare( )
//display an alert controller here
notificationFeedbackGenerator,notificationQccurred(type: error)
Impact on Existing Code
Existing first-party clients using _UITapticEngine will need to transition over to using the appropriate public or private UIFeedbackGenerator subclass, or the new UIPreviewInteraction API for Peek & Pop.
FAQ
What happens if I don't call prepare?
If you don't call prepare, you'll still get proper feedback playing but it may be delayed. Calling this method in advance is an optimization to ensure the best latency and feedback experience.
What happens if I call prepare constantly?
If you call prepare constantly, UIKit will try to honor it but might ignore your calls at some point to prevent an app from keeping the hardware warm if not actually triggering feedback.
What happens if I call a method generating feedback on a feedback generator and then immediately release/dealloc it? Will the feedback still be felt?
Yes, because the feedback generator schedules feedback events on a different object so it's not needed to actually play it. The hardware will go back to idle state as soon as the feedback is done playing—providing no other feedback generator is in play at the same time.
What if a third party client wants to have more complex haptics?
We currently don't support this but might in the future, either in UIKit or directly in CoreAudio.
Can a third party client disable or customize feedback on UIKit built-in controls?
No, we don't allow this to provide a unified experience across the system.
Date Picker
Let's look at the concrete example of a date picker (
The date picker is made of 4 independently spinnable wheels which can be rotated simultaneously. As a consequence, we'll use 4 instances of UISelectionFeedbackGenerator to provide feedback when a new item is selected in each one of them.
A feature of the UISelectionFeedbackGenerator that is used by the date picker is that the pitch and volume of the audio and haptic are proportional to how fast the wheel is spinning. Each wheel will call selectionChanged on its own feedback generator, which will calculate the speed based on the frequency of the calls. Then the feedback generator will internally modulate the feedback to provide a great feeling for the end user.
Additionally, we want to limit the global frequency of played feedback across all selection feedback generators, to avoid overflowing the user with vibrations.
To achieve this rich experience, each wheel of the date picker (assuming they are subclasses of UIScrollView) would need this simple code:
Objective-C
UIFeedbackGenerator Additions
Architecture Overview
Let's explore these layers one by one, starting from the bottom.
Low-Level: Core Audio AVHapticPlayer and System Sound Services
AVHapticPlayer is the low-level entry point into the haptic system. This layer is vended by Core Audio. It allows UIKit to drive discrete haptics and modulate continuous ones. It also lets UIKit inform the system about how to prioritize haptic requests. The intent is for this layer to be consumed only by UIKit. This will keep UIKit as the only client of AVHapticPlayer, and allow us to iterate quickly on different haptic feelings.
The Core Audio System Sound Services APIs can play legacy haptics (e.g. peek & pop haptics) as well as sounds (e.g. keyboard clicks, device lock/unlock sounds). The new UIKit UIFeedback stack uses System Sound Services to play these sounds and legacy haptics, and as well as system sounds that we want to play alongside haptic feedback.
Mid-Level: UIKit UIFeedback
The UIFeedback class represents playable feedback, which could be haptic and/or audio. There are subclasses for different use cases: UIDiscreteFeedback for discrete one-off haptics (e.g. “Peek” or “Pop”), UIContinuousFeedback for continuous haptics (e.g. a continuous vibration), and UIFeedbackPattern which can compose multiple discrete and continuous feedback into a more complex pattern. When a UIFeedback instance is told to play, it is handed over to a UIFeedbackEngine which is responsible for using the low-level Core Audio APIs to prepare the hardware and then schedule & play the feedback.
This UIFeedback layer is consumed primarily by UIKit to implement the high-level UIFeedbackGenerator API described below. Internal clients with exceptional needs can use UIFeedback directly, but such cases are extremely limited (currently there are none).
High-Level: UIKit UIFeedbackGenerator (API)
UIFeedbackGenerator is a high-level representation of a user interaction that would result in haptic and/or audio feedback.
Synchronizing with the UI
To synchronize your UI with the feedback and make sure both happen at the same time, you can call prepareWithCompletionHandler: and execute your UI and feedback code in the handler, which will be called on the main thread. This will ensure that the feedback generated has a minimal latency and is experienced in sync with the UI.
The success parameter informs you about whether feedback will actually be played for actions called inside the handler or not.
If you want to display some UI which would be synchronized with a feedback.
Objective-C
[generator prepareWithCompetionHandler:{circumflex over ( )}(BOOL success) {
The UIDragFeedbackGenerator is used for interactive drag & drop and reordering.
Objective-C
NS_ASSUME_NONNULL_BEGIN
NS_CLASS_AVAILABLE_IOS(10_0) @interface UIDragFeedbackGenerator: UIFeedbackGenerator <UIFeedbackGeneratorUsernteractionDriven>
///call when: the interaction has moved the object being dragged
UIDragFeedbackGenerator generates feedback when items are dragged and reordered. The drag generator has a sub-class UIDragSnappingFeedbackGenerator to be used when the dragged item will snap into place.
The drag generator is user interaction driven, so the appropriate calls should be made when user interaction begins/ends/cancels. Then the client should call-positionUpdated whenever the dragged item moves, and (if using the snapping style) call-snappedToFinalPosition when the dragged item snaps into place.
Dragging and dropping an object.
Objective-C
UIDragFeedbackGenerator*dragGenerator=[UIDragFeedbackGenerator generatorWithCoordinateSpace: self];
//when the user interaction starts,
//typically in the Began state of a gesture recognizer
[dragGenerator userInteractionStarted];
//when the user moved the dragged object on the screen
//expected to be called a lot of times
[dragGenerator positionUpdated];
//when the major drop target changes,
//for example moving from one area to another
[dragGenerator dropTargetUpdated];
//when the user interaction stops,
//typically in the Ended state of a gesture recognizer
[dragGenerator userinteractionEnded];
Edge Feedback Generator
The UIEdgeFeedbackGenerator is used when reaching an edge or limit.
Objective-C
NS_ASSUME_NONNULL_BEGIN
NS_CLASS_AVAILABLE_IOS(10_0) @interface UIEdgeFeedbackGenerator: UIFeedbackGenerator <UIFeedbackGeneratorUserInteractionDriven>
//distance describes the area between edges
//By default, it is the axis size component of the generator's
//coordinate spaces' bounds
@property (nonatomic) CGFloat distance;
//extentBeyondDistance specifies how many points, in
//coordinateSpace, the interaction can move, 0 by default
@property (nonatomic) CGFloat extentBeyondDistance;
//position can range from (0—exten:tBeyondDistance) to
//(distance+extent BeyondDistance)
//position should be within coordinateSpace
UIEdgeFeedbackGenerator generates feedback when an edge or limit is reached and/or exceeded. Each edge generator is created with a style for the particular use, which affects the feedback that is generated. The edge generator is one-dimensional, and is configured for a single axis. It is also configured with a distance (i.e. the size of the view in that axis) and an extentBeyondDistance (i.e. the maximum rubber band distance; how far beyond the distance can the position move).
UIZoomEdgeFeedbackGenerator is a subclass of edge generator that generates feedback when a zoom limit is reached and/or exceeded. It is configured with minimum and maximum zoom scales, as well as minimum/maximum temporary zoom scales (the equivalent rubber band effect for zooming).
Both the edge and zoom edge generators are user interaction driven, so the appropriate calls should be made when user interaction begins/ends/cancels. Then the client just needs to call-positionUpdated: or -zoomScaleUpdated: whenever the value changes. The generator processes these inputs to play feedback; for example, when an edge is reached the generator plays a haptic with an intensity proportional to the velocity at that time.
Implementing a slider-like UIControl subclass.
Swift
class MyCustomSlider: UIControl {
Several components of UIKit have adopted feedback and expose new APIs to control how the produce this feedback. They take the form of the generator property being exposed, which can either be set to nil to remove the feedback for this generator, or to a different object if the client wants a custom feedback experience (typically, the same object created with a different style).
Exposing the feedback generators instead of just boolean properties allows for future API extension without needing to change all the UIKit component APIs again and focus only on the feedback generator class and subclasses.
UISwitch API Additions
UISwitch uses the retarget generator to provide feedback when the switch flips value.
Objective-C
@interface UISwitch ( )
@property (nonatomic, strong, nullable) UIImpactFeedbackGenerator*impactFeedbackGenerator;
@end
UIPickerView API Additions
UIPickerView uses the retarget generator to provide feedback when a component (wheel) of the picker view changes selection.
Objective-C
@interface UIPickerView ( )
@property (nonatomic, strong, nullable) UIRetargetFeedbackGenerator*retargetFeedbackGenerator;
@end
UIDatePicker API Additions
UIDatePicker uses the retarget generator to provide feedback when a component (wheel) of the date picker changes selection.
Objective-C
@interface UIDatePicker ( )
@property (nonatomic, strong, nullable) UIRetargetFeedbackGenerator*retargetFeedbackGenerator
@end
UIRefreshControl API Additions
UIRefreshControl uses the impact generator to provide feedback when the control begins refreshing.
Objective-C
@interface UIRefreshControl ( )
@property (nonatomic, strong, nullable) UIImpactFeedbackGenerator*refreshFeedbackGenerator;
@end
UIScrollView API Additions
UIScrollView uses the edge generator to provide feedback when the user reaches an edge of the scrollable content area (where the rubber band effect begins), as well as when the user reaches a zoom limit when pinching with two fingers. Because scroll view can scroll horizontally and vertically, it uses two separate edge generators, one per axis. It also uses one zoom edge generator.
Objective-C
interface UIScrollView ( )
@property (nonatomic, strong, nullable) UIEdgeFeedbackGenerator*horizontalFeedbackGenerator;
@property (nonatomic, strong, nullable) UIEdgeFeedbackGenerator*verticalFeedbackGenerator;
@property (nonatomic, strong, nullable) UIZoomEdgeFeedbackGenerator*zoomFeedbackGenerator;
@end
UISlider API Additions
UISlider uses the edge generator to provide feedback when the slider's thumb (indicator knob) reaches the left or right edge of the slider. Because slider is strictly horizontal, it exposes a single edge generator.
Objective-C
@interface UISlider ( )
@property (nonatomic, strong, nullable) UIEdgeFeedbackGenerator*edgeFeedbackGenerator;
@end
UITableView API Additions
UITableView uses the drag generator to provide feedback when the user reorders rows in the table view, and a retarget generator when the user switched to another section using the index bar.
Objective-C
interface UITableView ( )
@property (nonatomic, strong, nullable) UIRetargetFeedbackGenerator*indexRetargetFeedbackGenerator;
@property (nonatomic, strong, nullable) UIDragSnappin:gFeedbackGenerator*reorderFeedbackGenerator;
@end
UICollectionView API Additions
UICollectionView uses the drag generator to provide feedback when the user reorders items in the collection view.
Objective-C
@interface UICollectionView ( )
@property (nonatomic, strong, nullable)
UIDragSnappingFeedbackGenerator*reorderFeedbackGenerator;
@end
This application is a continuation application of U.S. application Ser. No. 16/240,684, filed Jan. 4, 2019, which is a continuation application of U.S. application Ser. No. 15/688,754, filed Aug. 28, 2017, now U.S. Pat. No. 10,175,762, which is a continuation application of U.S. application Ser. No. 15/271,073, filed Sep. 20, 2016, now U.S. Pat. No. 9,753,541, which claims priority to U.S. Provisional Application Ser. No. 62/384,159, filed Sep. 6, 2016, all of which are incorporated by reference herein in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5959624 | Johnston, Jr. et al. | Sep 1999 | A |
| 5990869 | Kubica et al. | Nov 1999 | A |
| 6424251 | Byre | Jul 2002 | B1 |
| 6433771 | Yocum et al. | Aug 2002 | B1 |
| 6560165 | Barker | May 2003 | B1 |
| 7130664 | Williams | Oct 2006 | B1 |
| 7305257 | Ladouceur et al. | Dec 2007 | B2 |
| 7308253 | Moody et al. | Dec 2007 | B2 |
| 7469381 | Ording | Dec 2008 | B2 |
| 7479949 | Jobs et al. | Jan 2009 | B2 |
| 7720213 | Desai et al. | May 2010 | B2 |
| 7809406 | Weinans | Oct 2010 | B2 |
| 7978183 | Rosenberg et al. | Jul 2011 | B2 |
| 8026814 | Heinze et al. | Sep 2011 | B1 |
| 8131848 | Denise | Mar 2012 | B1 |
| 8165640 | Mullen | Apr 2012 | B2 |
| 8204548 | Blinn et al. | Jun 2012 | B1 |
| 8207832 | Yun et al. | Jun 2012 | B2 |
| 8209606 | Ording | Jun 2012 | B2 |
| 8266550 | Cleron et al. | Sep 2012 | B1 |
| 8331268 | Hicks, III | Dec 2012 | B2 |
| 8509856 | Blinn et al. | Aug 2013 | B1 |
| 8548418 | Jintaseranee et al. | Oct 2013 | B1 |
| 8619051 | Lacroix et al. | Dec 2013 | B2 |
| 8624864 | Birnbaum et al. | Jan 2014 | B2 |
| 8659571 | Birnbaum et al. | Feb 2014 | B2 |
| 8676274 | Li | Mar 2014 | B2 |
| 8698766 | Ali et al. | Apr 2014 | B2 |
| 8717151 | Forutanpour et al. | May 2014 | B2 |
| 8750296 | Bosschaert et al. | Jun 2014 | B2 |
| 8754757 | Ullrich et al. | Jun 2014 | B1 |
| 8768838 | Hoffman | Jul 2014 | B1 |
| 8773356 | Martin et al. | Jul 2014 | B2 |
| 8886252 | Luke et al. | Nov 2014 | B2 |
| 8886576 | Sanketi et al. | Nov 2014 | B1 |
| 9088668 | Salvador | Jul 2015 | B1 |
| 9092953 | Mortimer et al. | Jul 2015 | B1 |
| 9100805 | Oshita | Aug 2015 | B2 |
| 9110529 | Kido | Aug 2015 | B2 |
| 9166823 | Karmarkar | Oct 2015 | B2 |
| 9189932 | Kerdemelidis | Nov 2015 | B2 |
| 9247525 | Jacobs et al. | Jan 2016 | B2 |
| 9357052 | Ullrich | May 2016 | B2 |
| 9411422 | McClendon et al. | Aug 2016 | B1 |
| 9430796 | So | Aug 2016 | B1 |
| 9509829 | Culbert et al. | Nov 2016 | B2 |
| 9542820 | Moussette et al. | Jan 2017 | B2 |
| 9548050 | Gruber et al. | Jan 2017 | B2 |
| 9588586 | Rihn | Mar 2017 | B2 |
| 9690382 | Moussette et al. | Jun 2017 | B1 |
| 9830784 | Moussette et al. | Nov 2017 | B2 |
| 9852590 | Bhatia | Dec 2017 | B2 |
| 9864432 | Moussette et al. | Jan 2018 | B1 |
| 9928699 | Moussette et al. | Mar 2018 | B2 |
| 9984539 | Moussette et al. | May 2018 | B2 |
| 10034129 | Ellis et al. | Jul 2018 | B1 |
| 10276000 | Moussette et al. | Apr 2019 | B2 |
| 20010002126 | Rosenberg et al. | May 2001 | A1 |
| 20020080112 | Braun et al. | Jun 2002 | A1 |
| 20020115478 | Fujisawa et al. | Aug 2002 | A1 |
| 20040088353 | Mendelsohn et al. | May 2004 | A1 |
| 20040095311 | Tarlton et al. | May 2004 | A1 |
| 20040213401 | Aupperle et al. | Oct 2004 | A1 |
| 20040233161 | Shahoian et al. | Nov 2004 | A1 |
| 20050231489 | Ladouceur et al. | Oct 2005 | A1 |
| 20050275638 | Kolmykov-Zotov et al. | Dec 2005 | A1 |
| 20050285846 | Funaki | Dec 2005 | A1 |
| 20060026521 | Hotelling et al. | Feb 2006 | A1 |
| 20060026535 | Hotelling et al. | Feb 2006 | A1 |
| 20060045252 | Gorti et al. | Mar 2006 | A1 |
| 20060248183 | Barton | Nov 2006 | A1 |
| 20070046627 | Soh et al. | Mar 2007 | A1 |
| 20070055770 | Karmakar et al. | Mar 2007 | A1 |
| 20070088560 | Mock et al. | Apr 2007 | A1 |
| 20070106457 | Rosenberg | May 2007 | A1 |
| 20070146316 | Poupyrev et al. | Jun 2007 | A1 |
| 20070193436 | Chu | Aug 2007 | A1 |
| 20070226646 | Nagiyama et al. | Sep 2007 | A1 |
| 20070274503 | Klemm et al. | Nov 2007 | A1 |
| 20070283239 | Morris | Dec 2007 | A1 |
| 20080024459 | Poupyrev et al. | Jan 2008 | A1 |
| 20080122796 | Jobs et al. | May 2008 | A1 |
| 20080174570 | Jobs et al. | Jul 2008 | A1 |
| 20080270931 | Bamford | Oct 2008 | A1 |
| 20090075694 | Kim et al. | Mar 2009 | A1 |
| 20090085878 | Heubel et al. | Apr 2009 | A1 |
| 20090128581 | Brid et al. | May 2009 | A1 |
| 20090135142 | Fu et al. | May 2009 | A1 |
| 20090167509 | Fadell et al. | Jul 2009 | A1 |
| 20090167704 | Terlizzi et al. | Jul 2009 | A1 |
| 20090178008 | Herz et al. | Jul 2009 | A1 |
| 20090215432 | Matsuoka | Aug 2009 | A1 |
| 20090215479 | Karmarkar | Aug 2009 | A1 |
| 20090222902 | Bender et al. | Sep 2009 | A1 |
| 20090231271 | Heubel et al. | Sep 2009 | A1 |
| 20090284463 | Morimoto et al. | Nov 2009 | A1 |
| 20090292990 | Park et al. | Nov 2009 | A1 |
| 20090303031 | Strohallen et al. | Dec 2009 | A1 |
| 20090322497 | Ku et al. | Dec 2009 | A1 |
| 20090325645 | Bang et al. | Dec 2009 | A1 |
| 20090325647 | Cho et al. | Dec 2009 | A1 |
| 20100017489 | Birnbaum et al. | Jan 2010 | A1 |
| 20100099445 | Song et al. | Apr 2010 | A1 |
| 20100114974 | Jung et al. | May 2010 | A1 |
| 20100141411 | Ahn et al. | Jun 2010 | A1 |
| 20100144395 | Komiya | Jun 2010 | A1 |
| 20100156818 | Burrough et al. | Jun 2010 | A1 |
| 20100231367 | Cruz-Hernandez et al. | Sep 2010 | A1 |
| 20100231534 | Chaudhri et al. | Sep 2010 | A1 |
| 20100231537 | Pisula et al. | Sep 2010 | A1 |
| 20100267424 | Kim et al. | Oct 2010 | A1 |
| 20100299638 | Choi | Nov 2010 | A1 |
| 20100302003 | Zellner | Dec 2010 | A1 |
| 20100302042 | Barnett et al. | Dec 2010 | A1 |
| 20110001707 | Faubert et al. | Jan 2011 | A1 |
| 20110017828 | Pine | Jan 2011 | A1 |
| 20110018695 | Bells et al. | Jan 2011 | A1 |
| 20110053577 | Lee et al. | Mar 2011 | A1 |
| 20110074695 | Rapp et al. | Mar 2011 | A1 |
| 20110081889 | Gao et al. | Apr 2011 | A1 |
| 20110102349 | Harris | May 2011 | A1 |
| 20110126148 | Krishnaraj et al. | May 2011 | A1 |
| 20110141142 | Leffert et al. | Jun 2011 | A1 |
| 20110148608 | Grant et al. | Jun 2011 | A1 |
| 20110179388 | Fleizach et al. | Jul 2011 | A1 |
| 20110190595 | Bennett et al. | Aug 2011 | A1 |
| 20110202843 | Morris | Aug 2011 | A1 |
| 20110210926 | Pasquero et al. | Sep 2011 | A1 |
| 20110252346 | Chaudhri et al. | Oct 2011 | A1 |
| 20110264491 | Birnbaum et al. | Oct 2011 | A1 |
| 20110266375 | Ono et al. | Nov 2011 | A1 |
| 20110267181 | Kildal | Nov 2011 | A1 |
| 20110267294 | Kildal | Nov 2011 | A1 |
| 20110270358 | Davis et al. | Nov 2011 | A1 |
| 20110271181 | Tsai et al. | Nov 2011 | A1 |
| 20110279380 | Weber et al. | Nov 2011 | A1 |
| 20110279381 | Tong et al. | Nov 2011 | A1 |
| 20110316698 | Palin et al. | Dec 2011 | A1 |
| 20120019365 | Tuikka et al. | Jan 2012 | A1 |
| 20120026110 | Yamano | Feb 2012 | A1 |
| 20120027216 | Tirry et al. | Feb 2012 | A1 |
| 20120028577 | Rodriguez et al. | Feb 2012 | A1 |
| 20120050324 | Jeong et al. | Mar 2012 | A1 |
| 20120056806 | Rosenberg et al. | Mar 2012 | A1 |
| 20120062491 | Coni et al. | Mar 2012 | A1 |
| 20120105367 | Son et al. | May 2012 | A1 |
| 20120173770 | Walker et al. | Jul 2012 | A1 |
| 20120174033 | Joo | Jul 2012 | A1 |
| 20120191704 | Jones | Jul 2012 | A1 |
| 20120216139 | Ording et al. | Aug 2012 | A1 |
| 20120229276 | Ronkainen | Sep 2012 | A1 |
| 20120249461 | Flanagan et al. | Oct 2012 | A1 |
| 20120268412 | Cruz-Hernandez et al. | Oct 2012 | A1 |
| 20120286943 | Rothkopf et al. | Nov 2012 | A1 |
| 20120286944 | Forutanoour et al. | Nov 2012 | A1 |
| 20120299857 | Grant et al. | Nov 2012 | A1 |
| 20120299859 | Kinoshita | Nov 2012 | A1 |
| 20120306631 | Hughes | Dec 2012 | A1 |
| 20120306632 | Fleizach et al. | Dec 2012 | A1 |
| 20120306790 | Kyung et al. | Dec 2012 | A1 |
| 20120311477 | Mattos et al. | Dec 2012 | A1 |
| 20120327006 | Israr et al. | Dec 2012 | A1 |
| 20130091462 | Gray et al. | Apr 2013 | A1 |
| 20130165226 | Thorner | Jun 2013 | A1 |
| 20130167058 | Levee et al. | Jun 2013 | A1 |
| 20130174137 | Kim | Jul 2013 | A1 |
| 20130201115 | Heubel | Aug 2013 | A1 |
| 20130222224 | Eriksson et al. | Aug 2013 | A1 |
| 20130225300 | Brinlee | Aug 2013 | A1 |
| 20130234929 | Libin | Sep 2013 | A1 |
| 20130244633 | Jacobs et al. | Sep 2013 | A1 |
| 20130262298 | Morley | Oct 2013 | A1 |
| 20130265268 | Okumura et al. | Oct 2013 | A1 |
| 20130282325 | Takahashi et al. | Oct 2013 | A1 |
| 20130290442 | Dgani | Oct 2013 | A1 |
| 20130300684 | Kim et al. | Nov 2013 | A1 |
| 20130307786 | Heubel | Nov 2013 | A1 |
| 20130316744 | Newham et al. | Nov 2013 | A1 |
| 20130318437 | Jung et al. | Nov 2013 | A1 |
| 20130321317 | Hirukawa | Dec 2013 | A1 |
| 20130326367 | Nakamura et al. | Dec 2013 | A1 |
| 20130332721 | Chaudhri et al. | Dec 2013 | A1 |
| 20140002386 | Rosenberg et al. | Jan 2014 | A1 |
| 20140007005 | Libin et al. | Jan 2014 | A1 |
| 20140024414 | Fuji | Jan 2014 | A1 |
| 20140039900 | Heubel et al. | Feb 2014 | A1 |
| 20140059427 | Dombrowski et al. | Feb 2014 | A1 |
| 20140074716 | Ni | Mar 2014 | A1 |
| 20140075375 | Hwang et al. | Mar 2014 | A1 |
| 20140082501 | Bae et al. | Mar 2014 | A1 |
| 20140091857 | Bernstein | Apr 2014 | A1 |
| 20140092037 | Kim | Apr 2014 | A1 |
| 20140132568 | Hirose et al. | May 2014 | A1 |
| 20140168110 | Araki et al. | Jun 2014 | A1 |
| 20140176415 | Buuck et al. | Jun 2014 | A1 |
| 20140176452 | Aleksov et al. | Jun 2014 | A1 |
| 20140176455 | Araki et al. | Jun 2014 | A1 |
| 20140181222 | Geris et al. | Jun 2014 | A1 |
| 20140181756 | Kuo | Jun 2014 | A1 |
| 20140197946 | Park et al. | Jul 2014 | A1 |
| 20140207880 | Malkin et al. | Jul 2014 | A1 |
| 20140210740 | Lee | Jul 2014 | A1 |
| 20140215494 | Kim | Jul 2014 | A1 |
| 20140218317 | Aberg et al. | Aug 2014 | A1 |
| 20140232657 | Aviles et al. | Aug 2014 | A1 |
| 20140253319 | Chang | Sep 2014 | A1 |
| 20140258857 | Dykstra-Erickson et al. | Sep 2014 | A1 |
| 20140267076 | Birnbaum et al. | Sep 2014 | A1 |
| 20140273858 | Panther et al. | Sep 2014 | A1 |
| 20140281924 | Chipman et al. | Sep 2014 | A1 |
| 20140292501 | Lim et al. | Oct 2014 | A1 |
| 20140292668 | Fricklas et al. | Oct 2014 | A1 |
| 20140292706 | Hunt et al. | Oct 2014 | A1 |
| 20140300454 | Lacroix et al. | Oct 2014 | A1 |
| 20140320402 | Stahlberg | Oct 2014 | A1 |
| 20140320431 | Cruz-Hernandez et al. | Oct 2014 | A1 |
| 20140320435 | Modarres et al. | Oct 2014 | A1 |
| 20140329567 | Chan et al. | Nov 2014 | A1 |
| 20140333564 | Hong et al. | Nov 2014 | A1 |
| 20140340316 | Gu et al. | Nov 2014 | A1 |
| 20140351698 | Nakagawa | Nov 2014 | A1 |
| 20140358709 | Wu | Dec 2014 | A1 |
| 20140363113 | McGavran et al. | Dec 2014 | A1 |
| 20140368440 | Polyakov et al. | Dec 2014 | A1 |
| 20150002477 | Cheatham, III et al. | Jan 2015 | A1 |
| 20150020015 | Zhou | Jan 2015 | A1 |
| 20150050966 | West | 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 |
| 20150067563 | Bernstein et al. | Mar 2015 | A1 |
| 20150067596 | Brown et al. | Mar 2015 | A1 |
| 20150070153 | Bhatia | Mar 2015 | A1 |
| 20150070260 | Saboune et al. | Mar 2015 | A1 |
| 20150077335 | Taguchi et al. | Mar 2015 | A1 |
| 20150078586 | Ang et al. | Mar 2015 | A1 |
| 20150089613 | Tippett et al. | Mar 2015 | A1 |
| 20150097657 | Gandhi et al. | Apr 2015 | A1 |
| 20150103028 | Ruemelin et al. | Apr 2015 | A1 |
| 20150116205 | Westerman et al. | Apr 2015 | A1 |
| 20150116239 | Kaplan et al. | Apr 2015 | A1 |
| 20150134531 | Xia | May 2015 | A1 |
| 20150135109 | Zambetti et al. | May 2015 | A1 |
| 20150138046 | Kerdemelidis | May 2015 | A1 |
| 20150145656 | Levesque et al. | May 2015 | A1 |
| 20150145657 | Levesque et al. | May 2015 | A1 |
| 20150149899 | Bernstein et al. | May 2015 | A1 |
| 20150153828 | Monkhouse et al. | Jun 2015 | A1 |
| 20150153830 | Hirose et al. | Jun 2015 | A1 |
| 20150156196 | Kim et al. | Jun 2015 | A1 |
| 20150169059 | Behles et al. | Jun 2015 | A1 |
| 20150199172 | Ringuette et al. | Jul 2015 | A1 |
| 20150201065 | Shim et al. | Jul 2015 | A1 |
| 20150227204 | Gipson et al. | Aug 2015 | A1 |
| 20150227280 | Westerman et al. | Aug 2015 | A1 |
| 20150227589 | Chakrabarti et al. | Aug 2015 | A1 |
| 20150234464 | Yliaho | Aug 2015 | A1 |
| 20150244848 | Park et al. | Aug 2015 | A1 |
| 20150253835 | Yu | Sep 2015 | A1 |
| 20150254570 | Florence et al. | Sep 2015 | A1 |
| 20150254947 | Komori et al. | Sep 2015 | A1 |
| 20150261296 | Yoshikawa | Sep 2015 | A1 |
| 20150261387 | Petersen | Sep 2015 | A1 |
| 20150268725 | Levesque et al. | Sep 2015 | A1 |
| 20150286288 | Lee et al. | Oct 2015 | A1 |
| 20150293592 | Cheong et al. | Oct 2015 | A1 |
| 20150301838 | Steeves | Oct 2015 | A1 |
| 20150323996 | Obana et al. | Nov 2015 | A1 |
| 20150332226 | Wu et al. | Nov 2015 | A1 |
| 20150332565 | Cho et al. | Nov 2015 | A1 |
| 20150346916 | Jisrawi et al. | Dec 2015 | A1 |
| 20150347010 | Yang et al. | Dec 2015 | A1 |
| 20150350146 | Cary et al. | Dec 2015 | A1 |
| 20150365306 | Chaudhri et al. | Dec 2015 | A1 |
| 20160007290 | Lindemann et al. | Jan 2016 | A1 |
| 20160034152 | Wilson et al. | Feb 2016 | A1 |
| 20160034253 | Bang et al. | Feb 2016 | A1 |
| 20160041750 | Cieplinski et al. | Feb 2016 | A1 |
| 20160062464 | Moussette et al. | Mar 2016 | A1 |
| 20160062465 | Moussette et al. | Mar 2016 | A1 |
| 20160062466 | Moussette et al. | Mar 2016 | A1 |
| 20160062467 | Buxton et al. | Mar 2016 | A1 |
| 20160062590 | Karunamuni et al. | Mar 2016 | A1 |
| 20160063496 | Royyuru et al. | Mar 2016 | A1 |
| 20160063825 | Moussette et al. | Mar 2016 | A1 |
| 20160063826 | Morrell et al. | Mar 2016 | A1 |
| 20160063827 | Moussette et al. | Mar 2016 | A1 |
| 20160063828 | Moussette et al. | Mar 2016 | A1 |
| 20160063850 | Yang et al. | Mar 2016 | A1 |
| 20160065525 | Dye et al. | Mar 2016 | A1 |
| 20160123745 | Cotier et al. | May 2016 | A1 |
| 20160161922 | Shin | Jun 2016 | A1 |
| 20160165038 | Lim et al. | Jun 2016 | A1 |
| 20160179203 | Modarres et al. | Jun 2016 | A1 |
| 20160187988 | Levesque et al. | Jun 2016 | A1 |
| 20160205244 | Dvortsov et al. | Jul 2016 | A1 |
| 20160246376 | Birnbaum et al. | Aug 2016 | A1 |
| 20160259435 | Qian | Sep 2016 | A1 |
| 20160259499 | Kocienda et al. | Sep 2016 | A1 |
| 20160259519 | Foss et al. | Sep 2016 | A1 |
| 20160259528 | Foss et al. | Sep 2016 | A1 |
| 20160259542 | Chaudhri et al. | Sep 2016 | A1 |
| 20160295010 | Miller | Oct 2016 | A1 |
| 20160313875 | Williams et al. | Oct 2016 | A1 |
| 20160342973 | Jueng et al. | Nov 2016 | A1 |
| 20160349936 | Cho et al. | Dec 2016 | A1 |
| 20160357354 | Chen et al. | Dec 2016 | A1 |
| 20160357362 | Gauci et al. | Dec 2016 | A1 |
| 20160357363 | Decker et al. | Dec 2016 | A1 |
| 20170011210 | Cheong et al. | Jan 2017 | A1 |
| 20170031495 | Smith | Feb 2017 | A1 |
| 20170046024 | Dascola et al. | Feb 2017 | A1 |
| 20170068511 | Brown et al. | Mar 2017 | A1 |
| 20170075520 | Bauer et al. | Mar 2017 | A1 |
| 20170075534 | Leschenko | Mar 2017 | A1 |
| 20170102916 | Noble et al. | Apr 2017 | A1 |
| 20170357317 | Chaudhri et al. | Dec 2017 | A1 |
| 20170357318 | Chaudhri et al. | Dec 2017 | A1 |
| 20170357319 | Chaudhri et al. | Dec 2017 | A1 |
| 20170357320 | Chaudhri et al. | Dec 2017 | A1 |
| 20170358181 | Moussette et al. | Dec 2017 | A1 |
| 20180067557 | Robert et al. | Mar 2018 | A1 |
| 20180082552 | Moussette et al. | Mar 2018 | A1 |
| 20180129292 | Moussette et al. | May 2018 | A1 |
| 20180204425 | Moussette et al. | Jul 2018 | A1 |
| 20180335848 | Moussette et al. | Nov 2018 | A1 |
| 20180367489 | Dye et al. | Dec 2018 | A1 |
| 20190050055 | Chaudhri et al. | Feb 2019 | A1 |
| 20190138103 | Robert et al. | May 2019 | A1 |
| 20190213846 | Moussette et al. | Jul 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 2016100246 | Apr 2016 | AU |
| 101375582 | Feb 2009 | CN |
| 101631162 | Jan 2010 | CN |
| 101901048 | Dec 2010 | CN |
| 102330123 | Feb 2012 | CN |
| 102484664 | May 2012 | CN |
| 102609078 | Jul 2012 | CN |
| 102651920 | Aug 2012 | CN |
| 103503428 | Jan 2014 | CN |
| 103649885 | Mar 2014 | CN |
| 1038438424 | Jun 2014 | CN |
| 104049746 | Sep 2014 | CN |
| 104123035 | Oct 2014 | CN |
| 104321723 | Jan 2015 | CN |
| 104412201 | Mar 2015 | CN |
| 104423595 | Mar 2015 | CN |
| 104508618 | Apr 2015 | CN |
| 104598149 | May 2015 | CN |
| 104903835 | Sep 2015 | CN |
| 105260049 | Jan 2016 | CN |
| 102010048745 | Apr 2012 | DE |
| 2 141 569 | Jan 2010 | EP |
| 2 194 697 | Jun 2010 | EP |
| 2 328 063 | Jan 2011 | EP |
| 2 378 406 | Oct 2011 | EP |
| 2 386 935 | Nov 2011 | EP |
| 2 434 387 | Mar 2012 | EP |
| 2 728 445 | May 2014 | EP |
| 2 733 575 | May 2014 | EP |
| 2 821 912 | Jan 2015 | EP |
| 2 827 225 | Jan 2015 | EP |
| 2 846 226 | Mar 2015 | EP |
| 2 846 549 | Mar 2015 | EP |
| 2 847 658 | Mar 2015 | EP |
| 2 857 933 | Apr 2015 | EP |
| 2 950 192 | Dec 2015 | EP |
| 2 955 608 | Dec 2015 | EP |
| 2 977 859 | Jan 2016 | EP |
| 2532766 | Jun 2016 | GB |
| 2533572 | Jun 2016 | GB |
| 2000209311 | Jul 2000 | JP |
| 2004064117 | Feb 2004 | JP |
| 2004363999 | Dec 2004 | JP |
| 2008282125 | Nov 2008 | JP |
| 2010114702 | May 2010 | JP |
| 2010136151 | Jun 2010 | JP |
| 2011159110 | Aug 2011 | JP |
| 2013503578 | Jan 2013 | JP |
| 2013162167 | Aug 2013 | JP |
| 201300879 | Oct 2013 | JP |
| 20130075412 | Jul 2013 | KR |
| 20140002563 | Jan 2014 | KR |
| 20140025552 | Mar 2014 | KR |
| 20150013264 | Feb 2015 | KR |
| I388995 | Mar 2013 | TW |
| WO 0124158 | Apr 2001 | WO |
| WO 2004053830 | Jun 2004 | WO |
| WO 2008075082 | Jun 2008 | WO |
| WO 2012081182 | Jun 2012 | WO |
| WO 2013089294 | Jun 2013 | WO |
| WO 2013156815 | Oct 2013 | WO |
| WO 2013169300 | Nov 2013 | WO |
| WO 2013169853 | Nov 2013 | WO |
| WO 2013169854 | Nov 2013 | WO |
| WO 2013169865 | Nov 2013 | WO |
| WO 2013169875 | Nov 2013 | WO |
| WO 2013173838 | Nov 2013 | WO |
| WO 2014095756 | Jun 2014 | WO |
| WO 2014105275 | Jul 2014 | WO |
| WO 2015116056 | Aug 2015 | WO |
| WO 2016036509 | Mar 2016 | WO |
| WO 2016171848 | Oct 2016 | WO |
| WO 2017027526 | Feb 2017 | WO |
| WO 2017065365 | Apr 2017 | WO |
| Entry |
|---|
| Patent, dated Jul. 12, 2019, received in Danish Patent Application No. 2017 70369, which corresonds with U.S. Appl. No. 15/619,359, 4 pages. |
| Office Action, dated Jul. 23, 2109, received in Chinese Patent Application No. 2018110167326.2, which corresponds with U.S. Appl. No. 15/275,083, 6 pages. |
| Notice of Allowance, dated Jul. 24, 2019, received in U.S. Appl. No. 15/823,436, 5 pages. |
| European Search Report, dated Jul. 16, 2019, received in European Patent Application No. 19168886.0, which corresponds with U.S. Appl. No. 15/270,885, 6 pages. |
| Dosher et al., “Human Interaction with Small Haptic Effects”, University of Washington, Seattle, WA, Jun. 2005, 16 pages. |
| Immersion, “The Value of Haptics”, San Jose, California, 2010, 12 pages. |
| Sulaiman et al., “User Haptic Experience and the Design of Drawing Interfaces”, Interacting with Computers, http://doi.org/10.1016/j.intcom.2009.11.009, Dec. 5, 2009, 20 pages. |
| VladMaxSoft, “Make Your iPhone Ring Louder When Inside a Pocket or Bag with Ringing Pocket Tweak”, https://www.reddit.com/r/jailbreak/comments/1zj6zx/release_make_your_iphone_ring_louder_when_inside/, Mar. 4, 2014, 8 pages. |
| Notice of Allowance, dated Jan. 31, 2018, received in U.S. Appl. No. 15/619,359, 8 pages. |
| Notice of Allowance, dated Oct. 2, 2017, received in U.S. Appl. No. 15/619,359, 9 pages. |
| Certificate of Grant, dated May 18, 2017, received in Australian Patent Application No. 2017100482, which corresponds with U.S. Appl. No. 15/619,359, 1 page. |
| Office Action, dated Jun. 27, 2017, received in Australian Patent Application No. 2017100482, which corresponds with U.S. Appl. No. 15/619,359, 7 pages. |
| Certificate of Examination, dated Oct. 27, 2017, received in Australian Patent Application No. 2017100482, which corresponds with U.S. Appl. No. 15/619,359, 1 page. |
| Office Action, dated May 23, 2019, received in Australian Patent Application No. 2017286532, which corresponds with U.S. Appl. No. 15/619,359, 3 pages. |
| Office Action, dated May 10, 2019, received in European Patent Application No. 17733235.0, which corresponds with U.S. Appl. No. 15/619,359, 9 pages. |
| Office Action, dated Jan. 24, 2018, received in Danish Patent Application No. 201770369, which corresponds with U.S. Appl. No. 15/619,359, 6 pages. |
| Office Action, dated Aug. 6, 2018, received in Danish Patent Application No. 201770369, which corresponds with U.S. Appl. No. 15/619,359, 5 pages. |
| Intention to Grant, dated Jul. 4, 2019, received in Danish Patent Application No. 201770369, which corresponds with U.S. Appl. No. 15/619,359, 2 pages. |
| Grant, dated Jul. 8, 2019, received in Danish Patent Application No. 201770369, which corresponds with U.S. Appl. No. 15/619,359, 2 pages. |
| Notice of Allowance, dated Dec. 14, 2016, received in U.S. Appl. No. 15/270,885, 13 pages. |
| Notice of Allowance, dated Apr. 10, 2017, received in U.S. Appl. No. 15/270,885, 5 pages. |
| Notice of Allowance, dated Jul. 21, 2017, received in U.S. Appl. No. 15/270,885, 10 pages. |
| Notice of Allowance, dated Nov. 22, 2017, received in U.S. Appl. No. 15/270,885, 5 pages. |
| Notice of Acceptance, dated Aug. 18, 2017, received in Australian Patent Application No. 2017216447, which corresponds with U.S. Appl. No. 15/270,885, 3 pages. |
| Grant, dated Dec. 21, 2017, received in Australian Application No. 2017216447, which corresponds with U.S. Appl. No. 15/270,885, 1 page. |
| Notice of Acceptance, dated Aug. 21, 2017, received in Australian Patent Application No. 2017216475, which corresponds with U.S. Appl. No. 15/270,885, 3 pages. |
| Grant, dated Dec. 21, 2017, received in Australian Application No. 2017216475, which corresponds with U.S. Appl. No. 15/270,885, 1 page. |
| Office Action, dated Mar. 22, 2019, received in Australian Patent Application No. 2017251751, which corresponds with U.S. Appl. No. 15/270,885, 3 pages. |
| Office Action, dated Feb. 2, 2019, received in Chinese Patent Application No. 2017107348777, which corresponds with U.S. Appl. No. 15/270,885, 10 pages. |
| Office Action, dated Jan. 5, 2017, received in Danish Patent Application No. 201670721, which corresponds with U.S. Appl. No. 15/270,885, 7 pages. |
| Office Action, dated Jul. 20, 2017, received in Danish Patent Application No. 201670721, which corresponds with U.S. Appl. No. 15/270,885, 2 pages. |
| Decision to Grant, dated Oct. 25, 2017, received in Danish Patent Application No. 201670721, which corresponds with U.S. Appl. No. 15/270,885, 2 pages. |
| Office action, dated Jan. 18, 2017, received in Danish Patent Application No. 201670726, which corresponds with U.S. Appl. No. 15/270,885, 7 pages. |
| Office Action, dated Apr. 5, 2017, received in Danish Patent Application No. 201670726, which corresponds with U.S. Appl. No. 15/270,885, 2 pages. |
| Notice of Allowance, dated Jul. 18, 2017, received in Danish Patent Application No. 201670726, which corresponds with U.S. Appl. No. 15/270,885, 2 pages. |
| Patent, dated Oct. 16, 2017, received in Danish Patent Application No. 201670726, which corresponds with U.S. Appl. No. 15/270,885, 2 pages. |
| Office Action, dated Aug. 25, 2017, received in European patent Application No. 17177160.3, which corresponds with U.S. Appl. No. 15/270,885, 3 pages. |
| Office Action, dated Jan. 24, 2018, received in European Patent Application No. 17177160.3, which corresponds with U.S. Appl. No. 15/270,885, 4 pages. |
| Intention to Grant, dated Dec. 7, 2018, received in European Patent Application No. 17177160.3, which corresponds with U.S. Appl. No. 15/270,885, 7 pages. |
| Decision to Grant, dated May 16, 2019, received in European Patent Application No. 17177160.3, which corresponds with U.S. Appl. No. 15/270,885, 1 page. |
| Patent, dated Jun. 12, 2019, received in European Patent Application No. 17177160.3, which corresponds with U.S. Appl. No. 15/270,885, 3 page. |
| Intention to Grant, dated Feb. 1, 2019, received in European Patent Application No. 17177493.8, which corresponds with U.S. Appl. No. 15/270,885, 4 pages. |
| Decision to Grant, dated Apr. 18, 2019, received in European Patent Application No. 17177493.8, which corresponds with U.S. Appl. No. 15/270,885, 4 pages. |
| Patent, dated May 27, 2019, received in European Patent Application No. 17177493.8, which corresponds with U.S. Appl. No. 15/270,885, 2 pages. |
| Office Action, dated Jan. 17, 2017, received in U.S. Appl. No. 15/271,073, 8 pages. |
| Notice of Allowance, dated May 2, 2017, received in U.S. Appl. No. 15/271,073, 5 pages. |
| Notice of Allowance, dated Aug. 21, 2017, received in Australian Application No. 2017213578, which corresponds with U.S. Appl. No. 15/271,073, 3 pages. |
| Grant, dated Dec. 21, 2017, received in Australian Application No. 2017213578, which corresponds with U.S. Appl. No. 15/271,073, 1 page. |
| Notice of Allowance, dated Sep. 7, 2017, received in Australian Application No. 2017216471, which corresponds with U.S. Appl. No. 15/271,073, 3 pages. |
| Grant, dated Dec. 21, 2017, received in Australian Application No. 2017216471, which corresponds with U.S. Appl. No. 15/271,073, 1 page. |
| Notice of Allowance, dated Aug. 24, 2017, received in Australian Application No. 2017216453, which corresponds with U.S. Appl. No. 15/271,073, 3 pages. |
| Grant, dated Dec. 21, 2017, received in Australian Application No. 2017216453, which corresponds with U.S. Appl. No. 15/271,073, 1 page. |
| Office Action, dated Oct. 5, 2018, received in Australian Patent Application No. 201761484, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Notice of Acceptance, dated Apr. 26, 2019, received in Australian Patent Application No. 201761484, which corresponds with U.S. Appl. No. 15/271,073, 3 pages. |
| Office Action, dated Sep. 8, 2017, received in Chinese Application No. 201710735308.4, which corresponds with U.S. Appl. No. 15/271,073, 4 pages. |
| Office Action, dated Jan. 3, 2019, received in Chinese Application No. 201710735308.4, which corresponds with U.S. Appl. No. 15/271,073, 6 pages. |
| Notice of Allowance, dated Jul. 1, 2019, received in Chinese Application No. 201710735308.4, which corresponds with U.S. Appl. No. 15/271,073, 5 pages. |
| Office Action, dated Jan. 20, 2017, received in Danish Patent Application No. 201670720, which corresponds with U.S. Appl. No. 15/271,073, 9 pages. |
| Office Action, dated Sep. 4, 2017, received in Danish Patent Application No. 201670720, which corresponds with U.S. Appl. No. 15/271,073, 4 pages. |
| Office Action, dated Aug. 14, 2018, received in Danish Patent Application No. 201670720, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Office Action, dated Apr. 5, 2017, received in Danish Patent Application No. 2016-70724, which corresponds with U.S. Appl. No. 15/271,073, 5 pages. |
| Office Action, dated Aug. 1, 2017, received in Danish Patent Application No. 2016-70724, which corresponds with U.S. Appl. No. 15/271,073, 5 pages. |
| Office Action, dated Feb. 14, 2018, received in Danish Patent Application No. 2016-70724, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Notice of Allowance, dated Feb. 13, 2019, received in Danish Patent Application No. 2016-70724, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Office Action, dated Jan. 25, 2017, received in Danish Patent Application No. 201670725, which corresponds with U.S. Appl. No. 15/271,073, 6 pages. |
| Office Action, dated Apr. 5, 2017, received in Danish Patent Application No. 201670725, which corresponds with U.S. Appl. No. 15/271,073, 3 pages. |
| Office Action, dated Oct. 12, 2017, received in Danish Patent Application No. 201670725, which corresponds with U.S. Appl. No. 15/271,073, 3 pages. |
| Office Action, dated Jan. 14, 2019, received in Danish Patent Application No. 201670725, which corresponds with U.S. Appl. No. 15/271,073, 3 pages. |
| Office Action, dated May 16, 2018, received in Danish Patent Application No. 201670725, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Office Action, dated Feb. 10, 2017, received in U.S. Appl. No. 15/272,380, 18 pages. |
| Notice of Allowance, dated Dec. 6, 2017, received in U.S. Appl. No. 15/272,380, 11 pages. |
| Notice of Allowance, dated Mar. 8, 2018, received in U.S. Appl. No. 15/272,380 11 pages. |
| Certificate of Grant, dated Aug. 23, 2017, received in Australian Patent Application No. 2017101092, which corresponds with U.S. Appl. No. 15/272,380 1 page. |
| Office Action, dated Oct. 4, 2017, received in Australian Patent Application No. 2017101092, which correspond with U.S. Appl. No. 15/272,380, 8 pages. |
| Certificate of Grant, dated Apr. 26, 2018, received in Australian Patent Application No. 2018100429, which corresponds with U.S. Appl. No. 15/272,380, 1 page. |
| Office Action, dated May 31, 2018, received in Australian Patent Application No. 2018100429, which corresponds with U.S. Appl. No. 15/272,380, 5 pages. |
| Certificate of Examination, dated Aug. 7, 2018, received in Australian Patent Application No. 2018100429, which corresponds with U.S. Appl. No. 15/272,380, 1 page. |
| Office Action, dated Apr. 2, 2019, received in Chinese Patent Application No. 2017800042913, which corresponds with U.S. Appl. No. 15/272,380, 5 pages. |
| Office Action, dated Jul. 16, 2019, received in Chinese Patent Application No. 2017800042913, which corresponds with U.S. Appl. No. 15/272,380, 6 pages. |
| Office Action, dated Jun. 5, 2019, received in Chinese Patent Application No. 2018108328493, which corresponds with U.S. Appl. No. 15/272,380, 4 pages. |
| Office Action, dated Feb. 23, 2017, received in Danish Patent Application No. 201670729, which corresponds with U.S. Appl. No. 15/272,380 9 pages. |
| Office Action, dated Aug. 28, 2017, received in Danish Patent Application No. 201670729, which corresponds with U.S. Appl. No. 15/272,380, 3 pages. |
| Office Action, dated Mar. 9, 2018, received in Danish Patent Application No. 201670729, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Office Action, dated May 17, 2018, received in Danish Patent Application No. 201670729, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Notice of Allowance, dated Oct. 2, 2018, received in Danish Patent Application No. 201670729, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Patent, dated Jan. 4, 2019, received in Danish Patent Application No. 201670729, which corresponds with U.S. Appl. No. 15/272,380, 7 pages. |
| Office Action, dated Jan. 24, 2017, received in Danish Patent Application No. 201670735, which corresponds with U.S. Appl. No. 15/272,380, 8 pages. |
| Office Action, dated Jul. 27, 2017, received in Danish Patent Application No. 201670735, which corresponds with U.S. Appl. No. 15/272,380, 3 pages. |
| Office Action, dated Dec. 7, 2017, received in Danish Patent Application No. 201670735, which corresponds with U.S. Appl. No. 15/272,380, 3 pages. |
| Office Action, dated Jun. 15, 2018, received in Danish Patent Application No. 201670735, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Intention to Grant, dated Nov. 21, 2018, received in Danish Patent Application No. 201670735, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Patent, dated Mar. 13, 2019, received in Danish Patent Application No. 201670735, which corresponds with U.S. Appl. No. 15/272,380, 3 pages. |
| Office Action, dated Jan. 11, 2017, received in Danish Patent Application No. 201670736, which corresponds with U.S. Appl. No. 15/272,380, 11 pages. |
| Office Action, dated Aug. 30, 2017, received in Danish Patent Application No. 201670736, which corresponds with U.S. Appl. No. 15/272,380, 4 pages. |
| Office Action, dated Mar. 16, 2018, received in Danish Patent Application No. 201670736, which corresponds with U.S. Appl. No. 15/272,380, 4 pages. |
| Office Action, dated May 14, 2019, received in Danish Patent Application No. 201670736, which corresponds with U.S. Appl. No. 15/272,380, 3 pages. |
| Office Action, dated Jan. 30, 2017, received in Danish Patent Application No. 201670737, which corresponds with U.S. Appl. No. 15/272,380, 9 pages. |
| Office Action, dated Aug. 31, 2017, received in Danish Patent Application No. 201670737, which corresponds with U.S. Appl. No. 15/272,380, 4 pages. |
| Office Action, dated Jul. 25, 2018, received in Danish Patent Application No. 201670737, which corresponds with U.S. Appl. No. 15/272,380, 5 pages. |
| Office Action, dated Oct. 26, 2018, received in European Patent Application No. 18183341.9, which corresponds with U.S. Appl. No. 15/272,380, 7 pages. |
| Notice of Allowance, dated Aug. 27, 2018, received in U.S. Appl. No. 15/273,688, 27 pages. |
| Notice of Allowance, dated Jul. 12, 2018, received in U.S. Appl. No. 15/275,083, 22 pages. |
| Office Action, dated Jan. 14, 2019, received in European Patent Application No. 18191063.9, which corresponds with U.S. Appl. No. 15/275,083, 9 pages. |
| Notice of Allowance, dated Apr. 23, 2019, received in Japanese Patent Application No. 2018550359, which corresponds with U.S. Appl. No. 15/275,083, 4 pages. |
| Patent, dated May 17, 2019, received in Japanese Patent Application No. 2018550359, which corresponds with U.S. Appl. No. 15/275,083, 4 pages. |
| Notice of Allowance, dated Feb. 22, 2017, received in U.S. Appl. No. 15/271,534, 13 pages. |
| Office Action, dated Nov. 23, 2018, received in Chinese Patent Application No. 201710736303.3, which corresponds with U.S. Appl. No. 15/271,534, 7 pages. |
| Notification to Grant, dated Apr. 10, 2019, received in Chinese Patent Application No. 201710736303.3, which corresponds with U.S. Appl. No. 15/271,534, 6 pages. |
| Patent, dated Jun. 7, 2019, received in Chinese Patent Application No. 201710736303.3, which corresponds with U.S. Appl. No. 15/271,534, 6 pages. |
| Office Action, dated Jan. 10, 2017, received in U.S. Appl. No. 15/271,653, 9 pages. |
| Office Action, dated Sep. 13, 2017, received in Chinese Patent Application No. 201710728497.2, which corresponds with U.S. Appl. No. 15/271,653, 3 pages. |
| Office Action, dated Dec. 29, 2018, received in Chinese Patent Application No. 201710728497.2, which corresponds with U.S. Appl. No. 15/271,653, 6 pages. |
| Office Action, dated Jan. 27, 2017, received in U.S. Appl. No. 15/271,708, 8 pages. |
| Notice of Allowance, dated Apr. 5, 2017, received in U.S. Appl. No. 15/271,708, 5 pages. |
| Office Action, dated Nov. 22, 2017, received in Chinese Patent Application No. 201710736331.5, which corresponds with U.S. Appl. No. 15/271,108, 3 pages. |
| Office Action, dated Mar. 5, 2019, received in Chinese Patent Application No. 201710736331.5, which corresponds with U.S. Appl. No. 15/271,108, 6 pages. |
| Office Action, dated Nov. 30, 2015, received in U.S. Appl. No. 14/835,708, 28 pages. |
| Final Office Action, dated May 20, 2016, received in U.S. Appl. No. 14/835,708, 7 pages. |
| Notice of Allowance, dated Aug. 29, 2016, received in U.S. Appl. No. 14/835,708, 9 pages. |
| Office Action, dated Oct. 30, 2017, received in Australian Patent Application No. 2015312344, which corresponds with U.S. Appl. No. 14/835,708, 2 pages. |
| Notice of Acceptance, dated Apr. 5, 2018, received in Australian Patent Application No. 2015312344, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Certificate of Grant, dated Aug. 2, 2018, received in Australian Patent Application No. 2015312344, which corresponds with U.S. Appl. No. 14/835,708, 1 page. |
| Office Action, dated Apr. 18, 2019, received in Chinese Patent Application No. 201580044092.6, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Office Action, dated Apr. 18, 2019, received in European Patent Application No. 15748122.7, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Office Action, dated May 11, 2018, received in Japanese Patent Application No. 2017509011, which corresponds with U.S. Appl. No. 14/835,708, 8 pages. |
| Office Action, dated Dec. 14, 2018, received in Japanese Patent Application No. 2017509011, which corresponds with U.S. Appl. No. 14/835,708, 8 pages. |
| Notice of Allowance, dated May 24, 2019, received in Japanese Patent Application No. 2017509011, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Patent, dated Jun. 14, 2019, received in Japanese Patent Application No. 2017509011, which corresponds with U.S. Appl. No. 14/835,708, 3 pages. |
| Office Action, dated Dec. 26, 2017, received in Korean Patent Application No. 2017-7005874, which corresponds with U.S. Appl. No. 14/835,708, 11 pages. |
| Final Office Action, dated Jul. 17, 2018, received in Korean Patent Application No. 2017-7005874, which corresponds with U.S. Appl. No. 14/835,708, 3 pages. |
| Final Office Action, dated Nov. 8, 2018, received in Korean Patent Application No. 2017-7005874, which corresponds with U.S. Appl. No. 14/835,708, 3 pages. |
| Office Action, dated Aug. 1, 2016, received in Taiwanese Patent Application No. 104126890, which corresponds with U.S. Appl. No. 14/835,708, 17 pages. |
| Office Action, dated Dec. 20, 2016, received in Taiwanese Patent Application No. 104126890, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Office Action, dated Dec. 28, 2016, received in Taiwanese Patent Application No. 104126890, which corresponds with U.S. Appl. No. 14/835,708, 3 pages. |
| Patent, dated Apr. 11, 2018, received in Taiwanese Patent Application No. 104126890, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Office action, dated Apr. 5, 2017, received in Taiwanese Patent Application No. 105139726, which corresponds with U.S. Appl. No. 14/835,708, 2 pages. |
| Notice of Allowance, dated Jul. 21, 2017, received in Taiwanese Patent Application No. 105139726, which corresponds with U.S. Appl. No. 14/835,708, 6 pages. |
| Patent, dated Nov. 1, 2017, received in Taiwanese Patent Application No. 105139726, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Office Action, dated Feb. 12, 2016, received in U.S. Appl. No. 14/869,825, 15 pages. |
| Final Office Action, dated Jul. 8, 2016, received in U.S. Appl. No. 14/869,825, 20 pages. |
| Office Action, dated Dec. 27, 2016, received in U.S. Appl. No. 14/869,825, 27 pages. |
| Office Action, dated Feb. 12, 2016, received in U.S. Appl. No. 14/869,829, 20 pages. |
| Final Office Action, dated Aug. 8, 2016, received in U.S. Appl. No. 14/869,829, 28 pages. |
| Office Action, dated Mar. 7, 2017, received in U.S. Appl. No. 14/869,829, 24 pages. |
| Final Office Action, dated Jul. 24, 2017, received in U.S. Appl. No. 14/869,829, 30 pages. |
| Examiner's Answer, dated Mar. 21, 2018, received in U.S. Appl. No. 14/869,829, 8 pages. |
| Notice of Allowance, dated May 9, 2019, received in U.S. Appl. No. 14/869,829, 8 pages. |
| Notice of Allowance, dated Jun. 26, 2019, received in U.S. Appl. No. 14/869,829, 8 pages. |
| Office Action, dated Feb. 18, 2016, received in U.S. Appl. No. 14/869,834, 17 pages. |
| Final Office Action, dated Aug. 8, 2016, received in U.S. Appl. No. 14/869,834, 22 pages. |
| Office Action, dated Mar. 7, 2017, received in U.S. Appl. No. 14/869,834, 20 pages. |
| Final Office Action, dated Jul. 25, 2017, received in U.S. Appl. No. 14/869,834, 18 pages. |
| Notice of Allowance, dated Nov. 7, 2017, received in U.S. Appl. No. 14/869,834, 9 pages. |
| Office Action, dated May 3, 2019, received in Australian Patent Application No. 2018202796, which corresponds with U.S. Appl. No. 14/869,834, 2 pages. |
| Office Action, dated Mar. 21, 2019, received in Korean Patent Application No. 2019-7000444, which corresponds with U.S. Appl. No. 14/869,870, 3 pages. |
| Office Action, dated Feb. 17, 2016, received in U.S. Appl. No. 14/869,835, 15 pages. |
| Final Office Action, dated Aug. 4, 2016, received in U.S. Appl. No. 14/869,835, 21 pages. |
| Office Office Action, dated Jan. 6, 2017, received in U.S. Appl. No. 14/869,835, 17 pages. |
| Final Office Action, dated Jun. 28, 2017, received in U.S. Appl. No. 14/869,835, 24 pages. |
| Office Action, dated Nov. 30, 2017, received in U.S. Appl. No. 14/869,835, 8 pages. |
| Notice of Allowance, dated May 29, 2018, received in U.S. Appl. No. 14/869,835, 12 pages. |
| Office Action, dated Dec. 30, 2015, received in U.S. Appl. No. 14/869,837, 35 pages. |
| Final Office Action, dated Jun. 30, 2016, received in U.S. Appl. No. 14/869,837, 37 pages. |
| Office Action, dated Jan. 17, 2017, received in U.S. Appl. No. 14/869,837, 27 pages. |
| Notice of Allowance, dated Jul. 31, 2017, received in U.S. Appl. No. 14/869,837, 27 pages. |
| Office Action, dated Aug. 31, 2017, received in Danish Patent Application No. 201770372, 10 pages. |
| Office Action, dated Apr. 17, 2018, received in Danish Patent Application No. 201770372, 5 pages. |
| Office Action, dated May 10, 2019, received in Danish Patent Application No. 201770372, 5 pages. |
| Office Action, dated Mar. 7, 2018, received in U.S. Appl. No. 15/688,754, 9 pages. |
| Notice of Allowance, dated Aug. 27, 2018, received in U.S. Appl. No. 15/688,754, 5 pages. |
| Office Action, dated Feb. 12, 2019, received in U.S. Appl. No. 15/823,436, 7 pages. |
| Notice of Allowance, dated Apr. 11, 2019, received in U.S. Appl. No. 15/863,765, 10 pages. |
| Office Action, dated Jul. 20, 2018, received in U.S. Appl. No. 15/905,671, 7 pages. |
| Notice of Allowance, dated Dec. 20, 2018, received in U.S. Appl. No. 15/905,671, 9 pages. |
| Office Action, dated Feb. 13, 2019, received in U.S. Appl. No. 16/240,684, 9 pages. |
| Notice of Allowance, dated Mar. 19, 2019, received in U.S. Appl. No. 16/240,684, 5 pages. |
| Office Action, dated Jul. 17, 2019, received in U.S. Appl. No. 16/355,621, 7 pages. |
| International Search Report and Written Opinion, dated Nov. 29, 2017, received in International Patent Application No. PCT/US2017/037004, which corresponds with U.S. Appl. No. 15/619,359, 21 pages. |
| International Preliminary Report on Patentability, dated Dec. 18, 2018, received in International Patent Application No. PCT/US2017/037004, which corresponds with U.S. Appl. No. 15/619,359, 12 pages. |
| Extended European Search Report, dated Oct. 20, 2017, received in European Patent Application No. 17177493.8, which corresponds with U.S. Appl. No. 15/270,885, 6 pages. |
| Invitation to Pay Additional Fees, dated Nov. 8, 2017, received in International Patent Application No. PCT/US2017/045152, which corresponds with U.S. Appl. No. 15/270,885, 17 pages. |
| International Search Report and Written Opinion, dated Jan. 18, 2018, received in International Patent Application No. PCT/US2017/045152, which corresponds with U.S. Appl. No. 15/270,885, 20 pages. |
| Extended European Search Report, dated Jan. 10, 2018, received in European Patent Application No. 17186196.6, which corresponds with U.S. Appl. No. 15/271,073, 8 pages. |
| Extended European Search Report, dated Jan. 9, 2018, received in European Patent Application No. 17186312.9, which corresponds with U.S. Appl. No. 15/271,073, 6 pages. |
| Extended European Search Report, dated Jan. 5, 2018, received in European Patent Application No. 17186313.7, which corresponds with U.S. Appl. No. 15/271,073, 9 pages. |
| International Search Report and Written Opinion, dated Jan. 16, 2018, received in International Patent Application No. PCT/US2017/045740, which corresponds with U.S. Appl. No. 15/271,073, 19 pages. |
| European Search Report, dated Sep. 27, 2018, received in European Patent Application No. 18183341.9, which corresponds with U.S. Appl. No. 15/271,073, 4 pages. |
| International Search Report and Written Opinion, dated Jan. 18, 2018, received in International Patent Application No. PCT/US2017/044851, which corresponds with U.S. Appl. No. 15/272,380, 17 pages. |
| European Search Report, dated Dec. 3, 2018, received in European Patent Application No. 18191063.9, which corresponds with U.S. Appl. No. 15/275 083, 4 pages. |
| International Search Report and Written Opinion, dated Mar. 15, 2016, received in International Patent Application No. PCT/US2015/041858, which corresponds with U.S. Appl. No. 14/835,708, 31 pages. |
| International Search Report and Written Opinion, dated Aug. 22, 2018, received in International Patent Application No. PCT/US2018032936, which corresponds with U.S. Appl. No. 15/972,040, 14 pages. |
| Office Action, dated Aug. 9, 2019, received in Australian Patent Application No. 2017251751, which corresponds with U.S. Appl. No. 15/270,885, 5 pages. |
| Notice of Allowance, Office Action, dated Aug. 14, 2019, received in Chinese Patent Application No. 201710734877.7, which corresponds with U.S. Appl. No. 15/270,885, 5 pages. |
| Office Action, dated Aug. 1, 2019, received in European Patent Application No. 19168886.0, which corresponds with U.S. Appl. No. 15/270,885, 5 pages. |
| Office Action, dated Aug. 5, 2019, received in Japanese Patent Application No. 2019-090875, which corresponds with U.S. Appl. No. 15/272,380, 7 pages. |
| Notice of Allowance, dated Jul. 31, 2019, received in Chinese Patent Application No. 201710736331.5, which corresponds with U.S. Appl. No. 15/271,108, 6 pages. |
| Certificate of Grant, dated Aug. 28, 2019, received in Australian Patent Application No. 201761484, which corresponds with U.S. Appl. No. 15/271,073, 4 pages. |
| Patent, dated Aug. 27, 2019, received in Chinese Application No. 201710735308.4, which corresponds with U.S. Appl. No. 15/271,073, 6 pages. |
| Office Action, dated Sep. 27, 2019, received in Danish Patent Application No. 201670720, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Patent, dated Jun. 26, 2019, received in Danish Patent Application No. 2016-70724, which corresponds with U.S. Appl. No. 15/271,073, 4 pages. |
| Intention to Grant, dated Sep. 5, 2019, received in Danish Patent Application No. 201670725, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Notice of Allowance, dated Sep. 4, 2019, received in Chinese Patent Application No. 201710728497.2, which corresponds with U.S. Appl. No. 15/271,653, 5 pages. |
| Patent, dated Sep. 3, 2019, received in Chinese Patent Application No. 201710736331.5, which corresponds with U.S. Appl. No. 15/271,108, 6 pages. |
| Notice of Allowance, dated Sep. 10, 2019, received in Korean Patent Application No. 2019-7000444, which corresponds with U.S. Appl. No. 14/869,870, 4 pages. |
| Notice of Allowance, dated Sep. 18, 2019, received in U.S. Appl. No. 15/863,765, 8 pages. |
| Final Office Action, dated Dec. 12, 2019, received in U.S. Appl. No. 16/355,621, 8 pages. |
| Office Action, dated Nov. 18, 2019, received in Australian Patent Application No. 2017286532, which corresponds with U.S. Appl. No. 15/619,359, 2 pages. |
| Office Action, dated Oct. 15, 2016, received in Chinese Patent Application No. 201780030418.9, which corresponds with U.S. Appl. No. 15/619,359, 3 pages. |
| Office Action, dated Oct. 4, 2019, received in European Patent Application No. 17733235.0, which corresponds with U.S. Appl. No. 15/619,359, 4 pages. |
| Office Action, dated Nov. 14, 2019, received in Australian Patent Application No. 2017251751, which corresponds with U.S. Appl. No. 15/270,885, 3 pages. |
| Patent, dated Oct. 25, 2019, received in Chinese Patent Application No. 201710734877.7, which corresponds with U.S. Appl. No. 15/270,885, 6 pages. |
| Patent, dated Nov. 1, 2019, received in Chinese Patent Application No. 201710728497.2, which corresponds with U.S. Appl. No. 15/271,653, 6 pages. |
| Office Action, dated Nov. 27, 2019, received in U.S. Appl. No. 15/972,040, 17 pages. |
| Office Action, dated Nov. 26, 2019, received in Australian Patent Application No. 2019202429, which corresponds with U.S. Appl. No. 16/240,684, 2 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20190332179 A1 | Oct 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62384159 | Sep 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16240684 | Jan 2019 | US |
| Child | 16508218 | US | |
| Parent | 15688754 | Aug 2017 | US |
| Child | 16240684 | US | |
| Parent | 15271073 | Sep 2016 | US |
| Child | 15688754 | US |
