Patent Grant
10928907
The present disclosure relates generally to computer user interfaces, and more specifically to techniques for managing content-based tactile outputs.
At present, there is a need for electronic devices that provide sensory feedback (e.g., tactile and/or audio outputs) based on the type of content being displayed and navigated on the display to enhance the user experience, enhance user efficiency, and convenience in utilizing the device.
Some techniques for managing content-based tactile outputs using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for managing content-based tactile outputs. Such methods and interfaces optionally complement or replace other methods for managing content-based tactile outputs. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For example, such methods and interfaces enhance user experience and convenience in navigating content shown on a device, and thus enable the user to more easily and efficiently navigate content shown on the device. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.
In accordance with some embodiments, a method performed at an electronic device with a display, an input element, and one or more tactile output generators is described. The method comprises: displaying, on the display, a user interface; while displaying the user interface, detecting, via the input element, a first input; and in response to detecting the first input: navigating through the user interface; and generating, via the one or more tactile output generators, tactile output corresponding to the navigation through the user interface, including: in accordance with a determination that a currently-displayed portion of the user interface includes a first type of content, the tactile output corresponding to the navigation includes a first type of tactile output sequence that includes one or more tactile outputs determined based on an input metric of the first input; and in accordance with a determination that the currently-displayed portion of the user interface includes a second type of content different from the first type of content, the tactile output corresponding to the navigation includes a second type of tactile output sequence that includes one or more tactile outputs determined based on movement of predefined units of content in the user interface.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, an input element, and one or more tactile output generators, the one or more programs including instructions for: displaying, on the display, a user interface; while displaying the user interface, detecting, via the input element, a first input; and in response to detecting the first input: navigating through the user interface; and generating, via the one or more tactile output generators, tactile output corresponding to the navigation through the user interface, including: in accordance with a determination that a currently-displayed portion of the user interface includes a first type of content, the tactile output corresponding to the navigation includes a first type of tactile output sequence that includes one or more tactile outputs determined based on an input metric of the first input; and in accordance with a determination that the currently-displayed portion of the user interface includes a second type of content different from the first type of content, the tactile output corresponding to the navigation includes a second type of tactile output sequence that includes one or more tactile outputs determined based on movement of predefined units of content in the user interface.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, an input element, and one or more tactile output generators, the one or more programs including instructions for: displaying, on the display, a user interface; while displaying the user interface, detecting, via the input element, a first input; and in response to detecting the first input: navigating through the user interface; and generating, via the one or more tactile output generators, tactile output corresponding to the navigation through the user interface, including: in accordance with a determination that a currently-displayed portion of the user interface includes a first type of content, the tactile output corresponding to the navigation includes a first type of tactile output sequence that includes one or more tactile outputs determined based on an input metric of the first input: and in accordance with a determination that the currently-displayed portion of the user interface includes a second type of content different from the first type of content, the tactile output corresponding to the navigation includes a second type of tactile output sequence that includes one or more tactile outputs determined based on movement of predefined units of content in the user interface.
In accordance with some embodiments, an electronic device is described. The electronic device comprises a display, an input element, one or more tactile output generators, one or more processors, and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying, on the display, a user interface; while displaying the user interface, detecting, via the input element, a first input; and in response to detecting the first input: navigating through the user interface; and generating, via the one or more tactile output generators, tactile output corresponding to the navigation through the user interface, including: in accordance with a determination that a currently-displayed portion of the user interface includes a first type of content, the tactile output corresponding to the navigation includes a first type of tactile output sequence that includes one or more tactile outputs determined based on an input metric of the first input; and in accordance with a determination that the currently-displayed portion of the user interface includes a second type of content different from the first type of content, the tactile output corresponding to the navigation includes a second type of tactile output sequence that includes one or more tactile outputs determined based on movement of predefined units of content in the user interface.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; an input element; one or more tactile output generators; means for displaying, on the display, a user interface; means, while displaying the user interface, for detecting, via the input element, a first input; and means, in response to detecting the first input, for: navigating through the user interface; and generating, via the one or more tactile output generators, tactile output corresponding to the navigation through the user interface, including: in accordance with a determination that a currently-displayed portion of the user interface includes a first type of content, the tactile output corresponding to the navigation includes a first type of tactile output sequence that includes one or more tactile outputs determined based on an input metric of the first input; and in accordance with a determination that the currently-displayed portion of the user interface includes a second type of content different from the first type of content, the tactile output corresponding to the navigation includes a second type of tactile output sequence that includes one or more tactile outputs determined based on movement of predefined units of content in the user interface.
In accordance with some embodiments, a method performed at an electronic device with a display, an input element, and one or more tactile output generators is described. The method comprises: displaying, on the display, a first portion of content; while displaying the first portion of content, detecting, via the input element, a first input; in response to detecting the first input: navigating through the content to display a second portion of the content; and generating, via the one or more tactile output generators, a first type of tactile output sequence that includes one or more tactile outputs; while displaying the second portion of the content, detecting, via the input element, a second input; and in response to detecting the second input and in accordance with a determination that the second portion of the content is a terminal portion of the content: displaying a visual indication that the content is a terminal portion of the content; and forgoing generating, via the one or more tactile output generators, the first type of tactile output sequence.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, an input element, and one or more tactile output generators, the one or more programs including instructions for: displaying, on the display, a first portion of content; while displaying the first portion of content, detecting, via the input element, a first input; in response to detecting the first input: navigating through the content to display a second portion of the content; and generating, via the one or more tactile output generators, a first type of tactile output sequence that includes one or more tactile outputs; while displaying the second portion of the content, detecting, via the input element, a second input; and in response to detecting the second input and in accordance with a determination that the second portion of the content is a terminal portion of the content: displaying a visual indication that the content is a terminal portion of the content; and forgoing generating, via the one or more tactile output generators, the first type of tactile output sequence.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, an input element, and one or more tactile output generators, the one or more programs including instructions for: displaying, on the display, a first portion of content; while displaying the first portion of content, detecting, via the input element, a first input; in response to detecting the first input: navigating through the content to display a second portion of the content; and generating, via the one or more tactile output generators, a first type of tactile output sequence that includes one or more tactile outputs; while displaying the second portion of the content, detecting, via the input element, a second input; and in response to detecting the second input and in accordance with a determination that the second portion of the content is a terminal portion of the content: displaying a visual indication that the content is a terminal portion of the content; and forgoing generating, via the one or more tactile output generators, the first type of tactile output sequence.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display, an input element, one or more tactile output generators, one or more processors, and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying, on the display, a first portion of content; while displaying the first portion of content, detecting, via the input element, a first input; in response to detecting the first input: navigating through the content to display a second portion of the content; and generating, via the one or more tactile output generators, a first type of tactile output sequence that includes one or more tactile outputs; while displaying the second portion of the content, detecting, via the input element, a second input; and in response to detecting the second input and in accordance with a determination that the second portion of the content is a terminal portion of the content: displaying a visual indication that the content is a terminal portion of the content; and forgoing generating, via the one or more tactile output generators, the first type of tactile output sequence.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; an input element; one or more tactile output generators; means for displaying, on the display, a first portion of content; means, while displaying the first portion of content, for detecting, via the input element, a first input; means, in response to detecting the first input, for: navigating through the content to display a second portion of the content; and generating, via the one or more tactile output generators, a first type of tactile output sequence that includes one or more tactile outputs; means, while displaying the second portion of the content, for detecting, via the input element, a second input; and means, in response to detecting the second input and in accordance with a determination that the second portion of the content is a terminal portion of the content, for: displaying a visual indication that the content is a terminal portion of the content; and forgoing generating, via the one or more tactile output generators, the first type of tactile output sequence.
In accordance with some embodiments, a method performed at an electronic device with a touch-sensitive display and a rotatable input element is described. The method comprises: displaying, on the display, a user interface; while displaying the user interface, detecting a first portion of an input at the device: in response to detecting a first portion of the input, moving a user interface object across the display of the device in accordance with the movement of the input; and after detecting the first portion of the input, detecting a second portion of the input at the device; and in response to detecting the second portion of the input: in accordance with a determination that the input includes movement of a contact on the touch-sensitive display and that the movement moves the user interface object across the display by more than a first threshold amount, moving the user interface object to a respective position on the display; in accordance with a determination that the input includes movement of a contact on the touch-sensitive display and that the movement moves the user interface object across the display by less than the first threshold amount, forgoing moving the user interface object to the respective position on the display; in accordance with a determination that the input includes rotational input directed to the rotatable input element and that the rotational input moves the user interface object across the display by more than a second threshold amount that is less than the first threshold amount, moving the user interface object to the respective position on the display; and in accordance with a determination that the input includes rotational input directed to the rotatable input element and that the rotational input moves the user interface object across the display by less than the second threshold amount, forgoing moving the user interface object to the respective position on the display.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a touch-sensitive display and a rotatable input element, the one or more programs including instructions for: displaying, on the display, a user interface; while displaying the user interface, detecting a first portion of an input at the device: in response to detecting a first portion of the input, moving a user interface object across the display of the device in accordance with the movement of the input; and after detecting the first portion of the input, detecting a second portion of the input at the device; and in response to detecting the second portion of the input: in accordance with a determination that the input includes movement of a contact on the touch-sensitive display and that the movement moves the user interface object across the display by more than a first threshold amount, moving the user interface object to a respective position on the display; in accordance with a determination that the input includes movement of a contact on the touch-sensitive display and that the movement moves the user interface object across the display by less than the first threshold amount, forgoing moving the user interface object to the respective position on the display; in accordance with a determination that the input includes rotational input directed to the rotatable input element and that the rotational input moves the user interface object across the display by more than a second threshold amount that is less than the first threshold amount, moving the user interface object to the respective position on the display; and in accordance with a determination that the input includes rotational input directed to the rotatable input element and that the rotational input moves the user interface object across the display by less than the second threshold amount, forgoing moving the user interface object to the respective position on the display.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a touch-sensitive display and a rotatable input element, the one or more programs including instructions for: displaying, on the display, a user interface; while displaying the user interface, detecting a first portion of an input at the device: in response to detecting a first portion of the input, moving a user interface object across the display of the device in accordance with the movement of the input; and after detecting the first portion of the input, detecting a second portion of the input at the device; and in response to detecting the second portion of the input: in accordance with a determination that the input includes movement of a contact on the touch-sensitive display and that the movement moves the user interface object across the display by more than a first threshold amount, moving the user interface object to a respective position on the display; in accordance with a determination that the input includes movement of a contact on the touch-sensitive display and that the movement moves the user interface object across the display by less than the first threshold amount, forgoing moving the user interface object to the respective position on the display; in accordance with a determination that the input includes rotational input directed to the rotatable input element and that the rotational input moves the user interface object across the display by more than a second threshold amount that is less than the first threshold amount, moving the user interface object to the respective position on the display; and in accordance with a determination that the input includes rotational input directed to the rotatable input element and that the rotational input moves the user interface object across the display by less than the second threshold amount, forgoing moving the user interface object to the respective position on the display.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a touch-sensitive display, a rotatable input element, one or more processors, and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying, on the display, a user interface; while displaying the user interface, detecting a first portion of an input at the device: in response to detecting a first portion of the input, moving a user interface object across the display of the device in accordance with the movement of the input; and after detecting the first portion of the input, detecting a second portion of the input at the device; and in response to detecting the second portion of the input: in accordance with a determination that the input includes movement of a contact on the touch-sensitive display and that the movement moves the user interface object across the display by more than a first threshold amount, moving the user interface object to a respective position on the display; in accordance with a determination that the input includes movement of a contact on the touch-sensitive display and that the movement moves the user interface object across the display by less than the first threshold amount, forgoing moving the user interface object to the respective position on the display; in accordance with a determination that the input includes rotational input directed to the rotatable input element and that the rotational input moves the user interface object across the display by more than a second threshold amount that is less than the first threshold amount, moving the user interface object to the respective position on the display; and in accordance with a determination that the input includes rotational input directed to the rotatable input element and that the rotational input moves the user interface object across the display by less than the second threshold amount, forgoing moving the user interface object to the respective position on the display.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; a rotatable input element; means for displaying, on the display, a user interface; means, while displaying the user interface, for detecting a first portion of an input at the device: means, in response to detecting a first portion of the input, for moving a user interface object across the display of the device in accordance with the movement of the input; and means, after detecting the first portion of the input, for detecting a second portion of the input at the device; and means, in response to detecting the second portion of the input, for: in accordance with a determination that the input includes movement of a contact on the touch-sensitive display and that the movement moves the user interface object across the display by more than a first threshold amount, moving the user interface object to a respective position on the display; in accordance with a determination that the input includes movement of a contact on the touch-sensitive display and that the movement moves the user interface object across the display by less than the first threshold amount, forgoing moving the user interface object to the respective position on the display; in accordance with a determination that the input includes rotational input directed to the rotatable input element and that the rotational input moves the user interface object across the display by more than a second threshold amount that is less than the first threshold amount, moving the user interface object to the respective position on the display; and in accordance with a determination that the input includes rotational input directed to the rotatable input element and that the rotational input moves the user interface object across the display by less than the second threshold amount, forgoing moving the user interface object to the respective position on the display.
In accordance with some embodiments, a method performed at an electronic device with a display, an input element, and one or more tactile output generators is described. The method comprises: displaying, on the display, a user interface that includes a first adjustable item and a second adjustable item; while displaying the user interface, detecting, via the input element, a rotational input; and in response to detecting the rotational input: in accordance with a determination that the first adjustable item is currently-selected: adjusting, based on the rotational input, the first adjustable item; and while adjusting the first adjustable item, generating, via the one or more tactile output generators, a first sequence of tactile outputs including one or more tactile outputs having a first amplitude; and in accordance with a determination that the second adjustable item is currently-selected: adjusting, based on the rotational input, the second adjustable item; and while adjusting the second adjustable item, generating, via the one or more tactile output generators, a second sequence of tactile outputs including one or more tactile outputs having a second amplitude that is different from the first amplitude.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, an input element, and one or more tactile output generators, the one or more programs including instructions for: displaying, on the display, a user interface that includes a first adjustable item and a second adjustable item; while displaying the user interface, detecting, via the input element, a rotational input; and in response to detecting the rotational input: in accordance with a determination that the first adjustable item is currently-selected: adjusting, based on the rotational input, the first adjustable item; and while adjusting the first adjustable item, generating, via the one or more tactile output generators, a first sequence of tactile outputs including one or more tactile outputs having a first amplitude; and in accordance with a determination that the second adjustable item is currently-selected: adjusting, based on the rotational input, the second adjustable item; and while adjusting the second adjustable item, generating, via the one or more tactile output generators, a second sequence of tactile outputs including one or more tactile outputs having a second amplitude that is different from the first amplitude.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, an input element, and one or more tactile output generators, the one or more programs including instructions for: displaying, on the display, a user interface that includes a first adjustable item and a second adjustable item; while displaying the user interface, detecting, via the input element, a rotational input; and in response to detecting the rotational input: in accordance with a determination that the first adjustable item is currently-selected: adjusting, based on the rotational input, the first adjustable item; and while adjusting the first adjustable item, generating, via the one or more tactile output generators, a first sequence of tactile outputs including one or more tactile outputs having a first amplitude; and in accordance with a determination that the second adjustable item is currently-selected: adjusting, based on the rotational input, the second adjustable item; and while adjusting the second adjustable item, generating, via the one or more tactile output generators, a second sequence of tactile outputs including one or more tactile outputs having a second amplitude that is different from the first amplitude.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display, an input element, one or more tactile output generators, one or more processors, and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying, on the display, a user interface that includes a first adjustable item and a second adjustable item; while displaying the user interface, detecting, via the input element, a rotational input; and in response to detecting the rotational input: in accordance with a determination that the first adjustable item is currently-selected: adjusting, based on the rotational input, the first adjustable item; and while adjusting the first adjustable item, generating, via the one or more tactile output generators, a first sequence of tactile outputs including one or more tactile outputs having a first amplitude; and in accordance with a determination that the second adjustable item is currently-selected: adjusting, based on the rotational input, the second adjustable item; and while adjusting the second adjustable item, generating, via the one or more tactile output generators, a second sequence of tactile outputs including one or more tactile outputs having a second amplitude that is different from the first amplitude.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; an input element; one or more tactile output generators; means for displaying, on the display, a user interface that includes a first adjustable item and a second adjustable item; means, while displaying the user interface, for detecting, via the input element, a rotational input; and means, in response to detecting the rotational input, for: in accordance with a determination that the first adjustable item is currently-selected: adjusting, based on the rotational input, the first adjustable item; and while adjusting the first adjustable item, generating, via the one or more tactile output generators, a first sequence of tactile outputs including one or more tactile outputs having a first amplitude; and in accordance with a determination that the second adjustable item is currently-selected: adjusting, based on the rotational input, the second adjustable item; and while adjusting the second adjustable item, generating, via the one or more tactile output generators, a second sequence of tactile outputs including one or more tactile outputs having a second amplitude that is different from the first amplitude.
In accordance with some embodiments, a method performed at an electronic device with a display, a rotatable input element, and one or more tactile output generators is described. The method comprises: while displaying, on the display, a user interface, detecting, via the rotatable input element, a rotational input; and while detecting the rotational input, generating, via the one or more tactile output generators, a plurality of tactile outputs, wherein a type of the tactile outputs is associated with a modification of the user interface, and wherein: in accordance with a determination that a speed of the rotational input is a first speed, generating a first number of tactile outputs for a respective amount of rotation of the rotatable input element; and in accordance with a determination that the speed of the rotational input is a second speed that is different from the first speed, generating a second number of tactile outputs for the respective amount of rotation of the rotatable input element.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, a rotatable input element, and one or more tactile output generators, the one or more programs including instructions for: while displaying, on the display, a user interface, detecting, via the rotatable input element, a rotational input; and while detecting the rotational input, generating, via the one or more tactile output generators, a plurality of tactile outputs, wherein a type of the tactile outputs is associated with a modification of the user interface, and wherein: in accordance with a determination that a speed of the rotational input is a first speed, generating a first number of tactile outputs for a respective amount of rotation of the rotatable input element; and in accordance with a determination that the speed of the rotational input is a second speed that is different from the first speed, generating a second number of tactile outputs for the respective amount of rotation of the rotatable input element.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, a rotatable input element, and one or more tactile output generators, the one or more programs including instructions for: while displaying, on the display, a user interface, detecting, via the rotatable input element, a rotational input; and while detecting the rotational input, generating, via the one or more tactile output generators, a plurality of tactile outputs, wherein a type of the tactile outputs is associated with a modification of the user interface, and wherein: in accordance with a determination that a speed of the rotational input is a first speed, generating a first number of tactile outputs for a respective amount of rotation of the rotatable input element; and in accordance with a determination that the speed of the rotational input is a second speed that is different from the first speed, generating a second number of tactile outputs for the respective amount of rotation of the rotatable input element.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display, a rotatable input element, one or more tactile output generators, one or more processors, and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while displaying, on the display, a user interface, detecting, via the rotatable input element, a rotational input; and while detecting the rotational input, generating, via the one or more tactile output generators, a plurality of tactile outputs, wherein a type of the tactile outputs is associated with a modification of the user interface, and wherein: in accordance with a determination that a speed of the rotational input is a first speed, generating a first number of tactile outputs for a respective amount of rotation of the rotatable input element; and in accordance with a determination that the speed of the rotational input is a second speed that is different from the first speed, generating a second number of tactile outputs for the respective amount of rotation of the rotatable input element.
In accordance with some embodiments an electronic device is described. The electronic device comprises a display; a rotatable input element; one or more tactile output generators; means, while displaying, on the display, a user interface, for detecting, via the rotatable input element, a rotational input; and means, while detecting the rotational input, for generating, via the one or more tactile output generators, a plurality of tactile outputs, wherein a type of the tactile outputs is associated with a modification of the user interface, and wherein: in accordance with a determination that a speed of the rotational input is a first speed, generating a first number of tactile outputs for a respective amount of rotation of the rotatable input element; and in accordance with a determination that the speed of the rotational input is a second speed that is different from the first speed, generating a second number of tactile outputs for the respective amount of rotation of the rotatable input element.
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. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.
Thus, devices are provided with faster, more efficient methods and interfaces for managing content-based tactile outputs, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for managing content-based 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.
The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
There is a need for electronic devices that provide efficient methods and interfaces for managing content-based tactile outputs. For example, there is a need for electronic devices that provide sensory feedback (e.g., tactile and/or audio outputs) based on the type of content being displayed and navigated on the display to enhance user experience and convenience and user efficiency in utilizing the device. Such techniques can reduce the cognitive burden on a user who accesses displayed content associated with content-based tactile outputs, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.
Below,
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
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.
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. Exemplary 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 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 “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) 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) 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 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).
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.
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. Memory controller 122 optionally controls access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 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 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 RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11 ac), 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 screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, 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 control devices 116. The other input 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 to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 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 screen 112. Touch screen 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 optionally corresponds to user-interface objects.
Touch screen 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 screen 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 screen 112 and convert 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 screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 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 screen 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 screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.
A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 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 primarily 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 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 screen 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 depth camera sensors 175.
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, 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 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, 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 on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 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, 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 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.
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 threshold 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 sets 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).
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 (liftoff) 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 (liftoff) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used 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 or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 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 screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference 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 screen 112, display controller 156, contact/motion 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 screen 112, display controller 156, contact/motion 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, 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 an 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, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); 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 screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion 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, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact/motion 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 screen 112, display controller 156, contact/motion 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 screen 112, display controller 156, contact/motion 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 screen 112, display controller 156, contact/motion 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 screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display controller 156, contact/motion 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 screen 112, display controller 156, contact/motion 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 screen 112 or on an external, connected display 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 screen 112, display controller 156, contact/motion 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 screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 are, optionally, used 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 screen 112, display controller 156, contact/motion 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 instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display 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. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds 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 (e.g., 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 rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152,
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 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 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 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, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for 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 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 (e.g., 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 172, 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 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 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 include 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 liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (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 112, and liftoff 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 112, when a touch is detected on touch-sensitive display 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. 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 touchpads; 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.
Device 100 optionally also include 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 touch screen 112.
In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset 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 an alternative embodiment, 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 screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some 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), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 700 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “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, 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 optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation 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 optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, 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 is, optionally, 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 intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. 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 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.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold 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 to an intensity above the deep press intensity threshold 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 to an intensity between the contact-detection intensity threshold and the light press intensity threshold 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 to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
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., 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., 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., 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 descriptions 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 either: 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, and/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.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
Electronic device 600 includes one or more tactile output generators that are enclosed in and/or integrated with input element 604 and/or a housing of the device, or otherwise are mechanically coupled either directly or indirectly such that tactile outputs generated by the tactile output generators generate tactile outputs at input element 604. The one or more tactile output generators generate different types of tactile output sequences, as described below in Table 1, based on the type of content (e.g., continuous content, such as continuous text, or discrete content, such as platters, affordances, buttons) being displayed and navigated/scrolled/adjusted on display 602 of the device. In some embodiments, the one or more tactile output generators also generate different types of audio output sequences that are associated with the different types of tactile output sequences. Tactile output sequences 610, 620, 630, and 1220 described herein are generated by the one or more tactile output generators described above. In some embodiments, the audio output sequences described herein that are associated with tactile output sequences 610, 620, 630, and 1220 are also generated by the one or more tactile output generators described above.
In some embodiments, a particular type of tactile output sequence generated by the one or more tactile output generators of the device described directly above corresponds to a particular tactile output pattern. For example, 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.
More specifically,
As shown in
As shown in
Although specific frequencies, amplitudes, and waveforms are represented in the sample tactile output patterns in
Returning to the exemplary user interfaces of
In
Electronic device 600 continues to scroll the plurality of platters, including platters 608A and 608B, of user interface 608 while continuing to detect rotational input 601 on input element 604. In
In
Electronic device 600 continues to scroll the plurality of platters, including platter 608B, of user interface 608 while continuing to detect rotational input 601 on input element 604. In
Electronic device 600 continues to scroll the plurality of platters, including platter 608C, of user interface 608 while continuing to detect rotational input 601 on input element 604. In
In
In
In
In
In
While scrolling text 618 on the display, electronic device 600 generates, via the one or more tactile output generators, a tactile output sequence 620 (e.g., a “minor” tactile output, as described in Table 1). In some embodiments, electronic device 600 also generates an audio output sequence (e.g., having a second type of audio pattern) associated with tactile output sequence 620.
In
In
In
In
In
In some embodiments, upon displaying (e.g., fully displaying) affordance 626 on the display, as shown in
Alternatively, as with affordances 622 and 624, in some embodiments, upon displaying (e.g., fully displaying) affordance 626 on the display, electronic device 600 generates, via the one or more tactile output generators, tactile output sequence 610 and, in some embodiments, the audio output sequence associated with tactile output sequence 610. Alternatively, in some embodiments, electronic device 600 generates tactile output sequence 610 when affordance 622 “snaps” to the display from an edge (e.g., the bottom edge) of the display. Alternatively, in some embodiments, electronic device 600 generates tactile output sequence 610 when affordance 622 is moved to (e.g., and “snaps” to) a focal region of the display (e.g., a center region of the display).
In
After scrolling beyond affordance 626, electronic device 600 no longer detects rotational input 607.
In
In
In
In
In
In
In
In
In
In
In
As described below, method 700 provides an intuitive way for managing user interfaces associated with content-based tactile outputs. The method reduces the cognitive burden on a user for managing and navigating user interfaces, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to navigate user interfaces faster and more efficiently by providing content-based tactile outputs conserves power and increases the time between battery charges.
The electronic device (e.g., 600) displays (702), on the display (e.g., 602), a user interface (e.g., 608, 616, a user interface that includes continuous content, such as continuous text of a messaging application, and/or discrete content, such as buttons, affordances, rows, platters, paragraphs). In some embodiments, a platter is a predefined unit of a user interface that is a visually discrete and selectable user interface object, item, or element that is separate in functionality and/or purpose from other platters within the user interface, and is visually distinct and/or distinguishable from other platters and other user interface objects, items, or elements within the user interface.
While displaying the user interface (e.g., 608, 616), the electronic device (e.g., 600) detects (704), via the input element (e.g., 604), a first input (e.g., 601, 605, a rotational input on the input element, where the rotational input is in a clockwise or counter-clockwise direction).
In response to detecting (706) the first input (e.g., 601, 605), the electronic device (e.g., 600) navigates (708) through (e.g., scrolls through) the user interface (e.g., 608, 616). In response to detecting (706) the first input, the electronic device (e.g., 600) generates (710), via the one or more tactile output generators, tactile output (e.g., 610, 620, a sequence of a number of discrete, individual tactile outputs) corresponding to the navigation through the user interface. Generating a tactile output in response to a rotational input on an input element and while navigating through content enables a user to quickly and easily recognize that content on the user interface is being scrolled and the type of content that is displayed and scrolled on the user interface, thereby enhancing operability of the device and user efficiency. This in turn 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. Generating a tactile output in response to the rotational input
The tactile output (e.g., 610, 620, a sequence of a number of discrete, individual tactile outputs) corresponding to the navigation through the user interface (e.g., 616) includes, in accordance with a determination (712) that a currently-displayed portion of the user interface (e.g., 616) (e.g., a currently-selected (e.g., and displayed) portion of the user interface or a currently-selected user interface element within the user interface that is currently-displayed, a top portion or middle portion of the currently-selected user interface element) includes a first type of content (e.g., 618, continuous content, such as continuous text), the tactile output corresponding to the navigation includes (714) a first type of tactile output sequence (e.g., 620, a textural tactile output sequence) that includes one or more tactile outputs determined based on an input metric (e.g., a speed and/or magnitude) of the first input (e.g., without regard to movement of predefined units of content in the user interface). In some embodiments, the first type of tactile output sequence comprises variable tactile output spacing that is determined, for example, by the application corresponding to the displayed content. Generating a different type of tactile output sequence depending on the type of content that is being navigated in the user interface enables a user to quickly and easily recognize the nature, functionality, and/or features of the content that is being navigated while navigating/scrolling the content. Providing additional control of the device and reducing the number of inputs needed to perform an operation 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, the number of tactile outputs generated in the first type of tactile output sequence (e.g., 620, generated within a fixed period of time (e.g., a rate of output)) corresponds to (e.g., is proportional to) a speed (e.g., rotational speed) of the first input, the first input is a rotational input on the input element. In some embodiments, as described in greater detail below with reference to
The tactile output (e.g., a sequence of a number of discrete, individual tactile outputs) corresponding to the navigation through the user interface (e.g., 608) includes, in accordance with a determination (716) that the currently-displayed portion of the user interface (e.g., a currently-selected (e.g., and displayed) portion of the user interface or a currently-selected user interface element within the user interface that is currently-displayed, a top portion or middle portion of the currently-selected user interface element) includes a second type of content (e.g., discrete content, such as buttons, affordances, rows, platters, paragraphs) different from the first type of content, the tactile output corresponding to the navigation includes a second type of tactile output sequence (e.g., 610, a content-driven tactile output sequence) that includes (718) one or more tactile outputs determined based on movement of predefined units of content in the user interface. In some embodiments, the electronic device (e.g., 600) does not generate tactile outputs corresponding to the second type of tactile output sequence if the content being navigated is of the second type. In some embodiments, the predefined units of content correspond to visually distinguished content elements (e.g., buttons, affordances, rows, platters, paragraphs) within the content.
In some embodiments, the user interface does not include content that is the second type of content. In some embodiments, the user interface is a notification user interface (e.g., 612) that includes continuous notification text without including discrete content items (e.g., buttons, affordances, rows, platters, paragraphs)
In some embodiments, the user interface (e.g., 608) does not include content that is the first type of content. In some embodiments, the user interface includes discrete content items (e.g., buttons, affordances, rows, platters, paragraphs) without including continuous content such as a block of text or an image.
In some embodiments, a particular type of tactile output corresponds to a particular tactile output pattern. For example, as described with reference to
In some embodiments, the first type of tactile output sequence (e.g., 620, a textural tactile output sequence) is different from (e.g., distinguishable from) the second type of tactile output sequence (e.g., 610, a content-driven tactile output sequence). In some embodiments, the first type of tactile output sequence is different from the second type of tactile output sequence (e.g., 610) in that the number, amplitudes, and/or pattern of the one or more tactile outputs of the first type of tactile output sequence is different from the number, amplitudes, and/or pattern of the one or more tactile outputs of the second type of tactile output. That is, from the perspective of a user of the electronic device (e.g., 600), the sensory sensation felt by the user from first type of tactile output sequence and from the second type of tactile output sequence are distinguishable.
In some embodiments, the second type of tactile output sequence (e.g., 610, a content-driven tactile output sequence) is determined based on (e.g., synchronized to, aligned with, matches with) the movement of the predefined units of content (e.g., affordances, platters) in the user interface (e.g., 608) (e.g., a predefined unit starting to be displayed on the display (e.g., 602), being fully displayed on the display, moving in a snapping animation, starting to leave the display, being fully scrolled off of the display, or being scrolled to some predefined position on the display such as a center of the display), and the first type of tactile output sequence (e.g., 620, a textural tactile output sequence) is determined independently of (e.g., not synchronized to) the movement of content in the user interface.
In some embodiments, generating (710), via the one or more tactile output generators, tactile output corresponding to the navigation through the user interface (e.g., 616) includes, in accordance with a determination (736) that the user interface is displaying a terminal portion (e.g., a beginning or end portion, a top or bottom portion, an edge portion, a border portion) of the first type of content (e.g., continuous content, such as continuous text), the tactile output corresponding to the navigation includes a third type of tactile output sequence (e.g., 630), different from the first type of tactile output sequence (e.g., 620), indicating that the content is at the terminal portion. Providing a different type of tactile output to indicate that the content is at the terminal portion improves sensory feedback by enabling the user to quickly and easily recognize that the user has reached the end of the content (e.g., without having to attempt to further navigate/scroll the content). Providing improved feedback to the 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, generating (710), via the one or more tactile output generators, tactile output corresponding to the navigation through the user interface includes, in accordance with a determination (738) that the user interface is not displaying a terminal portion of the first type of content, the tactile output portion corresponding to the navigation does not include the third type of tactile output sequence (e.g., although the tactile output portion corresponding to the navigation optionally includes the first type of tactile output sequence or the second type of tactile output sequence depending on the type of content and the amount of navigation through the user interface).
In some embodiments, in accordance with the determination (716) that the user interface includes the second type of content (e.g., 608A, 608B, discrete content, such as buttons, affordances, rows, platters, paragraphs), and in accordance with a determination (728) that the predefined units of content are of a first type (e.g., relatively large discrete user interface objects), the tactile output has a first amplitude. In some embodiments, in accordance with the determination (716) that the user interface includes the second type of content (e.g., discrete content, such as buttons, affordances, rows, platters, paragraphs), and in accordance with a determination (730) that the predefined units of content are of a second type (e.g., relatively small discrete user interface objects) different from the first type, the tactile output has a second amplitude smaller than the first amplitude (e.g., a reduced amplitude). In some embodiments, the tactile output corresponding to the second type of predefined units of content is an amplitude-reduced version of the tactile output corresponding to the first type of predefined units of content. Different types of tactile outputs are described in greater detail above with reference to
In some embodiments, while navigating through the user interface (e.g., 608, 616, 632), in accordance with the determination that the currently-displayed portion of the user interface includes the second type of content (e.g. discrete content, such as buttons, affordances, rows, platters, paragraphs), generating (732) the tactile output (e.g., that includes the second type of tactile output sequence) comprises generating the tactile output in response to a movement (e.g., a snapping movement) of a first predefined unit of content (e.g., 608A, 608B, 622, 624) into alignment on the display (e.g., 602) (e.g., the first predefined unit snapping into a region of the display, such as a focal region, center region, or main viewing region of the display). Generating a tactile output in response to a movement of a first predefined unit of content into alignment on the display improves sensory feedback by enabling a user to quickly and easily recognize that the predefined unit of content is now the currently-selected content, and thus the user can proceed with using a feature/functionality associated with the predefined unit of content. Providing improved feedback to the 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, while navigating through the user interface (e.g., 608, 616, 632), in accordance with the determination that the currently-displayed portion of the user interface includes the second type of content (e.g. discrete content, such as buttons, affordances, rows, platters, paragraphs), generating (734) the tactile output (e.g., that includes the second type of tactile output sequence) comprises generating the tactile output in response a movement (e.g., a snapping movement) of a first predefined unit of content (e.g., 608A, 608B, 622, 624) out of alignment on the display (e.g., 602) (e.g., the first predefined unit snapping out of a region of the display, such as a focal region, center region, or main viewing region of the display).
In some embodiments, the electronic device (e.g., 600) displays (746) (e.g., subsequent to detecting the first input), on the display, a second user interface (e.g., 612, a non-scrollable user interface, a non-modifiable user interface, a non-navigable user interface, a notification) different from the user interface (e.g., 608, 616, 632, a scrollable user interface, a modifiable user interface, a navigable user interface). In some embodiments, while displaying the second user interface, the electronic device detects (748), via the input element, a second input (e.g., a rotational input, a rotational input on the input element in a clockwise or counter-clockwise direction). In some embodiments, in response to detecting (750) the second input, the electronic device, in accordance with a determination that the second input does not cause a navigation of the second user interface (e.g., because the second user interface is non-scrollable), forgoes generating (752), via the one or more tactile output generators, a tactile output. Thus, in some embodiments, if an input (e.g., rotational input) on the input element causes a change and/or modification of the displayed user interface, the electronic device does not generate a tactile output in response to the input, thereby enabling the user to quickly and easily recognize, while making an input on the device, that the input caused a change and/or modification of the displayed user interface. This in turn 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, in response to detecting (750) the second input, the electronic device, in accordance with a determination that the second input causes a navigation of the second user interface (e.g., because the second user interface is scrollable), generates (754), via the one or more tactile output generators, the tactile output. In some embodiments, if the navigation of the second user interface includes (e.g., only includes) a navigation of continuous content (e.g., continuous text), the generated tactile output is the first type of tactile output/tactile output sequence (e.g., a textural tactile output sequence). In some embodiments, if the navigation of the second sure interface includes (e.g., only includes) a navigation of discrete content (e.g., buttons, affordances, rows, platters, paragraphs), the generated tactile output is the second type of tactile output/tactile output sequence (e.g., a content-driven tactile output sequence) different from the first type of tactile output/tactile output sequence.
In some embodiments, the second user interface (e.g., 612) corresponds to a notification (e.g., of an incoming electronic communication, an alert), and the notification replaces display of the user interface (e.g., 608).
In some embodiments, while displaying the user interface (e.g., 608, 616), the electronic device (e.g., 600) detects (720), via a second input element (e.g., a touch-sensitive surface of the display of the electronic device) different from the input element (e.g., 604), a second input (e.g., a touch-based navigational gesture or scrolling gesture on the display (e.g., 602)). In some embodiments, in response to detecting (722) the second input, the electronic device navigates (724) through the user interface (e.g., scrolls through the user interface). In some embodiments, in response to detecting (722) the second input, the electronic device forgoes generating (726), via the one or more tactile output generators, the tactile output corresponding to the navigation through the user interface.
In some embodiments, in response to detecting (706) the first input (e.g., 601, 605), the electronic device (e.g., 600) generates (740) (e.g., via the one or more tactile out generators and/or one or more speakers of or connected to the electronic device) audio output associated with the tactile output corresponding to the navigation through the user interface (e.g., 608, 616, 632). In some embodiments, in accordance with the determination (742) that the currently-displayed portion of the user interface (e.g., 616) includes the first type of content (e.g., continuous content), the audio output includes an audio output sequence that is associated with (e.g., based on) tactile output sequence 610. In some embodiments, in accordance with the determination (744) that the currently-displayed portion of the user interface (e.g., 608) includes the second type of content (e.g., discrete content), the audio output includes a second type of audio output sequence that is associated with (e.g., based on) the second type of tactile output sequence. Providing an audio output associated with the tactile output improves feedback by providing another avenue for the user to recognize that content is being scrolled and the types of content that are being scrolled in the user interface. Providing improved feedback to the 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, in accordance with a determination (7526) that an event triggering a notification (e.g., 612, activation of an alert, receiving an electronic communication, such as a text or email message) is detected while not detecting input via the input element (e.g., 604), the electronic device (e.g., 600) generates a tactile output (e.g., 614) corresponding to the notification and, optionally, displaying, on the display, the notification. In some embodiments, in accordance with a determination that the event triggering the notification (e.g., activation of an alert, receiving an electronic communication, such as a text or email message) is detected while detecting input via the first input element, the electronic device forgoes generating the tactile output corresponding to the notification and, optionally, forgoing displaying, on the display, the notification. In some embodiments, the tactile output corresponding to the notification is suppressed. In some embodiments, the tactile output corresponding to the notification is delayed until input via the first input element ceases to be detected. In some embodiments, the electronic device displays the notification upon detecting that the first input is no longer being detected.
In some embodiments, in accordance with a determination that an event triggering a notification (e.g., 612, activation of an alert, receiving an electronic communication, such as a text or email message) is detected while detecting the first input (e.g., 601, 605), the electronic device (e.g., 600) forgoes generating (756) a tactile output (e.g., 614) corresponding to the notification (e.g., an alert tactile output) until predefined criteria (e.g., a predetermined amount of time) are met and, optionally, displaying, on the display, the notification for a predetermined amount of time. In some embodiments, in response to a determination that the predetermined criteria have been met (e.g., that the predetermined amount of time has passed), the electronic device generates (758) the tactile output corresponding to the notification and, optionally, displaying, on the display, the notification. In some embodiments, the electronic device displays the notification after the predetermined amount of time has passed even if the first input is still being detected. Thus, in some embodiments, the tactile output corresponding to the notification (e.g., an alert tactile output) does not interfere with the tactile output corresponding to the navigation through the user interface via the first input.
Note that details of the processes described above with respect to method 700 (e.g.,
In
In
In
In
In
In
In
In some embodiments, affordance 808 is a terminus user interface item (e.g., the last, bottom-most user interface item) of user interface 802. In some embodiments, even if affordance 808 is a terminus user interface item of user interface 802, electronic device 600 does not generate a tactile output (e.g., tactile output sequence 630) when the display reaches an end of user interface 802.
In
In response to detecting and while continuing to detect rotational input 809 on input element 604, electronic device 600 scrolls the plurality of platters of user interface 810. In
In
In
In
As described below, method 900 provides an intuitive way for managing user interfaces associated with content-based tactile outputs. The method reduces the cognitive burden on a user for managing and navigating user interfaces, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to navigate user interfaces faster and more efficiently by providing content-based tactile outputs conserves power and increases the time between battery charges.
The electronic device (e.g., 600) displays (902), on the display (e.g., 602), a first portion (e.g., a non-terminal portion) of content (e.g., continuous content, such as continuous text of a messaging application (e.g., an email application or a chat application), discrete content, such as buttons, affordances, rows, platters, paragraphs).
While displaying the first portion of content (e.g., 804), the electronic device (e.g., 600) detects (904), via the input element (e.g., 604), a first input (e.g., 801, 803, a rotational input on the input element, a rotational input in a particular direction, such as a clockwise direction or a counter-clockwise direction). Detecting a rotational input via an input element (e.g., a rotatable input element) enhances usability and user efficiency of the device by enabling a user to quickly, easily, and intuitively navigate/scroll through displayed content. This is in turn 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 response to detecting (906) the first input (e.g., 801, 803), the electronic device (e.g., 600) navigates (908) through the content (e.g., 804) (e.g., scrolling through the content) to display a second portion of the content (e.g., a different portion of the content that was previously not displayed). In response to detecting (906) the first input (e.g., 801, 803), the electronic device generates (910), via the one or more tactile output generators, a first type of tactile output sequence (e.g., 620) that includes one or more tactile outputs (e.g., a textural tactile output sequence that is based on an input metric of the input).
While displaying the second portion of the content, the electronic device (e.g., 600) detects (912), via the input element (e.g., 604), a second input (e.g., a rotational input on the input element, a rotational input in a particular direction, such as a clockwise direction or a counter-clockwise direction).
In response to detecting (914) the second input and in accordance with a determination that the second portion of the content is a terminal portion (e.g., a beginning or end portion, a border portion, an edge portion) of the content, the electronic device (e.g., 600) displays (916) a visual indication (e.g., shifting animation, a bouncing animation (e.g., prior to a bounce-back animation), a rubberbanding-effect animation of the content) that the content (e.g., 804) is a terminal portion of the content. In some embodiments, the terminal portion of the content is a beginning portion (e.g., top portion, a top-edge portion) of the content or an end portion (e.g., a bottom portion, a bottom-edge portion) of the content. Displaying a visual indication that the content is a terminal portion of the content improves visual feedback by providing an intuitive visual effect that enables a user to quickly and easily recognize that an end of the content has been reached while the user interface can still be moved. Providing improved visual feedback to the 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, displaying the visual indication (e.g., the rubberbanding effect) that the content is a terminal portion of the content includes displaying a visual effect that changes as the input (e.g., 803) continues such as displaying an area (e.g., a background) beyond the terminus of the visual content, displaying a graphical element that increases or decreases in size, opacity or brightness as the input continues to be detected after reaching at terminus of the content, or continuing to move the content on the display (e.g., 602) in a respective direction but decreasing the amount by which a unit of movement of the input moves the content in the respective direction as the input continues. Displaying a visual effect that changes as the input continues, such as displaying an area (e.g., a background) beyond the terminus of the visual content improves visual feedback by providing an intuitive visual effect that enables a user to quickly and easily recognize that an end of the content has been reached while the user interface can still be moved. Providing improved visual feedback to the 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, displaying the visual indication that the content is a terminal portion of the content comprises shifting (e.g., moving the portion of content a particular distance in a particular direction on the display (e.g., 602), bouncing the portion of content off of its initial position on the display) the second portion of the content on the display. In some embodiments, after shifting the second portion of the content, the content is subsequently shifted back to its initial position on the display. Displaying a shifting of the content and then a subsequent bounce-back of the content improves visual feedback by providing an intuitive visual effect that enables a user to quickly and easily recognize that an end of the content has been reached while the user interface can still be moved. Providing improved visual feedback to the 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, shifting the second portion of the content on the display (e.g., 602) comprises moving the second portion of the content at least partially off of an edge of the display. In some embodiments, after moving/shifting the second portion of the content at least partially off of an edge of the display, the second portion of the content is subsequently moved/shifted back onto the display, and the content is returned to its initial position.
In some embodiments, a visual characteristic (e.g., a rate of movement of a shifting indication, a color, a brightness, a frequency of a recurring visual effect) of the visual indication that the content is a terminal portion of the content is based on an input metric (e.g., speed and/or magnitude) of the second input.
In response to detecting (914) the second input and in accordance with a determination that the second portion of the content is a terminal portion (e.g., a beginning or end portion, a border portion, an edge portion) of the content, the electronic device (e.g., 600) forgoes generating (918), via the one or more tactile output generators, the first type of tactile output sequence (e.g., 620) or, optionally, forgoing generating any tactile output. In some embodiments, a particular type of tactile output corresponds to a particular tactile output pattern. For example, as described in greater detail above with reference to
In some embodiments, in response to detecting (914) the second input (e.g., 803, a rotational input on the input element (e.g., 604), a rotational input in a particular direction, such as the clockwise direction or a counter-clockwise direction) and in accordance with the determination that the second portion of the content is a terminal portion (e.g., a beginning or end portion, a border portion, an edge portion) of the content, the electronic device (e.g., 600) generates (934), via the one or more tactile output generators, a third type of tactile output sequence (e.g., different from the first type of tactile output sequence, a reduced-amplitude version first type of tactile output sequence). Generating the tactile output sequence upon first reaching an end of the content improves sensory feedback and user efficiency by enabling the user to quickly and easily recognize, while providing a rotational input on an input element, that the end of the content has been reached. Providing improved feedback to the 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, subsequent to detecting the second input (e.g., 803) and while displaying the second portion of the content, the electronic device (e.g., 600) detects (936), via the input element, a third input (e.g., a rotational input on the input element), where the second input (e.g., a rotational input) is in a first direction (e.g., a clockwise direction or a counter-clockwise direction) and the third input is in a direction opposite of that of the second input. In some embodiments, in response to detecting the third input, the electronic device forgoes generating (938), via the one or more tactile output generators, the third type of tactile output sequence (e.g., 630, and instead generating, via the one or more tactile output generators, the first type of tactile output sequence). Forgoing generating the tactile output upon reaching the end of the content a second time (e.g., after a bounce-back from a rubberbanding effect) improves the operability and user convenience of the device by forgoing generating unnecessary feedback, which in turn 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, the third type of tactile output sequence (e.g., 630) corresponds to (e.g., has the same types/pattern of tactile outputs as) the first type of tactile output sequence, the first type of tactile output sequence is associated with a first type of audio output sequence, and the third type of tactile output sequence is associated with a second type of audio output sequence different from (e.g., different in types and/or pattern) the first type of audio output sequence. In some embodiments, similar to a tactile output, a particular type of audio output corresponds to a particular type of audio output pattern. For example, an audio output pattern specifies characteristics of an audio output, such as the magnitude/amplitude/volume of the audio output, the shape of a sound waveform of the audio output, the frequency of the audio output, and/or the duration of the audio output. When audio outputs with different audio output patterns are generated by a device (e.g., via one or more tactile output generators that move a moveable mass to generate audio outputs, via one or more speakers), the audio outputs may invoke different audio-related sensations in a user holding or touching the device or proximate to the device.
In some embodiments, subsequent to detecting the second input (e.g., 803) and while displaying the second portion of the content, the electronic device (e.g., 600) detects (926), via the input element (e.g., 604), a third input (e.g., a third rotation of the input element), where the third input is in a direction opposite of the second input. In some embodiments, in response to detecting (928) the third input, the electronic device navigates back (930) (e.g., navigating in the opposite direction from the navigation caused by the first input) through the content to display the first portion of the content. In some embodiments, in response to detecting (928) the third input, the electronic device generates (932), via the one or more tactile output generators, the first type of tactile output sequence (e.g., a textural tactile output sequence that is based on an input metric of the input).
In some embodiments, while displaying the second portion of the content, the electronic device (e.g., 600) detects (940), on the display (e.g., 602, via a touch-sensitive surface of the display), a fourth input (e.g., a touch-based scrolling input on a touch-sensitive surface of the display and not on the input element). In some embodiments, in response to detecting (942) the scrolling input and in accordance with the determination that the second portion of the content is a terminal portion (e.g., a beginning or end portion, a border portion, an edge portion) of the content, the electronic device displays (944) the visual indication that the content is a terminal portion of the content. In some embodiments, in response to detecting (942) the scrolling input and in accordance with the determination that the second portion of the content is a terminal portion (e.g., a beginning or end portion, a border portion, an edge portion) of the content, the electronic device forgoes generating (946), via the one or more tactile output generators, the first type of tactile output sequence and, optionally, forgoing any tactile output/tactile output sequence associated with navigating through the content.
In some embodiments, in response to detecting (920) the second input (e.g., 803) and in accordance with a determination that the second portion of the content is not a terminal portion (e.g., a beginning or end portion, a border portion, an edge portion) of the content, the electronic device (e.g., 600) displays (922), on the display (e.g., 602), a third portion of the content (e.g., navigating through the content to display a portion of the content adjacent to/continuous with the second portion of the content). In some embodiments, in response to detecting (920) the second input and in accordance with a determination that the second portion of the content is not a terminal portion (e.g., a beginning or end portion, a border portion, an edge portion) of the content, the electronic device generates (924), via the one or more tactile output generators, the first type of tactile output sequence (e.g., a textural tactile output sequence that is based on an input metric of the input). Generating a different type of tactile output for navigating/scrolling through content and for reaching an end of the content improves feedback by enabling the user to quickly and easily recognize that whether the displayed content is being scrolled and can be further scrolled. Providing improved feedback to the 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.
Note that details of the processes described above with respect to method 900 (e.g.,
In
In
In
After moving back (e.g., “snapping” back) to the focal point of the display, electronic device 600 detects, via input element 604, a rotational input 1003. In
In
In
In
In
In
In
In
Thus, as shown by
As described below, method 1100 provides an intuitive way for managing user interfaces associated with content-based tactile outputs. The method reduces the cognitive burden on a user for managing and navigating user interfaces, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to navigate user interfaces faster and more efficiently by providing content-based tactile outputs conserves power and increases the time between battery charges.
The electronic device (e.g., 600) displays (1102), on the display (e.g., 602), a user interface (e.g., 1002, a user interface that includes continuous content, such as continuous text of a messaging application, and/or discrete content, such as buttons, affordances, rows, platters, paragraphs).
While displaying the user interface (e.g., 1002), the electronic device (e.g., 600) detects (1104) a first portion of an input (e.g., 1001, 1005, a rotational input on the rotatable input element or a touch gesture on the touch-sensitive display) at the device. Detecting a rotational input via an input element (e.g., a rotatable input element) enhances usability and user efficiency of the device by enabling a user to quickly, easily, and intuitively navigate/scroll through displayed content. This is in turn 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 response to detecting a first portion of the input (e.g., 1001, 1005), the electronic device (e.g., 600) moves (1106) a user interface object (e.g., 1004, a unit of content of the user interface) across the display of the device in accordance with the movement of the input. Moving the user interface object across the display in accordance with the movement of the input provides visual feedback that the rotational input is controlling the movement of the user interface object. Providing improved visual feedback to the 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.
After detecting the first portion of the input, the electronic device (e.g., 600) detects (1108) a second portion of the input (e.g., 1003, 1007) at the device (e.g., an end of the input or movement of the user interface object beyond (e.g., 1004) a threshold amount, where the second portion of the input is a continuation of the first portion of the same input).
In response to detecting (1110) the second portion of the input (e.g., 1003, 1007, an end of the input or movement of the user interface object (e.g., 1004) beyond a threshold amount), in accordance with a determination that the input (e.g., 1007) includes movement of a contact on the touch-sensitive display (e.g., 602) and that the movement moves the user interface object across the display by more than a first threshold amount (e.g., before an end of the input is detected), the electronic device (e.g., 600) moves (1112) (e.g., by snapping) the user interface object to a respective (e.g., predefined) position on the display. In some embodiments, the movement of the user interface object to the respective position on the display occurs upon detecting an end of the input (e.g., liftoff of the contact). In some embodiments, the movement of the user interface object to the respective position on the display occurs upon detecting movement of the user interface object by more than the first threshold amount without regard to whether or not the input has ended. In some embodiments, moving the user interface object to the respective (e.g., predefined) position on the display comprises “snapping” the user interface object to the respective position on the display, where “snapping” the user interface object comprises moving and aligning the object to the next alignment point (e.g., the respective position) on the display.
In response to detecting (1110) the second portion of the input (e.g., 1003, 1007, an end of the input or movement of the user interface object (e.g., 1004) beyond a threshold amount), in accordance with a determination that the input (e.g., 1007) includes movement of a contact on the touch-sensitive display (e.g., 602) and that the movement moves the user interface object across the display by less than the first threshold amount (e.g., before an end of the input is detected), the electronic device (e.g., 600) forgoes moving (1114) the user interface object to the respective (e.g., predefined) position on the display. Forgoing moving the user interface object to the respective position on the display in response to an input provides visual feedback that the input is insufficient to move the user interface object to the respective position. Further, it helps to prevent a user from accidently moving the user interface object to the respective position on the display against the user's intention. Providing improved visual feedback and additional control options and reducing the number of inputs needed to perform an operation 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 response to detecting (1110) the second portion of the input (e.g., 1003, 1007, an end of the input or movement of the user interface object (e.g., 1004) beyond a threshold amount), in accordance with a determination that the input (e.g., 1003) includes rotational input directed to the rotatable input element (e.g., 604) and that the rotational input moves the user interface object across the display by more than a second threshold amount that is less than the first threshold amount (e.g., before an end of the input is detected), the electronic device (e.g., 600) moves (1116) (e.g., by snapping) the user interface object to the respective (e.g., predefined) position on the display (e.g., the object snaps into the respective position on the display even if it moves by less than the first threshold amount so long as it moves by more than the second threshold amount). In some embodiments, the movement of the user interface object to the respective position on the display occurs upon detecting an end of the input (e.g., an end of a touch on the rotatable input element or ceasing to detect rotation of the rotatable input element for at least a threshold amount of time). In some embodiments, the movement of the user interface object to the respective position on the display occurs upon detecting movement of the user interface object by more than the first threshold amount without regard to whether or not the input has ended.
In response to detecting (1110) the second portion of the input (e.g., 1003, 1007, an end of the input or movement of the user interface object (e.g., 1004) beyond a threshold amount), in accordance with a determination that the input (e.g., 1003) includes rotational input directed to the rotatable input element (e.g., 604) and that the rotational input moves the user interface object across the display by less than the second threshold amount (e.g., before an end of the input is detected), the electronic device (e.g., 600) forgoes moving (1118) the user interface object to the respective (e.g., predefined) position on the display. In some embodiments, the second portion of the input includes one or more of: liftoff of the contact from the touch-sensitive display or ceasing to detect a touch on the rotatable input element or ceasing to detect rotation of the rotatable input element for more than a threshold amount of time, or detecting rotation of the rotatable input element that moves the user interface object across the display by more than the second threshold amount.
In some embodiments, in response to detecting (1110) the second portion of the input (e.g., 1003, 1007, an end of the input or movement of the user interface object (e.g., 1004) beyond a threshold amount), in accordance with a determination that the input (e.g., 1007) includes movement of a contact on the touch-sensitive display (e.g., 602) and that the movement moves the user interface object across the display by less than the first threshold amount, the electronic device (e.g., 600) moves (1132) (e.g., by snapping) the user interface object back in the opposite direction (e.g., snapping the user interface object back to the previous location of the user interface object before the input started).
In some embodiments, in response to detecting (1110) the second portion of the input (e.g., 1003, 1007, an end of the input or movement of the user interface object (e.g., 1004) beyond a threshold amount), in accordance with a determination that the input (e.g., 1003) includes rotational input directed to the rotatable input element (e.g., 604) and that the rotational input moves the user interface object across the display by less than the second threshold amount, the electronic device (e.g., 600) moves (1134) (e.g., by snapping) the user interface object back in the opposite direction (e.g., snapping the user interface object back to the previous location of the user interface object before the input started). Setting a higher threshold for moving the user interface object to the respective position on the display for one type of input (e.g., a touch input) over a different type of input (e.g., a rotational input on the input element) helps to prevent a user from accidently moving the user interface object to the respective position on the display against the user's intention when one type of input (e.g., a touch input) is more prone to accidental inputs than the different type of input (e.g., the rotational input). Providing additional control options and reducing the number of inputs needed to perform an operation 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, the electronic device (e.g., 600) includes a (e.g., single) tactile output generator (e.g., wherein the tactile output generator is located in and is connected to (e.g., and configured to generate tactile outputs to) the rotatable input element (e.g., 604) and a housing of the electronic device).
In some embodiments, the electronic device (e.g., 600) includes one or more tactile output generators that generate localized tactile outputs directed to the rotatable input element (e.g., 604) and one or more separate tactile output generators that generate tactile outputs for the electronic device that are not specifically directed to the rotatable input element (e.g., and instead is located in and is connected to (e.g., and configured to generate tactile outputs to) a main housing of the electronic device or generate tactile outputs that are localized to a different component of the electronic device). In some embodiments, the tactile output generator located in or near the rotatable input element, and is configured to generate tactile outputs that move the rotatable input element relative to the housing (e.g., by moving the shaft of the rotatable input element).
In some embodiments, the one or more tactile output generators are configured to (e.g., in addition to generating tactile outputs) generate audio outputs (e.g., wherein the audio outputs correspond to and/or are associated with tactile outputs generated by the one or more tactile output generators and are generated in a coordinated manner with the tactile outputs to generate combined audio/tactile outputs).
In some embodiments, in response to detecting (1110) the second portion of the input (e.g., an end of the input or movement of the user interface object beyond a threshold amount), in accordance with the determination that the input (e.g., 1003) includes rotational input directed to the rotatable input element (e.g., 604) and that the rotational input meets criteria for moving (e.g., snapping) the user interface object (e.g., 1004) to the respective (e.g., predefined) position on the display, the electronic device (e.g., 600) moves (1136) the user interface object to the respective position on the display in conjunction with generating (e.g., via the one or more tactile output generators) a tactile output (e.g., a sequence of tactile outputs) corresponding to the movement of the user interface object. In some embodiments, if the displayed content is a first type of content (e.g., continuous content, such as continuous text), the tactile output includes a first type of tactile output sequence (e.g., a textural tactile output sequence) that includes one or more tactile outputs determined based on an input metric (e.g., a speed and/or magnitude) of the input. In some embodiments, if the displayed content is a second type of content (e.g., discrete content, such as buttons, affordances, rows, platters, paragraphs), the tactile output includes a second type of tactile output sequence (e.g., a content-driven tactile output sequence) that includes one or more tactile outputs determined based on movement of predefined units of content in the user interface. In some embodiments, in response to detecting (1110) the second portion of the input, in accordance with the determination that the input includes movement of a contact on the touch-sensitive display that meets criteria for moving (e.g., snapping) the user interface object to the respective (e.g., predefined) position on the display, the electronic device moves (1138) the user interface object to the respective position on the display without generating (e.g., via the one or more tactile output generators) the tactile output. Generating the tactile output for one type of input (e.g., a rotational input on the input element) but not for another type of input (e.g., a touch input) enables the device to conserve battery power and thus improve battery life by providing sensory feedback for (e.g., only for) types of input that will have a greater benefit to user experience and convenience if the sensory feedback were provided.
In some embodiments, an amplitude of the tactile output is based on (e.g., corresponds to) a size of the user interface object (e.g., 1004). In some embodiments, the amplitudes of the one or more tactile outputs are larger if the user interface object is a relatively larger object and are smaller if the user interface object is a relatively smaller object.
In some embodiments, the tactile output (e.g., a sequence of tactile outputs) corresponding to the movement (e.g., snapping) of the user interface object (e.g., 1004) to the respective (e.g., predefined) position on the display (e.g., 602) comprise a tactile output sequence having a first predetermined frequency range (e.g., 180-200 Hz) that is different from a second predetermined frequency range (e.g., around 100 Hz) corresponding to a tactile output sequence associated with displaying a notification (e.g., for an alert, for an incoming electronic communication) on the display. Thus, from the perspective of a user of the electronic device (e.g., 600), the sensory sensation experienced from tactile output sequence having the first predetermined frequency (e.g., 180-200 Hz) and from the tactile output sequence having the second predetermined frequency (e.g., around 100 Hz) are distinguishable.
In some embodiments, while displaying the user interface (e.g., 1002), the electronic device (e.g., 600) detects (1120) a second input (e.g., a press input, a press-and-hold input, an input applied with a downward pressing force, a non-rotational input, a non-rotational touch input, a tap input) directed to the rotatable input element (e.g., 604). In some embodiments, in response to detecting the second input directed to the rotatable input element, the electronic device forgoes (e.g., suppresses) generating (1122), via the one or more tactile output generators, tactile output corresponding to rotation of the rotatable input element (e.g., even when the second input includes both a press of the rotatable input element and rotational input directed to the rotatable input element). Thus, in some embodiments, certain types of inputs on the rotatable input element (e.g., a rotatable input that causes a modification of the user interface) causes the electronic device to generate (e.g., via a tactile output generator) tactile outputs, whereas certain types of inputs on the rotatable input element (e.g., a press input, a press-and-hold input, or a touch input) does not cause the electronic device to generate (e.g., via a tactile output generator) tactile outputs.
In some embodiments, while displaying the user interface (e.g., 1002), the electronic device (e.g., 600) detects (1124) a third input directed to the rotatable input element (e.g., 604). In some embodiments, in response to detecting (1126) the third input directed to the rotatable input element, in accordance with a determination that the third input includes rotation of the rotatable input element without a press of the rotatable input element, the electronic device generates (1128), via the one or more input devices, tactile output corresponding to rotation of the rotatable input element. In some embodiments, in response to detecting (1134) the third input directed to the rotatable input element, in accordance with a determination that the third input includes rotation of the rotatable input element and a press of the rotatable input element, the electronic device forgoes generating (1130), via the one or more tactile output generators, the tactile output corresponding to rotation of the rotatable input element.
Note that details of the processes described above with respect to method 1100 (e.g.,
In
In
In
In
In
In
In
In
In
In
In
In
Subsequently, electronic device 600 further detects, via input element 604, a rotational input 1209 (e.g., in a clockwise direction). In
In
As described below, method 1300 provides an intuitive way for managing user interfaces associated with content-based tactile outputs. The method reduces the cognitive burden on a user for managing and navigating user interfaces, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to navigate user interfaces faster and more efficiently by providing content-based tactile outputs conserves power and increases the time between battery charges.
The electronic device (e.g., 600) displays (1302), on the display (e.g., 602), a user interface (e.g., 1202, a time user interface correlated to changing a time setting of the device) that includes a first adjustable item (e.g., 1204, a first time item, such as hours) and a second adjustable item (e.g., 1206, a second time item, such as minutes). In some embodiments, the user interface is a time user interface, where the time user interface includes a display of the current time, and where the current hour is displayed in the first adjustable item and the current minute is displayed in the second adjustable item. In some embodiments, the time user interface includes a plurality of selectable setting options (e.g., 1210) that are used to adjust the first adjustable time item or the second adjustable time item. In some embodiments, the plurality of selectable setting options surround (e.g., in a circular shape, such as a wheel) the current time setting that is displayed at the center of the time user interface. Displaying the first and second adjustable items together with the selectable settings options enables a user to quickly and easily view adjustments being made to an adjustable item while the adjustment is being made. Providing additional control options and reducing the number of inputs needed to perform an operation 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, the first adjustable item corresponds to a first portion (e.g., the hour of the time) of a user interface setting (e.g., time) and the second adjustable item corresponds to a second portion (e.g., the minute of the time) of the user interface setting.
In some embodiments, the user interface corresponds to a time-setting user interface (e.g., a “wheel of time” user interface), the first adjustable item corresponds to an hour setting of the electronic device (e.g., for an alarm of the electronic device), and the second adjustable item corresponds to a minute setting of the electronic device (e.g., for an alarm of the electronic device).
While displaying the user interface (e.g., 1202), the electronic device (e.g., 600) detects (1304), via the input element (e.g., 604), a rotational input (e.g., 1201, 1203, 1205, 1207, 1209, in a clockwise or counter-clockwise direction).
In response to detecting (1306) the rotational input (e.g. 1201, 1203, 1205, 1207, 1209), in accordance with a determination (1308) that the first adjustable item (e.g., 1204) is currently-selected, the electronic device (e.g., 600) adjusts (1310), based on the rotational input, the first adjustable item (e.g., changing the current hour setting). While adjusting the first adjustable item, the electronic device generates (1312), via the one or more tactile output generators, a first sequence of tactile outputs (e.g., 610) including one or more tactile outputs having a first amplitude (e.g., without generating tactile outputs having a second amplitude that is different from the first amplitude). Generating the first sequence of tactile outputs in response to detecting the rotational input improves sensory feedback and enhances user experience by enabling the user to perceive of adjustments being made to an adjustable item while the adjustments are being made. Providing additional control options and reducing the number of inputs needed to perform an operation 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 response to detecting (1306) the rotational input, in accordance with a determination (1318) that the second adjustable item (e.g., 1206) is currently-selected, the electronic device (e.g., 600) adjusts (1320) (e.g., without adjusting the first adjustable item), based on the rotational input (e.g., 1201, 1203, 1205, 1207, 1209), the second adjustable item (e.g., changing the current minute setting). While adjusting the second adjustable item, the electronic device generates (1322), via the one or more tactile output generators, a second sequence of tactile outputs (e.g., 1220) including one or more tactile outputs having a second amplitude that is different from the first amplitude (e.g., without generating tactile outputs having the first amplitude). In some embodiments, the second amplitude is smaller than the first amplitude, and thus the second type of tactile output is a smaller-amplitude tactile output than the first type of tactile output. Generating the second sequence of tactile outputs while adjusting the second adjustable item and generating the first sequence of tactile outputs while adjusting the first adjustable item improves feedback by enabling a user to quickly and easily recognize, without looking closely into the display, whether the user is adjusting the first or second adjustable item. Providing improved visual feedback to the 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, adjusting, based on the rotational input (e.g., 1201, 1203, 1205, 1207, 1209, an input having an input magnitude (e.g., an amount of rotation of the rotational input)), the first adjustable item (e.g., 1204) comprises adjusting the first adjustable item by a first number of values (e.g., values between 1 through 12 for hours). In some embodiments, adjusting, based on the rotational input, the second adjustable item (e.g., 1206) comprises adjusting the second adjustable items by a second number of values, the second number of values (e.g., values between 1 through 60 for minutes) different from the first number of values. In some embodiments, the same magnitude of input (e.g., an amount of rotation) adjusts the values of the first adjustable item by a greater amount than that same magnitude of input adjusts the second adjustable item.
In some embodiments, generating, via the one or more tactile output generators, the first sequence of tactile outputs (e.g., 610) including one or more tactile outputs having the first amplitude comprises generating the first sequence of tactile outputs irrespective of the direction (e.g., clockwise direction, counter-clockwise direction) of the rotational input (e.g., 1201, 1203, 1205, 1207, 1209). In some embodiments, generating, via the one or more tactile output generators, the second sequence of tactile outputs (e.g., 1220) including one or more tactile outputs having the second amplitude comprises generating the second sequence of tactile outputs irrespective of the direction (e.g., clockwise direction, counter-clockwise direction) of the rotational input.
In some embodiments, while adjusting the first adjustable item (e.g., 1204), the electronic device (e.g., 600) moves (1314), on the user interface (e.g., 1202), an indicator (e.g., 1212) through a plurality of predetermined alignment points (e.g., 1210), where the indicator snaps to (e.g., aligns to, fits to, stops at) the alignment points of the plurality of alignment point of the predetermined alignment points, and the one or more tactile outputs of the first sequence of tactile outputs are coordinated with the snapping of the indicator to the alignment points of the plurality of alignment points. In some embodiments, the indicator snapping to an alignment point comprises using a particular threshold to determine the amount of rotation of the rotatable input element is required to reach the alignment point, and if the threshold is not reached, then snapping to a prior alignment point, and if the threshold is reached, then snapping to the next alignment point. Moving the indicator through the plurality of predetermined alignment points improves visual feedback by enabling the user to quickly and easily view adjustments being made to the first or second adjustable items in an intuitive manner. Providing improved visual feedback to the 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, while adjusting the first adjustable item (e.g., 1204), the electronic device (e.g., 600) displays (1316), on the display (e.g., 602), the plurality of predetermined alignment points (e.g., 1210), where the plurality of predetermined alignment points includes a first number of alignment points. In some embodiments, while adjusting the second adjustable item (e.g., 1206), the electronic device displays (1324), on the display, a second plurality of predetermined alignment points (e.g., 1210), where the second plurality of predetermined alignment points includes a second number of alignment points different from the first number. In some embodiments, the first adjustable item corresponds to the hour setting of a time, and each of the plurality of predetermined alignment points corresponds to a particular hour setting. Thus, in some embodiment, the first number is twelve, with each alignment point corresponding to a particular hour setting. In some embodiments, the second adjustable item corresponds to the minute setting of a time, and each of the plurality of predetermined alignment points corresponds to a particular minute setting. Thus, in some embodiments, the second number is sixty, with each alignment point corresponding to a particular minute setting.
In some embodiments, in response to detecting (1326) the rotational input (e.g., 1201, 1203, 1205, 1207, 1209), in accordance with a determination that the rotational input is of a first rotational speed, the electronic device (e.g., 600) moves (1328) the indicator (e.g., 1212) through the plurality of displayed values (e.g., 1210) at a first speed associated with the first rotational speed. In some embodiments, in response to detecting (1326) the rotational input, in accordance with a determination that the rotational input is of a second rotation speed different from the first rotational speed, the electronic device moves (1330) the indicator through the plurality of displayed values at a second speed associated with the second rotational speed, the second speed different from the first speed. In some embodiments, if the second rotational speed of the rotational input is greater than the first rotational speed, the second speed of the indicator moving through the plurality of displayed values is greater than the first speed of the indicator, and if the second rotational speed of the rotational input is slower than the second rotational speed, then the second speed of the indicator moving through the plurality of displayed values is slower than the first speed of the indicator.
In some embodiments, while displaying the user interface (e.g., 1202) and while the first adjustable item (e.g., 1204) is a currently-selected adjustable item, the electronic device (e.g., 600) detects (1332) (e.g., via one or more input devices of the electronic device, such as a touch-sensitive surface of the display) a first input (e.g., 1205, a tap gesture on the display). In some embodiments, in response to detecting the first input, the electronic device sets (1334) the second adjustable item (e.g., 1206) (e.g., instead of the first adjustable item) as the currently-selected adjustable item.
Note that details of the processes described above with respect to method 1300 (e.g.,
In
In some embodiments, in addition to generating tactile output sequence 620 in
In
In some embodiments, in addition to generating tactile output sequence 620 in
In
In some embodiments, in addition to generating tactile output sequence 620 in
In
In some embodiments, in addition to generating tactile output sequence 620 in
In
In some embodiments, in addition to generating tactile output sequence 620 in
In
In some embodiments, as shown by graph 1410, the magnitude (e.g., amplitude) of generated tactile outputs remains constant when the speed of rotation of a detected rotational input on input element 604 is less than a speed 1418. The magnitude of generated tactile outputs decreases (e.g., linearly) when the speed of rotation of the detected rotational input on input element 604 is between speed 1418 and a speed 1420. The magnitude of generated tactile outputs again remains constant when the speed of rotation of the detected rotational input on input element 604 is greater than speed 1420.
In some embodiments, the number of discrete tactile outputs that are generated for a respective rotation of input element 604 from a detected rotational input shares a similar (e.g., but inverse) relationship with the speed of rotation of the rotational input. That is, the number of discrete tactile outputs for the respective rotation of input element 604 remains constant when the speed of rotation of the detected rotational input for the respective amount of rotation of input element 604 is less than a first speed (e.g., speed 1418). The number of generated tactile outputs becomes greater (e.g., linearly) as the speed of rotation of the detected rotational input for the respective amount of rotation of input element 604 increases between the first speed (e.g., speed 1418) and a second speed (e.g., speed 1420). The number of discrete tactile outputs of generated tactile outputs remains constant when the speed of rotation of the detected rotational input for the respective amount of rotation of input element 604 is greater than the second speed (e.g., speed 1418).
Graph 1422 includes a curve 1428 (e.g., similar to curve 1416) illustrating the relationship between the speed of rotation of input element 604 and the resulting magnitude of generated tactile outputs. Graph 1422 also includes a curve 1430 illustrating the relationship between the speed of rotation of input element 604 and the resulting magnitude of generated audio outputs.
In some embodiments, as shown by graph 1430, the magnitude (e.g., amplitude) of generated audio outputs remains constant when the speed of rotation of a detected rotational input on input element 604 is less than a speed 1430. The magnitude of generated audio outputs decreases (e.g., linearly) when the speed of rotation of the detected rotational input on input element 604 is between speed 1430 and a speed 1432. The magnitude of generated audio outputs again remains constant when the speed of rotation of the detected rotational input on input element 604 is greater than speed 1432.
As shown in
In some embodiments, the number of discrete audio outputs that are generated for a respective rotation of input element 604 from a detected rotational input shares a similar (e.g., but inverse) relationship with the speed of rotation of the rotational input. That is, the number of discrete audio outputs for the respective amount of rotation of input element 604 remains constant when the speed of rotation of the detected rotational input for the respective amount of rotation of input element 604 is less than a first speed (e.g., speed 1430). The number of generated audio outputs becomes greater (e.g., linearly) as the speed of rotation of the detected rotational input for the respective amount of rotation of input element 604 increases between the first speed (e.g., speed 1430) and a second speed (e.g., speed 1432). The number of discrete audio outputs respective amount of rotation of input element 604 remains constant when the speed of rotation of the detected rotational input for the respective amount of rotation of input element 604 is greater than the second speed (e.g., speed 1432).
As with the magnitude of audio outputs, in some embodiments, the speeds that result in changes to the number of discrete audio outputs (e.g., speeds 1430 and 1432) respective amount of ration of rotational input 604 is not the same as the speeds that result in changes to the number of discrete tactile outputs for the respective amount of ration of rotational input 604 (e.g., speeds 1418 and 1420). Speed 1430 can be less than, equal to, or greater than speed 1418 and, similarly, speed 1432 can be less than, equal to, or greater than speed 1420.
As described below, method 1500 provides an intuitive way for managing user interfaces associated with content-based tactile outputs. The method reduces the cognitive burden on a user for managing and navigating user interfaces, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to navigate user interfaces faster and more efficiently by providing content-based tactile outputs conserves power and increases the time between battery charges.
While displaying, on the display (e.g., 602), a user interface (e.g., 1402), the electronic device (e.g., 600) detects (1502), via the rotatable input element (e.g., 604), a rotational input (e.g., 1401, 1403, 1405, 1407, 1409, a continuous rotational input on the rotatable input element that continues for a period of time, such as 1 second or 2 seconds).
While detecting the rotational input (e.g., 1401, 1403, 1405, 1407, 1409), the electronic device (e.g., 600) generates (1506), via the one or more tactile output generators, a plurality of tactile outputs (e.g., 620, a sequence of tactile outputs (e.g., discrete, individual tactile outputs)), where a type (e.g., a major-type of tactile output, a minor-type of tactile output, a major-reduced-type tactile output) of the tactile outputs is associated with a modification of the user interface (e.g., 1402), and where, in accordance with a determination (1508) that a speed (e.g., rotational speed) of the rotational input (e.g., 1401) is a first speed (e.g., a first rotational speed), the electronic device generates (1510) a first number of tactile outputs for a respective amount of rotation of the rotatable input element (e.g., 604), and in accordance with a determination (1514) that the speed (e.g., rotational speed) of the rotational input (e.g., 1405) is a second speed (e.g., a second rotational speed) that is different from (e.g., faster than or slower than) the first speed, the electronic device generates (1516) a second number of tactile outputs (e.g., different from the first number of tactile outputs) for the respective amount of rotation of the rotatable input element. Generating a plurality of tactile outputs in response to the rotational input, where one or more characteristics (e.g., magnitude/amplitude, rate of occurrence) of the tactile outputs differ based on a rotation speed of the rotational input improves sensory feedback by enabling the user to quickly and easily perceive of the speed and which the user is navigating/scrolling the user interface, and to adjust accordingly. Providing improved feedback to the 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, the second speed (e.g., 1420) is greater than the first speed (e.g., 1418) (e.g., the rotatable input element (e.g., 604) is rotated at a faster speed/rate for the second speed than for the first speed), and the second number of tactile outputs is smaller than the first number of tactile outputs for the respective amount of rotation of the rotatable input element. In some embodiments, if the second speed is slower than the first speed (e.g., the rotatable input element is rotated at a slower speed/rate for the second speed than for the first speed), the second number of tactile outputs is greater than the first number of tactile outputs for the same respective amount of rotation of the rotatable input element.
In some embodiments, the second speed (e.g., 1420) is greater than the first speed (e.g., 1418) (e.g., the rotatable input element (e.g., 604) is rotated at a faster speed/rate for the second speed than for the first speed), and amplitudes of the second number of tactile outputs is smaller than amplitudes of the first number of tactile outputs. In some embodiments, if the second speed is slower than the first speed (e.g., the rotatable input element is rotated at a slower speed/rate for the second speed than for the first speed), the amplitudes of the second number of tactile outputs is greater than amplitudes of the first number of tactile outputs.
In some embodiments, in accordance with the modification of the user interface (e.g., 1402) being a first type of modification (e.g. navigating/scrolling continuous content, such as a notification or continuous text), the generated plurality of tactile outputs (e.g., 620) are (1536) of a first type (e.g., plurality of tactile outputs having a first number of tactile outputs in the sequence and/or a first amplitude). In some embodiments, in accordance with the modification of the user interface being a second type of modification (e.g., navigating/scrolling discrete content, such as buttons, affordances, platters, paragraphs), the generated plurality of tactile outputs are (1538) of a second type different from the first type (e.g., plurality of tactile outputs having a second number of tactile outputs in the sequence and/or a second amplitude). Generating a particular type of tactile outputs for a particular type of modification of the user interface improves sensory feedback by enabling a user to quickly and easily recognize the type of modification that was made to the user interface, in particular if the modification was accidental and against the user's intent. Providing improved feedback to the 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, the type of the tactile outputs that are generated is based (e.g., based at least in part) on content displayed in the user interface that is being modified while the rotational input (e.g., 1401, 1403, 1405, 1407, 1409) is detected, as described above with reference to
In some embodiments, the number of tactile outputs of the plurality of tactile outputs (e.g., 620) is at least in part based on a size characteristic (e.g., a size of the display of the device) of the electronic device (e.g., 600). For example, the display (e.g., 602) of the electronic device is of a first size, the number of tactile outputs included in the plurality of tactile outputs is smaller than if the display of the electronic device is of a second size, where the second size is larger than the first size.
In some embodiments, amplitudes of the plurality of tactile outputs (e.g., 620) are at least in part based on a size characteristic (e.g., a size of the display of the device) of the electronic device (e.g., 600). For example, if the display (e.g., 602) of the electronic device is of a first size, the amplitudes are relatively smaller than if the display of the electronic device is of a second size, where the second size is larger than the first size. Basing (e.g., at least in part) the number of tactile outputs of the plurality of tactile outputs and/or the amplitudes of the tactile outputs based on the size of the device improves operability of the device by customizing the number of tactile outputs to be functionality appropriate with the size of the device, which in turn 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, while detecting (1504) the rotational input (e.g., 1401, 1403, 1405, 1407, 1409), in accordance with a determination (1524) that a speed (e.g., rotational speed) of the rotational input is a third speed (e.g., a third rotational speed) that is faster than the first speed and slower than the second speed (e.g., the third speed corresponds to a rotational speed that is in between the rotational speed corresponding to the first speed and the rotational speed corresponding to the third speed), the electronic device (e.g., 600) generates (1526) the first number of tactile outputs (e.g., 620) for the respective amount of rotation of the rotatable input element (e.g., 604). Thus, in some embodiments, the number of tactile outputs generated for the respective amount of rotation of the rotatable input element at the first speed of the rotational input and at the third speed of the rotational input (e.g., where the third speed is faster than the first speed but slower than the second speed, and thus is a speed that is between the first and second speeds) is the same, but the number of tactile outputs generated for the respective amount of rotation of the rotatable input element at the second speed is different from the number of tactile outputs generated at the first and third speeds.
In some embodiments, while detecting (1504) the rotational input, in accordance with the determination (1508) that the speed (e.g., rotational speed) of the rotational input (e.g., 1401, 1403, 1405, 1407, 1409) is the first speed (e.g., a first rotational speed), the plurality of tactile outputs has (1512) a first amplitude. In some embodiments, while detecting (1504) the rotational input, in accordance with a determination (1524) that a speed (e.g., rotational speed) of the rotational input is a third speed (e.g., a third rotational speed) that is faster than the first speed and slower than the second speed (e.g., the third speed corresponds to a rotational speed that is in between the rotational speed corresponding to the first speed and the rotational speed corresponding to the third speed), the plurality of tactile outputs have (1528) the first amplitude. Thus, in some embodiments, the plurality of tactile outputs (e.g., 620) have the same amplitude while the rotational input is detected at the first speed and at the third speed, even though the third speed is greater than the first speed. In some embodiments, in accordance with the determination (1514) that the speed (e.g., rotational speed) of the rotational input is the second speed (e.g., a second rotational speed) that is different from (e.g., faster than or slower than) the first speed and from the third speed, the plurality of tactile outputs have (1518) a second amplitude different from (e.g., greater than, smaller than) the first amplitude. In some embodiments, the second speed is a threshold speed of the rotational input at which the rotational input causes the amplitudes of the plurality of tactile outputs to change (e.g., become bigger or smaller).
In some embodiments, while detecting (1504) the rotational input, in accordance with the determination (1514) that the speed (e.g., rotational speed) of the rotational input (e.g., 1401, 1403, 1405, 1407, 1409) is the second speed (e.g., a first rotational speed), a number of the tactile outputs for the respective amount of rotation of the rotatable input element is (1520) a third number, where the third number corresponds to a minimum number (e.g., the smallest number of tactile outputs generated by the electronic device). In some embodiments, in accordance with a determination (1530) that a speed (e.g., rotational speed) of the rotational input is a fourth speed (e.g., a fourth rotational speed) that is faster than the second speed (e.g., the fourth speed corresponds to a rotational speed that is greater than the rotational speed corresponding to the second speed), the number of tactile outputs corresponds to (1532) the third number. Thus, in some embodiments, the electronic device (e.g., 600) does not generate a smaller number of tactile outputs than the third number (e.g., a minimum number) of tactile outputs even if the speed of the rotation input further changes (e.g., becomes even faster).
In some embodiments, while detecting (1504) the rotational input (e.g., 1401, 1403, 1405, 1407, 1409), in accordance with the determination (1514) that the speed (e.g., rotational speed) of the rotational input is the second speed (e.g., a first rotational speed), the plurality of tactile outputs have (1522) a third amplitude, where the third amplitude corresponds to a minimum amplitude (e.g., the smallest greater-than-zero tactile output amplitude generated by the one or more tactile output generators of the electronic device). In some embodiments, in accordance with a determination (1530) that a speed (e.g., rotational speed) of the rotational input is a fourth speed (e.g., a fourth rotational speed) that is faster than the second speed (e.g., the fourth speed corresponds to a rotational speed that is greater than the rotational speed corresponding to the second speed), the plurality of tactile outputs have (1534) the third amplitude. Thus, in some embodiments, the plurality of tactile outputs have the same amplitude while the rotational input is detected at the second speed and at the fourth speed, even though the fourth speed is greater than the second speed.
In some embodiments, while detecting (1504) the rotational input (e.g., 1401, 1403, 1405, 1407, 1409), in accordance with a determination that the second speed corresponds to a maximum threshold speed (e.g., a maximum threshold rotational speed), the second number of tactile outputs corresponds to (1526) a maximum number of tactile outputs that can be generated for the respective amount of rotation of the rotatable input element. Thus, in some embodiments, even if the second speed goes over the maximum threshold speed, the second number of tactile outputs no longer increases (e.g., but rather stays constant at the maximum number of tactile outputs (e.g., at space of 15 ms between tactile outputs).
In some embodiments, while detecting (1504) the rotational input (e.g., 1401, 1403, 1405, 1407, 1409), the electronic device (e.g., 600) generates (1540) (e.g., via the one or more tactile output generators and/or via one or more other output devices of the electronic device, such as one or more internal speakers and/or one or more external speakers (e.g., headphones, earphones) connected to the electronic device) a plurality of audio outputs associated with the plurality of tactile outputs. In some embodiments, in accordance with the determination that the speed of the rotational input is the first speed, the electronic device generates (1544) a first number of audio outputs for the respective amount of rotation of the rotatable input element. In some embodiments, in accordance with the determination that the speed of the rotation input is the second speed, the electronic device generates (1550) a second number of audio outputs for the respective amount of rotation of the rotatable input element. Generating associated audio outputs in addition to the tactile outputs provides another feedback method, thus enhancing the operability of the device by enhancing the versatility of the device.
In some embodiments, the audio outputs are generated via the one or more tactile output generators (e.g., integrated into the rotatable input element and/or a housing of the electronic device).
In some embodiments, while detecting (1504) the rotational input (e.g., 1401, 1403, 1405, 1407, 1409), the electronic device (e.g., 600) generates (1540) (e.g., via the one or more tactile output generators and/or via one or more other output devices of the electronic device, such as one or more internal speakers and/or one or more external speakers (e.g., headphones, earphones) connected to the electronic device) a plurality of audio outputs associated with the plurality of tactile outputs. In some embodiments, in accordance with the determination (1542) that the speed of the rotational input is the first speed, the electronic device generates (1546) the audio outputs at a first magnitude (e.g., a first volume) for the respective amount of rotation of the rotatable input element. In some embodiments, in accordance with the determination (1548) that the speed of the rotation input is the second speed, the electronic device generates (1552) the audio outputs at a second magnitude (e.g., a second volume) different from the first magnitude (e.g., greater/louder than the first magnitude or smaller/quieter than the first magnitude) for the respective amount of rotation of the rotatable input element.
In some embodiments, the second speed (e.g., 1420) is greater than the first speed (e.g., 1418) (e.g., the rotatable input element is rotated at a faster speed/rate for the second speed than for the first speed), and the second number of audio outputs is smaller than the first number of audio outputs for the respective amount of rotation of the rotatable input element. In some embodiments, if the second speed is slower than the first speed (e.g., the rotatable input element is rotated at a slower speed/rate for the second speed than for the first speed), the second number of audio outputs is greater than the first number of audio outputs for the respective amount of rotation of the rotatable input element.
In some embodiments, the difference in the number of outputs between the second number of audio outputs and the first number of audio outputs is different from the difference in the number of outputs between the second number of tactile outputs and the first number of tactile outputs. Thus, in some embodiments, when the speed of rotation of the rotatable input element changes (e.g., becomes faster or becomes slower), the change in the number of audio outputs generated by the electronic device for the respective amount of rotation of the rotatable input element changes at a different rate than the change in the number of tactile outputs generated by the electronic device for the respective amount of rotation of the rotatable input element.
In some embodiments, while detecting (1504) the rotational input (e.g., 1401, 1403, 1405, 1407, 1409), in accordance with a determination (1554) that the speed of the rotational input is of an initial speed (e.g., the initial speed of the rotational input the moment/right after the rotational input is detected), the electronic device (e.g., 600) generates (1556) an initial number of tactile outputs and an initial number of audio outputs for the respective amount of rotation of the rotatable input element (e.g., 604). In some embodiments, while detecting (1504) the rotational input, in accordance with a determination (1560) that the speed of the rotational input is of a threshold speed (e.g., the speed of the rotational input that first triggers a change in the number of tactile outputs that are generated), the electronic device generates (1562) a threshold number of tactile outputs and the initial number of audio outputs for the respective amount of rotation of the rotatable input element, the threshold number of tactile outputs different from (e.g., greater than) the initial number of tactile outputs. In some embodiments, in accordance with a determination (1560) that the speed of the rotational input is of the threshold speed, the electronic device generates the initial number of tactile outputs and a threshold number of audio outputs for the respective amount of rotation of the rotatable input element, the threshold number of audio outputs different from (e.g., greater than) the initial number of audio outputs. In some embodiments, the tactile outputs and the audio outputs are generated by the same tactile output generators of the one or more tactile output generators.
In some embodiments, while detecting (1504) the rotational input (e.g., 1401, 1403, 1405, 1407, 1409), in accordance with a determination (1554) that the speed of the rotational input is of an initial speed (e.g., the initial speed of the rotational input the moment/right after the rotational input is detected), the electronic device (e.g., 600) generates (1558) the plurality of tactile outputs having an initial amplitude and the plurality of audio outputs having an initial magnitude (e.g., an initial volume) for the respective amount of rotation of the rotatable input element. In some embodiments, while detecting (1504) the rotational input, in accordance with a determination (1560) that the speed of the rotational input is of a threshold speed (e.g., the speed of the rotational input that first triggers a change in the number of tactile outputs that are generated), the electronic device (e.g., 600) generates (1564) the plurality of tactile outputs having a threshold amplitude and the plurality of audio outputs having the initial magnitude (e.g., the initial volume) for the respective amount of rotation of the rotatable input element, the threshold amplitude different from (e.g., greater than) the initial amplitude. In some embodiments, in accordance with a determination that the speed of the rotational input is of the threshold speed, the electronic device generates the plurality of tactile outputs having the initial amplitude and the plurality of audio outputs having a threshold magnitude for the respective amount of rotation of the rotatable input element, the threshold magnitude different from (e.g., greater than) the initial magnitude. In some embodiments, the tactile outputs and the audio outputs are generated by the same tactile output generators of the one or more tactile output generators.
In some embodiments, in accordance with the modification of the user interface (e.g., 1402) corresponding to a navigation of the user interface in a first direction (e.g., an upwards scrolling direction, a forwards navigation direction), the generated plurality of tactile outputs (e.g., 620) and the generated plurality of audio outputs are of a first type (e.g., plurality of tactile outputs having a first number of tactile outputs in the sequence and/or a first amplitude, plurality of audio outputs having a first number of audio outputs in the sequence and/or a first magnitude). In some embodiments, in accordance with the modification of the user interface corresponding to a navigation of the user interface in a second direction (e.g., a downwards scrolling direction, a backwards navigation direction), the generated plurality of tactile outputs and the generated plurality of audio outputs are of a second type different from the first type (e.g., plurality of tactile outputs having a second number of tactile outputs in the sequence and/or a second amplitude, plurality of audio outputs having a second number of audio outputs in the sequence and/or a second magnitude).
In some embodiments, a particular type of tactile output corresponds to a particular tactile output pattern. For example, as described in greater detail above with reference to
Similarly, in some embodiments, a particular type of audio output corresponds to a particular type of audio output pattern. For example, an audio output pattern specifies characteristics of an audio output, such as the magnitude/amplitude/volume of the audio output, the shape of a sound waveform of the audio output, the frequency of the audio output, and/or the duration of the audio output. When audio outputs with different audio output patterns are generated by a device (e.g., via one or more tactile output generators that move a moveable mass to generate audio outputs, via one or more speakers), the audio outputs may invoke different audio-related sensations in a user holding or touching the device or proximate to the device.
Note that details of the processes described above with respect to method 1500 (e.g.,
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 techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.
As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve sensor feedback to users, and thus enhance user experience, convenience, and efficiency, as a user navigates through content of a user interface displayed on an electronic device. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records relating to a user's health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.
The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure.
The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.
Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.
Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user's privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.
Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data.
This applications claims priority to U.S. Provisional Patent Application Ser. No. 62/729,978, entitled “CONTENT-BASED TACTILE OUTPUTS,” filed Sep. 11, 2018, the contents of which are hereby incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4185283 | Clark | Jan 1980 | A |
| 4358837 | Yamazaki et al. | Nov 1982 | A |
| 4395134 | Luce | Jul 1983 | A |
| 4444515 | Clark | Apr 1984 | A |
| 4623261 | Muto | Nov 1986 | A |
| 5088070 | Shiff | Feb 1992 | A |
| 5204600 | Kahkoska | Apr 1993 | A |
| 5220260 | Schuler | Jun 1993 | A |
| 5313229 | Gilligan et al. | May 1994 | A |
| 5323363 | Hysek et al. | Jun 1994 | A |
| 5329501 | Meister et al. | Jul 1994 | A |
| 5477508 | Will | Dec 1995 | A |
| 5508978 | Kalbermatter et al. | Apr 1996 | A |
| 5519393 | Brandestini | May 1996 | A |
| 5528260 | Kent | Jun 1996 | A |
| 5563631 | Masunaga | Oct 1996 | A |
| 5689628 | Robertson | Nov 1997 | A |
| 5691747 | Amano | Nov 1997 | A |
| 5739775 | Brandestini | Apr 1998 | A |
| 5751260 | Nappi et al. | May 1998 | A |
| 5825353 | Will | Oct 1998 | A |
| 5852413 | Bacchi et al. | Dec 1998 | A |
| 5874961 | Bates et al. | Feb 1999 | A |
| 5903229 | Kishi | May 1999 | A |
| 5940521 | East et al. | Aug 1999 | A |
| 5960366 | Duwaer | Sep 1999 | A |
| 5982710 | Rawat et al. | Nov 1999 | A |
| 6005579 | Sugiyama et al. | Dec 1999 | A |
| 6081256 | Herget et al. | Jun 2000 | A |
| 6128006 | Rosenberg et al. | Oct 2000 | A |
| 6157381 | Bates et al. | Dec 2000 | A |
| 6161957 | Guanter | Dec 2000 | A |
| 6192258 | Kamada et al. | Feb 2001 | B1 |
| 6203190 | Stotz | Mar 2001 | B1 |
| 6249689 | Aizawa | Jun 2001 | B1 |
| 6266098 | Cove et al. | Jul 2001 | B1 |
| 6297795 | Kato et al. | Oct 2001 | B1 |
| 6300939 | Decker et al. | Oct 2001 | B1 |
| 6305234 | Thies et al. | Oct 2001 | B1 |
| 6310648 | Miller et al. | Oct 2001 | B1 |
| 6323846 | Westerman et al. | Nov 2001 | B1 |
| 6336126 | Bjorklund et al. | Jan 2002 | B1 |
| 6339438 | Bates et al. | Jan 2002 | B1 |
| 6351657 | Yamada | Feb 2002 | B2 |
| 6369794 | Sakurai et al. | Apr 2002 | B1 |
| 6396482 | Griffin et al. | May 2002 | B1 |
| 6477117 | Narayanaswami et al. | Nov 2002 | B1 |
| 6489950 | Griffin et al. | Dec 2002 | B1 |
| 6525997 | Narayanaswami et al. | Feb 2003 | B1 |
| 6535461 | Karhu | Mar 2003 | B1 |
| 6556222 | Narayanaswami | Apr 2003 | B1 |
| 6570557 | Westerman et al. | May 2003 | B1 |
| 6570583 | Kung et al. | May 2003 | B1 |
| 6597374 | Baker et al. | Jul 2003 | B1 |
| 6636197 | Goldenberg et al. | Oct 2003 | B1 |
| 6636246 | Gallo et al. | Oct 2003 | B1 |
| 6647338 | Hamberger et al. | Nov 2003 | B1 |
| 6661438 | Shiraishi et al. | Dec 2003 | B1 |
| 6677932 | Westerman | Jan 2004 | B1 |
| 6686904 | Sherman et al. | Feb 2004 | B1 |
| 6686911 | Levin et al. | Feb 2004 | B1 |
| 6700564 | McLoone et al. | Mar 2004 | B2 |
| 6720860 | Narayanaswami | Apr 2004 | B1 |
| 6763226 | Mczeal, Jr. | Jul 2004 | B1 |
| 6788220 | Netzer | Sep 2004 | B2 |
| 6809275 | Cheng et al. | Oct 2004 | B1 |
| 6809724 | Shiraishi et al. | Oct 2004 | B1 |
| 6842169 | Griffin et al. | Jan 2005 | B2 |
| 6937228 | Yu | Aug 2005 | B2 |
| 6967642 | SanGiovanni | Nov 2005 | B2 |
| 6967903 | Guanter | Nov 2005 | B2 |
| 6977868 | Brewer et al. | Dec 2005 | B2 |
| 7002558 | Keely et al. | Feb 2006 | B2 |
| 7046230 | Zadesky et al. | May 2006 | B2 |
| 7058904 | Khan et al. | Jun 2006 | B1 |
| 7075513 | Silfverberg et al. | Jul 2006 | B2 |
| 7081905 | Raghunath | Jul 2006 | B1 |
| 7091964 | Wong et al. | Aug 2006 | B2 |
| 7116317 | Gregorio et al. | Oct 2006 | B2 |
| 7130664 | Williams | Oct 2006 | B1 |
| 7143355 | Yamaguchi et al. | Nov 2006 | B2 |
| 7146005 | Anft et al. | Dec 2006 | B1 |
| 7168047 | Huppi | Jan 2007 | B1 |
| 7227963 | Yamada et al. | Jun 2007 | B1 |
| 7256770 | Hinckley et al. | Aug 2007 | B2 |
| 7272077 | Nobs | Sep 2007 | B2 |
| 7286063 | Gauthey et al. | Oct 2007 | B2 |
| 7286119 | Yamaguchi et al. | Oct 2007 | B2 |
| 7317449 | Robbins et al. | Jan 2008 | B2 |
| 7333084 | Griffin | Feb 2008 | B2 |
| 7463239 | Ledbetter et al. | Dec 2008 | B2 |
| 7469381 | Ording | Dec 2008 | B2 |
| 7469386 | Bear et al. | Dec 2008 | B2 |
| 7477890 | Narayanaswami | Jan 2009 | B1 |
| 7489303 | Pryor | Feb 2009 | B1 |
| 7499040 | Zadesky et al. | Mar 2009 | B2 |
| 7506269 | Lang | Mar 2009 | B2 |
| 7519468 | Orr et al. | Apr 2009 | B2 |
| 7596761 | Lemay et al. | Sep 2009 | B2 |
| 7600192 | Hashimoto et al. | Oct 2009 | B1 |
| 7614008 | Ording | Nov 2009 | B2 |
| 7633076 | Huppi et al. | Dec 2009 | B2 |
| 7653883 | Hotelling et al. | Jan 2010 | B2 |
| 7657849 | Chaudhri et al. | Feb 2010 | B2 |
| 7663607 | Hotelling et al. | Feb 2010 | B2 |
| 7710393 | Tsuk et al. | May 2010 | B2 |
| 7710409 | Robbin et al. | May 2010 | B2 |
| 7720552 | Lloyd | May 2010 | B1 |
| 7794138 | Hilfiker | Sep 2010 | B2 |
| 7844914 | Andre et al. | Nov 2010 | B2 |
| 7844915 | Platzer et al. | Nov 2010 | B2 |
| 7856255 | Tsuchiya et al. | Dec 2010 | B2 |
| 7916157 | Kelley et al. | Mar 2011 | B1 |
| 7956847 | Christie | Jun 2011 | B2 |
| 7957762 | Herz et al. | Jun 2011 | B2 |
| 7965276 | Martin et al. | Jun 2011 | B1 |
| 8001488 | Lam | Aug 2011 | B1 |
| 8006002 | Kalayjian et al. | Aug 2011 | B2 |
| 8009144 | Yajima | Aug 2011 | B2 |
| 8046705 | Hunleth et al. | Oct 2011 | B2 |
| 8130205 | Forstall et al. | Mar 2012 | B2 |
| 8140996 | Tomkins | Mar 2012 | B2 |
| 8191011 | Abanami et al. | May 2012 | B2 |
| 8194036 | Braun et al. | Jun 2012 | B1 |
| 8201102 | Lee et al. | Jun 2012 | B2 |
| 8239784 | Hotelling et al. | Aug 2012 | B2 |
| 8266550 | Cleron et al. | Sep 2012 | B1 |
| 8279180 | Hotelling et al. | Oct 2012 | B2 |
| 8307306 | Komatsu | Nov 2012 | B2 |
| 8311727 | Eckstein et al. | Nov 2012 | B2 |
| 8381135 | Hotelling et al. | Feb 2013 | B2 |
| 8427432 | Kim et al. | Apr 2013 | B2 |
| 8479122 | Hotelling et al. | Jul 2013 | B2 |
| 8487882 | Inaba et al. | Jul 2013 | B2 |
| 8533623 | St, Jacques | Sep 2013 | B2 |
| 8549429 | Tsuruta et al. | Oct 2013 | B2 |
| 8566722 | Gordon et al. | Oct 2013 | B2 |
| 8627236 | Jung et al. | Jan 2014 | B2 |
| 8665209 | Rimas-Ribikauskas et al. | Mar 2014 | B2 |
| 8669945 | Coddington | Mar 2014 | B2 |
| 8677283 | Fong | Mar 2014 | B2 |
| 8686944 | Charlton et al. | Apr 2014 | B1 |
| 8717302 | Qin et al. | May 2014 | B1 |
| 8799816 | Wells et al. | Aug 2014 | B2 |
| 8824245 | Lau et al. | Sep 2014 | B2 |
| 8860674 | Lee et al. | Oct 2014 | B2 |
| 8952886 | Tsuk et al. | Feb 2015 | B2 |
| 8954887 | Tseng et al. | Feb 2015 | B1 |
| 9001625 | Essery et al. | Apr 2015 | B2 |
| 9007057 | Villaret | Apr 2015 | B2 |
| 9007302 | Bandt-Horn | Apr 2015 | B1 |
| 9007323 | Araki | Apr 2015 | B2 |
| 9104705 | Fujinaga | Aug 2015 | B2 |
| 9176652 | Patel et al. | Nov 2015 | B1 |
| 9182876 | Kim et al. | Nov 2015 | B2 |
| 9189089 | Sutton et al. | Nov 2015 | B2 |
| 9195219 | Hong et al. | Nov 2015 | B2 |
| 9229624 | Wei et al. | Jan 2016 | B2 |
| 9268400 | Gomez Sainz-Garcia | Feb 2016 | B2 |
| 9395867 | Griffin et al. | Jul 2016 | B2 |
| 9395905 | Wherry | Jul 2016 | B2 |
| 9442649 | Davis et al. | Sep 2016 | B2 |
| 9448691 | Suda | Sep 2016 | B2 |
| 9454229 | Wellen | Sep 2016 | B1 |
| D778912 | Akana et al. | Feb 2017 | S |
| 9582187 | Gil et al. | Feb 2017 | B2 |
| 9620312 | Ely et al. | Apr 2017 | B2 |
| 9646471 | Agarwal | May 2017 | B2 |
| 9651922 | Hysek et al. | May 2017 | B2 |
| 9666178 | Loubiere et al. | May 2017 | B2 |
| 9678571 | Robert et al. | Jun 2017 | B1 |
| 9696809 | Temple | Jul 2017 | B2 |
| 9772769 | Shimazu | Sep 2017 | B2 |
| 9798443 | Gray | Oct 2017 | B1 |
| 9823828 | Zambetti et al. | Nov 2017 | B2 |
| D813239 | Akana et al. | Mar 2018 | S |
| 9921711 | Oh et al. | Mar 2018 | B2 |
| 9965144 | Nakamura et al. | May 2018 | B2 |
| 9984539 | Moussette et al. | May 2018 | B2 |
| 10019097 | Ely et al. | Jul 2018 | B2 |
| 10048802 | Shedletsky et al. | Aug 2018 | B2 |
| 10057470 | Kim et al. | Aug 2018 | B2 |
| 10097496 | Dye et al. | Oct 2018 | B2 |
| 10133439 | Brichter et al. | Nov 2018 | B1 |
| 10175652 | Ely et al. | Jan 2019 | B2 |
| 10216147 | Ely et al. | Feb 2019 | B2 |
| 10216352 | Liang et al. | Feb 2019 | B2 |
| 10222909 | Shedletsky et al. | Mar 2019 | B2 |
| 10275117 | Zambetti et al. | Apr 2019 | B2 |
| D849749 | Akana et al. | May 2019 | S |
| 10289218 | Young | May 2019 | B1 |
| 10296125 | Ely et al. | May 2019 | B2 |
| 10324620 | Balaram | Jun 2019 | B2 |
| 10331081 | Ely et al. | Jun 2019 | B2 |
| 10331082 | Ely et al. | Jun 2019 | B2 |
| 10339721 | Dascola et al. | Jul 2019 | B1 |
| 10642467 | Merminod et al. | May 2020 | B2 |
| 20010004337 | Paratte | Jun 2001 | A1 |
| 20010011991 | Wang et al. | Aug 2001 | A1 |
| 20010035884 | Kikinis et al. | Nov 2001 | A1 |
| 20010041596 | Forlenzo et al. | Nov 2001 | A1 |
| 20020015024 | Westerman et al. | Feb 2002 | A1 |
| 20020019296 | Freeman et al. | Feb 2002 | A1 |
| 20020027547 | Kamijo et al. | Mar 2002 | A1 |
| 20020030665 | Ano | Mar 2002 | A1 |
| 20020030668 | Hoshino et al. | Mar 2002 | A1 |
| 20020036623 | Kano | Mar 2002 | A1 |
| 20020047860 | Ceulaer et al. | Apr 2002 | A1 |
| 20020063684 | Tran | May 2002 | A1 |
| 20020101457 | Lang | Aug 2002 | A1 |
| 20020101458 | Sangiovanni | Aug 2002 | A1 |
| 20020118169 | Hinckley et al. | Aug 2002 | A1 |
| 20020126099 | Engholm | Sep 2002 | A1 |
| 20020154150 | Ogaki et al. | Oct 2002 | A1 |
| 20020154175 | Abello et al. | Oct 2002 | A1 |
| 20020171689 | Fox et al. | Nov 2002 | A1 |
| 20020186621 | Lai | Dec 2002 | A1 |
| 20030020671 | Santoro et al. | Jan 2003 | A1 |
| 20030025673 | Ledbetter et al. | Feb 2003 | A1 |
| 20030052901 | Fukuchi | Mar 2003 | A1 |
| 20030076301 | Tsuk et al. | Apr 2003 | A1 |
| 20030098891 | Molander | May 2003 | A1 |
| 20030103044 | Sunda et al. | Jun 2003 | A1 |
| 20030112279 | Irimajiri | Jun 2003 | A1 |
| 20030115384 | Sonehara et al. | Jun 2003 | A1 |
| 20030123329 | Guanter et al. | Jul 2003 | A1 |
| 20030137540 | Klevenz et al. | Jul 2003 | A1 |
| 20030142081 | Iizuka et al. | Jul 2003 | A1 |
| 20030142288 | Kinrot et al. | Jul 2003 | A1 |
| 20030189598 | Lipstein et al. | Oct 2003 | A1 |
| 20030210286 | Gerpheide et al. | Nov 2003 | A1 |
| 20040013042 | Farine | Jan 2004 | A1 |
| 20040027793 | Haraguchi et al. | Feb 2004 | A1 |
| 20040038667 | Vance | Feb 2004 | A1 |
| 20040047244 | Iino et al. | Mar 2004 | A1 |
| 20040073935 | Kang | Apr 2004 | A1 |
| 20040085328 | Maruyama et al. | May 2004 | A1 |
| 20040100479 | Nakano et al. | May 2004 | A1 |
| 20040113819 | Gauthey et al. | Jun 2004 | A1 |
| 20040130580 | Howard et al. | Jul 2004 | A1 |
| 20040130581 | Howard et al. | Jul 2004 | A1 |
| 20040145595 | Bennett | Jul 2004 | A1 |
| 20040150621 | Bohn | Aug 2004 | A1 |
| 20040155907 | Yamaguchi et al. | Aug 2004 | A1 |
| 20040170270 | Takashima et al. | Sep 2004 | A1 |
| 20040218472 | Narayanaswami et al. | Nov 2004 | A1 |
| 20040225613 | Narayanaswami et al. | Nov 2004 | A1 |
| 20040230599 | Moore et al. | Nov 2004 | A1 |
| 20040233162 | Kobayashi | Nov 2004 | A1 |
| 20040239649 | Ludtke | Dec 2004 | A1 |
| 20040239692 | Balle et al. | Dec 2004 | A1 |
| 20040252119 | Hunleth et al. | Dec 2004 | A1 |
| 20040264301 | Howard et al. | Dec 2004 | A1 |
| 20050007884 | Lorenzato | Jan 2005 | A1 |
| 20050012723 | Pallakoff | Jan 2005 | A1 |
| 20050081164 | Hama et al. | Apr 2005 | A1 |
| 20050097466 | Levi Montalcini | May 2005 | A1 |
| 20050116941 | Wallington | Jun 2005 | A1 |
| 20050136955 | Mumick et al. | Jun 2005 | A1 |
| 20050168566 | Tada et al. | Aug 2005 | A1 |
| 20050183012 | Petro et al. | Aug 2005 | A1 |
| 20050190059 | Wehrenberg | Sep 2005 | A1 |
| 20050191994 | May et al. | Sep 2005 | A1 |
| 20050195216 | Kramer et al. | Sep 2005 | A1 |
| 20050209051 | Santomassimo et al. | Sep 2005 | A1 |
| 20050215848 | Lorenzato | Sep 2005 | A1 |
| 20050259077 | Adams et al. | Nov 2005 | A1 |
| 20060007129 | Pletikosa | Jan 2006 | A1 |
| 20060017692 | Wehrenberg et al. | Jan 2006 | A1 |
| 20060020904 | Aaltonen et al. | Jan 2006 | A1 |
| 20060022956 | Lengeling et al. | Feb 2006 | A1 |
| 20060026521 | Hotelling et al. | Feb 2006 | A1 |
| 20060026535 | Hotelling et al. | Feb 2006 | A1 |
| 20060026536 | Hotelling et al. | Feb 2006 | A1 |
| 20060028444 | Hinckley et al. | Feb 2006 | A1 |
| 20060028446 | Liberty et al. | Feb 2006 | A1 |
| 20060033724 | Chaudhri et al. | Feb 2006 | A1 |
| 20060064716 | Sull et al. | Mar 2006 | A1 |
| 20060085751 | O'brien et al. | Apr 2006 | A1 |
| 20060090090 | Perng | Apr 2006 | A1 |
| 20060092177 | Blasko | May 2006 | A1 |
| 20060112350 | Kato | May 2006 | A1 |
| 20060143574 | Ito et al. | Jun 2006 | A1 |
| 20060152480 | Senn | Jul 2006 | A1 |
| 20060181506 | Fyke | Aug 2006 | A1 |
| 20060197753 | Hotelling | Sep 2006 | A1 |
| 20060212905 | Matsuda et al. | Sep 2006 | A1 |
| 20060224945 | Khan et al. | Oct 2006 | A1 |
| 20060255683 | Suzuki et al. | Nov 2006 | A1 |
| 20060268019 | Wang et al. | Nov 2006 | A1 |
| 20060268020 | Han | Nov 2006 | A1 |
| 20060290671 | Bohn et al. | Dec 2006 | A1 |
| 20070002019 | Lane et al. | Jan 2007 | A1 |
| 20070031119 | Iwanaga | Feb 2007 | A1 |
| 20070046635 | Nishiyama et al. | Mar 2007 | A1 |
| 20070063995 | Bailey et al. | Mar 2007 | A1 |
| 20070070090 | Debettencourt et al. | Mar 2007 | A1 |
| 20070073917 | Larson et al. | Mar 2007 | A1 |
| 20070085841 | Tsuk et al. | Apr 2007 | A1 |
| 20070097151 | Rosenberg | May 2007 | A1 |
| 20070106949 | Narita et al. | May 2007 | A1 |
| 20070120819 | Young et al. | May 2007 | A1 |
| 20070132733 | Ram | Jun 2007 | A1 |
| 20070168369 | Bruns | Jul 2007 | A1 |
| 20070176910 | Simek et al. | Aug 2007 | A1 |
| 20070180379 | Osato | Aug 2007 | A1 |
| 20070182595 | Ghasabian | Aug 2007 | A1 |
| 20070182999 | Anthony et al. | Aug 2007 | A1 |
| 20070209017 | Gupta et al. | Sep 2007 | A1 |
| 20070211042 | Kim | Sep 2007 | A1 |
| 20070226646 | Nagiyama et al. | Sep 2007 | A1 |
| 20070229458 | Moon | Oct 2007 | A1 |
| 20070236475 | Wherry | Oct 2007 | A1 |
| 20070236479 | Wang et al. | Oct 2007 | A1 |
| 20070237493 | Hall et al. | Oct 2007 | A1 |
| 20070239837 | Jablokov et al. | Oct 2007 | A1 |
| 20070242569 | Inoue et al. | Oct 2007 | A1 |
| 20070247435 | Benko et al. | Oct 2007 | A1 |
| 20070279401 | Ramstein et al. | Dec 2007 | A1 |
| 20070290045 | Cisar | Dec 2007 | A1 |
| 20070296711 | Yee et al. | Dec 2007 | A1 |
| 20080001915 | Pihlaja et al. | Jan 2008 | A1 |
| 20080004084 | Park | Jan 2008 | A1 |
| 20080020810 | Park | Jan 2008 | A1 |
| 20080040692 | Sunday et al. | Feb 2008 | A1 |
| 20080043028 | Tanaka | Feb 2008 | A1 |
| 20080052945 | Matas et al. | Mar 2008 | A1 |
| 20080062127 | Brodersen et al. | Mar 2008 | A1 |
| 20080062141 | Chandhri | Mar 2008 | A1 |
| 20080066135 | Brodersen et al. | Mar 2008 | A1 |
| 20080123473 | Ozawa et al. | May 2008 | A1 |
| 20080125196 | Ryu | May 2008 | A1 |
| 20080129520 | Lee | Jun 2008 | A1 |
| 20080130421 | Akaiwa et al. | Jun 2008 | A1 |
| 20080148177 | Lang et al. | Jun 2008 | A1 |
| 20080150901 | Lowles et al. | Jun 2008 | A1 |
| 20080155461 | Ozaki | Jun 2008 | A1 |
| 20080155475 | Duhig | Jun 2008 | A1 |
| 20080158149 | Levin | Jul 2008 | A1 |
| 20080163116 | Lee et al. | Jul 2008 | A1 |
| 20080163119 | Kim et al. | Jul 2008 | A1 |
| 20080165124 | Kim | Jul 2008 | A1 |
| 20080165140 | Christie et al. | Jul 2008 | A1 |
| 20080165153 | Platzer et al. | Jul 2008 | A1 |
| 20080168349 | Lamiraux et al. | Jul 2008 | A1 |
| 20080168382 | Louch et al. | Jul 2008 | A1 |
| 20080168384 | Platzer et al. | Jul 2008 | A1 |
| 20080168404 | Ording | Jul 2008 | A1 |
| 20080172634 | Choi et al. | Jul 2008 | A1 |
| 20080174570 | Jobs et al. | Jul 2008 | A1 |
| 20080186808 | Lee | Aug 2008 | A1 |
| 20080204478 | Hung | Aug 2008 | A1 |
| 20080207281 | Tsuchiya et al. | Aug 2008 | A1 |
| 20080216001 | Ording et al. | Sep 2008 | A1 |
| 20080224995 | Perkunder | Sep 2008 | A1 |
| 20080257701 | Wlotzka | Oct 2008 | A1 |
| 20080279475 | Lee et al. | Nov 2008 | A1 |
| 20080288880 | Reponen et al. | Nov 2008 | A1 |
| 20080318635 | Yoon et al. | Dec 2008 | A1 |
| 20080320391 | Lemay et al. | Dec 2008 | A1 |
| 20090007019 | Kobayashi et al. | Jan 2009 | A1 |
| 20090015550 | Koski | Jan 2009 | A1 |
| 20090030800 | Grois | Jan 2009 | A1 |
| 20090046110 | Sadler et al. | Feb 2009 | A1 |
| 20090050465 | Asada | Feb 2009 | A1 |
| 20090051649 | Rondel | Feb 2009 | A1 |
| 20090059730 | Lyons et al. | Mar 2009 | A1 |
| 20090064031 | Bull et al. | Mar 2009 | A1 |
| 20090070705 | Ording | Mar 2009 | A1 |
| 20090070711 | Kwak et al. | Mar 2009 | A1 |
| 20090079698 | Takashima et al. | Mar 2009 | A1 |
| 20090098912 | Kim et al. | Apr 2009 | A1 |
| 20090100373 | Pixley et al. | Apr 2009 | A1 |
| 20090109069 | Takasaki et al. | Apr 2009 | A1 |
| 20090119678 | Shih et al. | May 2009 | A1 |
| 20090125811 | Bethurum | May 2009 | A1 |
| 20090143117 | Shin et al. | Jun 2009 | A1 |
| 20090144642 | Crystal | Jun 2009 | A1 |
| 20090152452 | Lee et al. | Jun 2009 | A1 |
| 20090156255 | Shin et al. | Jun 2009 | A1 |
| 20090193359 | Anthony et al. | Jul 2009 | A1 |
| 20090196124 | Mooring | Aug 2009 | A1 |
| 20090199130 | Tsern et al. | Aug 2009 | A1 |
| 20090204920 | Beverley et al. | Aug 2009 | A1 |
| 20090204929 | Baurmann et al. | Aug 2009 | A1 |
| 20090231271 | Heubel et al. | Sep 2009 | A1 |
| 20090241150 | White et al. | Sep 2009 | A1 |
| 20090288039 | Mail et al. | Nov 2009 | A1 |
| 20090289905 | Ahn | Nov 2009 | A1 |
| 20090315867 | Sakamoto et al. | Dec 2009 | A1 |
| 20090325563 | Horodezky et al. | Dec 2009 | A1 |
| 20100001967 | Yoo | Jan 2010 | A1 |
| 20100029327 | Jee | Feb 2010 | A1 |
| 20100058223 | Price et al. | Mar 2010 | A1 |
| 20100058226 | Flake et al. | Mar 2010 | A1 |
| 20100058240 | Bull et al. | Mar 2010 | A1 |
| 20100070926 | Abanami et al. | Mar 2010 | A1 |
| 20100073692 | Waltman et al. | Mar 2010 | A1 |
| 20100079500 | O'sullivan et al. | Apr 2010 | A1 |
| 20100088634 | Tsuruta et al. | Apr 2010 | A1 |
| 20100093400 | Ju et al. | Apr 2010 | A1 |
| 20100110044 | Englund | May 2010 | A1 |
| 20100113101 | Tanada | May 2010 | A1 |
| 20100128570 | Smith et al. | May 2010 | A1 |
| 20100141609 | Frisbee | Jun 2010 | A1 |
| 20100146387 | Hoover | Jun 2010 | A1 |
| 20100148945 | Yun et al. | Jun 2010 | A1 |
| 20100164908 | Hill et al. | Jul 2010 | A1 |
| 20100169097 | Nachman et al. | Jul 2010 | A1 |
| 20100173678 | Kim et al. | Jul 2010 | A1 |
| 20100187074 | Manni | Jul 2010 | A1 |
| 20100188268 | Grignani et al. | Jul 2010 | A1 |
| 20100199232 | Mistry et al. | Aug 2010 | A1 |
| 20100211498 | Aabye et al. | Aug 2010 | A1 |
| 20100211919 | Brown et al. | Aug 2010 | A1 |
| 20100214243 | Birnbaum et al. | Aug 2010 | A1 |
| 20100220562 | Hozumi et al. | Sep 2010 | A1 |
| 20100223055 | Mclean | Sep 2010 | A1 |
| 20100235742 | Hsu et al. | Sep 2010 | A1 |
| 20100248778 | Biswas | Sep 2010 | A1 |
| 20100259481 | Oh | Oct 2010 | A1 |
| 20100267424 | Kim et al. | Oct 2010 | A1 |
| 20100269038 | Tsuda | Oct 2010 | A1 |
| 20100271340 | Nagashima et al. | Oct 2010 | A1 |
| 20100271342 | Nagashima et al. | Oct 2010 | A1 |
| 20100271343 | Nagashima et al. | Oct 2010 | A1 |
| 20100277126 | Naeimi et al. | Nov 2010 | A1 |
| 20100283743 | Coddington | Nov 2010 | A1 |
| 20100315417 | Cho et al. | Dec 2010 | A1 |
| 20100325575 | Platzer et al. | Dec 2010 | A1 |
| 20100331145 | Lakovic et al. | Dec 2010 | A1 |
| 20110006980 | Taniguchi et al. | Jan 2011 | A1 |
| 20110014956 | Lee et al. | Jan 2011 | A1 |
| 20110022472 | Zon | Jan 2011 | A1 |
| 20110025311 | Chauvin et al. | Feb 2011 | A1 |
| 20110025624 | Goto | Feb 2011 | A1 |
| 20110055752 | Rubinstein et al. | Mar 2011 | A1 |
| 20110057877 | Nagashima et al. | Mar 2011 | A1 |
| 20110057886 | Ng et al. | Mar 2011 | A1 |
| 20110072345 | Lim | Mar 2011 | A1 |
| 20110074719 | Yeh et al. | Mar 2011 | A1 |
| 20110074828 | Capela et al. | Mar 2011 | A1 |
| 20110081889 | Gao et al. | Apr 2011 | A1 |
| 20110086613 | Doudkine et al. | Apr 2011 | A1 |
| 20110090255 | Wilson et al. | Apr 2011 | A1 |
| 20110099509 | Horagai | Apr 2011 | A1 |
| 20110102455 | Temple | May 2011 | A1 |
| 20110126155 | Krishnaraj et al. | May 2011 | A1 |
| 20110128226 | Jensen | Jun 2011 | A1 |
| 20110131494 | Ono et al. | Jun 2011 | A1 |
| 20110131531 | Russell et al. | Jun 2011 | A1 |
| 20110157046 | Lee et al. | Jun 2011 | A1 |
| 20110164042 | Chaudhri | Jul 2011 | A1 |
| 20110167262 | Ross et al. | Jul 2011 | A1 |
| 20110187355 | Dixon et al. | Aug 2011 | A1 |
| 20110199342 | Vartanian et al. | Aug 2011 | A1 |
| 20110202834 | Mandryk et al. | Aug 2011 | A1 |
| 20110202859 | Fong | Aug 2011 | A1 |
| 20110202866 | Huang et al. | Aug 2011 | A1 |
| 20110210834 | Pasquero et al. | Sep 2011 | A1 |
| 20110210926 | Pasquero et al. | Sep 2011 | A1 |
| 20110224967 | Van Schaik | Sep 2011 | A1 |
| 20110248948 | Griffin et al. | Oct 2011 | A1 |
| 20110252357 | Chaudhri | Oct 2011 | A1 |
| 20110252362 | Cho et al. | Oct 2011 | A1 |
| 20110252369 | Chaudhri | Oct 2011 | A1 |
| 20110271183 | Bose et al. | Nov 2011 | A1 |
| 20110271233 | Radakovitz et al. | Nov 2011 | A1 |
| 20110279384 | Miller et al. | Nov 2011 | A1 |
| 20110296312 | Boyer et al. | Dec 2011 | A1 |
| 20110298830 | Lam | Dec 2011 | A1 |
| 20110300915 | Stoustrup et al. | Dec 2011 | A1 |
| 20110302493 | Runstedler et al. | Dec 2011 | A1 |
| 20110307842 | Chiang et al. | Dec 2011 | A1 |
| 20110316888 | Sachs et al. | Dec 2011 | A1 |
| 20120011437 | James et al. | Jan 2012 | A1 |
| 20120026198 | Maesaka | Feb 2012 | A1 |
| 20120030627 | Nurmi et al. | Feb 2012 | A1 |
| 20120032988 | Katayama | Feb 2012 | A1 |
| 20120038582 | Grant | Feb 2012 | A1 |
| 20120044267 | Fino | Feb 2012 | A1 |
| 20120050185 | Davydov et al. | Mar 2012 | A1 |
| 20120054670 | Rainisto | Mar 2012 | A1 |
| 20120056848 | Yamano et al. | Mar 2012 | A1 |
| 20120062398 | Durand | Mar 2012 | A1 |
| 20120066638 | Ohri | Mar 2012 | A1 |
| 20120068925 | Wong et al. | Mar 2012 | A1 |
| 20120083260 | Arriola et al. | Apr 2012 | A1 |
| 20120089951 | Cassidy | Apr 2012 | A1 |
| 20120092383 | Hysek et al. | Apr 2012 | A1 |
| 20120099406 | Lau et al. | Apr 2012 | A1 |
| 20120105484 | Cui | May 2012 | A1 |
| 20120127071 | Jitkoff et al. | May 2012 | A1 |
| 20120131504 | Fadell et al. | May 2012 | A1 |
| 20120155223 | Hoover | Jun 2012 | A1 |
| 20120159380 | Kocienda et al. | Jun 2012 | A1 |
| 20120162261 | Kim et al. | Jun 2012 | A1 |
| 20120169776 | Rissa et al. | Jul 2012 | A1 |
| 20120174005 | Deutsch et al. | Jul 2012 | A1 |
| 20120179998 | Nesladek et al. | Jul 2012 | A1 |
| 20120186951 | Wu et al. | Jul 2012 | A1 |
| 20120192110 | Wu | Jul 2012 | A1 |
| 20120197743 | Grigg et al. | Aug 2012 | A1 |
| 20120218205 | Park | Aug 2012 | A1 |
| 20120226977 | Lengeling et al. | Sep 2012 | A1 |
| 20120236037 | Lessing et al. | Sep 2012 | A1 |
| 20120242584 | Tuli | Sep 2012 | A1 |
| 20120256863 | Zhang et al. | Oct 2012 | A1 |
| 20120272145 | Ryan et al. | Oct 2012 | A1 |
| 20120272181 | Rogers et al. | Oct 2012 | A1 |
| 20120278725 | Gordon et al. | Nov 2012 | A1 |
| 20120286944 | Forutanpour et al. | Nov 2012 | A1 |
| 20120289290 | Chae et al. | Nov 2012 | A1 |
| 20120290472 | Mullen et al. | Nov 2012 | A1 |
| 20120304113 | Patten et al. | Nov 2012 | A1 |
| 20120306765 | Moore | Dec 2012 | A1 |
| 20120307603 | Bongio et al. | Dec 2012 | A1 |
| 20120324390 | Tao | Dec 2012 | A1 |
| 20120327006 | Israr et al. | Dec 2012 | A1 |
| 20130019182 | Gil et al. | Jan 2013 | A1 |
| 20130024780 | Sutedja et al. | Jan 2013 | A1 |
| 20130024811 | Gleadall et al. | Jan 2013 | A1 |
| 20130027412 | Roddy | Jan 2013 | A1 |
| 20130038636 | Fujiwaka | Feb 2013 | A1 |
| 20130055160 | Yamada et al. | Feb 2013 | A1 |
| 20130067390 | Kwiatkowski et al. | Mar 2013 | A1 |
| 20130073932 | Migos et al. | Mar 2013 | A1 |
| 20130097566 | Berglund | Apr 2013 | A1 |
| 20130111342 | Alameh et al. | May 2013 | A1 |
| 20130111384 | Kim et al. | May 2013 | A1 |
| 20130111407 | Mullen | May 2013 | A1 |
| 20130117689 | Lessing et al. | May 2013 | A1 |
| 20130117698 | Park et al. | May 2013 | A1 |
| 20130135228 | Won et al. | May 2013 | A1 |
| 20130135234 | Hisano et al. | May 2013 | A1 |
| 20130135236 | Yano | May 2013 | A1 |
| 20130139102 | Miura et al. | May 2013 | A1 |
| 20130141342 | Bokma et al. | Jun 2013 | A1 |
| 20130142016 | Pozzo di borgo et al. | Jun 2013 | A1 |
| 20130145292 | Cohen et al. | Jun 2013 | A1 |
| 20130147747 | Takagi | Jun 2013 | A1 |
| 20130149674 | Anderson et al. | Jun 2013 | A1 |
| 20130154933 | Sheik-nainar | Jun 2013 | A1 |
| 20130169579 | Havnor | Jul 2013 | A1 |
| 20130176020 | Chauvin et al. | Jul 2013 | A1 |
| 20130205939 | Meerovitsch | Aug 2013 | A1 |
| 20130208013 | Yuu et al. | Aug 2013 | A1 |
| 20130218517 | Ausserlechner | Aug 2013 | A1 |
| 20130222301 | Lee et al. | Aug 2013 | A1 |
| 20130226444 | Johansson et al. | Aug 2013 | A1 |
| 20130258819 | Hoover | Oct 2013 | A1 |
| 20130262564 | Wall et al. | Oct 2013 | A1 |
| 20130282360 | Shimota et al. | Oct 2013 | A1 |
| 20130282459 | Smets et al. | Oct 2013 | A1 |
| 20130290116 | Hepworth et al. | Oct 2013 | A1 |
| 20130303087 | Hauser et al. | Nov 2013 | A1 |
| 20130305187 | Phillips et al. | Nov 2013 | A1 |
| 20130307603 | Koester | Nov 2013 | A1 |
| 20130339343 | Hierons et al. | Dec 2013 | A1 |
| 20130339345 | Soto Matamala et al. | Dec 2013 | A1 |
| 20130342457 | Cox et al. | Dec 2013 | A1 |
| 20140028554 | De los reyes et al. | Jan 2014 | A1 |
| 20140028688 | Houjou et al. | Jan 2014 | A1 |
| 20140028735 | Williams et al. | Jan 2014 | A1 |
| 20140040742 | Park et al. | Feb 2014 | A1 |
| 20140075368 | Kim et al. | Mar 2014 | A1 |
| 20140092037 | Kim | Apr 2014 | A1 |
| 20140105278 | Bivolarsky | Apr 2014 | A1 |
| 20140106734 | Lee | Apr 2014 | A1 |
| 20140132640 | Sharma et al. | May 2014 | A1 |
| 20140136443 | Kinsey et al. | May 2014 | A1 |
| 20140136981 | Xiang et al. | May 2014 | A1 |
| 20140137020 | Sharma et al. | May 2014 | A1 |
| 20140139422 | Mistry | May 2014 | A1 |
| 20140139637 | Mistry et al. | May 2014 | A1 |
| 20140143678 | Mistry et al. | May 2014 | A1 |
| 20140143737 | Mistry et al. | May 2014 | A1 |
| 20140157160 | Cudak et al. | Jun 2014 | A1 |
| 20140160078 | Seo et al. | Jun 2014 | A1 |
| 20140192626 | Wolff et al. | Jul 2014 | A1 |
| 20140204229 | Leung et al. | Jul 2014 | A1 |
| 20140215340 | Shetty et al. | Jul 2014 | A1 |
| 20140222916 | Foley et al. | Aug 2014 | A1 |
| 20140237382 | Grandhi | Aug 2014 | A1 |
| 20140253487 | Bezinge et al. | Sep 2014 | A1 |
| 20140258935 | Nishida et al. | Sep 2014 | A1 |
| 20140260776 | Burleson | Sep 2014 | A1 |
| 20140282142 | Lin | Sep 2014 | A1 |
| 20140282214 | Shirzadi et al. | Sep 2014 | A1 |
| 20140292668 | Fricklas et al. | Oct 2014 | A1 |
| 20140298233 | Pettey et al. | Oct 2014 | A1 |
| 20140306989 | Doubleday et al. | Oct 2014 | A1 |
| 20140328147 | Yang et al. | Nov 2014 | A1 |
| 20140330435 | Stoner et al. | Nov 2014 | A1 |
| 20140333670 | Agnetta et al. | Nov 2014 | A1 |
| 20140347289 | Suh et al. | Nov 2014 | A1 |
| 20140362024 | Hicks | Dec 2014 | A1 |
| 20140372115 | Lebeau et al. | Dec 2014 | A1 |
| 20150011204 | Seo et al. | Jan 2015 | A1 |
| 20150036555 | Shin et al. | Feb 2015 | A1 |
| 20150041289 | Ely | Feb 2015 | A1 |
| 20150046871 | Lewis | Feb 2015 | A1 |
| 20150058744 | Dhingra et al. | Feb 2015 | A1 |
| 20150067497 | Cieplinski et al. | Mar 2015 | A1 |
| 20150074615 | Han et al. | Mar 2015 | A1 |
| 20150077398 | Yairi et al. | Mar 2015 | A1 |
| 20150085621 | Hong et al. | Mar 2015 | A1 |
| 20150121224 | Krasnahill, Jr. | Apr 2015 | A1 |
| 20150149899 | Bernstein et al. | May 2015 | A1 |
| 20150178041 | Uskoreit | Jun 2015 | A1 |
| 20150199012 | Palmer | Jul 2015 | A1 |
| 20150199110 | Nakazato | Jul 2015 | A1 |
| 20150234518 | Teller et al. | Aug 2015 | A1 |
| 20150234562 | Ording | Aug 2015 | A1 |
| 20150261310 | Walmsley et al. | Sep 2015 | A1 |
| 20150269944 | Wang | Sep 2015 | A1 |
| 20150277559 | Vescovi et al. | Oct 2015 | A1 |
| 20150293592 | Cheong et al. | Oct 2015 | A1 |
| 20150302301 | Petersen | Oct 2015 | A1 |
| 20150339018 | Moon et al. | Nov 2015 | A1 |
| 20150370425 | Chen | Dec 2015 | A1 |
| 20150370529 | Zambetti et al. | Dec 2015 | A1 |
| 20150378447 | Nagano et al. | Dec 2015 | A1 |
| 20150378555 | Ramanathan et al. | Dec 2015 | A1 |
| 20160011758 | Dornbush et al. | Jan 2016 | A1 |
| 20160034133 | Wilson et al. | Feb 2016 | A1 |
| 20160034148 | Wilson et al. | Feb 2016 | A1 |
| 20160034152 | Wilson et al. | Feb 2016 | A1 |
| 20160034153 | Lejeune et al. | Feb 2016 | A1 |
| 20160034166 | Wilson et al. | Feb 2016 | A1 |
| 20160034167 | Wilson et al. | Feb 2016 | A1 |
| 20160054710 | Jo et al. | Feb 2016 | A1 |
| 20160062466 | Moussette et al. | Mar 2016 | A1 |
| 20160062487 | Foss et al. | Mar 2016 | A1 |
| 20160062567 | Yang et al. | Mar 2016 | A1 |
| 20160062571 | Dascola et al. | Mar 2016 | A1 |
| 20160062573 | Dascola et al. | Mar 2016 | A1 |
| 20160062608 | Foss et al. | Mar 2016 | A1 |
| 20160063828 | Moussette et al. | Mar 2016 | A1 |
| 20160063850 | Yang et al. | Mar 2016 | A1 |
| 20160065509 | Yang et al. | Mar 2016 | A1 |
| 20160065525 | Dye et al. | Mar 2016 | A1 |
| 20160071241 | Anzures et al. | Mar 2016 | A1 |
| 20160098016 | Ely et al. | Apr 2016 | A1 |
| 20160162164 | Phillips et al. | Jun 2016 | A1 |
| 20160170436 | Farrar et al. | Jun 2016 | A1 |
| 20160170598 | Zambetti et al. | Jun 2016 | A1 |
| 20160170608 | Zambetti et al. | Jun 2016 | A1 |
| 20160170624 | Zambetti et al. | Jun 2016 | A1 |
| 20160170625 | Zambetti | Jun 2016 | A1 |
| 20160180820 | Pascucci et al. | Jun 2016 | A1 |
| 20160202866 | Zambetti et al. | Jul 2016 | A1 |
| 20160209939 | Zambetti et al. | Jul 2016 | A1 |
| 20160231883 | Zambetti et al. | Aug 2016 | A1 |
| 20160259499 | Kocienda et al. | Sep 2016 | A1 |
| 20160259530 | Everitt et al. | Sep 2016 | A1 |
| 20160259535 | Fleizach et al. | Sep 2016 | A1 |
| 20160269540 | Butcher et al. | Sep 2016 | A1 |
| 20160327911 | Eim et al. | Nov 2016 | A1 |
| 20170010678 | Tuli | Jan 2017 | A1 |
| 20170010751 | Shedletsky et al. | Jan 2017 | A1 |
| 20170045958 | Battlogg | Feb 2017 | A1 |
| 20170053542 | Wilson et al. | Feb 2017 | A1 |
| 20170089735 | Ruh | Mar 2017 | A1 |
| 20170104902 | Kim et al. | Apr 2017 | A1 |
| 20170208466 | Seo et al. | Jul 2017 | A1 |
| 20170269692 | Eck et al. | Sep 2017 | A1 |
| 20170315716 | Zambetti et al. | Nov 2017 | A1 |
| 20170357321 | Fleizach et al. | Dec 2017 | A1 |
| 20170357427 | Wilson et al. | Dec 2017 | A1 |
| 20170358181 | Moussette et al. | Dec 2017 | A1 |
| 20180024683 | Ely et al. | Jan 2018 | A1 |
| 20180067557 | Robert et al. | Mar 2018 | A1 |
| 20180074690 | Zambetti et al. | Mar 2018 | A1 |
| 20180081453 | Ely | Mar 2018 | A1 |
| 20180088532 | Ely et al. | Mar 2018 | A1 |
| 20180088797 | Mcatee et al. | Mar 2018 | A1 |
| 20180210516 | Zambetti et al. | Jul 2018 | A1 |
| 20180307363 | Ely et al. | Oct 2018 | A1 |
| 20180329587 | Ko et al. | Nov 2018 | A1 |
| 20180335891 | Shedletsky et al. | Nov 2018 | A1 |
| 20180335901 | Manzari et al. | Nov 2018 | A1 |
| 20180336866 | Triverio et al. | Nov 2018 | A1 |
| 20180341344 | Foss et al. | Nov 2018 | A1 |
| 20180367489 | Dye et al. | Dec 2018 | A1 |
| 20190033862 | Groden et al. | Jan 2019 | A1 |
| 20190050055 | Chaudhri et al. | Feb 2019 | A1 |
| 20190056700 | Matsuno et al. | Feb 2019 | A1 |
| 20190072912 | Pandya et al. | Mar 2019 | A1 |
| 20190080066 | Van Os et al. | Mar 2019 | A1 |
| 20190080072 | Van Os et al. | Mar 2019 | A1 |
| 20190101870 | Pandya et al. | Apr 2019 | A1 |
| 20190163324 | Shedletsky et al. | May 2019 | A1 |
| 20190163329 | Yang et al. | May 2019 | A1 |
| 20190212885 | Zambetti et al. | Jul 2019 | A1 |
| 20190243471 | Foss et al. | Aug 2019 | A1 |
| 20190272036 | Grant et al. | Sep 2019 | A1 |
| 20190274565 | Soli et al. | Sep 2019 | A1 |
| 20190279520 | Wilson et al. | Sep 2019 | A1 |
| 20190354268 | Everitt et al. | Nov 2019 | A1 |
| 20200081538 | Moussette et al. | Mar 2020 | A1 |
| 20200110522 | Zambetti et al. | Apr 2020 | A1 |
| 20200145361 | Dye et al. | May 2020 | A1 |
| 20200167047 | Dascola et al. | May 2020 | A1 |
| 20200272287 | Yang et al. | Aug 2020 | A1 |
| 20200272293 | Zambetti et al. | Aug 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 2012200689 | Mar 2012 | AU |
| 2014100584 | Jul 2014 | AU |
| 2016231505 | Oct 2016 | AU |
| 2018100429 | May 2018 | AU |
| 2018100429 | Aug 2018 | AU |
| 1330310 | Jan 2002 | CN |
| 1398366 | Feb 2003 | CN |
| 1549998 | Nov 2004 | CN |
| 1757011 | Apr 2006 | CN |
| 1797295 | Jul 2006 | CN |
| 1811899 | Aug 2006 | CN |
| 101101595 | Jan 2008 | CN |
| 101192047 | Jun 2008 | CN |
| 101431545 | May 2009 | CN |
| 101446802 | Jun 2009 | CN |
| 101625620 | Jan 2010 | CN |
| 101876877 | Nov 2010 | CN |
| 101893992 | Nov 2010 | CN |
| 101976171 | Feb 2011 | CN |
| 101241407 | Jul 2011 | CN |
| 102402328 | Apr 2012 | CN |
| 102508707 | Jun 2012 | CN |
| 102591579 | Jul 2012 | CN |
| 102750066 | Oct 2012 | CN |
| 102859482 | Jan 2013 | CN |
| 102902453 | Jan 2013 | CN |
| 102902454 | Jan 2013 | CN |
| 102905181 | Jan 2013 | CN |
| 101034328 | Feb 2013 | CN |
| 102981770 | Mar 2013 | CN |
| 103069378 | Apr 2013 | CN |
| 103154878 | Jun 2013 | CN |
| 103270486 | Aug 2013 | CN |
| 103460164 | Dec 2013 | CN |
| 103703437 | Apr 2014 | CN |
| 103782252 | May 2014 | CN |
| 103793138 | May 2014 | CN |
| 103858088 | Jun 2014 | CN |
| 103870255 | Jun 2014 | CN |
| 103914261 | Jul 2014 | CN |
| 103970413 | Aug 2014 | CN |
| 104166458 | Nov 2014 | CN |
| 105955591 | Sep 2016 | CN |
| 107710135 | Feb 2018 | CN |
| 107797657 | Mar 2018 | CN |
| 108139863 | Jun 2018 | CN |
| 108304106 | Jul 2018 | CN |
| 108334190 | Jul 2018 | CN |
| 108369455 | Aug 2018 | CN |
| 1052566 | Nov 2000 | EP |
| 1168149 | Jan 2002 | EP |
| 1406158 | Apr 2004 | EP |
| 1486860 | Dec 2004 | EP |
| 1505484 | Feb 2005 | EP |
| 1850213 | Oct 2007 | EP |
| 1942401 | Jul 2008 | EP |
| 1944677 | Jul 2008 | EP |
| 1956433 | Aug 2008 | EP |
| 1956446 | Aug 2008 | EP |
| 2124131 | Nov 2009 | EP |
| 2207084 | Jul 2010 | EP |
| 2224317 | Sep 2010 | EP |
| 2237140 | Oct 2010 | EP |
| 2302492 | Mar 2011 | EP |
| 2385451 | Nov 2011 | EP |
| 2551784 | Jan 2013 | EP |
| 2610738 | Jul 2013 | EP |
| 2733579 | May 2014 | EP |
| 2733598 | May 2014 | EP |
| 2741176 | Jun 2014 | EP |
| 3401770 | Nov 2018 | EP |
| 2392773 | Mar 2004 | GB |
| 2489580 | Oct 2012 | GB |
| 55-80084 | Jun 1980 | JP |
| 5-88812 | Apr 1993 | JP |
| 6-348408 | Dec 1994 | JP |
| 7-152478 | Jun 1995 | JP |
| 11-110106 | Apr 1999 | JP |
| 2000-503153 | Mar 2000 | JP |
| 2000-305760 | Nov 2000 | JP |
| 2001-100905 | Apr 2001 | JP |
| 2001-202178 | Jul 2001 | JP |
| 2001-202181 | Jul 2001 | JP |
| 2002-288690 | Oct 2002 | JP |
| 2003-248544 | Sep 2003 | JP |
| 2003-330586 | Nov 2003 | JP |
| 2003-330856 | Nov 2003 | JP |
| 2004-21522 | Jan 2004 | JP |
| 2004-184396 | Jul 2004 | JP |
| 2004-259063 | Sep 2004 | JP |
| 2005-4891 | Jan 2005 | JP |
| 2005-196077 | Jul 2005 | JP |
| 2006-11690 | Jan 2006 | JP |
| 2006-140990 | Jun 2006 | JP |
| 2006-185273 | Jul 2006 | JP |
| 2007-170995 | Jul 2007 | JP |
| 2007-179544 | Jul 2007 | JP |
| 2008-97057 | Apr 2008 | JP |
| 2008-518539 | May 2008 | JP |
| 2008-139163 | Jun 2008 | JP |
| 2008-157974 | Jul 2008 | JP |
| 2008-539513 | Nov 2008 | JP |
| 2009-59382 | Mar 2009 | JP |
| 2009-510404 | Mar 2009 | JP |
| 2009-128296 | Jun 2009 | JP |
| 2009-246553 | Oct 2009 | JP |
| 2009-294526 | Dec 2009 | JP |
| 2010-257051 | Nov 2010 | JP |
| 2011-8540 | Jan 2011 | JP |
| 2011-90640 | May 2011 | JP |
| 2011-96043 | May 2011 | JP |
| 2011-530738 | Dec 2011 | JP |
| 2012-58979 | Mar 2012 | JP |
| 2012-155698 | Aug 2012 | JP |
| 2013-114844 | Jun 2013 | JP |
| 2013-122738 | Jun 2013 | JP |
| 2013-137750 | Jul 2013 | JP |
| 2014-42164 | Mar 2014 | JP |
| 2016-538653 | Dec 2016 | JP |
| 10-2004-0107472 | Dec 2004 | KR |
| 10-0630154 | Sep 2006 | KR |
| 10-2010-0003589 | Jan 2010 | KR |
| 10-2010-0109277 | Oct 2010 | KR |
| 10-2011-0093090 | Aug 2011 | KR |
| 10-2011-0114294 | Oct 2011 | KR |
| 10-2012-0071468 | Jul 2012 | KR |
| 10-2012-0079707 | Jul 2012 | KR |
| 10-2013-0027017 | Mar 2013 | KR |
| I269202 | Dec 2006 | TW |
| D122820 | May 2008 | TW |
| 200843452 | Nov 2008 | TW |
| 201119339 | Jun 2011 | TW |
| I349212 | Sep 2011 | TW |
| I381305 | Jan 2013 | TW |
| I384394 | Feb 2013 | TW |
| I394410 | Apr 2013 | TW |
| I395498 | May 2013 | TW |
| I405106 | Aug 2013 | TW |
| 201403363 | Jan 2014 | TW |
| I426416 | Feb 2014 | TW |
| 201421340 | Jun 2014 | TW |
| I443547 | Jul 2014 | TW |
| 199308517 | Apr 1993 | WO |
| 199619872 | Jun 1996 | WO |
| 200169369 | Sep 2001 | WO |
| 2003021568 | Mar 2003 | WO |
| 2006037545 | Apr 2006 | WO |
| 2006042309 | Apr 2006 | WO |
| 2008033853 | Mar 2008 | WO |
| 2008085742 | Jul 2008 | WO |
| 2008086218 | Jul 2008 | WO |
| 2008106777 | Sep 2008 | WO |
| 2009026508 | Feb 2009 | WO |
| 2009085378 | Jul 2009 | WO |
| 2009097592 | Aug 2009 | WO |
| 2010024969 | Mar 2010 | WO |
| 2010150768 | Dec 2010 | WO |
| 2011126502 | Oct 2011 | WO |
| 2012006494 | Jan 2012 | WO |
| 2012080020 | Jun 2012 | WO |
| 2013105664 | Jul 2013 | WO |
| 2013114844 | Aug 2013 | WO |
| 2013133901 | Sep 2013 | WO |
| 2013169842 | Nov 2013 | WO |
| 2013169846 | Nov 2013 | WO |
| 2013169849 | Nov 2013 | WO |
| 2013169875 | Nov 2013 | WO |
| 2014105276 | Jul 2014 | WO |
| 2015034969 | Mar 2015 | WO |
| 2016144696 | Sep 2016 | WO |
| 2016144385 | Sep 2016 | WO |
| 2016144563 | Sep 2016 | WO |
| 2017027625 | Feb 2017 | WO |
| 2018048518 | Mar 2018 | WO |
| 2018048632 | Mar 2018 | WO |
| Entry |
|---|
| Notice of Allowance received for U.S. Appl. No. 14/913,350, dated Dec. 19, 2018, 27 pages. |
| Office Action received for Australian Patent Application No. 2017276285, dated Nov. 26, 2018, 2 pages. |
| Office Action received for Australian Patent Application No. 2018200289, dated Dec. 4, 2018, 4 pages. |
| Search Report and opinion received for Danish Patent Application No. PA201870631, dated Dec. 6, 2018, 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870632, dated Dec. 3, 2018, 8 pages. |
| Advisory Action received for U.S. Appl. No. 15/049,052, dated Sep. 11, 2017, 2 pages. |
| Advisory Action received for U.S. Appl. No. 15/049,064, dated May 10, 2017, 3 Pages. |
| Advisory Action received for U.S. Appl. No. 15/049,058, dated Oct. 18, 2017, 3 pages. |
| Agarwal, Deepesh, “DexClock—Live Clock and Date Blended Into Beautiful Artwork as Your Desktop Wallpaper”, available at: https://www.megaleecher.net/DexCiock_Wallpaper_Designs, Jul. 6, 2013, 4 pages. |
| Apple, “iPhone User's Guide”, Available at: http://mesnotices.20minutes.fr/manuel-notice-mode-emploi/APPLE/IPHONE%2D%5FE#, Jun. 2007, 137 pages. |
| Brinkmann, Martin, “How to Zoom in Firefox”, Ghacks, Available at: https://web.archive.org/web/20130804034728/https://www.ghacks.net/2009/02/23/how-to-zoom-in-firefox/>, Feb. 23, 2009, 11 pages. |
| Colt, Sam, “Here's One Way Apple's Smartwatch Could Be Better Than Anything Else”, Business Insider, Aug. 21, 2014, pp. 1-4. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/641,252, dated Aug. 28, 2018, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/641,252, dated Jul. 9, 2018, 25 Pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/641,252, dated May 10, 2018, 10 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/829,573, dated Aug. 9, 2018, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/829,573, dated Sep. 11, 2018, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/841,656, dated Apr. 11, 2018, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/841,656, dated May 7, 2018, 14 pages. |
| Decision to Grant received for Danish Patent Application No. PA201570781, dated Jul. 17, 2017, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201670117, dated Nov. 20, 2017, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201770181, dated Mar. 7, 2018, 2 pages. |
| Final Office Action received for U.S. Appl. No. 13/038,276, dated Mar. 27, 2014, 24 pages. |
| Final Office Action received for U.S. Appl. No. 13/038,276, dated Mar. 11, 2016, 36 pages. |
| Final Office Action received for U.S. Appl. No. 14/641,308, dated Mar. 14, 2018, 42 pages. |
| Final Office Action received for U.S. Appl. No. 14/830,629, dated Apr. 16, 2018, 27 pages. |
| Final Office Action received for U.S. Appl. No. 14/841,646, dated Aug. 2, 2018, 22 pages. |
| Final Office Action received for U.S. Appl. No. 14/913,345, dated Oct. 26, 2018, 20 pages. |
| Final Office Action received for U.S. Appl. No. 14/913,349, dated Jul. 30, 2018, 18 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,049 dated Jul. 12, 2018, 24 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,049, dated May 23, 2017, 23 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,052, dated Mar. 1, 2018, 15 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,052, dated May 17, 2017, 13 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,052, dated Oct. 2, 2018, 16 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,058, dated Aug. 8, 2018, 23 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,058, dated May 8, 2017, 21 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,064, dated Feb. 27, 2017, 13 Pages. |
| Final Office Action received for U.S. Appl. No. 14/839,912, dated Sep. 13, 2018, 31 pages. |
| “Headset Button Controller v7.3 APK Full App Download for Andriod”, Blackberry, iPhone, Jan. 27, 2014, 11 pages. |
| IBM, “Watchpad 1.5”, Online Available at: web.archive.org/web/20011205071448/http://www.trl.ibm.com/projects/ngm/index_e.htm>, Oct. 11, 2001, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201570781, dated Dec. 8, 2016, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201670117, dated Apr. 21, 2017, 2 pages. |
| Intention to Grant received for European Patent Application No. 15782209.9, dated Sep. 28, 2018, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2012/025519, dated Sep. 3, 2013, 5 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2014/053951, dated Mar. 17, 2016, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2014/053957, dated Mar. 17, 2016, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2014/053958, dated Mar. 17, 2016, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2014/053961, dated Jul. 21, 2016, 24 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/019322, dated Mar. 16, 2017, 11 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/045936, dated Mar. 16, 2017, 9 Pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/045965, dated Dec. 27, 2016, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/047704, dated Mar. 16, 2017, 19 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/054310, dated Sep. 14, 2017, 7 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/019637, dated Sep. 21, 2017, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/019320, dated Mar. 16, 2017, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/019321, dated Mar. 16, 2017, 8 Pages. |
| International Search Report and Written Opinion received for PCT Application No. PCT/US2015/045936, dated Nov. 4, 2015, 12 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2012/025519, dated Jun. 11, 2012, 7 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2014/053951, dated Dec. 8, 2014, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2014/053957, dated Feb. 19, 2015, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2014/053958, dated Feb. 19, 2015, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/019320, dated Jul. 2, 2015, 14 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/019321, dated Jun. 3, 2015, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/019322, dated Jun. 18, 2015, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/045965, dated Feb. 1, 2016, 20 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/047704, dated Feb. 22, 2016, 25 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/054310, dated Jan. 20, 2016, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/019637, dated Aug. 18, 2016, 18 pages. |
| International Search Report and Written Opinion Received for PCT Patent Application No. PCT/US2017/035325, dated Sep. 7, 2017, 11 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2014/053961, dated Jul. 11, 2016, 10 pages. |
| International Written Opinion received for PCT Patent Application No. PCT/US2014/053961, dated Jul. 11, 2016, 22 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2014/053961, dated Aug. 3, 2015, 6 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/047704, dated Dec. 16, 2015, 10 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2016/019637, dated Jun. 1, 2016, 6 pages. |
| Kamijo, Noboru, “Next Generation Mobile System—WatchPad1.5”, Available at: http://researcher.ibm.com/researcher/view_group_subpage.php?id=5617>, retrieved on Jul. 4, 2015, 2 pages. |
| Mai, Tuan, “This Watch Tells You the Time in Vibrating Morse Code”, Available at: https://web.archive.org/web/20130915060538/http://www.tomsguide.com/us/Watch-Concept-Morse-Code,news-12089.html>, Aug. 9, 2011, pp. 1-3. |
| NDTV, “Sony SmartWatch 2 Launched in India for Rs. 14,990”, available at: http://gadgets.ndtv.com/others/news/sony-smartwatch-2-launched-in-india-for-rs-14990-420319>, Sep. 18, 2013, 4 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/038,276, dated Jul. 29, 2015, 31 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/038,276, dated Sep. 12, 2013, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,308, dated Jun. 23, 2017, 53 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/829,573, dated Jan. 22, 2018, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/830,629, dated Dec. 1, 2016, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/830,629, dated Jun. 15, 2017, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,914, dated Oct. 19, 2017, 46 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,646, dated Dec. 1, 2017, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,656, dated Jul. 26, 2017, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/913,345, dated Apr. 5, 2018, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/913,349, dated Jan. 11, 2018, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/913,350, dated May 14, 2018, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,049 dated Dec. 15, 2017, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,049, dated Nov. 9, 2016, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,052, dated May 31, 2018, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,052, dated Nov. 29, 2016, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,052, dated Sep. 21, 2017, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,058, dated Feb. 20, 2018, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,058, dated Nov. 16, 2016, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,064, dated Oct. 27, 2016, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/421,711, dated May 18, 2018, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,912, dated Feb. 12, 2018, 30 pages. |
| Non-Final office Action Received for U.S. Appl. No. 14/839,912, dated Jun. 8, 2017, 26 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2014315319, dated Oct. 12, 2017, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2014315324, dated Sep. 28, 2017, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2014315325, dated Apr. 19, 2017, 3 Pages. |
| Notice of Allowance Action received for U.S. Appl. No. 14/841,656, dated Feb. 12, 2018, 9 pages. |
| Notice of Allowance and Search Report received for Taiwanese Patent Application No. 104128687, dated Jun. 7, 2016, 4 pages (1 page of English Translation and 3 pages of Official copy). |
| Notice of Allowance received for Danish Patent Application No. PA201570776, dated Feb. 8, 2017, 2 pages. |
| Notice of Allowance received for Danish Patent Application No. PA201670118, dated Mar. 30, 2017, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-537945, dated Aug. 3, 2018, 4 pages (1 page of English translation and 3 pages of Official copy). |
| Notice of Allowance received for Japanese Patent Application No. 2016-537946, dated Mar. 26, 2018, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2016-537947, dated Jun. 5, 2017, 3 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7002695, dated Oct. 8, 2018, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 103130517, dated May 14, 2018, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 103130518, dated May 19, 2016, 2 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Notice of Allowance received for Taiwanese Patent Application No. 103130519, dated Oct. 27, 2016, 3 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Notice of Allowance received for Taiwanese Patent Application No. 103130520, dated Apr. 25, 2018, 4 pages (1 page of English Translation and 3 pages of Official copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 104107333, dated Nov. 8, 2016, 2 pages (Official Copy Only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Notice of Allowance received for Taiwanese Patent Application No. 104107334, dated Jan. 26, 2017, 3 pages (Official Copy Only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Notice of Allowance received for Taiwanese Patent Application No. 104133281, dated Mar. 29, 2018, 4 pages (1 page of English Translation and 3 pages of Official copy). |
| Notice of Allowance received for U.S. Appl. No. 13/038,276, dated Nov. 3, 2016, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/038,276, dated Nov. 30, 2016, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,241, dated Apr. 13, 2017, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,241, dated Jan. 31, 2017, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,241, dated Mar. 24, 2017, 3 Pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,252, dated Apr. 11, 2018, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,252, dated Jul. 18, 2018, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/829,573, dated Apr. 25, 2018, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/830,629, dated Oct. 17, 2018, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,914, dated Jun. 22, 2018, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/841,656, dated Mar. 5, 2018, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/049,064, dated Jul. 18, 2017, 24 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/058,996, dated Dec. 27, 2016, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/421,711, dated Oct. 5, 2018, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/055,489, dated Nov. 8, 2018, 28 pages. |
| Nova Launcher, Available on https://web.archive.org/web/20150703231459/https://play.google.com/store/apps/details?id=com.teslacoilsw.launcher, 3 pages. |
| Office Action and Search Report received for Danish Patent Application No. PA201670118, dated Jul. 1, 2016, 7 pages. |
| Office Action received for Danish Patent Application No. PA201770794, dated Dec. 19, 2017, 8 pages. |
| Office Action received for Australian Patent Application No. 2014315234, dated Jul. 12, 2017, 4 pages. |
| Office Action received for Australian Patent Application No. 2014315234, dated Nov. 2, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2014315319, dated Aug. 3, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2014315319, dated Oct. 17, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2014315324, dated Aug. 8, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2014315324, dated Oct. 21, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2014315325, dated Nov. 3, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2016229407, dated Aug. 15, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2017254897, dated Aug. 29, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2018200998, dated Mar. 9, 2018, 5 pages. |
| Office Action received for Australian Patent Application No. 2014315234, dated Apr. 19, 2017, 4 pages. |
| Office Action received for Chinese Patent Application No. 201480059543.9, dated Jan. 26, 2018, 17 pages (4 pages of English Translation and 13 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201480059543.9, dated Sep. 19, 2018, 18 pages (5 pages of English Translation and 13 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201480060044.1, dated Jan. 26, 2018, 15 pages (5 pages of English translation and 10 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201480060044.1, dated Sep. 25, 2018, 6 pages (3 pages of English translation and 3 pages of official copy). |
| Office Action received for Chinese Patent Application No. 201480060082.7, dated Jan. 26, 2018, 15 pages (4 pages of English translation and 11 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201480060082.7, dated Sep. 25, 2018, 6 pages (3 pages of English Translation and 3 pages of Official copy). |
| Office Action received for Danish Patent Application No. PA201570776, dated Aug. 19, 2016, 3 pages. |
| Office Action received for Danish Patent Application No. PA201570781, dated Aug. 19, 2016, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670117, dated Jan. 12, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670117, dated Jun. 13, 2016, 10 pages. |
| Office Action received for Danish Patent Application No. PA201670118, dated Feb. 2, 2017, 2 pages. |
| Office Action received for Danish Patent Application No. PA201670118, dated Oct. 25, 2016, 3 Pages. |
| Office Action received for Danish Patent Application No. PA201670580, dated Mar. 8, 2018, 3 Pages. |
| Office Action received for Danish Patent Application No. PA201770181, dated Jan. 3, 2018, 2 Pages. |
| Office Action received for Danish Patent Application No. PA201770181, dated Jun. 13, 2017, 6 pages. |
| Office Action received for Danish Patent Application No. PA201770794, dated Apr. 5, 2018, 4 pages. |
| Office Action received for Danish Patent Application No. PA201770794, dated Oct. 30, 2018, 3 pages. |
| Office Action received for European Patent Application No. 14771688.0, dated May 31, 2018, 6 pages. |
| Office Action received for European Patent Application No. 14771688.0, dated Nov. 30, 2017, 15 pages. |
| Office Action received for European Patent Application No. 14772001.5, dated Feb. 14, 2018, 5 pages. |
| Office Action received for European Patent Application No. 14772001.5, dated May 30, 2017, 10 pages. |
| Office Action received for European Patent Application No. 14772002.3, dated Jul. 4, 2017, 8 pages. |
| Office Action received for European Patent Application No. 14772494.2, dated Jun. 20, 2017, 7 pages. |
| Office Action received for European Patent Application No. 14772494.2, dated Oct. 2, 2018, 9 pages. |
| Office Action received for European Patent Application No. 18157131.6, dated May 8, 2018, 12 pages. |
| Office Action received for Japanese Patent Application No. 2016-537945, dated Apr. 7, 2017, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-537945, dated Jan. 9, 2018, 5 pages (2 page of English Translation and 3 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2016-537946, dated Aug. 7, 2017, 8 pages (4 Pages of English Translation and 4 Pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-537946, dated Jan. 30, 2017, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-537947, dated Feb. 24, 2017, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-537948, dated Apr. 6, 2018, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-537948, dated Jun. 9, 2017, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-537948, dated Sep. 3, 2018, 4 pages (2 pages of English Translation and 2 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2017-545561, dated Aug. 6, 2018, 8 pages (4 pages of English Translation and 4 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008449, dated Jan. 12, 2017, 15 pages (6 pages of English translation and 9 pages of official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008449, dated Jan. 16, 2018, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008449, dated Nov. 27, 2017, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008474, dated Aug. 6, 2018, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008474, dated Dec. 28, 2016, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008474, dated May 15, 2018, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008474, dated Nov. 27, 2017, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008488, dated Feb. 8, 2018, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008488, dated Jan. 12, 2017, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008488, dated Nov. 27, 2017, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008682, dated Dec. 30, 2016, 11 pages (4 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008682, dated Feb. 8, 2018, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008682, dated Nov. 27, 2017, 7 pages (3 page of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7024506, dated Sep. 28, 2018, 11 pages (4 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7002695, dated Feb. 27, 2018, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7002695, dated Jun. 19, 2018, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7010872, dated May 21, 2018, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7013265, dated Aug. 10, 2018, 12 pages (5 pages of English Translation and 7 pages of Official copy). |
| Office Action received for Taiwan Patent Application No. 103130517, dated Feb. 22, 2016, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Taiwan Patent Application No. 103130519, dated Mar. 25, 2016, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130517, dated Jul. 29, 2016, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130517, dated Feb. 6, 2018, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130520, dated Apr. 17, 2017, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130520, dated Jan. 23, 2018, 05 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130520, dated May 23, 2016, 38 pages (15 pages of English Translation and 23 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130520, dated Oct. 1, 2015, 58 pages (22 pages of English translation and 36 pages of Official copy). |
| Office Action received for Taiwanese Patent Application No. 103130520, dated Sep. 29, 2016, 39 pages (16 pages of English Translation and 23 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104107333, dated May 17, 2016, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104107334, dated Sep. 19, 2016, 15 pages (6 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104128701, dated Jul. 22, 2016, 25 pages (9 pages of English Translation and 16 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104128701, dated Mar. 16, 2017, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104133281, dated Mar. 30, 2017, 10 Pages (4 pages of English translation and 6 pages of official copy). |
| Office Action received for Taiwanese Patent Application No. 104133281, dated Sep. 1, 2016, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104107327, dated Sep. 28, 2018, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA201570776, dated Jan. 26, 2016, 12 pages. |
| Raghunath, et al, “User Interfaces for Applications on a Wrist Watch”, Journal of Personal and Ubiquitous Computing, vol. 6, Feb. 2002, pp. 17-30. |
| Search Report and Opinion received for Danish Patent Application No. PA201670580, dated Jan. 31, 2017, 7 pages. |
| Search Report received for Danish Patent Application No. PA201570781, dated Mar. 8, 2016, 10 pages. |
| Search Report received for European Patent Application No. 18157131.6, dated Apr. 19, 2018, 4 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 14772001.5, mailed on Nov. 14, 2018, 5 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 14772001.5, mailed on Oct. 4, 2018, 15 pages. |
| The Blind Life, “Double Tap Big Clock”, https://www.youttlbe.com/watch?v-=U6XMnSPCEXU, Mar. 2, 2016, 2 Pages. |
| “The interview with a key person. IBM and Citizen met and applied Linux to a watch”, ASCII Corporation, vol. 25, No. 12, Dec. 12, 2001, pp. 136-143 (Official Copy Only) (See Communication under 37 CFR § 1.98(a) (3)). |
| The Window Club, “How to Set GIF as Background Windows 7”, Online Available at: https://www.youtube.com/watch?v=tUec42Qd7ng>, Dec. 24, 2012, pp. 1-5. |
| “Timebuzz”, Feel the Current Time on your Apple Watch with Time Buzz, Available at: https://web.archive.org/web/20160125032143/http://www.timebuzz.nl/>, Jan. 25, 2016, pp. 1-6. |
| Toyssy, et al, “Telling Time by Vibration”, University of Tampere, Department of Computer Sciences, Interactive Technology, Master's Thesis, Nov. 2007, 57 Pages. |
| Toyssy, Sampo, et al, “Telling Time by Vibration”, 6th International Conference, EuroHaptics 2008 Madrid, Spain, Jun. 10-11, 2008, pp. 924-929. |
| “Watchpad 1.5 demo”, YouTube.com, Online Available at: https://www.youtube.com/watch?v=7xjvVbeUn80>, Uploaded on Jun. 20, 2010, 2 pages. |
| Wikipedia, “Rotary encoder”, Online Available at: https://en.wikipedia.org/wiki/Rotary_encoder>, Retrieved on May 17, 2017, 17 pages (10 pages of English Translation and 7 pages of Official Copy). |
| Dewsberry, Victor, “Designing for Small Screens”, AVA Publishing, 2005, 27 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/035325, dated Dec. 27, 2018, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,308, dated Dec. 20, 2018, 43 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870631, dated Apr. 5, 2019, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870632, dated Apr. 5, 2019, 2 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017276285, dated Apr. 3, 2019, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-143982, dated Apr. 8, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 14/841,646, dated Apr. 18, 2019, 7 pages. |
| Office Action received for Australian Patent Application No. 2018200289, dated Apr. 9, 2019, 5 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870631, dated May 15, 2019, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870632, dated May 14, 2019, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,058, dated Jun. 5, 2019, 25 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-090084, dated May 24, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 15/927,768, dated May 31, 2019, 13 pages. |
| Office Action received for Australian Patent Application No. 2016229407, dated May 27, 2019, 4 pages. |
| Intention to Grant received for European Patent Application No. 14772001.5, dated Mar. 22, 2019, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/913,349, dated Apr. 2, 2019, 15 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201480060082.7, dated Mar. 12, 2019, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Office Action received for Chinese Patent Application No. 201480059543.9, dated Feb. 28, 2019, 16 pages (4 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201580046339.8, dated Feb. 26, 2019, 18 pages (6 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2018-090084, dated Feb. 15, 2019, 6 pages (3 pages of English Translation and 3 pages of Official copy). |
| Final Office Action received for U.S. Appl. No. 14/913,349, dated Jul. 22, 2019, 20 pages. |
| Final Office Action received for U.S. Appl. No. 14/839,912, dated Jul. 30, 2019, 42 pages. |
| Intention to Grant received for European Patent Application No. 14772001.5, dated Jul. 18, 2019, 16 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-545561, dated Jul. 12, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2018-083313, dated Jul. 1, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 15/049,049, dated Jul. 25, 2019, 8 pages. |
| Partial European Search Report received for European Patent Application No. 19173371.6, dated Jul. 18, 2019, 17 pages. |
| Partial European Search Report received for European Patent Application No. 19173886.3, dated Jul. 18, 2019, 15 pages. |
| Advisory Action received for U.S. Appl. No. 14/841,646, dated Nov. 21, 2018, 5 pages. |
| Intention to Grant received for European Patent Application No. 18157131.6, dated Jan. 9, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/055,489, dated Jan. 9, 2019, 24 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/055,489, dated Jan. 25, 2019, 8 pages. |
| Office Action received for Chinese Patent Application No. 201480060083.1, dated Dec. 5, 2018, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for European Patent Application No. 14771688.0, dated Jan. 21, 2019, 8 pages. |
| Office Action received for Japanese Patent Application No. 2018-143982, dated Dec. 7, 2018, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7010872, dated Dec. 21, 2018, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7032106, dated Dec. 26, 2018, 10 pages (4 pages of English translation and 6 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/830,629, dated Feb. 13, 2019, 3 pages. |
| Decision to Grant received for European Patent Application No. 15782209.9, dated Feb. 14, 2019, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,049, dated Feb. 6, 2019, 21 pages. |
| Office Action received for Australian Patent Application No. 2018200998, dated Jan. 30, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201670580, dated Feb. 4, 2019, 2 pages. |
| Office Action received for Taiwanese Patent Application No. 104107318, dated Dec. 26, 2018, 33 pages (9 pages of English Translation and 24 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2018-083313, dated Feb. 12, 2019, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Extended European Search Report received for European Patent Application No. 19156614.0, dated May 28, 2019, 9 pages. |
| Final Office Action received for U.S. Appl. No. 14/641,308, dated Jul. 1, 2019, 46 pages. |
| Intention to Grant received for European Patent Application No. 14772002.3, dated Jun. 24, 2019, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/913,345, dated Jun. 26, 2019, 23 pages. |
| Office Action received for Danish Patent Application No. PA201770794, dated Jun. 13, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/927,768, dated Jul. 9, 2019, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/655,253, dated Jul. 10, 2019, 16 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7032106, dated Jun. 28, 2019, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2017254897, dated Jun. 28, 2019, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2018-7013265, dated Jun. 14, 2019, 6 pages (2 pages of English Translation and 4 pages of official copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/055,489, dated Feb. 26, 2019, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,912, dated Feb. 26, 2019, 36 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,950, dated Mar. 6, 2019, 24 pages. |
| Office Action received for European Patent Application No. 16710372.0, dated Feb. 22, 2019, 7 pages. |
| Office Action received for Korean Patent Application No. 10-2018-7010872, dated Feb. 13, 2019, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Decision to Grant received for European Patent Application No. 18157131.6, dated May 16, 2019, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201480060044.1, dated Mar. 29, 2019, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2019201628, dated May 13, 2019, 2 pages. |
| Office Action received for Chinese Patent Application No. 201780014703.1, dated Apr. 30, 2019, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Search Report and Opinion received for Danish Patent Application No. PA201970259, dated Jul. 19, 2019, 10 pages. |
| European Search Report received for European Patent Application No. 19173371.6, dated Oct. 30, 2019, 7 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/049237, dated Oct. 31, 2019, 18 pages. |
| Office Action received for European Patent Application No. 19173371.6, dated Nov. 12, 2019, 11 pages. |
| Office Action received for European Patent Application No. 19173886.3, dated Nov. 12, 2019, 9 pages. |
| Advisory Action received for U.S. Appl. No. 14/641,308, dated Nov. 14, 2019, 4 pages. |
| Advisory Action received for U.S. Appl. No. 14/839,912, dated Nov. 14, 2019, 6 pages. |
| Advisory Action received for U.S. Appl. No. 14/913,349, dated Oct. 29, 2019, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 14/913,345, dated Nov. 4, 2019, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 14/913,349, dated Oct. 7, 2019, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/655,253, dated Nov. 12, 2019, 3 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 14/839,912, dated Nov. 5, 2019, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 14/641,308, dated Oct. 10, 2019, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/109,120, dated Nov. 12, 2019, 2 pages. |
| Decision on Appeal received for Korean Patent Application No. 10-2016-7008449, mailed on Jul. 30, 2019, 29 pages (7 pages of English Translation and 22 pages of Official Copy). |
| Decision on Appeal received for Korean Patent Application No. 10-2016-7008488, mailed on Oct. 18, 2019, 33 pages (4 pages of English Translation and 29 pages of Official Copy). |
| Decision to Grant received for Danish Patent Application No. PA201770794, dated Nov. 11, 2019, 2 pages. |
| Decision to Grant received for European Patent Application No. 14772001.5, dated Dec. 5, 2019, 2 pages |
| European Search Report received for European Patent Application No. 19199004.3, dated Nov. 12, 2019, 6 pages. |
| European Search Report received for European Patent Application No. 19206249.5, dated Dec. 19, 2019, 4 pages. |
| Extended European Search Report received for European Patent Application No. 17813779.0, dated Oct. 29, 2019, 8 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,950, dated Nov. 25, 2019, 24 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770794, dated Aug. 15, 2019, 2 pages. |
| Intention to Grant received for European Patent Application No. 14772002.3, dated Nov. 6, 2019, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/913,349, dated Jan. 2, 2020, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/818,500, dated Aug. 30, 2019, 17 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019201628, dated Sep. 10, 2019, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201480059543.9, dated Sep. 4, 2019, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201780014703.1, dated Nov. 6, 2019, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2016-537948, dated Nov. 11, 2019, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7008449, dated Aug. 9, 2019, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7008488, dated Oct. 25, 2019, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 14/641,308, dated Jan. 15, 2020, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/049,052, dated Sep. 16, 2019, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/109,120, dated Sep. 11, 2019, 12 pages. |
| Office Action received for Australian Patent Application No. 2019216614, dated Aug. 22, 2019, 3 pages. |
| Office Action received for Chinese Patent Application No. 201480060083.1, dated Aug. 13, 2019, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201580046339.8, dated Oct. 31, 2019, 9 pages (3 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201910454076.4, dated Dec. 18, 2019, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA201970259, dated Jan. 15, 2020, 4 pages. |
| Office Action received for European Patent Application No. 14771688.0, dated Sep. 16, 2019, 7 pages. |
| Office Action received for European Patent Application No. 19199004.3, dated Nov. 22, 2019, 10 pages. |
| Office Action received for Indian Patent Application No. 201617008291, dated Jan. 14, 2020, 7 pages. |
| Office Action received for Indian Patent Application No. 201617008296, dated Jan. 14, 2020, 7 pages. |
| Office Action received for Korean Patent Application No. 10-2017-7024506, dated Aug. 12, 2019, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7033888, dated Nov. 28, 2019, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7007748, dated Nov. 15, 2019, 9 pages (3 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7028736, dated Nov. 28, 2019, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| European Search Report received for European Patent Application No. 19173886.3, dated Oct. 30, 2019, 8 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/927,768, dated Aug. 7, 2019, 2 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018200289, dated Jul. 23, 2019, 3 pages. |
| Notice of Allowance received for Taiwanese Patent Application No. 104107327, dated Jul. 19, 2019, 5 pages (2 pages of English Translation and 3 pages of Official copy). |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/144,950, dated Jan. 29, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/818,500, dated Jan. 30, 2020, 5 pages. |
| Decision on Appeal received for Korean Patent Application No. 10-2018-7010872, mailed on Jan. 20, 2020, 20 pages (3 pages of English Translation and 17 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 15/655,253, dated Feb. 4, 2020, 20 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/049237, dated Jan. 8, 2020, 21 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/913,345, dated Feb. 10, 2020, 10 pages. |
| Office Action received for European Patent Application No. 19206249.5, dated Jan. 20, 2020, 8 pages. |
| Office Action received for Indian Patent Application No. 201617009216, dated Jan. 24, 2020, 6 pages. |
| Office Action received for Chinese Patent Application No. 201910454069.4, dated Dec. 20, 2019, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/641,308, dated Mar. 10, 2020, 4 pages. |
| Extended European Search Report received for European Patent Application No. 19195247.2, dated Mar. 9, 2020, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,950, dated Mar. 19, 2020, 14 pages. |
| Office Action received for Chinese Patent Application No. 201580077206.7, dated Feb. 3, 2020, 29 pages (8 pages of English Translation and 21 pages of Official Copy). |
| Extended European Search Report received for European Patent Application No. 19217240.1, dated May 25, 2020, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/384,726, dated May 14, 2020, 16 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7007748, dated May 6, 2020, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7028736, dated May 7, 2020, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 16/144,950, dated Feb. 20, 2020, 5 pages. |
| Decision on Appeal received for Korean Patent Application No. 10-2016-7008474, mailed on Jan. 29, 2020, 21 pages (2 pages of English Translation and 19 pages of Official Copy). |
| Decision to Grant received for European Patent Application No. 14772002.3, dated Feb. 20, 2020, 2 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7010872, dated Feb. 10, 2020, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Indian Patent Application No. 201617009428, dated Feb. 26, 2020, 7 pages. |
| Office Action received for Korean Patent Application No. 10-2017-7024506, dated Feb. 19, 2020, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/655,253, dated Mar. 31, 2020, 5 pages. |
| Intention to Grant received for European Patent Application No. 14772494.2, dated Mar. 16, 2020, 10 pages. |
| Office Action received for Taiwanese Patent Application No. 104107318, dated Feb. 18, 2020, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/913,345, dated Apr. 13, 2020, 4 pages. |
| Final Office Action received for U.S. Appl. No. 15/818,500, dated Apr. 6, 2020, 15 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7013265, dated Apr. 1, 2020, 4 pages (1 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2019216614, dated Apr. 1, 2020, 4 pages. |
| Office Action received for Taiwanese Patent Application No. 104107329, dated Mar. 5, 2020, 22 pages (9 pages of English Translation and 13 pages of Official Copy). |
| Non-Final Office Action received for U.S. Appl. No. 14/913,349, dated Apr. 22, 2020, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/358,483, dated May 1, 2020, 37 pages. |
| Office Action received for Chinese Patent Application No. 201910164962.3, dated Apr. 8, 2020, 25 pages (13 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130518, dated Oct. 15, 2015, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201910454069.4, dated Jul. 24, 2020, 8 pp. (5 pages of English Translation and 3 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/525,082, dated Jul. 28, 2020, 4 pages. |
| Decision to Grant received for European Patent Application No. 14772494.2, dated Jul. 23, 2020, 2 pages. |
| Intention to Grant received for European Patent Application No. 19199004.3, dated Sep. 14, 2020, 9 pages. |
| Intention to Grant received for Indian Patent Application No. 201617009216, dated Aug. 27, 2020, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/655,253, dated Sep. 10, 2020, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/263,280, dated Jul. 27, 2020, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/525,082, dated Jul. 9, 2020, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/734,173, dated Jul. 23, 2020, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/930,300, dated Aug. 5, 2020, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/525,082, dated Aug. 20, 2020, 5 pages. |
| Office Action received for Australian Patent Application No. 2019206101, dated Jul. 14, 2020, 4 pages. |
| Office Action received for Australian Patent Application No. 2019216614, dated Aug. 13, 2020, 4 pages. |
| Office Action received for Australian Patent Application No. 2019257521, dated Aug. 7, 2020, 5 pages. |
| Office Action received for Australian Patent Application No. 2019272034, dated Sep. 14, 2020, 4 pages. |
| Office Action received for Chinese Patent Application No. 201580046339.8, dated Jun. 3, 2020, 19 pages (10 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680012759.9, dated Jun. 19, 2020, 18 pages (7 pages of English Translation and 11 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201810074876.9, dated Jul. 31, 2020, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for European Patent Application No. 17813779.0, dated Aug. 28, 2020, 7 pages. |
| Office Action received for Japanese Patent Application No. 2019-088503, dated Jul. 31, 2020, 7 pages (4 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7024506, dated Jul. 8, 2020, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7033888, dated Jul. 7, 2020, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7019035, dated Aug. 28, 2020, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7022802, dated Aug. 28, 2020, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104107329, dated Jul. 24,. 2020, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Pedersen Isabel, “Ready to Wear (or Not) Examining the Rhetorical Impact of. Proposed Wearable Devices”, 2013 IEEE International Symposium on Technology and Society (ISTAS) Social Implications of Wearable Computing and Augmediated Reality III. Everyday Life, Dec. 31, 2013, pp. 201-202. |
| Tong et al., “Discussion About the Influence of Wearable Device on Mobile Operators'Service”, Telecom science, Oct. 31, 2014, pp. 134-142 (Official Copy Only) {See. Communication under 37 Cfr § 1.98(a) (3)}. |
| Notice of Allowance received for Chinese Patent Application No. 201910454069.4, dated Nov. 2, 2020, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201910454076.4, dated Oct. 16, 2020, 14 pages (8 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA201970259, dated Nov. 23, 2020, 3 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20200081539 A1 | Mar 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62729978 | Sep 2018 | US |
