Patent Grant
11740785
This relates generally to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that detect inputs for manipulating user interfaces.
The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Exemplary touch-sensitive surfaces include touchpads and touch-screen displays. Such surfaces are widely used to manipulate user interfaces on a display.
Exemplary manipulations include adjusting the position and/or size of one or more user interface objects or activating buttons or opening files/applications represented by user interface objects, as well as associating metadata with one or more user interface objects or otherwise manipulating user interfaces. Exemplary user interface objects include digital images, video, text, icons, and control elements such as buttons and other graphics.
A user will, in some circumstances, need to perform such manipulations on user interface objects in a file management program (e.g., Finder from Apple Inc. of Cupertino, Calif.), a messaging application (e.g., Messages from Apple Inc. of Cupertino, Calif.), an image management application (e.g., Photos from Apple Inc. of Cupertino, Calif.), a camera application (e.g., Camera from Apple Inc. of Cupertino, Calif.), a map application (e.g., Maps from Apple Inc. of Cupertino, Calif.), a note taking application (e.g., Notes from Apple Inc. of Cupertino, Calif.), digital content (e.g., videos and music) management applications (e.g., Music and iTunes from Apple Inc. of Cupertino, Calif.), a news application (e.g., News from Apple Inc. of Cupertino, Calif.), a phone application (e.g., Phone from Apple Inc. of Cupertino, Calif.), an email application (e.g., Mail from Apple Inc. of Cupertino, Calif.), a browser application (e.g., Safari from Apple Inc. of Cupertino, Calif.), a drawing application, a presentation application (e.g., Keynote from Apple Inc. of Cupertino, Calif.), a word processing application (e.g., Pages from Apple Inc. of Cupertino, Calif.), a spreadsheet application (e.g., Numbers from Apple Inc. of Cupertino, Calif.), a reader application (e.g., iBooks from Apple Inc. of Cupertino, Calif.), a video making application (e.g., iMovie from Apple Inc. of Cupertino, Calif.), and/or geo location applications (e.g., Find Friends and Find iPhone from Apple Inc. of Cupertino, Calif.).
But existing methods for performing these manipulations are cumbersome and inefficient. In addition, existing methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, there is a need for electronic devices with faster, more efficient methods and interfaces for manipulating user interfaces. Such methods and interfaces optionally complement or replace conventional methods for manipulating user interfaces. Such methods and interfaces reduce the number, extent, and/or nature of the inputs from a user and produce a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.
The above deficiencies and other problems associated with user interfaces for electronic devices with touch-sensitive surfaces are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the device is a personal electronic device (e.g., a wearable electronic device, such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen” or “touch-screen display”). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and/or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions optionally include image editing, drawing, presenting, word processing, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music playing, note taking, and/or digital video playing. Executable instructions for performing these functions are, optionally, included in a non-transitory computer readable storage medium or other computer program product configured for execution by one or more processors.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors for detecting intensities of contacts on the touch-sensitive surface. The device concurrently displays, on the display: a background user interface; and a first version of a notification associated with a first application, wherein: the first version of the notification has a first size, the first version of the notification includes first content, and the first version of the notification is overlaid on the background user interface. While displaying the first version of the notification associated with the first application overlaid on the background user interface, the device detects a first portion of a first input that includes detecting a first contact at a location on the touch-sensitive surface that corresponds to the first version of the notification. In response to detecting the first portion of the first input: in accordance with a determination that the first portion of the first input meets application-launching criteria, wherein the application-launching criteria do not require that a characteristic intensity of the first contact on the touch-sensitive surface meet a preview intensity threshold in order for the application-launching criteria to be met, the device initiates a process to launch the first application, wherein launching the first application includes ceasing to display the background user interface and displaying a user interface associated with the first application; and, in accordance with a determination that the first portion of the first input meets notification-expansion criteria, wherein the notification-expansion criteria require that the characteristic intensity of the first contact on the touch-sensitive surface meet the preview intensity threshold in order for the notification-expansion criteria to be met, the device displays a second version of the notification, wherein: the second version of the notification has a second size larger than the first size, the second version of the notification includes expanded notification content that is not displayed in the first version of the notification, and the second version of the notification is overlaid on the background user interface.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors for detecting intensities of contacts on the touch-sensitive surface. The method includes: displaying, on the display, a user interface that includes a plurality of application icons that correspond to different applications in a plurality of applications; while displaying the user interface that includes the plurality of application icons, detecting a first input that includes detecting a first contact on the touch-sensitive surface at a location on the touch-sensitive surface that corresponds to a first application icon of the plurality of application icons, the first application icon being associated with a first application of the plurality of applications; in response to detecting the first input: in accordance with a determination that the first input meets application-launching criteria, wherein the application-launching criteria do not require that a characteristic intensity of the first contact on the touch-sensitive surface meet a first intensity threshold in order for the application-launching criteria to be met: launching the first application; and replacing display of the user interface that includes the plurality of application icons with a user interface of the first application; and, in accordance with a determination that the first input meets menu-presentation criteria, wherein the menu-presentation criteria require that the characteristic intensity of the first contact on the touch-sensitive surface meet the first intensity threshold in order for the menu-presentation criteria to be met, concurrently displaying a contextual content object and a respective affordance that is associated with the contextual content object, wherein: the contextual content object includes contextually selected content that has been automatically selected from the first application based on a current context of the electronic device; and the respective affordance, when activated, is configured to add the contextual content object to a user interface that includes information for multiple applications.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors for detecting intensities of contacts on the touch-sensitive surface. The method includes: displaying, on the display, a user interface that includes a plurality of user interface objects that correspond to different applications in a plurality of applications, wherein the plurality of user interface objects include a first user interface object that corresponds a first application that is in a process of being downloaded; while displaying the user interface that includes the plurality of user interface objects, detecting a first input that includes detecting a first contact at a location on the touch-sensitive surface that corresponds to the first user interface object; and in response to detecting the first input: in accordance with a determination that the first user interface object corresponds to an application that has not been fully downloaded and that the first input meets menu-presentation criteria, wherein the menu-presentation criteria require that a characteristic intensity of a contact in a detected input meet a first intensity threshold in order for the menu-presentation criteria to be met, displaying one or more first selectable options that, when activated, are configured to perform actions with respect to downloading of the first application.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors for detecting intensities of contacts on the touch-sensitive surface. The method includes: displaying a user interface on the display, wherein: the user interface includes a folder icon that corresponds to an application folder containing a plurality of application icons, the plurality of application icons correspond to different applications in a plurality of applications, and the plurality of applications include one or more applications that have one or more unread notifications; while displaying the user interface that includes the folder icon, detecting a first input that includes detecting a first contact at a location on the touch-sensitive surface that corresponds to the folder icon; and in response to detecting the first input: in accordance with a determination that the first input meets menu-presentation criteria, wherein the menu-presentation criteria require that a characteristic intensity of a contact in a detected input meet a first intensity threshold in order for the menu-presentation criteria to be met, displaying one or more selectable options that, when activated, are configured to launch corresponding applications from the plurality of applications in the application folder that have unread notifications.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensities of contacts with the touch-sensitive surface. The method includes: displaying a control user interface that includes a plurality of control affordances; detecting a first input by a contact at a location on the touch-sensitive surface that corresponds to a first control affordance, of the plurality of control affordances, on the display; in response to detecting the first input: in accordance with a determination that the first input meets control toggle criteria, wherein the control toggle criteria do not require that a characteristic intensity of the contact meet a first intensity threshold in order for the control toggle criteria to be met, toggling a function of a control that corresponds to the first control affordance; and, in accordance with a determination that the first input meets enhanced control criteria, wherein the enhanced control criteria require that the characteristic intensity of the contact meet the first intensity threshold in order for the enhanced control criteria to be met, displaying one or more modification options for the control that correspond to the first control affordance; while displaying the one or more modification options for the control that correspond to the first control affordance, detecting a second input that activates a first modification option of the one or more modification options; and modifying the control that corresponds to the first control affordance in accordance with the activated first modification option.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensities of contacts with the touch-sensitive surface. The method includes: displaying a user interface that includes: an editable content area that has a plurality of characters, and a content deletion control; detecting a deletion input that includes detecting a contact at a location on the touch-sensitive surface that corresponds to the content deletion control on the display; and in response to detecting the deletion input, deleting content in the editable content area based on a duration and a characteristic intensity of the contact, including: in accordance with a determination that the contact was maintained for a first time period without the characteristic intensity of the contact increasing above a first intensity threshold, deleting the content in the editable content area by sequentially deleting a plurality of sub-units of the content of a first type of sub-unit of the content at a rate that does not vary based on the characteristic intensity of the contact; in accordance with a determination that the contact was maintained for a second time period that is longer than the first time period without the characteristic intensity of the contact increasing above the first intensity threshold, deleting the content in the editable content area by sequentially deleting a plurality of sub-units of the content of a second type of sub-unit of the content at a rate that does not vary based on the characteristic intensity of the contact; and in accordance with a determination that the characteristic intensity of the contact increased above the first intensity threshold, deleting the content in the editable content area by sequentially deleting a plurality of sub-units of the content at a rate that varies based on the characteristic intensity of the contact.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensities of contacts with the touch-sensitive surface. The method includes: displaying, on the display, a messaging interface that includes a conversation transcript and a message input area, wherein the message input area includes an affordance for sending a message; while the message input area contains message content, detecting a first input by a contact at a location of the touch-sensitive surface that corresponds to the affordance for sending the message; determining a characteristic intensity of the contact in the first input; in response to detecting the first input: in accordance with a determination that the first input meets send criteria, wherein the send criteria do not require that a characteristic intensity of the contact meet a first intensity threshold in order for the send criteria to be met, initiating sending the message content to a remote device; and, in accordance with a determination that the contact meets message impact criteria, wherein the message impact criteria required that the characteristic intensity of the contact meet the first intensity threshold in order for the message impact criteria to be met, displaying a plurality of message impact effect options for changing an animation that is displayed when the message is received at the remote device; while displaying the plurality of message impact effect options, detecting a second input by a contact to send the message content with a selected message impact effect option of the plurality of impact effect options; and in response to detecting the second input, in accordance with a determination that the second input was received at a location on the touch-sensitive surface that corresponds to a first message impact effect option of the plurality of impact effect options, initiating sending, to the remote device, the message content with the first message impact effect option.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensities of contacts with the touch-sensitive surface. The method includes: displaying, on the display, a user interface that includes a plurality of activatable objects, including a first activatable object with a first visual appearance, wherein the device is configured to: for intensity-reactive activatable objects, perform operations corresponding to the intensity-reactive activatable objects based on characteristic intensities of inputs on the touch-sensitive surface that correspond to the intensity-reactive activatable objects, such that when a characteristic intensity of a contact that is providing input that corresponds to a respective intensity-reactive activatable object on the touch-sensitive surface meets intensity-based activation criteria, an operation corresponding to the respective intensity-reactive activatable object is performed as a result of the characteristic intensity of the contact meeting the intensity-based activation criteria; and for intensity-nonreactive activatable objects, perform operations corresponding to the intensity-nonreactive activatable objects without regard to whether inputs on the touch-sensitive surface that correspond to the intensity-nonreactive activatable objects meet the intensity-based activation criteria, such that when a characteristic intensity of a contact that is providing input that corresponds to a respective intensity-nonreactive activatable object on the touch-sensitive surface meets the intensity-based activation criteria, an operation corresponding to the respective intensity-nonreactive activatable object is not performed as a result of the characteristic intensity of the contact meeting the intensity-based activation criteria; while displaying the user interface on the display, detecting an input that corresponds to a request to select the first activatable object in the plurality of activatable objects, wherein a characteristic intensity of the input fails to meet the intensity-based activation criteria during the input; and in response to detecting the input: in accordance with a determination that the first activatable object is an intensity-reactive activatable object, displaying the first activatable object with a first transformation from its first visual appearance; and, in accordance with a determination that the first activatable object is an intensity-nonreactive activatable object, displaying the first activatable object without displaying the first transformation.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensities of contacts with the touch-sensitive surface: while displaying a user interface, detecting an input by a contact at a first location on the touch-sensitive surface that corresponds to a first activatable user interface object on the display; and, in response to detecting the input by the contact: in accordance with a determination that the first activatable user interface object is intensity-reactive, changing a visual appearance of the first activatable user interface object in accordance with changes in a detected intensity of the contact on the touch-sensitive surface; and, in accordance with a determination that the first activatable user interface object is intensity-nonreactive, changing the visual appearance of the first activatable user interface object by a predetermined amount.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensities of contacts with the touch-sensitive surface. The method includes: displaying a user interface that includes a plurality of activatable user interface objects; while displaying the user interface, detecting a first portion of an input by a contact at a first location on the touch-sensitive surface that corresponds to a first user interface object on the display; in response to detecting the first portion of the input: changing a visual appearance of the first user interface object by applying a first visual transformation to the first user interface object, wherein the first visual transformation corresponds to a first user interface operation; after changing the visual appearance of the first user interface object by applying the first visual transformation to the first user interface object, detecting a second portion of the input; and in response to detecting the second portion of the input: in accordance with a determination that the second portion of the input is consistent with the first user interface operation, performing the first user interface operation; and in accordance with a determination that the second portion of the input includes a gradual change in a first parameter that is indicative of performance of a second user interface operation, dynamically reducing the first visual transformation as the first parameter gradually changes without performing the first user interface operation.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensities of contacts with the touch-sensitive surface. The method includes: displaying a user interface that includes a plurality of activatable user interface objects; while displaying the user interface, detecting a first portion of an input by a contact at a first location on the touch-sensitive surface that corresponds to a first user interface object on the display; in response to detecting the first portion of the input by the contact: changing a visual appearance of the first user interface object to indicate that an operation corresponding to the first user interface object will be performed in response to detecting liftoff of the contact from the touch-sensitive surface, wherein the change in the visual appearance includes applying a first transformation to the first user interface object; detecting a second portion of the input by the contact, wherein the second portion of the input immediately follows the first portion of the input; and, in response to detecting the second portion of the input by the contact: in accordance with a determination that the second portion of the input includes a gradual change in a first input parameter and corresponds to a first gesture, changing the visual appearance of the first user interface object by dynamically reducing the first transformation and applying a second transformation corresponding to the first gesture as the first input parameter gradually changes; and, in accordance with a determination that the second portion of the input includes a gradual change in a second input parameter and corresponds to a second gesture, changing the visual appearance of the first user interface object by dynamically reducing the first transformation and applying a third transformation corresponding to the second gesture as the second input parameter gradually changes.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensities of contacts with the touch-sensitive surface. The method includes: displaying a first user interface that includes a plurality of activatable user interface objects; while displaying the first user interface, detecting an input by a contact at a first location on the touch-sensitive surface that corresponds to a first activatable user interface object on the display, wherein: the first activatable user interface object is associated with a control function with three or more available values; and a first value of the control function is selected as a current value for the control function; in response to detecting the input by the contact: in accordance with a determination that the input meets toggle criteria, wherein the toggle criteria do not require that a characteristic intensity of the contact on the touch-sensitive surface meets a first intensity threshold in order for the toggle criteria to be met, toggling the control function that corresponds to the first activatable user interface object between a first state that is based on the current value for the control function and a second state; and, in accordance with a determination that the input meets control adjustment criteria, wherein the control adjustment criteria require that the characteristic intensity of the contact on the touch-sensitive surface meets the first intensity threshold in order for the control adjustment criteria to be met, displaying a second user interface that includes a second activatable user interface object that has three or more state options that correspond to the three or more available values for the control function; and while displaying the second user interface and continuing to detect the contact: detecting movement of the contact across the touch-sensitive surface; ceasing to detect the contact; and, in response to detecting the movement of the contact across the touch-sensitive surface, changing the current value for the control function based on the movement of the contact.
In accordance with some embodiments, an electronic device includes a display, a touch-sensitive surface, optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, one or more processors, memory, and one or more programs; the one or more programs are stored in the memory and configured to be executed by the one or more processors and the one or more programs include instructions for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, a computer readable storage medium has stored therein instructions which when executed by an electronic device with a display, a touch-sensitive surface, and optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, cause the device to perform or cause performance of the operations of any of the methods described herein. In accordance with some embodiments, a graphical user interface on an electronic device with a display, a touch-sensitive surface, optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, a memory, and one or more processors to execute one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described herein, which are updated in response to inputs, as described in any of the methods described herein. In accordance with some embodiments, an electronic device includes: a display, a touch-sensitive surface, and optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface; and means for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a display and a touch-sensitive surface, and optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface, includes means for performing or causing performance of the operations of any of the methods described herein.
Thus, electronic devices with displays, touch-sensitive surfaces and optionally one or more sensors to detect intensity of contacts with the touch-sensitive surface are provided with faster, more efficient methods and interfaces for providing access to content and functions of applications without first launching the application, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for accessing content and functions of an application.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
FIGS. 5A1-5I9 illustrate example user interfaces for interacting with a notification associated with a respective application (e.g., to access a subset of functions and/or content of the respective application from the notification without having to first activate the respective application), in accordance with some embodiments.
FIGS. 5J1-5P2 illustrate example user interfaces for displaying a contextual content object (e.g., a mini application object) associated with a respective application (e.g., to provide access to a subset of functions and content of the respective application without having to first activate the respective application), in accordance with some embodiments.
FIGS. 5Q1-5S5 illustrate user interfaces for interacting with a menu of applications that includes an application that is in the process of being downloaded (e.g., providing a menu of options to quickly invoke one of several download-related quick actions with respect to the application that is in the process of being downloaded), in accordance with some embodiments.
FIGS. 5T1-5T15 illustrate user interfaces for interacting with a menu of applications that include a folder of applications (e.g., selectively providing a menu for quickly launching a respective application with unread notifications from the folder containing multiple applications without having to first open the folder), in accordance with some embodiments.
FIGS. 5U1-5W5 illustrate user interfaces for quickly entering a rename and icon reconfiguration mode for an application folder (e.g., without having to first open the folder), in accordance with some embodiments.
FIGS. 9A1-9A25 illustrate exemplary user interfaces for displaying intensity-reactive and intensity-nonreactive user interface objects, in accordance with some embodiments.
FIGS. 9B1-9B10 illustrate exemplary user interfaces for displaying intensity-reactive and intensity-nonreactive user interface objects, in accordance with some embodiments.
FIGS. 9C1-9C19 illustrate exemplary user interfaces for displaying control settings interfaces for control functions for remote devices, in accordance with some embodiments.
FIGS. 24A1-24A3 are flow diagrams illustrating a method of displaying intensity-reactive and intensity-nonreactive user interface objects in accordance with some embodiments.
FIGS. 24B1-24B3 are flow diagrams illustrating a method of displaying intensity-reactive and intensity-nonreactive user interface objects in accordance with some embodiments.
FIGS. 27A1-27A5 are flow diagrams illustrating a method of displaying intensity-reactive and intensity-nonreactive user interface objects in accordance with some embodiments.
FIGS. 27B1-27B3 are flow diagrams illustrating a method of displaying intensity-reactive and intensity-nonreactive user interface objects in accordance with some embodiments.
The methods, devices and GUIs described herein provide visual and/or haptic feedback that makes manipulation of user interface objects more efficient and intuitive for a user.
In some embodiments, in a system where a trackpad or touch-screen display is sensitive to a range of contact intensity that includes more than one or two specific intensity values (e.g., more than a simple on/off, binary intensity determination), the user interface provides responses (e.g., visual and/or tactile cues) that are indicative of the intensity of the contact within the range. This provides a user with a continuous response to the force or pressure of a user's contact, which provides a user with visual and/or haptic feedback that is richer and more intuitive. For example, such continuous force responses give the user the experience of being able to press lightly to preview an operation and/or press deeply to push to a predefined user interface state corresponding to the operation.
In some embodiments, for a device with a touch-sensitive surface that is sensitive to a range of contact intensity, multiple contact intensity thresholds are monitored by the device and different responses are mapped to different contact intensity thresholds.
In some embodiments, for a device with a touch-sensitive surface that is sensitive to a range of contact intensity, the device provides additional functionality by allowing users to perform complex operations with a single continuous contact.
In some embodiments, for a device with a touch-sensitive surface that is sensitive to a range of contact intensity, the device provides additional functionality that complements conventional functionality. For example, additional functions provided by intensity-based inputs (e.g., user interface previews and/or navigation shortcuts provided by light-press and/or deep-press gestures) are seamlessly integrated with conventional functions provided by conventional tap and swipe gestures. A user can continue to use conventional gestures to perform conventional functions (e.g., tapping on an application icon on a home screen to launch the corresponding application), without accidentally activating the additional functions. Yet it is also simple for a user to discover, understand, and use the intensity-based inputs and their added functionality (e.g., pressing on a notification, a contextual content object, a mini application object, a folder icon, a downloading icon, and/or an application icon on a background user interface (e.g., the notification center user interface, the home screen, the widget view, etc.), allows a user to access a subset of content, functionalities, menu options from a corresponding application without having to first launch the corresponding application, and without having to leave the current context (e.g., another application, and/or the background user interface).
A number of different approaches for manipulating user interfaces are described herein. Using one or more of these approaches (optionally in conjunction with each other) helps to provide a user interface that intuitively provides users with additional information and functionality. Using one or more of these approaches (optionally in conjunction with each other) reduces the number, extent, and/or nature of the inputs from a user and provides a more efficient human-machine interface. This enables users to use devices that have touch-sensitive surfaces faster and more efficiently. For battery-operated devices, these improvements conserve power and increase the time between battery charges.
Below,
FIGS. 5A1-5I9 illustrate example user interfaces for interacting with a notification associated with a respective application (e.g., to access a subset of functions and content of the respective application from the notifications without having to first activate the respective application), in accordance with some embodiments.
FIGS. 5J1-5P2 illustrate example user interfaces for displaying a contextual content object (e.g., a mini application object) associated with a respective application (e.g., to access a subset of functions and content of the respective application from the contextual content object without having to first activate the respective application), in accordance with some embodiments.
FIGS. 5Q1-5S5 illustrate user interfaces for interacting with a menu of applications that include an application that is in the process of being downloaded (e.g., providing a menu of options to quickly invoke one of several download-related quick actions with respect to the application that is in the process of being downloaded), in accordance with some embodiments.
FIGS. 5T1-5T15 illustrate user interfaces for interacting with a menu of applications that includes a folder of applications (e.g., selectively providing a menu for quickly launching a respective application with unread notifications from the folder containing multiple applications without having to first open the folder, in accordance with some embodiments.
FIGS. 5U1-5W5 illustrate user interfaces for quickly entering a rename and reconfiguration mode for an application folder (e.g., without having to first open the folder), in accordance with some embodiments.
Below,
Below,
Below,
Below FIGS. 9A1-9A25 illustrate exemplary user interfaces for displaying intensity-reactive and intensity-nonreactive user interface objects, in accordance with some embodiments. FIGS. 24A1-24A3 are flow diagrams illustrating a method of displaying intensity-reactive and intensity-nonreactive user interface objects in accordance with some embodiments. FIGS. 24B1-24B3 are flow diagrams illustrating a method of displaying intensity-reactive and intensity-nonreactive user interface objects in accordance with some embodiments. The user interfaces in FIGS. 9A1-9A25 are used to illustrate the processes in FIGS. 24A1-24A3 and 24B1-24B3.
Below FIGS. 9B1-9B10 illustrate exemplary user interfaces for displaying intensity-reactive and intensity-nonreactive user interface objects, in accordance with some embodiments. FIGS. 27A1-27A5 are flow diagrams illustrating a method of displaying intensity-reactive and intensity-nonreactive user interface objects in accordance with some embodiments. FIGS. 27B1-27B3 are flow diagrams illustrating a method of displaying intensity-reactive and intensity-nonreactive user interface objects in accordance with some embodiments. The user interfaces in FIGS. 9B1-9B10 are used to illustrate the processes in FIGS. 27A1-27A5 and 27B1-27B3.
FIGS. 9C1-9C19 illustrate exemplary user interfaces for displaying control settings interfaces for control functions for remote devices, in accordance with some embodiments.
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact, unless the context clearly indicates otherwise.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Example embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch-screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch-screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a note taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
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 FIG. 1A are implemented in hardware, software, firmware, or a combination thereof, including one or more signal processing and/or application specific integrated circuits.
Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU(s) 120 and the peripherals interface 118, is, optionally, controlled by memory controller 122.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU(s) 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.
In some embodiments, peripherals interface 118, CPU(s) 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication optionally uses any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch-sensitive display system 112 and other input or control devices 116, with peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled with any (or none) of the following: a keyboard, infrared port, USB port, stylus, and/or a pointer device such as a mouse. The one or more buttons (e.g., 208,
Touch-sensitive display system 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch-sensitive display system 112. Touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term “affordance” refers to a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to inputs directed toward the graphical user interface object). Examples of user-interactive graphical user interface objects include, without limitation, a button, slider, icon, selectable menu item, switch, hyperlink, or other user interface control.
Touch-sensitive display system 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch-sensitive display system 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch-sensitive display system 112. In an example embodiment, a point of contact between touch-sensitive display system 112 and the user corresponds to a finger of the user or a stylus.
Touch-sensitive display system 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch-sensitive display system 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch-sensitive display system 112. In an example embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.
Touch-sensitive display system 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen video resolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally makes contact with touch-sensitive display system 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch-sensitive display system 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, haptic feedback module (or set of instructions) 133, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 stores device/global internal state 157, as shown in
Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. In some embodiments, the external port is a Lightning connector that is the same as, or similar to and/or compatible with the Lightning connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif.
Contact/motion module 130 optionally detects contact with touch-sensitive display system 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact (e.g., by a finger or by a stylus), such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts or stylus contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event. Similarly, tap, swipe, drag, and other gestures are optionally detected for a stylus by detecting a particular contact pattern for the stylus.
In some embodiments, detecting a finger tap gesture depends on the length of time between detecting the finger-down event and the finger-up event, but is independent of the intensity of the finger contact between detecting the finger-down event and the finger-up event. In some embodiments, a tap gesture is detected in accordance with a determination that the length of time between the finger-down event and the finger-up event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4 or 0.5 seconds), independent of whether the intensity of the finger contact during the tap meets a given intensity threshold (greater than a nominal contact-detection intensity threshold), such as a light press or deep press intensity threshold. Thus, a finger tap gesture can satisfy input criteria that are configured to be met even when the characteristic intensity of a contact does not satisfy a given intensity threshold. For clarity, the finger contact in a tap gesture typically needs to satisfy a nominal contact-detection intensity threshold, below which the contact is not detected, in order for the finger-down event to be detected. A similar analysis applies to detecting a tap gesture by a stylus or other contact. In cases where the device is configured to detect a finger or stylus contact hovering over a touch sensitive surface, the nominal contact-detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch sensitive surface.
The same concepts apply in an analogous manner to other types of gestures. For example, a swipe gesture, a pinch gesture, a depinch gesture, and/or a long press gesture are optionally detected based on the satisfaction of criteria that are independent of intensities of contacts included in the gesture. For example, a swipe gesture is detected based on an amount of movement of one or more contacts; a pinch gesture is detected based on movement of two or more contacts towards each other; a depinch gesture is detected based on movement of two or more contacts away from each other; and a long press gesture is detected based on a duration of the contact on the touch-sensitive surface with less than a threshold amount of movement. As such, the statement that gesture recognition criteria are configured to be met when a contact in a gesture has an intensity below a respective intensity threshold means that the gesture recognition criteria are capable of being satisfied even if the contact(s) in the gesture do not reach the respective intensity threshold. It should be understood, however, that this statement does not preclude the gesture recognition criteria from being satisfied in circumstances where one or more of the contacts in the gesture do reach or exceed the respective intensity threshold. For example, a tap gesture is configured to be detected if the finger-down and finger-up event are detected within a predefined time period, without regard to whether the contact is above or below the respective intensity threshold during the predefined time period, and a swipe gesture is configured to be detected if the contact movement is greater than a predefined magnitude, even if the contact is above the respective intensity threshold at the end of the contact movement.
Contact intensity thresholds, duration thresholds, and movement thresholds are, in some circumstances, combined in a variety of different combinations in order to create heuristics for distinguishing two or more different gestures directed to the same input element or region so that multiple different interactions with the same input element are enabled to provide a richer set of user interactions and responses. The statement that a particular set of gesture recognition criteria are configured to be met when a contact in a gesture has an intensity below a respective intensity threshold does not preclude the concurrent evaluation of other intensity-dependent gesture recognition criteria to identify other gestures that do have a criteria that is met when a gesture includes a contact with an intensity above the respective intensity threshold. For example, in some circumstances, first gesture recognition criteria for a first gesture—which are configured to be met when a gesture has an intensity below a respective intensity threshold—are in competition with second gesture recognition criteria for a second gesture—which are dependent on the gesture reaching the respective intensity threshold. In such competitions, the gesture is, optionally, not recognized as meeting the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are met first. For example, if a contact reaches the respective intensity threshold before the contact moves by a predefined amount of movement, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves by the predefined amount of movement before the contact reaches the respective intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such circumstances, the first gesture recognition criteria for the first gesture are still configured to be met when a contact in the gesture has an intensity below the respective intensity because if the contact stayed below the respective intensity threshold until an end of the gesture (e.g., a swipe gesture with a contact that does not increase to an intensity above the respective intensity threshold), the gesture would have been recognized by the first gesture recognition criteria as a swipe gesture. As such, particular gesture recognition criteria that are configured to be met when an intensity of a contact remains below a respective intensity threshold will (A) in some circumstances ignore the intensity of the contact with respect to the intensity threshold (e.g. for a tap gesture) and/or (B) in some circumstances still be dependent on the intensity of the contact with respect to the intensity threshold in the sense that the particular gesture recognition criteria (e.g., for a long press gesture) will fail if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognize an input as corresponding to an intensity-dependent gesture before the particular gesture recognition criteria recognize a gesture corresponding to the input (e.g., for a long press gesture that is competing with a deep press gesture for recognition).
Graphics module 132 includes various known software components for rendering and displaying graphics on touch-sensitive display system 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing, to camera 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 includes executable instructions to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers and/or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, Apple Push Notification Service (APNs) or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 146, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (in sports devices and smart watches); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.
In conjunction with touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, and/or delete a still image or video from memory 102.
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 includes executable instructions to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch-sensitive display system 112, or on an external display connected wirelessly or via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes executable instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen 112, or on an external display connected wirelessly or via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video.
Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display system 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display system 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views, when touch-sensitive display system 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (i.e., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver module 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 includes one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170, and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event 187 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display system 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 186 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display system 112, when a touch is detected on touch-sensitive display system 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event 187 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module 145. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input-devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 optionally also includes one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch-screen display.
In some embodiments, device 100 includes the touch-screen display, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In some embodiments, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch-sensitive display system 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above identified elements in
Attention is now directed towards embodiments of user interfaces (“UI”) that are, optionally, implemented on portable multifunction device 100.
It should be noted that the icon labels illustrated in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures, etc.), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse based input or a stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
As used herein, the term “focus selector” is an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector,” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact or a stylus contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average or a sum) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be readily accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch-screen display can be set to any of a large range of predefined thresholds values without changing the trackpad or touch-screen display hardware. Additionally, in some implementations a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second intensity threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more intensity thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective option or forgo performing the respective operation) rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact transitioning from a start location and reaching an end location (e.g., a drag gesture), at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location may be based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm may be applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The user interface figures described herein optionally include various intensity diagrams that show the current intensity of the contact on the touch-sensitive surface relative to one or more intensity thresholds (e.g., a contact detection intensity threshold IT0, a light press intensity threshold ITL, a deep press intensity threshold ITD (e.g., that is at least initially higher than ITL), and/or one or more other intensity thresholds (e.g., an intensity threshold ITH that is lower than ITL)). This intensity diagram is typically not part of the displayed user interface, but is provided to aid in the interpretation of the figures. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold IT0 below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
In some embodiments, the response of the device to inputs detected by the device depends on criteria based on the contact intensity during the input. For example, for some “light press” inputs, the intensity of a contact exceeding a first intensity threshold during the input triggers a first response. In some embodiments, the response of the device to inputs detected by the device depends on criteria that include both the contact intensity during the input and time-based criteria. For example, for some “deep press” inputs, the intensity of a contact exceeding a second intensity threshold during the input, greater than the first intensity threshold for a light press, triggers a second response only if a delay time has elapsed between meeting the first intensity threshold and meeting the second intensity threshold. This delay time is typically less than 200 ms in duration (e.g., 40, 100, or 120 ms, depending on the magnitude of the second intensity threshold, with the delay time increasing as the second intensity threshold increases). This delay time helps to avoid accidental deep press inputs. As another example, for some “deep press” inputs, there is a reduced-sensitivity time period that occurs after the time at which the first intensity threshold is met. During the reduced-sensitivity time period, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep press inputs. For other deep press inputs, the response to detection of a deep press input does not depend on time-based criteria.
In some embodiments, one or more of the input intensity thresholds and/or the corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, application running, rate at which the intensity is applied, number of concurrent inputs, user history, environmental factors (e.g., ambient noise), focus selector position, and the like. Example factors are described in U.S. patent application Ser. Nos. 14/399,606 and 14/624,296, which are incorporated by reference herein in their entireties.
For example,
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold ITL to an intensity between the light press intensity threshold ITL and the deep press intensity threshold ITD is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold ITD to an intensity above the deep press intensity threshold ITD is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold IT0 to an intensity between the contact-detection intensity threshold IT0 and the light press intensity threshold ITL is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold IT0 to an intensity below the contact-detection intensity threshold IT0 is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments IT0 is zero. In some embodiments, IT0 is greater than zero. In some illustrations a shaded circle or oval is used to represent intensity of a contact on the touch-sensitive surface. In some illustrations, a circle or oval without shading is used represent a respective contact on the touch-sensitive surface without specifying the intensity of the respective contact.
In some embodiments, described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., the respective operation is performed on a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., the respective operation is performed on an “up stroke” of the respective press input).
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., the respective operation is performed on an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the description of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. As described above, in some embodiments, the triggering of these responses also depends on time-based criteria being met (e.g., a delay time has elapsed between a first intensity threshold being met and a second intensity threshold being met).
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on an electronic device, such as portable multifunction device 100 or device 300, with a display, a touch-sensitive surface, and one or more sensors to detect intensities of contacts with the touch-sensitive surface.
For convenience of explanation, some of the embodiments will be discussed with reference to operations performed on a device with a touch-sensitive display system 112. In such embodiments, the focus selector is, optionally: a respective finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., a centroid of a respective contact or a point associated with a respective contact), or a centroid of two or more contacts detected on the touch-sensitive display system 112. However, analogous operations are, optionally, performed on a device with a display 450 and a separate touch-sensitive surface 451 in response to detecting the contacts on the touch-sensitive surface 451 while displaying the user interfaces shown in the figures on the display 450, along with a focus selector.
FIGS. 5A1-519 illustrate example user interfaces for interacting with a notification associated with a respective application (e.g., to access a subset of functions and content of the respective application from the notifications without having to first activate the respective application), in accordance with some embodiments. An input on a notification either launches the respective application associated with the notification or causes an expanded version of the notification to be displayed to provide a subset of content and/or functionality from the respective application to the user without first launching the application, in accordance with some embodiments.
FIGS. 5A1-5A6 illustrate various example user interfaces on which notifications are presented in accordance with some embodiments.
FIG. 5A1 illustrates wake screen user interface 5002 that is displayed when device 100 is activated from a screen-off state (e.g., a sleep state) to a screen-on state (e.g., a wake state) in an unlocked mode (e.g., as indicated by the “unlocked” indicator 5004). A number of notifications (e.g., notification 5006 for a calendar invitation, notification 5008 for a new instant message, and notification 5010 for a voicemail message) are displayed on the wake screen user interface 5002. Each notification includes notification content (e.g., an excerpt from a communication, a summary of an event or communication, etc.) and identifying information that identifies a respective application that corresponds to the notification.
FIG. 5A2 illustrates wake screen user interface 5012 that is displayed when device 100 is activated from a screen-off state (e.g., a sleep state) to a screen-on state (e.g., a wake state) in an locked mode (e.g., as indicated by the “locked” indicator 5014). A number of notifications (e.g., notification 5016 for a calendar invitation, notification 5018 for a new instant message, and notification 5020 for a voicemail message) are displayed on the wake screen user interface 5012. Each notification includes notification content (e.g., an excerpt from a communication, a summary of an event or communication, etc.) and identifying information that identifies a respective application that corresponds to the notification. In some embodiments, device 100 displays a first version of a notification (e.g., notification 5006, or notification 5008) with more notification content when the device is in the unlocked mode (as shown in FIG. 5A1), and displays a second version of the notification (e.g., notification 5016, or notification 5018) with less notification content when the device is in the locked mode (e.g., as shown in FIG. 5A2).
FIG. 5A3 illustrates a notification (e.g., banner 5022 for a new e-mail message) that is displayed over home screen user interface 5024 (e.g., analogous to home screen user interface 400 shown in
FIG. 5A4 illustrates notification screen 5026 (e.g., a notification center user interface) displayed while device 100 is in a locked mode (e.g., as indicated by “locked” indicator 5014). A number of notifications (e.g., notifications 5028 and 5030 for two new instant messages, notification 5032 for a new voicemail, and notification 5034 for a new email message) are displayed in a vertical stack on notification screen 5026.
FIG. 5A5 illustrates notification screen 5036 (e.g., a notification center user interface) displayed while device 100 is in an unlocked mode (e.g., as indicated by “unlocked” indicator 5004). A number of notifications (e.g., notifications 5038 and 5040 for two new instant messages, notification 5042 for a new voicemail, and notification 5044 for a new email message) are displayed in a vertical stack on notification screen 5036. Each notification includes notification content (e.g., an excerpt from a communication, a summary of an event or communication, etc.) and identifying information that identifies a respective application that corresponds to the notification. In some embodiments, device 100 displays a first version of a notification (e.g., notification 5028, notification 5030, or notification 5034) with less notification content when the device is in the locked mode (e.g., as shown in FIG. 5A4) and displays a second version of a notification (e.g., notification 5038, notification 5040, or notification 5044) with more notification content when the device is in the unlocked mode (as shown in FIG. 5A5). In FIG. 5A5, notification 5038 for an instant message (displayed while the device is in the unlocked mode) includes a thumbnail image 5046 for an image attachment included in the instant message, in addition to textual content of the instant message.
FIG. 5A6 illustrates a notification (e.g., alert 5048) that is displayed over a user interface of an application (e.g., application user interface 5050). An alert is a type of notification that requests a user to perform an action (e.g., to confirm a ride request, or cancel the ride request). An alert is also used sometimes when user's immediate attention is requested (e.g., when a failure has been detected (e.g., failure to connect to a peripheral device or a server), or when a task requested by a user has not been successfully completed (e.g., failure to send a message)).
FIGS. 5B1-5B4 illustrate a process for launching an application from a notification associated with the application (e.g., in response to a tap input on the notification), in accordance with some embodiments.
FIG. 5B1 illustrates notification screen 5026 displaying a number of notifications (e.g., notifications 5028, 5030, 5032, and 5034) while device 100 is in the locked state.
FIG. 5B2 illustrates that a contact (e.g., contact 5052) is detected on notification 5028; and in response to the detection of the contact, notification 5028 is selected.
FIGS. 5B3-5B4 illustrate that, when a characteristic intensity of contact 5052 (as indicated by the “intensity of contact” in the intensity meter illustrated next to device 100 in the Figures) does not increase above a predetermined threshold intensity (e.g., the hint intensity threshold ITH) before lift-off of the contact is detected, device 100 initiates a process to launch an instant messaging application (e.g., the Messages app) corresponding to notification 5028.
FIG. 5B3 illustrates that, upon detecting lift-off of contact 5052, device 100 darkens notification screen 5026 and displays an authentication user interface (e.g., password user interface 5054) over the darkened notification screen 5026.
FIG. 5B4 illustrates that, upon receiving the correct authentication information from password user interface 5054, device 100 is unlocked. In the unlocked mode, device 100 launches the Messages application and displays a user interface of the Messages application (e.g., conversation screen 5056). The user interface (e.g., conversation screen 5056) includes the content of the notification (e.g., message text (e.g., text of message 5062), sender name “Alice”) and additional content (e.g., one or more previous messages between Alice and the user (e.g., message 5060), and an image (e.g., image 5058) that corresponds to an image attachment included in message 5062)).
FIGS. 5C1-5C6 illustrate a process for displaying a second version of a notification with expanded notification content in response to an input (e.g., a press input) on a first version of the notification with standard notification content, in accordance with some embodiments.
FIG. 5C1 shows the same notification screen as FIG. 5B1. In FIG. 5C1, notification screen 5026 displaying a number of notifications (e.g., notifications 5028, 5030, 5032, and 5034) while device 100 is in the locked state.
FIG. 5C2 illustrates that a contact (e.g., contact 5064) is detected on notification 5028, and in response to the detection of the contact, notification 5028 is selected.
FIGS. 5C3 and 5C4 illustrate that, once the characteristic intensity of contact 5064 increases above a predetermined threshold intensity (e.g., a hint intensity threshold ITH), device 100 applies dynamic changes to the user interface in accordance with a current value of the characteristic intensity. For example, device 100 dynamically increases (or decreases) the amount of blurring and darkening applied to notification screen 5026 in accordance with the increase (or decrease) in the characteristic intensity of contact 5064, while notification 5028 is overlaid on top of the blurred and darkened notification screen 5026. As shown in FIGS. 5C3 and 5C4, as contact intensity is increased within the range ITH and a first higher intensity threshold (e.g., a light press intensity threshold ITL), the amount of blurring and darkening applied to notification screen 5026 is increased accordingly. Before the characteristic intensity of contact 5064 crosses the first higher intensity threshold (e.g., ITL), lift-off of the contact returns the user interface to its original state (e.g., the state shown in FIG. 5C1).
FIG. 5C5 illustrates that, once the characteristic intensity of contact 5064 exceeds the first intensity threshold (e.g., light press intensity threshold ITL), an expanded version of the notification (e.g., notification 5066) is displayed over the blurred and darkened notification screen 5026. In addition, in some embodiments, the appearance of notification screen 5026 is maintained (e.g., does not change in accordance with the current characteristic intensity of contact 5064) once the characteristic intensity has exceeded the first intensity threshold for the first time. As shown in FIG. 5C5, the expanded version of the notification (e.g., notification 5066) includes content from the initially displayed version of the notification (e.g., notification 5028) and additional functions (e.g., selectable options for performing actions with respect to the notification or the application) and/or content that is not included in the initially displayed version of the notification. For example, notification 5066 includes “Reply” button 5068 for launching a “Reply” user interface for composing a reply to the message represented in the notification, and “Delete” button 5070 for deleting the message represented in the notification. Notification 5066 optionally includes a preview of an image attachment from the message represented in the notification.
FIG. 5C6 illustrates that the expanded notification (e.g., notification 5066) remains displayed on the blurred and darkened notification screen after lift-off of contact 5064 is detected. Another input (e.g., a tap input) subsequently detected on the expanded notification (e.g., notification 5066) outside areas occupied by buttons 5068 and 5070 starts a process for launching the Messages application (e.g., as illustrated in FIGS. 5B3 and 5B4).
FIGS. 5D1-5E4 illustrate a process in which movement of the contact beyond a threshold distance cancels the display of expanded notification, in accordance with some embodiments.
FIG. 5D1 shows the same notification screen as FIGS. 5B1 and 5C1. In FIG. 5D1, notification screen 5026 displaying a number of notifications (e.g., notifications 5028, 5030, 5032, and 5034) while device 100 is in the locked state.
FIG. 5D2 illustrates that a contact (e.g., contact 5072) is detected on notification 5028, and in response to the detection of the contact, notification 5028 is selected.
FIGS. 5D3 and 5D4 illustrate that, once the characteristic intensity of contact 5072 increases above a predetermined threshold intensity (e.g., a hint intensity threshold ITH), device 100 applies dynamic changes to the user interface in accordance with a current value of the characteristic intensity. For example, device 100 dynamically increases (or decreases) the amount of blurring and darkening applied to notification screen 5026 in accordance with the increase (or decrease) in the characteristic intensity of contact 5072, while notification 5028 is overlaid on top of the blurred and darkened notification screen 5026. As shown in FIGS. 5D3 and 5D4, as contact intensity is increased within the range ITH and a first higher intensity threshold (e.g., a light press intensity threshold ITL), the amount of blurring and darkening applied to notification screen 5026 is increased accordingly. Before the characteristic intensity of contact 5072 crosses the first intensity threshold, lift-off of the contact returns the user interface to its original state (e.g., the state shown in FIG. 5D1).
FIG. 5D5 illustrates that, before the characteristic intensity of contact 5072 crosses the first intensity threshold, movement of contact 5072 is detected. When the amount of movement is less than a first movement threshold (e.g., 10 pixels), device 100 continues to dynamically vary the amount of blurring and darkening applied to notification screen 5026 in accordance with a current value of the characteristic intensity of contact 5072. For example, the amount of blurring and darkening is greater in the notification screen 5026 in FIG. 5D5 as compared to the notification screen 5026 in FIG. 5D4.
FIG. 5D6 illustrates that, as soon as the amount of movement made by contact 5072 is more than the first movement threshold, device cancels the hint effects (e.g., the blurring and darkening of notification screen 5026) provided in accordance the current contact intensity, and notification screen 5026 is restored to its original clarity and brightness. In addition, device 100 recognizes the gesture provided by contact 5072 as a drag gesture. Accordingly, device 100 moves notification 5028 in accordance with movement of contact 5072 (e.g., notification 5072 is dragged to the left by contact 5072). As shown in FIG. 5D6, although intensity of contact 5072 is greater than the first intensity threshold (e.g., ITL), an expanded version of the notification is not presented (e.g., in contrast to the case illustrated in FIG. 5C5).
FIG. 5D6 illustrates that, as contact 5072 continues to move, notification 5028 is dragged further to the left and a quick response action affordance (e.g., “Delete” affordance 5074) is revealed from behind notification 5028.
As illustrated in FIGS. 5D6-5D7, once a threshold amount of movement by contact 5072 has been detected, the user interface does not respond to further changes in the characteristic intensity of contact 5072 and/or the characteristic intensity meeting the first intensity threshold.
FIG. 5D8 shows that, after the quick response action affordance (“Delete” affordance 5074) has been revealed, the quick response action affordance, and optionally, notification 5028 along with the rest of notification screen 5026 remains displayed after lift-off of contact 5072 is detected. Selection of “Delete” affordance 5074 by another input (e.g., a tap input) causes deletion of notification 5028 and/or the message represented in notification 5028.
Although not illustrated in FIGS. 5D5-5D8, movement of contact 5072 in the reverse direction (e.g., from left to right) after dragging notification 5028 and revealing “Delete” affordance 5074 returns notification 5028 to its original location and hides “Delete” affordance 5074 again. In addition, although not illustrated in FIGS. 5D5-5D8, movement of contact 5072 in the reverse direction (e.g., from left to right) that is started while notification 5028 is at its original location drags notification 5072 to the right and reveals a different quick response action affordance (e.g., a “Flag” affordance, or a “Reply” affordance).
FIGS. 5E1-5E4 illustrates movement of contact 5072 in a vertical direction. FIG. 5E1 continues from FIG. 5D3 and is the same as FIG. 5D4.
In FIGS. 5E1-5E2, before the characteristic intensity of contact 5072 crosses the first intensity threshold, movement of contact 5072 in the vertical direction is detected (e.g., as shown in FIG. 5E2). When the amount of movement is less than a second movement threshold (e.g., 10 pixels or another threshold number of pixels), device 100 continues to dynamically vary the amount of blurring and darkening of notification screen 5026 in accordance with a current value of the characteristic intensity of contact 5072.
FIG. 5E3 illustrates that, as soon as the amount of movement made by contact 5072 is more than the second movement threshold, device cancels the hint effects (e.g., the blurring and darkening of notification screen 5026) provided in accordance the current contact intensity, and notification screen 5026 is restored to its original clarity and brightness. In addition, device 100 recognizes the gesture provided by contact 5072 as a scroll gesture. Accordingly, device 100 scrolls notification screen 5026 in accordance with movement of contact 5072 (e.g., notification 5028 along with other notifications in notification screen 5026 are scrolled upward by contact 5072). As shown in FIG. 5E3, although intensity of contact 5072 is greater than the first intensity threshold (e.g., ITL), an expanded version of the notification is not presented (e.g., in contrast to the case illustrated in FIG. 5C5).
As illustrated in FIGS. 5E1-5E3, once a threshold amount of movement has been detected, the user interface does not respond to further changes in the characteristic intensity of contact 5072 and/or the characteristic intensity meeting the first intensity threshold.
FIG. 5E4 shows that, after notification screen 5026 has been scrolled, notification screen 5026 remains in the scrolled state after lift-off of contact 5072 is detected.
Although not illustrated in FIGS. 5E1-5E4, movement of contact 5072 in the reverse direction (e.g., in the downward direction) after scrolling the notification screen upward scrolls the notification screen downward again.
In addition, in some embodiments (not shown in FIGS. 5E1-5E4), instead of scrolling the entire notification screen, movement of contact 5072 scrolls the notification content within notification 5028. In some embodiments (not shown in FIGS. 5E1-5E4), scrolling of notification content is prioritized before scrolling of the notification screen. In other words, movement of the contact scrolls the notification content first, and if movement of the contact continues when no more notification content can be scrolled in accordance with the movement of the contact, then scrolling of the notification screen is started.
In some embodiments (not shown in FIGS. 5E1-5E4), when the touch-down location of a contact is within a notification, movement of the contact only scrolls the notification content. In such embodiments, the scrolling of the notification screen occurs when the initial touch-down location of a contact is outside of the content region of a notification (e.g., outside of a notification, on the header portion of a notification, or outside or straddling the boundary of the notification screen) and the contact moves vertically within the notification screen.
Although the examples shown in FIGS. 5D1-5E4 are illustrated with a notification shown when device 100 is in a locked mode, cancelation of the hint states (e.g., the blurring and darkening of the background user interface) and dragging of the notification and/or scrolling of the background user interface in accordance with movement of the contact applies to a notification (e.g., a notification that includes restricted notification content) that is shown when device 100 is in an unlocked mode as well.
FIGS. 5F1-5F7 illustrate a process for displaying a second version of a notification with expanded notification content in response to an input (e.g., a press input) on a first version of the notification with standard notification content, in accordance with some embodiments. In contrast to the process shown in
In FIG. 5F1, notification screen 5036 displays a number of notifications (e.g., notifications 5038, 5040, 5042, and 5044) while device 100 is in the unlocked state.
FIG. 5F2 illustrates that a contact (e.g., contact 5076) is detected on notification 5038; and in response to the detection of the contact, notification 5038 is selected.
FIG. 5F3 illustrates that, once the characteristic intensity of contact 5076 increases above a predetermined threshold intensity (e.g., a hint intensity threshold ITH), device 100 applies dynamic changes to the user interface in accordance with a current value of the characteristic intensity. For example, device 100 dynamically increases (or decreases) the amount of blurring and darkening applied to notification screen 5036 in accordance with the increase (or decrease) in the characteristic intensity of contact 5076, while notification 5038 is overlaid on top of the blurred and darkened notification screen 5036. As contact intensity is increased within the range ITH and a first higher intensity threshold (e.g., a light press intensity threshold ITL), the amount of blurring and darkening applied to notification screen 5036 is increased accordingly. Before the characteristic intensity of contact 5076 crosses the first intensity threshold, lift-off of the contact returns the user interface to its original state (e.g., the state shown in 5F1).
FIG. 5F4 illustrates that, once the characteristic intensity of contact 5076 exceeds the first intensity threshold (e.g., light press intensity threshold ITL), an expanded version of the notification (e.g., notification 5078) is displayed over the blurred and darkened notification screen 5036. In addition, in some embodiments, the appearance of notification screen 5036 is maintained (e.g., does not change in accordance with the current characteristic intensity of contact 5076) once the characteristic intensity has exceeded the first intensity threshold for the first time.
As shown in FIG. 5F4, the expanded version of the notification (e.g., notification 5078) includes content (e.g., message text (e.g., text of message 5062), sender name “Alice”) from the initially displayed version of the notification (e.g., notification 5038) and additional functions (e.g., selectable options for performing actions with respect to the notification or the application) and/or content that is not included in the initially displayed version of the notification. For example, notification 5078 includes “Reply” button 5082 for launching a “Reply” user interface for composing a reply to the message represented in the notification. Notification 5078 further includes one or more previous messages between Alice and the user (e.g., message 5060), and an image (e.g., image 5058) that corresponds to thumbnail 5046 included in notification 5028 (image 5058 is an attachment included in message 5062))). Notification 5078 further includes header region 5080 that is distinct from the content region (e.g., the region displaying the conversation log) and the control region (e.g., the region displaying the control affordances (e.g., “Reply” affordance 5082)). Header region 5080 includes information identifying the Messages application (e.g., the application icon and application name) and information identifying the sender of the message (e.g., avatar 5084 of the sender “Alice”).
Although not shown in FIGS. 5F1-5F5, the expanded notification (e.g., notification 5078) remains displayed on the blurred and darkened notification screen after lift-off of contact 5076 is detected. Another input (e.g., a tap input) subsequently detected on the expanded notification (e.g., notification 5078) outside areas occupied by affordance 5082 (e.g., a tap input on the notification content region or the header region) launches the Messages application (e.g., as shown in FIG. 5B4).
FIGS. 5F5-5F7 illustrate that, a second press input by the same contact (e.g., contact 5076) before liftoff, on Reply affordance 5082, activates Reply affordance 5082 and causes a reply user interface to be displayed. FIG. 5F5 illustrates that, before lift-off, contact 5078 moves from its original location to a location on Reply affordance 5082. FIG. 5F6 illustrates that, while contact 5078 is at a location on Reply affordance 5082, an increase in the characteristic intensity of contact 5078 is detected, and the characteristic intensity exceeds a respective intensity threshold (e.g., the light press intensity threshold ITL). FIG. 5F5 also illustrates that, before the characteristic intensity of contact 5076 exceeds the respective intensity threshold, the characteristic intensity of contact 5076 was below the respective intensity threshold (e.g., the characteristic intensity of contact 5076 is below ITL during movement of contact 5076 from its original location to the location on Reply affordance 5082). Contact 5082 does not move by more than a threshold amount (e.g., is substantially stationary) when an increase in intensity above the respective intensity threshold is detected (in other words, the second press input is detected while contact 5076 is substantially stationary).
FIG. 5F7 illustrates that, upon lift-off of contact 5076, Reply affordance 5082 is activated, and a reply user interface (e.g., reply user interface 5090) is displayed. In some embodiments, the reply user interface (e.g., reply user interface 5090) is displayed over the blurred and darkened notification screen 5036. In some embodiments, the reply user interface is updated in real-time (e.g., message bubble 5088 indicates that Alice is composing a message). The reply user interface includes soft keyboard 5092 and message input field for displaying a draft message entered by the user (e.g., “Oh?”).
FIGS. 5G1-5G3 illustrate that a tap input detected outside of expanded notification 5078 dismisses notification 5078 (and its shorter version—notification 5038). FIG. 5G1 shows expanded notification 5078 overlaid on blurred and darkened notification screen 5036, e.g., following liftoff of contact 5076 from the state shown in FIG. 5F4.
FIG. 5G2 illustrates that new contact 5096 is detected outside of expanded notification 5078. FIG. 5G3 illustrates that, upon lift-off of contact 5096, notification screen 5036 is restored to its original clarity and brightness. In addition, notification 5038 and expanded notification 5078 are dismissed from the user interface and are no longer displayed. Other notifications (e.g., notifications 5040, 5042, and 5044) that have not been dismissed are displayed in restored notification screen 5036.
FIGS. 5H1-5H2 illustrate that, after the state shown in FIG. 5G1, a tap input detected within expanded notification 5078 (e.g., a tap input detected within the content region of expanded notification 5078) launches the Messages application.
As shown in FIG. 5H1, new contact 5098 is detected within the content region of expanded notification 5078. FIG. 5H2 shows that, upon lift-off of contact 5098, device 100 launches the Messages application, and a user interface of the Messages application (e.g., application user interface 5100) replaces expanded notification 5078 and notification screen 5036 on the touch screen display 112. The tap input on the expanded notification launches the Messages application to a user interface in the Messages application that corresponds to the notification content (e.g., a user interface that includes the conversation log for message communications between the user and the sender “Alice”), rather than a default user interface that is displayed when the Messages application is launched by a tap input on the Messages application icon on the home screen (e.g., to the last user interface that was shown when the user previously exited the Messages application or the user interface that includes an index of conversations the user has with other users).
FIGS. 5I1-5I9 illustrate another example in which an expanded notification is presented in response to a press input detected on a notification for a ride sharing application, and provides a subset of content and functions from the ride sharing application without first launching the ride sharing application.
In FIG. 5I1, a first version of a notification (e.g., banner 5104) is displayed over a background user interface (e.g., email inbox user interface 5102 of an e-mail application).
FIG. 5I2 illustrate that, contact 5106 is detected on the first version of the notification (e.g., banner 5104), and when a characteristic intensity of contact 5106 exceeds a hint threshold ITH, a deemphasizing visual effect (e.g., blurring and darkening of the background user interface (e.g., user interface 5102)) is applied to the background user interface, while notification 5104 is visually lifted off of the background user interface without the deemphasizing visual effect. FIG. 5I3 illustrates that, as the characteristic intensity of contact 5106 increases (or decreases) within the range ITH and ITL, the amount of deemphasizing visual effect is varied dynamically (e.g., increased (or decreased)) in accordance with the change in the characteristic intensity of contact 5106. By applying the deemphasizing visual effect, the user is provided a hint for the alternative manner by which a subset of content and functions of the application can be accessed without leaving the current context.
FIG. 5I3 illustrates that, when the characteristic intensity of contact 5106 exceeds the first intensity threshold ITL, an expanded version of the notification (e.g., expanded notification 5108) is displayed over the deemphasized background user interface (e.g., application user interface 5102). As shown in FIG. 5I3, expanded notification 5108 includes a header portion 5110 that includes information identifying a corresponding application associated with the notification (e.g., application icon and application name of a ride sharing application “Rides”). Expanded notification 5108 also includes a content region (e.g., content region 5112) that displays notification content (e.g., text and graphics related to the subject matter of the notification). The notification content shown in the expanded version of the notification includes content that is not displayed in the initially displayed version of the notification (e.g., map 5114 and the additional details regarding the ride provider were not included in notification 5104).
In some embodiments, the content included in expanded notification 5108 is dynamically updated. For example, the location of the car icon 5116 in map 5114 indicates the real-time location of the car that has accepted the ride request, and is updated constantly while expanded notification 5108 is displayed on device 100.
In some embodiments, content region 5112 in expanded notification 5108 is scrollable. FIGS. 5I5-516 illustrate that one or more scroll inputs (e.g., provided by contacts 5120 and 5126 that are within the content region and moving upward) cause the content region to scroll upward to reveal additional content and a control region including one or more control affordances (e.g., control affordances 5122, 5124, 5128 and 5130).
FIG. 5I7 illustrates that update information regarding arrival of the ride is received, and a pop-up banner alert 5132 is displayed within expanded notification 5108. In addition, car icon 5116 indicates the current location of the driver in map 5114.
FIGS. 5I8 and 5I9 illustrate that a tap input (e.g., by contact 5134) is detected on control affordance 5122 for initiating a call to the driver of the ride (e.g., as shown in FIG. 5I8), and in response to the tap input, device 100 initiates a call to the driver of the ride, and expanded notification 5108 displays a call user interface 5136 during the call. Control affordance 5122 changes its appearance to indicate that a call is in progress once the call is connected.
Although not shown in FIGS. 5I1-5I9, a tap input detected within the content region of expanded notification 5108 (e.g., outside of any of the control affordances) launches the ride sharing application and a user interface of the ride sharing application replaces the display of expanded notification 5108 and the background user interface 5102. In addition, a tap input detected outside of expanded notification 5108 dismisses the notification (e.g., both notification 5104 and expanded notification 5108 are no longer displayed) and the background user interface (e.g., application user interface 5102) is restored to its original brightness and clarity.
FIGS. 5J1-5P2 illustrate example user interfaces for displaying a contextual content object (e.g., a mini application object) associated with a respective application (e.g., to provide access to a subset of functions and content of the respective application from the contextual content object without having to first activate the respective application), in accordance with some embodiments. The contextual content object is provided concurrently with a menu of selectable options for activating one or more functions of the respective application. The contextual content object responds to user inputs for displaying more information or functions from the respective application without launching the application, in accordance with some embodiments.
FIGS. 5J1-5J2 illustrates a process for launching an application by a tap input on an application icon in a menu of applications, in accordance with some embodiments.
In FIG. 5J1, a user interface (e.g., home screen 5202) includes an array of application icons that represent different applications that are installed on device 100. A contact (e.g., contact 5204) is detected on one of the application icons (e.g., application icon 424 associated with the Messages application), and the application icon is selected when the characteristic intensity of contact 5204 is above the detection threshold intensity IT0 and below the hint intensity threshold ITH.
FIG. 5J2 illustrates that, upon lift-off of contact 5204, device 100 launches the Messages application and replaces display of the home screen 5202 with a user interface of the Messages application (e.g., user interface 5208 that displays a listing of the user's contacts with whom the user has had previous conversations in the Messages application (e.g., a listing of conversations the user has had with others in the Messages application)).
FIGS. 5K1-5K4 illustrate a process in which instead of a tap input, a press input is detected on the Messages application icon, and the press input causes a contextual content object and a menu of options to be displayed, instead of launching the Messages application.
In FIG. 5K1, home screen 5202 is displayed. A contact (e.g., contact 5206) is detected on one of the application icons (e.g., application icon 424 associated with the Messages application), and the application icon is selected when the characteristic intensity of contact 5206 is above the detection threshold intensity IT0 and below the hint intensity threshold ITH.
FIG. 5K2-5K3 illustrate that, once the characteristic intensity of contact 5206 increases above a predetermined threshold intensity (e.g., the hint intensity threshold ITH), device 100 applies dynamic changes to the user interface in accordance with a current value of the characteristic intensity. For example, device 100 dynamically increases (or decreases) the amount of blurring and darkening applied to home screen 5202 in accordance with the increase (or decrease) in the characteristic intensity of contact 5206, while application icon 424 is overlaid on top of the blurred and darkened home screen 5202. In addition, a menu platter (e.g., platter 5208) emerges from between application icon 424 and home screen 5202, and the size of the platter changes (e.g., grows or shrinks) in accordance with the changes in the characteristic intensity of contact 5206. As shown in FIGS. 5K2 and 5K3, as contact intensity is increased within the range ITH and a first higher intensity threshold (e.g., the light press intensity threshold ITL), the amount of blurring and darkening applied to home screen 5202 is increased accordingly, and the size of platter 5208 is also increased accordingly. Before the characteristic intensity of contact 5206 crosses the first intensity threshold, lift-off of the contact returns the user interface to its original state (e.g., the home screen shown in 5K1 without the selection of application icon 424).
FIG. 5K4 illustrates that, once the characteristic intensity of contact 5206 exceeds the first intensity threshold (e.g., the light press intensity threshold ITL), a contextual content object (e.g., mini application object or widget 5210) associated with the Messages application is displayed over the blurred and darkened home screen 5202. The contextual content object includes contextually selected content that has been automatically selected based on a current context of device 100. For example, mini application object 5210 is a widget that includes a grid of several people that are selected based on the number of messages that have been sent between the user and the user's contacts (e.g., mini application object 5210 includes avatars or aliases (e.g., avatars 5224, 5226, 5228, and 5230) of four people with whom the user has had the highest numbers of instant messaging communications during the past week). In some embodiments, a respective avatar or alias also includes a badge (e.g., badge 5232 and 5234) that indicates the number of unread instant messaging communications from the person represented by the respective avatar or alias. For example, badge 5232 indicates that there are eight unread messages from Issac, and badge 5234 indicates that there are four unread messages from Miles. The badges are updated while mini application object 5210 is displayed, when new messages from the people represented in the mini application object 5210 are received at device 100.
In addition to contextually selected content, mini application object 5210 also includes an “add widget” affordance (e.g., affordance 5222) for adding the mini application object 5210 to another user interface (e.g., a mini application object screen or widget screen) that is configured to host a number of mini application objects that are associated with different applications installed on device 100. In some embodiments, affordance 5222 is only displayed if mini application object 5210 does not already exist in the user interface (e.g., a mini application object screen or widget screen) that is configured to host a number of mini application objects that are associated with different applications installed on device 100.
In addition, a menu of selectable options (e.g., menu 5212) is displayed concurrently with the contextual content object (e.g., mini application object 5210). The menu of selectable options includes options (e.g., options 5214, 5216, 5218, 5220) that when activated, are configured to launch the Messages application to a respective user interface of the Messages application for performing a respective function associated with the Messages application. For example, selection of option 5214 causes a new messages user interface to be displayed for the user to compose a new message; and selection of options 5214, 5218 and 5220 respectively causes display of a conversation interface for a messages conversation between the user and the person represented in the option (e.g., S. Ramanujan, Mom, and G. Hardy, respectively).
In addition, in some embodiments, the appearance of home screen 5202 is maintained (e.g., does not change in accordance with the current characteristic intensity of contact 5206) once the characteristic intensity has exceeded the first intensity threshold for the first time.
As shown in FIG. 5K4, the contextual content object (e.g., mini application object 5210) includes content contextually selected from the Messages application (e.g., the avatars of users, a miniature messages application icon, an application name) and optionally additional functions (e.g., the avatars 5224, 5226, 5228, and 5230 are responsive to tap inputs or deep press inputs for performing various actions with respect to the mini application object 5210 and/or the Messages application). For example, tapping on the avatar 5224 launches the Messages application and displays a conversation user interface for reviewing previous messages and composing a reply to the messages represented in the conversation user interface.
FIGS. 5K5-5K7 illustrate a process for adding the contextual content object to the user interface that is configured to display respective contextual content objects associated with different applications of a plurality of applications installed on device 100.
FIG. 5K5 illustrates that, the contextual content object (e.g., mini application object 5210) remains displayed on the blurred and darkened home screen 5202 after lift-off of contact 5206 is detected. Another input (e.g., a tap input by contact 5236) is subsequently detected on the “add widget” affordance (e.g., affordance 5222) displayed within (or otherwise concurrently with) the contextual content object (e.g., mini application object 5210).
FIG. 5K6 illustrates that, upon lift-off of contact 5236, an animation is presented illustrating that the contextual content object (e.g., mini application object 5210) is being added to the user interface that is configured to display respective contextual content objects associated with different applications of a plurality of applications installed on device 100. For example, a mini application object screen (e.g., mini application object screen or widget screen 5238) is shown to slide in from the left of the display and partially cover home screen 5202, and mini application object 5210 is shown to jump from its original location into a slot in the mini application object screen 5238. As shown in FIG. 5K6, mini application object screen 5238 already includes two mini application objects (e.g., the Up Next mini application object 5240 associated with the Calendar application, and the Calendar mini application object 5242 associated with the Calendar application).
FIG. 5K7 illustrates that once mini application object 5210 has been added to mini application object screen 5238, the mini application object screen 5238 slides back to the left, and disappears. The user interface is restored to the state before the “add widget” affordance is activated (e.g., the state as shown in FIG. 5K4). As shown in FIG. 5K7, once mini application object 5210 has been added to mini application object screen 5238, the “add widget” affordance is no longer displayed with mini application object 5210. Instead, an indicator (e.g., the text “Added” or a checkmark) is displayed to indicate that mini application object 5210 has already been added into the mini application object screen. In some embodiments, the indicator (e.g., the text “Added” or a checkmark) is only displayed briefly right after the addition of mini application object 5210 to mini application object screen 5238. In some embodiments (not shown), when mini application object 5210 is being added to mini application object screen 5238 in response to activation of the “add widget” affordance, device 100 displays mini application object screen 5238 including the newly added mini application object 5238 in lieu of home screen 5202.
FIGS. 5K8-5L3 illustrate that different portions of a contextual content object (e.g., mini application object 5210) have different responses to a press input (e.g., a light press input or a deep press input).
FIGS. 5K8-5K10 illustrate that a light press input (e.g., input by contact 5248 with a characteristic intensity above the light press intensity threshold ITL) on a first portion of mini application object 5210 is detected, causing a first type of additional information to be displayed.
FIG. 5K8 shows that contact 5248 is detected on a portion of mini application object 5210 outside of any of the avatars included in mini application object 5210. FIG. 5K9 illustrates that, when a characteristic intensity of contact 5248 exceeds a respective intensity threshold (e.g., the light press intensity threshold), an additional row of avatars/aliases (e.g., avatars 5252, 5254, 5256, and 5258) is displayed. These additional avatars/aliases are for people that are selected based on the number of messages that have been sent between the user and the user's contacts (e.g., mini application object 5210 now includes additional avatars or aliases (e.g., avatars 5252, 5254, 5256, and 5258) of four people with whom the user has had the next highest numbers of instant messaging communications during the past week). FIG. 5K10 illustrates that, upon lift-off of contact 5248, the additional avatars and aliases (e.g., avatars 5252, 5254, 5256, and 5258) remain displayed in mini application object 5210.
FIGS. 5L1-5L3 illustrate that a light press input (e.g., input by contact 5260 with a characteristic intensity above the light press intensity threshold ITL) on a second portion of mini application object 5210 is detected, causing a second type of additional information to be displayed.
FIG. 5L1 shows that contact 5260 is detected on a portion of mini application object 5210 that displays one of the avatars included in mini application object 5210 (e.g., contact 5260 is detected on avatar 5230). FIG. 5L2 illustrates that, when a characteristic intensity of contact 5260 exceeds a respective intensity threshold (e.g., the light press intensity threshold), the last communication (e.g., message 5262) from the person represented by the selected avatar (e.g., avatar 5230) is displayed in mini application object 5210. FIG. 5L3 illustrates that, upon lift-off of contact 5260, the last communication (e.g., message 5262) is removed from mini application object 5210. The user can press on another avatar to see the last communication from the person represented by that avatar. Although FIG. 5L1 shows that additional avatars are also displayed in response to the press input by contact 5260, this is optional or is not implemented in some embodiments.
FIGS. 5L4-5L5 illustrate that a tap input (e.g., by contact 5264) that is detected outside of mini application object 5210 and menu 5212, dismisses mini application object 5210 and menu 5212 from home screen 5202. Home screen 5202 is restored to its original brightness and clarity.
FIGS. 5L6-5L8 illustrate that a swipe input (e.g., by contact 5266 moving from left to right) on home screen 5202 scrolls home screen 5202 to the right, and brings in mini application object screen 5238 from the left. FIG. 5L8 shows that mini application object screen 5238 now replaces home screen 5202 and occupies the entire display 112.
As shown in FIG. 5L8, mini application object screen 5238 includes a number of mini application objects each associated with a respective application (e.g., mini application object 5268 associated with the Messages application, mini application object 5240 associated with the Calendar application, and mini application object 5242 associated with the Calendar application). In some embodiments, each mini application object includes an affordance for displaying additional information in the mini application object (e.g., a “show more” affordance).
FIGS. 5L9-5M2 illustrate that different portions of a contextual content object (e.g., mini application object 5268) have different responses to an input (e.g., a tap input).
FIGS. 5L9-5L10 illustrate that a tap input (e.g., by contact 5272) detected on a first portion of mini application object 5268 (e.g., a tap input detected on avatar 5230) causes device 100 to launch the Messages application and display a first user interface of the Messages application (e.g., a conversation user interface for a message conversation between the user and a person represented by the selected avatar 5230). In FIG. 5L9, mini application object 5268 is displayed in mini application object screen 5238. Contact 5272 is detected on avatar 5230 in mini application object 5268. A characteristic intensity of contact 5272 does not increase above a light press intensity threshold ITL. FIG. 5L10, upon lift-off of contact 5272, device 100 launches the Messages application, and replaces mini application object screen 5238 with a conversation user interface of the Messages application (e.g., conversation user interface 5274). The conversation user interface (e.g., conversation user interface 5274) displays a message conversation between the user and the person represented by the selected avatar (e.g., avatar 5230). The conversation interface displays one or more previous messages (e.g., messages 5276, 5278, and 5280) sent between the user and the person represented by the selected avatar. The conversation interface also includes a soft keyboard 5282 and a text input field for composing a message to the person represented by the selected avatar.
FIGS. 5M1-5M2 illustrate that a tap input (e.g., by contact 5284) detected on a second portion of mini application object 5268 (e.g., a tap input detected on the header portion) causes device 100 to launch the Messages application and display a second user interface of the Messages application (e.g., a conversation listing user interface for listing message conversations the user had with other users). In FIG. 5M1, mini application object 5268 is displayed in mini application object screen 5238. Contact 5284 is detected on the header portion of mini application object 5268. A characteristic intensity of contact 5284 does not increase above the light press intensity threshold ITL. FIG. 5M2, upon lift-off of contact 5284, device 100 launches the Messages application, and replaces mini application object screen 5238 with a conversation listing user interface of the Messages application (e.g., conversation listing user interface 5286). The conversation listing user interface (e.g., conversation listing user interface 5286) displays a listing of message conversations between the user and other contacts of the user. The user can navigate to the conversation user interface for a respective person by selecting the corresponding listing item in the conversation listing user interface 5286 (e.g., a tap input on the conversation listing item for Genevive will cause the device to display the conversation user interface shown in FIG. 5L10).
FIGS. 5N1-5N4 illustrate a process in which a deep press input is detected on the Contacts application icon, and the deep press input causes a contextual content object and a menu of options for the Contacts application to be displayed over the home screen.
In FIG. 5N1, home screen 5288 is displayed. A contact (e.g., contact 5290) is detected on one of the application icons (e.g., application icon 445 associated with the Contacts application (e.g., also referred to as the Address Book application)), and the application icon is selected when the characteristic intensity of contact 5290 is above the detection threshold intensity IT0 and below the hint intensity threshold ITH.
FIG. 5N2-5N3 illustrate that, once the characteristic intensity of contact 5290 increases above a predetermined threshold intensity (e.g., the hint intensity threshold ITH), device 100 applies dynamic changes to the user interface in accordance with a current value of the characteristic intensity. For example, device 100 dynamically increases (or decreases) the amount of blurring and darkening applied to home screen 5288 in accordance with the increase (or decrease) in the characteristic intensity of contact 5290, while application icon 445 is overlaid on top of the blurred and darkened home screen 5288. In addition, a menu platter (e.g., platter 5292) emerges from between application icon 445 and home screen 5288, and the size of the platter changes (e.g., grows or shrinks) in accordance with the changes in the characteristic intensity of contact 5290. As shown in FIGS. 5N1 and 5N2, as contact intensity is increased within the range ITH and a first higher intensity threshold (e.g., the light press intensity threshold ITL), the amount of blurring and darkening applied to home screen 5288 is increased accordingly, and the size of platter 5292 is also increased accordingly. Before the characteristic intensity of contact 5290 crosses the first intensity threshold, lift-off of the contact returns the user interface to its original state (e.g., the home screen shown in 5N1 without the selection of application icon 445).
FIG. 5N4 illustrates that, once the characteristic intensity of contact 5290 exceeds the first intensity threshold (e.g., the light press intensity threshold ITL), a contextual content object (e.g., mini application object or widget 5294) associated with the Contacts application is displayed over the blurred and darkened home screen 5288. The contextual content object includes contextually selected content that has been automatically selected based on a current context of device 100. For example, mini application object 5294 is a widget that includes a grid of several people that are selected based on the number of communications (e.g., instant messages, e-mail messages, telephone calls, VoIP calls, etc.) that have occurred between the user and the user's contacts (e.g., mini application object 5294 includes avatars or aliases (e.g., avatars 5296, 5298, 5300, 5302) of four people with whom the user has had the highest numbers of communications (e.g., communications of various types) during the past week). In some embodiments, a respective avatar or alias also includes a badge (e.g., badges 5304a-d) that indicates the number of communications that have occurred between the user and the person represented by the respective avatar or alias. For example, badge 5304a indicates that there are eight communications between Issac and the user, and badge 5304c indicates that there are four communications between Miles and the user in the past week. The badges are updated while mini application object 5294 is displayed, when new communications from the people represented in the mini application object 5294 are received at device 100.
In addition, a menu of selectable options (e.g., menu 5309) is displayed concurrently with the contextual content object (e.g., mini application object 5294). The menu of selectable options include options that when activated, are configured to launch the Contacts application to a respective user interface of the Contacts application for performing a respective function associated with the Contacts application. For example, selection of option “Create New Contact” causes a new contact user interface to be displayed for the user to create a new contact card; and selection of option “Search Addressbook” causes a search interface to be displayed; selection of option Recent communications causes a user interface that displays recent communications of various types to be displayed; and selection of option “Show my info” causes the user's own contact card to be displayed.
As shown in FIG. 5N4, the contextual content object (e.g., mini application object 5294) includes content contextually selected from Contacts application (e.g., the avatars of users, a miniature Contacts application icon, an application name) and optionally additional functions (e.g., the avatars 5296, 5298, 5300, and 5302 are responsive to tap inputs or press inputs for performing various actions with respect to the mini application object 5294 and/or the Contacts application). For example, tapping on the avatar 5296 launches the Contacts application and displays a contact card for reviewing contact information of and initiating various types of communications to the person represented by the selected avatar (e.g., Issac).
In some embodiments, the placement of the mini application object and the menu of options are based on the location of the corresponding application icon on the home screen. For example, if there is more space below the application icon, the mini application object is placed below the application icon, and the menu of options is placed below the mini application object, e.g., as shown in the example in FIG. 5K4. If there is more space above the application icon, the mini application object is placed above the application icon, and the menu of options is placed above the mini application object, e.g., as shown in the example in FIG. 5W5. In some embodiments, as shown in FIG. 5N4, when the combined size of the mini application object and the menu of options to be displayed with the application icon is too large for both the space above the application icon and the space below the application icon, the application icon is shifted slightly upward or downward to accommodate the mini application object and the menu of options when the deep press input is detected on the application icon. For example, as shown in FIG. 5N4, application icon 445 is shifted upward by about half of icon height, and mini application object is displayed below application icon 445. The menu of options 5309 is displayed below mini application object 5294.
FIGS. 5N5 and 5N6 illustrates that while contact 5290 is maintained on the touch screen 112, a movement of contact 5290 is detected. As contact 5290 moves from application icon 445 to an option “Show my info” in the menu of options 5306, haptic feedback is provided when contact 5290 passes each option in the menu of options 5306. FIG. 5N6 illustrates that, when lift-off of contact 5290 is detected when contact is over the option “Show my info”, the user's own contact card is displayed (e.g., in contact card user interface 5311). In some embodiments (not shown), contact card user interface 5311 is overlaid on a portion of the blurred and darkened version of home screen 5288. In some embodiments, contact card user interface 5311 replaces home screen 5288 and mini application object 5294 and menu 5309 on the display.
FIGS. 5P1-5P2 illustrate that a light press input (e.g., input by contact 5312 with a characteristic intensity above the light press intensity threshold ITL) on a second portion of mini application object 5240 is detected, causing a second type of additional information to be displayed.
FIG. 5P1 shows that contact 5314 is detected on a portion of mini application object 5240 that is not displaying details of the event that is coming up next (e.g., a blank portion or the header portion). FIG. 5P2 illustrates that, when a characteristic intensity of contact 5314 exceeds a respective intensity threshold (e.g., the light press intensity threshold), mini application object 5240 is expanded (e.g., shown as expanded mini application object 5272 in FIG. 5P2) and displays both the originally displayed event and additional events that are coming up next (e.g., event items 5316, 5318, and 5320). For example, as shown in FIG. 5P2, two more events (e.g., “Team meeting” and “Dinner with Mom”) are displayed in addition to the event (e.g., “Coffee with Jon”) that was displayed in expanded mini application object 5272. As shown in FIG. 5P2, expanded mini application object 5272 is displayed within mini application object screen 5238 and replaces mini application object 5240. In some embodiments, expanded mini application object 5272 is overlaid on a blurred and darkened version of mini object screen 5238. In some embodiments, expanded mini application object 5272 is dismissed and mini application object screen is restored (e.g., to the state shown in FIG. 5P1) when lift-off of contact 5314 is detected. In some embodiments (not shown), expanded mini application object 5272 remains overlaid on the blurred and darkened version of mini application object screen 5238 when lift-off of the contact is detected. Another input (e.g., a tap outside of expanded mini application object 5272 or a tap on a “close” affordance displayed within expanded mini application object 5272 is detected) can dismiss expanded mini application object 5272 and restore mini application object screen 5238 to its original brightness and clarity.
In some embodiments, the mini application object shown in the mini application object screen (e.g., mini application object 5268 in FIG. 5P2) is identical to the mini application object (e.g., mini application object 5210 in FIG. 5K4) displayed concurrently with the application icon (e.g., the Messages application icon 424) and the menu of options (e.g., menu 5212) over the home screen, except for the portion displaying the “add widget” affordance 5222. The mini application object for a given application has the same functions and behaviors in response to user inputs (e.g., a tap input or light press input on various portions of the mini application object) detected on the mini application object, regardless of whether the mini application object is displayed in the mini application object screen or over the home screen, in accordance with some embodiments.
In some embodiments, the mini application object shown over the home screen is a representation of a corresponding mini application object that has been added to the mini application object screen. For example, the mini application object shown over the home screen may provide a subset of functions or content that is shown in the corresponding mini application object that has been added to the mini application object screen. For example, in response to the same input on the mini application object, the amount of additional information that is displayed in the mini application object shown over the home screen may be less than the amount of additional information that is displayed in the corresponding mini application object that has been added to the mini application object screen (e.g., due to space constraint on the home screen). In some embodiments, the mini application object is scrollable to reveal additional content and selectable options for additional functions from the corresponding application when it is displayed in the mini application object screen, but not when it is displayed over a darkened version of the home screen.
Although the examples shown in FIGS. 5J1-5P2 are shown only in one environment at a time (e.g., either in the mini application object screen or overlaid on a deemphasized version of a background user interface (e.g., the home screen or another screen showing application icons)), some or all of the responses and behaviors illustrated in that environment are optionally implemented in other environments that display the mini application object as well. In the interest of brevity, all combinations of environments and behaviors are not exhaustively enumerated herein.
FIGS. 5Q1-5S5 illustrate user interfaces for quickly invoking one of several download-related quick actions with respect to an application that are in the process of being downloaded, in accordance with some embodiments.
FIGS. 5Q1-5Q6 illustrate a process for displaying a menu of options related to downloading of an application, in accordance with some embodiments.
FIG. 5Q1 displays a user interface (e.g., home screen 5402) that includes a plurality of application icons (e.g., application icon 5404 for launching the Messages application and application icon 5406 for launching the Calendar application, etc.) and one or more downloading icons that represent applications that are in the process of being downloaded (e.g., downloading icon 5408 that represents a Game application that is in the process of being downloaded, and downloading icon 5410 that represents a Sketch application that is in the process of being downloaded). As shown in FIG. 5Q1, downloading icon 5408 indicates that the downloading of the Game application is in progress. Also shown in FIG. 5Q1, downloading icon 5410 indicates that downloading of the Sketch application has been paused. Other possible states of the downloading icon include a suspended state (e.g., due to lack of authorization or approval from a server), or a waiting state (e.g., due to lack of downloading bandwidth or unavailability of server, etc.), etc.
FIG. 5Q2 illustrates that a contact (e.g., contact 5412) is detected on downloading icon 5408. FIGS. 5Q2-5Q4 indicate that as the characteristic intensity of contact 5412 changes between the range ITH and ITL (e.g., increases within the range ITH) and ITL, device 100 dynamically applies a deemphasizing visual effect (e.g., dynamically applies a blurring and darkening effect) on home screen 5402, including all application icons on home screen 5402, except downloading icon 5408, in accordance with a current value of the characteristic intensity of contact 5412. In addition, when the characteristic intensity of contact 5412 is above the hint intensity threshold, platter 5414 is displayed between downloading icon 5408 and the deemphasized home screen 5402. The size of platter 5414 changes dynamically (e.g., increases dynamically) in accordance with the changes in the characteristic intensity of contact 5412 (e.g., in accordance with the increase in the characteristic intensity of contact 5412).
FIG. 5Q5 illustrates that, when the characteristic intensity of contact 5412 increases above a respective intensity threshold (e.g., the light press intensity threshold ITL), device 100 displays a menu of selectable options (e.g., menu 5416) concurrently with downloading icon 5408 over the deemphasized home screen 5402. In some embodiments, the menu of selectable options includes respective options related to downloading of the application represented by downloading icon 5408. As shown in FIG. 5Q5, menu 5416 includes option 5418 for prioritizing the downloading of the Game application over one or more other applications that are also in the process of being downloaded (e.g., the Sketch application). Menu 5416 also includes option 5420 for pausing the download of the Game application. Menu 5416 also includes option 5422 for canceling the download of the Game application. Menu 5416 also includes option 5424 for sharing the Game application with other users.
FIG. 5Q6 illustrates that, upon lift-off of contact 5412, menu 5416 remains displayed over the deemphasized home screen 5402.
FIGS. 5Q7-5Q8 illustrate that selection and activation of option 5424 (e.g., by a tap input (e.g., by contact 5426) on option 5424) causes device 100 to display a share user interface (e.g., share card 5428). In FIG. 5Q8, share card 5428 is displayed over the deemphasized home screen 5402. In some embodiments, menu 5416 ceases to be displayed when share card 5428 is displayed. The share card includes options to share the Game application via a number of communication methods (e.g., via a wireless connection, an instant message, an email, a reminder, etc.), or in various other manners (e.g., copy link, send as a gift, etc.). In some embodiments, selection of option 5424 causes an application store application (e.g., the App Store application) to be launched, and the page showing the Game application to be displayed in the initial user interface of the application store application.
FIG. 5Q9 illustrates that, after downloading of the Game application is completed, downloading icon 5408 is replaced by application icon 5408′ that represents the Game application in home screen 5402. A tap input on application icon 5408′ launches the Game application.
FIGS. 5Q9-5Q11 illustrate a press input (e.g., by contact 5432) on downloading icon 5410 causes device 100 to display menu 5434 that include respective options related to downloading of the application represented by downloading icon 5410.
As shown in FIG. 5Q10, when the characteristic intensity of contact 5432 increases above the hint intensity threshold, device 100 applies a deemphasizing visual effect on home screen 5402, except for on downloading icon 5410. The amount of deemphasizing visual effect is dynamically varied in accordance with a current value of the characteristic intensity of contact 5432. Platter 5434 is displayed between downloading icon 5410 and deemphasized home screen 5402. The size of platter 5434 changes dynamically with the characteristic intensity of contact 5432, when the characteristic intensity varies within the range between ITH and ITL.
FIG. 5Q11 illustrates that when the characteristic intensity of contact 5432 increases above the light press intensity threshold, a menu of selectable options (e.g., menu 5434) is presented with downloading icon 5410 over the deemphasized home screen 5402. As shown in FIG. 5Q11, menu 5434 includes option 5436 for prioritizing the downloading of the Sketch application over one or more other applications that are also in the process of being downloaded. Menu 5434 also includes option 5438 for resuming the download of the Sketch application. Menu 5434 also includes option 5440 for canceling the download of the Sketch application. Menu 5434 also includes option 5442 for sharing the Sketch application with other users. In some embodiments, if the downloading icon represents the only application that is in the process of being downloaded on device 100, the option for prioritizing download (e.g., option 5436) is optionally omitted from menu 5434. In this example, the downloading of the Sketch application was paused before the press input was detected, therefore, the option for pausing the download is replaced with the option for resuming the download.
As shown in FIGS. 5Q7 and 5Q11, the menu of options presented in response to a press input on a downloading icon is a generic menu common to all downloading icons, with the exception that the option of pausing the download and the option for resuming the download are toggled depending on the current state of the downloading for a particular application icon that received the press input.
FIG. 5Q12 illustrates that, before lift-off of contact 5432, movement of contact 5432 to option 5438 (e.g., option to resume download) is detected. FIG. 5Q13 illustrates that, when lift-off of contact 5432 is detected, option 5438 (e.g., option to resume download) is activated, and downloading of the Sketch application is resumed. In addition, selection and activation of option 5438 (or any other option) causes dismissal of menu 5434 and restoration of home screen 5402.
Figure Q14 illustrates that when download of the Sketch application is completed, downloading icon 5410 is replaced with application icon 5410′. A tap input on application icon 5410′ launches the Sketch application.
FIGS. 5Q15-5Q17 illustrates that a press input on an application icon for an application causes the display of a contextual content object associated with the application and an application-specific menu of selectable options.
As shown in FIG. 5Q15, a press input (by contact 5446) is detected on application icon 5408′ for the Game application. When a characteristic intensity of contact 5446 is between the range ITH and ITL, device 100 dynamically deemphasizes home screen 5402 except for application icon 5408′. Platter 5444 is displayed between application icon 5408′ and deemphasized home screen 5402.
FIG. 5Q16 illustrates that, when the characteristic intensity of contact 5446 exceeds the light press intensity threshold, mini application object 5448 is displayed over deemphasized home screen 5402 concurrently with application icon 5408′. Mini application object 5448 includes avatars of several gaming friends of the user. In some embodiments, a tap input on one of the avatars starts a communication (e.g., an instant messaging communication or a communication supported by the Game application) with the person represented by the avatar. As shown in FIG. 5Q16, a menu of selectable options (e.g., menu 5450) for activating various functions in the Game application is also presented with mini application object 5448. Menu 5450 includes option 5452 for launching a frequently played game in the Game application, option 5454 for displaying a score board with top scores for games played in the Game application, option 5456 for display a list of the user's favorite games or frequently played games, and option 5458 for sharing the Game application. In some embodiments, a selectable option displayed in menu 5450, when activated, launches the Game application and displays a user interface corresponding to the function represented by the option as the initial user interface of the Game application. In some embodiments, a selectable option displayed in menu 5450, when activated, provide access to a function available within the Game application, without launching the Game application and without leaving the current context (e.g., the home screen).
FIG. 5Q17 illustrates that, when lift-off of contact 5446 is detected, mini application object 5448 and menu 5450 remain displayed over the deemphasized home screen 5402. A subsequent input (e.g., a tap input, a light press input, and/or a deep press input) can be used to select a menu option or activate an area in the mini application object to show more information related to the Game application, show more content from the Game application, show more functions from the Game application, or perform one or more functions of the Game application. A tap input outside of mini application object 5448, application icon 5408′, and menu 5450, dismisses mini application object 5448 and menu 5450 and restores home screen 5402.
FIGS. 5R1-5R4 illustrate that when an application does not have an associated contextual content object, a press input on an application icon for the application causes the display of an application-specific menu of selectable options, without displaying any contextual content object. In some embodiments, when only a menu of options is displayed, the width of the menu is independent of the width of the contextual content objects (e.g., a standard width that applies to contextual content objects of all applications installed on device 100).
FIG. 5R2 illustrates that, a press input (by contact 5460) is detected on application icon 5410′ for the Sketch application. When a characteristic intensity of contact 5460 is between the range ITH and ITL, device 100 dynamically deemphasizes home screen 5402 except for application icon 5410′. Platter 5408 is displayed between application icon 5410′ and deemphasized home screen 5402.
FIG. 5R3 illustrates that, when the characteristic intensity of contact 5460 exceeds the light press intensity threshold, a menu of selectable options (e.g., menu 5462) for activating various functions in the Sketch application is presented with application icon 5410′ over the deemphasized home screen 5402. Menu 5462 includes option 5464 for displaying a user interface with a new sketch, option 5466 for displaying the last sketch that was made with the Sketch application, option 5468 for displaying a list of the user's favorite sketches, and option 5470 for sharing the Sketch application. In some embodiments, a selectable option displayed in menu 5462, when activated, launches the Sketch application and displays a user interface corresponding to the function represented by the option as the initial user interface of the Sketch application. In some embodiments, a selectable option displayed in menu 5462, when activated, provides access to a function available within the Sketch application, without launching the Sketch application and without leaving the current context (e.g., the home screen).
FIG. 5R4 illustrates that, when lift-off of contact 5460 is detected, menu 5462 remains displayed over the deemphasized home screen 5402. A subsequent input (e.g., a tap input, a light press input, and/or a deep press input) can be used to select a menu option to perform one or more functions of the Sketch application and launching the Sketch application to respective user interfaces associated with the one or more functions.
FIG. 5R5-5R6 illustrate that, a tap input (e.g., by contact 5472) outside of application icon 5410′ and menu 5462 dismisses menu 5462 and restores home screen 5402.
FIGS. 5R6-5R7 illustrate that, a tap input (e.g., by contact 5474) on an application icon (e.g., application icon 5410′) displayed in home screen 5402 launches the application represented by the application icon (e.g., the Sketch application). FIG. 5R7 illustrates that, the Sketch application is launched upon lift-off of contact 5474 from application icon 5410′. The initial user interface of the Sketch application is optionally, a user interface for creating a new sketch. In some embodiments, the Sketch application is launched and displays a user interface that represents the last state of the Sketch application when the user last left the Sketch application.
FIGS. 5S1-5S3 illustrate that a tap input (e.g., by contact 5478) on a downloading icon (e.g., downloading icon 5408) in the downloading state (e.g., active downloading of application data is in progress) pauses the download of the application. As shown in FIG. 5S3, downloading icon 5408″ represents the Game application in the paused state.
FIGS. 5S3-5S5 illustrate that a tap input (e.g., by contact 5480) on a downloading icon (e.g., downloading icon 5410) in the paused state (e.g., active downloading of application data is paused) resumes the active download of the application data. As shown in FIG. 5S5, downloading icon 5410″ represents the Sketch application in the active downloading state.
FIGS. 5T1-5T15 illustrate user interfaces for quickly launching a respective application with unread notifications from a folder containing multiple applications without having to first open the folder, in accordance with some embodiments.
FIGS. 5T1-5T5 illustrate a process for displaying a menu of selectable options in response to a press input detected on an application folder icon.
As shown in FIG. 5T1, home screen 5502 includes a plurality of application icons and one or more application folder icons (e.g., application folder icon 5504). Application folder icon 5504 represents an application folder that includes one or more application icons for launching respective applications installed on device 100. In some embodiments, a badge (e.g., badge 5506) is displayed on the application folder icon (e.g., application folder icon 5504) to indicate a total number of all unread notifications (e.g., nine) associated with applications represented within the application folder (e.g., the “Fav-1” folder).
FIGS. 5T2-5T4 illustrate that a press input (by contact 5508) is detected on application folder icon 5504. When a characteristic intensity of contact 5508 increases above the hint intensity threshold ITH, device 100 dynamically deemphasizes home screen 5502, while providing a platter 5510 between application folder icon 5504 and the deemphasized home screen 5502 (e.g., as shown in FIGS. 5T3-5T4). For example, when the characteristic intensity of contact 5508 varies (e.g., increases) within the range ITH and ITL, the amount of deemphasizing (e.g., blurring and darkening) applied to home screen 5502 is dynamically varied (e.g., increased) accordingly. If lift-off of contact 5508 is detected before the characteristic intensity of contact 5508 exceeds the light press intensity threshold ITL, device 100 restores home screen 100 to its original state (e.g., original clarity and brightness).
FIG. 5T5 illustrates that when the characteristic intensity of contact 5508 exceeds the light press intensity threshold ITL, device 100 displays a menu of selectable options (e.g., menu 5512) concurrently with application folder icon 5504. As shown in FIG. 5T5, menu 5512 includes selectable options each for launching a respective application represented in the application folder (e.g., folder “Fav-1”) that has at least one unread notification. For example, as shown in FIG. 5T5, menu 5512 includes three selectable options for respectively launching three applications that have unread notifications, and an option for renaming the application folder. In the current example, menu 5512 includes a first option (e.g., option 5514) for launching the Messages application in the application folder and the Messages application has five unread notifications. Menu 5512 also includes a second option (e.g., option 5516) for launching the Mail application in the application folder and the Mail application has three unread notifications. Menu 5512 also includes a third option (e.g., option 5518) for launching the Music application in the application folder and the Music application has one unread notification. In this example, the application folder “Fav-1” represented by folder icon 5504 includes several other applications in addition to the three applications represented in menu 5512. However, because these other applications currently do not have any unread notifications, menu 5512 does not include a corresponding option for launching each of these other applications. In some embodiments, in each option for launching a respective application, an identifier for identifying the application (e.g., a miniature application icon and application name) is included, along with a count of unread notification currently associated with the application.
In this example, the maximum number of application launching options that can be displayed in menu 5512 is four. However, since only three applications in the folder have unread notifications at the time when menu 5512 displayed, only three application launching options are displayed in menu 5512. In some embodiments, the application launching options for applications with unread notifications are sorted in menu 5512 in accordance with the number of unready notifications that are associated with each of the applications with unread notifications.
FIG. 5T6 illustrates that, while menu 5512 is displayed, two more notifications are received by applications within the application folder “Fav-1”. In response to receiving new notifications, device 100 updates badge 5506 to reflect the updated total number of unread notifications for applications in the application folder. In some embodiments, at shown in FIG. 5T6, if any of the application represented by the application launching options in menu 5512 receives additional new notifications, the count of unread notification displayed in the application launching option is also updated. For example, as shown in FIG. 5T6, the Messages application has received one additional new message, and the total number of unread notifications for the Messages application is increased to six. As a result, option 5514 for launching the Messages application is updated to reflect that the total number of unread notifications for the Messages application is now six. In some embodiments, if, while menu 5512 is displayed, an application that is not represented in menu 5512 receives one or more new notifications, an application launching option for that application is optionally added to menu 5512 in real time. In some embodiments, in order to avoid confusing the user and keeping the user interface stable, the application launching option for that application that is not currently represented in menu 5512 is not added to menu 5512 until menu 5512 is closed and displayed again in response to another press input.
FIG. 5T7-5T8 illustrate that menu 5512 is dismissed when a tap input (e.g., by contact 5522) is detected outside of menu 5512 and application icon 5504 on the deemphasized home screen 5502. Upon lift-off of contact 5522, home screen 5502 is restored to its original state. As shown in FIG. 5T8, the application folder “Fav-1” now has a total of twelve unread notifications.
FIG. 5T9 illustrates that another press input (by contact 5524) is detected on application folder icon 5504. When a characteristic intensity of contact 5524 increases above the hint intensity threshold ITH, device 100 dynamically deemphasizes home screen 5502, while providing platter 5526 between application folder icon 5504 and the deemphasized home screen 5502, as shown in FIGS. 5T10-5T11. For example, when the characteristic intensity of contact 5524 varies (e.g., increases) within the range ITH and ITL, the amount of deemphasizing (e.g., blurring and darkening) applied to home screen 5502 is dynamically varied (e.g., increased) accordingly. If lift-off of contact 5524 is detected before the characteristic intensity of contact 5524 exceeds the light press intensity threshold ITL, device 100 restores home screen 100 to its original state (e.g., original clarity and brightness).
FIG. 5T12 illustrates that when the characteristic intensity of contact 5524 exceeds the light press intensity threshold ITL, device 100 displays a menu of selectable options (e.g., menu 5528) concurrently with application folder icon 5504. As shown in FIG. 5T12, menu 5528 includes selectable options each for launching a respective application represented in the application folder (e.g., folder “Fav-1”) that has at least one unread notification. For example, as shown in FIG. 5T12, menu 5528 includes four selectable options for respectively launching four applications that have unread notifications, and an option for renaming the application folder. In the current example, menu 5528 includes a first option (e.g., option 5530) for launching the App Store application in the application folder and the App Store application has one unread notification which is an alert. Menu 5528 also includes a second option (e.g., option 5532) for launching the Messages application in the application folder and the Messages application has six unread notifications. Menu 5528 also includes a third option (e.g., option 5534) for launching the Mail application in the application folder and the Mail application has three unread notifications. Menu 5528 also includes a fourth option (e.g., option 5536) for launching the Music application in the application folder and the Music application has one unread notification. Menu 5528 also includes a rename option (e.g., option 5538) for renaming the folder.
In this example, the application folder “Fav-1” represented by folder icon 5504 includes several other applications in addition to the four applications represented in menu 5528. In fact, one of the other applications also has one unread notification. However, because the maximum number of application launching options that can be included in menu 5528 is four, the application launching option for one of the five applications with unread notifications is not included in menu 5528. In some embodiments, when prioritizing which application launching options to include in menu 5528, alert is prioritized above regular notifications (e.g., because alert requests a user action); and for the same type of notifications, the application launching options are sorted based on the total count of unread notifications for each application. In some embodiments, for applications with the same number and same types of unread notifications, the application launching options for the applications are sorted according to the timestamps for the latest notifications that have been received for the respective applications.
FIG. 5T13 illustrates that, when lift-off of contact 5524 is detected, menu 5528 remains displayed over deemphasized home screen 5502. FIG. 5T14 illustrates that another tap input (e.g., by contact 5540) is detected on one of the application launching options (e.g., option 5532 for launching the Messages application). FIG. 5T15 illustrates that, upon lift-off of contact 5540, device 100 launching the Messages application, and a user interface of the Messages application (e.g., conversation listing user interface 5542) replaces application icon 5504, menu 5528, and deemphasized home screen 5502 on the touch screen 112.
FIGS. 5U1-5W5 illustrate user interfaces for quickly entering a rename and reconfiguration mode for an application folder without having to first open the folder, in accordance with some embodiments.
FIGS. 5U1-5U7 illustrate a conventional process for editing a folder name and folder content of an application folder.
FIG. 5U1 illustrates home screen 5502 that includes a plurality of application icons and one or more application folder icons (e.g., application folder icon 5504). A tap input (e.g., by contact 5544) is detected on application folder icon 5504. Upon lift-off of contact 5544, application folder 5504 is opened to show its content. FIG. 5U2 shows an intermediate state of folder 5504 (e.g., represented as folder 5504′) as it is popping up from its original location and is expanded. FIG. 5U1 illustrates that expanded folder 5546 is displayed over deemphasized home screen 5502. Expanded folder 5546 includes respective application icons for several applications (e.g., application icons 424, 418, 480, 484, and 438).
FIGS. 5U4-5U5 illustrate that a long press input (e.g., by contact 5550) is detected on one of the applications icons (e.g., application icon 438 for the Weather application) in expanded folder 5546. When the time threshold for the long press input is met by contact 5550, icon reconfiguration mode is activated, as shown in FIG. 5U5. In the icon reconfiguration mode, in some embodiments, a deletion affordance (e.g., an “x” sign) is displayed on each application icon, and activation of the deletion affordance on a respective application icon deletes the application that corresponds to the application icon from device 100. FIG. 5U5 further illustrates that folder name 5548 of the application folder (e.g., “Fav-1”) is displayed with expanded folder 5546. Folder name 5548 is initially displayed in a non-editable state.
FIGS. 5U6-5U7 illustrate that, another tap input (e.g., by contact 5552) is detected on folder name 5548. In response to detecting the tap input on folder name 5548, device 100 displays folder 5546 in an editable state and displays soft keyboard 5555 with expanded folder 5546 and folder name 5552 over deemphasized home screen 5502.
A subsequent contact (e.g., contact 5554) on a respective application icon in expanded folder 5546 can drag the respective application icon to another location (e.g., to a location outside of expanded folder 5546). In some embodiments, selection of an application icon dismisses soft keyboard 5555 but does not terminate the icon reconfiguration mode.
FIGS. 5V1-5V5 illustrate a process for displaying the menu of options with application launching options for applications with unread notifications and an option for renaming the folder.
As shown in FIG. 5V1, folder “Fav-1” now has a total of three unread notifications (as indicated by badge 5506 on folder icon 5504). FIGS. 5V2-5V4 illustrate that a press input (e.g., by contact 5556) is detected on folder icon 5504 and intermediate hint states are displayed in response to varying characteristic intensities of contact 5556 in the range between ITH and ITL. FIG. 5V5 illustrates that a menu of selectable options (e.g., menu 5558) is displayed in response to detecting that the characteristic intensity of contact 5556 exceeded the light press intensity threshold ITL. As shown in FIG. 5V5, in this example, only three applications in the folder “Fav-1” currently have unread notifications. Two of the applications each have one alert (e.g., the Mail application and the App Store application each have one alert), and their corresponding application launching options (e.g., options 5560 and 5562) are listed first in menu 5558. The Mail application has an alert that is newer than the alert for the App Store application, therefore, the application launching option for the Mail application is listed before the application launching option for the App Store application. One of the three applications (e.g., the Music application) has a regular notification and the application launching option (e.g., option 5564) is listed last.
As shown in FIG. 5V5, menu 5558 includes an option for renaming the folder (e.g., option 5566). FIGS. 5V6-5V8 illustrate that selection of the renaming option immediately puts the application folder in the reconfiguration mode and the folder name in the editable state.
As shown in FIG. 5V6, a tap input (e.g., by contact 5568) is detected on option 5566 for renaming the folder. FIG. 5V7 illustrates the application folder popping up from deemphasized home screen 5502 and is expanded to reveal its content upon lift-off of contact 5568. FIG. 5V8 illustrates that expanded folder 5546 is displayed over the deemphasized home screen 5502. Expanded folder includes application icons in the reconfiguration mode. In some embodiments, icons outside of expanded folder 5546 (e.g., in the deemphasized home screen 5502) are also in the reconfiguration mode. In other words, the selection of the renaming option puts the home screen (including all the application icons on the home screen) into the reconfiguration mode. An application icon in the reconfiguration mode can be moved and repositioned on home screen 5502. FIG. 5V8 further illustrates that, upon lift-off of contact 5568, folder name 5552 is displayed in an editable state and soft keyboard 5555 is displayed with expanded folder 5546 over deemphasized home screen 5502.
FIGS. 5V9-5V10 illustrate that inputs received through soft keyboard 5555 (e.g., by tap inputs on character keys (e.g., by contact 5570 on the letter “E” on keyboard 5555)) edit the folder name 5552. As shown in FIG. 5V10, the folder name is changed from “Fav-1” to “Fav-ONE”. FIG. 5V9-5V10 further illustrate that, when inputs are received from soft keyboard 5555 to edit the folder name, application icons in expanded folder 5546 remain in the reconfiguration mode.
FIG. 5V11 illustrates that, in response to detecting a selection input (e.g., by contact 5572) on a respective application icon in expanded folder 5546, device 100 ceases to display the folder name 5552 in the editable state, and ceases to display soft keyboard 5555. Application icons in expanded folder 5546 are still displayed in the reconfiguration mode.
FIGS. 5V12-5V14 illustrate that an application icon (e.g., application icon 438) is dragged from within expanded folder 5546 to outside of expanded folder 5546 and placed on home screen 5502. Folder icon 5504 is restored on home screen 5502 (now represented by folder icon 5504′) and the folder no longer contains the application icon 438. After the input for dragging application icon 438 to home screen 5502, the application icons on home screen 5502 still remain in the icon reconfiguration mode.
FIGS. 5W1-5W3 illustrate repositioning of another application icon (e.g., application icon 5408′ for the Game application) in response to a drag input by contact 5574. After application icon 5408′ is repositioned to the bottom of home screen 5502, an input is received (e.g., a press input on home button 204) to exit the icon reconfiguration mode. FIG. 5W3 shows that the home screen has been restored and icon reconfiguration mode has been terminated.
FIGS. 5W4-5W5 illustrate that a press input (e.g., by contact 5576) on the Game application icon 5408′causes display of mini application object 5448 and menu 5578. As shown in FIG. 5W5, because there is more space above application icon 5408′, mini application object 5448 is displayed above application icon 5408′, and menu 5578 is displayed above mini application object 5448, in contrast to the case shown in FIG. 5Q17.
In some embodiments, the device is an electronic device with a separate display (e.g., display 450) and a separate touch-sensitive surface (e.g., touch-sensitive surface 451). In some embodiments, the device is portable multifunction device 100, the display is touch-sensitive display system 112, and the touch-sensitive surface includes tactile output generators 167 on the display (
An input by a contact is detected at a location corresponding to Wi-Fi control affordance 614, as indicated by focus selector 640. In some embodiments, the appearance of one or more of the control affordances of control user interface 608 indicates a state of the control affordance. For example, Wi-Fi control affordance 614 is shown shaded to indicate that Wi-Fi is disabled. As indicated by intensity meter 606, the characteristic intensity of the contact is below hint press intensity threshold ITH, light press intensity threshold ITL, and deep press intensity threshold ITD. In accordance with a determination that the characteristic intensity of the contact meets control toggle criteria (e.g., the characteristic intensity of the contact is below hint press intensity threshold ITH), a Wi-Fi control that corresponds to the Wi-Fi control affordance 614 is toggled from a disabled state to an enabled state.
An input by a contact is detected at a location corresponding to Wi-Fi control affordance 614, as indicated by focus selector 642. In accordance with a determination that the characteristic intensity of the contact meets control toggle criteria (e.g., the characteristic intensity of the contact is below hint press intensity threshold ITH), the Wi-Fi control that corresponds to the Wi-Fi control affordance 614 is toggled from an enabled state to a disabled state.
In
In
In
In
In
In
In
In
In
In
In
In
In some embodiments, the device is an electronic device with a separate display (e.g., display 450) and a separate touch-sensitive surface (e.g., touch-sensitive surface 451). In some embodiments, the device is portable multifunction device 100, the display is touch-sensitive display system 112, and the touch-sensitive surface includes tactile output generators 167 on the display (
In
In
In
In
In
In
In
In some embodiments, one or more keys of content input area 740 do not trigger a tactile output when activated. For example, in response to an input detected by a contact at a location corresponding to a character 742 (the letter “a”), no tactile output occurs in accordance with a determination that a characteristic intensity of the contact is above a deep press intensity threshold ITD. No tactile output occurs at t5.
In some embodiments, as the speed of typing increases, both a tactile output parameter of tactile outputs and an audio output parameter of audio outputs increases. In some embodiments, as the speed of typing increases, both a tactile output parameter of tactile outputs and an audio output parameter of audio outputs decreases. In some embodiments, as the speed of typing increases, a tactile output parameter of tactile outputs increases and an audio output parameter of audio outputs decreases. In some embodiments, as the speed of typing increases, a tactile output parameter of tactile outputs decreases and an audio output parameter of audio outputs increases.
In some embodiments, the device is an electronic device with a separate display (e.g., display 450) and a separate touch-sensitive surface (e.g., touch-sensitive surface 451). In some embodiments, the device is portable multifunction device 100, the display is touch-sensitive display system 112, and the touch-sensitive surface includes tactile output generators 167 on the display (
In accordance with a determination that the characteristic intensity of the contact detected at a location corresponding to send affordance 810 increases above a deep press intensity threshold ITD, a plurality of message impact effect options are displayed, as indicated in
While the plurality of message impact effect options are displayed, the contact moves along a path indicated by arrow 844 to a position corresponding to “Loud” message impact effect option 824. In some embodiments, message impact effect option selection control 836 includes affordances that correspond to respective message impact effect options, such as affordance 845 that corresponds to “Loud” message impact effect option 824. In some embodiments, when a contact moves across touch-sensitive surface 112 to a position that corresponds to affordance 845, the affordance morphs into an affordance 847 for sending message content 808 with a selected message impact effect option.
In
In
In
The contact moves along a path indicated by arrow 849 to a position corresponding to “Slam” message impact effect option 822.
In
In
In
Screen 854 is gradually removed from third altered message region 852 and message content 808 is gradually revealed as a characteristic intensity of the contact increases.
In
In
In
In
In
In
In some embodiments, in accordance with a determination that the characteristic intensity of the contact detected at a location corresponding to message region 874 increases above deep press intensity threshold ITD, an acknowledgement selection affordance 878 is displayed, as indicated in
In
In some embodiments, e.g., when a number of avatars exceeds a threshold number of avatars, multiple avatars are displayed in a stacked configuration (e.g., such that one or more avatars are at least partially hidden behind another avatar). In some embodiments, an input detected at a location that corresponds to the stack of avatars (e.g., a tap by a contact indicated by focus selector 8108 in
FIGS. 9A1-9A25 illustrate exemplary user interfaces for displaying intensity-reactive and intensity-nonreactive user interface objects, in accordance with some embodiments.
FIG. 9A1 illustrates a user interface 900 on display 950; user interface 900, in the example shown in FIGS. 9A1-9A25, includes a user interface of a menu of applications represented by a plurality of activatable user interface objects (e.g., multiple application icons) arranged in an array, including activatable objects 902 and 904 (e.g., the application icon for launching the Messages application, and the application icon for launching the Weather application).
As shown in FIG. 9A1, user input intensity graph 906 and user input lateral displacement graph 908 indicate that no contact by a user input that corresponds to a request to select an activatable object in user interface 900 has been detected.
FIG. 9A2 illustrates a transition of user interface 900 from the state of that user interface in FIG. 9A1. In particular, FIG. 9A2 shows the position of user input 910 positioned over intensity-nonreactive activatable object 904 in user interface 900. In the example shown in FIG. 9A2, user input 910 corresponds to an input object (e.g., a finger or stylus) detected hovering over a touch-sensitive surface (e.g., touch-sensitive surface 451 or a touch-sensitive surface of touch-screen display 450,
FIG. 9A3 illustrates a transition of user interface 900 from the state of that user interface in either of FIGS. 9A1-9A2. In particular, FIG. 9A3 shows the state of user interface 900 at a current time tc, indicating detection of a contact by user input 910 on the touch-sensitive surface that corresponds to a request to select intensity-nonreactive activatable object 904. As shown in user input intensity graph 906, the intensity (also called contact intensity) of user input 910 is initially below a first intensity threshold ITH. As shown in user input lateral displacement graph 908, the lateral displacement (e.g., the displacement from an initial contact position of the user input) of the user input is zero.
In response to detecting the contact by user input 910 corresponding to intensity-nonreactive activatable object 904, the visual appearance of activatable object 904 is changed by a predetermined amount from that shown in FIGS. 9A1-9A2 (e.g., activatable object 904 is dimmed or darkened, as shown in FIG. 9A3), independent of the contact intensity of user input 910. For example, FIGS. 9A4-9A6 show that although the contact intensity of user input 910 has increased from its value as shown in FIG. 9A3 to values above the first intensity threshold ITH, above the second intensity threshold ITL, and above the third intensity threshold ITD, respectively, the visual appearance of activatable object 904 is maintained at the predetermined amount of change as shown in FIG. 9A3, and is unaffected by the increase in contact intensity of user input 910.
FIG. 9A7 illustrates a transition of user interface 900 from the state of that user interface in FIG. 9A6. In particular, FIG. 9A7 shows the state of user interface 900 at a current time tc upon ceasing to detect the contact by user input 910 (e.g., due to liftoff of the contact) corresponding to activatable object 904. As shown in user input intensity graph 906, the contact intensity of user input 910 has decreased from its intensity as shown in FIG. 9A6 to zero, in accordance with ceasing to detect the contact by user input 910.
In response to ceasing to detect the contact by user input 910 corresponding to intensity-nonreactive activatable object 904 (e.g., in accordance with a determination that user input 910 is a tap gesture), an activation operation corresponding to activatable object 904 is performed. In the example shown in FIG. 9A3, in response to ceasing to detected the contact by user input 910 corresponding to activatable object 904, an application associated with activatable object 904 (e.g., a weather application) is launched and displayed on user interface 900.
FIG. 9A8 is similar to FIG. 9A3 and illustrates a transition of user interface 900 from the state of that user interface in either of FIGS. 9A1-9A2. In particular, FIG. 9A8 shows, at current time tc, the position of user input 911 corresponding to intensity-nonreactive activatable object 904, whose visual appearance is changed by a predetermined amount (e.g., dimmed or darkened) from that shown in FIGS. 9A1-9A2. As shown in user input intensity graph 906, the intensity of user input 911 is initially below intensity threshold ITH, and as shown in user input lateral displacement graph 908, the lateral displacement of the user input from the initial contact position is initially below a lateral displacement threshold Dt.
FIG. 9A9 illustrates a transition of user interface 900 from the state of that user interface in FIG. 9A8. In particular, FIG. 9A9 shows continued lateral movement of user input 911 with respect to user interface 900 (e.g., corresponding to lateral movement of the contact corresponding to user input 911 as the contact is maintained on the touch-sensitive surface, such as a drag gesture). As shown in user input lateral displacement graph 908, the lateral displacement of the user input has increased from that shown in FIG. 9A8 and satisfies (and exceeds) lateral displacement threshold Dt. In accordance with a determination that the lateral displacement of the user input satisfies displacement criteria (e.g., including satisfying lateral displacement threshold Dt), at least a portion of user interface 900 is scrolled in accordance with the lateral movement of the user input.
In the example shown in FIG. 9A9, in response to detecting lateral displacement of user input 911 that satisfies displacement criteria, the visual appearance of intensity-nonreactive activatable object 904 is changed by the predetermined amount back to its initial or previous appearance prior to detecting the contact by user input 911. More specifically, the visual appearance of intensity-nonreactive activatable object 904 is changed instantaneously rather than gradually (e.g., activatable object 904 is undimmed or brightened) back to its previous appearance (e.g., as shown in FIG. 9A1) upon scrolling user interface 900. Moreover, although the contact intensity of user input 911 has increased, as shown in user input intensity graph 906, the change in visual appearance of intensity-nonreactive activatable object 904 is independent of the contact intensity of the user input.
FIG. 9A10 illustrates a transition of user interface 900 from the state of that user interface in FIG. 9A9. In particular, FIG. 9A10 shows the state of user interface 900 at current time tc in accordance with continued lateral movement of user input 911 corresponding to a further increase in lateral displacement. As shown in user input lateral displacement graph 908, the lateral displacement of user input 911 has increased from that shown in FIG. 9A9. As shown in user input intensity graph 906, the contact intensity of user input 911 has increased from that shown in FIG. 9A9 and satisfies (and exceeds) first intensity threshold ITH. However, as discussed above with respect to FIG. 9A9, in response to detecting the lateral displacement of user input 911 that satisfied displacement criteria, the visual appearance of intensity-nonreactive activatable object 904 was changed instantaneously by the predetermined amount back to its initial appearance. Thus, as shown in FIG. 9A10, the visual appearance of intensity-nonreactive activatable object 904 is independent of and not further changed in response to the further increase in lateral displacement or the further increase in contact intensity of user input 911.
FIG. 9A11 illustrates an alternate transition of user interface 900 from the state of that user interface in FIG. 9A1. In particular, FIG. 9A11 shows the position of user input 912 positioned over intensity-reactive activatable object 902 in user interface 900. In the example shown in FIG. 9A11, user input 912 corresponds to an input object (e.g., a finger or stylus) detected hovering over a touch-sensitive surface (e.g., touch-sensitive surface 451 or a touch-sensitive surface of touch-screen display 450,
FIG. 9A12 illustrates a transition of user interface 900 from the state of that user interface in FIG. 9A11. In particular, FIG. 9A12 shows the state of user interface 900 at a current time tc, indicating detection of a contact by user input 912 on the touch-sensitive surface that corresponds to a request to select intensity-reactive activatable object 902. As shown in user input intensity graph 906, the contact intensity of user input 912 is initially below a first intensity threshold ITH. As shown in user input lateral displacement graph 908, the lateral displacement (e.g., the displacement from an initial contact position of the user input) of the user input is zero.
In response to detecting the contact by user input 912 corresponding to intensity-reactive activatable object 902 with an intensity below the first intensity threshold ITH, the visual appearance of activatable object 902 is changed using a second extent of the first transformation (e.g., greater than the first extent). In the example shown in FIG. 9A12, the size of activatable object 902 is decreased from that shown in FIG. 9A11, and a greater amount of the platter displayed behind activatable object 902 is visible as compared to FIG. 9A11.
FIG. 9A13 illustrates a transition of user interface 900 from the state of that user interface in FIG. 9A12. In particular, FIG. 9A13 shows the state of user interface 900 at current time tc in accordance with an increase in the contact intensity of user input 912, such that the contact intensity of user input 912 satisfies the first intensity threshold ITH, as shown in user input intensity graph 906.
In response to detecting the contact by user input 912 corresponding to intensity-reactive activatable object 902 with a contact intensity that satisfies the first intensity threshold ITH, the visual appearance of activatable object 902 is changed using a second transformation in accordance with changes in the detected intensity of the contact on the touch-sensitive surface (e.g., as compared to FIG. 9A12, the size of activatable object 902 is further decreased, and a greater amount of the platter displayed behind activatable object 902 is visible, in accordance with changes in the detected intensity of the contact). In addition, the visual appearance of user interface 900, other than activatable object 902, is changed to include blurring, and optionally shrinking (not shown), of user interface 900, in accordance with changes in the detected intensity of the contact.
FIG. 9A14 illustrates a transition of user interface 900 from the state of that user interface in FIG. 9A13. In particular, FIG. 9A14 shows a greater extent of the changes in the visual appearances of intensity-reactive activatable object 902 and user interface 900 in accordance with a further increase in the contact intensity of user input 912. As the contact intensity of user input 912 increases above the first intensity threshold ITH, but remains below a second intensity threshold ITL, as shown in user input intensity graph 906, the visual appearance of intensity-reactive activatable object 902 is further changed using a greater extent of the second transformation (e.g., as compared to FIG. 9A13, the size of activatable object 902 is even further decreased, and an even greater amount of the platter displayed behind activatable object 902 is visible). In addition, the visual appearance of user interface 900, excluding activatable object 902, includes a greater degree of blurring, and optionally a greater degree of shrinking (not shown).
FIG. 9A15 illustrates a transition of user interface 900 from the state of that user interface in FIG. 9A14. In particular, FIG. 9A14 shows the state of user interface 900 at a current time tc in accordance with an increase in the contact intensity of user input 912 corresponding to intensity-reactive activatable object 902. As shown in user input intensity graph 906, the contact intensity of user input 912 satisfies the second intensity threshold ITL. In accordance with the contact intensity of user input 912 satisfying the second intensity threshold ITL, a preview of related content (e.g., a quick actions menu) associated with intensity-reactive activatable object 902 is displayed as activatable object 914 and, optionally, a tactile output 916 is generated.
FIG. 9A16 illustrates an alternate transition of user interface 900 from the state of that user interface in FIG. 9A1. In particular, FIG. 9A16 shows the state of user interface 900 at a current time tc, indicating detection of a contact by user input 912 on the touch-sensitive surface that corresponds to a request to select intensity-reactive activatable object 902. As shown in user input intensity graph 906, the contact intensity of user input 912 is initially below a first intensity threshold ITH. As shown in user input lateral displacement graph 908, the lateral displacement (e.g., the displacement from an initial contact position of the user input) of the user input is below a lateral displacement threshold Dt.
In response to detecting the contact by user input 912 corresponding to intensity-reactive activatable object 902 with an intensity below the first intensity threshold ITH, the visual appearance of activatable object 902 is changed using the first transformation. In the example shown in FIG. 9A16, the size of activatable object 902 is decreased from that shown in FIG. 9A1, for example, and a platter is displayed behind activatable object 902 in the area previously occupied by activatable object 902 prior to its size being decreased).
FIG. 9A17 illustrates a transition of user interface 900 from the state of that user interface in FIG. 9A16. In particular, FIG. 9A17 shows the state of user interface 900 at current time tc in accordance with continued lateral movement of user input 912 with respect to user interface 900. As shown in user input lateral displacement graph 908, the lateral displacement of the user input has increased from that shown in FIG. 9A16 and satisfies (and exceeds) lateral displacement threshold Dt. In accordance with a determination that the lateral displacement of user input 912 satisfies displacement criteria (e.g., including satisfying lateral displacement threshold Dt), a third transformation is applied to at least a portion of user interface 900 including activatable object 902 such that the portion of user interface 900 is scrolled in accordance with the lateral displacement of user input 912.
In the example shown in FIG. 9A17, the third transformation is applied such that at least a portion of user interface 900 is scrolled in a first direction in accordance with the lateral displacement of user input 912 and a position of activatable object 902 is changed accordingly. Furthermore, the change in the visual appearance of intensity-reactive activatable object 902 using the first transformation is gradually and dynamically reduced from that shown in FIG. 9A16 in accordance with the lateral movement of user input 912, such that the visual appearance of activatable object 902 (other than its position) is gradually changed back to its initial or previous appearance prior to detecting user input 912. More specifically, FIG. 9A17 shows that the size of activatable object 902 is increased from that shown in FIG. 9A16, and a lesser amount of the platter displayed behind activatable object 902 is visible, upon scrolling user interface 900 in accordance with the lateral movement of user input 912.
FIG. 9A18 illustrates a transition of user interface 900 from the state of that user interface in FIG. 9A17. In particular, FIG. 9A18 shows a greater extent of the changes in the visual appearances of activatable object 902 and user interface 900 at current time tc in accordance with continued lateral movement of user input 912 with respect to user interface 900 corresponding to an increase in the lateral displacement of user input 912. As the lateral displacement of user input 912 is further increased from that shown in FIG. 9A17, as shown in user input lateral displacement graph 908, a greater extent of the third transformation is applied such that the portion of user interface 900 including activatable object 902 is further scrolled in the first direction, and the change in the visual appearance of intensity-reactive activatable object 902 due to the first transformation is gradually and dynamically reduced even further. More specifically, FIG. 9A18 shows that the size of intensity-reactive activatable object 902 is increased to its original size as shown in FIG. 9A1, for example, and the platter is no longer visible, in accordance with the further increase in lateral displacement of user input 912. In some embodiments, the application of the first transformation to activatable object 902 is completely reduced in accordance with a determination that the lateral displacement of user input 912 includes a predefined threshold amount of lateral displacement (e.g., if the lateral displacement of the user input satisfies a second lateral displacement threshold, not shown in FIG. 9A18).
FIG. 9A19 illustrates a transition of user interface 900 from the state of that user interface in FIG. 9A18. In particular, FIG. 9A19 shows the changes in the visual appearances of activatable object 902 and user interface 900 in accordance with continued lateral movement of user input 912 corresponding to a decrease in the lateral displacement of user input 912 as the contact is maintained on the touch-sensitive surface. As shown in user input lateral displacement graph 908, the lateral displacement of user input 912 has decreased from that shown in FIG. 9A18 but remains above lateral displacement threshold Dt. In accordance with the decrease in lateral displacement, the visual appearance of intensity-reactive activatable object 902 is changed by gradually reapplying the first transformation (e.g., FIG. 9A19 shows that the size of activatable object 902 is again decreased, and the platter is again displayed behind activatable object 902 in the area previously occupied by activatable object 902 prior to its size being decreased). Furthermore, in accordance with the decrease in lateral displacement of user input 912, the third transformation is gradually reduced such that the scrolling of the portion of user interface 900 including activatable object 902 in the first direction is reversed (i.e., scrolled in a second direction opposite the first direction).
FIG. 9A20 illustrates a transition of user interface 900 from the state of that user interface in FIG. 9A19. In particular, FIG. 9A20 shows the changes in the visual appearances of activatable object 902 and user interface 900 in accordance with continued lateral movement of user input 912 corresponding to a further decrease in lateral displacement as the contact is maintained on the touch-sensitive surface. As shown in user input lateral displacement graph 908, the lateral displacement of user input 912 has decreased from that shown in FIG. 9A19 and is below lateral displacement threshold Dt. In accordance with the decrease in lateral displacement, the visual appearance of intensity-reactive activatable object 902 is further changed by continuing to gradually reapply the first transformation (e.g., FIG. 9A20 shows that the size of activatable object 902 is further decreased, and a greater amount of the platter displayed behind activatable object 902 is again visible). Furthermore, in accordance with the further reduction in lateral displacement of user input 912, the third transformation is further reduced such that the scrolling of the portion of user interface 900 including activatable object 902 in the first direction is further reversed (i.e., scrolled in the second direction opposite the first direction back to the initial position as shown in FIG. 9A16).
It is noted that FIGS. 9A19-9A20 illustrate both that the portion of user interface 900 is scrolled in the second direction back to its initial position and that the first transformation is reapplied to intensity-reactive activatable object 902 as the lateral displacement of user input 912 decreases while the contact is maintained on the touch-sensitive surface. However, in some embodiments, the portion of user interface 900 is scrolled in the second direction back to its initial position without the first transformation being reapplied to intensity-reactive activatable object 902, such that the visual appearance of activatable object 902 (other than its position) is maintained as shown in FIG. 9A18.
FIGS. 9A21-9A22 illustrate a series of transitions of user interface 900 from the state of that user interface in FIG. 9A20. In particular, FIGS. 9A21-9A22 show the changes in the visual appearances of activatable object 902 in response to ceasing to detect the contact corresponding to user input 912. As shown in user input intensity graph 906, the contact intensity of user input 912 has decreased from its intensity as shown in FIG. 9A20 to zero, in accordance with ceasing to detect the contact (e.g., due to liftoff of the contact from the touch-sensitive surface).
In FIGS. 9A21-9A22, in response to ceasing to detect the contact, the change in the visual appearance of intensity-reactive activatable object 902 due to the first transformation is gradually and dynamically reduced, such that the visual appearance of intensity-reactive activatable object 902 is gradually changed back to its initial or previous appearance prior to detecting the contact by user input 912. More specifically, FIG. 9A21 shows that the size of activatable object 902 is increased from that shown in FIG. 9A20, and a lesser amount of the platter displayed behind activatable object 902 is visible, and FIG. 9A22 shows that the size of activatable object 902 is subsequently increased to its original size as shown in FIG. 9A1, for example, and the platter is no longer visible, in response to ceasing to detect the contact.
In some embodiments, in response to ceasing to detect the contact by user input 912, and in accordance with a determination that user input 912 corresponds to a tap gesture, an activation operation corresponding to activatable object 902 is performed (e.g., the application, such as a messaging application, associated with activatable object 902 is launched) in conjunction with changing the visual appearance of activatable object 902 by gradually reducing the first transformation.
FIG. 9A23 illustrates an alternate transition of user interface 900 from the state of that user interface in FIG. 9A1. In particular, FIG. 9A23 shows the state of user interface 900 at a current time tc, indicating detection of a contact by user input 913 on the touch-sensitive surface that corresponds to a request to select intensity-reactive activatable object 902. As shown in user input intensity graph 906, the contact intensity of user input 913 is initially below a first intensity threshold ITH. In addition, the total amount of time that the contact by user input 913 has been maintained on the touch-sensitive surface is below a first time threshold TH. Also, as shown in user input lateral displacement graph 908, the lateral displacement (e.g., the displacement from an initial contact position of the user input) of the user input is zero. In response to detecting the contact by user input 913 corresponding to activatable object 902, the visual appearance of activatable object 902 is changed using the first transformation (e.g., FIG. 9A23 shows that the size of activatable object 902 is decreased from that shown in FIG. 9A1, for example, and a platter is displayed behind activatable object 902 in the area previously occupied by activatable object 902 prior to its size being decreased).
FIG. 9A24 illustrates a transition of user interface 900 from the state of that user interface in FIG. 9A23. In particular, FIG. 9A24 shows that, at time tc, the contact corresponding to user input 913 is maintained on the touch-sensitive display for an additional amount of time since that shown in FIG. 9A23. As shown in user input intensity graph 906, the intensity of user input 913 remains below the first intensity threshold ITH, and the total amount of time that the contact by user input 913 has been maintained on the touch-sensitive surface satisfies the first time threshold TH (e.g., a time-dependent long press hint threshold) but does not satisfy a second time threshold TLP (e.g., a time-dependent long press transformation threshold).
In accordance with the contact being maintained on the touch-sensitive surface such that the total amount of time that the contact is maintained satisfies the first time threshold TH without the contact meeting the first intensity threshold ITH or the lateral displacement threshold Dt, the visual appearance of intensity-reactive activatable object 902 is changed using a fourth transformation. In the example shown in FIG. 9A24, the brightness of activatable object 902 is decreased such that activatable object 902 is dimmed or darkened as compared to FIG. 9A23. The platter displayed behind activatable object 902 remains visible to the same extent.
FIG. 9A25 illustrates a transition of user interface 900 from the state of that user interface in FIG. 9A24. In particular, FIG. 9A25 shows the state of user interface 900 at current time tc in accordance with an increase in the contact intensity of user input 913. As shown in user input intensity graph 906, the intensity of user input 79 has increased from that shown in FIG. 9A24 to above the first intensity threshold ITH. In accordance with detecting the increase in contact intensity, and in accordance with a determination that the contact intensity satisfies the first intensity threshold ITH, the fourth transformation is dynamically reduced as the contact intensity increases (e.g., as shown in FIG. 9A25, the decrease in brightness of activatable object 902 is reversed such that activatable object 902 is undimmed in accordance with the increase in the contact intensity of user input 913 to above the first intensity threshold ITH).
FIGS. 9B1-9B10 illustrate exemplary user interfaces for displaying intensity-reactive and intensity-nonreactive user interface objects, in accordance with some embodiments.
FIG. 9B1 illustrates a user interface 901 on display 950; in the example shown in FIGS. 9B1-9B10, user interface 901 includes a user interface of a mail application (e.g., e-mail client module 140,
As shown in FIG. 9B1, user input intensity graph 906 and user input lateral displacement graph 908 indicate that no user input that corresponds to a request to select an activatable object in user interface 900 has been detected.
FIG. 9B2 illustrates a transition of user interface 901 from the state of that user interface in FIG. 9B1. In particular, FIG. 9B2 shows the state of user interface 900 at a current time tc, indicating detection of a contact by user input 915 on the touch-sensitive surface that corresponds to a request to select intensity-reactive activatable object 930. As shown in user input intensity graph 906, the contact intensity of user input 915 is initially below the first intensity threshold ITH. As shown in user input lateral displacement graph 908, the lateral displacement of the user input is initially below lateral displacement threshold Dt.
In response to detecting the contact by user input 915 corresponding to intensity-reactive activatable object 930, the visual appearance of activatable object 930 is changed using a first transformation. In the example shown in FIG. 9B2, the size of activatable object 930 is decreased (e.g., displaying movement of activatable object 930 downwards in a virtual z direction) and activatable object 930 is dimmed or darkened, as compared to its visual appearance as shown in FIG. 9B1. Alternatively, in some embodiments, the size of activatable object 930 is increased (e.g., displaying movement of activatable object 930 upwards in a virtual z direction) rather than decreased.
FIG. 9B3 illustrates a transition of user interface 901 from the state of that user interface in FIG. 9B2. In particular, FIG. 9B3 shows the state of user interface 901 at current time tc in accordance with an increase in the contact intensity of user input 915 (e.g., consistent with a light press gesture), such that the contact intensity of user input 915 satisfies the first intensity threshold ITH, as shown in user input intensity graph 906, while the lateral displacement of user input 915, as shown in user input lateral displacement graph 908, remains below lateral displacement threshold Dt.
In accordance with a determination that the contact intensity of user input 915 satisfies the first intensity threshold ITH, the visual appearance of activatable object 930 is changed using a second transformation in accordance with changes in the detected intensity of the contact on the touch-sensitive surface (e.g., as compared to FIG. 9B2, the size of activatable object 930 is increased, such as to indicate movement of activatable object upwards in a virtual z direction, and the brightness of activatable object 930 is increased). In addition, the visual appearance of user interface 901, other than activatable object 930, is changed to include blurring, and optionally shrinking (not shown), of user interface 901 excluding activatable object 930.
FIG. 9B4 illustrates a transition of user interface 901 from the state of that user interface in FIG. 9B3. In particular, FIG. 9B4 shows a greater extent of the changes in the visual appearances of intensity-reactive activatable object 930 and user interface 901 in accordance with a further increase in the contact intensity of user input 915 (e.g., further consistent with a light press input). As shown in user input lateral displacement graph 908, the lateral displacement of user input 915 remains below lateral displacement threshold Dt. As the contact intensity of user input 915 increases above the first intensity threshold ITH, but remains below a second intensity threshold ITL, as shown in user input intensity graph 906, the visual appearance of intensity-reactive activatable object 930 is further changed using a greater extent of the second transformation (e.g., as compared to FIG. 9B3, the brightness and size of activatable object 930 are further increased). In addition, the visual appearance of user interface 901, excluding activatable object 930, includes a greater degree of blurring, and optionally a greater degree of shrinking (not shown).
FIG. 9B5 illustrates a transition of user interface 901 from the state of that user interface in FIG. 9B4. In particular, FIG. 9B5 shows the state of user interface 901 at a current time tc in accordance with an increase in the contact intensity of user input 915 corresponding to intensity-reactive activatable object 930. As shown in user input intensity graph 906, the contact intensity of user input 915 satisfies the second intensity threshold ITL, while the lateral displacement of user input 915 remains below lateral displacement threshold Dt, as shown in user input lateral displacement graph 908. In accordance with the contact intensity of user input 915 satisfying the second intensity threshold ITL (e.g., corresponding to a light press gesture), a preview of related content (e.g., a portion of an electronic mail message) associated with intensity-reactive activatable object 930 is displayed as user interface object 931 and, optionally, a tactile output 917 is performed.
FIG. 9B6 illustrates a transition of user interface 901 from the state of that user interface in FIG. 9B5. In particular, FIG. 9B6 shows the state of user interface 901 at a current time tc in accordance with a further increase in the contact intensity of user input 915 corresponding to intensity-reactive activatable object 930, FIG. 9B4, and user interface object 931, FIG. 9B5. As shown in user input intensity graph 906, the contact intensity of user input 915 satisfies the third intensity threshold ITD, while the lateral displacement of user input 915 remains below lateral displacement threshold Dt, as shown in user input lateral displacement graph 908. In accordance with the contact intensity of user input 915 satisfying the third intensity threshold ITD (e.g., corresponding to a deep press input), the related content (e.g., the electronic mail message) associated with intensity-reactive activatable object 930 is displayed as user interface object 931 and, optionally, a tactile output 918 is generated.
FIG. 9B7 illustrates an alternate transition of user interface 901 from the state of that user interface in FIG. 9B4. In particular, FIG. 9B7 shows the state of user interface 901 at current time tc in accordance with resumed lateral movement of user input 915 with respect to user interface 901 and a decrease in the contact intensity of user input 915. As shown in user input lateral displacement graph 908, the lateral displacement of user input 915 has increased from that shown in FIG. 9B4 to above lateral displacement threshold Dt (e.g., consistent with a scroll input). In accordance with a determination that the lateral displacement of user input 915 satisfies displacement criteria (e.g., including satisfying lateral displacement threshold Dt), a third transformation is applied to at least a portion of user interface 901 including activatable object 930 such that the portion of user interface 901 is scrolled in accordance with the lateral displacement of user input 915.
Moreover, in accordance with the increase in the lateral displacement of user input 915 and with the decrease in the contact intensity of user input 915, as shown in user input intensity graph 906, the change in visual appearance of activatable object 930 using the second transformation is dynamically reduced (e.g., the brightness and size of activatable object 930 are decreased). In addition, the visual appearance of user interface 901 is changed to include a lesser degree of blurring, and optionally a lesser degree of shrinking (not shown), than in FIG. 9B4.
FIG. 9B8 illustrates a transition of user interface 901 from the state of that user interface in FIG. 9B7. In particular, FIG. 9B8 shows a greater extent of the changes in the visual appearances of activatable object 930 and user interface 901 in accordance with an increase in the contact intensity of user input 915 (e.g., again consistent with a light press gesture). As shown in user input intensity graph 906, the contact intensity of user input 915 continues to satisfy the first intensity threshold ITH (while remaining below the second intensity threshold ITL). As shown in user input lateral displacement graph 908, the lateral displacement of user input 915 has not changed from that shown in FIG. 9B7, although the lateral displacement continues to satisfy lateral displacement threshold Dt.
In accordance with the increase in contact intensity of user input 915 above the first intensity threshold ITH (but below the second intensity threshold ITL), the visual appearance of intensity-reactive activatable object 930 is changed using a greater extent of the second transformation (e.g., as compared to FIG. 9B7, the brightness and size of activatable object 930 are increased). In addition, the visual appearance of user interface 901, excluding activatable object 930, includes a greater degree of blurring, and optionally a greater degree of shrinking (not shown).
FIG. 9B9 illustrates a transition of user interface 901 from the state of that user interface in FIG. 9B8. In particular, FIG. 9B9 shows the state of user interface 901 at current time tc in accordance with resumed lateral movement of user input 915 with respect to user interface 901 and a decrease in the contact intensity of user input 915. In accordance with the decrease in the contact intensity of user input 915, as shown in user input intensity graph 906, the change in visual appearance of activatable object 930 using the second transformation is dynamically reduced (e.g., the brightness and size of activatable object 930 are decreased). In addition, the visual appearance of user interface 900 is changed to include a lesser degree of blurring, and optionally a lesser degree of shrinking (not shown), than in FIG. 9B8.
Also, as shown in user input lateral displacement graph 908, the lateral displacement of user input 915 has increased from that shown in FIG. 9B8, while continuing to satisfy lateral displacement threshold Dt (e.g., consistent with a scroll gesture). In accordance with a determination that the lateral displacement of user input 915 satisfies displacement criteria (e.g., including satisfying lateral displacement threshold Dt), the third transformation is reapplied such that the portion of user interface 901 including activatable object 930 is scrolled in accordance with the lateral displacement of user input 915.
FIG. 9B10 illustrates a transition of user interface 901 from the state of that user interface in FIG. 9B9. In particular, FIG. 9B10 shows the state of user interface 901 at current time tc in accordance with a further increase in lateral displacement of user input 915 and a further decrease in contact intensity of user input 915. As shown in user input lateral displacement graph 908, the lateral displacement of user input 915 has increased further from that shown in FIG. 9B9 (e.g., further consistent with a scroll gesture). In accordance with the further increase in the lateral displacement of user input 915, a greater extent of the third transformation is applied such that the portion of user interface 901 including activatable object 930 is further scrolled.
Moreover, in accordance with the further increase in the lateral displacement of user input 915 and with the further decrease in the contact intensity of user input 915 to below the first intensity threshold ITH, as shown in user input intensity graph 906, the second transformation of activatable object 930 is completely reduced such that the brightness and size of activatable object 930 are restored to their initial appearance prior to detecting user input 915. In addition, the blurring of user interface 901 is completely reduced. In some embodiments, the application of the second transformation to activatable object 930 and the blurring of user interface 901 are completely reduced in accordance with a determination that the lateral displacement of user input 915 includes a predefined threshold amount of lateral displacement (e.g., if the lateral displacement of the user input satisfies a second lateral displacement threshold, not shown in FIG. 9B10).
FIGS. 9C1-9C19 illustrate exemplary user interfaces for displaying control settings interfaces for control functions for remote devices (e.g., another device that is in wireless communication with, and is controlled by the electronic device that is displaying the user interfaces), in accordance with some embodiments.
FIG. 9C1 illustrates a first user interface 903 including one or more activatable objects 962-1 through 962-8. In FIG. 9C1, activatable objects 962-1 through 962-8 are associated with control functions including, for example, a temperature or thermostat icon 962-1 for controlling temperature settings of a remote temperature control, a fan icon 962-2 for controlling fan settings for a remote fan, shades icon 962-3 for controlling window shade or blinds settings for a remote window shade or blinds, lights icon 962-4 for controlling lights settings (e.g., brightness or color) for a remote light, doors icon 962-5 for controlling door settings (e.g. locking or unlocking) of a remote door lock, camera icon 962-6 for controlling or viewing security camera feeds of a remote security camera, smoke alarm icon 962-7 for controlling or viewing smoke detector statuses of a remote smoke detector, and sleep icon 962-8 for setting one or more control functions for a set of associated remote devices to a sleep or low power state.
FIG. 9C2 is similar to FIG. 9C1 except that FIG. 9C2 shows the state of user interface 903 at a current time tc, indicating detection of a contact by user input 954 on a touch-sensitive surface (e.g., touch-sensitive surface 451 or a touch-sensitive surface of touch-screen display 450,
FIG. 9C3 illustrates a transition of first user interface 903 from the state of that user interface in FIG. 9C2. In particular, FIG. 9C3 shows the state of user interface 903 at current time tc in accordance with an increase in the contact intensity of user input 954, such that the contact intensity of user input 954 satisfies the first intensity threshold ITH, as shown in user input intensity graph 906.
In response to detecting the contact by user input 954 corresponding to lights icon 962-4 with a contact intensity that satisfies the first intensity threshold ITH, the visual appearance of lights icon 962-4 is changed (e.g., as compared to FIG. 9C2, the size of lights icon 962-4 is decreased, and a platter is displayed behind lights icon 962-4 in the area previously occupied by lights icon 962-4 prior to its size being decreased), in accordance with changes in the detected intensity of the contact. In addition, the visual appearance of user interface 901, other than lights icon 962-4, is changed to include blurring, and optionally shrinking (not shown), of user interface 901, in accordance with changes in the detected intensity of the contact.
FIG. 9C4 illustrates a second user interface 951, displayed at current time tc in accordance with a further increase in the contact intensity of user input 954 such that the contact intensity satisfies a second intensity threshold ITL. In addition, in accordance with the contact intensity of user input 954 satisfying the second intensity threshold ITL, a tactile output 920 is optionally output. The second user interface 951 includes a second activatable user interface object 958 that has seven state options (e.g., state options 958-0 through 958-6) that correspond to available values for a control function that controls a setting corresponding to lights icon 962-4, FIG. 9C2. In the example shown in FIG. 9C4, the lowest value 958-0 corresponds to an off state of the control function, whereas the values 958-1 through 958-6 correspond to varying degrees of an on state of the control function. Also, as shown in FIG. 9C4, a first value 958-3 is selected as a current value for the control function.
In some embodiments, when second user interface 951 is displayed, if the contact by user input 954 lifts off without moving across the touch-sensitive surface, second user interface 951 continues to be displayed so that a user can make a second input on the second user interface to adjust the setting of the control function, as described in further detail herein.
Moreover, in some embodiments, as shown in the example illustrated in FIG. 9C4, second user interface 951 is displayed over a portion of first user interface 903 (e.g., second user interface 951 may be displayed as a platter over first user interface 903). The visual appearance of first user interface 903, as shown in FIG. 9C4, is optionally changed to include blurring.
FIG. 9C5 is similar to FIG. 9C4, except that FIG. 9C5 does not show first user interface 903 displayed behind second user interface 951. For ease of discussion, FIG. 9C5 and subsequent illustrations show second user interface 952 displayed on display 950 without showing any portion of first user interface 903.
FIG. 9C6 illustrates a transition of second user interface 952 from the state of that user interface in FIG. 9C5. In particular, FIG. 9C6 shows the state of user interface 952 in accordance with lateral movement of user input 954. In some embodiments, including the example shown in FIG. 9C6, the lateral movement of user input 954 as shown in FIG. 9C6 is a continuation of the contact by user input 954, FIG. 9C2, while maintaining a contact intensity that satisfies the second intensity threshold ITL.
In accordance with the lateral movement of user input 954 corresponding to a first amount of lateral displacement of the contact in a first direction (e.g., upward) from an initial contact position, the current value for the control function as shown by activatable user interface object 958 is increased from the first value 958-3 to a second value 958-4. In addition, the visual appearance of control icon 907 representing the state of the control function is changed accordingly to indicate that the current value for the control function has been increased (e.g., that the brightness of a corresponding light bulb has been increased).
FIG. 9C7 illustrates a transition of second user interface 952 from the state of that user interface in FIGS. 9C5-9C6. In particular, FIG. 9C7 shows further lateral movement of user input 954 corresponding to a second amount (e.g., greater than the first amount) of lateral displacement of the contact in the first direction (e.g., upward). In accordance with the additional lateral displacement of user input 954 in the first direction, the current value for the control function as shown by activatable user interface object 958 is further increased to a third value 958-5. In addition, the visual appearance of control icon 907 representing the state of the control function is changed accordingly to indicate that the current value for the control function has been further increased (e.g., that the brightness of the light bulb has been further increased).
FIG. 9C8 illustrates a transition of second user interface 952 from the state of that user interface in FIGS. 9C5-9C7. In particular, FIG. 9C8 shows even further lateral movement of user input 954 corresponding to a third amount (e.g., greater than the first and second amounts) of lateral displacement of the contact in the first direction (e.g., upward). In accordance with the additional lateral displacement of user input 954 in the first direction, the current value for the control function as shown by activatable user interface object 958 is even further increased to a fourth and maximum value 958-6. In addition, the visual appearance of control icon 907 representing the state of the control function is changed accordingly to indicate that the current value for the control function has been further increased (e.g., that the brightness of the light bulb has been further increased to the maximum value).
FIG. 9C9 illustrates a transition of second user interface 952 from the state of that user interface in FIGS. 9C5-9C8. In particular, FIG. 9C9 shows further lateral movement of user input 954 corresponding to a fourth amount of lateral displacement of the contact in the first direction, where the fourth amount is greater than the third amount. As shown in FIG. 9C9, the current value for the control function is maintained at the maximum value, and the visual appearance of control icon 907 is maintained accordingly. In addition, in accordance with the additional lateral displacement of user input 954 in the first direction, an animation of activatable user interface object 958 is displayed to show activatable user interface object 958 elongating (e.g., transforming into a third activatable user interface object that is an elongated form of activatable user interface object 958). Optionally, a tactile output 921 is output in conjunction with displaying the animation of activatable user interface object 958 elongating.
FIG. 9C10 illustrates a transition of second user interface 952 from the state of that user interface in FIG. 9C9. FIG. 9C10 shows a state of second user interface 952 in accordance with subsequently ceasing to detect the contact by user input 954 (e.g., by detecting liftoff of the contact by user input 954) at the position corresponding to the fourth amount of lateral displacement of the contact in the second direction. In accordance with ceasing to detect the contact, an animation of activatable user interface object 958 is displayed to show the elongated form of activatable user interface object 958 (as shown in FIG. 9C9) contracting and returning to its previous size (e.g., an animation of the third activatable user interface object that is an elongated form of activatable user interface object 958 transforming back into activatable user interface object 958). Optionally, a tactile output 922 is output in conjunction with ceasing to detect the contact and/or in conjunction with displaying the animation of activatable user interface object 958. In some embodiments, tactile output 922 is output as an alternative to outputting tactile output 921 as illustrated in FIG. 9C9.
FIG. 9C11 is similar to FIG. 9C6, except that FIG. 9C11 illustrates lateral movement of user input 954 corresponding to the first amount of lateral displacement of the contact in a second direction (e.g., downward) from the initial contact position. In accordance with the lateral displacement of user input 954 by the first amount in the second direction, the current value for the control function as shown by activatable user interface object 958 is decreased to from the first value 958-3 to a fifth value 958-2. In addition, the visual appearance of control icon 907 representing the state of the control function is changed accordingly to indicate that the current value for the control function has been decreased (e.g., that the brightness of the light bulb has been decreased).
FIG. 9C12 illustrates a transition of second user interface 952 from the state of that user interface in FIGS. 9C6 and 9C11. In particular, FIG. 9C12 shows further lateral movement of user input 954 corresponding to the second amount of lateral displacement of the contact in the second direction (e.g., downward). In accordance with the additional lateral displacement of user input 954 in the second direction, the current value for the control function as shown by activatable user interface object 958 is further decreased to a sixth value 958-1. In addition, the visual appearance of control icon 907 representing the state of the control function is changed accordingly to indicate that the current value for the control function has been further decreased (e.g., that the brightness of the light bulb has been further decreased).
FIG. 9C13 illustrates a transition of second user interface 952 from the state of that user interface in FIGS. 9C6 and 9C11-9C12. In particular, FIG. 9C13 shows even further lateral movement of user input 954 corresponding to the third amount of lateral displacement of the contact in the second direction (e.g., downward). In accordance with the additional lateral displacement of user input 954 in the second direction, the current value for the control function as shown by activatable user interface object 958 is even further decreased to a seventh and minimum value 958-0, corresponding to an off state of the control function. In addition, the visual appearance of control icon 907 representing the state of the control function is changed accordingly to indicate that the current value for the control function has been even further decreased to the minimum value (e.g., that the light bulb has been turned off).
FIG. 9C14 illustrates a transition of second user interface 952 from the state of that user interface in FIG. 9C13. In particular, FIG. 9C14 shows further lateral movement of user input 954 corresponding to a fifth amount of lateral displacement of the contact in the second direction, where the fifth amount is greater than the third amount. As shown in FIG. 9C14, the current value for the control function is maintained at the minimum value, and the visual appearance of control icon 907 is maintained accordingly. In addition, in accordance with the additional lateral displacement of user input 954 in the second direction, an animation of activatable user interface object 958 is displayed to show activatable user interface object 958 elongating (e.g., transforming into a third activatable user interface object that is an elongated form of activatable user interface object 958). Optionally, a tactile output 923 is output in conjunction with displaying the animation of activatable user interface object 958 elongating.
FIG. 9C15 illustrates a transition of second user interface 952 from the state of that user interface in FIG. 9C14. As noted above, in some embodiments, FIG. 9C6 and subsequent FIGS. 9C11-9C14 correspond to lateral movement of user input 954 being detected while the contact by user input 954 continues to be maintained on the touch-sensitive surface. FIG. 9C15 shows a state of second user interface 952 in accordance with subsequently ceasing to detect the contact by user input 954 (e.g., by detecting liftoff of the contact by user input 954) at the position corresponding to the fifth amount of lateral displacement of the contact in the second direction. In accordance with ceasing to detect the contact, an animation of activatable user interface object 958 is displayed to show the elongated form of activatable user interface object 958 (as shown in FIG. 9C14) contracting and returning to its previous size (e.g., an animation of the third activatable user interface object that is an elongated form of activatable user interface object 958 transforming back into activatable user interface object 958). Optionally, a tactile output 924 is output in conjunction with ceasing to detect the contact and/or in conjunction with displaying the animation of activatable user interface object 908. In some embodiments, tactile output 924 is output as an alternative to outputting tactile output 923 as illustrated in FIG. 9C14.
FIG. 9C16 illustrates a further transition of second user interface 952 from the state of that user interface in FIG. 9C15. In particular, subsequent to ceasing to detect the contact by user input 954 (e.g., by detecting liftoff of the contact by user input 954) and displaying the animation of activatable user interface 958, second user interface 952 ceases to be displayed, and first user interface 903 is displayed instead. In some embodiments, an animation is displayed of the activatable user interface object 958 transforming into lights icon 962-4. In addition, in accordance with ceasing to detect the contact while the current value for the control function is set to the minimum value corresponding to an off state of the control function, first user interface 903 indicates that the control function corresponding to lights icon 962-4 has been set to the off state.
FIGS. 9C17-9C19 illustrate exemplary user interfaces for displaying a secondary settings interface, in accordance with some embodiments.
FIG. 9C17 illustrates an alternate transition of second user interface 952 from the state of that user interface in FIG. 9C5. In particular, FIG. 9C17 shows a second user interface 952 displayed at current time tc in accordance with ceasing to detect the contact by user input 954 prior to detecting movement of the contact across the touch-sensitive surface. As noted above, in some embodiments, when the second user interface is displayed, ceasing to detect the contact by the user input prior to detecting movement of the contact across the touch-sensitive surface results in the second user interface continuing to be displayed so that a user can make a second input on the second user interface to adjust the setting of the control function. Accordingly, FIG. 9C17 illustrates that second user interface 952 continues to be displayed subsequent to ceasing to detect the contact by user input 954 prior to detecting lateral movement of the contact.
FIG. 9C18 illustrates a transition of second user interface 952 from the state of that user interface in FIG. 9C17. In particular, FIG. 9C18 shows the position of a contact by a second user input 955 with respect to second user interface 952. In addition, indicia 909 (e.g., pagination indicia or dots) indicate that second user interface 952 corresponds to a first page of settings interfaces.
FIG. 9C19 illustrates a transition from second user interface 952 as shown in FIG. 9C18 to a third user interface 953 in accordance with lateral movement of user input 955 in a third direction (e.g., toward the left). In particular, FIG. 9C19 shows third user interface 953 including additional activatable user interface objects 960-1 through 960-7 that correspond to available values for a secondary setting of the control function (e.g., for selecting a color of the light bulb). FIG. 9C19 shows, for example, that the currently selected color for the light bulb is that of activatable object 960-1. In addition, indicia 909 indicate that third user interface 953 corresponds to a second page of settings interfaces.
As described below, the method provides (1000) an intuitive way to interact with an application launching icon, allowing the user to choose to launch the application or accessing a subset of functions or content from the application without launching the application using a single touch input (e.g., by controlling an intensity of a contact before terminating the contact). The method reduces the number, extent, and/or nature of the inputs from a user to interact with an electronic device, and avoids fully launching an application when not necessary, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to enter inputs faster and more efficiently conserves power and increases the time between battery charges.
The device concurrently displays (1002), on the display: a background user interface (e.g., the user interface is the notification center interfaces (e.g., 5026, 5036), the lock screen (e.g., 5012), the wake screen (e.g., 5002), the user interface of another application (e.g., 5050), the home screen (e.g., 5024), etc.); and a first version of a notification (e.g., a short version of the notification or a standard version of the notification) associated with a first application (e.g., notification 5028, notification 5038, notification 5104), wherein: the first version of the notification has a first size, the first version of the notification includes first content, and the first version of the notification is overlaid on the background user interface. This is illustrated in FIGS. 5A1-5A6 with notifications (e.g., 5028, 5038, 5104) overlaid on various types of background user interfaces (e.g., 5002, 5012, 5024, 5026, 5036, and 5050). In some embodiments, the background user interface is deemphasized (e.g., blurred or darkened) when the first version of the notification is overlaid on top of the background user interface.
While displaying the first version of the notification associated with the first application overlaid on the background user interface, the device detects (1004) a first portion of a first input that includes detecting a first contact at a location on the touch-sensitive surface that corresponds to the first version of the notification (e.g., contact 5052 on notification 5028 in FIG. 5B2, contact 5064 on notification 5028 in FIG. 5C2, contact 5076 on notification 5038 in FIG. 5F2, contact 5106 on notification 5104 in FIG. 5I2).
In response (1006) to detecting the first portion of the first input: in accordance with a determination that the first portion of the first input meets application-launching criteria, wherein the application-launching criteria do not require that a characteristic intensity of the first contact on the touch-sensitive surface meet a preview intensity threshold in order for the application-launching criteria to be met (e.g., in some embodiments, the application-launching criteria are met when the first input is a tap input), the device initiates (1008) a process to launch the first application, wherein launching the first application includes ceasing to display the background user interface and displaying a user interface associated with the first application (e.g., launching the first application if the phone is unlocked, and displaying an “unlock your phone” notification or an authentication interface if the phone is locked and launching the first application once correct authentication information is received). This is illustrated in FIGS. 5B2-5B4, for example. In some embodiments, the application-launching criteria are met when the device detects a tap input with a duration that is below a threshold duration without regard to whether or not the characteristic intensity of the contact exceeded the preview intensity threshold. In some embodiments, the application-launching criteria are met when the device detects liftoff of the contact without the characteristic intensity of the contact having reached the preview intensity threshold since touchdown of the contact. In some embodiments, the application-launching criteria are met when the device detects liftoff of the contact without the characteristic intensity of the contact having exceeded the first intensity for at least a predetermined amount of time before liftoff of the contact was detected. In some embodiments, a combination of two or more of the heuristics described above is used to determine whether an input meets the application-launching criteria. In some embodiments, when the first application is launched in response to an input at a location corresponding to the first version of the notification that meets the application-launching criteria, the application is launched to a view that shows additional information related to the notification (e.g., a view of the corresponding email, messaging, or voice message, or a view of an application that describes the purpose of the alert).
In accordance with a determination that the first portion of the first input meets notification-expansion criteria, wherein the notification-expansion criteria require that the characteristic intensity of the first contact on the touch-sensitive surface meet the preview intensity threshold in order for the notification-expansion criteria to be met (e.g., the preview intensity threshold is the deep press intensity threshold and the first portion of the first input is a deep press input), the device displays (1010) a second version of the notification (e.g., a long or expanded version of the notification) (e.g., expanded notifications 5066 in FIG. 5C5, expanded notification 5078 shown in FIG. 5F4, expanded notification 5108 shown in FIG. 5I4), wherein: the second version of the notification has a second size larger than the first size, the second version of the notification includes expanded notification content that is not displayed in the first version of the notification (e.g., the second version of the notification includes the first content and additional content, or the second version of the notification includes part of the first content and additional content, or the second version of the notification includes a more complete version of the first content), and the second version of the notification is overlaid on the background user interface (e.g., the second version of the notification replaces the first version of the notification, or the second version of the notification is an expansion of the first version of the notification). This is illustrated in FIGS. 5C1-5C6 (e.g., expanded notification 5066 is displayed in response to a press input by contact 5064), for example. This is further illustrated in FIGS. 5F1-5F4 (e.g., expanded notification 5078 is displayed in response to a press input by contact 5076), for example. This is illustrated in FIGS. 5I1-5I4 (e.g., expanded notification 5108 is displayed in response to a press input by contact 5106), for example. In some embodiments, authentication is required before the second version of the notification is displayed. For example, in some embodiments, when the background user interface is the lock screen or wake screen, an authentication interface (e.g., an alert asking for a fingerprint input, or a user interface for entering a password) is presented in accordance with a determination that the first portion of the first input meets the notification-expansion criteria. Once correct authentication information is received through the authentication interface, the second version of the notification is displayed overlaid on the background user interface. The second version of the notification is distinct from the user interface of the first application, and typically, provides access to fewer functionalities and content than the user interface of the first application).
In some embodiments, the second version of the notification includes (1012) the first content. For example, in some embodiments, the notification is for an instant message that includes both text and an image, the first version of the notification includes the text of the instant message, but not the image (e.g., the first version of the notification may optionally include only the text or include the text and a thumbnail of the image, e.g., as shown in FIG. 5B1 or FIG. 5F1), and the second version of the notification includes both the text and the image in the instant message (e.g., the second version of the notification includes the text below the image, e.g., as shown in FIG. 5F4).
In some embodiments, the expanded-notification content includes (1014) one or more of an image (e.g., image 5058 in FIG. 5F4), an audio clip, a video clip, a custom view, and interactive content (e.g., interactive map 5114 in FIG. 5I4), that are not included in the first version of the notification.
In some embodiments, while displaying the second version of the notification, the device receives (1016) an information update relevant to the notification. In response to receiving the information update relevant to the notification, the device updates the second version of the notification (e.g., expanded notification 5078 in FIGS. 5F5 and 5F7 showing new messages 5086, 5088; expanded notification 5108 in FIGS. 5I5-5I7 showing live map and “Arrival” alert) to reflect the information update relevant to the notification. For example, suppose that the first application is an instant messaging app, and the notification is for a first instant message from a social network contact of the user. The first version of the notification includes a textual excerpt from the first instant message (or a textual summary of the first instant message) and the name and avatar of the social network contact. The second version of the notification includes a conversation log or a portion thereof that includes the first instant message (e.g., including the full content (e.g., text and an image) of the first instant message) and optionally, one or more earlier messages in the conversation between the user and the social network contact. While the second version of the notification is displayed, suppose that a new instant message is received from the social network contact. In response to receiving the new instant message from the social network contact, the device updates the second version of the notification to include the new instant message as part of the conversation log that is displayed in the second version of the notification. This is illustrated in FIGS. 5F1-5F7, for example. In some embodiments, when annotation of an earlier instant message is permitted in the instant messaging app, if the social network contact starts to annotate an image included in the first instant message while the user is viewing the image displayed within the second version of the notification, the image displayed within the second version of the notification is updated in real-time to show the annotations as they are entered by the social network contact of the user. In another example, suppose that the first application is a ridesharing or taxi service app, and the notification is generated in response to a driver's acceptance of a ride pickup request made earlier by the user. The first version of the notification includes text identifying the driver and notifying the user of the driver's acceptance of the pickup request. The second version of the notification includes a live map showing the current location of the driver. The current location of the driver is updated in real-time on the map included in the second version of the notification, while the second version of the notification is displayed on the user's device. This is illustrated in FIGS. 5I1-5I7, for example.
In some embodiments, the second version of the notification includes 1018 a content region and an action region, the content region includes the expanded content (e.g., the content region includes the first content and the additional content). For example, in some embodiments, the first version of the notification includes text of an instant message, and the second version of the notification includes a content region (e.g., a conversation log) that displays the instant message and one or more earlier messages in the same conversation, e.g., as shown in expanded notification 5078 in FIG. 5F4-5F7. In another example, the first version of the notification includes an alert for a new voicemail, and the second version of the notification includes a content region that includes an audio clip for the voicemail, and a textual transcription of the voicemail, and the action region includes one or more selectable options that, when activated, are configured to perform actions with respect to the notification. For example, in some embodiments, the action region is a menu that includes menu options to dismiss the notification, reply to a communication, save the communication, etc. This is illustrated in FIG. 5F6 (e.g., Reply affordance 5082), for example. In some embodiments, the action region includes an input field (e.g., a text input field for entering a reply message), a soft keyboard, one or more affordances for entering a selection (e.g., check boxes, radio buttons, etc.), controlling various aspects of a selected action (e.g., audio or video playback controls), etc. In some embodiments, the action region is scrollable (e.g., the menu options in expanded notification 5108 in FIGS. 5I5-5I6 are scrollable). In some embodiments, the action region is only visible upon detection of a scroll input (e.g., upward movement of the first contact) on the content region (e.g., as illustrated in FIGS. 5I4-5I5, menu options 5122 and 5124 become visible in response to a scroll input by contact 5120). In some embodiments, some of the menu options are visible and some of the menu options are outside of the viewable area of the display when the second version of the notification is initially displayed. A scroll input (e.g., an upward swipe gesture) can be used to scroll the action region to reveal the menu options that are outside of the view area of the display. In some embodiments, the action region and the content region of the notification are displayed in two separate layers, and when the action region is scrolled, the content region remains unchanged (e.g., the menu options scrolls up and down in a layer underneath the content region of the notification). In some embodiments, the second version of the notification includes a header region (e.g., the header region in a notification for an instant message or email includes an icon for the application (e.g., the Messages app, or the email app) (e.g., header 5080 in FIG. 5F4) and an avatar of the sender (e.g., avatar 5084 in FIG. 5F4)). In some embodiments, the content region of the notification and the action region of the notification are scrollable on a layer underneath the header region, while the header region remains unchanged (e.g., as shown in FIGS. 5I4-5I5, content 5112 is scrollable underneath header 5110 in expanded notification 5108). In some embodiments, options for performing application-specific actions are included in the second version of the notification (e.g., options 5122, 5124, 5128, 5130 in expanded notification 5108 in FIG. 5I8). For example, for an instant messaging app, the menu options displayed in a notification for a new instant message include an option for “reply” (e.g., Reply affordance 5082 in expanded notification 5078 in FIG. 5F4); for a telephony app, the menu options displayed in a notification for a missed call include an option for “call back”; and for a voicemail app (or the voicemail function in the telephony app), the menu option displayed in a notification for a voicemail include an option for “play voicemail” and/or an option for “delete”.
In some embodiments, while displaying the second version of the notification, the device detects (1020) a second portion of the first input. In response to detecting the second portion of the first input: in accordance with a determination that the second portion of the first input meets option-activation criteria, the option-activation criteria configured to be met when the characteristic intensity of the first contact increases above the preview intensity threshold (e.g., the deep press intensity threshold) after the characteristic intensity of the first contact decreases below the preview intensity threshold (e.g., the first contact is maintained at the same location on the touch-sensitive surface after the first deep press input on the first version of the notification causes the display of the second version of the notification, and the first contact provides a second deep press on the second version of the notification), the device ceases to display the second version of the notification; and the device performs an action that corresponds to one of the one or more selectable options. This is illustrated in FIGS. 5F5-5F7 (e.g., by contact 5076 activating Reply affordance 5082). In some embodiments, the option-activation criteria are satisfied by a separate input (e.g., a second input with a second contact that is distinct from the first input with the first contact). In some embodiments, the threshold intensity used in the option-activation criteria is lower than the preview intensity threshold. In some embodiments, the option-activation criteria are met when the device detects a decrease in contact intensity followed by an increase in contact intensity above a second intensity threshold (e.g., a reduced deep press intensity threshold). It is to be noted that, in some embodiments, the option-activation criteria are met without requiring the location of the first contact to correspond to the option that is activated. In other words, the first contact may remain in the content region (e.g., in a portion of the content region that does not otherwise responds to a deep press input) when an option (e.g., a default option or the only option) in the action region is activated in response to the second deep press input provided by the first contact. In some embodiments, performing the action that corresponds to one of the one or more selectable options includes performing an action that corresponds to a default option among the one or more selectable options. If there is only one option, the action that corresponds to the option is performed. In some embodiments, the notification is for a communication, and the second version of the notification includes a “reply” option for replying to the communication. When a second press input is detected on the second version of the notification (e.g., while the first contact remains at its touch-down location on the touch-sensitive surface, and the characteristic intensity of the first contact increases above the preview intensity threshold for a second time after decreasing below the preview intensity threshold), the action for replying to the communication is activated, and a reply user interface is displayed in lieu of the second version of the notification (or the second version of the notification is further expanded to become the reply user interface including text input field and a soft keyboard). In some embodiments, a soft keyboard and a reply field (or an empty or partially prepared reply message) is automatically displayed in the reply user interface. In some embodiments, the notification is for a ride sharing request, and a first press input causes the notification to expand to display a live map and an “accept” button. A second press input accepts the ride sharing request and send the acceptance to the user that is offering the ride share.
In some embodiments, while displaying the second version of the notification, the device detects (1022) termination of the first input (e.g., detecting lift-off of the first contact). In response to detecting the termination of the first input, the device maintains display of the second version of the notification overlaid on the background user interface (e.g., expanded notification 5078 remains displayed after lift-off of contact 5076 in FIG. 5G1 following FIG. 5F4; expanded notification 5108 remains displayed after lift-off of contact 5106 in FIG. 5I5 following 514).
In some embodiments, while displaying the second version of the notification overlaid on the background user interface (e.g., the second version of the notification remains overlaid on the background user interface after liftoff of the first contact is detected), the device detects (1024) a second input that includes detecting a second contact on the touch-sensitive surface. In response to detecting the second input (e.g., the second input is a tap input): in accordance with a determination that the second contact is detected at a location on the touch-sensitive surface that corresponds to a portion of the background user interface surrounding the second version of the notification: the device ceases to display the second version of the notification; and the device maintains display of the background user interface (e.g., the background user interface includes the first version of the notification and respective first versions of one or more other notifications that have not been dismissed from the background user interface). In some embodiments, if the background user interface has been deemphasized (e.g., blurred or darkened) in response to the first input, the background user interface is restored to its original clarity and brightness when the second version of the notification ceases to be displayed. In some embodiments, after displaying the second version of the notification, the notification is considered read, and is removed from the background user interface when the background user interface is restored (e.g., only displaying the short versions of notifications that have not yet been viewed, if there is any). This is illustrated in FIGS. 5G1-5G3 (a tap input by contact 5096 dismisses notification 5078), for example. In some embodiments, the second version of the notification can also be dismissed by a tap input detected on a “dismiss” button or affordance (e.g., a button with a cross “x” on it) included in the second version of the notification.
In some embodiments, in response to detecting the second input (e.g., the second input is a tap input): in accordance with a determination that the second contact is detected at a location on the touch-sensitive surface that corresponds to a content region in the second version of the notification (e.g., the content region is distinct from the action region and the header region of the second version of the notification): the device ceases (1026) to display the second version of the notification; the device ceases to display the background user interface; and the device initiates a process to launch the first application (e.g., displaying a user interface of the first application, or displaying an authentication interface is authentication is required before the first application can be launched). This is illustrated in FIGS. 5H1-5H2, for example. In some embodiments, a tap input detected at a location on the touch-sensitive surface that corresponds to the first version of the notification also initiates the process to launch the first application, and replacement of the first version of the notification and the background user interface by the authentication interface or the user interface of the first application.
In some embodiments, in response to detecting the first portion of the first input: in accordance with a determination that the first input meets background-deemphasizing criteria, wherein the background-deemphasizing criteria require that the characteristic intensity of the first contact on the touch-sensitive surface meet a hint intensity threshold (e.g., a light press intensity threshold, or an intensity threshold that is lower than the preview intensity threshold) that is lower than the preview intensity threshold in order for the background-deemphasizing criteria to be met, the device applies (1028) a visual effect to deemphasize the background user interface (e.g., blur or darken the background user interface) before displaying the second version of the notification (e.g., as shown in FIGS. 5C3-5C4, background user interface 5026 is deemphasized before expanded notification 5066 is displayed in FIG. 5C5; as shown in FIGS. 5F2-5F3, background user interface 5036 is deemphasized before expanded notification 5078 is displayed in FIG. 5F4; and as shown in FIGS. 5I2-5I3, background user interface 5102 is deemphasized before expanded notification 5108 is displayed in FIG. 5I4;). In some embodiments, the second version of the notification is overlaid on a blurred version of the background user interface (e.g., as shown in FIGS. 5C5, 5F4, and 5I4). In some embodiments, the amount of blurring is dynamically varied in accordance with a current value of the characteristic intensity of the first contact in the first input (e.g., as shown in FIGS. 5C3-5C5, 5F2-5F3, and 512-514).
In some embodiments, in response to detecting the first portion of the first input: in accordance with a determination that the first portion of the first input includes a movement of the first contact that exceeds a movement threshold (e.g., the first contact moves away from its touchdown location by more than a threshold number of pixels (e.g., ten pixels))(e.g., the movement is in any direction): the device restores (1030) the background user interface (e.g., restoring the clarity and brightness of the background user interface after the background user interface has been blurred and darkened in response to the characteristic intensity of the first contact increases above the hint intensity threshold) (e.g., in FIG. 5D6, user interface 5026 is restored when contact 5072 moves for more than a threshold amount); and the device forgoes displaying the second version of the notification when the first portion of the first input meets the notification-expansion criteria (e.g., the display of the second version of the notification is canceled when sufficient amount of movement had been detected when the characteristic intensity of the first contact exceeded the deep press intensity threshold, e.g., as shown in FIG. 5D6). The notification-expansion criteria are not met if the movement of the first contact exceeds the movement threshold, even though the criterion associated with the preview intensity threshold has been met. This is illustrated in FIGS. 5D4-5E4, for example.
In some embodiments, in response to detecting the first portion of the first input: in accordance with a determination that the first portion of the first input includes a movement of the first contact that exceeds a movement threshold (e.g., the first contact moves away from its touchdown location by more than a threshold number of pixels (e.g., ten pixels)) (e.g., the movement is in the vertical direction), the device scrolls (1032) the background user interface (and any notifications overlaid on the background user interface) in accordance with the movement of the first contact (e.g., if multiple notifications are displayed on the background user interface in a list, and the movement is in a vertical direction, the first input scrolls the list of notifications on the background user interface). The notification-expansion criteria are not met if the movement of the first contact exceeds the movement threshold, even though the criterion associated with the preview intensity threshold has been met. In some embodiments, the notification-scrolling criteria are met when the movement is in the vertical direction and exceeds the movement threshold. This is illustrated in FIGS. 5E1-5E4, for example.
In some embodiments, in response to detecting the first portion of the first input: in accordance with a determination that the first portion of the first input includes a movement of the first contact that exceeds a movement threshold (e.g., the first contact moves away from its touchdown location by more than a threshold number of pixels) (e.g., the movement is in the horizontal direction): the device slides (1034) the first version of the notification in accordance with the movement of the first contact; and (e.g., without sliding other notifications) the device displays one or more selectable actions adjacent to the first version of the notification (e.g., respective affordances for one or more quick response actions are displayed in the space that is vacated by the first version of the notification when the first version of the notification is moved horizontally in accordance with the movement of the first contact). In some embodiments, as the first version of the notification is moved horizontally, the respective affordances for the one or more quick response actions are revealed from behind the first version of the notification. The notification-expansion criteria are not met if the movement of the first contact exceeds the movement threshold, even though the criterion associated with the preview intensity threshold has been met. In some embodiments, option-revealing criteria are met when the movement is in the horizontal direction and exceeds the movement threshold. This is illustrated in FIGS. 5D4-5D8 (e.g., sliding notification 5028 to reveal option 5074 in accordance with movement of contact 5072), for example.
In some embodiments, prior to displaying the second version of the notification, in response to detecting an increase in the characteristic intensity of the first contact on the touch-sensitive surface, the device starts (1036) to adjust an appearance of the user interface dynamically based on the characteristic intensity of the first contact (e.g., to indicate that a preview operation will be performed if the intensity of the contact continues to increase), as shown by the blurring of the user interfaces in FIGS. 5C2-5C4, 5F2-5F4, and 512-514. In some embodiments, the content on the display other than the representation of the first version of the notification is obscured dynamically so that the magnitude of the obscuring changes based on the changes in the characteristic intensity of the contact. Examples of how the appearance of the user interface may be dynamically adjusted are described in U.S. patent application Ser. No. 14/869,899, filed on Sep. 29, 2015, titled “Devices, Methods, and Graphical User Interfaces for Manipulating User Interface Objects with Visual and/or Haptic Feedback”, which is incorporated by reference herein in its entirety. After starting to dynamically adjust the appearance of the user interface based on the characteristic intensity of the first contact (and before displaying the second version of the notification), the device detects movement of the first contact on the touch-sensitive surface; and in some embodiments, the appearance of the user interface is dynamically adjusted based on the intensity of the contact to indicate that a preview operation will be performed if the characteristic intensity of the contact continues to increase. In response to detecting the movement of the first contact on the touch-sensitive surface: in accordance with a determination that the movement of the first contact meets preview-cancellation criteria (e.g., the movement exceeds a movement threshold (e.g., more than ten pixels)), the device moves the first version of the notification based on the movement of the first contact and the device ceases to dynamically adjust the appearance of the user interface based on the characteristic intensity of the first contact (e.g., moving the first version of the notification to the side and showing options for interacting with the first notification for a leftward swipe input, or scrolling a plurality of notifications including the first version of the notification for an upward or downward swipe input). In some embodiments, if the movement meets preview-cancellation criteria, the device ignores further changes in the characteristic intensity of the contact until the contact ceases to be detected on the display and forgoes displaying the second version of the notification (e.g., even if the contact would otherwise meet the notification-expansion criteria). In some embodiments, the preview cancellation criteria are based on one or more of a total distance moved by the contact, movement of the contact away from a point of at which the contact exceeded a hint intensity threshold that is lower than the preview intensity threshold, movement of the contact in an x direction (e.g., from a point of at which the contact exceeded the hint intensity threshold), movement of the contact in a y direction (e.g., from a point of at which the contact exceeded the hint intensity threshold). In accordance with a determination that the movement does not meet the preview-cancellation criteria, the device continues to dynamically adjust the appearance of the user interface based on the characteristic intensity of the first contact (e.g., without moving the first version of the notification based on the movement of the contact). In some embodiments, if the movement does not meet the preview-cancellation criteria, the device continues to respond to changes in the characteristic intensity of the contact (e.g., displaying the second version of the notification if the contact meets the notification-expansion criteria).
In some embodiments, prior to displaying the second version of the notification, in response to detecting an increase in the characteristic intensity of the first contact on the touch-sensitive surface, the device obscures (1038) (e.g., blurs and/or darkens) content on the display other than a representation of the first version of the notification (e.g., as shown by the blurring of the user interfaces in FIGS. 5C2-5C4, 5F2-5F4, and 512-514)). In some embodiments, the content on the display other than the representation of the first version of the notification is obscured dynamically so that the magnitude of the obscuring changes based on the changes in the characteristic intensity of the first contact. In some embodiments, the content on the display dynamic changes to the appearance of the first version of the notification is also applied. After obscuring the content on the display other than a representation of the first version of the notification in response to the increase in the characteristic intensity of the first contact (and before displaying the second version of the notification), the device detects movement of the first contact on the touch-sensitive surface. In response to detecting movement of the first contact on the touch-sensitive surface: in accordance with a determination that the movement of the first contact meets preview-cancellation criteria, the device ceases to obscure the content on the display other than a representation of the first version of the notification and moving the first version of the notification based on the movement of the first contact (e.g., moving the first version of the notification to the side and showing options for interacting with the first notification for a leftward swipe input, or scrolling a plurality of notifications including the first version of the notification for an upward or downward swipe input). In some embodiments, if the movement meets preview-cancellation criteria, the device ignores further changes in the characteristic intensity of the contact until the contact ceases to be detected on the display and forgoes displaying the second version of the notification (e.g., even if the contact would otherwise meet the notification-expansion criteria). In some embodiments, the preview cancellation criteria are based on one or more of a total distance moved by the contact, movement of the contact away from a point of at which the contact exceeded a hint intensity threshold that is lower than the preview intensity threshold, movement of the contact in an x direction (e.g., from a point of at which the contact exceeded the hint intensity threshold), movement of the contact in a y direction (e.g., from a point of at which the contact exceeded the hint intensity threshold). In accordance with a determination that the movement of the first contact does not meet the preview-cancellation criteria, the device continues to obscure content on the display other than a representation of the first version of the notification (e.g., dynamically obscuring the content in accordance with the characteristic intensity of the first contact) (e.g., without moving the first version of the notification based on the movement of the contact). In some embodiments, if the movement does not meet the preview-cancellation criteria, the device continues to respond to changes in the characteristic intensity of the contact (e.g., displaying the second version of the notification if the contact meets the notification-expansion criteria).
In accordance with some embodiments,
As shown in
As described below, the method 1200 provides an intuitive way to access contextual content associated with an application without first launching the application. The method reduces the number, extent, and/or nature of the inputs from a user when accessing a subset of content and/or functions of the application, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to access desired content and function faster and more efficiently conserves power and increases the time between battery charges. Furthermore, in some embodiments, the contextual content object is presented with menu of options that, when activated, trigger different sub-functions of the application. Thus, a single input with a single contact on the same application icon can be used to arrive at different levels of functionality and content of the corresponding application, further improving the efficiency of the user interface.
The device displays (1202), on the display, a user interface that includes a plurality of application icons that correspond to different applications in a plurality of applications (e.g., a desktop or home screen user interface generated by an operating system of the device that includes an array of application launch icons). In some embodiments, the application icons are displayed in an arrangement on the user interface (e.g., in a grid pattern, or in a row or column) (e.g., home screen 5202 in FIG. 5K1, home screen 5288 in 5N1).
The device, while displaying the user interface that includes the plurality of application icons, detects (1204) a first input that includes detecting a first contact on the touch-sensitive surface at a location on the touch-sensitive surface that corresponds to a first application icon of the plurality of application icons, the first application icon being associated with a first application of the plurality of applications (e.g., contact 5206 on icon 524 in FIG. 5K1, contact 5290 on icon 445 in FIG. 5N1).
The device, in response to detecting the first input (1206), performs a number of operations. In response to detecting the first input, in accordance with a determination that the first input meets application-launching criteria, wherein the application-launching criteria do not require that a characteristic intensity of the first contact on the touch-sensitive surface meet a first intensity threshold in order for the application-launching criteria to be met (e.g., a deep press intensity threshold) (e.g., in some embodiments, the application-launching criteria are met when the first input is a tap input): the device launches the first application, and the device replaces display of the user interface that includes the plurality of application icons with a user interface of the first application. This is illustrated in FIGS. 5J1-5J2 (e.g., a tap input by contact 5204 on icon 424 launches the Messages application), for example. In some embodiments, the application-launching criteria are met when the device detects a tap input with a duration that is below a threshold duration without regard to whether or not the characteristic intensity of the contact exceeded the first intensity threshold. In some embodiments, the application-launching criteria are met when the device detects liftoff of the contact without the characteristic intensity of the contact having reached the first intensity threshold since touchdown of the contact. In some embodiments, the application-launching criteria are met when the device detects liftoff of the contact without the characteristic intensity of the contact having exceeded the first intensity for at least a predetermined amount of time before liftoff of the contact was detected. In some embodiments, a combination of two or more of the heuristics described above is used to determine whether an input meets the application launching criteria.
In response to detecting the first input, in accordance with a determination that the first input meets menu-presentation criteria, wherein the menu-presentation criteria require that the characteristic intensity of the first contact on the touch-sensitive surface meet the first intensity threshold in order for the menu-presentation criteria to be met (e.g., in some embodiments, the menu-presentation criteria are met when the first input is a deep press), the device concurrently displays a contextual content object (e.g., a widget or interactive mini-application object that is associated with the first application, or a preview of the widget or mini-application object, or interactive and/or graphical representation of the widget or mini-application object) and a respective affordance that is associated with the contextual content object (e.g., an “add to widget view” button or link overlaid on the widget, mini-application object, or preview of the widget or mini-application object). This is illustrated in FIGS. 5K1-5K6 (e.g., contextual content object 5210 is displayed in response to a press input by contact 5206 on application icon 424 for the Messages application, and the contextual content object 5210 includes an “add widget” affordance 5222), for example. In some embodiments, the contextual content object (e.g., a widget or mini-application object) is displayed while maintaining display of a representation of at least a portion of the user interface that includes the plurality of application icons (e.g., the widget or mini-application object is overlaid on at least a portion of the user interface that includes the plurality of application icons (e.g., a blurred or darkened version of a home screen or desktop user interface)). In some embodiments, the contextual content object is displayed on top of and obscuring the application icon of the first application to which the contextual content object corresponds. In some embodiments, the display location of the contextual content object is adjusted so as to avoid obscuring the application icon of the first application. In some embodiments, the contextual content object includes contextually selected content that has been automatically selected from the first application (e.g., by the first application or by the electronic device) based on a current context of the electronic device (e.g., the contextual content object is a widget or mini-application object, or a preview of the widget or mini-application object with information and/or action affordances that are selected based on the current context (e.g., time, location, recently contacted users, recent activities within the app, etc.)). In some embodiments, the respective affordance, when activated, is configured to add the contextual content object (or a widget or mini-application object represented by the contextual content object) to a user interface that includes information for multiple applications (e.g., a contextual content object view that includes an array of contextual content objects associated with different applications of two or more of the plurality of applications).
In some embodiments, the user interface that includes information for multiple applications includes (1208) a contextual content object view (e.g., in the widget screen, a widget portion of a home screen or another screen, etc.) that is configured to concurrently display respective contextual content objects (e.g., widgets or mini-application objects) associated with different applications selected from the plurality of applications (e.g., the widget view hosts respective widgets with contextually selected content from any number of different applications, e.g., as shown in user interface 5238 in FIGS. 5L8, 501, 5P1).
In some embodiments, while displaying the contextual content object (e.g., overlaid on at least a portion of the user interface that includes the plurality of application icons (e.g., a blurred or darkened version of a home screen or desktop user interface)), the device detects (1210) a second input that includes detecting a second contact on the touch-sensitive surface at a location on the touch-sensitive surface that corresponds to the contextual content object (e.g., the second input can be detected after termination of the first input, and while the display of the contextual content object is maintained). In response to detecting the second input: in accordance with a determination that the second input meets the application-launching criteria, wherein the application-launching criteria do not require the characteristic intensity of the second contact to meet the first intensity threshold (e.g., before detecting lift-off of the second contact) in order for the application-launching criteria to be met (e.g., the application-launching criteria are satisfied when the second input is a tap input): the device launches the first application, and the device replaces display of the contextual content object (and the blurred user interface that includes the plurality of application icons) with a user interface of the first application. This is illustrated in FIGS. 5L9-5L10 (e.g., a tap input by contact 5272 on contextual content object 5268 launches the Messages application) and FIGS. 5M1-5M2 (e.g., a tap input by contact 5284 on contextual content object 5268 launches the Messages application), for example.
In some embodiments, replacing display of the contextual content object with a user interface of the first application includes (1212): in accordance with a determination that the second contact is detected at a first location on the touch-sensitive surface that corresponds to a first portion of the contextual content object, displaying a first user interface from the first application; and in accordance with a determination that the second contact is detected at a second location on the touch-sensitive surface that corresponds to a second portion of the contextual content object, displaying a second user interface from the first application that is distinct from the first user interface from the first application. This is illustrated in FIGS. 5L9-5M2, for example. For example, the people widget (e.g., a mini-application object associated with the Contacts application) includes a grid of frequently contacted people (e.g., a list of favorite social contacts of the user) that are represented by respective avatars/photos/monograms and respective names of those people. A tap input detected on one portion of the people widget (e.g., a tap input on an avatar/photo/monogram of a person in the grid) initiates a communication with a user (e.g., launching a messages user interface for composing a message to the selected user, e.g., as shown in FIGS. 5L9-5L10) and a tap input detected on another portion of the people widget (e.g., a tap input detected on a person's name) causes display of the contact card for the selected user, and a tap input detected on yet another portion of the people widget (e.g., a tap input detected on the header portion of the people widget) launches a user interface that lists the conversations in the Messages application (e.g., as shown in FIGS. 5M1-5M2).
In some embodiments, while displaying the contextual content object, the device displays (1214) representation (e.g., a blurred or darkened representation) of at least a portion of the user interface that includes the plurality of application icons (e.g., the contextual content object is overlaid on at least a portion of the user interface that includes the plurality of application icons (e.g., a blurred or darkened version of a home screen or desktop user interface, as shown in FIGS. 5K1 and 5N4).
In some embodiments, in response to detecting the first input: in accordance with the determination that the first input meets the menu-presentation criteria, the device displays (1216) one or more selectable options concurrently with the contextual content object, wherein the one or more selectable options, when activated, are configured to perform respective functions associated with the first application (e.g., the contextual content object is presented with a quick action menu associated with the first application). This is illustrated in FIGS. 5K4 (e.g., menu 5212 is presented with mini application object 5210), and FIGS. 5N4 (e.g., menu 5309 is presented with mini application object 5294) for example. In some embodiments, the quick action menu includes one or more menu options that, when activated, are configured to perform respective functions provided by the first application. In some embodiments, the contextual content object is presented in the same background container (e.g., a menu platter) as the menu options. In some embodiments, the contextual content object is presented in a separate display region from the quick action menu (e.g., the widget is presented above the quick action menu, and both are presented next to the first application icon and over the blurred home screen). In some embodiments, a haptic signal is provided when the menu-presentation criteria are met, and the menu of options are presented. In some embodiments, if an application does not have a corresponding contextual content object and selectable options, nothing is displayed when the menu-presentation criteria are met by a press input on an application icon corresponding to the application. In such a situation, the device provides a haptic signal to indicate the failure to present a contextual content object and menu options for the application.
In some embodiments, the device detects (1218) termination of the first input that includes detecting liftoff of the first contact. In response to detecting the termination of the first input, the device maintains concurrent display of the contextual content object and the one or more selectable options (e.g., overlaid on a blurred or darkened version of the home screen). While the concurrent display of the contextual content object and the one or more selectable options is maintained, the device detects a selection input that selects a first option of the one or more selectable options (e.g., a tap input on a first option of the selectable options in the quick action menu, or a press input by the same continuous contact on a first option of the selectable options in the quick action menu). In response to detecting the selection input, the device starts to perform a first function of the first application that corresponds to the selected first option (e.g., the first option is for sending a message to a first social contact of the user, and a tap input on the first option causes the first application to launch and the first application displays an initial user interface for composing a message to the first social contact of the user; or the first option is for showing a contact card of the user, a press input by the same continuous contact (e.g., contact 5209 in FIG. 5N5) displays the contact card of the user). In some embodiments, a selection input on the contextual content object launches the app to a first location (e.g., a selection input on the favorite people widget leads to the user interface that lists the users' favorite contacts), while a selection input on one of the menu items launches the app to a different location (e.g., a selection input on the “show my info” option leads to the user interface that displays the user's contact card).
In some embodiments, while concurrently displaying the contextual content object and the one or more selectable options, the device detects (1220) movement of the first contact to a location on the touch-sensitive surface that corresponds to a second option of the one or more selectable options. In response to detecting the movement of the first contact to the location on the touch-sensitive surface that corresponds to the second option of the one or more selectable options, in accordance with a determination that the first input meets selection criteria (e.g., the selection criteria requires that the first contact remains at the location that corresponds to the second option for more than a threshold amount of time, and/or requires that the characteristic intensity of the first contact meet a respective threshold intensity (e.g., a light press intensity threshold or a deep press intensity threshold) while the first contact remains at the location that corresponds to the second option, in order for the selection criteria to be met), the device starts to perform a second function of the first application that corresponds to the selected second option (e.g., suppose that the second option is for composing a new message to an unspecified recipient; and by sliding the first contact to the second option and maintaining the first contact on the second option until selection criteria are met by the first input, the user causes the first application to launch and the first application displays an initial user interface for composing a new message to a recipient that is yet to be specified by the user).
In some embodiments, the device provides (1222) a first haptic signal when the first contact moves past each selectable option of the one or more selectable options.
In some embodiments, the contextual content object is (1224) a first mini-application object that corresponds to the first application (e.g., a mini-application object is an interactive object that is associated with an application, and provides a subset of the content and/or functions of the application. In some embodiments, the mini-application object is referred to as a widget. In some embodiments, the mini-application object exists and functions without requiring the corresponding application to be running or active. In some embodiments, the mini-application object is operated by the operating system and is configured to retrieve content of the corresponding application without requiring the corresponding application to be running or active. In some embodiments, the contextual content object is a representation of a first mini-application object associated with the first application (e.g., the contextual information is a preview of a widget or mini-application object that is associated with the first application). For example, the preview includes substantially the same information and/or functions as the widget or mini-application itself, but not all the information and/or functions. In some embodiments, the preview also visually looks similar to the widget or mini-application object to which it corresponds, but is simplified to conform to the size and unified look and feel requirements of all contextual content objects on the home screen.
In some embodiments, while concurrently displaying the contextual content object and the respective affordance, the device detects (1226) an input activating the respective affordance (e.g., a tap input on the add-widget affordance). In response to detecting the input activating the respective affordance, the device adds the contextual content object (or a widget or mini-application object represented by the contextual content object, if the contextual content object is a preview or representation of the actual widget or mini-application object) to the user interface that includes information for multiple applications (e.g., the contextual content object view or widget view). This is illustrated in 5K5-5K6, for example. In some embodiments, the contextual content object view or widget view is a user interface that is configured to concurrently display respective contextual content objects (e.g., widgets or mini-application objects) associated with different applications selected from the plurality of applications. In some embodiments, the device displays an animation showing the contextual content object jumping from its original location to the widget screen (e.g., the screen showing a list of existing widgets that have already been added to the widget view previously by the user, and optionally, in addition to one or more default widgets already included in the widget view by the operating system). In some embodiments, the widget screen is presented briefly on the display (e.g., sliding in from the left to cover part of the home screen) to show that the widget has been added to the widget view in response to the user's input activating the add-widget affordance, and then the display is restored (e.g., the widget screen slides back to the left) to display the home screen again. In some embodiments, once the widget has been added to the widget view, the add-widget affordance is no longer displayed with the widget.
In some embodiments, in response to adding the contextual content object to the user interface that includes information for a plurality of applications (e.g., the contextual content object view or widget view), the device ceases (1228) to concurrently display the respective affordance with the contextual content object, e.g., as shown in FIG. 5K7 (“add widget” affordance is no longer displayed after it has been invoked). In some embodiments, once the contextual content object is added to the widget view, the add-widget affordance is replaced by an indicator that indicates the current inclusion of the contextual content object in the widget view (e.g., the “added” indicator 5244 in FIG. 5K7). In some embodiments, the indicator is displayed with the widget each time the widget is shown in response to subsequent inputs that meet the menu-presentation criteria. In some embodiments, the indicator is only displayed briefly immediately after the activation of the add-widget affordance and the addition of the contextual content object into the widget view. After the brief display of the indicator, the indicator is no longer displayed during subsequent times when the contextual content object is called up again in response to inputs that meet the menu-presentation criteria.
In some embodiments, after adding the contextual content object to the user interface that includes information for a plurality of applications (e.g., the contextual content object view or widget view), while displaying the user interface that includes the plurality of application icons, the device detects (1230) a navigation input (e.g., a swipe gesture in the horizontal direction (e.g., from left to right)) for navigating to the user interface that includes information for a plurality of applications (e.g., the contextual content object view or widget view). In response to detecting the navigation input, the device replaces display of the user interface that includes the plurality of application icons with the user interface that includes information for a plurality of applications (e.g., the contextual content object view or widget view), wherein the user interface that includes information for a plurality of applications (e.g., the contextual content object view or widget view) includes the contextual content object associated with the first application (and one or more additional contextual content objects that are associated with one or more other applications in the plurality of applications). This is illustrated in FIGS. 5L5-5L8, for example.
While displaying the user interface that includes information for a plurality of applications (e.g., the contextual content object view or widget view) including the contextual content object associated with the first application, the device detects a third input that includes detecting a third contact on the touch-sensitive surface at a location that corresponds to the contextual content object in the user interface that includes information for a plurality of applications (e.g., the contextual content object view or widget view). In response to detecting the third input: in accordance with a determination that the third input meets content expansion criteria, wherein the content expansion criteria require that a characteristic intensity of the third contact on the touch-sensitive surface meet the first intensity threshold (e.g., in some embodiments, the content expansion criteria are met when the third input is a deep press input), the device expands the contextual content object to display the contextually selected content (e.g., the stock widget includes stocks that the user has previously viewed, the weather widget includes the weather forecast for the city that the user is currently in, etc.) and additional content (e.g., additional rows of stocks in the stock widget, or additional weather forecasts in the weather widget, etc.). This is illustrated in
In some embodiments, expanding the contextual content object to display the contextually selected content and the additional content includes (1232): in accordance with a determination that the third contact is detected at a third location on the touch-sensitive surface that corresponds to a third portion of the contextual content object (e.g., the third portion of the contextual content object includes areas outside of a content item (e.g., a stock, an avatar, etc., a weather forecast)), displaying first additional content with the contextually selected content; and in accordance with a determination that the third contact is detected at a fourth location on the touch-sensitive surface that corresponds to a fourth portion of the contextual content object (e.g., the fourth portion of the contextual content object includes areas of a specific content item (e.g., a stock, an avatar, etc., a weather forecast)), displaying second additional content that is distinct from the first additional content. This is illustrated in
In some embodiments, the contextual content object includes (1234) a first content item of a first content item type, and wherein the first additional content includes additional content items of the first content item type. This is illustrated in FIGS. 5K8-5K9 (e.g., more favorite people's avatars are displayed in response to press input by contact 5248), and FIGS. 5P1-5P2 (e.g., more events are displayed in response to press input by contact 5214), for example. For example, the stock widget includes two default stock items, and the expanded stock widget includes one or more additional stock items. In another example, the weather widget includes the current weather forecast for a first city, and the expanded weather widget includes the current weather forecasts for one or more additional cities (e.g., cities near the first city).
In some embodiments, the contextual content object includes (1236) a first content item, and wherein the second additional content includes additional information associated with the first content item. This is illustrated, for example, in FIGS. 5L1-5L2 (e.g., last message 5262 from Genevive is displayed in response to a press input by contact 5260 on Genevive's avatar), and
In some embodiments, the device detects (1238) termination of the third input that includes detecting liftoff of the third contact. In response to detecting the termination of the third input, the device maintains display of the contextually selected content and the additional content (e.g., as shown in FIGS. 5K8-5K10).
In some embodiments, the device detects (1240) termination of the third input that includes detecting liftoff of the third contact. In response to detecting the termination of the third input: the device maintains display of the contextually selected content, and the device ceases to display the additional content (e.g., as shown in FIG. 5L1-5L3, additional content 5262 is no longer displayed after termination of the press input by contact 5260).
In some embodiments, the contextual content object includes (1242) a first interactive object (e.g., an interactive control for a light bulb or a thermostat) from the first application (e.g., a home control application). In some embodiments, activating the first interactive object causes a change in functionality controlled by the application (e.g., turning on/off an appliance). In some embodiments, the contextual content object includes a plurality of interactive objects.
In some embodiments, the contextual content object includes (1244) representations of one or more social contacts associated with a user of the device (e.g., avatars/photos/monograms and names/aliases of the users' favorite contacts arranged in a grid (e.g., a two by four grid)), e.g., avatars 5224, 5226, 5228, 5230, 5252, 5254, 5256, 5258 in FIG. 5K9. In some embodiments, the representations of users include graphical indications of recent communications received from the users (e.g., a badge associated with a contact that represents the number of new/unread/unviewed communications received from the contact, e.g., badges 5232, 5234, 5246 in FIG. 5K8).
In some embodiments, in response to detecting the first input, in accordance with the determination that the first input meets the menu-presentation criteria, the device provides (1246) a second haptic signal when displaying the contextual content object.
In some embodiments, displaying the contextual content object includes (1248) displaying the contextual content object at a location on the display that corresponds to the location of the first contact on the touch-sensitive surface (e.g., the contextual content object is overlaid on a portion of the user interface that previously displayed the first application icon). In some embodiments, the first application icon is not obscured by the contextual content object. In such embodiments, the contextual content object and the quick action menu are positioned on the display to keep the first application icon unobscured (while other portions of the user interface are blurred or darkened).
In some embodiments, displaying the contextual content object includes (1250) maintaining display of the first application icon at its original location and displaying the contextual content object in proximity to the first application icon (e.g., the contextual content object is displayed between the first application icon and the quick action menu (e.g., the one or more selectable options)). In such embodiments, the contextual content object and the quick action menu are positioned on the display to keep the first application icon unobscured (while other portions of the user interface are blurred or darkened), e.g., as shown in FIGS. 5K4 and 5N4.
In some embodiments, displaying the contextual content object includes (1252) maintaining display of the first application icon at a location offset from its original location and displaying the contextual content object in proximity to the first application icon (e.g., the contextual content object is displayed between the first application icon and the quick action menu (e.g., the one or more selectable options)). In such embodiments, the contextual content object and the quick action menu are positioned on the display to keep the first application icon unobscured (while other portions of the user interface are blurred or darkened). The first application icon is slightly offset from its original location (e.g., moved up or down) by a small amount to accommodate the contextual content object and the one or more selectable options on the display, e.g., as shown in FIG. 5N4.
In accordance with some embodiments,
As shown in
The processing unit 1308 is configured to enable display of (e.g., with enabling unit 1310), on the display unit, a user interface that includes a plurality of application icons that correspond to different applications in a plurality of applications. While displaying the user interface that includes the plurality of application icons, the processing unit 1308 is configured to detect (e.g., with detecting unit 1312) a first input that includes detecting a first contact on the touch-sensitive surface unit at a location on the touch-sensitive surface unit that corresponds to a first application icon of the plurality of application icons, the first application icon being associated with a first application of the plurality of applications. In response to detecting the first input: in accordance with a determination that the first input meets application-launching criteria, wherein the application-launching criteria do not require that a characteristic intensity of the first contact on the touch-sensitive surface meet a first intensity threshold in order for the application-launching criteria to be met: the processing unit 1308 is configured to launch (e.g., with launching unit 1314) the first application; and replace (e.g., with replacing unit 1316) display of the user interface that includes the plurality of application icons with a user interface of the first application.
In accordance with a determination that the first input meets menu-presentation criteria, wherein the menu-presentation criteria require that the characteristic intensity of the first contact on the touch-sensitive surface meet the first intensity threshold in order for the menu-presentation criteria to be met, the processing unit 1308 is configured to concurrently enable display of (e.g., with enabling unit 1310) a contextual content object and a respective affordance that is associated with the contextual content object, wherein: the contextual content object includes contextually selected content that has been automatically selected from the first application based on a current context of the electronic device; and the respective affordance, when activated, is configured to add the contextual content object to a user interface that includes information for multiple applications.
As described below, in some embodiments, an input by a single contact can be used to toggle between pausing download and resume download, or to present a menu with multiple download related options and select one of the multiple options, depending on the intensity, duration, and/or movement of the contact. This allows the user to activate the desired function related to downloading applications with fewer steps, and thus improving the efficiency of the user interface while avoiding over-cluttering the user interface.
At an electronic device with a display, a touch-sensitive surface, and one or more sensors for detecting intensities of contacts on the touch-sensitive surface, the device displays (1402), on the display, a user interface that includes a plurality of user interface objects (e.g., application icons and, optionally, placeholder icons that represent downloading apps) that correspond to different applications in a plurality of applications (e.g., the user interface is a home screen or an application springboard that includes application icons and optionally placeholder icons that represent applications that have not been completely downloaded), wherein the plurality of user interface objects include a first user interface object (e.g., a first application icon, or a first placeholder icon that temporarily represent an application while it is being downloaded) that corresponds a first application that is in a process of being downloaded (e.g., downloading icons 5408, 5410 in user interface 5402, FIG. 5S1). In some embodiments, the first application is in the process of being downloaded when the first application is waiting in a queue to start download. In some embodiments, the first application is in the process of being downloaded when the first application has already started to download, but the downloading has been paused before completion. In some embodiments, the first application is in the process of being downloaded when the first application is currently being downloaded (e.g., data transfer is in progress). In some embodiments, the first application is in the process of being downloaded when the first application is in any of the above mentioned states. In some embodiments, when the first application is in the process of being downloaded, the first application icon or first placeholder icon takes on an appearance that indicates the current state of the first application. For example, when the first application is waiting in a queue to start download, the caption text in the application name portion of the first application icon or the first placeholder icon is changed to “waiting . . . ”, and the first application icon or placeholder icon is darkened or grayed out. In some embodiments, when the downloading of the first application is in progress, an overlay (e.g., a circular progress indicator) on the first application icon or placeholder icon is continuously updated to show the current progress of the download. When the downloading of the first application is paused, an overlay (e.g., a circular progress indicator) on the first application icon or placeholder icon displays the amount of download that has been completed, and the caption text of the first application icon or placeholder indicates that the downloading of the first application has been paused. In some embodiments, if a placeholder icon is used to represent an application that is in the process of being downloaded, when downloading of the application is completed, the placeholder icon is replaced by the application icon that corresponds to the application.
While displaying the user interface that includes the plurality of user interface objects, the device detects (1404) a first input that includes detecting a first contact at a location on the touch-sensitive surface that corresponds to the first user interface object (e.g., the first application icon or the first placeholder icon) (e.g., contact 5412 on downloading icon 5408, contact 5432 on downloading icon 5410, contact 5478 on downloading icon 5408, contact 5480 on downloading icon 5410).
In response to detecting the first input: in accordance with a determination that the first user interface object corresponds to an application that has not been fully downloaded and that the first input meets menu-presentation criteria, wherein the menu-presentation criteria require that a characteristic intensity of a contact in a detected input meet a first intensity threshold in order for the menu-presentation criteria to be met, the device displays (1406) one or more (in some embodiments, a plurality of) first selectable options that, when activated, are configured to perform actions with respect to downloading of the first application. For clarity, the menu-presentation criteria include a criterion that is met when a characteristic intensity of a respective contact in a respective input exceeds a first intensity threshold. For clarity, the menu-presentation criteria require that a characteristic intensity of a respective contact in a respective input meet a first intensity threshold in order for the menu-presentation criteria to be met. For example, the one or more menu-presentation criteria require that a characteristic intensity of a first contact in a first input meet the first intensity threshold in order for the menu-presentation criteria to be met; the menu-presentation criteria require that a characteristic intensity of a second contact in a second input, distinct from the first input, meet the first intensity threshold in order for the menu-presentation criteria to be met; and so on. In some embodiments, the selectable options for a downloading application are the same for different applications while they are being downloaded, even if those applications have different selectable options once they have completed downloading. This is illustrated in FIGS. 5Q1-5Q5, and 5Q9-5Q13, for example.
In some embodiments, in response to detecting the first input: in accordance with a determination that the first user interface object corresponds to an application that has been installed on the device and that the first input meets the menu-presentation criteria, the device displays (1408) one or more (in some embodiments, a plurality of) second selectable options that, when activated, are configured to perform application-specific actions (e.g., launch the application to a non-default portion of the application, create a new document or communication, initiate a function of the application, or initiate a function of the device that is controlled by the application). This is illustrated in FIGS. 5Q14-5Q16, and 5R1-5R4, for example. In some embodiments, the menu for both the downloading app and the installed app display with a same animation (e.g., with a surface of the menu sliding out from behind the user interface object and displaying above or below the user interface object).
In some embodiments, in response to detecting the first input: in accordance with a determination that the first user interface object corresponds to an application that has not been fully downloaded and that the first input meets action-performing criteria, wherein the action-performing criteria do not require that a characteristic intensity of a contact (e.g., the first contact) in the detected input (e.g., the first input) on the touch-sensitive surface meet the first intensity threshold in order for the action-performing criteria to be met (e.g., in some embodiments, the action-performing criteria are met when the detected first input is a tap input), the device performs (1410) a first action with respect to the downloading of the first application (e.g., pausing the downloading of the first application if the downloading of the first application is already in progress, resuming the downloading of the first application if the downloading of the first application is in a suspended or paused state, and/or starting the downloading of the first application (e.g., prioritizing the downloading of the first application ahead of one or more other applications that are in processes of being downloaded) if the first application is in a waiting state in a queue). This is illustrated in FIGS. 5S1-5S5, for example.
In some embodiments, in response to detecting the first input: in accordance with a determination that the first user interface object corresponds to an application that has been installed on the device and that first input meets action-performing criteria, wherein the action-performing criteria do not require that a characteristic intensity of a contact (e.g., the first contact) in the detected input (e.g., the first input) meet the first intensity threshold in order for the action-performing criteria to be met (e.g., in some embodiments, the action-performing criteria are met when the detected first input is a tap input), the device launches (1412) the first application (e.g., replaces display of the home screen with a default user interface of the first application). This is illustrated in FIGS. 5R6-5R7, for example.
In some embodiments, the one or more first selectable options include (1414) an option that, when activated, is configured to prioritize the downloading of the first application versus one or more other applications that are in processes of being downloaded (e.g., so that the first application is downloaded before the one or more other applications) (e.g., option 5418 in FIG. 5Q5).
In some embodiments, the one or more first selectable options include (1416) an option that, when activated, is configured to pause the downloading of the first application (e.g., so that the device stops downloading the first application) (e.g., option 5420 in FIG. 5Q5).
In some embodiments, the one or more first selectable options include (1418) an option that, when activated, is configured to cancel the downloading of the first application (e.g., so that the device stops downloading the first application, removes the first user interface object from the display and, optionally, deletes any downloaded data for the first application) (e.g., option 5422 in FIG. 5Q5).
In some embodiments, the one or more first selectable options include (1420) an option that, when activated, is configured to resume the downloading of the first application (e.g., option 5438 in FIG. 5Q11). In some embodiments, the option for resuming downloading is displayed only when the downloading of the first application is currently in a paused or suspended state. When the downloading is not in a paused or suspended state, the option for resuming downloading is replaced with an option for pausing the downloading of the first application.
In some embodiments, in accordance with the determination that the first input meets the menu-presentation criteria, the device displays (1422) a second selectable option that, when activated, is configured to display a menu of sharing options for sharing the first application (e.g., option 5424 in FIG. 5Q5). In some embodiments, when an input selecting the option for sharing the first application is detected, a menu of sharing options is presented on or overlaid on the user interface. The menu includes options for, e.g., sharing the first application (e.g., a link to the first application in an app store) via an instant message, an email, one or more social networking applications, and/or one or more wireless connections (e.g., WiFi, Bluetooth connections), and/or copying information (e.g., a link or address of the first application in an app store) associated with the first application. In some embodiments, the share option is also displayed in the menu that is displayed in response to an input that meets the menu-presentation criteria, after the application has been downloaded and installed (e.g., share card 5428 in FIG. 5Q8).
In some embodiments, the device dynamically blurs (1424) the user interface in accordance with a current intensity of the first contact, wherein displaying one or more first selectable options for performing actions with respect to downloading of the first application includes displaying a menu that includes the one or more first selectable options over a blurred version of the user interface. In some embodiments, the menu is displayed over a blurred version of the user interface that is of the same dimensions and scales as the user interface before the blurring. In other words, the menu “pops up” from the first application icon, and is overlaid on top of the blurred user interface. This is illustrated in FIG. 5Q6. In some embodiments, the first application icon is not blurred with the rest of the user interface, the menu occupies less than the full width of the user interface, and the menu is positioned so as not to obscure the first application icon, e.g., as shown in FIG. 5Q6. In some embodiments, the first application icon is blurred with the rest of the user interface, the menu occupies substantially the full width of the user interface, and the menu is positioned without regard to whether it obscure the blurred first application icon, e.g., as shown in FIG. 5Q17.
In some embodiments, the plurality of user interface objects include a second user interface object that corresponds a second application that is in a process of being downloaded; and wherein while displaying the user interface that includes the plurality of user interface objects and before the downloading of the second application is completed, the device detects (1426) a second input that includes detecting a second contact at a location on the touch-sensitive surface that corresponds to the second user interface object. In response to detecting the second input: in accordance with a determination that the second input meets the menu-presentation criteria, the device displays the one or more first selectable options. In some embodiments, the plurality of user interface objects includes multiple application icons (or placeholder icons) that each correspond to a respective application that is in a process of being downloaded; and when a respective input meeting the menu-presentation criteria is detected on each of the multiple application icons (or placeholder icons) (at different time, rather than simultaneously), the device displays an identical menu that includes the one or more first selectable options. This is illustrated in FIGS. 5Q6 and 5Q12 (menu 5416 and menu 5434 have the same set of options (pause and resume download is a toggled option that have two different states that are displayed depending on the current state of the downloading) across the downloading icons for different applications).
In some embodiments, while displaying the user interface that includes the plurality of user interface objects and after the downloading of the first application is completed, the device detects (1428) a third input that includes detecting a third contact at a location on the touch-sensitive surface that corresponds to the first user interface object (e.g., the location of the first application icon). In response to detecting the third input: in accordance with a determination that the third input meets the menu-presentation criteria, the device displays one or more third selectable options that, when activated, are configured to perform application-specific actions associated with the first application. This is illustrated in FIGS. 5Q14-5Q17 (e.g., menu 5450) and 5R1-5R4 (menu 5462), for example.
In some embodiments, in response to detecting the third input: in accordance with a determination that the third input meets application-launching criteria, wherein the application-launching criteria do not require that a characteristic intensity of a contact (e.g., the third contact) in a detected input (e.g., the third input) meet the first intensity threshold in order for the application-launching criteria to be met (e.g., in some embodiments, the application launching criteria are met when the detected third input is a tap input), the device launches (1430) the first application; and, the device replaces the user interface that includes the plurality of user interface objects with a user interface of the first application (e.g., as shown in FIGS. 5R6-5R7). In some embodiments, the application-launching criteria and the action-performing criteria are the same criteria, and the application-launching criteria are used when the application download has been completed, and the action-performing criteria are used when the application download is not yet completed. In some embodiments, in response to detecting a long press can (e.g., a touch input that moves by less than a threshold amount for more than a threshold amount of time), the user interface objects enter a reconfiguration mode in which movements on the touch-sensitive surface at locations that correspond to the user interface objects cause the user interface objects (e.g., application icons for installed applications and representations of downloading applications (e.g., placeholder icons)) can be moved around the user interface (e.g., the application launch user interface, the home screen, etc.).
In accordance with some embodiments,
As shown in
The processing unit 1510 is configured to enable display of (e.g., with enabling unit 1512), on the display, a user interface that includes a plurality of user interface objects that correspond to different applications in a plurality of applications, wherein the plurality of user interface objects include a first user interface object that corresponds a first application that is in a process of being downloaded.
While displaying the user interface that includes the plurality of user interface objects, the processing unit 1510 is configured to detect (e.g., with detecting unit 1514) a first input that includes detecting a first contact at a location on the touch-sensitive surface that corresponds to the first user interface object.
In response to detecting the first input: in accordance with a determination that the first user interface object corresponds to an application that has not been fully downloaded and that the first input meets menu-presentation criteria, wherein the menu-presentation criteria require that a characteristic intensity of a contact in a detected input meet a first intensity threshold in order for the menu-presentation criteria to be met, the processing unit 1510 is configured to enable display of (e.g., with enabling unit 1512) one or more first selectable options that, when activated, are configured to perform actions with respect to downloading of the first application.
As described below, in some embodiments, when a press input is detected on a folder icon, a menu of selected application launching icons are displayed, where the selected application launching icons correspond to applications that have unread notifications, thus the user can quickly select a desired application to access its functions. Each time the menu is displayed, it may display different application icons selected from the folder, depending on which applications have the most recent or more urgent notifications. The method 1600 reduces the number, extent, and/or nature of the inputs from a user when accessing applications within a folder, thereby conserving power and increasing the time between battery charges.
As described below, in some embodiments, when a press input is detected on a folder icon, a menu is displayed to shown an option to rename a folder. The option provides access to multiple folder reconfiguration functions (e.g., icon reconfiguration and folder renaming) with fewer inputs, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to access desired functions faster and more efficiently conserves power and increases the time between battery charges.
As described below, the method 1600 reduces the number, extent, and/or nature of the inputs from a user when accessing folder reconfiguration functions (e.g., icon reconfiguration and folder renaming), thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to access desired content and function faster and more efficiently conserves power and increases the time between battery charges.
At an electronic device with a display, a touch-sensitive surface, and one or more sensors for detecting intensities of contacts on the touch-sensitive surface, the device displays (1602) a user interface (e.g., a home screen, or an application springboard, etc.) on the display, wherein: the user interface includes a folder icon (e.g., as one of a grid of multiple icons, including application icons and/or other folder icons, on a home screen, an application springboard, or a quick access bar) that corresponds to an application folder containing a plurality of application icons (e.g., an “EXTRAS” folder icon that corresponds to an application folder that contains respective application icons for several accessory apps), the plurality of application icons correspond to different applications in a plurality of applications, and the plurality of applications include one or more applications that have one or more unread notifications For example, suppose that, at the time the folder icon is displayed, the application folder includes three application icons that correspond to three different applications, respectively; and two of the three applications each have at least one unread notifications (e.g., one app has twenty unread notifications, and the other app has five unread notifications) and the third application does not have any unread notifications at the present time. In some embodiments, unread notifications correspond to incoming communications that have not been reviewed by the user. In some embodiments, unread notifications correspond to events that have occurred within applications (e.g., applications ready for update, new media ready for download, etc.) but the user has not yet responded to. In some embodiments, unread notifications correspond to alerts that have been generated by applications (e.g., a reminder for a calendar event, an alert for a failure to complete a task (e.g., failure to send a communication, failure to connect to a server, etc.), a request for user input to complete a task (e.g., a request for consent for downloading an application update, making a wireless connection, activating location services, etc.), etc.). FIG. 5T1 illustrates a folder icon 5504 that include multiple applications, some of which have unread notifications (e.g., as indicated by badge 5506 that shows the total number of unread notifications for applications in the folder).
While displaying the user interface that includes the folder icon, the device detects (1604) a first input that includes detecting a first contact at a location on the touch-sensitive surface that corresponds to the folder icon (e.g., contact 5508 on folder icon 5504 in FIG. 5T2).
In response to detecting the first input: in accordance with a determination that the first input meets menu-presentation criteria, wherein the menu-presentation criteria require that a characteristic intensity of a contact (e.g., the first contact) in a detected input (e.g., the first input) meet a first intensity threshold (e.g., a deep press intensity threshold) in order for the menu-presentation criteria to be met, the device displays (1606) one or more selectable options (e.g., a respective menu option in a quick action menu for each of the one or more applications with unread notifications) that, when activated, are configured to launch corresponding applications from the plurality of applications in the application folder that have unread notifications. This is illustrated in FIGS. 5T1-5T5 (e.g., menu 5512 includes three options for launching three applications that have unread notifications, in FIG. 5T5; and menu 5528 include four options for launching four applications that have unread notifications), for example. For example, when two of the three applications each have at least one unread notifications and the remaining one application does not have any unread notifications at the present time, respective menu options for launching the two applications are displayed in the quick action menu, and no menu option is displayed for launching the remaining application that does not currently have any unread notifications. If at a later time, a notification arrives and the remaining application now also has at least one unread notification, when the quick action menu is presented again (e.g., in response to another deep press input on the folder icon), a menu option for launching that remaining application is also presented (e.g., option 5530 is displayed in menu 5528 in FIG. 5T12, but not in menu 5512 in FIG. 5T5). If at a later time, all of the notifications associated with one of the applications are flagged as read or are dismissed, when the quick action menu is presented again (e.g., in response to another deep press input on the folder icon), the menu option for launching that application which no longer has any unread notification is no longer displayed, while the menu options for launching the other two applications that still have unread notifications are displayed in the quick action menu.). In some embodiments, applications are considered to be “in a folder” if icons corresponding to those applications are displayed within the folder.
In some embodiments, the plurality of applications in the application folder include (1608) a first application with one or more unread notifications and a second application with one or more unread notifications; and the one or more selectable options include a first selectable option for launching the first application and a second selectable option for launching the second application. In some embodiments, the respective options for launching the one or more applications with unread notifications each include a respective application icon for a corresponding application, a name of the corresponding application, and an indicator of the type and count of the unread notifications for the corresponding application (e.g., as shown in FIGS. 5T5 and 5T12, respectively).
In some embodiments, the one or more selectable options are (1610) displayed within a menu that is limited to containing no more than a predetermined number of selectable options for launching applications (e.g., limited to four menu options, as shown in FIG. 5T12, four application launching options are displayed when five applications in the folder have unread notifications). Displaying one or more selectable options includes: in accordance with a determination that a first number of applications that correspond to application icons in the folder, less than (or equal to) the predetermined number, have unread notifications (e.g., three (i.e., less than four) applications have unread notifications), the device displays the first number of selectable options corresponding to the first number of applications in the menu (e.g., displaying three selectable options, each option for launching a corresponding one of the three applications that have unread notifications, as shown in FIG. 5T5). In accordance with a determination that a second number of applications that correspond to application icons in the folder, greater than the predetermined number, have unread notifications (e.g., five (i.e., greater than four) applications have unread notifications), the device displays, in the menu, the predetermined number of selectable options corresponding to less than all of the second number of applications (e.g., displaying four selectable options, each option for launching a corresponding one of four out of the five applications that have unread notifications, e.g., as shown in FIG. 5T12).
In some embodiments, displaying, in the menu, the predetermined number of selectable options corresponding to less than all of the second number of applications includes (1612) selecting applications to represent with selectable options in the menu so that applications with more recently received notifications are prioritized over applications with less recently received notifications (e.g., excluding the display of a selectable option for an application for which the most recently received notification was received later than the notifications of the other applications that are represented by application icons in the folder).
In some embodiments, displaying the one or more selectable options includes (1614): when ordering the one or more selectable options for display, prioritizing the selectable options for applications with a first type of unread notifications (e.g., applications with alerts) over the selectable options for applications with a second type of unread notifications (e.g., applications with regular notifications). For example, in some embodiments, when ordering the selectable options in the menu, the options for launching applications with unread alerts are listed before the options for launching applications with unread notifications that are not alerts, e.g., as shown in FIG. 5T12, option 5530 is listed before other options in menu 5528. If the number of applications with alerts is greater than the predetermined number of options set for the menu, then none of the options for launching those applications without any alerts is displayed in the menu.
In some embodiments, displaying the one or more selectable options includes (1616): when ordering the one or more selectable options for display, prioritizing an application with a greater number of unread notifications over an application with a smaller number of unread notifications (e.g., as shown in FIG. 5T5). For example, in some embodiments, when ordering the selectable options in the menu, within a group of applications with the same type of unread notifications (e.g., alerts or non-alert notifications), the options are sorted based on the count of unread notifications for each of the applications in the group. For example, the option for launching an application with three alerts is listed before the option for launching an application with one alert, and after the options for applications with alerts are all listed, the option for launching an application with five notifications is listed before the option for launching an application with three notifications. In some embodiments, after the options are sorted based on notification type and notification count, the options are optionally sorted alphabetically or based on the receipt time of the last notification for each application.
In some embodiments, the device displays (1618), concurrently with the application folder, an indicator (e.g., a badge) specifying an aggregated number of unread notifications for the one or more applications in the application folder with unread notifications. This is illustrated in FIG. 5T5 (e.g., badge 5506 shows that the total number of unread notifications for the applications in folder 5504 is nine), for example. For example, if, at the time the folder icon is displayed, the application folder includes three application icons that correspond to three different applications, respectively; and two of the three applications each have at least one unread notifications (e.g., one app has twenty unread notifications, and the other has five unread notifications) and the remaining one application does not have any unread notifications at the present time), the badge on the folder icon shows “twenty five” which is the sum of twenty and five. In some embodiments, if, while the application folder is displayed, a new notification arrives for one of the three applications (e.g., one of the two applications now has six unread notifications, or the remaining one application now has one unread notification), the badge is automatically updated in real time to show the number “twenty six”.
In some embodiments, displaying the one or more selectable options includes (1620) concurrently displaying: a first selectable option for a first application in the application folder along with an indication of a number of unread notifications for the first application; and a second selectable option for a second application in the application folder along with an indication of a number of unread notifications for the second application. In other words, the device displays, concurrently with the respective selectable options for launching corresponding applications with unread notifications, respective counts of the unread notifications for the corresponding applications. For example, the respective selectable option for launching one of the two applications, e.g., the “Mail” app, includes the Mail app icon, the name of the Mail app, and text specifying that there are twenty unread notifications for the Mail app; and similarly, the respective selectable option for launching the other one of the two applications, e.g., the “Messages” app, includes the Messages app icon, the name of the Messages app, and text specifying that there are five unread notifications for the Messages app. For example, FIG. 5T5 shows that each option (e.g., options 5514, 5516, 5518) displays the number of unread notifications (e.g., 5, 3, and 1) for the application represented in the option.
In some embodiments, while displaying the first selectable option for the first application and the second selectable option for the second application, the device receives (1622) a new notification for the first application; and in response to receiving the new notification, the device updates the indication of the number of unread notifications for the first application (e.g., as shown in FIGS. 5T5 and 5T6, option 5514 is updated (e.g., from showing five unread notifications to showing six unread notifications) when a new notification is received for the Messages application, while menu 5512 is displayed). For example, while the menu displays an option for launching the Mail app with a count indicator “five” for five unread mail messages, and an option for launching the Messages app with a count indicator “three” for three unread instant messages, suppose that a new message is received for the Messages app and a new notification is generated for the new message. The device updates the menu by changing the count indicator for the Messages app to show that the Messages app now has four unread notifications.
In some embodiments, the plurality of applications include (1624) an application that does not have any unread notifications. In response to detecting the first input: in accordance with a determination that the first input meets the menu-presentation criteria, the device foregoes displaying, concurrently with the one or more selectable options for launching corresponding applications that have unread notifications, a selectable option that, when activated, is configured to launch the application that does not have any unread notifications. For example, in some embodiments, if, at the time the quick action menu is displayed (e.g., in response to a deep press input on the folder icon), only the Messages app has five unread notifications, and the Mail app and the Call app do not have any unread notifications, then, only a menu option for launching the Messages app is displayed in the quick action menu, and menu options for launching the Mail app and the Call app are not displayed in the quick action menu. Additionally, if the unread messages from the Messages app become read at a later point in time, then a subsequent menu-display input on the folder icon will cause the device to display a menu that does not have a menu option for launching the Messages app. Similarly, if an app receives a notification, then a subsequent menu-display input on the folder will cause the device to display a menu that has a menu option for launching the app.
In some embodiments, in response to detecting the first input: in accordance with a determination that the first input meets the menu-presentation criteria, the device displays (1626) a selectable option that, when activated, is configured to enable renaming of the application folder (e.g., the menu option for renaming the folder is displayed concurrently with the menu options for launching the application(s) that have unread notifications in the quick action menu) (e.g., option 5520 in FIG. 5T5). In some embodiments, the selectable option for renaming the folder is displayed without regard to whether or not there are any applications with unread notifications in the folder (e.g., a menu-presentation input on a folder that does not contain any applications with unread notifications will cause the device to display a menu that includes a selectable option that, when activated, is configured to enable renaming of the application folder. In some embodiments, enabling renaming of a folder includes transitioning from a mode in which the folder cannot be renamed into a mode in which the folder can be renamed. In some embodiments, the option for renaming the folder is displayed in response to a menu presentation input, without regard to the status of notifications for the applications in the folder.
In some embodiments, while displaying the selectable option for renaming the application folder, the device detects (1628) a second input selecting the selectable option for renaming the application folder (e.g., as shown in FIG. 5V6). In response to detecting the second input: the device displays the application folder containing the plurality of application icons (e.g., displaying a zoomed view of the application icon (e.g., over a blurred version of the user interface (e.g., the home screen))) to show application icons within the application folder in their regular sizes) (e.g., as shown in FIG. 5V8). In some embodiments, the application folder is displayed over a blurred version of the user interface that is of the same dimensions and scales as the user interface before the blurring. In other words, the application folder “pops up” from the folder icon, and is overlaid on top of the blurred user interface. In some embodiments, the folder icon is not blurred with the rest of the user interface, and the view port on the screen zooms into toward the folder icon, with the rest of the user interface expanding away from the folder icon, until the folder icon is expanded into the application icon containing the application icons. In response to detecting the second input, the device displays a folder name of the application folder in an editable state (e.g., by placing a text cursor within the text of the folder name). In some embodiments, when an option in the quick action menu is selected, the menu ceases to be displayed over the blurred user interface. This is illustrated in FIGS. 5V6-5V8, for example.
In some embodiments, in response to detecting the second input, the device displays (1630) an onscreen keyboard concurrently with the folder name of the application folder (e.g., the onscreen keyboard is automatically displayed as soon as the “Rename” option is selected from the quick action menu), wherein an input received through the onscreen keyboard edits the folder name that is displayed in the editable state, e.g., as illustrated in FIG. 5V6.
In some embodiments, in response to detecting the second input, the device presents (1632) the plurality of application icons in a reconfiguration mode within the application folder (e.g., the plurality of application icons are presented in an “jiggling” state, and a user can drag each application icon to a different location within or outside of the application folder, or select an affordance presented on the application icon to delete the application corresponding to the application icon) (e.g., as shown in FIG. 5V6). In some embodiments, other application icons outside of the application folder are also placed in the reconfiguration mode. In some embodiments, when the icons are not presented in a reconfiguration mode, a touch input at a location that corresponds to an application icon and includes movement across the touch-sensitive surface will cause a different page of icons to be displayed.
In some embodiments, while displaying the onscreen keyboard and while displaying the plurality of application icons in the reconfiguration mode, the device detects (1634) a third input through the onscreen keyboard. In response to detecting the third input: the device edits the folder name in accordance with the third input; and continues to display the plurality of application icons in the reconfiguration mode. This is illustrated in FIGS. 5V8-5V10, for example.
In some embodiments, while displaying the onscreen keyboard and while displaying the plurality of application icons in the reconfiguration mode, the device detects (1636) a fourth input selecting one of the plurality of application icons. In response to detecting the fourth input: the device ceases to display the folder name in the editable state; the device ceases to display the onscreen keyboard; and the device continues to present the plurality of application icons in the reconfiguration mode. This is illustrated in FIGS. 5V10-5V11, for example.
In some embodiments, in response to detecting the first input: in accordance with a determination that the first input meets folder-content-display criteria, wherein the folder-content-display criteria do not require that a characteristic intensity of a contact (e.g., the first contact) associated with the detected input (e.g., the first input) meet the first intensity threshold in order for the folder-content-display criteria to be met (e.g., in some embodiments, the folder-content-display criteria are met when the first input is a tap input), the device displays (1638) the application folder containing the plurality of application icons (e.g., without placing the folder name in the editable state and without placing the plurality of application icons in the reconfiguration mode) (e.g., as shown in FIGS. 5U1-5U3). In some embodiments, displaying the application folder includes displaying a zoomed view of the application icon (e.g., over a blurred version of the user interface (e.g., the home screen))) to show application icons within the application folder in their regular sizes. In some embodiments, an animation showing a process of zooming in onto the folder icon is displayed, which results in the zoomed view of the folder icon (and the regular view of the application folder) on the screen. In some embodiments, an animation showing the folder icon popping up from its original location, and morphs into the application folder overlaid on the blurred user interface.
In accordance with some embodiments,
As shown in
The processing unit 1710 is configured to enable display of (e.g., with enabling unit 1712) a user interface on the display unit 1702, wherein: the user interface includes a folder icon that corresponds to an application folder containing a plurality of application icons, the plurality of application icons correspond to different applications in a plurality of applications, and the plurality of applications include one or more applications that have one or more unread notifications.
While displaying the user interface that includes the folder icon, the processing unit 1710 is configured to detect (e.g., with detecting unit 1714) a first input that includes detecting a first contact at a location on the touch-sensitive surface unit 1704 that corresponds to the folder icon.
In response to detecting the first input: in accordance with a determination that the first input meets menu-presentation criteria, wherein the menu-presentation criteria require that a characteristic intensity of a contact in a detected input meet a first intensity threshold in order for the menu-presentation criteria to be met, the processing unit 1710 is configured to enable display of (e.g., with enabling unit 1712) one or more selectable options that, when activated, are configured to launch corresponding applications from the plurality of applications in the application folder that have unread notifications.
As described below, the method 1800 provides an intuitive way to modify the functionality of a control affordance. The method allows the user to choose between a simplified toggle switch versus a more fine-grained control based on characteristic of a single input (e.g., an intensity of a single contact) on the control affordance. Thus, the method reduces the cognitive burden on a user when modifying the functionality of a control affordance, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to modify the functionality of a control affordance faster and more efficiently conserves power and increases the time between battery charges.
The device displays (1802) a control user interface 608 that includes a plurality of control affordances (e.g., control affordances 612-634 as shown in
The device detects (1804) a first input by a contact at a location on a touch-sensitive surface 112 that corresponds to a first control affordance, of the plurality of control affordances. For example, the first input is a contact at a location of Wi-Fi control affordance 614, as indicated by focus selector 640 in
In response to detecting the first input (1806): in accordance with a determination that the first input meets control toggle criteria, wherein the control toggle criteria do not require that a characteristic intensity of the contact meet a first intensity threshold in order for the control toggle criteria to be met (e.g., in some embodiments, the control toggle criteria are met when the characteristic intensity of the contact is below a hint press intensity threshold ITH, a light press intensity threshold ITL or a deep press intensity threshold ITD) (e.g., in some embodiments, the control toggle criteria are met when the first input is a tap input), the device toggles a function of a control that corresponds to the first control affordance; and in accordance with a determination that the first input meets enhanced control criteria, the enhanced control criteria require that the characteristic intensity of the contact meet the first intensity threshold in order for the enhanced control criteria to be met, the device displays one or more modification options for the control that correspond to the first control affordance. For example, as discussed with regard to
While displaying the one or more modification options for the control that correspond to the first control affordance, the device detects (1808) a second input that activates a first modification option of the one or more modification options. For example, an input at a location of modification option 654, as indicated by focus selector 658 of
The device modifies (1810) the control that corresponds to the first control affordance in accordance with the activated first modification option. For example, in response to the input by a contact at a location indicated by focus selector 658 in
By providing different responses to inputs that meet different criteria, a single input affordance is usable to adjust a wider variety of functionality. The navigation required to access device features (such as changing a Wi-Fi network to which the device is connected, temporarily disabling a Wi-Fi network, or other features describe below in Table 1) is reduced, conserving device battery life.
Table 1 is a listing of toggle/control functions and modification options that correspond to device controls, in accordance with some embodiments.
In some embodiments, the second input that activates the first modification option also toggles (1812) the function of the control that corresponds to the first control affordance. For example, the second input activates a modification option (e.g., selects a Wi-Fi network) and also toggles the control (e.g., turns Wi-Fi on with the selected network). In another example, the second input turns on a flashlight with a selected flashlight mode. For example, in response to the input by a contact at a location indicated by focus selector 658 in
In some embodiments, modifying the control that corresponds to the first control affordance in accordance with the activated first modification option includes (1814): in accordance with a determination that the function is on when the second input is detected, modifying the function in accordance with the first modification option; (e.g., turning a brightness of a flashlight from a low setting to a high setting if the high setting is selected) and, in accordance with a determination that the function is off when the second input is detected, turning the function on with modification in accordance with the first modification option (e.g., turning the flashlight from off to on at a high setting if the high setting is selected). For example, a second input is an input that adjusts an adjustable control 680 as shown in
In some embodiments, the modification option modifies (1816) a mode (e.g., a flashlight level, such as high, warm light and/or low) of the control that corresponds to the first control affordance. For example, modification options 696, 698, 6100, and 6102 listed in modification option menu 694 of
In some embodiments, modifying the control that corresponds to the first control affordance in accordance with the activated first modification option includes (1818) setting reversion criteria for the control. Reversion criteria include, e.g., criteria that are met when a time duration has passed, criteria that are met when a device arrives at a location (e.g., a geofence, city, and/or address), criteria that are met when a device departs from a location; and/or criteria that are met at a future point in time. In accordance with a determination that the reversion criteria are met, the device reverts the control that corresponds to the first control affordance to a prior state of the control (e.g., the previous state and/or default state). For example, the selected modification option enables/disables Wi-Fi in accordance with the reversion criteria (e.g., when the device leaves a designated area, as indicated by modification option 654 in
In some embodiments, in accordance with a determination that the characteristic intensity of the contact meets the enhanced control criteria, the device determines (1820) a (current) state of the control that corresponds to the first control affordance. For example, the device determines a state of a timer (e.g., running, not running) that corresponds to timer control affordance 624 in
In accordance with a determination that the characteristic intensity of the contact in the first input meets the enhanced control criteria (1826), the device concurrently displays a current value of a parameter of the control (e.g., a current time status of a timer) with the one or more modification options for the control that corresponds to the first control affordance. For example, user interface 678 for setting a timer includes a timer duration (e.g., a default timer duration and/or a previously set timer duration, such as the text that indicates “12 minutes” and the position of the adjustable control 680), and user interface 682 that indicates progress of a running timer includes a timer progress indication (e.g., the text that indicates “1:42” and the position of the progress indicator in progress bar 684). In some embodiments, the current value of the parameter of the control is displayed instead of the one or more modification options for the control (e.g., when the control was previously set and activated).
In some embodiments, the first control affordance is (1828) a first application affordance (e.g., an application icon, such as camera control affordance 630) that corresponds to a first application (e.g., a camera application). A second application affordance (e.g., camera application icon 430 in
In some embodiments, the one or more modification options for the control that corresponds to the first control affordance include (1836) at least one network connection activation option (e.g., Wi-Fi network pairing options such as 656, 664, and/or 666 in
In some embodiments, the control user interface partially overlays (1838) a portion of a second user interface that is distinct from the control user interface (e.g., a springboard, lock screen, or application user interface). For example, as shown in
In some embodiments, the control user interface 608 includes (1840) a plurality of controls (e.g., control affordances 612-634, as shown in
It should be understood that the particular order in which the operations in
In accordance with some embodiments,
As shown in
The processing unit 1908 is configured to enable display (e.g., with enabling unit 1910) of a control user interface that includes a plurality of control affordances. The processing unit 1908 is configured to detect (e.g., with detecting unit 1912) a first input by a contact at a location on the touch-sensitive surface unit that corresponds to a first control affordance, of the plurality of control affordances, on the display unit. In response to detecting the first input: in accordance with a determination that the first input meets control toggle criteria, wherein the control toggle criteria do not require that the characteristic intensity of the contact meet a first intensity threshold in order for the control toggle criteria to be met, the processing unit 1908 is configured to toggle (e.g., with toggling unit 1914) a function of a control that corresponds to the first control affordance. In accordance with a determination that the first input meets enhanced control criteria, wherein the enhanced control criteria require that the characteristic intensity of the contact meet the first intensity threshold in order for the enhanced control criteria to be met, the processing unit 1908 is configured to enable display (e.g., with enabling unit 1910) of one or more modification options for the control that correspond to the first control affordance. While displaying the one or more modification options for the control that correspond to the first control affordance, the processing unit 1908 is configured to detect (e.g., with detecting unit 1912) a second input that activates a first modification option of the one or more modification options. The processing unit 1908 is configured to modify (e.g., with modifying unit 1916) the control that corresponds to the first control affordance in accordance with the activated first modification option.
The operations in the information processing methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to
As described below, the method 2000 provides an intuitive and effective way to delete content. The method reduces the tedious repetitions of a deletion input required of a user when deleting content, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to delete content faster and more efficiently conserves power and increases the time between battery charges.
The device displays (2002) a user interface (e.g., 702) that includes: an editable content area (e.g., 704) that has a plurality of characters, and a content deletion control (e.g., 708 (e.g., a delete key in a content input area such as a keyboard 709), e.g., as shown in
The device detects (2004) a deletion input that includes detecting a contact (e.g., as indicated by focus selector 710) at a location on the touch-sensitive surface that corresponds to the content deletion control (e.g., 708) on the display.
In response to detecting the deletion input, the device deletes (2006) content (e.g., one or more characters) in the editable content area (e.g., 704) based on a duration and a characteristic intensity of the contact.
In accordance with a determination that the contact was maintained for a first time period without the characteristic intensity of the contact increasing above a first intensity threshold (e.g., the characteristic intensity of the contact remains below a light press intensity threshold ITL or a deep press intensity threshold ITD), the device deletes (2008) the content in the editable content area (e.g., 704) by sequentially deleting a plurality of sub-units of the content of a first type of sub-unit of the content (e.g., deleting text character-by-character, as illustrated at
In accordance with a determination that the contact was maintained for a second time period that is longer than the first time period, without the characteristic intensity of the contact increasing above the first intensity threshold, the device deletes (2010) the content in the editable content area (e.g., 704) by sequentially deleting a plurality of sub-units of the content of a second type of sub-unit of the content (e.g., deleting text word-by-word, as illustrated at
In some embodiments, in accordance with a determination that the characteristic intensity of the contact increased above the first intensity threshold, the device deletes (2012) the content in the editable content area (e.g., 704) by sequentially deleting a plurality of sub-units of the content at a rate that varies based on the characteristic intensity of the contact. For example, in
In some embodiments, deleting the content in the editable content area (e.g., 704) by sequentially deleting the plurality of sub-units of the content at the rate that varies based on the characteristic intensity of the contact includes (2014), in accordance with a determination that the characteristic intensity increases above the first intensity threshold after the contact has been maintained on the touch-sensitive surface for the first time period, increasing the rate of deletion of the first type of sub-unit of the content (e.g., deleting text character-by-character) in the editable content area as the intensity of the contact increases. For example, in
In some embodiments, deleting the content characters in the editable content area by sequentially deleting the plurality of sub-units of the content at the rate that varies based on the characteristic intensity of the contact includes (2016), in accordance with a determination that the characteristic intensity of the contact increases above the first intensity threshold after the contact has been maintained on the touch-sensitive surface for the first time period, continuing to delete the first type of sub-unit of the content (e.g., deleting text character-by-character) in the editable content area after the contact has been maintained on the touch-sensitive surface for the second time period instead of switching to deleting the second type of sub-unit of the content (e.g., deleting text word-by-word). For example, in
In some embodiments, deleting the content in the editable content area (e.g., 704) by sequentially deleting the plurality of sub-units of the content at the rate that varies based on the characteristic intensity of the contact includes (2018), in accordance with a determination that the characteristic intensity first increases above the first intensity threshold after the contact has been maintained on the touch-sensitive surface for the second time period, increasing the rate of deletion of the second type of sub-unit of the content (e.g., deleting text word-by-word, as illustrated at
In some embodiments, deleting the content in the editable content area (e.g., 704) by sequentially deleting the plurality of sub-units of the content at the rate that varies based on the characteristic intensity of the contact includes (2020), in accordance with a determination that the characteristic intensity increases above the first intensity threshold after the contact has been maintained on the touch-sensitive surface for the first time period and before the contact has been maintained on the touch-sensitive surface for the second time period, starting to sequentially delete the plurality of sub-units of the content of the second type of sub-unit of the content (e.g., deleting text word-by-word, as illustrated at
In some embodiments, starting to sequentially delete the plurality of sub-units of the content of the second type of sub-unit of the content (e.g., deleting text word-by-word, as illustrated at
In some embodiments, after starting to sequentially delete the plurality of sub-units of the content of the second type of sub-unit of the content (e.g., deleting text word-by-word, as illustrated at
In some embodiments, in accordance with a determination that liftoff of the contact was detected before the contact was maintained on the touch-sensitive surface for more than a tap time threshold, a single character is deleted (2026) from the content. For example, in
In some embodiments, the user interface (e.g., 702) includes (2028) a content insertion indicator (e.g., 716) (e.g., text cursor) that is displayed within the editable content area (e.g., 704); and deleting the content in the editable content area includes deleting the plurality of sub-units of the content from a location in the editable content area that corresponds to the content insertion indicator. For example, as illustrated at
In some embodiments, the device detects (2030) a repositioning input that includes detecting a second contact at a second location (e.g., as indicated by focus selector 732a) on the touch-sensitive surface, wherein the second location on the touch-sensitive surface is distinct from the location that corresponds to the content deletion control (e.g., 708). In accordance with a determination that a characteristic intensity of the second contact increased above the first intensity threshold (e.g., a light press intensity threshold ITL or a deep press intensity threshold ITD, as indicated by intensity meter 712) the device activates (2032) a content insertion indicator repositioning mode. While the content insertion indicator repositioning mode is active, the device (2034): displays indicia (e.g., replacing autocorrect text and/or text on the keys of the keyboard with blank space, as illustrated at
In some embodiments, the device includes (2040) one or more tactile output generators.
In some embodiments, the device outputs (2042), with the one or more tactile output generators, a plurality of tactile outputs, wherein a respective tactile output in the plurality of tactile outputs is triggered based on deletion of a respective sub-unit of the plurality of sub-units of the content. For example, as shown in
In some embodiments, a tactile output profile (e.g., including one or more parameters such as amplitude, duration, damping, and/or frequency) of a respective tactile output in the plurality of tactile outputs varies (2044) based on the characteristic intensity of the contact. For example, as shown in
In some embodiments, the user interface includes (2046) a content input area (e.g., 740) (e.g., of which the content deletion control 708 is a part) that includes a plurality of keys that are distinct from the content deletion control; and one or more keys of the plurality of keys that are distinct from the content deletion control (e.g., 708) (e.g., one or more character keys) do not trigger a tactile output when activated. In some embodiments, other keys (e.g., a keyboard switching key (for switching between different language keyboards), a keyboard mode-switching key (for switching between a letter keyboard and a number keyboard), and/or a shift key) that are non-character keys do trigger tactile outputs.
In some embodiments, the device detects (2048) a menu-display input at a location on the touch-sensitive surface that corresponds to a content input area (e.g., 740). In response to detecting the menu-display input, the device displays (2050) a menu that includes one or more menu items (e.g., an alternate letter selection menu and/or an alternate keyboard menu) in the user interface. For example, as shown in
In some embodiments, the user interface includes (2056) a content input area (e.g., 740) (e.g., of which the content deletion control is a part) that includes a plurality of keys that are distinct from the content deletion control (e.g., 708). The device detects (2058) a first input at a first location that corresponds to a first key of the content input area (e.g., an input at a location that corresponds to the “A” key as indicated by focus selector 732 of
In some embodiments, the electronic device includes (2064) one or more audio output generators.
In some embodiments, the user interface includes (2066) a content input area (e.g., 740) (e.g., of which the content deletion control 708 is a part) that includes a plurality of keys that are distinct from the content deletion control (e.g., 708). The device detects (2068) a first input at a first location that corresponds to a first key of the content input area (e.g., an input at a location that corresponds to the “A” key as indicated by focus selector 732 of
In some embodiments, the user interface includes (2074) a content input area (e.g., 740) (e.g., of which the content deletion control 708 is a part) that includes a plurality of keys that are distinct from the content deletion control (e.g., 708). In response to detecting the deletion input, the device outputs (2076) a first audio output that has a first audio output profile. The device detects (2078) a first input at a first location that corresponds to a first key of the plurality of keys that are distinct from the content deletion control (e.g., 708). In accordance with a determination that the first key has a first key type (e.g., a letter key), the device outputs (2080) a second audio output that has a second audio output profile, distinct from the first audio output profile. In some embodiments, when audio output for keys is varied based on typing speed that variation is variation in a parameter that is different from the parameter(s) that differentiate the audio output for the delete key from the audio output for keys of the first type (e.g., character keys), so that even when the audio output of the keys is varied based on typing speed the sound output for the first type of keys is different from the sound output for the delete key.
In some embodiments, in accordance with a determination that the first key has a second key type (e.g., a space key, a shift key, and/or a keyboard switching key), the device outputs (2082) a third audio output that has a third audio output profile that is distinct from the first audio output profile and the second audio output profile. In some embodiments, when audio output for keys is varied based on typing speed that variation is variation in a parameter that is different from the parameter(s) that differentiate the audio output for the delete key from the audio output for keys of the first type (e.g., character keys) and the second type (e.g., a space key, a shift key, and/or a keyboard switching key), so that even when the audio output of the keys is varied based on typing speed the sound output for the first type of keys is different from the sound output for the delete key and the sound output from the second type of keys.
It should be understood that the particular order in which the operations in
In accordance with some embodiments,
As shown in
The processing unit 2108 is configured to: enable display of (e.g., with enabling unit 2110) a user interface that includes: an editable content area that has a plurality of characters, and a content deletion control. The processing unit 2108 is configured to detect (e.g., with detecting unit 2112) a deletion input that includes detecting a contact at a location on the touch-sensitive surface unit 2104 that corresponds to the content deletion control on the display unit 2102. In response to detecting the deletion input, the processing unit 2108 is configured to delete (e.g., with deleting unit 2114) content in the editable content area based on a duration and a characteristic intensity of the contact. In accordance with a determination that the contact was maintained for a first time period without the characteristic intensity of the contact increasing above a first intensity threshold, the processing unit 2108 is configured to delete (e.g., with deleting unit 2114) the content in the editable content area by sequentially deleting a plurality of sub-units of the content of a first type of sub-unit of the content at a rate that does not vary based on the characteristic intensity of the contact. In accordance with a determination that the contact was maintained for a second time period that is longer than the first time period without the characteristic intensity of the contact increasing above the first intensity threshold, the processing unit 2108 is configured to delete (e.g., with deleting unit 2114) the content in the editable content area by sequentially deleting a plurality of sub-units of the content of a second type of sub-unit of the content at a rate that does not vary based on the characteristic intensity of the contact. In accordance with a determination that the characteristic intensity of the contact increased above the first intensity threshold, the processing unit 2108 is configured to delete (e.g., with deleting unit 2114) the content in the editable content area by sequentially deleting a plurality of sub-units of the content at a rate that varies based on the characteristic intensity of the contact.
As described below, the method 2200 provides an intuitive way to present special effect options for a message in a messaging interface. The method reduces the cognitive burden on a user when preparing a message to be sent with special effects, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to detecting input at a messaging interface faster and more efficiently conserves power and increases the time between battery charges.
The device displays (2202) a messaging interface (e.g., 802) that includes a conversation transcript (e.g., 804) and a message input area (e.g., 806). Message input area (e.g., 806) includes an affordance (e.g., 810) for sending a message. While message input area (e.g., 806) contains message content (e.g., 808), the device detects (2204) a first input by a contact (e.g., as indicated by focus selector 812, as shown in
The device determines (2206) a characteristic intensity of the contact in the first input. For example, the characteristic intensity of the contact indicated by focus selector 812 is indicated by intensity meter 814.
In response to detecting the first input (2208), in accordance with a determination that the first input meets send criteria (e.g., a tap gesture), wherein the send criteria do not require that a characteristic intensity of the contact meet a first intensity threshold in order for the send criteria to be met, the device initiates (2210) sending the message content to a remote device (e.g., with a default animation to be displayed when the message is received at the remote device). For example, when the first input meets send criteria, the message is sent to remote device 820 and the message content 808 is displayed by remote device 820 as shown in
In response to detecting the first input (2208), in accordance with a determination that the contact meets (first) message impact criteria, wherein the (first) message impact criteria require that the characteristic intensity of the contact meet the first intensity threshold in order for the (first) message impact criteria to be met (e.g., in some embodiments, the message impact criteria are met when the characteristic intensity of the contact meets a light press intensity threshold ITL or a deep press intensity threshold ITD), the device displays (2212) a plurality of message impact effect options (e.g., 822 (“Slam”), 824 (“Loud”), 826 (“Gentle”), and/or 828 (“Invisible Ink”) as shown in
While displaying the plurality of message impact effect options (e.g., in message impact effect options interface 830 as shown in
In response to detecting the second input, in accordance with a determination that the second input was received at a location on the touch-sensitive surface that corresponds to a first message impact effect option of the plurality of impact effect options (e.g., at affordance 847 for sending message content 808 with a “Loud” message impact effect option), the device initiates sending (2216), to the remote device (e.g., 820), the message content (e.g., 808) with the first message impact effect option (e.g., “Loud” message impact effect option 824). In some embodiments, the first message impact effect option includes an animation to be displayed when the message is received at the remote device (e.g., 820) that is different from the default animation with which the message is displayed when it is sent via a tap input on the send affordance.
In accordance with a determination that the second input is detected at a location on the touch-sensitive surface that corresponds to a second message impact effect option of the plurality of message impact effect options (e.g., at affordance 847 for sending message content 808 with a “Slam” message impact effect option 822), the device initiates sending (2218) to the remote device (e.g., 820), the message content with the second message impact effect option (e.g., with an impact animation that is different from an impact animation that corresponds to the first message impact effect option, such an animation illustrated at
In some embodiments, the contact in the first input and the contact in the second input are the same contact (e.g., as indicated by focus selector 812), and the contact is continuously detected (2220) on the touch-sensitive surface (e.g., 112) between the time that the first input is detected and the time that the second input is detected. For example, a single contact makes a first press input on the send icon 810 (e.g., a contact at a location that corresponds to send icon 810 with a characteristic intensity that increases above a deep press intensity threshold ITD or a light press intensity threshold ITL) to bring up a menu of message impact effect options (e.g., message impact effect options 822-828); then, the same contact slides to a respective message impact effect in the menu to select the respective message impact effect option; and finally the same contact presses on the respective message impact effect option (or, in some embodiments, lifts off from the respective message impact effect option) to initiate sending the message with the respective message impact effect option.
Alternatively, in some embodiments, the contact in the first input and the contact in the second input are different contacts that are not continuously detected on the touch-sensitive surface (e.g., 112) between the time that the first input is detected and the time that the second input is detected. For example, a first contact makes a first input on the send affordance 810 (e.g., a contact at a location that corresponds to send icon 810 with a characteristic intensity that increases above a deep press intensity threshold ITD or a light press intensity threshold ITL) to bring up a menu of message impact effect options (e.g., message impact effect options 822-828). Then, the first contact lifts off the touch-sensitive surface, ending the contact with the touch-sensitive surface. After lift-off of the first contact, and while the menu of message impact effect options is still displayed, a second contact is detected touching down on the touch-sensitive surface (e.g., 112) as part of an input at a location that corresponds to the respective message impact effect option (e.g., as part of a tap gesture or deep press on the respective message impact effect option). Then, in response to the input by the second contact, the electronic device initiates sending the message with the respective message impact effect option. In this example, the same finger may be used to make the contact in the first input and the contact in the second input.
In some embodiments, the device detects (2222) an option preview input (e.g., that is detected while the contact is continuously detected on the touch-sensitive surface 112) that moves across the touch-sensitive surface (e.g., 112) along locations (e.g., locations on message impact effect option selection control 836) that correspond to the plurality of impact effect options. In response to detecting the option preview input (2224): in accordance with a determination that the option preview input has moved to a first location on the touch-sensitive surface that corresponds to the first message impact effect option of the plurality of impact effect options (e.g., at affordance 847 for sending message content 808 with a “Loud” message impact effect option 824), the device displays a first preview of the message content (e.g., 808) with the first message impact effect option (e.g., as illustrated at
In some embodiments, in response to detecting the option preview input (2226): in accordance with a determination that the option preview input has moved to the first location on the touch-sensitive surface that corresponds to the first message impact effect option of the plurality of impact effect options (e.g., at affordance 847 for sending message content 808 with a “Loud” message impact effect option 824), the device outputs, with one or more tactile output generators, a first tactile output; and in accordance with a determination that the option preview input has moved to the second location on the touch-sensitive surface that corresponds to a second message impact effect option of the plurality of impact effect options (e.g., at affordance 847 for sending message content 808 with a “Slam” message impact effect option 822), the device outputs, with the one or more tactile output generators, a second tactile output. For example,
In some embodiments (2228), the first tactile output has a first tactile output profile, and the second tactile output has a second tactile output profile that is the same as the first tactile output profile. A tactile output profile includes, e.g., one or more parameters such as amplitude, duration, damping, and/or frequency. For example, in
In some embodiments (2230), the first tactile output has a first tactile output profile that corresponds to the first message impact effect option, and the second tactile output has a second tactile output profile, distinct from the first tactile output profile, that corresponds to the second message impact effect option. For example, for a more emphatic message impact effect option, the tactile output has a higher peak amplitude and/or longer duration, while for a less emphatic message impact effect option the tactile output has a lower peak amplitude and/or shorter duration.
In some embodiments, a characteristic intensity of the contact in the second input satisfies (2232) a second intensity threshold. In some embodiments, the second intensity threshold is the same as the first intensity threshold. In some embodiments, the second intensity threshold is different from the first intensity threshold. In some embodiments, a press input by a contact on a respective message impact effect option that satisfies an intensity threshold (e.g., a characteristic intensity of the contact that increases above a light press intensity threshold ITL or a deep press intensity threshold ITD) is needed to initiate sending the message content with the respective message impact effect.
In some embodiments (2234), in response to detecting the second input, in accordance with the determination that the second input was received at a location on the touch-sensitive surface that corresponds to the first message impact effect option (e.g., at affordance 847 for sending message content 808 with a “Loud” message impact effect option 824), outputting, with one or more tactile output generators of the electronic device, at least one tactile output that corresponds to sending the message content with the first message impact effect option. In some embodiments, tactile output is provided when the second input is a deep press gesture (e.g., when the input includes a contact with a characteristic intensity that increases above deep press intensity threshold ITD, as indicated by intensity meter 814). In some embodiments, tactile output is not provided when the second input is a tap gesture. In some embodiments, tactile output is not provided when the second input is a lift off of the contact.
In some embodiments (2236), second message impact criteria include a criterion that is met when a duration of the contact with the touch-sensitive surface satisfies a first time threshold (e.g., a long press time threshold), the second input is a lift off of the contact, and: in response to detecting the first input, in accordance with a determination that the contact meets the second message impact criteria, the device displays the plurality of message impact effect options (e.g., message impact effect options 822-828). In some embodiments, in accordance with a determination that the contact does not meet the second message impact criteria, the device forgoes displaying the plurality of message impact effect options.
In some embodiments (2238), second message impact criteria include a criterion that is met when a duration of the contact with the touch-sensitive surface satisfies a first time threshold (e.g., a long press time threshold); and the second input is a tap gesture; and in response to detecting the first input, in accordance with a determination that the contact meets the second message impact criteria, the device displays the plurality of message impact effect options (e.g., message impact effect options 822-828). In some embodiments, in accordance with a determination that the contact does not meet the second message impact criteria, the device forgoes displaying the plurality of message impact effect options.
In some embodiments, the conversation transcript (e.g., 804) includes (2240) a received message (e.g., 873) displayed in a message region (e.g., 874) (e.g., as shown in
In some embodiments, the conversation transcript includes (2250) a message (e.g., 893) displayed in a message region (e.g., 894) (e.g., a received message or a sent message) and a plurality of acknowledgements (e.g., 896) that correspond to the message region (e.g., 894) (e.g., as shown in
In some embodiments, the conversation transcript (e.g., 804) includes (2256) a message region (e.g., 852) with content (e.g., 808) that is hidden by a screen (e.g., 852), e.g., as illustrated in
In some embodiments, an area of the portion of the screen varies (2262) based on the characteristic intensity of the contact (e.g., the area of the screen 854 diminishes as the characteristic intensity of the contact increases, as illustrated at
In some embodiments, the device detects (2264) a seventh input (e.g., a continuation of the sixth input); and in response to detecting the seventh input, in accordance with a determination that the seventh input meets full message reveal criteria that include a criterion that is met when a characteristic intensity of the contact (e.g., as indicated by focus selector 860) satisfies a third intensity threshold (e.g., a threshold that is distinct from the second intensity threshold, such as a deep press intensity threshold ITD, as indicated by intensity meter 814 of
In some embodiments, the device varies (2268) an extent of a blurring effect applied to at least a part of the messaging interface (e.g., 802) (e.g., blurring the display except for the affordance for sending the message 810, the message input area 806, and/or the plurality of message impact effect options, e.g., as indicated at
It should be understood that the particular order in which the operations in
In accordance with some embodiments,
As shown in
The processing unit 2310 is configured to enable display (e.g., with the display enabling unit 2312) of, on the display unit 2302, a messaging interface that includes a conversation transcript and a message input area, where the message input area includes an affordance for sending a message. While the message input area contains message content, the processing unit 2310 is configured to detect (e.g., with the detecting unit 2314) a first input by a contact at a location of the touch-sensitive surface unit 2304 that corresponds to the affordance for sending the message. The processing unit 2310 is configured to determine (e.g., with the determining unit 2316) a characteristic intensity of the contact in the first input. In response to detecting the first input, the processing unit 2310 is configured to: in accordance with a determination that the first input meets send criteria, wherein the send criteria do not require that a characteristic intensity of the contact meet a first intensity threshold in order for the send criteria to be met, initiate sending the message content to a remote device (e.g., with sending unit 2318); and, in accordance with a determination that the contact meets message impact criteria, wherein the message impact criteria required that the characteristic intensity of the contact meet the first intensity threshold in order for the message impact criteria to be met, enable display (e.g., with the display enabling unit 2312) of a plurality of message impact effect options for changing an animation that is displayed when the message is received at the remote device. While displaying the plurality of message impact effect options, the processing unit 2310 is configured to detect (e.g., with the detecting unit 2314) a second input by a contact to send the message content with a selected message impact effect option of the plurality of impact effect options. In response to detecting the second input, in accordance with a determination that the second input was received at a location on the touch-sensitive surface unit 2304 that corresponds to a first message impact effect option of the plurality of impact effect options, the processing unit is configured to initiate sending (e.g., with the sending unit 2318), to the remote device, the message content with the first message impact effect option.
FIGS. 24A1-24A3 are flow diagrams illustrating a method 2400A of displaying intensity-reactive and intensity-nonreactive user interface objects in accordance with some embodiments. The method 2400A is performed (2402) at an electronic device (e.g., device 300,
The device displays (2402), on the display, a user interface (e.g., user interface 900, FIG. 9A1, or user interface 902, FIG. 9B1) that includes a plurality of activatable objects, including a first activatable object with a first visual appearance (e.g., messages icon 902, FIG. 9A1, or e-mail message 930, FIG. 9B1).
The device is configured to (2404), for intensity-reactive activatable objects (e.g., messages icon 902, FIG. 9A1, or electronic mail object 930, FIG. 9B1), perform (2406) operations corresponding to the intensity-reactive activatable objects based on characteristic intensities of inputs on the touch-sensitive surface that correspond to the intensity-reactive activatable objects, such that when a characteristic intensity of a contact that is providing input that corresponds to a respective intensity-reactive activatable object on the touch-sensitive surface meets intensity-based activation criteria (e.g., an intensity threshold such as ITL, FIGS. 9A15 and 9B5), an operation corresponding to the respective intensity-reactive activatable object is performed as a result of the characteristic intensity of the contact meeting the intensity-based activation criteria (e.g., a quick actions menu 914, FIG. 9A15, or a preview of e-mail message 930, FIG. 9B5, is displayed).
In some embodiments, the intensity-reactive activatable objects cause operations driven based on the intensity of the contact, such as the display of a hint animation, a quick action menu, or a peek platter (e.g., quick actions menu 914, FIG. 9A15, or peek platter of e-mail message 930, FIG. 9B5). In some embodiments, when a characteristic intensity of a contact that is providing input that corresponds to a respective intensity-reactive activatable object on the touch-sensitive surface meets intensity-based activation criteria, an appearance of the respective intensity-reactive activatable object is transformed based on the change in characteristic intensity of the contact.
The device is configured to (2404), for intensity-nonreactive activatable objects (2408), perform operations corresponding to the intensity-nonreactive activatable objects without regard to whether inputs on the touch-sensitive surface that correspond to the intensity-nonreactive activatable objects meet the intensity-based activation criteria, such that when a characteristic intensity of a contact that is providing input that corresponds to a respective intensity-nonreactive activatable object on the touch-sensitive surface meets the intensity-based activation criteria, an operation corresponding to the respective intensity-nonreactive activatable object is not performed as a result of the characteristic intensity of the contact meeting the intensity-based activation criteria. For example, as shown in FIG. 9A2-9A7, for intensity-nonreactive weather icon 904, displaying the weather application, FIG. 9A7, is performed upon liftoff of user input 910 without regard to whether user input 910 meets one or more intensity thresholds ITH, ITL, or ITD.
For example, in some embodiments, the satisfaction of the intensity-based activation criteria is ignored when determining whether or not to perform an operation corresponding to the intensity-nonreactive activatable object, and other activation criteria are used instead, such as whether liftoff of the contact was detected without more than a threshold amount of movement, and/or whether liftoff of the contact was detected within a threshold amount of time from detecting touchdown of the contact. In some embodiments, intensity-nonreactive activatable objects do not cause operations driven based on the intensity of the contact, such as the display of a hint animation, a quick action menu, or a peek platter. In some embodiments, when a characteristic intensity of a contact that is providing input that corresponds to a respective intensity-nonreactive activatable object on the touch-sensitive surface meets the intensity-based activation criteria, an appearance of the respective intensity-nonreactive activatable object is not transformed based on the change in the characteristic intensity of the contact.
While displaying the user interface on the display, the device detects (2410) an input (e.g., user input 912, FIG. 9A12, or user input 915, FIG. 9B2) that corresponds to a request to select the first activatable object (e.g., messages icon 902, FIG. 9A12, or e-mail message 930, FIG. 9B2) in the plurality of activatable objects, wherein a characteristic intensity of the input (e.g., as shown in user input intensity graph 906, FIG. 9A12, or user input intensity graph 906, FIG. 9B2) fails to meet the intensity-based activation criteria during the input (e.g., the contact that performed the input maintains an intensity that is below the respective intensity threshold, e.g., ITH, during the input).
In some embodiments, the device is configured (2412) to change an appearance of intensity-reactive activatable objects using a respective transformation (e.g., a first portion of a hint state) of the activatable objects, wherein the respective transformation is adjusted dynamically as the characteristic intensity of the contact on the touch-sensitive surface changes through a range of intensity values up to a threshold intensity value (e.g., a “hint” threshold (e.g., ITH)).
In some embodiments, for intensity-reactive activatable objects (e.g., messages icon 902, FIG. 9A12, or e-mail message 930, FIG. 9B2), the operations include (2414) displaying a preview of related content (e.g., quick actions menu 914, FIG. 9A15, or peek platter of e-mail message 930, FIG. 9B5) for a respective intensity-reactive activatable object as a result of the characteristic intensity of the contact meeting the intensity-based activation criteria (e.g., a “hint” threshold such as ITH); and for intensity-nonreactive activatable objects, the operations do not include displaying a preview of related content as a result of the characteristic intensity of the contact meeting the intensity-based activation criteria.
In response to detecting the input (e.g., user input 912, FIG. 9A12, or user input 915, FIG. 9B2) (2416), in accordance with a determination that the first activatable object is an intensity-reactive activatable object, the device displays (2418) the first activatable object with a first transformation from its first visual appearance (e.g., increasing a size of the first activatable object from its initial size, or decreasing a size of the first activatable object from its initial size, as shown in FIG. 9A12 or FIG. 9B2). Changing the appearance of intensity-reactive activatable objects by applying a first transformation provides the user with feedback about the level of intensity that is being detected by the device and provides visual feedback to the user indicating that the activatable object is intensity-reactive, and that pressing harder will cause the device to perform one or more operations associated with intensity-reactive objects. 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).
In some embodiments, the first transformation is (2420) an initial portion of a change in visual appearance of a respective intensity-reactive object (e.g., a hint state).
In some embodiments, an extent of the first transformation for an intensity-reactive activatable object varies (2422) based on the characteristic intensity of a contact during the input (e.g., a larger size increase or decrease for a hard tap than for a light tap and/or a larger movement in a virtual z direction for a hard tap than for a light tap).
In accordance with a determination that the first activatable object is an intensity-nonreactive activatable object, the device displays (2424) the first activatable object without displaying the first transformation (e.g., darkening the first activatable object without increasing the size of the first activatable object from its initial size, such as for weather icon 904, FIGS. 9A3-9A6).
In some embodiments, the input is (2426) a tap input (e.g., an input that meets activation criteria for the first activatable object that are capable of being met without the contact having an intensity above an intensity threshold that is part of the intensity-based activation criteria), and, in response to detecting the tap input, the device performs an activation operation that corresponds to the first activatable object (e.g., without regard to whether the object is an intensity-reactive object or an intensity-nonreactive object, such as launching weather application corresponding to weather icon 904, FIG. 9A7).
In some embodiments, the detected input that corresponds to the request to select the first activatable object is (2428) a first part of a contact with the touch-sensitive surface; the detected input that corresponds to the request to select the first activatable object is associated with a first gesture; the device detects a second part of the contact with the touch-sensitive surface (e.g., subsequent to the first part); and, in accordance with a determination that the second part of the contact is not associated with the first gesture, the device dynamically reduces display of the first transformation of the first activatable object (e.g., a first part of the contact by user input 912 is associated with a tap gesture, FIG. 9A16, a second part of the contact by user input 912 is associated with a scroll gesture, FIG. 9A17, and the first transformation of messages icon 902 is dynamically reduced from FIG. 9A16 to FIG. 9A17).
FIGS. 24B1-24B3 are flow diagrams illustrating a method 2400B of displaying intensity-reactive and intensity-nonreactive user interface objects in accordance with some embodiments. The method 2400B is performed (2452) at an electronic device (e.g., device 300,
While displaying a user interface, the device detects (2452) an input by a contact (e.g., a finger or stylus contact, such as user input 912, FIG. 9A12, or user input 915, FIG. 9B2) at a first location on the touch-sensitive surface that corresponds to a first activatable user interface object (e.g., messages icon 902, FIG. 9A12, or e-mail message 930, FIG. 9B2) on the display (e.g., display 950, Figures FIGS. 9A12 and 9B2).
In some embodiments, the displayed user interface includes (2454) a plurality of activatable user interface objects, wherein a first subset of the activatable user interface objects is intensity-reactive, and wherein a second subset of the activatable user interface objects is intensity-nonreactive.
In some embodiments, the first activatable user interface object is (2456) displayed in a list (e.g., as shown in FIG. 9B1). In some embodiments, the first activatable user interface object is (2458) displayed in an array of objects (e.g., a multi column, multi row array such as an application launch screen of a phone or tablet, as shown in FIG. 9A1).
In some embodiments, in response to detecting the input by the contact (2460), the device determines (2462) whether the first activatable user interface object is intensity-reactive.
In response to detecting the input by the contact (2460), in accordance with a determination that the first activatable user interface object is intensity-reactive (2464), the device changes a visual appearance of the first activatable user interface object (e.g., message icon 902, FIG. 9A12, or e-mail message 930, FIG. 9B2) in accordance with changes in a detected intensity of the contact on the touch-sensitive surface. In accordance with a determination that the first activatable user interface object is intensity-nonreactive, the device changes (2466) the visual appearance of the first activatable user interface object (e.g., weather icon 904, FIG. 9A3) by a predetermined amount. Changing the visual appearance of intensity-reactive activatable user interface objects in accordance with changes in a detected intensity of the contact on the touch-sensitive surface provides the user with feedback about the level of intensity that is being detected by the device and provides visual feedback to the user indicating that the activatable object is intensity-reactive, and that pressing harder will cause the device to perform one or more operations associated with intensity-reactive objects. Changing the visual appearance of intensity non-reactive activatable user interface objects by a predetermined amount provides visual feedback to the user indicating that the activable object is intensity-nonreactive, and that pressing harder will not cause the device to perform operations associated with intensity-reactive objects. 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).
In some embodiments, changing the visual appearance of the first activatable user interface object in accordance with the detected intensity of the contact includes (2468) changing a brightness of the first activatable user interface object in accordance with the detected intensity of the contact; and changing a size of the first activatable user interface object in accordance with the detected intensity of the contact (e.g., e-mail message 930, FIG. 9B2).
In some embodiments, changing the size of the first activatable user interface object in accordance with the detected intensity of the contact includes (2470) increasing the size of the first activatable user interface object (e.g., displaying movement of the first activatable user interface object upwards in a virtual z direction) in accordance with the detected intensity of the contact.
In some embodiments, changing the size of the first activatable user interface object in accordance with the detected intensity of the contact includes (2472) decreasing the size of the first activatable user interface object (e.g., displaying movement of the first activatable user interface object downwards in a virtual z direction) in accordance with the detected intensity of the contact (e.g., messages icon 902, FIG. 9A12, or e-mail message 930, FIG. 9B2).
In some embodiments, the first activatable user interface object occupies (2474) a first area prior to changing its size, and, in accordance with the determination that the first activatable user interface object is intensity-reactive, the device displays a platter that occupies the first area and that is displayed behind the first activatable user interface object, wherein the platter is visible as the size of the first activatable user interface object is decreased (e.g., as shown with respect to messages icon 902, FIG. 9A12).
In some embodiments, detecting the input by the contact at the first location on the touch-sensitive surface includes (2476) detecting the contact hovering over the touch-sensitive surface at the first location (e.g., user input 912, FIG. 9A11), wherein the first location corresponds to the first activatable user interface object, and, in response to detecting the input by the contact, in accordance with the determination that the first activatable user interface object is intensity-reactive, and while the contact is hovering over the touch-sensitive surface at the first location, the device performs a preview operation that includes changing the visual appearance of the first activatable user interface object (e.g., displays a beginning of a tap animation before touchdown, as shown in FIG. 9A11 with respect to messages icon 902).
In some embodiments, changing the visual appearance of the first activatable user interface object by a predetermined amount includes (2478) changing a brightness of the first activatable user interface object by a predetermined amount that is independent of the detected intensity of the contact; and maintaining a size of the first activatable user interface object (e.g., weather icon 904, FIGS. 9A3-9A6).
In some embodiments, in accordance with the determination that the first activatable user interface object is intensity-reactive (2480), the device blurs and shrinks the user interface excluding the first activatable user interface object, in accordance with the detected intensity (e.g., FIGS. 9A13-9A15 illustrate increasing degrees of blurring of user interface 900 excluding intensity-reactive messages icon 902), and in accordance with the determination that the first activatable user interface object is intensity-nonreactive, the device displays the user interface without blurring and shrinking the user interface (e.g., FIGS. 9A3-9A6 illustrate that user interface 900 is not blurred with respect to intensity-nonreactive weather icon 904).
In accordance with some embodiments,
As shown in
The processing unit is configured to: enable display, on the display unit 2502, of a user interface that includes a plurality of activatable objects (e.g., with the display enabling unit 2510), including a first activatable object with a first visual appearance, wherein the processing unit is configured to: for intensity-reactive activatable objects, perform operations corresponding to the intensity-reactive activatable objects based on characteristic intensities of inputs on the touch-sensitive surface unit that correspond to the intensity-reactive activatable objects (e.g., with the operation performing unit 2512), such that when a characteristic intensity of a contact that is providing input that corresponds to a respective intensity-reactive activatable object on the touch-sensitive surface unit meets intensity-based activation criteria, an operation corresponding to the respective intensity-reactive activatable object is performed as a result of the characteristic intensity of the contact meeting the intensity-based activation criteria; and for intensity-nonreactive activatable objects, perform operations corresponding to the intensity-nonreactive activatable objects without regard to whether inputs on the touch-sensitive surface unit that correspond to the intensity-nonreactive activatable objects meet the intensity-based activation criteria (e.g., with the operation performing unit 2512), such that when a characteristic intensity of a contact that is providing input that corresponds to a respective intensity-nonreactive activatable object on the touch-sensitive surface unit meets the intensity-based activation criteria, an operation corresponding to the respective intensity-nonreactive activatable object is not performed as a result of the characteristic intensity of the contact meeting the intensity-based activation criteria; while the user interface is displayed on the display unit, detect an input that corresponds to a request to select the first activatable object in the plurality of activatable objects (e.g., with the detecting unit 2514), wherein a characteristic intensity of the input fails to meet the intensity-based activation criteria during the input; and, in response to detecting the input: in accordance with a determination that the first activatable object is an intensity-reactive activatable object, enable display of the first activatable object (e.g., with the display enabling unit 2510) with a first transformation from its first visual appearance (e.g., with the transformation unit 2516); and, in accordance with a determination that the first activatable object is an intensity-nonreactive activatable object, enable display of the first activatable object without displaying the first transformation (e.g., with the display enabling unit 2510).
In accordance with some embodiments,
As shown in
The processing unit is configured to: while a user interface is displayed, detect an input by a contact at a first location on the touch-sensitive surface unit that corresponds to a first activatable user interface object on the display unit (e.g., with the detecting unit 2612); and, in response to detecting the input by the contact: in accordance with a determination that the first activatable user interface object is intensity-reactive, change a visual appearance of the first activatable user interface object in accordance with changes in a detected intensity of the contact on the touch-sensitive surface unit (e.g., with the transformation unit 2614); and, in accordance with a determination that the first activatable user interface object is intensity-nonreactive, change the visual appearance of the first activatable user interface object by a predetermined amount (e.g., with the transformation unit 2614).
FIGS. 27A1-27A5 are flow diagrams illustrating a method 2700A of displaying intensity-reactive and intensity-nonreactive user interface objects in accordance with some embodiments. The method 2700A is performed (2702) at an electronic device (e.g., device 300,
The device displays (2702) a user interface that includes a plurality of activatable user interface objects.
While displaying the user interface, the device detects (2704) a first portion of an input by a contact (e.g., user input 912, FIG. 9A12, or user input 915, FIG. 9B2) at a first location on the touch-sensitive surface that corresponds to a first user interface object on the display (e.g., messages icon 902, FIG. 9A12, or e-mail message 930, FIG. 9B2).
In response to detecting the first portion of the input, the device changes (2706) a visual appearance of the first user interface object by applying a first visual transformation to the first user interface object (e.g., darkening the first user interface object to provide an indication that a selection and/or activation operation corresponding to the first user interface object will be performed in response to detecting liftoff of the contact from the touch-sensitive surface if no other gesture performed with the contact is detected prior to detecting liftoff of the contact from the touch sensitive surface, as shown with respect to e-mail message 930, FIG. 9B2, or shrinking the first user interface object as shown with respect to messages icon 902, FIG. 9A12). The first visual transformation corresponds (2708) to a first user interface operation (e.g., a tap to select and/or activate the first user interface object). Changing the visual appearance of user interface objects using the first visual transformation corresponding to a first user interface operation provides the user with feedback regarding which user interface operation will be performed if the remainder of the input is consistent with the first user interface operation. 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).
After changing the visual appearance of the first user interface object by applying the first visual transformation to the first user interface object, the device detects (2710) a second portion of the input (e.g., a continuation of the input that includes a change in one or more parameters of a contact that performed the first input while the contact is continuously detected on the touch-sensitive surface).
In response to detecting the second portion of the input (2712), in some embodiments, in accordance with a determination that the second portion of the input is consistent with the first user interface operation (2714), the device dynamically reduces the first transformation prior to performing the first user interface operation (e.g., FIGS. 9A21-9A22 illustrate that the first transformation of messages icon 902 is dynamically reduced upon liftoff of the contact by user input 912).
In accordance with a determination that the second portion of the input is consistent with the first user interface operation, the device performs (2716) the first user interface operation (e.g., in response to liftoff of the contact). For example, in some embodiments, for a tap input, the device selects and/or activates the object, typically without dynamically reducing the first visual transformation as a first parameter gradually changes.
In accordance with a determination that the second portion of the input includes a gradual change in a first parameter (e.g., a dynamic change in the intensity of a contact in the input through a plurality of intensity values or a dynamic change in the location of a contact in the input through a plurality of positions across the touch-sensitive surface, as shown for example in FIGS. 9B3-9B4) that is indicative of performance of a second user interface operation (e.g., a press harder to peek, FIGS. 9B3-9B4, or a drag gesture to scroll), the device dynamically reduces (2718) the first visual transformation (e.g., as shown for e-mail message 930, FIG. 9B2) as the first parameter gradually changes (e.g., by gradually increasing or decreasing the shading of the user interface object as the intensity of the contact on the touch-sensitive surface increases or as the location of the contact on the touch-sensitive surface changes) without performing the first user interface operation. For example, FIGS. 9B3-9B4 illustrate that the shading of e-mail message 930 is gradually decreased as the intensity of the contact by user input 915 increases as shown in user input intensity graph 906. Dynamically reducing the first transformation without performing the first user interface operation if the second portion of the input includes a gradual change in the first parameter that is indicative of performance of a second user interface operation allows a user input to transition between possible operations to be performed in accordance with changes in the input and provides the user with feedback that a different user interface operation may performed in accordance with further changes in the input. Providing the ability to transition between possible operations to be performed and 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).
In some embodiments, after dynamically reducing the first visual transformation in accordance with a determination that the second portion of the input includes a gradual change in the first parameter that is indicative of performance of the second user interface operation, the device detects (2720) a third portion of the input; in response to detecting the third portion of the input, and in accordance with a determination that the third portion of the input is consistent with the first user interface operation, the device changes the visual appearance of the first user interface object by reapplying the first visual transformation (and, in some embodiments, dynamically reduces the second visual transformation) and performs the first user interface operation (e.g., in response to liftoff of the contact). For example, FIGS. 9A16-9A18 illustrate dynamically reducing the first visual transformation in accordance with a determination that the second portion of user input 912 includes a gradual change in lateral displacement that is indicative of scrolling, and FIGS. 9A18-9A20 illustrate that, in response to detecting a third portion of user input 912, and in accordance with a determination that the third portion of user input 912 is consistent with an activation operation, the first visual transformation is reapplied and the second visual transformation is dynamically reduced. Dynamically reapplying the first transformation and optionally dynamically reducing the second transformation in accordance with the third portion of the input being consistent with the activation operation allows a user input to transition between possible operations to be performed in accordance with changes in the input and provides the user with feedback regarding which operation may performed in accordance with changes in the input. Providing the ability to transition between possible operations to be performed and 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).
In some embodiments, the device changes (2722) the visual appearance of the first user interface object by applying a second visual transformation to the first user interface object, in conjunction with dynamically reducing the first visual transformation as the first parameter gradually changes.
In some embodiments, the gradual change in the first parameter includes (2724) an increase in intensity of the contact, and the second visual transformation includes changing a size of the first user interface object in accordance with the increase in intensity of the contact (e.g., messages icon 902, FIGS. 9A13-9A14, or e-mail message 930, FIG. 9B3-9B4).
In some embodiments, the gradual change in the first parameter includes (2726) an increase in intensity of the contact, and the second visual transformation includes blurring and shrinking a portion of the user interface, other than the first user interface object, in accordance with the increase in intensity of the contact (e.g., user interface 900, FIGS. 9A13-9A14, or user interface 900, FIG. 9B3-9B4).
In some embodiments, the gradual change in the first parameter includes (2728) lateral movement of the contact, and the second visual transformation includes changing a position of the first user interface object on the display (e.g., scrolling the first user interface object and other user interface objects on the display when the second portion of the input is a drag or swipe gesture, as shown in FIGS. 9A17-9A18 with respect to messages icon 902).
In some embodiments, the device changes (2730) the visual appearance of the first user interface object by applying a second visual transformation to the first user interface object after the first visual transformation has been dynamically reduced by a predefined amount.
In some embodiments, in accordance with a determination that the second portion of the input includes a gradual change in a second parameter (e.g., through a plurality of values) that is indicative of performance of a third user interface operation (e.g., pan to scroll content), the device changes (2732) the visual appearance of the first user interface object by applying a third visual transformation as the second parameter gradually changes (e.g., by gradually increasing or decreasing a size of the user interface object as the amount of movement of the contact on the touch-sensitive surface changes).
In some embodiments, the gradual change in the second parameter includes (2734) lateral movement of the contact, and the third visual transformation includes changing a position of the first user interface object on the display in accordance with the lateral movement of the contact (e.g., as shown in FIGS. 9A17-9A18 with respect to messages icon 902.
In some embodiments, in accordance with a determination that the second portion of the input includes a gradual change in a third parameter (e.g., through a plurality of values) that is indicative of performance of a fourth user interface operation (e.g., press longer to enter an icon reconfiguration mode), the device changes (2736) the visual appearance of the first user interface object by applying a fourth visual transformation as the third parameter gradually changes (e.g., by gradually darkening the user interface object the longer the contact is maintained without changing the pressure or scrolling, as shown in FIG. 9A24 with respect to messages icon 902).
In some embodiments, the gradual change in the third parameter includes (2738) an increase in a duration of maintaining the contact on the touch-sensitive surface (e.g., satisfying time threshold TH but not time threshold TLP as shown in user input intensity graph 906, FIG. 9A24) with no more than a threshold amount of lateral movement (e.g., Dt as shown in user input lateral displacement graph 908, FIG. 9A24) and with no more than a threshold amount of change in intensity (e.g., ITH as shown in user input intensity graph 906, FIG. 9A24), and the fourth visual transformation includes changing at least one of a shading and a color of the first user interface object in accordance with the increasing duration of the contact being maintained on the touch-sensitive surface (e.g., as shown in FIG. 9A24 with respect to messages icon 902).
In some embodiments, after changing the visual appearance of the first user interface object by applying the fourth visual transformation (2740), the device detects a change in a respective parameter other than the third parameter (e.g., either the first parameter or the second parameter), and, in accordance with a determination that the change in the respective parameter satisfies a respective threshold, dynamically reduces the fourth visual transformation as the respective parameter changes. For example, FIG. 9A25 illustrates detecting a change in contact intensity of user input 913, as shown in user input intensity graph 906, and, in accordance with a determination that the change in the contact intensity of user input 913 satisfies the first intensity threshold ITH, the fourth visual transformation (e.g., darkening of messages icon 902) is dynamically reduced as the contact intensity changes.
In some embodiments, the input is a first input (2742), the first user interface object is an intensity-reactive object, and, while displaying the user interface, the device detects a first portion of a second input by a contact at a second location (e.g., user input 911, FIG. 9A8) on the touch-sensitive surface that corresponds to a second user interface object (e.g., weather icon 904, FIG. 9A8) on the display (e.g., display 950, FIG. 9A8), wherein the second user interface object is an intensity-nonreactive object. In some embodiments, in response to detecting the first portion of the second input, the device changes a visual appearance of the second user interface object by applying a fifth visual transformation to the second user interface object (e.g., darkening weather icon 904, FIG. 9A8), wherein the fifth visual transformation corresponds to a fifth user interface operation (e.g., the fifth user interface operation is the same as the first operation and is a tap to select). In some embodiments, after changing the visual appearance of the second user interface object by applying the fifth visual transformation to the second user interface object, the device detects a second portion of the second input (e.g., user input 911 as shown in FIG. 9A9). In some embodiments, in response to detecting the second portion of the second input, in accordance with a determination that the second portion of the second input includes a change in a fourth parameter (e.g., lateral displacement of user input 911, FIG. 9A9) that is indicative of performance of a sixth user interface operation, the device instantaneously changes the visual appearance of the second user interface object by removing the fifth visual transformation without regard to a gradual change in the fourth parameter (e.g., the darkening of weather icon 904 is removed, FIG. 9A9).
FIGS. 27B1-27B3 are flow diagrams illustrating a method 2700B of displaying intensity-reactive and intensity-nonreactive user interface objects in accordance with some embodiments. The method 2700B is performed (2752) at an electronic device (e.g., device 300,
The device displays (2752) a user interface (e.g., user interface 900,
While displaying the user interface, the device detects (2754) a first portion of an input by a contact (e.g., a finger or stylus contact, such as user input 912, FIG. 9A12, or user input 915, FIG. 9B2) at a first location on the touch-sensitive surface that corresponds to a first user interface object (e.g., messages icon 902, FIG. 9A12, or e-mail message 930, FIG. 9B2) on the display.
In response to detecting the first portion of the input by the contact (2756), the device changes a visual appearance of the first user interface object to indicate that an operation corresponding to the first user interface object will be performed in response to detecting liftoff of the contact from the touch-sensitive surface. The change in the visual appearance includes (2758) applying a first transformation to the first user interface object (e.g., the first transformation includes changing a brightness of the first user interface object from a first brightness to a second brightness, as shown in FIG. 9B2 with respect to e-mail message 930). Changing the visual appearance of user interface objects using the first transformation provides the user with feedback indicating that an operation will be performed in response to liftoff of the contact. 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).
The device detects (2760) a second portion of the input by the contact. The second portion of the input immediately follows (2762) the first portion of the input.
In some embodiments, the second portion of the input includes (2764) lateral movement of the contact and corresponds to a drag (e.g., scroll) gesture.
In some embodiments, the second portion of the input includes (2766) a change in detected intensity of the contact and corresponds to a stationary press gesture that meets a first intensity criterion.
In some embodiments, the second portion of the input includes (2768) continuing to maintain the contact on the touch-sensitive surface for at least a first amount of time such that a total amount of time that the contact is maintained without meeting a threshold amount of lateral movement and a first intensity criterion is greater than a first time threshold (e.g., time threshold TH as shown in user input intensity graph 906, FIG. 9A24).
In response to detecting the second portion of the input by the contact (2770), in accordance with a determination that the second portion of the input includes a gradual change in a first input parameter and corresponds to a first gesture (e.g., a drag or scroll), the device changes (2772) the visual appearance of the first user interface object by dynamically reducing the first transformation and applying a second transformation corresponding to the first gesture as the first input parameter gradually changes. For example, in some embodiments, the first input parameter includes lateral movement of the contact and corresponds to a scroll gesture, and the second transformation includes gradually changing the brightness of the first user interface object from the second brightness back to the first brightness in accordance with the lateral movement of the contact, and scrolling at least a subset of the activatable user interface objects on the display in accordance with the lateral movement of the contact with respect to the first location on the touch-sensitive surface (e.g., as shown in FIGS. 9A16-9A18 with respect to messages icon 902 and user interface 900). Dynamically reducing the first transformation and applying the second transformation corresponding to the first gesture as the first input parameter gradually changes provides the user with feedback indicating that a different operation will be performed in accordance with a different gesture being detected, and allows the user input to transition between possible operations to be performed in accordance with changes in the input. 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).
In accordance with a determination that the second portion of the input includes a gradual change in a second input parameter and corresponds to a second gesture (e.g., a deep press), the device changes (2774) the visual appearance of the first user interface object by dynamically reducing the first transformation and applying a third transformation corresponding to the second gesture as the second input parameter gradually changes. For example, in some embodiments, the second input parameter includes a change (e.g., increase) in intensity of the contact and corresponds to a stationary press that meets a first intensity criterion, and the third transformation includes gradually changing the brightness of the first user interface object from the second brightness to a third brightness in accordance with the detected intensity of the contact during the second portion of the input, and changing a size of the first user interface object in accordance with the detected intensity of the contact during the second portion of the input (e.g., the brightness and size of e-mail message 930 is gradually increased in accordance with the increase in contact intensity of user input 915, FIGS. 9B2-9B4). Dynamically reducing the first transformation and applying the third transformation corresponding to the second gesture as the second input parameter gradually changes provides the user with feedback indicating that a different operation will be performed in accordance with a different gesture being detected, and allows the user input to transition between possible operations to be performed in accordance with changes in the input. 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).
In some embodiments, the first transformation includes (2776) changing a brightness (and/or color) of the first user interface object from a first brightness to a second brightness (e.g., the second brightness (for a tap selection state) is darker or dimmer than the first brightness); the second transformation includes changing the brightness of the first user interface object from the second brightness to a third brightness (e.g., the third brightness is brighter or lighter than the second brightness, and could be the same as the first brightness) as the first parameter gradually changes (e.g., lighter for swipe or deep press); and the third transformation includes changing the brightness of the first user interface object from the second brightness to a fourth brightness (e.g., distinct from the first, second, and third brightnesses, and darker or dimmer than all the others) as the second parameter gradually changes (e.g., darker for long press).
In some embodiments, the second transformation includes (2778) increasing a size of the first user interface object (e.g., larger for swipe or long press), and the third transformation includes changing the size of the first user interface object by decreasing the size of the first user interface object during a first portion of the third transformation and increasing the size of the first user interface object during a second portion of the third transformation (e.g., smaller, then larger for a deep press). For example, in some embodiments, the second portion of the third transformation is a continuation of the third transformation subsequent to and immediately following the first portion.
In some embodiments, in accordance with a determination that the second portion of the input includes a gradual change in a third input parameter and corresponds to a third gesture (e.g., a long press), the device changes (2780) the visual appearance of the first user interface object by dynamically reducing the first transformation and applying a fourth transformation corresponding to the third gesture as the third input parameter gradually changes. For example, in some embodiments, the third input parameter includes an increase in a time duration of maintaining the contact on the touch-sensitive surface with no more than a threshold amount of lateral movement and with no more than a threshold amount of change in detected intensity, and corresponds to a stationary press gesture that does not meet the first intensity criterion, and the fourth transformation includes decreased brightness of the first user interface object (e.g., decreasing the brightness of messages icon 902, FIG. 9A24).
In some embodiments, in accordance with a determination that the second portion of the input includes a gradual change in both the first input parameter and the second input parameter, the device changes (2782) the visual appearance of the first user interface object by dynamically reducing the first transformation and applying at least a portion of the second transformation and at least a portion of the third transformation. For example, in some embodiments, a change in size for a deep press and a change in color for a long press (e.g., for a home screen) are applied (e.g., messages icon 902, FIG. 9A24). As another example, in some embodiments, a change in location for a drag gesture and a change in size for a deep press (e.g., for a table view such as in a mail application) are applied (e.g., e-mail message 930, FIG. 9B7).
In accordance with some embodiments,
As shown in
The processing unit is configured to: enable display of a user interface that includes a plurality of activatable user interface objects (e.g., with the display enabling unit 2810); while the user interface is displayed, detect a first portion of an input by a contact at a first location on the touch-sensitive surface unit that corresponds to a first user interface object on the display unit (e.g., with the detecting unit 2812); in response to detecting the first portion of the input: change a visual appearance of the first user interface object by applying a first visual transformation to the first user interface object (e.g., with the transformation unit 2814), wherein the first visual transformation corresponds to a first user interface operation; after changing the visual appearance of the first user interface object by applying the first visual transformation to the first user interface object, detect a second portion of the input (e.g., with the detecting unit 2812); in response to detecting the second portion of the input: in accordance with a determination that the second portion of the input is consistent with the first user interface operation, perform the first user interface operation (e.g., with the operation performing unit 2816); and in accordance with a determination that the second portion of the input includes a gradual change in a first parameter that is indicative of performance of a second user interface operation, dynamically reduce the first visual transformation as the first parameter gradually changes without performing the first user interface operation (e.g., with the transformation unit 2814).
As shown in
The processing unit is configured to: enable display of a user interface that includes a plurality of activatable user interface objects (e.g., with the display enabling unit 2910); while the user interface is displayed, detect a first portion of an input by a contact at a first location on the touch-sensitive surface unit that corresponds to a first user interface object on the display unit (e.g., with the detecting unit 2912); in response to detecting the first portion of the input by the contact: change a visual appearance of the first user interface object to indicate that an operation corresponding to the first user interface object will be performed in response to detecting liftoff of the contact from the touch-sensitive surface unit, wherein the change in the visual appearance includes applying a first transformation to the first user interface object (e.g., with the transformation unit 2914); detect a second portion of the input by the contact, wherein the second portion of the input immediately follows the first portion of the input (e.g., with the detecting unit 2912); and, in response to detecting the second portion of the input by the contact: in accordance with a determination that the second portion of the input includes a gradual change in a first input parameter and corresponds to a first gesture, change the visual appearance of the first user interface object by dynamically reducing the first transformation and applying a second transformation corresponding to the first gesture as the first input parameter gradually changes (e.g., with the transformation unit 2914); and, in accordance with a determination that the second portion of the input includes a gradual change in a second input parameter and corresponds to a second gesture, change the visual appearance of the first user interface object by dynamically reducing the first transformation and applying a third transformation corresponding to the second gesture as the second input parameter gradually changes (e.g., with the transformation unit 2914).
The device displays (3002) a first user interface (e.g., user interface 903, FIG. 9C1) that includes a plurality of activatable user interface objects (e.g., including a plurality of virtual controls, such as remote device control affordances, for example icons 962-1 through 962-8).
While displaying the first user interface, the device detects (3004) an input by a contact at a first location (e.g., user input 954) on the touch-sensitive surface that corresponds to a first activatable user interface object on the display (e.g., a first remote device control affordance, such as lights icon 962-4, FIG. 9C2). The first activatable user interface object is (3006) associated with a control function with three or more available values. Also, a first value of the control function is (3008) selected as a current value for the control function (e.g., a temperature setting, a volume setting, a brightness setting, etc.).
In response to detecting the input by the contact (3010), in accordance with a determination that the input meets toggle criteria (3012), wherein the toggle criteria do not require that a characteristic intensity of the contact on the touch-sensitive surface meets a first intensity threshold in order for the toggle criteria to be met (e.g., the characteristic intensity of the contact remains below a light press intensity threshold ITL, such as for a contact in a tap gesture), the device toggles the control function that corresponds to the first activatable user interface object between a first state that is based on the current value for the control function and a second state (e.g., by turning the control function on with the current value for a setting or turning the control function off).
In some embodiments, the toggle criteria include (3014) a criterion that is met when the characteristic intensity of the contact remains below the first intensity threshold (e.g., IT=as shown in user input intensity graph 956, FIG. 9C2). In some embodiments, the toggle criteria include (3016) a criterion that is met when the input is a tap input.
In response to detecting the input by the contact (3010), in accordance with a determination that the input meets control adjustment criteria (3018), wherein the control adjustment criteria require that the characteristic intensity of the contact on the touch-sensitive surface meets the first intensity threshold in order for the control adjustment criteria to be met (e.g., the characteristic intensity of the contact is above a light press intensity threshold ITL as shown in user input intensity graph 906, FIGS. 9C4-9C5), the device displays a second user interface (e.g., user interface 951, FIG. 9C4 or user interface 952, FIG. 9C5) that includes a second activatable user interface object (e.g., activatable object 958, FIGS. 9C4-9C5) that has three or more state options that correspond to the three or more available values for the control function (e.g., state options 958-1 through 958-6, FIGS. 9C4-9C5). Displaying a second user interface that includes an activatable user interface object for controlling the control function in accordance with the input meeting control adjustment criteria provides the user with an efficient means of controlling remote devices, thereby enhancing 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).
In some embodiments, the second user interface includes (3020) an icon that represents the control function (e.g., icon 907, FIGS. 9C4-9C15) and the icon is animated in accordance with the current value for the control function. For example, for a temperature setting, the icon may include a thermometer icon and change color in accordance with the current temperature setting; for a brightness setting, the icon may include a light bulb icon and be animated to show the light bulb becoming brighter or dimmer; for a fan setting, the icon may include a fan icon and be animated to show the fan speed increasing or decreasing, etc.
While displaying the second user interface and continuing to detect the contact (3022), in some embodiments, while displaying the second user interface and prior to detecting movement of the contact across the touch sensitive surface (3024), the device ceases to detect the contact, and, in response to ceasing to detect the contact, continues to display the second user interface (e.g., ceasing to detect user input 954 and continuing to display second user interface 952, as shown in FIG. 9C17). In some embodiments, when the second user interface is displayed (to enable adjusting the setting of a control), if the contact lifts off without moving across the touch sensitive surface, display of the second user interface is maintained so that a user can make a second input (e.g., user input 955, FIG. 9C18) on the second user interface to adjust the setting of a control. Conversely, in some embodiments, if the contact by the first input moves across the touch-sensitive surface while the second user interface is displayed (e.g., user input 954 moves as shown in FIG. 9C14) and then lifts off (e.g., user input 954 lifts off, FIG. 9C15), then the setting of the control is adjusted based on the movement of the contact and the second user interface ceases to be displayed when the contact lifts off (e.g., the setting of the control is adjusted to the minimum value 958-0 and user input 954 ceases to be detected, FIG. 9C15, and second user interface 952 ceases to be displayed such that first user interface 903 is redisplayed, FIG. 9C16). Thus, adjusting the setting of the control can be performed with either (a) an input by a single continuous contact or (b) two inputs by two separate contacts with the touch sensitive surface (where the same finger may make the two separate contacts).
While displaying the second user interface and continuing to detect the contact (3022), the device detects (3026) movement of the contact across the touch-sensitive surface (e.g., movement of user input 954 is detected, FIGS. 9C6-9C9, or alternatively FIGS. 9C11-9C14). In some embodiments, while detecting the movement of the contact across the touch-sensitive surface, the device changes (3028) the current value for the control function based on the movement of the contact.
Next, while displaying the second user interface and continuing to detect the contact (3022), the device ceases (3030) to detect the contact (e.g., the device detects liftoff of the contact, such as user input 954, FIG. 9C10, or user input 954, FIG. 9C15) from the touch-sensitive surface).
In response to detecting the movement of the contact across the touch-sensitive surface, the device changes (3032) the current value for the control function based on the movement of the contact (e.g., by changing the current value to a second value if the movement is a first amount of movement in a first direction or changing the current value to a third value if the movement is the first amount of movement in a second direction, or changing the current value to a fourth value if the movement is a second amount of movement in the second direction). For example, the current value is changed to a second value 958-4 when the movement is a first amount of movement upwards, FIG. 9C6, and to a third value 958-2 when the movement is the first amount of movement downwards, FIG. 9C11. Or, the current value is changed to a fourth value 958-1 if the movement is a second amount of movement downwards, FIG. 9C12. Changing the current value for the control function based on the movement of the contact while displaying the second user interface provides the user with an efficient means of changing settings for controlling remote devices, thereby enhancing 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).
In some embodiments, the current value of the control function after ceasing to detect the contact is (3034) a last value for the control function prior to ceasing to detect the contact (e.g., the last value for the control function prior to ceasing to detect user input 954 was the minimum value 958-0 corresponding to an off state of the function, as shown in FIGS. 9C14-9C15, and the current value of the control function as shown in FIG. 9C16 is the minimum value such that the function is in an off state).
In some embodiments, in response to detecting the movement of the contact across the touch-sensitive surface and ceasing to detect the contact, the device sets (3036) the control function to an on state.
In some embodiments, in response to ceasing to detect the contact, the device ceases (3038) to display the second user interface and redisplays the first user interface (e.g., in response to ceasing to detect user input 954, second user interface 952 as shown in FIG. 9C15 ceases to be displayed, and first user interface 903 is redisplayed as shown in FIG. 9C16). In some embodiments, ceasing to display the second user interface includes (3040) displaying an animation of the second activatable user interface object (e.g., second activatable user interface object 958, FIG. 9C15) transforming into the first activatable user interface object (e.g., lights icon 962-4, FIG. 9C16).
In some embodiments, while displaying the second user interface, the device detects (3042) movement of the contact that corresponds to a swipe gesture (e.g., a left swipe, as indicated by user input 955, FIG. 9C19, or a right swipe), and, in response to detecting movement of the contact that corresponds to the swipe gesture, the device displays a third user interface (e.g., third user interface 953, FIG. 9C19) that includes a third activatable user interface object (e.g., as illustrated in FIG. 9C19, the third activatable user interface object is made up of activatable user interface objects 960-1 through 960-7) that corresponds to one or more additional controls for the function. In some embodiments, the second user interface includes (3044) a plurality of pagination indicia (e.g., dots, such as pagination dots 909, FIGS. 9C18-9C19) that indicate that one or more additional pages of controls for the function are available.
In some embodiments, changing the current value for the control function based on the movement of the contact includes (3046) changing the current value for the control function to a lowest available value of the control function (e.g., minimum value 958-0, FIG. 9C13, corresponding to an off state of the function) in accordance with a determination that the movement of the contact includes at least a first amount of movement in a first direction (e.g., a long, downward swipe turns off the function).
In some embodiments, changing the current value of the control function to the lowest available value includes (3048), in accordance with a determination that the movement of the contact includes an amount of movement in the first direction that is greater than the first amount (e.g., as indicated by user input 954, FIG. 9C14), displaying an animation of the second activatable user interface object transforming into a third user interface object (e.g., a stretched form of the second activatable user interface object, as shown in FIG. 9C14) that corresponds to the movement in the first direction without changing the current value for the control function from the lowest available value (e.g., the current value for the control function is still the minimum value 958-0, FIG. 9C14), and in response to ceasing to detect the contact, displaying an animation of the third user interface object transforming into the second activatable user interface object (e.g., displaying an animation of activatable user interface object 958 contracting, as indicated in FIG. 9C15).
For example, in some embodiments, the third user interface object is an elongated or stretched form of the second activatable user interface object, optionally showing selection of a value lower than the lowest available value, the animation of the second activatable user interface object transforming into the third user interface object includes the second activatable user interface object stretching in accordance with continued movement of the contact in the first direction, and the animation of the third user interface object transforming (back) into the second activatable user interface object includes the third user interface object snapping or springing back into the second activatable user interface object, typically showing selection of the lowest available value.
In some embodiments, changing the current value for the control based on the movement of the contact includes (3050) changing the current value for the control to a highest available value of the function (e.g., maximum value 958-6, FIG. 9C8) in accordance with a determination that the movement of the contact includes a second amount of movement in a second direction (e.g., a long, upward swipe increases the function to its maximum value).
In some embodiments, changing the current value for the control to the highest available value includes (3052), in accordance with a determination that the movement of the contact includes an amount of movement in the second direction that is greater than the second amount (e.g., as indicated by user input 954, FIG. 9C9), displaying an animation of the second activatable user interface object transforming into a fourth user interface object (e.g., a stretched form of the second activatable user interface object, as shown in FIG. 9C9) that corresponds to the movement in the second direction without changing the current value for the control function from the highest available value (e.g., the current value for the control function is still the maximum value 958-6, FIG. 9C9), and, in response to ceasing to detect the contact, displaying an animation of the fourth user interface object transforming into the second activatable user interface object (e.g., displaying an animation of activatable user interface object 958 contracting, as indicated in FIG. 9C10).
For example, in some embodiments the fourth user interface object is an elongated or stretched form of the second activatable user interface object, optionally showing selection of a value higher than the highest available value, the animation of the second activatable user interface object transforming into the fourth user interface object includes the second activatable user interface object stretching in accordance with continued movement of the contact in the second direction, and the animation of the fourth user interface object transforming (back) into the second activatable user interface object includes the fourth user interface object snapping or springing back into the second activatable user interface object, typically showing selection of the highest available value.
In some embodiments, the electronic device includes (3054) a tactile output generator, and, in response to changing the current value of the control function to a lowest available value of the control function (e.g., an off state of the function such as 0%), the device outputs a tactile output. In some embodiments, the tactile output is generated in response to a request to decrease the current value of the control function beyond the lowest available value (e.g., as indicated by tactile output 923, FIG. 9C14) and/or in response to snapping back to the lowest available value after receiving a request to increase the current value of the control function beyond the lowest available value (e.g., as indicated by tactile output 924, FIG. 9C15).
In some embodiments, the electronic device includes (3056) a tactile output generator, and, in response to changing the current value of the control function to a highest available value of the function (e.g., a maximum value such as 100%), the device outputs a tactile output. In some embodiments, the tactile output is generated in response to a request to increase the current value of the control function beyond the highest available value (e.g., as indicated by tactile output 921, FIG. 9C9) and/or in response to snapping back to the highest available value after receiving a request to increase the current value of the control function beyond the highest available value (e.g., as indicated by tactile output 922, FIG. 9C10).
In some embodiments, the electronic device includes (3058) a tactile output generator, and, in response to detecting the movement of the contact across the touch sensitive surface while displaying the second user interface, the device outputs one or more tactile outputs in conjunction with changing the current value for the control based on the movement of the contact.
In accordance with some embodiments,
As shown in
The processing unit is configured to: enable display of a first user interface that includes a plurality of activatable user interface objects (e.g., with the display enabling unit 3110); while the first user interface is displayed, detect an input by a contact at a first location on the touch-sensitive surface unit that corresponds to a first activatable user interface object on the display unit (e.g., with the detecting unit 3112), wherein: the first activatable user interface object is associated with a control function with three or more available values; and a first value of the control function is selected as a current value for the control function; in response to detecting the input by the contact: in accordance with a determination that the input meets toggle criteria, wherein the toggle criteria do not require that a characteristic intensity of the contact on the touch-sensitive surface unit meets a first intensity threshold in order for the toggle criteria to be met, toggle the control function that corresponds to the first activatable user interface object between a first state that is based on the current value for the control function and a second state (e.g., with the toggling unit 3118); and, in accordance with a determination that the input meets control adjustment criteria, wherein the control adjustment criteria require that the characteristic intensity of the contact on the touch-sensitive surface unit meets the first intensity threshold in order for the control adjustment criteria to be met, enable display of a second user interface that includes a second activatable user interface object that has three or more state options that correspond to the three or more available values for the control function (e.g., with the display enabling unit 3110); and while the second user interface is displayed and while continuing to detect the contact: detect movement of the contact across the touch-sensitive surface unit (e.g., with the detecting unit 3112); cease to detect the contact (e.g., with the ceasing unit 3114); and, in response to detecting the movement of the contact across the touch-sensitive surface unit, change the current value for the control function based on the movement of the contact (e.g., with the function changing unit 3116).
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best use the invention and various described embodiments with various modifications as are suited to the particular use contemplated.
This application is a continuation of U.S. application Ser. No. 16/262,800, filed Jan. 30, 2019, which is a continuation of U.S. application Ser. No. 15/272,327, filed Sep. 21, 2016, now U.S. Pat. No. 10,209,884, which is a continuation of U.S. application Ser. No. 15/231,745, filed Aug. 8, 2016, now U.S. Pat. No. 9,880,735, which claims priority to the following: (1) U.S. Provisional Application Ser. No. 62/349,096, filed Jun. 12, 2016; (2) U.S. Provisional Application Ser. No. 62/215,722, filed Sep. 8, 2015; (3) U.S. Provisional Application Ser. No. 62/213,609, filed Sep. 2, 2015; and (4) U.S. Provisional Application Ser. No. 62/203,387, filed Aug. 10, 2015, all of which are incorporated by reference herein in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4864520 | Setoguchi et al. | Sep 1989 | A |
| 5184120 | Schultz | Feb 1993 | A |
| 5374787 | Miller et al. | Dec 1994 | A |
| 5428730 | Baker et al. | Jun 1995 | A |
| 5463722 | Venolia | Oct 1995 | A |
| 5510813 | Makinwa et al. | Apr 1996 | A |
| 5555354 | Strasnick et al. | Sep 1996 | A |
| 5559301 | Bryan, Jr. et al. | Sep 1996 | A |
| 5589855 | Blumstein et al. | Dec 1996 | A |
| 5664210 | Fleming et al. | Sep 1997 | A |
| 5710896 | Seidl | Jan 1998 | A |
| 5717438 | Kim et al. | Feb 1998 | A |
| 5793360 | Fleck et al. | Aug 1998 | A |
| 5793377 | Moore | Aug 1998 | A |
| 5801692 | Muzio et al. | Sep 1998 | A |
| 5805144 | Scholder et al. | Sep 1998 | A |
| 5805167 | Van Cruyningen | Sep 1998 | A |
| 5809267 | Moran et al. | Sep 1998 | A |
| 5819293 | Comer et al. | Oct 1998 | A |
| 5825352 | Bisset et al. | Oct 1998 | A |
| 5844560 | Crutcher et al. | Dec 1998 | A |
| 5870683 | Wells et al. | Feb 1999 | A |
| 5872922 | Hogan et al. | Feb 1999 | A |
| 5946647 | Miller et al. | Aug 1999 | A |
| 5956032 | Argiolas | Sep 1999 | A |
| 5973670 | Barber et al. | Oct 1999 | A |
| 6002397 | Kolawa et al. | Dec 1999 | A |
| 6031989 | Cordell | Feb 2000 | A |
| 6088019 | Rosenberg | Jul 2000 | A |
| 6088027 | Konar et al. | Jul 2000 | A |
| 6111575 | Martinez et al. | Aug 2000 | A |
| 6121960 | Carroll et al. | Sep 2000 | A |
| 6208329 | Ballare | Mar 2001 | B1 |
| 6208340 | Amin et al. | Mar 2001 | B1 |
| 6219034 | Elbing et al. | Apr 2001 | B1 |
| 6223188 | Albers et al. | Apr 2001 | B1 |
| 6232891 | Rosenberg | May 2001 | B1 |
| 6243080 | Molne | Jun 2001 | B1 |
| 6252594 | Xia et al. | Jun 2001 | B1 |
| 6292233 | Erba et al. | Sep 2001 | B1 |
| 6300936 | Braun et al. | Oct 2001 | B1 |
| 6313836 | Russell, Jr. et al. | Nov 2001 | B1 |
| 6396523 | Segal et al. | May 2002 | B1 |
| 6429846 | Rosenberg et al. | Aug 2002 | B2 |
| 6448977 | Braun et al. | Sep 2002 | B1 |
| 6459442 | Edwards et al. | Oct 2002 | B1 |
| 6489978 | Gong et al. | Dec 2002 | B1 |
| 6512530 | Rzepkowski et al. | Jan 2003 | B1 |
| 6563487 | Martin et al. | May 2003 | B2 |
| 6567102 | Kung | May 2003 | B2 |
| 6583798 | Hoek et al. | Jun 2003 | B1 |
| 6590568 | Astala et al. | Jul 2003 | B1 |
| 6661438 | Shiraishi et al. | Dec 2003 | B1 |
| 6734882 | Becker | May 2004 | B1 |
| 6735307 | Volckers | May 2004 | B1 |
| 6750890 | Sugimoto | Jun 2004 | B1 |
| 6806893 | Kolawa et al. | Oct 2004 | B1 |
| 6822635 | Shahoian et al. | Nov 2004 | B2 |
| 6906697 | Rosenberg | Jun 2005 | B2 |
| 6919927 | Hyodo | Jul 2005 | B1 |
| 6943778 | Astala et al. | Sep 2005 | B1 |
| 7036088 | Tunney | Apr 2006 | B2 |
| 7138983 | Wakai et al. | Nov 2006 | B2 |
| 7312791 | Hoshino et al. | Dec 2007 | B2 |
| 7411575 | Hill et al. | Aug 2008 | B2 |
| 7434177 | Ording et al. | Oct 2008 | B1 |
| 7453439 | Kushler et al. | Nov 2008 | B1 |
| 7471284 | Bathiche et al. | Dec 2008 | B2 |
| 7479949 | Jobs et al. | Jan 2009 | B2 |
| 7500127 | Fleck et al. | Mar 2009 | B2 |
| 7516404 | Colby et al. | Apr 2009 | B1 |
| 7533352 | Chew et al. | May 2009 | B2 |
| 7552397 | Holecek et al. | Jun 2009 | B2 |
| 7577530 | Vignalou-Marche | Aug 2009 | B2 |
| 7614008 | Ording | Nov 2009 | B2 |
| 7619616 | Rimas Ribikauskas et al. | Nov 2009 | B2 |
| 7629966 | Anson | Dec 2009 | B2 |
| 7656413 | Khan et al. | Feb 2010 | B2 |
| 7683889 | Rimas Ribikauskas et al. | Mar 2010 | B2 |
| 7702733 | Fleck et al. | Apr 2010 | B2 |
| 7743348 | Robbins et al. | Jun 2010 | B2 |
| 7760187 | Kennedy | Jul 2010 | B2 |
| 7787026 | Flory et al. | Aug 2010 | B1 |
| 7797642 | Karam et al. | Sep 2010 | B1 |
| 7801950 | Eisenstadt et al. | Sep 2010 | B2 |
| 7812826 | Ording et al. | Oct 2010 | B2 |
| 7890862 | Kompe et al. | Feb 2011 | B2 |
| 7903090 | Soss et al. | Mar 2011 | B2 |
| 7952566 | Poupyrev et al. | May 2011 | B2 |
| 7956847 | Christie | Jun 2011 | B2 |
| 7973778 | Chen | Jul 2011 | B2 |
| 8000694 | Labidi et al. | Aug 2011 | B2 |
| 8040142 | Bokma et al. | Oct 2011 | B1 |
| 8059104 | Shahoian et al. | Nov 2011 | B2 |
| 8059105 | Rosenberg et al. | Nov 2011 | B2 |
| 8106856 | Matas et al. | Jan 2012 | B2 |
| 8125440 | Guyot-Sionnest et al. | Feb 2012 | B2 |
| 8125492 | Wainwright et al. | Feb 2012 | B1 |
| RE43448 | Kimoto et al. | Jun 2012 | E |
| 8209628 | Davidson | Jun 2012 | B1 |
| 8271900 | Walizaka et al. | Sep 2012 | B2 |
| 8300005 | Tateuchi et al. | Oct 2012 | B2 |
| 8311514 | Bandyopadhyay et al. | Nov 2012 | B2 |
| 8325398 | Satomi et al. | Dec 2012 | B2 |
| 8363020 | Li et al. | Jan 2013 | B2 |
| 8390583 | Forutanpour et al. | Mar 2013 | B2 |
| 8423089 | Song et al. | Apr 2013 | B2 |
| 8446376 | Levy et al. | May 2013 | B2 |
| 8446382 | Goto et al. | May 2013 | B2 |
| 8453057 | Stallings et al. | May 2013 | B2 |
| 8456431 | Victor | Jun 2013 | B2 |
| 8466889 | Tong et al. | Jun 2013 | B2 |
| 8482535 | Pryor | Jul 2013 | B2 |
| 8499243 | Yuki | Jul 2013 | B2 |
| 8504946 | Williamson et al. | Aug 2013 | B2 |
| 8508494 | Moore | Aug 2013 | B2 |
| 8542205 | Keller | Sep 2013 | B1 |
| 8553092 | Tezuka et al. | Oct 2013 | B2 |
| 8570296 | Birnbaum et al. | Oct 2013 | B2 |
| 8581870 | Bokma et al. | Nov 2013 | B2 |
| 8587542 | Moore | Nov 2013 | B2 |
| 8593415 | Han et al. | Nov 2013 | B2 |
| 8593420 | Buuck | Nov 2013 | B1 |
| 8625882 | Backlund et al. | Jan 2014 | B2 |
| 8638311 | Kang et al. | Jan 2014 | B2 |
| 8665227 | Gunawan | Mar 2014 | B2 |
| 8669945 | Coddington | Mar 2014 | B2 |
| 8698765 | Keller | Apr 2014 | B1 |
| 8706172 | Priyantha et al. | Apr 2014 | B2 |
| 8713471 | Rowley et al. | Apr 2014 | B1 |
| 8717305 | Williamson et al. | May 2014 | B2 |
| 8726198 | Rydenhag et al. | May 2014 | B2 |
| 8743069 | Morton et al. | Jun 2014 | B2 |
| 8760425 | Crisan | Jun 2014 | B2 |
| 8769431 | Prasad | Jul 2014 | B1 |
| 8773389 | Freed | Jul 2014 | B1 |
| 8788964 | Shin et al. | Jul 2014 | B2 |
| 8793577 | Schellingerhout et al. | Jul 2014 | B2 |
| 8799816 | Wells et al. | Aug 2014 | B2 |
| 8816989 | Nicholson et al. | Aug 2014 | B2 |
| 8854316 | Shenfield | Oct 2014 | B2 |
| 8872729 | Lyons et al. | Oct 2014 | B2 |
| 8872773 | Mak et al. | Oct 2014 | B2 |
| 8875044 | Ozawa et al. | Oct 2014 | B2 |
| 8881062 | Kim et al. | Nov 2014 | B2 |
| 8914732 | Jun et al. | Dec 2014 | B2 |
| 8932412 | Ferragut, II et al. | Jan 2015 | B2 |
| 8952987 | Momeyer et al. | Feb 2015 | B2 |
| 8954889 | Fujibayashi | Feb 2015 | B2 |
| 8959430 | Spivak et al. | Feb 2015 | B1 |
| 8976128 | Moore | Mar 2015 | B2 |
| 9026932 | Dixon | May 2015 | B1 |
| 9030419 | Freed | May 2015 | B1 |
| 9030436 | Ikeda | May 2015 | B2 |
| 9032321 | Cohen et al. | May 2015 | B1 |
| 9043732 | Nurmi et al. | May 2015 | B2 |
| 9046999 | Teller et al. | Jun 2015 | B1 |
| 9052820 | Jarrett et al. | Jun 2015 | B2 |
| 9052925 | Chaudhri | Jun 2015 | B2 |
| 9063563 | Gray et al. | Jun 2015 | B1 |
| 9063731 | Heo et al. | Jun 2015 | B2 |
| 9069460 | Moore | Jun 2015 | B2 |
| 9078208 | Dutta et al. | Jul 2015 | B1 |
| 9086755 | Cho et al. | Jul 2015 | B2 |
| 9086875 | Harrat et al. | Jul 2015 | B2 |
| 9092058 | Kasahara et al. | Jul 2015 | B2 |
| 9098188 | Kim | Aug 2015 | B2 |
| 9104260 | Marsden et al. | Aug 2015 | B2 |
| 9111076 | Park et al. | Aug 2015 | B2 |
| 9116569 | Stacy et al. | Aug 2015 | B2 |
| 9116571 | Zeliff et al. | Aug 2015 | B2 |
| 9122364 | Kuwabara et al. | Sep 2015 | B2 |
| 9128605 | Nan et al. | Sep 2015 | B2 |
| 9141262 | Nan et al. | Sep 2015 | B2 |
| 9146914 | Dhaundiyal | Sep 2015 | B1 |
| 9164779 | Brakensiek et al. | Oct 2015 | B2 |
| 9170607 | Bose et al. | Oct 2015 | B2 |
| 9170649 | Ronkainen | Oct 2015 | B2 |
| 9178971 | Nemoto | Nov 2015 | B2 |
| 9218105 | Mansson et al. | Dec 2015 | B2 |
| 9244562 | Rosenberg et al. | Jan 2016 | B1 |
| 9244576 | Vadagave et al. | Jan 2016 | B1 |
| 9244601 | Kim et al. | Jan 2016 | B2 |
| 9244606 | Kocienda et al. | Jan 2016 | B2 |
| 9246487 | Casparian et al. | Jan 2016 | B2 |
| 9262002 | Momeyer et al. | Feb 2016 | B2 |
| 9280286 | Commarford et al. | Mar 2016 | B2 |
| 9304668 | Rezende et al. | Apr 2016 | B2 |
| 9307112 | Molgaard et al. | Apr 2016 | B2 |
| 9349552 | Huska et al. | May 2016 | B2 |
| 9361018 | Defazio et al. | Jun 2016 | B2 |
| 9383887 | Khafizov et al. | Jul 2016 | B1 |
| 9389718 | Letourneur | Jul 2016 | B1 |
| 9389722 | Matsuki et al. | Jul 2016 | B2 |
| 9395800 | Liu et al. | Jul 2016 | B2 |
| 9400581 | Bokma et al. | Jul 2016 | B2 |
| 9405367 | Jung et al. | Aug 2016 | B2 |
| 9405428 | Roh et al. | Aug 2016 | B2 |
| 9417754 | Smith | Aug 2016 | B2 |
| 9423938 | Morris | Aug 2016 | B1 |
| 9436344 | Kuwabara et al. | Sep 2016 | B2 |
| 9448694 | Sharma et al. | Sep 2016 | B2 |
| 9451230 | Henderson et al. | Sep 2016 | B1 |
| 9471145 | Langlois et al. | Oct 2016 | B2 |
| 9477393 | Zambetti et al. | Oct 2016 | B2 |
| 9542013 | Dearman et al. | Jan 2017 | B2 |
| 9547436 | Ohki et al. | Jan 2017 | B2 |
| 9569093 | Lipman et al. | Feb 2017 | B2 |
| 9582178 | Grant et al. | Feb 2017 | B2 |
| 9600114 | Milam et al. | Mar 2017 | B2 |
| 9600116 | Tao et al. | Mar 2017 | B2 |
| 9612741 | Brown et al. | Apr 2017 | B2 |
| 9619076 | Bernstein et al. | Apr 2017 | B2 |
| 9619113 | Mark | Apr 2017 | B2 |
| 9625987 | LaPenna et al. | Apr 2017 | B1 |
| 9645722 | Stasior et al. | May 2017 | B1 |
| 9665762 | Thompson et al. | May 2017 | B2 |
| 9671943 | Van der Velden | Jun 2017 | B2 |
| 9678571 | Robert et al. | Jun 2017 | B1 |
| 9733716 | Shaffer | Aug 2017 | B2 |
| 9740381 | Chaudhri et al. | Aug 2017 | B1 |
| 9753527 | Connell et al. | Sep 2017 | B2 |
| 9760241 | Lewbel | Sep 2017 | B1 |
| 9785305 | Alonso Ruiz et al. | Oct 2017 | B2 |
| 9798443 | Gray | Oct 2017 | B1 |
| 9804665 | DeBates et al. | Oct 2017 | B2 |
| 9829980 | Lisseman et al. | Nov 2017 | B2 |
| 9891747 | Jang et al. | Feb 2018 | B2 |
| 10055066 | Lynn et al. | Aug 2018 | B2 |
| 10057490 | Shin et al. | Aug 2018 | B2 |
| 10095396 | Kudershian et al. | Oct 2018 | B2 |
| 10133388 | Sudou | Nov 2018 | B2 |
| 10133397 | Smith | Nov 2018 | B1 |
| 10180722 | Lu | Jan 2019 | B2 |
| 10222980 | Alonso Ruiz et al. | Mar 2019 | B2 |
| 10235023 | Gustafsson et al. | Mar 2019 | B2 |
| 10275087 | Smith | Apr 2019 | B1 |
| 10331769 | Hill et al. | Jun 2019 | B1 |
| 10386960 | Smith | Aug 2019 | B1 |
| 10469767 | Shikata | Nov 2019 | B2 |
| 10496151 | Kim et al. | Dec 2019 | B2 |
| 10547895 | Morris | Jan 2020 | B1 |
| 10739896 | Kim et al. | Aug 2020 | B2 |
| 10771274 | Reimann et al. | Sep 2020 | B2 |
| 10782871 | Bernstein et al. | Sep 2020 | B2 |
| 20010024195 | Hayakawa et al. | Sep 2001 | A1 |
| 20010045965 | Orbanes et al. | Nov 2001 | A1 |
| 20020006822 | Krintzman | Jan 2002 | A1 |
| 20020008691 | Hanajima et al. | Jan 2002 | A1 |
| 20020015064 | Robotham et al. | Feb 2002 | A1 |
| 20020042925 | Ebisu et al. | Apr 2002 | A1 |
| 20020054011 | Bruneau et al. | May 2002 | A1 |
| 20020057256 | Flack | May 2002 | A1 |
| 20020109668 | Rosenberg et al. | Aug 2002 | A1 |
| 20020109678 | Marmolin et al. | Aug 2002 | A1 |
| 20020128036 | Yach et al. | Sep 2002 | A1 |
| 20020140680 | Lu | Oct 2002 | A1 |
| 20020140740 | Chen | Oct 2002 | A1 |
| 20020163498 | Chang et al. | Nov 2002 | A1 |
| 20020180763 | Kung | Dec 2002 | A1 |
| 20020186257 | Cadiz et al. | Dec 2002 | A1 |
| 20030001869 | Nissen | Jan 2003 | A1 |
| 20030013492 | Bokhari et al. | Jan 2003 | A1 |
| 20030058241 | Hsu | Mar 2003 | A1 |
| 20030068053 | Chu | Apr 2003 | A1 |
| 20030086496 | Zhang et al. | May 2003 | A1 |
| 20030112269 | Lentz et al. | Jun 2003 | A1 |
| 20030117440 | Hellyar et al. | Jun 2003 | A1 |
| 20030122779 | Martin et al. | Jul 2003 | A1 |
| 20030128242 | Gordon | Jul 2003 | A1 |
| 20030151589 | Bensen et al. | Aug 2003 | A1 |
| 20030184574 | Phillips et al. | Oct 2003 | A1 |
| 20030189552 | Chuang et al. | Oct 2003 | A1 |
| 20030189647 | Kang | Oct 2003 | A1 |
| 20030201914 | Fujiwara et al. | Oct 2003 | A1 |
| 20030206169 | Springer et al. | Nov 2003 | A1 |
| 20030222915 | Marion et al. | Dec 2003 | A1 |
| 20040015662 | Cummings | Jan 2004 | A1 |
| 20040021643 | Hoshino et al. | Feb 2004 | A1 |
| 20040056849 | Lohbihler et al. | Mar 2004 | A1 |
| 20040108995 | Hoshino et al. | Jun 2004 | A1 |
| 20040138849 | Schmidt et al. | Jul 2004 | A1 |
| 20040141010 | Fitzmaurice et al. | Jul 2004 | A1 |
| 20040150631 | Fleck et al. | Aug 2004 | A1 |
| 20040150644 | Kincaid et al. | Aug 2004 | A1 |
| 20040155752 | Radke | Aug 2004 | A1 |
| 20040155869 | Robinson et al. | Aug 2004 | A1 |
| 20040168131 | Blumberg | Aug 2004 | A1 |
| 20040174399 | Wu et al. | Sep 2004 | A1 |
| 20040219969 | Casey et al. | Nov 2004 | A1 |
| 20040267877 | Shiparo et al. | Dec 2004 | A1 |
| 20050012723 | Pallakoff | Jan 2005 | A1 |
| 20050039141 | Burke et al. | Feb 2005 | A1 |
| 20050064911 | Chen et al. | Mar 2005 | A1 |
| 20050066207 | Fleck et al. | Mar 2005 | A1 |
| 20050076256 | Fleck et al. | Apr 2005 | A1 |
| 20050078093 | Peterson, Jr. et al. | Apr 2005 | A1 |
| 20050091604 | Davis | Apr 2005 | A1 |
| 20050110769 | DaCosta et al. | May 2005 | A1 |
| 20050114785 | Finnigan et al. | May 2005 | A1 |
| 20050125742 | Grotjohn et al. | Jun 2005 | A1 |
| 20050134578 | Chambers et al. | Jun 2005 | A1 |
| 20050156892 | Grant | Jul 2005 | A1 |
| 20050183017 | Cain | Aug 2005 | A1 |
| 20050190280 | Haas et al. | Sep 2005 | A1 |
| 20050204295 | Voorhees et al. | Sep 2005 | A1 |
| 20050223338 | Partanen | Oct 2005 | A1 |
| 20050229112 | Clay et al. | Oct 2005 | A1 |
| 20050283726 | Lunati | Dec 2005 | A1 |
| 20050289476 | Tokkonen | Dec 2005 | A1 |
| 20060001650 | Robbins et al. | Jan 2006 | A1 |
| 20060001657 | Monney et al. | Jan 2006 | A1 |
| 20060012577 | Kyrola | Jan 2006 | A1 |
| 20060022955 | Kennedy | Feb 2006 | A1 |
| 20060026536 | Hotelling et al. | Feb 2006 | A1 |
| 20060031776 | Glein et al. | Feb 2006 | A1 |
| 20060036945 | Radtke et al. | Feb 2006 | A1 |
| 20060036971 | Mendel et al. | Feb 2006 | A1 |
| 20060059436 | Nurmi | Mar 2006 | A1 |
| 20060067677 | Tokiwa et al. | Mar 2006 | A1 |
| 20060101347 | Runov et al. | May 2006 | A1 |
| 20060101581 | Blanchard et al. | May 2006 | A1 |
| 20060109252 | Kolmykov-Zotov et al. | May 2006 | A1 |
| 20060109256 | Grant et al. | May 2006 | A1 |
| 20060119586 | Grant et al. | Jun 2006 | A1 |
| 20060132455 | Rimas-Ribikauskas et al. | Jun 2006 | A1 |
| 20060132456 | Anson | Jun 2006 | A1 |
| 20060132457 | Rimas-Ribikauskas et al. | Jun 2006 | A1 |
| 20060136834 | Cao et al. | Jun 2006 | A1 |
| 20060136845 | Rimas-Ribikauskas et al. | Jun 2006 | A1 |
| 20060161861 | Holecek et al. | Jul 2006 | A1 |
| 20060161870 | Hotelling et al. | Jul 2006 | A1 |
| 20060190834 | Marcjan | Aug 2006 | A1 |
| 20060195438 | Galuten | Aug 2006 | A1 |
| 20060197753 | Hotelling | Sep 2006 | A1 |
| 20060210958 | Rimas-Ribikauskas et al. | Sep 2006 | A1 |
| 20060212812 | Simmons et al. | Sep 2006 | A1 |
| 20060213754 | Jarrett et al. | Sep 2006 | A1 |
| 20060224989 | Pettiross et al. | Oct 2006 | A1 |
| 20060233248 | Rynderman et al. | Oct 2006 | A1 |
| 20060236263 | Bathiche et al. | Oct 2006 | A1 |
| 20060274042 | Krah et al. | Dec 2006 | A1 |
| 20060274086 | Forstall et al. | Dec 2006 | A1 |
| 20060277469 | Chaudhri et al. | Dec 2006 | A1 |
| 20060282778 | Barsness et al. | Dec 2006 | A1 |
| 20060284858 | Rekimoto | Dec 2006 | A1 |
| 20060290681 | Ho et al. | Dec 2006 | A1 |
| 20070003134 | Song et al. | Jan 2007 | A1 |
| 20070024595 | Baker et al. | Feb 2007 | A1 |
| 20070024646 | Saarinen et al. | Feb 2007 | A1 |
| 20070036456 | Hooper | Feb 2007 | A1 |
| 20070080953 | Lii | Apr 2007 | A1 |
| 20070113681 | Nishimura et al. | May 2007 | A1 |
| 20070120834 | Boillot | May 2007 | A1 |
| 20070120835 | Sato | May 2007 | A1 |
| 20070124699 | Michaels | May 2007 | A1 |
| 20070152959 | Peters | Jul 2007 | A1 |
| 20070157089 | Van Os et al. | Jul 2007 | A1 |
| 20070157173 | Klein et al. | Jul 2007 | A1 |
| 20070168369 | Bruns | Jul 2007 | A1 |
| 20070168890 | Zhao et al. | Jul 2007 | A1 |
| 20070176904 | Russo | Aug 2007 | A1 |
| 20070182999 | Anthony et al. | Aug 2007 | A1 |
| 20070186178 | Schiller | Aug 2007 | A1 |
| 20070200713 | Weber et al. | Aug 2007 | A1 |
| 20070222768 | Geurts et al. | Sep 2007 | A1 |
| 20070229455 | Martin et al. | Oct 2007 | A1 |
| 20070229464 | Hotelling et al. | Oct 2007 | A1 |
| 20070236450 | Colgate et al. | Oct 2007 | A1 |
| 20070236477 | Ryu et al. | Oct 2007 | A1 |
| 20070245241 | Bertram et al. | Oct 2007 | A1 |
| 20070257821 | Son et al. | Nov 2007 | A1 |
| 20070270182 | Gulliksson et al. | Nov 2007 | A1 |
| 20070271513 | Andren et al. | Nov 2007 | A1 |
| 20070288862 | Ording | Dec 2007 | A1 |
| 20070294295 | Finkelstein et al. | Dec 2007 | A1 |
| 20070299923 | Skelly et al. | Dec 2007 | A1 |
| 20080001924 | dos los Reyes et al. | Jan 2008 | A1 |
| 20080010610 | Lim et al. | Jan 2008 | A1 |
| 20080024459 | Poupyrev et al. | Jan 2008 | A1 |
| 20080034306 | Ording | Feb 2008 | A1 |
| 20080034331 | Josephsoon et al. | Feb 2008 | A1 |
| 20080036743 | Westerman et al. | Feb 2008 | A1 |
| 20080051989 | Welsh | Feb 2008 | A1 |
| 20080052945 | Matas et al. | Mar 2008 | A1 |
| 20080066010 | Brodersen et al. | Mar 2008 | A1 |
| 20080094367 | Van De Ven et al. | Apr 2008 | A1 |
| 20080094368 | Ording et al. | Apr 2008 | A1 |
| 20080094398 | Ng et al. | Apr 2008 | A1 |
| 20080106523 | Conrad | May 2008 | A1 |
| 20080109753 | Karstens | May 2008 | A1 |
| 20080136790 | Hio | Jun 2008 | A1 |
| 20080155415 | Yoon et al. | Jun 2008 | A1 |
| 20080163119 | Kim et al. | Jul 2008 | A1 |
| 20080165141 | Christie | Jul 2008 | A1 |
| 20080165160 | Kocienda et al. | Jul 2008 | A1 |
| 20080168379 | Forstall et al. | Jul 2008 | A1 |
| 20080168395 | Ording et al. | Jul 2008 | A1 |
| 20080168403 | Westerman et al. | Jul 2008 | A1 |
| 20080168404 | Ording | Jul 2008 | A1 |
| 20080189605 | Kay et al. | Aug 2008 | A1 |
| 20080202824 | Philipp et al. | Aug 2008 | A1 |
| 20080204427 | Heesemans et al. | Aug 2008 | A1 |
| 20080219493 | Tadmor | Sep 2008 | A1 |
| 20080222569 | Champion et al. | Sep 2008 | A1 |
| 20080225007 | Nakadaira et al. | Sep 2008 | A1 |
| 20080244448 | Goering et al. | Oct 2008 | A1 |
| 20080259046 | Carsanaro | Oct 2008 | A1 |
| 20080263452 | Tomkins | Oct 2008 | A1 |
| 20080284866 | Mizutani | Nov 2008 | A1 |
| 20080294984 | Ramsay et al. | Nov 2008 | A1 |
| 20080297475 | Woolf et al. | Dec 2008 | A1 |
| 20080303795 | Lowles et al. | Dec 2008 | A1 |
| 20080303799 | Schwesig et al. | Dec 2008 | A1 |
| 20080307335 | Chaudhri et al. | Dec 2008 | A1 |
| 20080307359 | Louch et al. | Dec 2008 | A1 |
| 20080307361 | Louch et al. | Dec 2008 | A1 |
| 20080317378 | Steinberg et al. | Dec 2008 | A1 |
| 20080320419 | Matas et al. | Dec 2008 | A1 |
| 20090007017 | Anzures et al. | Jan 2009 | A1 |
| 20090016645 | Sako et al. | Jan 2009 | A1 |
| 20090028359 | Terada et al. | Jan 2009 | A1 |
| 20090046110 | Sadler et al. | Feb 2009 | A1 |
| 20090058828 | Jiang et al. | Mar 2009 | A1 |
| 20090061837 | Chaudhri et al. | Mar 2009 | A1 |
| 20090064031 | Bull et al. | Mar 2009 | A1 |
| 20090066668 | Kim et al. | Mar 2009 | A1 |
| 20090073118 | Yamaji et al. | Mar 2009 | A1 |
| 20090075738 | Pearce | Mar 2009 | A1 |
| 20090083665 | Anttila et al. | Mar 2009 | A1 |
| 20090085878 | Heubel et al. | Apr 2009 | A1 |
| 20090085881 | Keam | Apr 2009 | A1 |
| 20090085886 | Huang et al. | Apr 2009 | A1 |
| 20090089293 | Garritano et al. | Apr 2009 | A1 |
| 20090100343 | Lee et al. | Apr 2009 | A1 |
| 20090102804 | Wong et al. | Apr 2009 | A1 |
| 20090102805 | Meijer et al. | Apr 2009 | A1 |
| 20090140985 | Liu | Jun 2009 | A1 |
| 20090150775 | Miyazaki et al. | Jun 2009 | A1 |
| 20090158198 | Hayter et al. | Jun 2009 | A1 |
| 20090160793 | Rekimoto | Jun 2009 | A1 |
| 20090160814 | Li et al. | Jun 2009 | A1 |
| 20090164905 | Ko | Jun 2009 | A1 |
| 20090167507 | Maenpaa | Jul 2009 | A1 |
| 20090167508 | Fadell et al. | Jul 2009 | A1 |
| 20090167509 | Fadell et al. | Jul 2009 | A1 |
| 20090167704 | Terlizzi et al. | Jul 2009 | A1 |
| 20090169061 | Anderson et al. | Jul 2009 | A1 |
| 20090178008 | Herz et al. | Jul 2009 | A1 |
| 20090187824 | Hinckley et al. | Jul 2009 | A1 |
| 20090189866 | Haffenden et al. | Jul 2009 | A1 |
| 20090195959 | Ladouceur et al. | Aug 2009 | A1 |
| 20090198767 | Jakobson et al. | Aug 2009 | A1 |
| 20090201260 | Lee et al. | Aug 2009 | A1 |
| 20090219294 | Young et al. | Sep 2009 | A1 |
| 20090225037 | Williamson et al. | Sep 2009 | A1 |
| 20090228842 | Westerman et al. | Sep 2009 | A1 |
| 20090231453 | Huang | Sep 2009 | A1 |
| 20090237374 | Li et al. | Sep 2009 | A1 |
| 20090244357 | Huang | Oct 2009 | A1 |
| 20090247112 | Lundy et al. | Oct 2009 | A1 |
| 20090247230 | Lundy et al. | Oct 2009 | A1 |
| 20090251410 | Mori et al. | Oct 2009 | A1 |
| 20090251421 | Bloebaum | Oct 2009 | A1 |
| 20090256947 | Ciurea et al. | Oct 2009 | A1 |
| 20090259975 | Asai et al. | Oct 2009 | A1 |
| 20090267906 | Schroderus | Oct 2009 | A1 |
| 20090276730 | Aybes et al. | Nov 2009 | A1 |
| 20090280860 | Dahlke | Nov 2009 | A1 |
| 20090282360 | Park et al. | Nov 2009 | A1 |
| 20090284478 | De la Torre Baltierra et al. | Nov 2009 | A1 |
| 20090288032 | Chang et al. | Nov 2009 | A1 |
| 20090289779 | Braun et al. | Nov 2009 | A1 |
| 20090293009 | Meserth et al. | Nov 2009 | A1 |
| 20090295713 | Piot et al. | Dec 2009 | A1 |
| 20090295739 | Nagara | Dec 2009 | A1 |
| 20090295943 | Kim et al. | Dec 2009 | A1 |
| 20090298546 | Kim et al. | Dec 2009 | A1 |
| 20090303187 | Pallakoff | Dec 2009 | A1 |
| 20090307583 | Tonisson | Dec 2009 | A1 |
| 20090307633 | Haughay, Jr. et al. | Dec 2009 | A1 |
| 20090322893 | Stallings et al. | Dec 2009 | A1 |
| 20090325566 | Bell et al. | Dec 2009 | A1 |
| 20100005390 | Bong | Jan 2010 | A1 |
| 20100007926 | Imaizumi et al. | Jan 2010 | A1 |
| 20100011304 | Van Os | Jan 2010 | A1 |
| 20100013613 | Weston | Jan 2010 | A1 |
| 20100013777 | Baudisch et al. | Jan 2010 | A1 |
| 20100017710 | Kim et al. | Jan 2010 | A1 |
| 20100020035 | Ryu et al. | Jan 2010 | A1 |
| 20100020221 | Tupman et al. | Jan 2010 | A1 |
| 20100026640 | Kim et al. | Feb 2010 | A1 |
| 20100026647 | Abe et al. | Feb 2010 | A1 |
| 20100039446 | Hillis et al. | Feb 2010 | A1 |
| 20100044121 | Simon et al. | Feb 2010 | A1 |
| 20100045619 | Birnbaum et al. | Feb 2010 | A1 |
| 20100057235 | Wang et al. | Mar 2010 | A1 |
| 20100058231 | Duarte et al. | Mar 2010 | A1 |
| 20100060548 | Choi et al. | Mar 2010 | A1 |
| 20100060605 | Rimas-Ribikauskas et al. | Mar 2010 | A1 |
| 20100061637 | Mochizuki et al. | Mar 2010 | A1 |
| 20100062803 | Yun et al. | Mar 2010 | A1 |
| 20100070908 | Mori et al. | Mar 2010 | A1 |
| 20100073329 | Raman et al. | Mar 2010 | A1 |
| 20100083116 | Akifusa et al. | Apr 2010 | A1 |
| 20100085302 | Fairweather et al. | Apr 2010 | A1 |
| 20100085314 | Kwok | Apr 2010 | A1 |
| 20100085317 | Park et al. | Apr 2010 | A1 |
| 20100088596 | Griffin et al. | Apr 2010 | A1 |
| 20100088654 | Henhoeffer | Apr 2010 | A1 |
| 20100102832 | Bartling et al. | Apr 2010 | A1 |
| 20100110082 | Myrick et al. | May 2010 | A1 |
| 20100111434 | Madden | May 2010 | A1 |
| 20100127983 | Irani et al. | May 2010 | A1 |
| 20100128002 | Stacy et al. | May 2010 | A1 |
| 20100138776 | Korhonen | Jun 2010 | A1 |
| 20100148999 | Casparian et al. | Jun 2010 | A1 |
| 20100149096 | Migos et al. | Jun 2010 | A1 |
| 20100153879 | Rimas-Ribikauskas et al. | Jun 2010 | A1 |
| 20100156807 | Stallings et al. | Jun 2010 | A1 |
| 20100156813 | Duarte et al. | Jun 2010 | A1 |
| 20100156818 | Burrough et al. | Jun 2010 | A1 |
| 20100156823 | Paleczny et al. | Jun 2010 | A1 |
| 20100156825 | Sohn et al. | Jun 2010 | A1 |
| 20100156830 | Homma et al. | Jun 2010 | A1 |
| 20100159995 | Stallings et al. | Jun 2010 | A1 |
| 20100171713 | Kwok et al. | Jul 2010 | A1 |
| 20100175023 | Gatlin et al. | Jul 2010 | A1 |
| 20100180136 | Thompson et al. | Jul 2010 | A1 |
| 20100180225 | Chiba et al. | Jul 2010 | A1 |
| 20100199227 | Xiao et al. | Aug 2010 | A1 |
| 20100211872 | Rolston et al. | Aug 2010 | A1 |
| 20100214135 | Bathiche et al. | Aug 2010 | A1 |
| 20100214239 | Wu | Aug 2010 | A1 |
| 20100218663 | Choi | Sep 2010 | A1 |
| 20100220065 | Ma | Sep 2010 | A1 |
| 20100225456 | Eldering | Sep 2010 | A1 |
| 20100225604 | Homma et al. | Sep 2010 | A1 |
| 20100231533 | Chaudhri | Sep 2010 | A1 |
| 20100231534 | Chaudhri et al. | Sep 2010 | A1 |
| 20100231539 | Cruz-Hernandez et al. | Sep 2010 | A1 |
| 20100235118 | Moore et al. | Sep 2010 | A1 |
| 20100235726 | Ording et al. | Sep 2010 | A1 |
| 20100235733 | Drislane et al. | Sep 2010 | A1 |
| 20100235746 | Anzures | Sep 2010 | A1 |
| 20100240415 | Kim et al. | Sep 2010 | A1 |
| 20100241955 | Price et al. | Sep 2010 | A1 |
| 20100248787 | Smuga et al. | Sep 2010 | A1 |
| 20100251168 | Fujita et al. | Sep 2010 | A1 |
| 20100259500 | Kennedy | Oct 2010 | A1 |
| 20100271312 | Alameh et al. | Oct 2010 | A1 |
| 20100271500 | Park et al. | Oct 2010 | A1 |
| 20100277419 | Ganey et al. | Nov 2010 | A1 |
| 20100277496 | Kawanishi et al. | Nov 2010 | A1 |
| 20100281379 | Meaney et al. | Nov 2010 | A1 |
| 20100281385 | Meaney et al. | Nov 2010 | A1 |
| 20100287486 | Coddington | Nov 2010 | A1 |
| 20100289807 | Yu et al. | Nov 2010 | A1 |
| 20100293460 | Budelli | Nov 2010 | A1 |
| 20100295789 | Shin et al. | Nov 2010 | A1 |
| 20100295805 | Shin et al. | Nov 2010 | A1 |
| 20100302177 | Kim et al. | Dec 2010 | A1 |
| 20100302179 | Ahn et al. | Dec 2010 | A1 |
| 20100306702 | Warner | Dec 2010 | A1 |
| 20100308983 | Conte et al. | Dec 2010 | A1 |
| 20100309147 | Fleizach et al. | Dec 2010 | A1 |
| 20100313050 | Harrat et al. | Dec 2010 | A1 |
| 20100313124 | Privault et al. | Dec 2010 | A1 |
| 20100313146 | Nielsen et al. | Dec 2010 | A1 |
| 20100313156 | Louch et al. | Dec 2010 | A1 |
| 20100313158 | Lee et al. | Dec 2010 | A1 |
| 20100313166 | Nakayama et al. | Dec 2010 | A1 |
| 20100315417 | Cho et al. | Dec 2010 | A1 |
| 20100315438 | Horodezky et al. | Dec 2010 | A1 |
| 20100317410 | Song et al. | Dec 2010 | A1 |
| 20100321301 | Casparian et al. | Dec 2010 | A1 |
| 20100321312 | Han et al. | Dec 2010 | A1 |
| 20100325578 | Mital et al. | Dec 2010 | A1 |
| 20100328229 | Weber et al. | Dec 2010 | A1 |
| 20110010626 | Fino et al. | Jan 2011 | A1 |
| 20110012851 | Ciesla et al. | Jan 2011 | A1 |
| 20110018695 | Bells et al. | Jan 2011 | A1 |
| 20110026099 | Kwon et al. | Feb 2011 | A1 |
| 20110035145 | Yamasaki | Feb 2011 | A1 |
| 20110037706 | Pasquero et al. | Feb 2011 | A1 |
| 20110038552 | Lam | Feb 2011 | A1 |
| 20110039602 | McNamara et al. | Feb 2011 | A1 |
| 20110047368 | Sundaramurthy et al. | Feb 2011 | A1 |
| 20110050576 | Forutanpour et al. | Mar 2011 | A1 |
| 20110050588 | Li et al. | Mar 2011 | A1 |
| 20110050591 | Kim et al. | Mar 2011 | A1 |
| 20110050594 | Kim et al. | Mar 2011 | A1 |
| 20110050628 | Homma et al. | Mar 2011 | A1 |
| 20110050629 | Homma et al. | Mar 2011 | A1 |
| 20110050630 | Ikeda | Mar 2011 | A1 |
| 20110050653 | Miyazawa et al. | Mar 2011 | A1 |
| 20110050687 | Alyshev et al. | Mar 2011 | A1 |
| 20110054837 | Ikeda | Mar 2011 | A1 |
| 20110055135 | Dawson et al. | Mar 2011 | A1 |
| 20110055741 | Jeon et al. | Mar 2011 | A1 |
| 20110057886 | Ng et al. | Mar 2011 | A1 |
| 20110057903 | Yamano et al. | Mar 2011 | A1 |
| 20110061021 | Kang et al. | Mar 2011 | A1 |
| 20110061029 | Yeh et al. | Mar 2011 | A1 |
| 20110063236 | Arai et al. | Mar 2011 | A1 |
| 20110063248 | Yoon | Mar 2011 | A1 |
| 20110069012 | Martensson | Mar 2011 | A1 |
| 20110069016 | Victor | Mar 2011 | A1 |
| 20110074697 | Rapp et al. | Mar 2011 | A1 |
| 20110080349 | Holbein et al. | Apr 2011 | A1 |
| 20110080350 | Almalki et al. | Apr 2011 | A1 |
| 20110080367 | Marchand et al. | Apr 2011 | A1 |
| 20110084910 | Almalki et al. | Apr 2011 | A1 |
| 20110087982 | McCann et al. | Apr 2011 | A1 |
| 20110087983 | Shim | Apr 2011 | A1 |
| 20110093815 | Gobeil | Apr 2011 | A1 |
| 20110093817 | Song et al. | Apr 2011 | A1 |
| 20110102829 | Jourdan | May 2011 | A1 |
| 20110107272 | Aquilar | May 2011 | A1 |
| 20110109617 | Snook et al. | May 2011 | A1 |
| 20110116716 | Kwon et al. | May 2011 | A1 |
| 20110119610 | Hackborn et al. | May 2011 | A1 |
| 20110126139 | Jeong et al. | May 2011 | A1 |
| 20110138295 | Momchilov et al. | Jun 2011 | A1 |
| 20110141031 | McCullough et al. | Jun 2011 | A1 |
| 20110141052 | Bernstein et al. | Jun 2011 | A1 |
| 20110144777 | Firkins et al. | Jun 2011 | A1 |
| 20110145752 | Fagans | Jun 2011 | A1 |
| 20110145753 | Prakash | Jun 2011 | A1 |
| 20110145759 | Leffert et al. | Jun 2011 | A1 |
| 20110145764 | Higuchi et al. | Jun 2011 | A1 |
| 20110149138 | Watkins | Jun 2011 | A1 |
| 20110154199 | Maffitt et al. | Jun 2011 | A1 |
| 20110159469 | Hwang et al. | Jun 2011 | A1 |
| 20110163971 | Wagner et al. | Jul 2011 | A1 |
| 20110163978 | Park et al. | Jul 2011 | A1 |
| 20110169765 | Aono | Jul 2011 | A1 |
| 20110175826 | Moore et al. | Jul 2011 | A1 |
| 20110175832 | Miyazawa et al. | Jul 2011 | A1 |
| 20110181521 | Reid et al. | Jul 2011 | A1 |
| 20110181526 | Shaffer et al. | Jul 2011 | A1 |
| 20110181538 | Aono | Jul 2011 | A1 |
| 20110181751 | Mizumori | Jul 2011 | A1 |
| 20110185299 | Hinckley et al. | Jul 2011 | A1 |
| 20110185300 | Hinckley et al. | Jul 2011 | A1 |
| 20110185316 | Reid et al. | Jul 2011 | A1 |
| 20110191675 | Kauranen | Aug 2011 | A1 |
| 20110193788 | King et al. | Aug 2011 | A1 |
| 20110193809 | Walley et al. | Aug 2011 | A1 |
| 20110193881 | Rydenhag | Aug 2011 | A1 |
| 20110197160 | Kim et al. | Aug 2011 | A1 |
| 20110201387 | Paek et al. | Aug 2011 | A1 |
| 20110202834 | Mandryk et al. | Aug 2011 | A1 |
| 20110202853 | Mujkic | Aug 2011 | A1 |
| 20110202879 | Stovicek et al. | Aug 2011 | A1 |
| 20110205163 | Hinckley et al. | Aug 2011 | A1 |
| 20110209088 | Hinckley et al. | Aug 2011 | A1 |
| 20110209093 | Hinckley et al. | Aug 2011 | A1 |
| 20110209097 | Hinckley et al. | Aug 2011 | A1 |
| 20110209099 | Hinckley et al. | Aug 2011 | A1 |
| 20110209104 | Hinckley et al. | Aug 2011 | A1 |
| 20110210834 | Pasquero et al. | Sep 2011 | A1 |
| 20110210926 | Pasquero et al. | Sep 2011 | A1 |
| 20110210931 | Shai | Sep 2011 | A1 |
| 20110215914 | Edwards | Sep 2011 | A1 |
| 20110221684 | Rydenhag | Sep 2011 | A1 |
| 20110221776 | Shimotani et al. | Sep 2011 | A1 |
| 20110231789 | Bukurak et al. | Sep 2011 | A1 |
| 20110234639 | Shimotani et al. | Sep 2011 | A1 |
| 20110238690 | Arrasvouri et al. | Sep 2011 | A1 |
| 20110239110 | Garrett et al. | Sep 2011 | A1 |
| 20110242029 | Kasahara et al. | Oct 2011 | A1 |
| 20110246801 | Seethaler et al. | Oct 2011 | A1 |
| 20110246877 | Kwak et al. | Oct 2011 | A1 |
| 20110248916 | Griffin et al. | Oct 2011 | A1 |
| 20110248942 | Yana et al. | Oct 2011 | A1 |
| 20110248948 | Griffin et al. | Oct 2011 | A1 |
| 20110252346 | Chaudhri | Oct 2011 | A1 |
| 20110252357 | Chaudhri | Oct 2011 | A1 |
| 20110252362 | Cho et al. | Oct 2011 | A1 |
| 20110252380 | Chaudhri | Oct 2011 | A1 |
| 20110258537 | Rives et al. | Oct 2011 | A1 |
| 20110260994 | Saynac et al. | Oct 2011 | A1 |
| 20110263298 | Park | Oct 2011 | A1 |
| 20110265035 | Lepage et al. | Oct 2011 | A1 |
| 20110265045 | Hsieh | Oct 2011 | A1 |
| 20110267530 | Chun | Nov 2011 | A1 |
| 20110279380 | Weber et al. | Nov 2011 | A1 |
| 20110279381 | Tong et al. | Nov 2011 | A1 |
| 20110279395 | Kuwabara et al. | Nov 2011 | A1 |
| 20110279852 | Oda et al. | Nov 2011 | A1 |
| 20110285656 | Yaksick et al. | Nov 2011 | A1 |
| 20110285659 | Kuwabara et al. | Nov 2011 | A1 |
| 20110291945 | Ewing, Jr. et al. | Dec 2011 | A1 |
| 20110291951 | Tong | Dec 2011 | A1 |
| 20110296334 | Ryu et al. | Dec 2011 | A1 |
| 20110296351 | Ewing, Jr. et al. | Dec 2011 | A1 |
| 20110304559 | Pasquero | Dec 2011 | A1 |
| 20110304577 | Brown et al. | Dec 2011 | A1 |
| 20110310049 | Homma et al. | Dec 2011 | A1 |
| 20110319136 | Labowicz et al. | Dec 2011 | A1 |
| 20120001856 | Davidson | Jan 2012 | A1 |
| 20120005622 | Park et al. | Jan 2012 | A1 |
| 20120007857 | Noda et al. | Jan 2012 | A1 |
| 20120011437 | James et al. | Jan 2012 | A1 |
| 20120013541 | Boka et al. | Jan 2012 | A1 |
| 20120013542 | Shenfield | Jan 2012 | A1 |
| 20120013607 | Lee | Jan 2012 | A1 |
| 20120019448 | Pitkanen et al. | Jan 2012 | A1 |
| 20120023591 | Sahita et al. | Jan 2012 | A1 |
| 20120026110 | Yamano | Feb 2012 | A1 |
| 20120030623 | Hoellwarth | Feb 2012 | A1 |
| 20120032979 | Blow et al. | Feb 2012 | A1 |
| 20120036441 | Basir et al. | Feb 2012 | A1 |
| 20120036556 | LeBeau et al. | Feb 2012 | A1 |
| 20120038580 | Sasaki | Feb 2012 | A1 |
| 20120044153 | Arrasvouri et al. | Feb 2012 | A1 |
| 20120047380 | Nurmi | Feb 2012 | A1 |
| 20120056837 | Park et al. | Mar 2012 | A1 |
| 20120056848 | Yamano et al. | Mar 2012 | A1 |
| 20120057039 | Gardiner et al. | Mar 2012 | A1 |
| 20120060123 | Smith | Mar 2012 | A1 |
| 20120062470 | Chang | Mar 2012 | A1 |
| 20120062564 | Miyashita et al. | Mar 2012 | A1 |
| 20120062604 | Lobo | Mar 2012 | A1 |
| 20120062732 | Marman et al. | Mar 2012 | A1 |
| 20120066630 | Kim et al. | Mar 2012 | A1 |
| 20120066648 | Rolleston et al. | Mar 2012 | A1 |
| 20120081326 | Heubel et al. | Apr 2012 | A1 |
| 20120081375 | Robert et al. | Apr 2012 | A1 |
| 20120084644 | Robert et al. | Apr 2012 | A1 |
| 20120084689 | Ledet et al. | Apr 2012 | A1 |
| 20120084713 | Desai et al. | Apr 2012 | A1 |
| 20120089932 | Kano et al. | Apr 2012 | A1 |
| 20120089942 | Gammon | Apr 2012 | A1 |
| 20120089951 | Cassidy | Apr 2012 | A1 |
| 20120092381 | Hoover et al. | Apr 2012 | A1 |
| 20120096393 | Shim et al. | Apr 2012 | A1 |
| 20120096400 | Cho | Apr 2012 | A1 |
| 20120098780 | Fujisawa et al. | Apr 2012 | A1 |
| 20120102437 | Worley et al. | Apr 2012 | A1 |
| 20120105358 | Momeyer et al. | May 2012 | A1 |
| 20120105367 | Son et al. | May 2012 | A1 |
| 20120106852 | Khawand et al. | May 2012 | A1 |
| 20120113007 | Koch et al. | May 2012 | A1 |
| 20120113023 | Koch et al. | May 2012 | A1 |
| 20120126962 | Ujii et al. | May 2012 | A1 |
| 20120131495 | Goossens et al. | May 2012 | A1 |
| 20120139844 | Ramstein et al. | Jun 2012 | A1 |
| 20120139864 | Sleeman et al. | Jun 2012 | A1 |
| 20120144330 | Flint | Jun 2012 | A1 |
| 20120146945 | Miyazawa et al. | Jun 2012 | A1 |
| 20120147052 | Homma et al. | Jun 2012 | A1 |
| 20120154303 | Lazaridis et al. | Jun 2012 | A1 |
| 20120154328 | Kono | Jun 2012 | A1 |
| 20120158629 | Hinckley et al. | Jun 2012 | A1 |
| 20120159380 | Kocienda et al. | Jun 2012 | A1 |
| 20120162093 | Buxton et al. | Jun 2012 | A1 |
| 20120174042 | Chang | Jun 2012 | A1 |
| 20120169646 | Berkes et al. | Jul 2012 | A1 |
| 20120169716 | Mihara | Jul 2012 | A1 |
| 20120176403 | Cha et al. | Jul 2012 | A1 |
| 20120179967 | Hayes | Jul 2012 | A1 |
| 20120180001 | Griffen et al. | Jul 2012 | A1 |
| 20120182226 | Tuli | Jul 2012 | A1 |
| 20120183271 | Forutanpour et al. | Jul 2012 | A1 |
| 20120192108 | Kolb | Jul 2012 | A1 |
| 20120200528 | Ciesla et al. | Aug 2012 | A1 |
| 20120206393 | Hillis et al. | Aug 2012 | A1 |
| 20120216114 | Privault et al. | Aug 2012 | A1 |
| 20120218203 | Kanki | Aug 2012 | A1 |
| 20120235912 | Laubach | Sep 2012 | A1 |
| 20120236037 | Lessing et al. | Sep 2012 | A1 |
| 20120240044 | Johnson et al. | Sep 2012 | A1 |
| 20120242584 | Tuli | Sep 2012 | A1 |
| 20120242599 | Seo et al. | Sep 2012 | A1 |
| 20120245922 | Koslova et al. | Sep 2012 | A1 |
| 20120249575 | Krolczyk et al. | Oct 2012 | A1 |
| 20120249853 | Krolczyk et al. | Oct 2012 | A1 |
| 20120250598 | Lonnfors et al. | Oct 2012 | A1 |
| 20120256829 | Dodge | Oct 2012 | A1 |
| 20120256846 | Mak | Oct 2012 | A1 |
| 20120256847 | Mak et al. | Oct 2012 | A1 |
| 20120256857 | Mak | Oct 2012 | A1 |
| 20120257071 | Prentice | Oct 2012 | A1 |
| 20120260208 | Jung | Oct 2012 | A1 |
| 20120260219 | Piccolotto | Oct 2012 | A1 |
| 20120260220 | Griffin | Oct 2012 | A1 |
| 20120274578 | Snow et al. | Nov 2012 | A1 |
| 20120274591 | Rimas-Ribikauskas et al. | Nov 2012 | A1 |
| 20120274662 | Kim et al. | Nov 2012 | A1 |
| 20120278744 | Kozitsyn et al. | Nov 2012 | A1 |
| 20120284673 | Lamb et al. | Nov 2012 | A1 |
| 20120293449 | Dietz | Nov 2012 | A1 |
| 20120293551 | Momeyer et al. | Nov 2012 | A1 |
| 20120297041 | Momchilov | Nov 2012 | A1 |
| 20120303548 | Johnson et al. | Nov 2012 | A1 |
| 20120304108 | Jarrett et al. | Nov 2012 | A1 |
| 20120304132 | Sareen et al. | Nov 2012 | A1 |
| 20120304133 | Nan et al. | Nov 2012 | A1 |
| 20120306632 | Fleizach et al. | Dec 2012 | A1 |
| 20120306748 | Fleizach et al. | Dec 2012 | A1 |
| 20120306764 | Kamibeppu | Dec 2012 | A1 |
| 20120306765 | Moore | Dec 2012 | A1 |
| 20120306766 | Moore | Dec 2012 | A1 |
| 20120306772 | Tan et al. | Dec 2012 | A1 |
| 20120306778 | Wheeldreyer et al. | Dec 2012 | A1 |
| 20120306927 | Lee et al. | Dec 2012 | A1 |
| 20120311429 | Decker et al. | Dec 2012 | A1 |
| 20120311437 | Weeldreyer et al. | Dec 2012 | A1 |
| 20120311498 | Kluttz et al. | Dec 2012 | A1 |
| 20120311504 | van Os et al. | Dec 2012 | A1 |
| 20120313847 | Boda et al. | Dec 2012 | A1 |
| 20130002561 | Wakasa | Jan 2013 | A1 |
| 20130014057 | Reinpoldt et al. | Jan 2013 | A1 |
| 20130016042 | Makinen et al. | Jan 2013 | A1 |
| 20130016056 | Shinozaki et al. | Jan 2013 | A1 |
| 20130016122 | Bhatt et al. | Jan 2013 | A1 |
| 20130019158 | Watanabe | Jan 2013 | A1 |
| 20130019174 | Gil et al. | Jan 2013 | A1 |
| 20130031514 | Gabbert | Jan 2013 | A1 |
| 20130036386 | Park et al. | Feb 2013 | A1 |
| 20130042199 | Fong et al. | Feb 2013 | A1 |
| 20130044062 | Bose et al. | Feb 2013 | A1 |
| 20130047100 | Kroeger et al. | Feb 2013 | A1 |
| 20130050131 | Lee et al. | Feb 2013 | A1 |
| 20130050143 | Kim et al. | Feb 2013 | A1 |
| 20130050518 | Takemura et al. | Feb 2013 | A1 |
| 20130061172 | Huang et al. | Mar 2013 | A1 |
| 20130063364 | Moore | Mar 2013 | A1 |
| 20130063389 | Moore | Mar 2013 | A1 |
| 20130067383 | Kataoka et al. | Mar 2013 | A1 |
| 20130067513 | Takami | Mar 2013 | A1 |
| 20130067527 | Ashbook et al. | Mar 2013 | A1 |
| 20130069889 | Pearce et al. | Mar 2013 | A1 |
| 20130069991 | Davidson | Mar 2013 | A1 |
| 20130074003 | Dolenc | Mar 2013 | A1 |
| 20130076649 | Myers et al. | Mar 2013 | A1 |
| 20130076676 | Gan | Mar 2013 | A1 |
| 20130077804 | Glebe et al. | Mar 2013 | A1 |
| 20130082824 | Colley | Apr 2013 | A1 |
| 20130082937 | Liu et al. | Apr 2013 | A1 |
| 20130086056 | Dyor et al. | Apr 2013 | A1 |
| 20130088455 | Jeong | Apr 2013 | A1 |
| 20130093691 | Moosavi | Apr 2013 | A1 |
| 20130093764 | Andersson et al. | Apr 2013 | A1 |
| 20130097520 | Lewin et al. | Apr 2013 | A1 |
| 20130097521 | Lewin et al. | Apr 2013 | A1 |
| 20130097534 | Lewin et al. | Apr 2013 | A1 |
| 20130097539 | Mansson et al. | Apr 2013 | A1 |
| 20130097556 | Louch | Apr 2013 | A1 |
| 20130097562 | Kermoian et al. | Apr 2013 | A1 |
| 20130102366 | Teng et al. | Apr 2013 | A1 |
| 20130111345 | Newman et al. | May 2013 | A1 |
| 20130111378 | Newman et al. | May 2013 | A1 |
| 20130111398 | Lu et al. | May 2013 | A1 |
| 20130111415 | Newman et al. | May 2013 | A1 |
| 20130111579 | Newman et al. | May 2013 | A1 |
| 20130113715 | Grant et al. | May 2013 | A1 |
| 20130113720 | Van Eerd et al. | May 2013 | A1 |
| 20130113760 | Gossweiler, III et al. | May 2013 | A1 |
| 20130120278 | Cantrell | May 2013 | A1 |
| 20130120280 | Kukulski | May 2013 | A1 |
| 20130120295 | Kim et al. | May 2013 | A1 |
| 20130120306 | Furukawa | May 2013 | A1 |
| 20130125039 | Murata | May 2013 | A1 |
| 20130127755 | Lynn et al. | May 2013 | A1 |
| 20130135243 | Hirsch et al. | May 2013 | A1 |
| 20130135288 | King et al. | May 2013 | A1 |
| 20130135499 | Song | May 2013 | A1 |
| 20130141364 | Lynn et al. | Jun 2013 | A1 |
| 20130141396 | Lynn et al. | Jun 2013 | A1 |
| 20130145313 | Roh et al. | Jun 2013 | A1 |
| 20130154948 | Schediwy et al. | Jun 2013 | A1 |
| 20130154959 | Lindsay et al. | Jun 2013 | A1 |
| 20130155018 | Dagdeviren | Jun 2013 | A1 |
| 20130159893 | Lewis et al. | Jun 2013 | A1 |
| 20130159930 | Paretti et al. | Jun 2013 | A1 |
| 20130162603 | Peng et al. | Jun 2013 | A1 |
| 20130162667 | Eskolin et al. | Jun 2013 | A1 |
| 20130169549 | Seymour et al. | Jul 2013 | A1 |
| 20130174049 | Townsend et al. | Jul 2013 | A1 |
| 20130174089 | Ki | Jul 2013 | A1 |
| 20130174094 | Heo et al. | Jul 2013 | A1 |
| 20130174179 | Park et al. | Jul 2013 | A1 |
| 20130179840 | Fisher et al. | Jul 2013 | A1 |
| 20130185642 | Gammons | Jul 2013 | A1 |
| 20130187869 | Rydenhag et al. | Jul 2013 | A1 |
| 20130191791 | Rydenhag et al. | Jul 2013 | A1 |
| 20130194217 | Lee et al. | Aug 2013 | A1 |
| 20130194480 | Fukata et al. | Aug 2013 | A1 |
| 20130198690 | Barsoum et al. | Aug 2013 | A1 |
| 20130201139 | Tanaka | Aug 2013 | A1 |
| 20130212515 | Eleftheriou | Aug 2013 | A1 |
| 20130212541 | Dolenc et al. | Aug 2013 | A1 |
| 20130215079 | Johnson et al. | Aug 2013 | A1 |
| 20130222274 | Mori et al. | Aug 2013 | A1 |
| 20130222323 | McKenzie | Aug 2013 | A1 |
| 20130222333 | Miles et al. | Aug 2013 | A1 |
| 20130222671 | Tseng et al. | Aug 2013 | A1 |
| 20130227413 | Thorsander et al. | Aug 2013 | A1 |
| 20130227419 | Lee et al. | Aug 2013 | A1 |
| 20130227450 | Na et al. | Aug 2013 | A1 |
| 20130228023 | Drasnin et al. | Sep 2013 | A1 |
| 20130232353 | Belesiu et al. | Sep 2013 | A1 |
| 20130232402 | Lu et al. | Sep 2013 | A1 |
| 20130234929 | Libin | Sep 2013 | A1 |
| 20130239057 | Ubillos et al. | Sep 2013 | A1 |
| 20130246954 | Gray et al. | Sep 2013 | A1 |
| 20130249814 | Zeng | Sep 2013 | A1 |
| 20130257793 | Zeliff et al. | Oct 2013 | A1 |
| 20130257817 | Yliaho | Oct 2013 | A1 |
| 20130263252 | Lien et al. | Oct 2013 | A1 |
| 20130265246 | Tae | Oct 2013 | A1 |
| 20130265452 | Shin et al. | Oct 2013 | A1 |
| 20130268875 | Han et al. | Oct 2013 | A1 |
| 20130271395 | Tsai et al. | Oct 2013 | A1 |
| 20130275422 | Silber et al. | Oct 2013 | A1 |
| 20130278520 | Weng et al. | Oct 2013 | A1 |
| 20130293496 | Takamoto | Nov 2013 | A1 |
| 20130305184 | Kim et al. | Nov 2013 | A1 |
| 20130307790 | Konttori et al. | Nov 2013 | A1 |
| 20130307792 | Andres et al. | Nov 2013 | A1 |
| 20130314359 | Sudou | Nov 2013 | A1 |
| 20130314434 | Shetterly et al. | Nov 2013 | A1 |
| 20130321340 | Seo et al. | Dec 2013 | A1 |
| 20130321457 | Bauermeister et al. | Dec 2013 | A1 |
| 20130325342 | Pylappan et al. | Dec 2013 | A1 |
| 20130326420 | Liu et al. | Dec 2013 | A1 |
| 20130326421 | Jo | Dec 2013 | A1 |
| 20130326583 | Freihold et al. | Dec 2013 | A1 |
| 20130328770 | Parham | Dec 2013 | A1 |
| 20130328793 | Chowdhury | Dec 2013 | A1 |
| 20130328796 | Al-Dahle et al. | Dec 2013 | A1 |
| 20130332836 | Cho | Dec 2013 | A1 |
| 20130332892 | Matsuki | Dec 2013 | A1 |
| 20130335373 | Tomiyasu | Dec 2013 | A1 |
| 20130338847 | Lisseman et al. | Dec 2013 | A1 |
| 20130339001 | Craswell et al. | Dec 2013 | A1 |
| 20130339909 | Ha | Dec 2013 | A1 |
| 20140002355 | Lee et al. | Jan 2014 | A1 |
| 20140002374 | Hunt et al. | Jan 2014 | A1 |
| 20140002386 | Rosenberg et al. | Jan 2014 | A1 |
| 20140013271 | Moore et al. | Jan 2014 | A1 |
| 20140015784 | Oonishi | Jan 2014 | A1 |
| 20140019786 | Green et al. | Jan 2014 | A1 |
| 20140024414 | Fuji | Jan 2014 | A1 |
| 20140026098 | Gilman | Jan 2014 | A1 |
| 20140026099 | Andersson Reimer et al. | Jan 2014 | A1 |
| 20140028554 | De Los Reyes et al. | Jan 2014 | A1 |
| 20140028571 | St. Clair | Jan 2014 | A1 |
| 20140028601 | Moore | Jan 2014 | A1 |
| 20140028606 | Giannetta | Jan 2014 | A1 |
| 20140035804 | Dearman | Feb 2014 | A1 |
| 20140035826 | Frazier et al. | Feb 2014 | A1 |
| 20140049491 | Nagar et al. | Feb 2014 | A1 |
| 20140053116 | Smith et al. | Feb 2014 | A1 |
| 20140055367 | Dearman et al. | Feb 2014 | A1 |
| 20140055377 | Kim | Feb 2014 | A1 |
| 20140059460 | Ho | Feb 2014 | A1 |
| 20140059485 | Lehrian et al. | Feb 2014 | A1 |
| 20140063316 | Lee et al. | Mar 2014 | A1 |
| 20140063541 | Yamazaki | Mar 2014 | A1 |
| 20140067293 | Parivar et al. | Mar 2014 | A1 |
| 20140068475 | Li et al. | Mar 2014 | A1 |
| 20140071060 | Santos-Gomez | Mar 2014 | A1 |
| 20140072281 | Cho et al. | Mar 2014 | A1 |
| 20140072283 | Cho et al. | Mar 2014 | A1 |
| 20140078318 | Alameh | Mar 2014 | A1 |
| 20140078343 | Dai et al. | Mar 2014 | A1 |
| 20140082536 | Costa et al. | Mar 2014 | A1 |
| 20140092025 | Pala et al. | Apr 2014 | A1 |
| 20140092030 | Van der Velden | Apr 2014 | A1 |
| 20140092031 | Schwartz et al. | Apr 2014 | A1 |
| 20140108936 | Khosropour et al. | Apr 2014 | A1 |
| 20140109016 | Ouyang et al. | Apr 2014 | A1 |
| 20140111456 | Kashiwa et al. | Apr 2014 | A1 |
| 20140111480 | Kim et al. | Apr 2014 | A1 |
| 20140111670 | Lord et al. | Apr 2014 | A1 |
| 20140118268 | Kuscher | May 2014 | A1 |
| 20140123080 | Gan | May 2014 | A1 |
| 20140139456 | Wigdor et al. | May 2014 | A1 |
| 20140139471 | Matsuki | May 2014 | A1 |
| 20140145970 | Cho | May 2014 | A1 |
| 20140152581 | Case et al. | Jun 2014 | A1 |
| 20140157203 | Jeon et al. | Jun 2014 | A1 |
| 20140160063 | Yairi et al. | Jun 2014 | A1 |
| 20140160073 | Matsuki | Jun 2014 | A1 |
| 20140160168 | Ogle | Jun 2014 | A1 |
| 20140164955 | Thiruvidam et al. | Jun 2014 | A1 |
| 20140164966 | Kim et al. | Jun 2014 | A1 |
| 20140165006 | Chaudhri et al. | Jun 2014 | A1 |
| 20140168093 | Lawrence | Jun 2014 | A1 |
| 20140168110 | Araki et al. | Jun 2014 | A1 |
| 20140168153 | Deichmann et al. | Jun 2014 | A1 |
| 20140173517 | Chaudhri | Jun 2014 | A1 |
| 20140179377 | Song et al. | Jun 2014 | A1 |
| 20140184526 | Cho | Jul 2014 | A1 |
| 20140201660 | Clausen et al. | Jul 2014 | A1 |
| 20140208271 | Bell et al. | Jul 2014 | A1 |
| 20140210758 | Park et al. | Jul 2014 | A1 |
| 20140210760 | Aberg et al. | Jul 2014 | A1 |
| 20140210798 | Wilson | Jul 2014 | A1 |
| 20140223376 | Tarvainen et al. | Aug 2014 | A1 |
| 20140223381 | Huang et al. | Aug 2014 | A1 |
| 20140237408 | Ohlsson et al. | Aug 2014 | A1 |
| 20140245202 | Yoon et al. | Aug 2014 | A1 |
| 20140245367 | Sasaki et al. | Aug 2014 | A1 |
| 20140253305 | Rosenberg et al. | Sep 2014 | A1 |
| 20140267114 | Lisseman et al. | Sep 2014 | A1 |
| 20140267135 | Chhabra | Sep 2014 | A1 |
| 20140267362 | Kocienda et al. | Sep 2014 | A1 |
| 20140282084 | Murarka et al. | Sep 2014 | A1 |
| 20140282211 | Ady et al. | Sep 2014 | A1 |
| 20140282214 | Shirzadi et al. | Sep 2014 | A1 |
| 20140300569 | Matsuki et al. | Oct 2014 | A1 |
| 20140304599 | Alexandersson | Oct 2014 | A1 |
| 20140304646 | Rossman | Oct 2014 | A1 |
| 20140304651 | Johansson et al. | Oct 2014 | A1 |
| 20140306897 | Cueto | Oct 2014 | A1 |
| 20140306899 | Hicks | Oct 2014 | A1 |
| 20140310638 | Lee et al. | Oct 2014 | A1 |
| 20140313130 | Yamano et al. | Oct 2014 | A1 |
| 20140333551 | Kim et al. | Nov 2014 | A1 |
| 20140333561 | Bull et al. | Nov 2014 | A1 |
| 20140344765 | Hicks et al. | Nov 2014 | A1 |
| 20140351744 | Jeon et al. | Nov 2014 | A1 |
| 20140354845 | Molgaard et al. | Dec 2014 | A1 |
| 20140354850 | Kosaka et al. | Dec 2014 | A1 |
| 20140359438 | Matsuki | Dec 2014 | A1 |
| 20140359528 | Murata | Dec 2014 | A1 |
| 20140361982 | Shaffer | Dec 2014 | A1 |
| 20140365882 | Lemay | Dec 2014 | A1 |
| 20140365945 | Karunamuni et al. | Dec 2014 | A1 |
| 20140365956 | Karunamuni et al. | Dec 2014 | A1 |
| 20140368436 | Abzarian et al. | Dec 2014 | A1 |
| 20140380247 | Tecarro et al. | Dec 2014 | A1 |
| 20150002664 | Eppinger et al. | Jan 2015 | A1 |
| 20150012861 | Loginov | Jan 2015 | A1 |
| 20150015763 | Lee et al. | Jan 2015 | A1 |
| 20150019997 | Kim et al. | Jan 2015 | A1 |
| 20150020032 | Chen | Jan 2015 | A1 |
| 20150020033 | Newham et al. | Jan 2015 | A1 |
| 20150020036 | Kim et al. | Jan 2015 | A1 |
| 20150022482 | Hewitt et al. | Jan 2015 | A1 |
| 20150026584 | Kobayakov et al. | Jan 2015 | A1 |
| 20150026592 | Mohammed et al. | Jan 2015 | A1 |
| 20150026642 | Wilson et al. | Jan 2015 | A1 |
| 20150029149 | Andersson et al. | Jan 2015 | A1 |
| 20150033184 | Kim et al. | Jan 2015 | A1 |
| 20150040065 | Bianco et al. | Feb 2015 | A1 |
| 20150042588 | Park | Feb 2015 | A1 |
| 20150046876 | Goldenberg | Feb 2015 | A1 |
| 20150049033 | Kim et al. | Feb 2015 | A1 |
| 20150052464 | Chen et al. | Feb 2015 | A1 |
| 20150055890 | Lundin et al. | Feb 2015 | A1 |
| 20150058723 | Cieplinski et al. | Feb 2015 | A1 |
| 20150062046 | Cho et al. | Mar 2015 | A1 |
| 20150062052 | Bernstein et al. | Mar 2015 | A1 |
| 20150062068 | Shih et al. | Mar 2015 | A1 |
| 20150066950 | Tobe | Mar 2015 | A1 |
| 20150067495 | Bernstein et al. | Mar 2015 | A1 |
| 20150067496 | Missig et al. | Mar 2015 | A1 |
| 20150067497 | Cieplinski et al. | Mar 2015 | A1 |
| 20150067513 | Zambetti et al. | Mar 2015 | A1 |
| 20150067519 | Missig et al. | Mar 2015 | A1 |
| 20150067534 | Choi et al. | Mar 2015 | A1 |
| 20150067559 | Missig et al. | Mar 2015 | A1 |
| 20150067560 | Cieplinski et al. | Mar 2015 | A1 |
| 20150067563 | Bernstein et al. | Mar 2015 | A1 |
| 20150067596 | Brown et al. | Mar 2015 | A1 |
| 20150067601 | Bernstein et al. | Mar 2015 | A1 |
| 20150067602 | Bernstein et al. | Mar 2015 | A1 |
| 20150067605 | Zambetti et al. | Mar 2015 | A1 |
| 20150071547 | Keating et al. | Mar 2015 | A1 |
| 20150082162 | Cho et al. | Mar 2015 | A1 |
| 20150082238 | Meng | Mar 2015 | A1 |
| 20150116205 | Westerman et al. | Apr 2015 | A1 |
| 20150121218 | Kim et al. | Apr 2015 | A1 |
| 20150121225 | Somasundaram et al. | Apr 2015 | A1 |
| 20150128092 | Lee et al. | May 2015 | A1 |
| 20150135108 | Pope et al. | May 2015 | A1 |
| 20150135109 | Zambetti et al. | May 2015 | A1 |
| 20150135132 | Josephson | May 2015 | A1 |
| 20150138126 | Westerman | May 2015 | A1 |
| 20150138155 | Bernstein et al. | May 2015 | A1 |
| 20150139605 | Wiklof | May 2015 | A1 |
| 20150143273 | Bernstein et al. | May 2015 | A1 |
| 20150143284 | Bennett et al. | May 2015 | A1 |
| 20150143294 | Piccinato et al. | May 2015 | A1 |
| 20150143303 | Sarrazin et al. | May 2015 | A1 |
| 20150149899 | Bernstein et al. | May 2015 | A1 |
| 20150149964 | Bernstein et al. | May 2015 | A1 |
| 20150149967 | Bernstein et al. | May 2015 | A1 |
| 20150153897 | Huang et al. | Jun 2015 | A1 |
| 20150153929 | Bernstein et al. | Jun 2015 | A1 |
| 20150160729 | Nakagawa | Jun 2015 | A1 |
| 20150169059 | Behles et al. | Jun 2015 | A1 |
| 20150185840 | Golyshko et al. | Jul 2015 | A1 |
| 20150193099 | Murphy | Jul 2015 | A1 |
| 20150193951 | Lee et al. | Jul 2015 | A1 |
| 20150205342 | Ooi et al. | Jul 2015 | A1 |
| 20150205495 | Koide et al. | Jul 2015 | A1 |
| 20150205775 | Berdahl et al. | Jul 2015 | A1 |
| 20150234446 | Nathan et al. | Aug 2015 | A1 |
| 20150234493 | Parivar et al. | Aug 2015 | A1 |
| 20150253866 | Amm et al. | Sep 2015 | A1 |
| 20150268786 | Kitada | Sep 2015 | A1 |
| 20150268802 | Kim et al. | Sep 2015 | A1 |
| 20150268813 | Bos | Sep 2015 | A1 |
| 20150309573 | Brombach et al. | Oct 2015 | A1 |
| 20150321607 | Cho et al. | Nov 2015 | A1 |
| 20150332107 | Paniaras | Nov 2015 | A1 |
| 20150332607 | Gardner, Jr. et al. | Nov 2015 | A1 |
| 20150378519 | Brown et al. | Dec 2015 | A1 |
| 20150378982 | McKenzie et al. | Dec 2015 | A1 |
| 20150381931 | Uhma et al. | Dec 2015 | A1 |
| 20160004373 | Huang | Jan 2016 | A1 |
| 20160004393 | Faaborg et al. | Jan 2016 | A1 |
| 20160004427 | Zambetti et al. | Jan 2016 | A1 |
| 20160004428 | Bernstein et al. | Jan 2016 | A1 |
| 20160004430 | Missig et al. | Jan 2016 | A1 |
| 20160004431 | Bernstein et al. | Jan 2016 | A1 |
| 20160004432 | Bernstein et al. | Jan 2016 | A1 |
| 20160011725 | D'Argenio et al. | Jan 2016 | A1 |
| 20160011771 | Cieplinski | Jan 2016 | A1 |
| 20160019718 | Mukkamala et al. | Jan 2016 | A1 |
| 20160021511 | Jin et al. | Jan 2016 | A1 |
| 20160041750 | Cieplinski et al. | Feb 2016 | A1 |
| 20160048326 | Kim et al. | Feb 2016 | A1 |
| 20160062466 | Moussette et al. | Mar 2016 | A1 |
| 20160062619 | Reeve et al. | Mar 2016 | A1 |
| 20160070401 | Kim et al. | Mar 2016 | A1 |
| 20160077721 | Laubach et al. | Mar 2016 | A1 |
| 20160085385 | Gao et al. | Mar 2016 | A1 |
| 20160092071 | Lawson et al. | Mar 2016 | A1 |
| 20160124924 | Greenberg et al. | May 2016 | A1 |
| 20160125234 | Ota et al. | May 2016 | A1 |
| 20160132139 | Du et al. | May 2016 | A1 |
| 20160188181 | Smith | Jun 2016 | A1 |
| 20160188186 | Yea | Jun 2016 | A1 |
| 20160196028 | Kenney et al. | Jul 2016 | A1 |
| 20160210025 | Bernstein et al. | Jul 2016 | A1 |
| 20160246478 | Davis et al. | Aug 2016 | A1 |
| 20160259412 | Flint et al. | Sep 2016 | A1 |
| 20160259413 | Anzures et al. | Sep 2016 | A1 |
| 20160259495 | Butcher et al. | Sep 2016 | A1 |
| 20160259496 | Butcher et al. | Sep 2016 | A1 |
| 20160259498 | Foss et al. | Sep 2016 | A1 |
| 20160259499 | Kocienda et al. | Sep 2016 | A1 |
| 20160259516 | Kudurshian et al. | Sep 2016 | A1 |
| 20160259517 | Butcher et al. | Sep 2016 | A1 |
| 20160259518 | King et al. | Sep 2016 | A1 |
| 20160259519 | Foss et al. | Sep 2016 | A1 |
| 20160259527 | Kocienda et al. | Sep 2016 | A1 |
| 20160259528 | Foss et al. | Sep 2016 | A1 |
| 20160259536 | Kudurshian et al. | Sep 2016 | A1 |
| 20160259548 | Ma | Sep 2016 | A1 |
| 20160274686 | Ruiz et al. | Sep 2016 | A1 |
| 20160274728 | Luo et al. | Sep 2016 | A1 |
| 20160274761 | Ruiz et al. | Sep 2016 | A1 |
| 20160283054 | Suzuki | Sep 2016 | A1 |
| 20160306507 | Defazio et al. | Oct 2016 | A1 |
| 20160320906 | Bokma et al. | Nov 2016 | A1 |
| 20160357368 | Federighi et al. | Dec 2016 | A1 |
| 20160357389 | Dakin et al. | Dec 2016 | A1 |
| 20160357390 | Federighi et al. | Dec 2016 | A1 |
| 20160357404 | Alonso Ruiz et al. | Dec 2016 | A1 |
| 20160360116 | Penha et al. | Dec 2016 | A1 |
| 20170045981 | Karunamuni et al. | Feb 2017 | A1 |
| 20170046039 | Karunamuni et al. | Feb 2017 | A1 |
| 20170046058 | Karunamuni et al. | Feb 2017 | A1 |
| 20170046059 | Karunamuni et al. | Feb 2017 | A1 |
| 20170046060 | Karunamuni et al. | Feb 2017 | A1 |
| 20170075520 | Bauer et al. | Mar 2017 | A1 |
| 20170075562 | Bauer et al. | Mar 2017 | A1 |
| 20170075563 | Bauer et al. | Mar 2017 | A1 |
| 20170090617 | Jang et al. | Mar 2017 | A1 |
| 20170090699 | Pennington et al. | Mar 2017 | A1 |
| 20170091153 | Thimbleby | Mar 2017 | A1 |
| 20170109011 | Jiang | Apr 2017 | A1 |
| 20170115867 | Bargmann | Apr 2017 | A1 |
| 20170123497 | Yonezawa | May 2017 | A1 |
| 20170124699 | Lane | May 2017 | A1 |
| 20170139565 | Choi | May 2017 | A1 |
| 20170315694 | Alonso Ruiz et al. | Nov 2017 | A1 |
| 20170357403 | Geary et al. | Dec 2017 | A1 |
| 20180024681 | Bernstein et al. | Jan 2018 | A1 |
| 20180059866 | Drake et al. | Mar 2018 | A1 |
| 20180082522 | Bartosik | Mar 2018 | A1 |
| 20180188920 | Bernstein et al. | Jul 2018 | A1 |
| 20180342103 | Schwartz et al. | Nov 2018 | A1 |
| 20180349362 | Sharp et al. | Dec 2018 | A1 |
| 20180364898 | Chen | Dec 2018 | A1 |
| 20190012059 | Kwon et al. | Jan 2019 | A1 |
| 20190018562 | Bernstein et al. | Jan 2019 | A1 |
| 20190042075 | Bernstein et al. | Feb 2019 | A1 |
| 20190042078 | Bernstein et al. | Feb 2019 | A1 |
| 20190065043 | Zambetti et al. | Feb 2019 | A1 |
| 20190121493 | Bernstein et al. | Apr 2019 | A1 |
| 20190121520 | Cieplinski et al. | Apr 2019 | A1 |
| 20190138101 | Bernstein | May 2019 | A1 |
| 20190138102 | Missig | May 2019 | A1 |
| 20190138189 | Missig | May 2019 | A1 |
| 20190146643 | Foss et al. | May 2019 | A1 |
| 20190155503 | Alonso Ruiz et al. | May 2019 | A1 |
| 20190158727 | Penha et al. | May 2019 | A1 |
| 20190163358 | Dascola et al. | May 2019 | A1 |
| 20190171353 | Missig et al. | Jun 2019 | A1 |
| 20190171354 | Dascola et al. | Jun 2019 | A1 |
| 20190212896 | Karunamuni et al. | Jul 2019 | A1 |
| 20190332257 | Kudurshian et al. | Oct 2019 | A1 |
| 20190364194 | Penha et al. | Nov 2019 | A1 |
| 20190391658 | Missig et al. | Dec 2019 | A1 |
| 20200081614 | Zambetti | Mar 2020 | A1 |
| 20200142548 | Karunamuni et al. | May 2020 | A1 |
| 20200201472 | Bernstein et al. | Jun 2020 | A1 |
| 20200210059 | Hu et al. | Jul 2020 | A1 |
| 20200218445 | Alonso Ruiz et al. | Jul 2020 | A1 |
| 20200301556 | Alonso Ruiz et al. | Sep 2020 | A1 |
| 20200333936 | Khoe et al. | Oct 2020 | A1 |
| 20200371683 | Zambetti et al. | Nov 2020 | A1 |
| 20200394413 | Bhanu et al. | Dec 2020 | A1 |
| 20200396375 | Penha et al. | Dec 2020 | A1 |
| 20210081082 | Dascola et al. | Mar 2021 | A1 |
| 20210117054 | Karunamuni et al. | Apr 2021 | A1 |
| 20210191602 | Brown et al. | Jun 2021 | A1 |
| 20210191975 | Lu et al. | Jun 2021 | A1 |
| 20210311598 | Bernstein et al. | Oct 2021 | A1 |
| 20210326039 | Alonso Ruiz et al. | Oct 2021 | A1 |
| 20210382613 | Kudurshian et al. | Dec 2021 | A1 |
| 20220011932 | Khoe et al. | Jan 2022 | A1 |
| 20220070359 | Clarke et al. | Mar 2022 | A1 |
| 20220129076 | Bernstein et al. | Apr 2022 | A1 |
| 20220261131 | Bernstein et al. | Aug 2022 | A1 |
| 20220365671 | Bernstein et al. | Nov 2022 | A1 |
| 20230133870 | Penha et al. | May 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 2780765 | May 2011 | CA |
| 1356493 | Jul 2002 | CN |
| 1534991 | Jun 2004 | CN |
| 1620327 | May 2005 | CN |
| 1808362 | Jul 2006 | CN |
| 101068310 | Jul 2007 | CN |
| 101118469 | Feb 2008 | CN |
| 101192097 | Jun 2008 | CN |
| 101202866 | Jun 2008 | CN |
| 101222704 | Jul 2008 | CN |
| 101227764 | Jul 2008 | CN |
| 101241397 | Aug 2008 | CN |
| 101320303 | Dec 2008 | CN |
| 101356493 | Jan 2009 | CN |
| 101384977 | Mar 2009 | CN |
| 101390039 | Mar 2009 | CN |
| 101421707 | Apr 2009 | CN |
| 101464777 | Jun 2009 | CN |
| 101498979 | Aug 2009 | CN |
| 101526876 | Sep 2009 | CN |
| 101527745 | Sep 2009 | CN |
| 101562703 | Oct 2009 | CN |
| 101593077 | Dec 2009 | CN |
| 101609380 | Dec 2009 | CN |
| 101620507 | Jan 2010 | CN |
| 101627359 | Jan 2010 | CN |
| 101630230 | Jan 2010 | CN |
| 101685370 | Mar 2010 | CN |
| 101692194 | Apr 2010 | CN |
| 101727179 | Jun 2010 | CN |
| 101739206 | Jun 2010 | CN |
| 101763193 | Jun 2010 | CN |
| 101784981 | Jul 2010 | CN |
| 101809526 | Aug 2010 | CN |
| 101896962 | Nov 2010 | CN |
| 101937304 | Jan 2011 | CN |
| 101945212 | Jan 2011 | CN |
| 101971603 | Feb 2011 | CN |
| 101998052 | Mar 2011 | CN |
| 102004575 | Apr 2011 | CN |
| 102004576 | Apr 2011 | CN |
| 102004577 | Apr 2011 | CN |
| 102004593 | Apr 2011 | CN |
| 102004602 | Apr 2011 | CN |
| 102004604 | Apr 2011 | CN |
| 102016777 | Apr 2011 | CN |
| 102053790 | May 2011 | CN |
| 102067068 | May 2011 | CN |
| 102112946 | Jun 2011 | CN |
| 102150018 | Aug 2011 | CN |
| 102160021 | Aug 2011 | CN |
| 102171629 | Aug 2011 | CN |
| 102195514 | Sep 2011 | CN |
| 102203702 | Sep 2011 | CN |
| 102214038 | Oct 2011 | CN |
| 102223476 | Oct 2011 | CN |
| 102243662 | Nov 2011 | CN |
| 102257460 | Nov 2011 | CN |
| 102301322 | Dec 2011 | CN |
| 102349038 | Feb 2012 | CN |
| 102349040 | Feb 2012 | CN |
| 102354269 | Feb 2012 | CN |
| 102365666 | Feb 2012 | CN |
| 102375605 | Mar 2012 | CN |
| 102385478 | Mar 2012 | CN |
| 102388351 | Mar 2012 | CN |
| 102438092 | May 2012 | CN |
| 102483666 | May 2012 | CN |
| 102483677 | May 2012 | CN |
| 102546925 | Jul 2012 | CN |
| 102566908 | Jul 2012 | CN |
| 102576251 | Jul 2012 | CN |
| 102576282 | Jul 2012 | CN |
| 102625931 | Aug 2012 | CN |
| 102646013 | Aug 2012 | CN |
| 102662571 | Sep 2012 | CN |
| 102662573 | Sep 2012 | CN |
| 102722312 | Oct 2012 | CN |
| 102752441 | Oct 2012 | CN |
| 102792255 | Nov 2012 | CN |
| 102819331 | Dec 2012 | CN |
| 102819401 | Dec 2012 | CN |
| 102841677 | Dec 2012 | CN |
| 102880417 | Jan 2013 | CN |
| 103019586 | Apr 2013 | CN |
| 103092386 | May 2013 | CN |
| 103092406 | May 2013 | CN |
| 103097992 | May 2013 | CN |
| 103139473 | Jun 2013 | CN |
| 103186345 | Jul 2013 | CN |
| 103201714 | Jul 2013 | CN |
| 103268184 | Aug 2013 | CN |
| 103279295 | Sep 2013 | CN |
| 103390017 | Nov 2013 | CN |
| 103518176 | Jan 2014 | CN |
| 103562841 | Feb 2014 | CN |
| 103581544 | Feb 2014 | CN |
| 103620531 | Mar 2014 | CN |
| 103649885 | Mar 2014 | CN |
| 103699292 | Apr 2014 | CN |
| 103699295 | Apr 2014 | CN |
| 103777850 | May 2014 | CN |
| 103777886 | May 2014 | CN |
| 103793134 | May 2014 | CN |
| 103838465 | Jun 2014 | CN |
| 103870190 | Jun 2014 | CN |
| 103888661 | Jun 2014 | CN |
| 103970474 | Aug 2014 | CN |
| 103984501 | Aug 2014 | CN |
| 104011637 | Aug 2014 | CN |
| 104020868 | Sep 2014 | CN |
| 104020955 | Sep 2014 | CN |
| 104021021 | Sep 2014 | CN |
| 104024985 | Sep 2014 | CN |
| 104038838 | Sep 2014 | CN |
| 104049861 | Sep 2014 | CN |
| 104077014 | Oct 2014 | CN |
| 104090979 | Oct 2014 | CN |
| 104142798 | Nov 2014 | CN |
| 104160362 | Nov 2014 | CN |
| 104205098 | Dec 2014 | CN |
| 104238904 | Dec 2014 | CN |
| 104267902 | Jan 2015 | CN |
| 104270565 | Jan 2015 | CN |
| 104331239 | Feb 2015 | CN |
| 104349124 | Feb 2015 | CN |
| 104392292 | Mar 2015 | CN |
| 104412201 | Mar 2015 | CN |
| 104471521 | Mar 2015 | CN |
| 104487928 | Apr 2015 | CN |
| 104487929 | Apr 2015 | CN |
| 104487930 | Apr 2015 | CN |
| 105264476 | Jan 2016 | CN |
| 100 59 906 | Jun 2002 | DE |
| O 364178 | Apr 1990 | EP |
| 0 859 307 | Mar 1998 | EP |
| 0 880 090 | Nov 1998 | EP |
| 1 028 583 | Aug 2000 | EP |
| 1 406 150 | Apr 2004 | EP |
| 1 674 977 | Jun 2006 | EP |
| 1 882 902 | Jan 2008 | EP |
| 2 000 896 | Dec 2008 | EP |
| 2 017 701 | Jan 2009 | EP |
| 2 028 583 | Feb 2009 | EP |
| 2 112 586 | Oct 2009 | EP |
| 2 141 574 | Jan 2010 | EP |
| 2 175 357 | Apr 2010 | EP |
| 2 196 893 | Jun 2010 | EP |
| 2 214 087 | Aug 2010 | EP |
| 2 226 715 | Sep 2010 | EP |
| 2 284 675 | Feb 2011 | EP |
| 2 299 351 | Mar 2011 | EP |
| 2 302 496 | Mar 2011 | EP |
| 2 363 790 | Sep 2011 | EP |
| 2 375 309 | Oct 2011 | EP |
| 2 375 314 | Oct 2011 | EP |
| 2 386 935 | Nov 2011 | EP |
| 2 407 868 | Jan 2012 | EP |
| 2 420 924 | Feb 2012 | EP |
| 2 426 580 | Mar 2012 | EP |
| 2 445 182 | Apr 2012 | EP |
| 2 447 818 | May 2012 | EP |
| 2 527 966 | Nov 2012 | EP |
| 2 530 677 | Dec 2012 | EP |
| 2 541 376 | Jan 2013 | EP |
| 2 555 500 | Feb 2013 | EP |
| 2 615 535 | Jul 2013 | EP |
| 2 631 737 | Aug 2013 | EP |
| 2 674 834 | Dec 2013 | EP |
| 2 674 846 | Dec 2013 | EP |
| 2 708985 | Mar 2014 | EP |
| 2 733 578 | May 2014 | EP |
| 2 808 764 | Dec 2014 | EP |
| 2 809 058 | Dec 2014 | EP |
| 2 813 938 | Dec 2014 | EP |
| 3 664 092 | Jun 2020 | EP |
| 2 402 105 | Dec 2004 | GB |
| 58-182746 | Oct 1983 | JP |
| H06-161647 | Jun 1994 | JP |
| H07-098769 | Apr 1995 | JP |
| H07-104915 | Apr 1995 | JP |
| H07-151512 | Jun 1995 | JP |
| H08-227341 | Sep 1996 | JP |
| H09-269883 | Oct 1997 | JP |
| H09-330175 | Dec 1997 | JP |
| H11-203044 | Jul 1999 | JP |
| 2001-078137 | Mar 2001 | JP |
| 2001-202192 | Jul 2001 | JP |
| 2001-222355 | Aug 2001 | JP |
| 2001-306207 | Nov 2001 | JP |
| 2002-044536 | Feb 2002 | JP |
| 2002-149312 | May 2002 | JP |
| 3085481 | May 2002 | JP |
| 2002-182855 | Jun 2002 | JP |
| 2003-157131 | May 2003 | JP |
| 2003-186597 | Jul 2003 | JP |
| 2004-054861 | Feb 2004 | JP |
| 2004-062648 | Feb 2004 | JP |
| 2004-070492 | Mar 2004 | JP |
| 2004-078957 | Mar 2004 | JP |
| 2004-086733 | Mar 2004 | JP |
| 2004-120576 | Apr 2004 | JP |
| 2004-152217 | May 2004 | JP |
| 2004-288208 | Oct 2004 | JP |
| 2005-031786 | Feb 2005 | JP |
| 2005-092386 | Apr 2005 | JP |
| 2005-102106 | Apr 2005 | JP |
| 2005-135106 | May 2005 | JP |
| 2005-157842 | Jun 2005 | JP |
| 2005-196810 | Jul 2005 | JP |
| 2005-317041 | Nov 2005 | JP |
| 2005-352927 | Dec 2005 | JP |
| 2006-059238 | Mar 2006 | JP |
| 2006-185443 | Jul 2006 | JP |
| 2007-116384 | May 2007 | JP |
| 2007-148104 | Jun 2007 | JP |
| 2007-264808 | Oct 2007 | JP |
| 2008-009759 | Jan 2008 | JP |
| 2008-015890 | Jan 2008 | JP |
| 2008-033739 | Feb 2008 | JP |
| 2008-516348 | May 2008 | JP |
| 2008-146453 | Jun 2008 | JP |
| 2008-191086 | Aug 2008 | JP |
| 2008-537615 | Sep 2008 | JP |
| 2008-305174 | Dec 2008 | JP |
| 2009-500761 | Jan 2009 | JP |
| 2009-110243 | May 2009 | JP |
| 2009-129171 | Jun 2009 | JP |
| 2009-129443 | Jun 2009 | JP |
| 2009-169452 | Jul 2009 | JP |
| 2009-211704 | Sep 2009 | JP |
| 2009-217543 | Sep 2009 | JP |
| 2009-294688 | Dec 2009 | JP |
| 2009-545805 | Dec 2009 | JP |
| 2010-009321 | Jan 2010 | JP |
| 2010-503126 | Jan 2010 | JP |
| 2010-503130 | Jan 2010 | JP |
| 2010-055274 | Mar 2010 | JP |
| 2010-097353 | Apr 2010 | JP |
| 2010-146507 | Jul 2010 | JP |
| 2010-152716 | Jul 2010 | JP |
| 2010-176174 | Aug 2010 | JP |
| 2010-176337 | Aug 2010 | JP |
| 2010-181934 | Aug 2010 | JP |
| 2010-181940 | Aug 2010 | JP |
| 2010-198385 | Sep 2010 | JP |
| 2010-536077 | Nov 2010 | JP |
| 2010-541071 | Dec 2010 | JP |
| 2011-501307 | Jan 2011 | JP |
| 2011-028635 | Feb 2011 | JP |
| 2011-048023 | Mar 2011 | JP |
| 2011-048666 | Mar 2011 | JP |
| 2011-048686 | Mar 2011 | JP |
| 2011-048762 | Mar 2011 | JP |
| 2011-048832 | Mar 2011 | JP |
| 2011-053831 | Mar 2011 | JP |
| 2011-053972 | Mar 2011 | JP |
| 2011-053973 | Mar 2011 | JP |
| 2011-053974 | Mar 2011 | JP |
| 2011-054196 | Mar 2011 | JP |
| 2011-059821 | Mar 2011 | JP |
| 2011-070342 | Apr 2011 | JP |
| 2011-100290 | May 2011 | JP |
| 2011-107823 | Jun 2011 | JP |
| 2011-123773 | Jun 2011 | JP |
| 2011-141868 | Jul 2011 | JP |
| 2011-170538 | Sep 2011 | JP |
| 2011-192179 | Sep 2011 | JP |
| 2011-192215 | Sep 2011 | JP |
| 2011-197848 | Oct 2011 | JP |
| 2011-221640 | Nov 2011 | JP |
| 2011-232947 | Nov 2011 | JP |
| 2011-242386 | Dec 2011 | JP |
| 2011-250004 | Dec 2011 | JP |
| 2011-253556 | Dec 2011 | JP |
| 2011-257941 | Dec 2011 | JP |
| 2011-530101 | Dec 2011 | JP |
| 2012-027940 | Feb 2012 | JP |
| 2012-033061 | Feb 2012 | JP |
| 2012-043266 | Mar 2012 | JP |
| 2012-043267 | Mar 2012 | JP |
| 2012-053687 | Mar 2012 | JP |
| 2012-053754 | Mar 2012 | JP |
| 2012-053926 | Mar 2012 | JP |
| 2012-073785 | Apr 2012 | JP |
| 2012-073873 | Apr 2012 | JP |
| 2012-509605 | Apr 2012 | JP |
| 2012-093820 | May 2012 | JP |
| 2012-118825 | Jun 2012 | JP |
| 2012-118993 | Jun 2012 | JP |
| 2012-123564 | Jun 2012 | JP |
| 2012-128825 | Jul 2012 | JP |
| 2012-168620 | Sep 2012 | JP |
| 2012-212473 | Nov 2012 | JP |
| 2012-527685 | Nov 2012 | JP |
| 2013-025357 | Feb 2013 | JP |
| 2013-030050 | Feb 2013 | JP |
| 2013-058149 | Mar 2013 | JP |
| 2013-077270 | Apr 2013 | JP |
| 2013-080521 | May 2013 | JP |
| 2013-093020 | May 2013 | JP |
| 2013-101465 | May 2013 | JP |
| 2013-105410 | May 2013 | JP |
| 2013-520727 | Jun 2013 | JP |
| 2013-131185 | Jul 2013 | JP |
| 2013-529339 | Jul 2013 | JP |
| 2013-200879 | Oct 2013 | JP |
| 2013-236298 | Nov 2013 | JP |
| 2013-542488 | Nov 2013 | JP |
| 2013-250602 | Dec 2013 | JP |
| 2014-504419 | Feb 2014 | JP |
| 2014-052852 | Mar 2014 | JP |
| 2014-130567 | Jul 2014 | JP |
| 2014-140112 | Jul 2014 | JP |
| 2014-149833 | Aug 2014 | JP |
| 2014-519109 | Aug 2014 | JP |
| 2014-529137 | Oct 2014 | JP |
| 2014-232347 | Dec 2014 | JP |
| 2015-099555 | May 2015 | JP |
| 2015-521315 | Jul 2015 | JP |
| 2015-153420 | Aug 2015 | JP |
| 2015-185161 | Oct 2015 | JP |
| 20020041828 | Jun 2002 | KR |
| 2006-0071353 | Jun 2006 | KR |
| 2006-0117870 | Nov 2006 | KR |
| 100807738 | Feb 2008 | KR |
| 20080026138 | Mar 2008 | KR |
| 2008-0045143 | Apr 2008 | KR |
| 100823871 | Apr 2008 | KR |
| 2008-0054346 | Jun 2008 | KR |
| 2009-0066319 | Jun 2009 | KR |
| 2009-0108065 | Oct 2009 | KR |
| 2010-0010860 | Feb 2010 | KR |
| 2010-0014095 | Feb 2010 | KR |
| 2010 0133246 | Dec 2010 | KR |
| 2011 0026176 | Mar 2011 | KR |
| 2011 0086501 | Jul 2011 | KR |
| 20120130972 | Jan 2012 | KR |
| 2012 0103670 | Sep 2012 | KR |
| 20120135488 | Dec 2012 | KR |
| 20120135723 | Dec 2012 | KR |
| 20130027017 | Mar 2013 | KR |
| 20130076397 | Jul 2013 | KR |
| 2013 0099647 | Sep 2013 | KR |
| 2014 0016495 | Feb 2014 | KR |
| 2014 0029720 | Mar 2014 | KR |
| 2014 0043760 | Apr 2014 | KR |
| 2014 0067965 | Jun 2014 | KR |
| 2014 0079110 | Jun 2014 | KR |
| 2014 0122000 | Oct 2014 | KR |
| 20150013263 | Feb 2015 | KR |
| 20150021977 | Mar 2015 | KR |
| 2007145218 | Jul 2009 | RU |
| 2503989 | Jan 2014 | RU |
| 201447740 | Dec 2014 | TW |
| WO 2005106637 | Nov 2005 | WO |
| WO 2006013485 | Feb 2006 | WO |
| WO 2006042309 | Apr 2006 | WO |
| WO 2006094308 | Sep 2006 | WO |
| WO 2007121557 | Nov 2007 | WO |
| WO 2008030976 | Mar 2008 | WO |
| WO 2008064142 | May 2008 | WO |
| WO 2009155981 | Dec 2009 | WO |
| WO 2009158549 | Dec 2009 | WO |
| WO 2010013876 | Feb 2010 | WO |
| WO 2010032598 | Mar 2010 | WO |
| WO 2010090010 | Aug 2010 | WO |
| WO 2010122813 | Oct 2010 | WO |
| WO 2010134729 | Nov 2010 | WO |
| WO 2011024389 | Mar 2011 | WO |
| WO 2011024465 | Mar 2011 | WO |
| WO 2011024521 | Mar 2011 | WO |
| WO 2011093045 | Aug 2011 | WO |
| WO 2011105009 | Sep 2011 | WO |
| WO 2011108190 | Sep 2011 | WO |
| WO 2011115187 | Sep 2011 | WO |
| WO 2011121375 | Oct 2011 | WO |
| WO 2012021417 | Feb 2012 | WO |
| WO 2012037664 | Mar 2012 | WO |
| WO 2012096804 | Jul 2012 | WO |
| WO 2012108213 | Aug 2012 | WO |
| WO 2012114760 | Aug 2012 | WO |
| WO 2012137946 | Oct 2012 | WO |
| WO 2012150540 | Nov 2012 | WO |
| WO 2012153555 | Nov 2012 | WO |
| WO 2013022486 | Feb 2013 | WO |
| WO 2013035725 | Mar 2013 | WO |
| WO 2013112453 | Aug 2013 | WO |
| WO 2013127055 | Sep 2013 | WO |
| WO 2013169302 | Nov 2013 | WO |
| WO 2013169845 | Nov 2013 | WO |
| WO 2013169846 | Nov 2013 | WO |
| WO 2013169849 | Nov 2013 | WO |
| WO 2013169851 | Nov 2013 | WO |
| WO 2013169853 | Nov 2013 | WO |
| WO 2013169854 | Nov 2013 | WO |
| WO 2013169870 | Nov 2013 | WO |
| WO 2013169875 | Nov 2013 | WO |
| WO 2013169877 | Nov 2013 | WO |
| WO 2013169882 | Nov 2013 | WO |
| WO 2013173838 | Nov 2013 | WO |
| WO 2014034706 | Mar 2014 | WO |
| WO 2014105275 | Jul 2014 | WO |
| WO 2014105276 | Jul 2014 | WO |
| WO 2014105277 | Jul 2014 | WO |
| WO 2014105278 | Jul 2014 | WO |
| WO 2014105279 | Jul 2014 | WO |
| WO 2014129655 | Aug 2014 | WO |
| WO 2014149473 | Sep 2014 | WO |
| WO 2014152601 | Sep 2014 | WO |
| WO 2014200733 | Dec 2014 | WO |
| WO 2016200584 | Dec 2016 | WO |
| Entry |
|---|
| Microsoft, “Windows 7 Aero Shake, Snap, and Peek”, hr.msu.edu.techtipshrsds/window 7 snappeekandshake.pdf, Apr. 4, 2012, 6 pages. |
| Patent, dated Jul. 13, 2022, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
| Decision to Grant, dated Jul. 21, 2022, received in European Patent Application No. 18183789.9, which corresponds with U.S. Appl. No. 16/262,800, 3 pages. |
| Patent, dated Aug. 17, 2022, received in European Patent Application No. 18183789.9, which corresponds with U.S. Appl. No. 16/262,800, 4 pages. |
| Office Action, dated Jul. 29, 2022, received in Indian Patent Application No. 202118007136, which corresponds with U.S. Appl. No. 14/866,511, 9 pages. |
| Office Action, dated Aug. 23, 2022, received in European Patent Application No. 19194418.0, which corresponds with U.S. Appl. No. 14/864,580, 6 pages. |
| Intention to Grant, dated Sep. 26, 2022, received in European Patent Application No. 16753795.0, which corresponds with U.S. Appl. No. 15/009,668, 7 pages. |
| Notice of Allowance, dated Oct. 14, 2022, received in Japanese Patent Application No. 2021-157204, which corresponds with U.S. Appl. No. 15/272,327, 2 pages. |
| Office Action, dated Jul. 25, 2022, received in Japanese Patent Application No. 2021-099049, which corresponds with U.S. Appl. No. 16/243,834, 2 pages. |
| Office Action, dated Jul. 18, 2022, received in Mexican Patent Application No. MX/a/2020/011482, which corresponds with U.S. Appl. No. 16/243,834, 4 pages. |
| Patent, dated Jun. 14, 2022, received in Japanese Patent Application No. 2020-174097, which corresponds with U.S. Appl. No. 16/241,883, 3 pages. |
| Office Action, dated Oct. 3, 2022, received in Japanese Patent Application No. 2021-132350, which corresponds with U.S. Appl. No. 16/258,394, 2 pages. |
| Final Office Action, dated Sep. 16, 2022, received in Japanese Patent Application No. 2019-047319, which corresponds with U.S. Appl. No. 16/896,141, 2 pages. |
| Office Action, dated Jul. 18, 2022, received in Chinese Patent Application No. 201910718931.8, 2 pages. |
| Final Office Action, dated Jul. 18, 2022, received in U.S. Appl. No. 16/685,773, 20 pages. |
| Notice of Allowance, dated Aug. 23, 2022, received in Australian Patent Application No. 2020257134, 2 pages. |
| Notice of Allowance, dated Oct. 18, 2022, received in Korean Patent Application No. 2022-7005994, 5 pages. |
| Office Action, dated Aug. 19, 2022, received in U.S. Appl. No. 17/103,899 24 pages. |
| Office Action, dated Nov. 11, 2021, received in Australian Patent Application No. 2021200655, which corresponds with U.S. Appl. No. 17/103,899, 4 pages. |
| Office Action, dated Nov. 8, 2022, received in U.S. Appl. No. 17/333,810, 9 pages. |
| Notice of Allowance, dated Aug. 24, 2022, received in U.S. Appl. No. 17/362,852, 9 pages. |
| Office Action, dated Nov. 9, 2022, received in U.S. Appl. No. 17/409,573, 20 pages. |
| Notice of Allowance, dated Sep. 22, 2022, received in U.S. Appl. No. 17/524,692, 22 pages. |
| Patent, dated Aug. 10, 2022, received in Korean Patent Application No. 2022-7015718, 6 pages. |
| Intent to Grant, dated Jan. 9, 2023, received in European Patent Application No. 16711725.8, which corresponds with U.S. Appl. No. 14/867,990, 7 pages. |
| Decision to Grant, dated Nov. 24, 2022, received in European Patent Application No. 16753795.0, which corresponds with U.S. Appl. No. 15/009,668, 4 pages. |
| Patent, dated Dec. 21, 2023, received in European Patent Application No. 16753795.0, which corresponds with U.S. Appl. No. 15/009,668, 4 pages. |
| Notice of Allowance, dated Jan. 20, 2023, received in Japanese Patent Application No. 2019-058800, which corresponds with U.S. Appl. No. 16/243,834, 2 pages. |
| Office Action, dated Jan. 5, 2023, received in Mexican Patent Application No. MX/a/2020/011482, which corresponds with U.S. Appl. No. 16/243,834, 5 pages. |
| Final Office Action, dated Feb. 24, 2023, received in U.S. Appl. No. 16/896,141, 23 pages. |
| Patent, dated Nov. 25, 2022, received in Chinese Patent Application No. 201910610331.X, 7 pages. |
| Notice of Allowance, dated Jan. 5, 2023, received in Chinese Patent Application No. 201910718931.8, 4 pages. |
| Office Action, dated Dec. 16, 2022, received in Australian Patent Application No. 2022200212, 3 pages. |
| Notice of Allowance, dated Nov. 23, 2022, received in Korean Patent Application No. 2020-7008888, 2 pages. |
| Office Action, dated Jan. 5, 2023, received in Japanese Patent Application No. 2022-031194, which corresponds with U.S. Appl. No. 17/003,869, 6 pages. |
| Patent, dated Dec. 22, 2022, received in Australian Patent Application No. 2020257134, 3 pages. |
| Final Office Action, dated Jan. 24, 2023, received in U.S. Appl. No. 17/103,899 27 pages. |
| Notice of Acceptance, dated Nov. 10, 2022, received in Australian Patent Application No. 2021200655, which corresponds with U.S. Appl. No. 17/103,899, 4 pages. |
| Office Action, dated Jan. 11, 2023, received in Australian Patent Application No. 2022202892, which corresponds with U.S. Appl. No. 15/113,779, 3 pages. |
| Office Action, dated Nov. 28, 2022, received in U.S. Appl. No. 17/560,013, 13 pages. |
| Office Action, dated Feb. 16, 2023, received in U.S. Appl. No. 17/728,909, 12 pages. |
| Notice of Allowance, dated Mar. 21, 2022, received in Chinese Patent Application No. 201810332044.2, which corresponds with U.S. Appl. No. 14/536,267, 1 page. |
| Intent to Grant, dated Mar. 16, 2022, received in European Patent Application No. 18183789.9, which corresponds with U.S. Appl. No. 16/262,800, 7 pages. |
| Patent, dated Mar. 3, 2022, received in Japanese Patent Application No. 2020-185336, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Patent, dated Mar. 8, 2022, received in Chinese Patent Application No. 201610869950.7, which corresponds with U.S. Appl. No. 14/871,462, 7 pages. |
| Office Action, dated Apr. 11, 2022, received in Japanese Patent Application No. 2019-058800, which corresponds with U.S. Appl. No. 16/243,834, 4 pages. |
| Final Office Action, dated Mar. 4, 2022, received in Japanese Patent Application No. 2019-047319, which corresponds with U.S. Appl. No. 16/896,141, 2 pages. |
| Office Action, dated Mar. 17, 2022, received in Chinese Patent Application No. 201910718931.8, 1 page. |
| Office Action, dated Mar. 16, 2022, received in U.S. Appl. No. 17/138,676, 22 pages. |
| Bognot, “Microsoft Windows 7 Aero Shake, Snap, and Peek”, https://www.outube.com/watch?v=vgD7wGrsQg4, Apr. 3, 2012, 4 pages. |
| Intent to Grant, dated May 11, 2022, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 7 pages. |
| Decision to Grant, dated Jun. 17, 2022, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 7 pages. |
| Patent, dated May 27, 2022, received in Chinese Patent Application No. 201810332044.2, which corresponds with U.S. Appl. No. 14/536,267, 6 pages. |
| Decision on Appeal, dated Jun. 9, 2022, received in U.S. Appl. No. 14/609,006, 11 pages. |
| Office Action, dated Mar. 2, 2022, received in Chinese Patent Application No. 201811561188.2, which corresponds with U.S. Appl. No. 15/081,771, 1 page. |
| Office Action, dated Jun. 7, 2022, received in European Patent Application No. 20188553.0, which corresponds with U.S. Appl. No. 15/499,693, 7 pages. |
| Notice of Allowance, dated Apr. 14, 2022, received in Russian Patent Application No. 2018146112, which corresponds with U.S. Appl. No. 16/243,834, 2 pages. |
| Certificate of Grant, dated Apr. 21, 2022, received in Australian Patent Application No. 2020201648, which corresponds with U.S. Appl. No. 16/262,784, 3 pages. |
| Patent, dated May 19, 2022, received in Australian Patent Application No. 2020267298, which corresponds with U.S. Appl. No. 16/258,394, 4 pages. |
| Office Action, dated May 6, 2022, received in Chinese Patent Application No. 201910610331.X, 5 pages. |
| Office Action, dated May 17, 2022, received in Korean Patent Application No. 2020-7008888, 2 pages. |
| Patent, dated May 19, 2022, received in Australian Patent Application No. 2020244406, which corresponds with U.S. Appl. No. 17/003,869, 3 pages. |
| Notice of Allowance, dated Feb. 7, 2022, received in U.S. Appl. No. 16/988,509, 16 pages. |
| Office Action, dated Apr. 27, 2022, received in Australian Patent Application No. 2020257134, 3 pages. |
| Office Action, dated Apr. 28, 2022, received in Korean Patent Application No. 2022-7005994, 5 pages. |
| Final Office Action, dated May 2, 2022, received in U.S. Appl. No. 17/103,899 21 pages. |
| Office Action, dated Jun. 10, 2022, received in U.S. Appl. No. 17/362,852, 12 pages. |
| Patent, dated May 10, 2022, received in Korean Patent Application No. 2022-7003345, 8 pages. |
| Office Action, dated May 23, 2022, received in Korean Patent Application No. 2022-7015718, 2 pages. |
| Agarwal, “How to Copy and Paste Text on Windows Phone 8,” Guiding Tech, http://web.archive.org/web20130709204246/http://www.guidingtech.com/20280/copy-paste-text-windows-phone-8/, Jul. 9, 2013, 10 pages. |
| Angelov, “Sponsor Flip Wall with Jquery & CSS”, Tutorialzine. N.p., Mar. 24, 2010. Web. http://tutorialzine.com/2010/03/sponsor-wall-slip-jquery-css/, Mar. 24, 2010, 8 pages. |
| Anonymous, “1-Click Installer for Windows Media Taskbar Mini-Player for Windows 7, 8, 8.1 10”, http://metadataconsulting.blogspot.de/2014/05/installer-for-windows-media-taskbar.htm, May 5, 2014, 6 pages. |
| Anonymous, “Acer Liquid Z5 Duo User's Manual”, https://global-download.acer.com, Feb. 21, 2014, 65 pages. |
| Anonymous, “Android—What Should Status Bar Toggle Button Behavior Be?”, https://ux.stackechange.com/questions/34814, Jan. 15, 2015, 2 pages. |
| Anonymous, “Google Android 5.0 Release Date, Specs and Editors Hands on Review—CNET”, http://www.cnet.com/products/google-an-android-5-0-lollipop/, Mar. 12, 2015, 10 pages. |
| Anonymous, “How Do I Add Contextual Menu to My Apple Watch App?”, http://www.tech-recipes.com/rx/52578/how-do-i-add-contextual-menu-to-my-apple-watch-app, Jan. 13, 2015, 3 pages. |
| Anonymous, “[new] WMP12 with Taskbar Toolbar for Windows 7—Windows Customization—WinMatrix”, http://www.winmatrix.com/forums/index/php?/topic/25528-new-wmp12-with-taskbar-toolbar-for-windows-7, Jan. 27, 2013, 6 pages. |
| Anonymous, “Nokia 808 PureView screenshots”, retrieved from Internet; no URL, Nov. 12, 2012, 8 pages. |
| Anonymous, “Nokia 808 PureView User Guide,” http://download-fds.webapps.microsoft.com/supportFiles/phones/files/pdf_guides/devices/808/Nokia_808_UG_en_APAC.pdf, Jan. 1, 2012, 144 pages. |
| Anonymous, “Notifications, Android 4.4 and Lower”, Android Developers, https://developer.android.com/design/patterns/notifications_k.html, May 24, 2015, 9 pages. |
| Anonymous, RX-V3800AV Receiver Owner's Manual, Yamaha Music Manuals, www.Manualslib.com, Dec. 31, 2007, 169 pages. |
| Anonymous, “Taskbar Extensions”, https://web.archive.org/web/20141228124434/http://msdn.microsoft.com:80/en-us/library/windows/desktop/dd378460(v=vs.85).aspx, Dec. 28, 2014, 8 pages. |
| Apple, “Final Cut Express 4 User Manual”, https://wsi.li.dl/mBGZWEQ8fh556f/, Jan. 1, 2007, 1,152 pages. |
| Apple, “Apple—September Event 2014”, https://www.youtube.com/watch?v=38lqQpqwPe7s, Sep. 10, 2014, 5 pages. |
| Azundris, “A Fire in the Pie,” http://web.archive.org/web/20140722062639/http://blog.azundrix.com/archives/168-A-fire-in-the-sky.html, Jul. 22, 2014, 8 pages. |
| Billibi, “Android 5.0 Lollipop”, https://www.bilibili.comvideo/av1636046?from=search&seid=3128140235778895126, Oct. 19, 2014, 6 pages. |
| B-log—betriebsraum weblog, “Extremely Efficient Menu Selection: Marking Menus for the Flash Platform,” http://www.betriebsraum.de/blog/2009/12/11/extremely-efficient-menu-selection-marking -for-the-flash-platform, Dec. 11, 2009, 9 pages. |
| Bolluyt, “5 Apple Watch Revelations from Apple's New WatchKit”, http://www.cheatsheet.com/tecnology/5-apple-watch-revelations-from-apples-new-watchkit.html/?a=viewall, Nov. 22, 2014, 3 pages. |
| Boring, “The Fat Thumb: Using the Thumb's Contact Size for Single-Handed Mobile Interaction”, https://www.youtube.com/watch?v=E9vGU5R8nsc&feature=youtu.be, Jun. 14, 2012, 2 pages. |
| Borowska, “6 Types of Digital Affordance that Impact Your Ux”, https://www.webdesignerdepot.com/2015/04/6-types-of-digital-affordance-that-implact-your-ux, Apr. 7, 2015, 6 pages. |
| Brewster, “The Design and Evaluation of a Vibrotactile Progress Bar”, Glasgow Interactive Systems Group, University of Glasgow, Glasgow, G12 8QQ, UK, 2005, 2 pages. |
| Brownlee, “Android 5.0 Lollipop Feature Review!”, https//www.youtube.com/watch?v=pEDQ1z1-PvU, Oct. 27, 2014, 5 pages. |
| Cheng, “iPhone 5: a little bit taller, a little bit baller”,https://arstechnica.com/gadgets/2012/09/iphone-5-a-little-bit-taller-a little-bit-baller, Oct. 14, 2021, 22 pages. |
| Clark, “Global Moxie, Touch Means a Renaissance for Radial Menus,” http://globalmoxie.com/blog/radial-menus-for-touch-ui˜print.shtml, Jul. 17, 2012, 7 pages. |
| Cohen, Cinemagraphs are Animated Gifs for Adults, http://www.tubefilter.com/2011/07/10/cinemagraph, Jul. 10, 2011, 3 pages. |
| CrackBerry Forums, Windows 8 Bezel Control and Gestures, http://wwwforums.crackberry.com/blackberry-playbook-f222/windows-8-bezel-control-gestures-705129/, Mar. 1, 2012, 8 pages. |
| Crook, “Microsoft Patenting Multi-Screen, Milti-Touch Gestures,” http://techcrunch.com/2011/08/25/microsoft-awarded-patents-for-multi-screen-multi-touch-gestures/, Aug. 25, 2011, 8 pages. |
| cvil.ly—a design blog, Interesting Touch Interactions on Windows 8, http://cvil.ly/2011/06/04/interesting-touch-interactions-on-windows-8/, Jun. 4, 2011, 3 pages. |
| Davidson, et al., “Extending 2D Object Arrangement with Pressure-Sensitive Layering Cues”, Proceedings of the 21st Annual ACM Symposium on User Interface Software and Technology, Oct. 19, 2008, 4 pages. |
| Dinwiddie, et al., “Combined-User Interface for Computers, Television, Video Recorders, and Telephone, Etc”, ip.com Journal, Aug. 1, 1990, 3 Pages. |
| Drinkwater, “Glossary: Pre/Post Alarm Image Buffer,” http://www.networkwebcams.com/ip-camera-learning-center/2008/07/17/glossary-prepost-alarm-image-buffer/, Jul. 17, 2008, 1 page. |
| Dzyre, “10 Android Notification Features You Can Fiddle With”, http://www.hongkiat.com/blog/android-notification-features, Mar. 10, 2014, 10 pages. |
| Easton-Ellett, “Three Free Cydia Utilities to Remove iOS Notification Badges”, http://www.ijailbreak.com/cydia/three-free-cydia-utilies-to-remove-ios-notification-badges, Apr. 14, 2012, 2 pages. |
| Elliot, “Mac System 7”, YouTube. Web. Mar. 8, 2017, http://www.youtube.com/watch?v=XLv22hfuuik, Aug. 3, 2011, 1 page. |
| Farshad, “SageThumbs—Preview and Convert Pictures From Windows Context Menu”, https://web.addictivetips.com/windows-tips/sagethumbs-preview-and-convert-photos-from-windows-context-menu, Aug. 8, 2011, 5 pages. |
| Fenlon, “The Case for Bezel Touch Gestures on Apple's iPad,” http://www.tested.com/tech/tablets/3104-the case-for-bezel-touch-gestures-on-apples-ipad/, Nov. 2, 2011, 6 pages. |
| Flaherty, “Is Apple Watch's Pressure-Sensitive Screen a Bigger Deal Than the Gadget Itself?”, http://www.wired.com/2014/09/apple-watchs-pressure-sensitive-screen-bigger-deal-gadget, Sep. 15, 2014, 3 pages. |
| Flixel, “Cinemagraph Pro for Mac”, https://flixel.com/products/mac/cinemagraph-pro, 2014, 7 pages. |
| Flowplayer, “Slowmotion: Flowplayer,” https://web.archive.org/web/20150226191526/http://flash.flowplayer.org/plugins/streaming/slowmotion.html, Feb. 26, 2015, 4 pages. |
| Garcia-Hernandez et al., “Orientation Discrimination of Patterned Surfaces through an Actuated and Non-Actuated Tactile Display”, 2011 IEEE World Haptics Conference, Istanbul, Jun. 21-24, 2011, 3 pages. |
| Forlines, et al., “Glimpse: a Novel Input Model for Multi-level Devices”, Chi '05 Extended Abstracts on Human Factors in Computing Systems, Apr. 2, 2005, 4 pages. |
| Gardner, “Recenz—Recent Apps in One Tap”, You Tube, https://www.youtube.com/watch?v-qailSHRgsTo, May 15, 2015, 1 page. |
| Geisler, “Enriched Links: A Framework for Improving Web Navigation Using Pop-Up Views”, Journal of the American Society for Information Science, Chapel Hill, NC, Jan. 1, 2000, 13 pages. |
| Gonzalo et al., “Zliding: Fluid Zooming and Sliding for High Precision Parameter Manipulation”, Department of Computer Science, University of Toronto, Seattle, Washington, Oct. 23, 2005, 10 pages. |
| Google-Chrome, “Android 5.0 Lollipop”, http://androidlover.net/android-os/android-5-0-lollipop/android-5-0-lollipop-recent-apps-card-google-search.html, Oct. 19, 2014, 10 pages. |
| Grant, “Android's Notification Center”, https://www.objc.io/issues/11-android/android-notifications, Apr. 30, 2014, 26 pages. |
| Gurman, “Force Touch on iPhone 6S Revealed: Expect Shortcuts, Faster Actions, iOS”, 9To5Mac Aug. 10, 2015, 31 pages. |
| Henderson et al., “Opportunistic User Interfaces for Augmented Reality”, Department of Computer Science, New York, NY, Jan. 2010, 13 pages. |
| IBM et al., “Pressure-Sensitive Icons”, IBM Technical Disclosure Bulletin, vol. 33, No. 1B, Jun. 1, 1990, 3 pages. |
| ICIMS Recruiting Software, “Blackberry Playbook Review,” http://www.tested.com/tech.tablets/5749-blackberry-playbook-review/, 2015, 11 pages. |
| IPhoneHacksTV, “Confero allows you to easily manage your Badge notifications—iPhone Hacks”, youtube, https://wwwyoutube.com/watch?v=JCk61pnL4SU, Dec. 26, 2014, 3 pages. |
| IPhoneOperator, “Wasser Liveeffekt fur Homescreen & Lockscreen—Aquaboard (Cydia)”, http://www.youtube.com/watch?v=fG9YMF-mB0Q, Sep. 22, 2012, 3 pages. |
| IPodHacks 142: “Water Ripple Effects on the Home and Lock Screen: AquaBoard Cydia Tweak Review”, YouTube, https://www.youtube.comwatch?v-Auu_uRaYHJs, Sep. 24, 2012, 3 pages. |
| Jauregui, “Design and Evaluation of 3D Cursors and Motion Parallax for the Exploration of Desktop Virtual Environments”, IEEE Symposium on 3D User Interfaces 2012, Mar. 4, 2012, 8 pages. |
| Jones, “Touch Screen with Feeling”, IEEE Spectrum, , spectrum.ieee.org/commuting/hardware/touch-screens-with-feeling, May 1, 2009, 2 pages. |
| Kaaresoja, “Snap-Crackle-Pop: Tactile Feedback for Mobile Touch Screens,” Nokia Research Center, Helsinki, Finland, Proceedings of Eurohaptics vol. 2006, Jul. 3, 2006, 2 pages. |
| Kiener, “Force Touch on iPhone”, https://www.youtube.com/watch?v=CEMmnsU5fC8, Aug. 4, 2015, 4 pages. |
| Kleinman, “iPhone 6s Said to Sport Force Touch Display, 2GB of RAM”, https://www.technobuffalo.com/2015/01/15/iphone-6s-said-to-sport-force-touch-display-2gb-of-ram, Jan. 15, 2015, 2 pages. |
| Kost, “LR3—Deselect All Images but One”, Julieanne Kost's Blog, blogs.adobe.com/jkost/2011/12/lr3-deselect-all-images-but-one.html, Dec. 22, 2011, 1 page. |
| Kronfli, “HTC Zoe Comes to Google Play, Here's Everything You Need to Know,” Know Your Mobile, http://www.knowyourmobile.com/htc/htc-one/19550/what-htc-zoe, Aug. 14, 2014, 5 pages. |
| Kumar, “How to Enable Ripple Effect on Lock Screen of Galaxy S2”, YouTube, http, http://www.youtube.com/watch?v+B9-4M5abLXA, Feb. 12, 2013, 3 pages. |
| Kurdi, “XnView Shell Extension: A Powerful Image Utility Inside the Context Menu”, http://www.freewaregenius.com/xnview-shell-extension-a-powerful-image-utility-inside-the-context-menu, Jul. 30, 2008, 4 pages. |
| Laurie, “The Power of the Right Click,” http://vlaurie.com/right-click/customize-context-menu.html, 2002-2016, 3 pages. |
| MacKenzie et al., “The Tactile Touchpad”, Chi '97 Extended Abstracts on Human Factors in Computing Systems Looking to the Future, Chi '97, Mar. 22, 1997, 5 pages. |
| Mahdi, Confero now available in Cydia, brings a new way to manage Notification badges [Jailbreak Tweak], http://www.iphonehacks.com/2015/01/confero/tweak-manage-notification-badges.html, Jan. 1, 2015, 2 pages. |
| Matthew, “How to Preview Photos and Images From Right-Click Context Menue in Windows [Tip]”, http://www.dottech.org/159009/add-image-preview-in-windows-context-menu-tip, Jul. 4, 2014, 5 pages. |
| McGarry, “Everything You Can Do With Force Touch on Apple Watch”, Macworld, www.macworld.com, May 6, 2015, 4 pages. |
| McRitchie, “Internet Explorer Right-Click Menus,” http://web.archive.org/web-201405020/http:/dmcritchie.mvps.org/ie/rightie6.htm, May 2, 2014, 10 pages. |
| Microsoft, “Lumia—How to Personalize Your Start Screen”, https://www.youtube.com/watch?v=6GI5Z3TrSEs, Nov. 11, 2014, 3 pages. |
| Microsoft, “Use Radial Menus to Display Commands in OneNote for Windows 8,” https://support.office.com/en-us/article/Use-radial-menues-to-display-OneNote-commands-Od75f03f-cde7-493a-a8a0b2ed6f99fbe2, 2016, 5 pages. |
| Minsky, “Computational Haptics The Sandpaper System for Synthesizing Texture for a Force-Feedback Display,” Massachusetts Institute of Technology, Jun. 1978, 217 pages. |
| Mitroff, “Google Android 5.0 Lollipop,” http://www.cnet.com/products/google-android-5-0-lollipop, Mar. 12, 2015, 5 pages. |
| Mohr, “Do Not Disturb—The iPhone Feature You Should Be Using”, http.www.wonderoftech.com/do-not-disturb-iphone, Jul. 14, 2014, 30 pages. |
| Nacca, “NiLS Lock Screen Notifications / Floating Panel—Review”, https://www.youtube.com/watch?v=McT4QnS9TDY, Feb. 3, 2014, 4 pages. |
| Neuburg, “Detailed Explanation iOS SDK”, Oreilly Japan, Dec. 22, 2014, vol. 4, p. 175-186, 15 pages. |
| Nickinson, How to Use Do Not Disturb on the HTC One M8, https://www.androidcentral.com/how-to-use-do-not-disturb-htc-one-m8, Apr. 7, 2014, 9 pages. |
| Nickinson, “Inside Android 4.2: Notifications and Quick Settings”, https://www.andrloidcentral.com/inside-android-42-notifications-and-quick-settings, Nov. 3, 2012, 3 pages. |
| Nikon, “Scene Recognition System and Advanced SRS,” http://www.nikonusa.com/en.Learn-And-Explore/Article/ftlzi4rr/Scene-Recognition-System.html, Jul. 22, 2015, 2 pages. |
| Nishino, “A Touch Screen Interface Design with Tactile Feedback”, Computer Science, 2011 International Conference on Complex, Intelligent, and Software Intensive Systems, 2011, 4 pages. |
| Ogino, “iOS 7 Design Standard”, Japan, Impress Japan Corporation, 1st edition, Nov. 21, 2013, 2 pages. |
| Oh, et al., “Moving Objects with 2D Input Devices in CAD Systems and Desktop Virtual Environments”, Proceedings of Graphics Interface 2005, 8 pages, May 2005. |
| O'Hara, et al., “Pressure-Sensitive Icons”, ip.com Journal, ip.com Inc., West Henrietta, NY, US, Jun. 1, 1990, 2 Pages. |
| Pallenberg, “Wow, the new iPad had gestures.” https://plus.google.com/+SaschaPallenberg/posts/aaJtJogu8ac, Mar. 7, 2012, 2 pages. |
| Phonebuff, “How to Pair Bluetooth on the iPhone”, https://www.youtube.com/watch?v=LudNwEar9A8, Feb. 8, 2012, 3 pages. |
| Plaisant et al, “Touchscreen Toggle Design”, Proceedings of CHI '92, pp. 667-668, May 3-7, 1992, 2 pages. |
| PoliceOne.com, “Coban Technologies Pre-Event Buffer & Fail Safe Feature,” http://www.policeone.com/police-products/police-technology/mobile-computures/videos/5955587-COBAN-Technologies-Pre-Event, Nov. 11, 2010, 2 pages. |
| Pradeep, “Android App Development—Microsoft Awarded With Patents on Gestures Supported on Windows 8,” http://mspoweruser.com/microsoft-awarded-with-patents-on-gestures-supported-on-windows-8/, Aug. 25, 2011, 16 pages. |
| “Quickly Preview Songs in Windows Media Player 12 in Windows 7,” Quickly Preview Songs in Windows Media Player 12 in Windows 7. How-to Geek, Apr. 28, 2010, Web. May 8, 2010, http://web.archive.org/web/20100502013134/http://www.howtogeek.com/howto/16157/quickly-preview-songs-in-windows-media-center-12-in-windows-7>, 6 pages. |
| Quinn, et al., “Zoofing! Faster List Selections with Pressure-Zoom-Flick-Scrolling”, Proceedings of the 21st Annual Conference of the Australian Computer-Human Interaction Special Interest Group on Design, Nov. 23, 2009, ACM Press, vol. 411, 8 pages. |
| Rekimoto, et al., “PreSense: Interaction Techniques for Finger Sensing Input Devices”, Proceedings of the 16th Annual ACM Symposium on User Interface Software and Technology, Nov. 30, 2003, 10 pages. |
| Rekimoto, et al., “PreSensell: Bi-directional Touch and Pressure Sensing Interactions with Tactile Feedback”, Conference on Human Factors in Computing Systems Archive, ACM, Apr. 22, 2006, 6 pages. |
| Rekimoto, et al., “SmartPad: A Finger-Sensing Keypad for Mobile Interaction”, CHI 2003, Ft. Lauderdale, Florida, ACM 1-58113-637—Apr. 5-10, 2003, 2 pages. |
| Ritchie, “How to see all the unread message notifications on your iPhone, all at once, all in the same place | iMore”, https://www.imore.com/how-see-all-unread-message-notifications-your-iphone-all-once-all-same-place, Feb. 22, 2014, 2 pages. |
| Roth et al., “Bezel Swipe: Conflict-Free Scrolling and Miltiple Selection on Mobile Touch Screen Devices,” Chi 2009, Boston, Massachusetts, USA, Apr. 4-9, 2009, 4 pages. |
| Rubino et al., “How to Enable ‘Living Images’ on your Nokia Lumia with Windows Phone 8.1”, https://www.youtube.com/watch?v=RX7vpoFy1Dg, Jun. 6, 2014, 5 pages. |
| Sleepfreaks, “How to Easily Play/Loop an Event Range in Cubase”, https://sleepfreaks-dtm.com/for-advance-cubase/position-3/>, Apr. 4, 2011, 14 pages. |
| Sony, “Intelligent Scene Recognition,” https://www.sony-asia.com/article/252999/section/product/product/dsc-t77, downloaded on May 20, 2016, 5 pages. |
| Sood, “MultitaskingGestures”, http://cydia.saurik.com/package/org.thebigboxx.multitaskinggestures/, Mar. 3, 2014, 2 pages. |
| Stewart, et al., “Characteristics of Pressure-Based Input for Mobile Devices”, Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Apr. 2010, 10 pages. |
| Stross, “Wearing a Badge, and a Video Camera,” The New York Times, http://www.nytimes.com/2013/04/07/business/wearable-video-cameras-for-police-offers.html? R=0, Apr. 6, 2013, 4 pages. |
| Taser, “Taser Axon Body Camera User Manual,” https://www.taser.com/images/support/downloads/product-resourses/axon_body_product_manual.pdf, Oct. 1, 2013, 24 pages. |
| Tidwell, “Designing Interfaces,” O'Reilly Media, Inc., USA, Nov. 2005, 348 pages. |
| Tweak, “QuickCenter—Add 3D-Touch Shortcuts to Control Center”, https://www.youtube.com/watch?v=8rHOFpGvZFM, Mar. 22, 2016, 2 pages. |
| Tweak, “iOS 10 Tweak on iOS 9.0.2 Jailbread & 9.2.1-9.3 Support: QuickCenter 3D, Touch Cydia Tweak!” https://wwwyoutube.com/watch?v=opOBr30_Fkl, Mar. 6, 2016, 3 pages. |
| UpDown-G, “Using Multiple Selection Mode in Android 4.0 / Getting Started”, https://techbooster.org/android/13946, Mar. 7, 2012, 7 pages. |
| VGJFeliz, “How to Master Android Lollipop Notifications in Four Minutes!”, https://www.youtube.com/watch?v=S-zBRG7GJgs, Feb. 8, 2015, 5 pages. |
| VisioGuy, “Getting a Handle on Selecting and Subselecting Visio Shapes”, http://www.visguy.com/2009/10/13/getting-a-handle-on-selecting-and-subselecting-visio-shapes/, Oct. 13, 2009, 18 pages. |
| Viticci, “Apple Watch: Our Complete Overview—MacStories”, https://www.macstories.net, Sep. 10, 2014, 21 pages. |
| Wikipedia, “AirDrop,”, Wikipedia, the free encyclopedia, http://en.wikipedia.org/wiki/AirDrop, May 17, 2016, 5 pages. |
| Wikipedia, “Cinemagraph,” Wikipedia, the free encyclopedia, http://en.wikipedia.org/wiki/Cinemagraph, Last Modified Mar. 16, 2016, 2 pages. |
| Wikipedia, “Context Menu,” Wikipedia, the free encyclopedia https://en.wikipedia.org/wiki/Context menu, Last Modified May 15, 2016, 4 pages. |
| Wikipedia, “HTC One (M7),” Wikipedia, the free encyclopedia, https://en.wikipedia.org/wiki/HTC_One_(M7), Mar. 2013, 20 pages. |
| Wikipedia, “Mobile Ad Hoc Network,” Wikipedia, the free encyclopedia, http://en.wikipedia.org/wiki/Mobile_ad_hoc_network, May 20, 2016, 4 pages. |
| Wikipedia, “Pie Menu,” Wikipedia, the free encyclopedia, http://en.wikipedia.org/wiki/Pie_menu, Last Modified Jun. 4, 2016, 3 pages. |
| Wikipedia, “Quick Look,” from Wikipedia, the free encyclopedia, https;//en.wikipedia.org/wiki/Quick_Look, Last Modified Jan. 15, 2016, 3 pages. |
| Wikipedia, “Sony Xperia Z1”, Wikipedia, the free encyclopedia, https://enwikipedia.org/wiki/Sony_Experia_Z1, Sep. 2013, 10 pages. |
| Wilson, et al., “Augmenting Tactile Interaction with Pressure-Based Input”, School of Computing Science, Glasgow, UK, Nov. 15-17, 2011, 2 pages. |
| Yang, et al., “Affordance Application on Visual Interface Design of Desk-Top Virtual Experiments”, 2014 International Conference on Information Science, Electronics and Electrical Engineering, IEEE, vol. 1, Apr. 26, 2014, 5 pages. |
| Yatani, et al., SemFeel: A User Interface with Semantic Tactile Feedback for Mobile Touch-Screen Devices, Proceedings of the 22nd annual ACM symposium on user interface software and technology (UIST '09), Oct. 2009, 10 pages. |
| YouTube, “Android Lollipop Lock-Screen Notification Tips”, https://www.youtube.com/watch?v=LZTxHBOwzIU, Nov. 13, 2014, 3 pages. |
| YouTube, “Blackberry Playbook bezel interaction,” https://www.youtube.com/watch?v=YGkzFqnOwXI, Jan. 10, 2011, 2 pages. |
| YouTube, “How to Master Android Lollipop Notifications in Four Minutes!”, Video Gadgets Journal (VGJFelix), https://www.youtube.com/watch?v=S-zBRG7GGJgs, Feb. 8, 2015, 4 pages. |
| YouTube, “HTC One Favorite Camera Features”, http://www.youtube.com/watch?v=sUYHfcjl4RU, Apr. 28, 2013, 3 pages. |
| YouTube, “Multitasking Gestures: Zephyr Like Gestures on iOS”, https://www.youtube.com/watch?v=Jcod-f7Lw0l, Jan. 27, 2014, 3 pages. |
| YouTube, “Recentz—Recent Apps in a Tap”, https://www.youtube.com/watch?v=qailSHRgsTo, May 15, 2015, 1 page. |
| Zylom, “House Secrets”, http://game.zylom.com/servlet/Entry?g=38&s=19521&nocache=1438641323066, Aug. 3, 2015, 1 page. |
| Office Action, dated Mar. 15, 2017, received in U.S. Appl. No. 14/535,671, 13 pages. |
| Office Action, dated Nov. 30, 2017, received in U.S. Appl. No. 14/535,671, 21 pages. |
| Notice of Allowance, dated Sep. 5, 2018, received in U.S. Appl. No. 14/535,671, 5 pages. |
| Office Action, dated Jun. 29, 2017, received in U.S. Appl. No. 14/608,895, 30 pages. |
| Final Office Action, dated Feb. 22, 2018, received in U.S. Appl. No. 14/608,895, 20 pages. |
| Notice of Allowance, dated Jun. 26, 2018, received in U.S. Appl. No. 14/608,895, 9 pages. |
| Office Action, dated Dec. 18, 2015, received in Australian Patent Application No. 2013368440, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Oct. 18, 2016, received in Australian Patent Application No. 2013368440, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Notice of Allowance, dated Dec. 20, 2016, received in Australian Patent Application No. 2013368440, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Certificate of Grant, dated Apr. 29, 2017, received in Australian Patent Application No. 2013368440, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Nov. 6, 2017, received in Chinese Patent Application No. 201380068493.6, which corresponds with U.S. Appl. No. 14/608,895, 5 pages. |
| Office Action, dated Oct. 9, 2018, received in Chinese Patent Application No. 201380068493.6, which corresponds with U.S. Appl. No. 14/608,895, 3 pages. |
| Patent, dated Dec. 25, 2018, received in Chinese Patent Application No. 201380068493.6, which corresponds with U.S. Appl. No. 14/608,895, 4 pages. |
| Office Action, dated Jul. 21, 2016, received in European Patent Application No. 13795391.5, which corresponds with U.S. Appl. No. 14/536,426, 9 pages. |
| Office Action, dated Mar. 9, 2018, received in European Patent Application No. 13795391.5, which corresponds with U.S. Appl. No. 14/536,426, 4 pages. |
| Intention to Grant, dated Jul. 6, 2018, received in European Patent Application No. 13795391.5, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Certificate of Grant, dated Dec. 26, 2018, received in European Patent Application No. 13795391.5, which corresponds with U.S. Appl. No. 14/536,426, 4 pages. |
| Office Action, dated Sep. 13, 2016, received in Japanese Patent Application No. 2015-547948, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Patent, dated May 12, 2017, received in Japanese Patent Application No. 2015-547948, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Apr. 5, 2016, received in Korean Patent Application No. 10-2015-7018851, which corresponds with U.S. Appl. No. 14/536,426, 7 pages. |
| Office Action, dated Feb. 24, 2017, received in Korean Patent Application No. 10-2015-7018851, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Patent, dated May 26, 2017, received in Korean Patent Application No. 2015-7018851, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Oct. 5, 2018, received in Korean Patent Application No. 2018-7028236, which corresponds with U.S. Appl. No. 14/608,895, 6 pages. |
| Notice of Allowance, dated May 24, 2019, received in Korean Patent Application No. 2018-7028236, which corresponds with U.S. Appl. No. 14/608,895, 4 pages. |
| Patent, dated Jul. 9, 2019, received in Korean Patent Application No. 2018-7028236, which corresponds with U.S. Appl. No. 14/608,895, 4 pages. |
| Office Action, dated Jul. 26, 2017, received in U.S. Appl. No. 14/536,235, 14 pages. |
| Final Office Action, dated Feb. 26, 2018, received in U.S. Appl. No. 14/536,235, 13 pages. |
| Notice of Allowance, dated Aug. 15, 2018, received in U.S. Appl. No. 14/536,235, 5 pages. |
| Office Action, dated Apr. 5, 2017, received in U.S. Appl. No. 14/536,367, 16 pages. |
| Notice of Allowance, dated Nov. 30, 2017, received in U.S. Appl. No. 14/536,367, 9 pages. |
| Notice of Allowance, dated May 16, 2018, received in U.S. Appl. No. 14/536,367, 5 pages. |
| Office Action, dated Dec. 17, 2015, received in U.S. Appl. No. 14/536,426, 28 pages. |
| Final Office Action, dated May 6, 2016, received in U.S. Appl. No. 14/536,426, 23 pages. |
| Office action, dated Aug. 3, 2017, received in U.S. Appl. No. 14/536,426, 10 pages. |
| Office Action, dated Jul. 15, 2015, received in Australian Patent Application No. 2013259606, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Notice of Allowance, dated May 23, 2016, received in Australian Patent Application No. 2013259606, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Certificate of Grant, dated Sep. 15, 2016, received in Australian Patent Australian Patent Application No. 2013259606, which corresponds with U.S. Appl. No. 14/536,426, 1 page. |
| Office Action, dated Nov. 18, 2015, received in Australian Patent Application No. 2015101231, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated May 15, 2017, received in Australian Patent Application No. 2016216580, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated May 8, 2018, received in Australian Patent Application No. 2016216580, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Notice of Allowance, dated May 17, 2018, received in Australian Patent Application No. 2016216580, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Certificate of Grant, dated Sep. 13, 2018, received in Australian Patent Application No. 2016216580, which corresponds with U.S. Appl. No. 14/536,426, 1 page. |
| Office Action, dated Apr. 12, 2019, received in Australian Patent Application No. 2018223021, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Nov. 18, 2019, received in Australian Patent Application No. 2018223021, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Feb. 18, 2020, received in Australian Patent Application No. 2018223021, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Notice of Allowance, dated Mar. 27, 2020, received in Australian Patent Application No. 2018223021, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Certificate of Grant, dated Jul. 23, 2020, received in Australian Patent Application No. 2018223021, which corresponds with U.S. Appl. No. 14/536,426, 4 pages. |
| Office Action, dated Sep. 19, 2017, received in Chinese Patent Application No. 201380035982.1, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Notice of Allowance, dated May 10, 2018, received in Chinese Patent Application No. 201380035982.1, which corresponds with U.S. Appl. No. 14/536,426, 2 pages. |
| Patent, dated Aug. 17, 2018, received in Chinese Patent Application No. 201380035982.1, which corresponds with U.S. Appl. No. 14/536,426, 4 pages. |
| Office Action, dated Sep. 20, 2017, received in Chinese Patent Application No. 201510566550.4, which corresponds with U.S. Appl. No. 14/536,426, 11 pages. |
| Notice of Allowance, dated Aug. 8, 2018, received in Chinese Patent Application No. 201510566550.4, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Patent, dated Oct. 23, 2018, received in Chinese Patent Application No. 201510566550.4, which corresponds with U.S. Appl. No. 14/536,426, 4 pages. |
| Office Action, dated Jan. 4, 2021, received in Chinese Patent Application No. 201810826224.6, which corresponds with U.S. Appl. No. 14/536,426, 6 pages. |
| Office Action, dated Jun. 24, 2021, received in Chinese Patent Application No. 201810826224.6, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Notice of Allowance, dated Oct. 11, 2021, received in Chinese Patent Application No. 201810826224.6, which corresponds with U.S. Appl. No. 14/536,426, 1 page. |
| Patent, dated Nov. 12, 2021, received in Chinese Patent Application No. 201810826224.6, which corresponds with U.S. Appl. No. 14/536,426, 7 pages. |
| Decision to Grant, dated Jul. 14, 2016, received in European Patent Application No. 13724100.6, which corresponds with U.S. Appl. No. 14/536,426, 1 page. |
| Letters Patent, dated Aug. 10, 2016, received in European Patent Application No. 13724100.6, which corresponds with U.S. Appl. No. 14/536,426, 1 page. |
| Office Action, dated Jan. 20, 2017, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Office Action, dated Aug. 21, 2017, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Intention to Grant, dated Mar. 9, 2018, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Intention to Grant, dated Aug. 14, 2018, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Decision to Grant, dated Jan. 10, 2019, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 4 pages. |
| Patent, dated Feb. 6, 2019, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 4 pages. |
| Office Action, dated Sep. 6, 2019, received in European Patent Application No. 18180503.7, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Certificate of Grant, dated Nov. 10, 2017, received in Hong Kong Patent Application No. 15107535.0, which corresponds with U.S. Appl. No. 14/536,426, 2 pages. |
| Certificate of Grant, dated Jul. 5, 2019, received in Hong Kong Patent Application No. 15108892.5, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Patent, dated Nov. 22, 2019, received in Hong Kong Patent Application No. 16107033.6, which corresponds with U.S. Appl. No. 14/536,426, 6 pages. |
| Office Action, dated Mar. 4, 2016, received in Japanese Patent Application No. 2015-511644, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Feb. 6, 2017, received in Japanese Patent Application No. 2015-511644, which corresponds with U.S. Appl. No. 14/536,426, 6 pages. |
| Notice of Allowance, dated Dec. 8, 2017, received in Japanese Patent Application No. 2015-511644, which corresponds with U.S. Appl. No. 14/536,426, 6 pages. |
| Patent, dated Jan. 12, 2018, received in Japanese Patent Application No. 2015-511644, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Nov. 6, 2018, received in Japanese Patent Application No. 2018-000753, which corresponds with U.S. Appl. No. 14/536,426, 8 pages. |
| Office Action, dated Oct. 7, 2019, received in Japanese Patent Application No. 2018-000753, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Office Action, dated Feb. 8, 2021, received in Japanese Patent Application No. 2018-000753, which corresponds with U.S. Appl. No. 14/536,426, 2 pages. |
| Office Action, dated Mar. 9, 2017, received in U.S. Appl. No. 14/536,464, 21 pages. |
| Final Office Action, dated Aug. 25, 2017, received in U.S. Appl. No. 14/536,464, 30 pages. |
| Office Action, dated Feb. 12, 2018, received in U.S. Appl. No. 14/536,464, 33 pages. |
| Final Office Action, dated Jun. 22, 2018, received in U.S. Appl. No. 14/536,464, 32 pages. |
| Notice of Allowance, dated Jan. 25, 2021, received in U.S. Appl. No. 14/536,464, 5 pages. |
| Notice of Allowance, dated Feb. 23, 2021, received in U.S. Appl. No. 14/536,464, 5 pages. |
| Office Action, dated Sep. 25, 2017, received in U.S. Appl. No. 14/536,644, 29 pages. |
| Final Office Action, dated May 3, 2018, received in U.S. Appl. No. 14/536,644, 28 pages. |
| Office Action, dated Nov. 2, 2018, received in U.S. Appl. No. 14/536,644, 24 pages. |
| Notice of Allowance, dated Jul. 2, 2019, received in U.S. Appl. No. 14/536,644, 5 pages. |
| Office Action, dated Oct. 19, 2017, received in U.S. Appl. No. 14/608,926, 14 pages. |
| Final Office Action, dated Jun. 6, 2018, received in U.S. Appl. No. 14/608,926, 19 pages. |
| Notice of Allowance, dated Apr. 10, 2019, received in U.S. Appl. No. 14/608,926, 16 pages. |
| Notice of Allowance, dated May 21, 2019, received in U.S. Appl. No. 14/608,926, 5 pages. |
| Office Action, dated Feb. 1, 2016, received in Australian Patent Application No. 2013368441, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
| Notice of Allowance, dated Mar. 30, 2016, received in Australian Patent Application No. 2013368441, which corresponds with U.S. Appl. No. 14/608,926, 1 page. |
| Certificate of Grant, dated Jul. 29, 2016, received in Australian Patent Application No. 2013368441, which corresponds with U.S. Appl. No. 14/608,926, 1 page. |
| Office Action, dated Jan. 3, 2017, received in Australian Patent Application No. 2016201451, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
| Notice of Acceptance, dated Dec. 20, 2017, received in Australian Patent Application No. 2016201451, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
| Certificate of Grant, dated May 3, 2018, received in Australian Patent Application No. 2016201451, which corresponds with U.S. Appl. No. 14/608,926, 1 page. |
| Office Action, dated May 4, 2017, received in Chinese Patent Application No. 201380068414.1, which corresponds with U.S. Appl. No. 14/608,926, 5 pages. |
| Notice of Allowance, dated Feb. 8, 2018, received in Chinese Patent Application No. 201380068414.1, which corresponds with U.S. Appl. No. 14/608,926, 2 pages. |
| Patent, dated May 4, 2018, received in Chinese Patent Application No. 201380068414.1, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
| Office Action, dated Dec. 1, 2020, received in Chinese Patent Application No. 201810369259.1, which corresponds with U.S. Appl. No. 14/608,926, 14 pages. |
| Office Action, dated Jul. 14, 2021, received in Chinese Patent Application No. 201810369259.1, which corresponds with U.S. Appl. No. 14/608,926, 5 pages. |
| Office Action, dated Jan. 10, 2022, received in Chinese Patent Application No. 201810369259.1, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
| Office Action, dated Apr. 21, 2016, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 6 pages. |
| Office Action, dated May 6, 2016, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 6 pages. |
| Office Action, dated Nov. 11, 2016, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 6 pages. |
| Office Action, dated Jul. 4, 2017, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
| Oral Summons, dated Feb. 13, 2017, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 11 pages. |
| Office Action, dated Mar. 14, 2016, received in Japanese Patent Application No. 2015-549392, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
| Notice of Allowance, dated Jan. 17, 2017, received in Japanese Patent Application No. 2015-549392, which corresponds with U.S. Appl. No. 14/608,926, 2 pages. |
| Patent, dated Feb. 17, 2017, received in Japanese Patent Application No. 2015-549392, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
| Patent, dated Apr. 27, 2018, received in Japanese Patent Application No. 2017-024234, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
| Office Action, dated Feb. 22, 2019, received in Japanese Patent Application No. 2018-079290, which corresponds with U.S. Appl. No. 14/608,926, 7 pages. |
| Office Action, dated Sep. 30, 2019, received in Japanese Patent Application No. 2018-079290, which corresponds with U.S. Appl. No. 14/608,926, 5 pages. |
| Notice of Allowance, dated Apr. 3, 2020, received in Japanese Patent Application No. 2018-079290, which corresponds with U.S. Appl. No. 14/608,926, 5 pages. |
| Patent, dated Apr. 14, 2020, received in Japanese Patent Application No. 2018-079290, which corresponds with U.S. Appl. No. 14/608,926, 5 pages. |
| Office Action, dated May 12, 2016, received in Korean Patent Application No. 10-2015-7018853, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
| Notice of Allowance, dated Mar. 31, 2017, received in Korean Patent Application No. 2015-7018853, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
| Patent, dated Jun. 30, 2017, received in Korean Patent Application No. 2015-7018853, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
| Office Action, dated Aug. 22, 2017, received in Korean Patent Application No. 2017-7018250, which corresponds with U.S. Appl. No. 14/608,926, 2 pages. |
| Notice of Allowance, dated Dec. 29, 2017, received in Korean Patent Application No. 2017-7018250, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
| Office Action, dated Oct. 19, 2017, received in U.S. Appl. No. 14/536,646, 21 pages. |
| Notice of Allowance, dated Aug. 9, 2018, received in U.S. Appl. No. 14/536,646, 5 pages. |
| Office Action, dated Jul. 17, 2015, received in Australian Patent Application No. 2013259613, which corresponds with U.S. Appl. No. 14/536,646, 5 pages. |
| Office Action, dated May 31, 2016, received in Australian Patent Application No. 2013259613, which corresponds with U.S. Appl. No. 14/536,646, 4 pages. |
| Notice of Allowance, dated Jul. 5, 2016, received in Australian Patent Application No. 2013259613, which corresponds with U.S. Appl. No. 14/536,646, 3 pages. |
| Office Action, dated Jun. 6, 2019, received in Australian Patent Application No. 2018256626, which corresponds with U.S. Appl. No. 14/536,646, 3 pages. |
| Notice of Acceptance, dated Aug. 1, 2019, received in Australian Patent Application No. 2018256626, which corresponds with U.S. Appl. No. 14/536,646, 3 pages. |
| Certificate of Grant, dated Dec. 5, 2019, received in Australian Patent Application No. 2018256626, which corresponds with U.S. Appl. No. 14/536,646, 3 pages. |
| Office Action, dated Dec. 1, 2016, received in Chinese Patent Application No. 2013800362059, which corresponds with U.S. Appl. No. 14/536,646, 3 pages. |
| Notice of Allowance, dated Oct. 9, 2017, received in Chinese Patent Application No. 2013800362059, which corresponds with U.S. Appl. No. 14/536,646, 3 pages. |
| Office Action, dated Jul. 3, 2020, received in Chinese Patent Application No. 201711425148.X, which corresponds with U.S. Appl. No. 14/536,646, 13 pages. |
| Office Action, dated Jun. 10, 2021, received in Chinese Patent Application No. 201711425148.X, which corresponds with U.S. Appl. No. 14/536,646, 2 pages. |
| Notice of Allowance, dated Oct. 9, 2021, received in Chinese Patent Application No. 201711425148.X, which corresponds with U.S. Appl. No. 14/536,646, 2 pages. |
| Office Action, dated Oct. 26, 2020, received in Chinese Patent Application No. 201711422092.2, which corresponds with U.S. Appl. No. 14/536,646, 20 pages. |
| Notice of Allowance, dated Mar. 22, 2021, received in Chinese Patent Application No. 201711422092.2, which corresponds with U.S. Appl. No. 14/536,646, 2 pages. |
| Certificate of Grant, dated Apr. 13, 2021, received in Chinese Patent Application No. 201711422092.2, which corresponds with U.S. Appl. No. 14/536,646, 8 pages. |
| Office Action, dated Nov. 12, 2015, received in European Patent Application No. 13724102.2, which corresponds with U.S. Appl. No. 14/536,646, 6 pages. |
| Office Action, dated May 31, 2016, received in European Patent Application No. 13724102.2, which corresponds with U.S. Appl. No. 14/536,646, 5 pages. |
| Notice of Allowance, dated Jan. 4, 2017, received in European Patent Application No. 13724102.2, which corresponds with U.S. Appl. No. 14/536,646, 5 pages. |
| Patent, dated May 26, 2017, received in European Patent Application No. 13724102.2, which corresponds with U.S. Appl. No. 14/536,646, 1 page. |
| Office Action, dated Feb. 29, 2016, received in Japanese Patent Application No. 2015-511645, which corresponds with U.S. Appl. No. 14/536,646, 5 pages. |
| Notice of Allowance, dated Dec. 22, 2016, received in Japanese Patent Application No. 2015-511645, which corresponds with U.S. Appl. No. 14/536,646, 2 pages. |
| Certificate of Grant, dated Jan. 25, 2019, received in Hong Kong Patent Application No. 2015-511645, which corresponds with U.S. Appl. No. 14/536,646, 4 pages. |
| Office Action, dated Apr. 3, 2017, received in U.S. Appl. No. 14/536,141, 11 pages. |
| Notice of Allowance, dated Sep. 20, 2017, received in U.S. Appl. No. 14/536,141, 10 pages. |
| Office Action, dated Aug. 27, 2015, received in Australian Patent Application No. 2013259614, which corresponds with U.S. Appl. No. 14/536,141, 4 pages. |
| Notice of Allowance, dated Aug. 15, 2016, received in Australian Patent Application No. 2013259614, which corresponds with U.S. Appl. No. 14/536,141, 1 page. |
| Office Action, dated Jul. 21, 2017, received in Australian Patent Application No. 2016262773, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
| Notice of Acceptance, dated Jul. 19, 2018, received in Australian Patent Application No. 2016262773, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
| Office Action, dated Jun. 5, 2019, received in Australian Patent Application No. 2018256616, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
| Notice of Acceptance, dated Jan. 22, 2020, received in Australian Patent Application No. 2018256616, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
| Certificate of Grant, dated May 21, 2020, received in Australian Patent Application No. 2018256616, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
| Office Action, dated Mar. 3, 2017, received in Chinese Patent Application No. 201380035893.7, which corresponds with U.S. Appl. No. 14/536,141, 8 pages. |
| Office Action, dated Feb. 2, 2018, received in Chinese Patent Application No. 201380035893.7, which corresponds with U.S. Appl. No. 14/536,141, 5 pages. |
| Notice of Allowance, dated Aug. 31, 2018, received in Chinese Patent Application No. 201380035893.7, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
| Office Action, dated Mar. 10, 2021, received in Chinese Patent Application No. 201811142423.1, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
| Office Action, dated Aug. 12, 2021, received in Chinese Patent Application No. 201811142423.1, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
| Notice of Allowance, dated Oct. 26, 2021, received in Chinese Patent Application No. 201811142423.1, which corresponds with U.S. Appl. No. 14/536,141, 2 pages. |
| Patent, dated Dec. 31, 2021, received in Chinese Patent Application No. 201811142423.1, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
| Patent, dated Oct. 23, 2018, received in Chinese Patent Application No. 201380035893.7, which corresponds with U.S. Appl. No. 14/536,141, 4 pages. |
| Office Action, dated Jan. 7, 2016, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 10 pages. |
| Office Action, dated Aug. 31, 2016, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 10 pages. |
| Office Action, dated Apr. 9, 2018, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 9 pages. |
| Office Action, dated Mar. 7, 2019, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 5 pages. |
| Intention to Grant, dated Sep. 6, 2019, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 7 pages. |
| Decision to Grant, dated Jan. 23, 2020, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 1 page. |
| Patent, dated Feb. 19, 2020, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 4 page. |
| Office Action, dated Feb. 29, 2016, received in Japanese Patent Application No. 2015-511646, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
| Office Action, dated Oct. 25, 2016, received in Japanese Patent Application No. 2015-511646, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
| Notice of Allowance, dated Jun. 30, 2017, received in Japanese Patent Application No. 2015-511646, which corresponds with U.S. Appl. No. 14/536,141, 5 pages. |
| Patent, dated Jul. 28, 2017, received in Japanese Patent Application No. 2015-511646, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
| Office Action, dated Aug. 10, 2018, received in Japanese Patent Application No. 2017-141953, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
| Office Action, dated Jul. 5, 2019, received in Japanese Patent Application No. 2017-141953, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
| Office Action, dated Dec. 8, 2016, received in U.S. Appl. No. 14/608,942, 9 pages. |
| Notice of Allowance, dated May 12, 2017, received in U.S. Appl. No. 14/608,942, 10 pages. |
| Office Action, dated Jan. 29, 2016, received in Australian Patent Application No. 2013368443, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
| Notice of Allowance, dated Mar. 11, 2016, received in Australian Patent Application No. 2013368443, which corresponds with U.S. Appl. No. 14/608,942, 2 pages. |
| Certificate of Grant, dated Jul. 7, 2016, received in Australian Patent Application No. 2013368443, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
| Office Action, dated Mar. 29, 2017, received in Australian patent Application No. 2016201303, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
| Notice of Acceptance, dated Mar. 7, 2018, received in Australian patent Application No. 2016201303, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
| Certificate of Grant, dated Jul. 5, 2018, received in Australian patent Application No. 2016201303, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
| Office Action, dated Jun. 16, 2017, received in Chinese Patent Application No. 201380068295.X, which corresponds with U.S. Appl. No. 14/608,942, 6 pages. |
| Office Action, dated Mar. 28, 2018, received in Chinese Patent Application No. 201380068295.X, which corresponds with U.S. Appl. No. 14/608,942, 5 pages. |
| Office Action, dated Oct. 8, 2018, received in Chinese Patent Application No. 201380068295.X, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
| Notice of Allowance, dated May 7, 2019, received in Chinese Patent Application No. 201380068295.X, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
| Patent, dated Jul. 5, 2019, received in Chinese Patent Application No. 201380068295.X, which corresponds with U.S. Appl. No. 14/608,942, 8 pages. |
| Office Action, dated Oct. 7, 2016, received in European Patent Application No. 13798464.7, which corresponds with U.S. Appl. No. 14/608,942, 7 pages. |
| Decision to Grant, dated Sep. 13, 2018, received in European Patent Application No. 13798464.7, which corresponds with U.S. Appl. No. 14/608,942, 2 pages. |
| Intention to Grant, dated Nov. 8, 2019, received in European Patent Application No. 18194127.9, which corresponds with U.S. Appl. No. 14/608,942, 7 pages. |
| Decision to Grant, dated Aug. 20, 2020, received in European Patent Application No. 18194127.9, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
| Patent, dated Sep. 16, 2020, received in European Patent Application No. 18194127.9, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
| Certificate of Grant, dated Jul. 26, 2019, received in Hong Kong, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
| Office Action, dated Jul. 4, 2016, received in Japanese Patent Application No. 2015-549393, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
| Notice of Allowance, dated May 12, 2017, received in Japanese Patent Application No. 2015-549393, which corresponds with U.S. Appl. No. 14/608,942, 5 pages. |
| Patent, dated Jun. 16, 2017, received in Japanese Patent Application No. 2015-549393, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
| Office Action, dated Apr. 5, 2016, received in Korean Patent Application No. 2015-7018448, which corresponds with U.S. Appl. No. 14/608,942, 6 pages. |
| Office Action, dated Feb. 24, 2017, received in Korean Patent Application No. 2015-7018448, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
| Notice of Allowance, dated Jan. 15, 2019, received in Korean Patent Application No. 2015-7018448, which corresponds with U.S. Appl. No. 14/608,942, 5 pages. |
| Patent, dated Mar. 8, 2019, received in Korean Patent Application No. 2015-7018448, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
| Office Action, dated Jul. 17, 2017, received in U.S. Appl. No. 14/536,166, 19 pages. |
| Notice of Allowance, dated Feb. 28, 2018, received in U.S. Appl. No. 14/536,166, 5 pages. |
| Office Action, dated Aug. 1, 2016, received in U.S. Appl. No. 14/536,203, 14 pages. |
| Notice of Allowance, dated Feb. 1, 2017, received in U.S. Appl. No. 14/536,203, 9 pages. |
| Office Action, dated Jul. 9, 2015, received in Australian Patent Application No. 2013259630, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Notice of Allowance, dated Jun. 15, 2016, received in Australian Patent Application No. 2013259630, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Certificate of Grant, dated Oct. 21, 2016, received in Australian Patent Application No. 2013259630, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Office Action, dated Jul. 4, 2017, received in Australian Patent Application No. 2016238917, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Notice of Acceptance, dated Jul. 19, 2018, received in Australian Patent Application No. 2016238917, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Certificate of Grant, dated Nov. 1, 2018, received in Australian Patent Application No. 2016238917, which corresponds with U.S. Appl. No. 14/536,203, 1 page. |
| Office Action, dated Aug. 20, 2018, received in Australian Patent Application No. 2018250481, which corresponds with U.S. Appl. No. 14/536,203, 2 pages. |
| Notice of Allowance, dated Apr. 29, 2020, received in Australian Patent Application No. 2018250481, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Certificate of Grant, dated Sep. 3, 2020, received in Australian Patent Application No. 2018250481, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Office Action, dated Oct. 25, 2017, received in Chinese Patent Application No. 201380035977.0, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Notice of Allowance, dated Apr. 4, 2018, received in Chinese Patent Application No. 201380035977.0, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Patent, dated Jul. 6, 2018, received in Chinese Patent Application No. 201380035977.0, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Office Action, dated Jan. 26, 2021, received in Chinese Patent Application No. 201810632507.7, 5 pages. |
| Notice of Allowance, dated Aug. 11, 2021, received in Chinese Patent Application No. 201810632507.7, which corresponds with U.S. Appl. No. 14/536,203, 1 page. |
| Patent, dated Oct. 22, 2021, received in Chinese Patent Application No. 201810632507.7, which corresponds with U.S. Appl. No. 14/536,203, 7 pages. |
| Office Action, dated Nov. 11, 2015, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Office Action, dated May 31, 2016, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Office Action, dated Dec. 6, 2017, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 9 pages. |
| Decision to Grant, dated Oct. 24, 2018, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Intention to Grant, dated Mar. 18, 2019, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 9 pages. |
| Decision to Grant, dated Aug. 8, 2019, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 1 page. |
| Certificate of Grant, dated Sep. 4, 2019, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Patent, dated Sep. 27, 2019, received in Hong Kong Patent Application No. 15108904.1, which corresponds with U.S. Appl. No. 14/536,203, 6 pages. |
| Office Action, dated Feb. 15, 2016, received in Japanese Patent Application No. 2015-511650, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Notice of Allowance, dated Aug. 5, 2016, received in Japanese Patent Application No. 2015-511650, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Certificate of Patent, dated Sep. 9, 2016, received in Japanese Patent Application No. 2015-511650, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Office Action, dated Jun. 23, 2017, received in Japanese Patent Application No. 2016173113, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Notice of Allowance, dated Jan. 12, 2018, received in Japanese Patent Application No. 2016173113, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Patent, dated Feb. 16, 2018, received in Japanese Patent Application No. 2016173113, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Office Action, dated Oct. 19, 2018, received in Japanese Patent Application No. 2018-022394, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Office Action, dated Sep. 30, 2019, received in Japanese Patent Application No. 2018-022394, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Office Action, dated Jan. 22, 2021, received in Japanese Patent Application No. 2018-022394, which corresponds with U.S. Appl. No. 14/536,203, 2 pages. |
| Notice of Allowance, dated Dec. 3, 2021, received in Japanese Patent Application No. 2018-022394, which corresponds with U.S. Appl. No. 14/536,203, 2 pages. |
| Patent, dated Dec. 13, 2021, received in Japanese Patent Application No. 2018-022394, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Office Action, dated Dec. 4, 2015, received in Korean Patent Application No. 2014-7034520, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Notice of Allowance, dated Sep. 1, 2016, received in Korean Patent Application No. 2014-7034520, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Office Action, dated Feb. 6, 2017, received in Korean Patent Application No. 2016-7033834, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Notice of Allowance, dated Oct. 30, 2017, received in Korean Patent Application No. 2016-7033834, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Patent, dated Jan. 23, 2018, received in Korean Patent Application No. 2016-7033834, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Office Action, dated Oct. 20, 2017, received in U.S. Appl. No. 14/608,965, 14 pages. |
| Office Action, dated Jul. 2, 2018, received in U.S. Appl. No. 14/608,965, 16 pages. |
| Final Office Action, dated Jan. 10, 2019, received in U.S. Appl. No. 14/608,965, 17 pages. |
| Notice of Allowance dated Nov. 7, 2019, received in U.S. Appl. No. 14/608,965, 17 pages. |
| Notice of Allowance dated Jan. 2, 2020, received in U.S. Appl. No. 14/608,965, 5 pages. |
| Office action, dated Oct. 11, 2017, received in Chinese Patent Application No. 201380074060.1, which corresponds with U.S. Appl. No. 14/608,965, 5 pages. |
| Office action, dated Aug. 1, 2018, received in Chinese Patent Application No. 201380074060.1, which corresponds with U.S. Appl. No. 14/608,965, 5 pages. |
| Office action, dated Nov. 1, 2018, received in Chinese Patent Application No. 201380074060.1, which corresponds with U.S. Appl. No. 14/608,965, 3 pages. |
| Office action, dated Apr. 3, 2019, received in Chinese Patent Application No. 201380074060.1, which corresponds with U.S. Appl. No. 14/608,965, 3 pages. |
| Patent, dated May 17, 2019, received in Chinese Patent Application No. 201380074060.1, which corresponds with U.S. Appl. No. 14/608,965, 6 pages. |
| Office Action, dated Jul. 22, 2016, received in European Office Action No. 13798465.4, which corresponds with U.S. Appl. No. 14/608,965, 3 pages. |
| Oral Proceedings, dated Mar. 7, 2018, received in European Office Action No. 13798465.4, which corresponds with U.S. Appl. No. 14/608,965, 5 pages. |
| Decision to Grant, dated Sep. 6, 2018, received in European Office Action No. 13798465.4, which corresponds with U.S. Appl. No. 14/608,965, 2 pages. |
| Office Action, dated Oct. 20, 2016, received in U.S. Appl. No. 14/536,247, 10 pages. |
| Final Office Action, dated Mar. 24, 2017, received in U.S. Appl. No. 14/536,247, 14 pages. |
| Notice of Allowance, dated Nov. 22, 2017, received in U.S. Appl. No. 14/536,247, 6 pages. |
| Office Action, dated Mar. 24, 2017, received in U.S. Appl. No. 14/536,267, 12 pages. |
| Notice of Allowance, dated Nov. 9, 2017, received in U.S. Appl. No. 14/536,267, 8 pages. |
| Notice of Allowance, dated Jun. 1, 2018, received in U.S. Appl. No. 14/536,267, 5 pages. |
| Office Action, dated Aug. 10, 2015, received in Australian Patent Application No. 2013259637, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Notice of Allowance, dated Jun. 28, 2016, received in Australian Patent Application No. 2013259637, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Certificate of Grant, dated Oct. 21, 2016, received in Australian Patent Application No. 2013259637, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Office Action, dated Mar. 24, 2017, received in Australian Patent Application No. 2016204411, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Notice of Acceptance, dated Feb. 27, 2018, received in Australian Patent Application No. 2016204411, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Certificate of Grant, dated Jun. 28, 2018, received in Australian Patent Application No. 2016204411, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Office Action, dated Mar. 15, 2019, received in Australian Patent Application No. 2018204236, which corresponds with U.S. Appl. No. 14/5326,267, 5 pages. |
| Notice of Acceptance, dated Apr. 29, 2019, received in Australian Patent Application No. 2018204236, which corresponds with U.S. Appl. No. 14/5326,267, 3 pages. |
| Certificate of Grant, dated Aug. 28, 2019, received in Australian Patent Application No. 2018204236, which corresponds with U.S. Appl. No. 14/5326,267, 4 pages. |
| Office Action, dated Dec. 9, 2016, received in Chinese Patent Application No. 2016120601564130, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Notice of Allowance, dated Jan. 29, 2018, received in Chinese Patent Application No. 201380035968.1, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Patent, dated Apr. 20, 2018, received in Chinese Patent Application No. 201380035968.1, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Office Action, dated Nov. 28, 2018, received in Chinese Patent Application No. 20161037334.1, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
| Office Action, dated Jul. 11, 2019, received in Chinese Patent Application No. 201610537334.1, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Office Action, dated Sep. 30, 2019, received in Chinese Patent Application No. 201610537334.1, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Office Action, dated Dec. 20, 2019, received in Chinese Patent Application No. 201610537334.1, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Office Action, dated Apr. 20, 2020, received in Chinese Patent Application No. 201610537334.1, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Patent, dated Sep. 29, 2020, received in Chinese Patent Application No. 201610537334.1, which corresponds with U.S. Appl. No. 14/536,267, 7 pages. |
| Office Action, dated Jun. 13, 2018, received in Chinese Patent Application No. 201810332044.2, which corresponds with U.S. Appl. No. 14/536,267, 2 pages. |
| Office Action, dated Jan. 20, 2021, received in Chinese Patent Application No. 201810332044.2, which corresponds with U.S. Appl. No. 14/536,267, 15 pages. |
| Office Action, dated Jul. 19, 2021, received in Chinese Patent Application No. 201810332044.2, which corresponds with U.S. Appl. No. 14/536,267, 1 page. |
| Office Action, dated Nov. 23, 2021, received in Chinese Patent Application No. 201810332044.2, which corresponds with U.S. Appl. No. 14/536,267, 2 page. |
| Office Action, dated Jan. 25, 2018, received in European Patent Application No. 13724106.3, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
| Intention to Grant, dated Jun. 27, 2018, received in European Patent Application No. 13724106.3, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
| Decision to Grant, dated Oct. 18, 2018, received in European Patent Application No. 13724106.3, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Grant Certificate, dated Nov. 14, 2018, received in European Patent Application No. 13724106.3, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. 4 pages. |
| Office Action, dated Sep. 13, 2017, received in European Patent Application No. 16177863.4, which corresponds with U.S. Appl. No. 14/536,267, 6 pages. |
| Decision to Grant, dated Nov. 29, 2018, received in European Patent Application No. 16177863.4, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Patent, dated Dec. 26, 2018, received in European Patent Application No. 16177863.4, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Office Action, dated Aug. 29, 2019, received in European Patent Application No. 18183789.9, which corresponds with U.S. Appl. No. 16/262,800, 9 pages. |
| Office Action, dated Aug. 21, 2020, received in European Patent Application No. 18183789.9, which corresponds with U.S. Appl. No. 16/262,800, 9 pages. |
| Patent, dated Aug. 30, 2019, received in Hong Kong Patent Application No. 15107537.8, which corresponds with U.S. Appl. No. 14/536,267, 9 pages. |
| Patent, dated Nov. 8, 2019, received in Hong Kong Patent Application No. 15108890.7, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Office Action, dated Jan. 29, 2016, received in Japanese Patent Application No. 2015-511652, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Notice of Allowance, dated Sep. 26, 2016, received in Japanese Patent Application No. 2015-511652, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
| Office Action, dated Mar. 3, 2017, received in Japanese Patent Application No. 2016-125839, which corresponds with U.S. Appl. No. 14/536,267, 6 pages. |
| Notice of Allowance, dated Nov. 17, 2017, received in Japanese Patent Application No. 2016-125839, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
| Office Action, dated Feb. 4, 2019, received in Japanese Patent Application No. 2017-237035, which corresponds with U.S. Appl. No. 14/536,267, 7 pages. |
| Notice of Allowance, dated Sep. 9, 2019, received in Japanese Patent Application No. 2017-237035, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
| Patent, dated Sep. 27, 2019, received in Japanese Patent Application No. 2017-237035, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Office Action, dated Dec. 4, 2015, received in Korean Patent Application No. 2014-7034530, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Notice of Allowance, dated Sep. 1, 2016, received in Korean Patent Application No. 2014-7034530, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Office Action, dated Jan. 5, 2017, received in Korean Patent Application No. 2016-7029533, which corresponds with U.S. Appl. No. 14/536,267, 2 pages. |
| Notice of Allowance, dated Sep. 1, 2017, received in Korean Patent Application No. 2016-7029533, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Patent, dated Dec. 1, 2017, received in Korean Patent Application No. 2016-7029533, which corresponds with U.S. Appl. No. 14/536,267, 2 pages. |
| Office Action, dated Jan. 29, 2018, received in Korean Patent Application No. 2017-7034838, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Notice of Allowance, dated Dec. 3, 2018, received in Korean Patent Application No. 2017-7034838, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
| Patent, dated Mar. 4, 2019, received in Korean Patent Application No. 2017-7034838, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Office Action, dated Apr. 7, 2017, received in U.S. Appl. No. 14/536,291, 11 pages. |
| Notice of Allowance, dated Dec. 1, 2017, received in U.S. Appl. No. 14/536,291, 19 pages. |
| Notice of Allowance, dated Mar. 20, 2018, received in U.S. Appl. No. 14/536,291, 5 pages. |
| Office Action, dated Aug. 18, 2015, received in Australian Patent Application No. 2013259642, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Office Action, dated Jul. 25, 2016, received in Australian Patent Application No. 2013259642, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Office Action, dated Aug. 10, 2016, received in Australian Patent Application No. 2013259642, which corresponds with U.S. Appl. No. 14/536,291, 4 pages. |
| Office Action, dated Jul. 21, 2017, received in Australian Patent Application No. 2016216658, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Notice of Acceptance, dated Jul. 19, 2018, received in Australian Patent Application No. 2016216658, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Patent, dated Nov. 30, 2018, received in Australian Patent Application No. 2016216658, which corresponds with U.S. Appl. No. 14/536,291, 4 pages. |
| Innovation Patent, dated Sep. 1, 2016, received in Australian Patent Application No. 2016101481, which corresponds with U.S. Appl. No. 14/536,291, 1 page. |
| Office Action, dated Sep. 29, 2016, received in Australian Patent Application No. 2016101481, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Office Action, dated Oct. 23, 2017, received in Chinese Patent Application No. 201380035986.X, which corresponds with U.S. Appl. No. 14/536,291, 9 pages. |
| Notice of Allowance, dated Jun. 24, 2020, received in Chinese Patent Application No. 201710781246.0, which corresponds with U.S. Appl. No. 14/536,291, 5 pages. |
| Patent, dated Jul. 31, 2020, received in Chinese Patent Application No. 201710781246.0, which corresponds with U.S. Appl. No. 14/536,291, 6 pages. |
| Office Action, dated Jul. 17, 2020, received in Chinese Patent Application No. 2018100116175.X, which corresponds with U.S. Appl. No. 14/536,291, 15 pages. |
| Office Action, dated Nov. 17, 2020, received in Chinese Patent Application No. 2018100116175.X, which corresponds with U.S. Appl. No. 14/536,291, 16 pages. |
| Notice of Allowance, dated Mar. 29, 2021, received in Chinese Patent Application No. 2018100116175.X, which corresponds with U.S. Appl. No. 14/536,291, 1 page. |
| Patent, dated Apr. 27, 2021, received in Chinese Patent Application No. 2018100116175.X, which corresponds with U.S. Appl. No. 14/536,291, 6 pages. |
| Office Action, dated Jan. 7, 2016, received in European Patent Application No. 13724107.1, which corresponds with U.S. Appl. No. 14/536,291, 11 pages. |
| Office Action, dated Aug. 22, 2016, received in European Patent Application No. 13724107.1, which corresponds with U.S. Appl. No. 14/536,291, 7 pages. |
| Office Action, dated Mar. 23, 2017, received in European Patent Application No. 13724107.1, which corresponds with U.S. Appl. No. 14/536,291, 8 pages. |
| Intention to Grant, dated Jan. 8, 2019, received in European Patent Application No. 17186744.3, which corresponds with U.S. Appl. No. 14/536,291, 7 pages. |
| Decision to Grant, dated Oct. 31, 2019, received in European Patent Application No. 17186744.3, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Patent, dated Nov. 27, 2019, received in European Patent Application No. 17186744.3, which corresponds with U.S. Appl. No. 14/536,291, 4 pages. |
| Office Action, dated Mar. 8, 2016, received in Japanese Patent Application No. 2015-511655, which corresponds with U.S. Appl. No. 14/536,291, 4 pages. |
| Final Office Action, dated Dec. 22, 2016, received in Japanese Patent Application No. 2015-511655, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Office Action, dated Jun. 29, 2018, received in Japanese Patent Application No. 2017-083027, which corresponds with U.S. Appl. No. 14/536,291, 5 pages. |
| Patent, dated Feb. 22, 2019, received in Japanese Patent Application No. 2017-083027, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Notice of Allowance, dated Jan. 15, 2019, received in Japanese Patent Application No. 2017-083027, which corresponds with U.S. Appl. No. 14/536,291, 5 pages. |
| Office Action, dated Oct. 19, 2017, received in U.S. Appl. No. 14/608,985, 13 pages. |
| Notice of Allowance, dated Apr. 20, 2018, received in U.S. Appl. No. 14/608,985, 5 pages. |
| Office Action, dated Jan. 15, 2016, received in Australian Patent Application No. 2013368445, which corresponds with U.S. Appl. No. 14/608,985, 3 pages. |
| Notice of Allowance, dated Jan. 18, 2017, received in Australian Patent Application No. 2013368445, which corresponds with U.S. Appl. No. 14/608,985, 3 pages. |
| Patent, dated May 18, 2017, received in Australian Patent Application No. 2013368445, which corresponds with U.S. Appl. No. 14/608,985, 1 page. |
| Office Action, dated May 19, 2017, received in Chinese Patent Application No. 201380068399.0, which corresponds with U.S. Appl. No. 14/608,985, 5 pages. |
| Notice of Allowance, dated Sep. 19, 2017, received in Chinese Patent Application No. 201380068399.0, which corresponds with U.S. Appl. No. 14/608,985, 3 pages. |
| Patent, dated Dec. 8, 2017, received in Chinese Patent Application No. 201380068399.0, which corresponds with U.S. Appl. No. 14/608,985, 4 pages. |
| Office Action, dated Jul. 25, 2016, received in European Patent Application No. 13811032.5, which corresponds with U.S. Appl. No. 14/608,985, 8 pages. |
| Office Action, dated Feb. 27, 2017, received in European Patent Application No. 13811032.5, which corresponds with U.S. Appl. No. 14/608,985, 6 pages. |
| Summons, dated Oct. 6, 2017, received in European Patent Application No. 13811032.5, which corresponds with U.S. Appl. No. 14/608,985, 6 pages. |
| Intention to Grant, dated Jan. 16, 2019, received in European Patent Application No. 13811032.5, which corresponds with U.S. Appl. No. 14/608,985, 9 pages. |
| Decision to Grant, dated Aug. 1, 2019, received in European Patent Application No. 13811032.5, which corresponds with U.S. Appl. No. 14/608,985, 2 pages. |
| Certificate of Grant, dated Aug. 28, 2019, received in European Patent Application No. 13811032.5, which corresponds with U.S. Appl. No. 14/608,985, 4 pages. |
| Certificate of Grant, dated Jun. 29, 2018, received in Hong Kong Patent Application No. 15112851.6, which corresponds with U.S. Appl. No. 14/608,985, 2 pages. |
| Office Action, dated Apr. 25, 2016, received in Japanese Patent Application No. 2015-550384, which corresponds with U.S. Appl. No. 14/608,985, 4 pages. |
| Notice of Allowance, dated Jan. 24, 2017, received in Japanese Patent Application No. 2015-550384, which corresponds with U.S. Appl. No. 14/608,985, 5 pages. |
| Patent, dated Feb. 24, 2017, received in Japanese Patent Application No. 2015-550384, which corresponds with U.S. Appl. No. 14/608,985, 2 pages. |
| Office Action, dated Nov. 4, 2016, received in Korean Patent Application No. 2015-7019984, which corresponds with U.S. Appl. No. 14/608,985, 8 pages. |
| Notice of Allowance, dated Sep. 19, 2017, received in Korean Patent Application No. 2015-7019984, which corresponds with U.S. Appl. No. 14/608,985, 4 pages. |
| Patent, dated Dec. 19, 2017, received in Korean Patent Application No. 2015-7019984, which corresponds with U.S. Appl. No. 14/608,985, 3 pages. |
| Office Action, dated Mar. 24, 2017, received in U.S. Appl. No. 14/609,006, 13 pages. |
| Final Office Action, dated Sep. 21, 2017, received in U.S. Appl. No. 14/609,006, 17 pages. |
| Office Action, dated Mar. 20, 2018, received in U.S. Appl. No. 14/609,006, 13 pages. |
| Office Action, dated Oct. 11, 2018, received in U.S. Appl. No. 14/609,006, 12 pages. |
| Final Office Action, dated May 23, 2019, received in U.S. Appl. No. 14/609,006, 14 pages. |
| Office Action, dated Jan. 7, 2020, received in U.S. Appl. No. 14/609,006, 17 pages. |
| Final Office Action, dated Jun. 15, 2020, received in U.S. Appl. No. 14/609,006, 19 pages. |
| Office Action, dated Apr. 19, 2017, received in U.S. Appl. No. 14/536,296, 12 pages. |
| Final Office Action, dated Nov. 2, 2017, received in U.S. Appl. No. 14/536,296, 13 pages. |
| Notice of Allowance, dated Mar. 14, 2018, received in U.S. Appl. No. 14/536,296, 8 pages. |
| Office Action, dated Nov. 1, 2017, received in U.S. Appl. No. 14/536,648, 22 pages. |
| Final Office Action, dated Aug. 7, 2018, received in U.S. Appl. No. 14/536,648, 14 pages. |
| Office Action, dated Jan. 2, 2019, received in U.S. Appl. No. 14/536,648 12 pages. |
| Notice of Allowance, dated Jul. 2, 2019, received in U.S. Appl. No. 14/536,648, 5 pages. |
| Office Action, dated Jul. 21, 2017, received in Australian Patent Application No. 2016247194, which corresponds with U.S. Appl. No. 14/536,648, 3 pages. |
| Notice of Acceptance, dated Jul. 19, 2018, received in Australian Patent Application No. 2016247194, which corresponds with U.S. Appl. No. 14/536,648, 3 pages. |
| Office Action, dated Jul. 24, 2020, received in Chinese Patent Application No. 201711422121.5, which corresponds with U.S. Appl. No. 14/536,648, 10 pages. |
| Notice of Allowance, dated Feb. 2, 2021, received in Chinese Patent Application No. 201711422121.5, which corresponds with U.S. Appl. No. 14/536,648, 1 page. |
| Patent, dated Mar. 9, 2021, received in Chinese Patent Application No. 201711422121.5, which corresponds with U.S. Appl. No. 14/536,648, 7 pages. |
| Intention to Grant, dated Apr. 1, 2019, received in European Patent Application No. 17153418.3, which corresponds with U.S. Appl. No. 14/536,648, 7 pages. |
| Decision to Grant, dated Aug. 16, 2019, received in European Patent Application No. 17153418.3, which corresponds with U.S. Appl. No. 14/536,648, 3 pages. |
| Grant Certificate, dated Sep. 11, 2019, received in European Patent Application No. 17153418.3, which corresponds with U.S. Appl. No. 14/536,648, 3 pages. |
| Office Action, dated Apr. 27, 2018, received in Japanese Patent Application No. 2017-008764, which corresponds with U.S. Appl. No. 14/536,648, 5 pages. |
| Notice of Allowance, dated Feb. 4, 2019, received in Japanese Patent Application No. 2017-008764, which corresponds with U.S. Appl. No. 14/536,648, 5 pages. |
| Patent, dated Mar. 1, 2019, received in Japanese Patent Application No. 2017-008764, which corresponds with U.S. Appl. No. 14/536,648, 3 pages. |
| Office Action, dated Jan. 19, 2017, received in U.S. Appl. No. 14/609,042, 12 pages. |
| Notice of Allowance, dated Jul. 10, 2017, received in U.S. Appl. No. 14/609,042, 8 pages. |
| Office Action, dated Aug. 24, 2018, received in Japanese Patent Application No. 2017-113598, which corresponds with U.S. Appl. No. 14/609,042, 6 pages. |
| Notice of Allowance, dated Apr. 9, 2019, received in Japanese Patent Application No. 2017-113598, which corresponds with U.S. Appl. No. 14/609,042, 5 pages. |
| Patent, dated Apr. 19, 2019, received in Japanese Patent Application No. 2017-113598, which corresponds with U.S. Appl. No. 14/609,042, 2 pages. |
| Notice of Allowance, dated Dec. 17, 2018, received in Korean Patent Application No. 2017-7008614, which corresponds with U.S. Appl. No. 14/609,042, 5 pages. |
| Patent, dated Mar. 8, 2019, received in Korean Patent Application No. 2017-7008614, which corresponds with U.S. Appl. No. 14/609,042, 4 pages. |
| Office Action, dated Mar. 31, 2016, received in U.S. Appl. No. 14/864,737, 17 pages. |
| Notice of Allowance, dated Feb. 27, 2017, received in U.S. Appl. No. 14/864,737, 9 pages. |
| Notice of Allowance, dated Jun. 19, 2017, received in U.S. Appl. No. 14/864,737, 8 pages. |
| Office Action, dated Apr. 16, 2018, received in Australian Patent Application No. 2016233792, which corresponds with U.S. Appl. No. 14/864,737, 2 pages. |
| Notice of Acceptance, dated Mar. 12, 2019, received in Australian Patent Application No. 2016233792, which corresponds with U.S. Appl. No. 14/864,737, 5 pages. |
| Certificate of Grant, dated Jul. 4, 2019, received in Australian Patent Application No. 2016233792, which corresponds with U.S. Appl. No. 14/864,737, 1 page. |
| Office Action, dated Sep. 11, 2018, received in Chinese Patent Application No. 201610159295.6, which corresponds with U.S. Appl. No. 14/864,737, 6 pages. |
| Notice of Allowance, dated Apr. 17, 2019, received in Chinese Patent Application No. 201610159295.6, which corresponds with U.S. Appl. No. 14/864,737, 3 pages. |
| Patent, dated May 31, 2019, received in Chinese Patent Application No. 201610159295.6, which corresponds with U.S. Appl. No. 14/864,737, 7 pages. |
| Notice of Allowance, dated Jul. 1, 2016, received in Chinese Patent Application No. 201620214376.7, which corresponds with U.S. Appl. No. 14/864,737, 3 pages. |
| Patent, dated Aug. 3, 2016, received in Chinese Patent Application No. 201620214376.7, which corresponds with U.S. Appl. No. 14/864,737, 5 pages. |
| Certificate of Registration, dated Jun. 20, 2016, received in German Patent Application No. 202016001845.1, which corresponds with U.S. Appl. No. 14/864,737, 3 pages. |
| Office Action, dated Apr. 5, 2016, received in Danish Patent Application No. 201500577, which corresponds with U.S. Appl. No. 14/864,737, 7 pages. |
| Intention to Grant, dated Aug. 2, 2016, received in Danish Patent Application No. 201500577, which corresponds with U.S. Appl. No. 14/864,737, 2 pages. |
| Decision to grant, dated Mar. 29, 2018, received in European Patent Application No. 16710871.1, which corresponds with U.S. Appl. No. 14/864,737, 2 pages. |
| Grant Certificate, dated Apr. 25, 2018, received in European Patent Application No. 16710871.1, which corresponds with U.S. Appl. No. 14/864,737, 2 pages. |
| Office Action, dated May 15, 2017, received in Japanese Patent Application No. 2016-558331, which corresponds with U.S. Appl. No. 14/864,737, 5 pages. |
| Notice of Allowance, dated Jun. 23, 2017, received in Japanese Patent Application No. 2016-558331, which corresponds with U.S. Appl. No. 14/864,737, 5 pages. |
| Patent, dated Jul. 28, 2017, received in Japanese Patent Application No. 2016-558331, which corresponds with U.S. Appl. No. 14/864,737, 3 pages. |
| Office Action, dated Feb. 14, 2018, received in Korean Patent Application No. 2017-7030129, which corresponds with U.S. Appl. No. 14/864,737, 17 pages. |
| Patent, dated Dec. 26, 2018, received in Korean Patent Application No. 2017-7030129, which corresponds with U.S. Appl. No. 14/864,737, 4 pages. |
| Patent, dated Jul. 12, 2017, received in Dutch Patent Application No. 2016452, which corresponds with U.S. Appl. No. 14/864,737, 2 pages. |
| Office Action, dated Jun. 27, 2016, received in U.S. Appl. No. 14/866,981, 22 pages. |
| Notice of Allowance, dated Oct. 24, 2016, received in U.S. Appl. No. 14/866,981, 7 pages. |
| Notice of Allowance, dated Feb. 10, 2017, received in U.S. Appl. No. 14/866,981, 5 pages. |
| Office Action, dated May 10, 2016, received in Australian Patent Application No. 2016100254, which corresponds with U.S. Appl. No. 14/866,981, 6 pages. |
| Patent, dated Nov. 2, 2016, received in Australian Patent Application No. 2016100254, which corresponds with U.S. Appl. No. 14/866,981, 1 page. |
| Office Action, dated Nov. 5, 2018, received in Chinese Patent Application No. 201610131415.1, which corresponds with U.S. Appl. No. 14/866,981, 6 pages. |
| Office Action, dated Jul. 16, 2019, received in Chinese Patent Application No. 201610131415.1, which corresponds with U.S. Appl. No. 14/866,981, 4 pages. |
| Office Action, dated Mar. 16, 2020, received in Chinese Patent Application No. 201610131415.1, which corresponds with U.S. Appl. No. 14/866,981, 3 pages. |
| Notice of Allowance, dated Dec. 4, 2020, received in Chinese Patent Application No. 201610131415.1, which corresponds with U.S. Appl. No. 14/866,981, 3 pages. |
| Patent, dated Jan. 22, 2021, received in Chinese Patent Application No. 201610131415.1, which corresponds with U.S. Appl. No. 14/866,981, 6 pages. |
| Notice of Allowance, dated Jul. 27, 2016, received in Chinese Patent Application No. 201620176169.7, which corresponds with U.S. Appl. No. 14/866,981, 3 pages. |
| Patent, dated Sep. 28, 2016, received in Chinese Patent Application No. 201620176169.7, which corresponds with U.S. Appl. No. 14/866,981, 4 pages. |
| Certificate of Registration, dated Jun. 20, 2016, received in German Patent Application No. 202016001514.2, which corresponds with U.S. Appl. No. 14/864,737, 3 pages. |
| Office Action, dated Mar. 18, 2016, received in Danish Patent Application No. 201500575, which corresponds with U.S. Appl. No. 14/866,981, 9 pages. |
| Office Action, dated Dec. 5, 2016, received in Danish Patent Application No. 201500575, which corresponds with U.S. Appl. No. 14/866,981, 3 pages. |
| Office Action, dated Jul. 7, 2017, received in Danish Patent Application No. 201500575, 4 pages. |
| Patent, Nov. 16, 2017, received in Dutch Patent Application No. 2016375, which corresponds with U.S. Appl. No. 14/866,981, 2 pages. |
| Office Action, dated Dec. 15, 2017, received in U.S. Appl. No. 14/866,159, 35 pages. |
| Notice of Allowance, dated May 18, 2018, received in U.S. Appl. No. 14/866,159, 8 pages. |
| Office Action, dated May 19, 2016, received in Australian Patent Application No. 2016100251, which corresponds with U.S. Appl. No. 14/866,159, 5 pages. |
| Office Action, dated Jun. 5, 2018, received in Chinese Patent Application No. 201610137839.9, which corresponds with U.S. Appl. No. 14/866,159, 11 pages. |
| Notice of Allowance, dated Dec. 6, 2018, received in Chinese Patent Application No. 201610137839.9, which corresponds with U.S. Appl. No. 14/866,159, 3 pages. |
| Patent, dated Feb. 19, 2019, received in Chinese Patent Application No. 201610137839.9, which corresponds with U.S. Appl. No. 14/866,159, 6 pages. |
| Office Action, dated Jul. 5, 2016, received in Chinese Patent Application No. 201620186008.6, which corresponds with U.S. Appl. No. 14/866,159, 3 pages. |
| Certificate of Registration, dated Jun. 16, 2016, received in German Patent No. 202016001483.9, which corresponds with U.S. Appl. No. 14/866,159, 3 pages. |
| Office Action, dated Mar. 9, 2016, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 11 pages. |
| Office Action, dated Sep. 27, 2016, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 4 pages. |
| Office Action, dated Mar. 14, 2017, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 5 pages. |
| Office Action, dated Jul. 6, 2017, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 3 pages. |
| Office Action, dated Jan. 10, 2018, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 2 pages. |
| Notice of Allowance, dated Mar. 21, 2018, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 2 pages. |
| Patent, dated May 22, 2018, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 2 pages. |
| Intention to Grant, dated Oct. 28, 2019, received in European Patent Application No. 16707356.8, which corresponds with U.S. Appl. No. 14/866,159, 7 pages. |
| Decision to Grant, dated Mar. 5, 2020, received in European Patent Application No. 16707356.8, which corresponds with U.S. Appl. No. 14/866,159, 2 pages. |
| Patent, dated Apr. 1, 2020, received in European Patent Application No. 16707356.8, which corresponds with U.S. Appl. No. 14/866,159, 3 pages. |
| Patent, dated Sep. 7, 2017, received in Dutch Patent Application No. 2016377, which corresponds with U.S. Appl. No. 14/866,159, 4 pages. |
| Office Action, dated Oct. 6, 2017, received in U.S. Appl. No. 14/868,078, 40 pages. |
| Notice of Allowance, dated May 24, 2018, received in U.S. Appl. No. 14/868,078, 6 pages. |
| Innovation Patent, dated Aug. 4, 2016, received in Australian Patent Application No. 2016101201, which corresponds with U.S. Appl. No. 14/868,078, 1 page. |
| Office Action, dated Oct. 12, 2016, received in Australian Patent Application No. 2016101201, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
| Notice of Allowance, dated Sep. 1, 2017, received in Australian Patent Application No. 2016229421, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
| Certificate of Grant, dated Jan. 3, 2018, received in Australian Patent Application No. 2016229421, which corresponds with U.S. Appl. No. 14/868,078, 1 page. |
| Office Action, dated Feb. 7, 2019, received in Australian Patent Application No. 2017258967, which corresponds with U.S. Appl. No. 14/868,078, 3 page. |
| Notice of Acceptance, dated Jun. 21, 2019, received in Australian Patent Application No. 2017258967, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
| Certificate of Grant, dated Oct. 17, 2019, received in Australian Patent Application No. 2017258967, which corresponds with U.S. Appl. No. 14/868,078, 4 page. |
| Office Action, dated Aug. 20, 2018, received in Chinese Patent Application No. 01610130348.1, which corresponds with U.S. Appl. No. 14/868,078, 6 pages. |
| Office Action, dated Feb. 26, 2019, received in Chinese Patent Application No. 01610130348.1, which corresponds with U.S. Appl. No. 14/868,078, 4 pages. |
| Notice of Allowance, dated May 6, 2019, received in Chinese Patent Application No. 01610130348.1, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
| Patent, dated Jul. 5, 2019, received in Chinese Patent Application No. 201610130348.1, which corresponds with U.S. Appl. No. 14/868,078, 6 pages. |
| Notice of Allowance, dated Oct. 1, 2016, received in Chinese Patent Application No. 201620175847.8, which corresponds with U.S. Appl. No. 14/868,078, 1 page. |
| Office Action, dated Nov. 21, 2019, received in Chinese Patent Application No. 201680011338.4, which corresponds with U.S. Appl. No. 14/868,078, 8 pages. |
| Office Action, dated May 19, 2020, received in Chinese Patent Application No. 201680011338.4, which corresponds with U.S. Appl. No. 14/868,078, 4 pages. |
| Office Action, dated Jun. 30, 2020, received in Chinese Patent Application No. 201680011338.4, which correspondence with U.S. Appl. No. 14/868,078, 4 pages. |
| Patent, dated Dec. 11, 2020, received in Chinese Patent Application No. 201680011338.4, which correspondence with U.S. Appl. No. 14/868,078, 3 pages. |
| Certificate of Registration, dated Jun. 30, 2016, received in German Patent Application No. 20201600156.9, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
| Office Action, dated Mar. 30, 2016, received in Danish Patent Application No. 201500588, which corresponds with U.S. Appl. No. 14/868,078, 9 pages. |
| Office Action, dated Sep. 2, 2016, received in Danish Patent Application No. 201500588, which corresponds with U.S. Appl. No. 14/868,078, 4 pages. |
| Notice of Allowance, dated Jan. 30, 2017, received in received in Danish Patent Application No. 201500588, which corresponds with U.S. Appl. No. 14/868,078, 2 pages. |
| Notice of Allowance, dated May 2, 2017, received in received in Danish Patent Application No. 201500588, which corresponds with U.S. Appl. No. 14/868,078, 2 pages. |
| Patent, dated Sep. 11, 2017, received in Danish Patent Application No. 201500588, which corresponds with U.S. Appl. No. 14/868,078, 5 pages. |
| Office Action, dated Apr. 25, 2018, received in European Patent Application No. 16708916.8, which corresponds with U.S. Appl. No. 14/868,078, 6 pages. |
| Intention to Grant, dated May 10, 2019, received in European Patent Application No. 16708916.8, which corresponds with U.S. Appl. No. 14/868,078, 5 pages. |
| Decision to Grant, dated Sep. 12, 2019, received in European Patent Application No. 16708916.8, which corresponds with U.S. Appl. No. 14/868,078, 2 pages. |
| Patent, dated Oct. 9, 2019, received in European Patent Application No. 16708916.8, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
| Office Action, dated Oct. 25, 2018, received in European Patent Application No. 17184437.6, which corresponds with U.S. Appl. No. 14/868,078, 6 pages. |
| Intention to Grant, dated May 22, 2019, received in European Patent Application No. 17184437.6, which corresponds with U.S. Appl. No. 14/868,078, 7 pages. |
| Decision to Grant, dated Sep. 19, 2019, received in European Patent Application No. 17184437.6, which corresponds with U.S. Appl. No. 14/868,078, 2 pages. |
| Patent, dated Oct. 16, 2019, received in European Patent Application No. 17184437.6, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
| Patent, dated Jul. 12, 2017, received in Dutch Patent Application No. 2016376, which corresponds with U.S. Appl. No. 14/868,078, 2 pages. |
| Office Action, dated May 9, 2016, received in U.S. Appl. No. 14/863,432, 26 pages. |
| Notice of Allowance, dated Nov. 14, 2016, received in U.S. Appl. No. 14/863,432, 7 pages. |
| Notice of Allowance, dated Apr. 27, 2017, received in U.S. Appl. No. 14/863,432, 7 pages. |
| Notice of Allowance, dated Sep. 18, 2017, received in U.S. Appl. No. 14/863,432, 8 pages. |
| Office Action, dated Aug. 19, 2016, received in Australian Patent Application No. 2016100647, which corresponds with U.S. Appl. No. 14/863,432, 5 pages. |
| Office Action, dated Dec. 4, 2018, received in Chinese Patent Application No. 201610342313.4, which corresponds with U.S. Appl. No. 14/863,432, 5 pages. |
| Office Action, dated Jun. 17, 2019, received in Chinese Patent Application No. 201610342313.4, which corresponds with U.S. Appl. No. 14/863,432, 4 pages. |
| Office Action, dated Nov. 5, 2019, received in Chinese Patent Application No. 201610342313.4, which corresponds with U.S. Appl. No. 14/863,432, 4 pages. |
| Notice of Allowance, dated Mar. 20, 2020, received in Chinese Patent Application No. 201610342313.4, which corresponds with U.S. Appl. No. 14/863,432, 6 pages. |
| Patent, dated May 12, 2020, received in Chinese Patent Application No. 201610342313.4, which corresponds with U.S. Appl. No. 14/863,432, 7 pages. |
| Notice of Allowance, dated Jan. 12, 2017, received in Chinese Patent Application No. 201620470063.8, which corresponds with U.S. Appl. No. 14/863,432, 1 page. |
| Patent, dated Feb. 8, 2017, received in Chinese Patent Application No. 201620470063.8, which corresponds with U.S. Appl. No. 14/863,432, 5 pages. |
| Office Action, dated Apr. 4, 2016, received in Danish Patent Application No. 201500582, which corresponds with U.S. Appl. No. 14/863,432, 10 pages. |
| Office Action, dated Oct. 7, 2016, received in Danish Patent Application No. 201500582, which corresponds with U.S. Appl. No. 14/863,432, 6 pages. |
| Office Action, dated Jun. 12, 2017, received in Danish Patent Application No. 201500582, which corresponds with U.S. Appl. No. 14/863,432, 5 pages. |
| Office Action, dated Jan. 10, 2020, received in Japanese Patent Application No. 2018-243773, which corresponds with U.S. Appl. No. 14/863,432, 6 pages. |
| Office Action, dated Jul. 17, 2020, received in Japanese Patent Application No. 2018-243773, which corresponds with U.S. Appl. No. 14/863,432, 5 pages. |
| Notice of Allowance, dated Dec. 4, 2020, received in Japanese Patent Application No. 2018-243773, which corresponds with U.S. Appl. No. 14/863,432, 5 pages. |
| Patent, dated Jan. 5, 2021, received in Japanese Patent Application No. 2018-243773, which corresponds with U.S. Appl. No. 14/863,432, 4 pages. |
| Notice of Allowance, dated Jul. 13, 2020, received in Korean Patent Application No. 2020-7015964, which corresponds with U.S. Appl. No. 14/863,432, 6 pages. |
| Patent, dated Oct. 12, 2020, received in Korean Patent Application No. 2020-7015964, which corresponds with U.S. Appl. No. 14/863,432, 8 pages. |
| Grant, dated Jul. 21, 2017, received in Dutch Patent Application No. 2016801, which corresponds with U.S. Appl. No. 14/871,227, 8 pages. |
| Office Action, dated Oct. 13, 2016, received in U.S. Appl. No. 14/866,511, 27 pages. |
| Final Office Action, dated Jan. 27, 2017, received in U.S. Appl. No. 14/866,511, 26 pages. |
| Notice of Allowance, dated Oct. 4, 2017, received in U.S. Appl. No. 14/866,511, 37 pages. |
| Office Action, dated Aug. 19, 2016, received in U.S. Appl. No. 14/291,880—to be referenced in 7294 per Robby), 19 pages. |
| Notice of Allowance, dated Jan. 10, 2017, received in U.S. Appl. No. 14/291,880—to be referenced in 7294 per Robby), 8 pages. |
| Patent, dated Aug. 8, 2016, received in Australian Patent Application 2016100653, corresponds with U.S. Appl. No. 14/866,511, 1 page. |
| Office Action, dated Dec. 5, 2018, received in Chinese Patent Application No. 201610342264.4, which corresponds with U.S. Appl. No. 14/866,511, 4 pages. |
| Office Action, dated Jul. 11, 2019, received in Chinese Patent Application No. 201610342264.4, which corresponds with U.S. Appl. No. 14/866,511, 4 pages. |
| Office Action, dated Sep. 17, 2019, received in Chinese Patent Application No. 201610342264.4, which corresponds with U.S. Appl. No. 14/866,511, 3 pages. |
| Notice of Allowance, dated Nov. 28, 2019, received in Chinese Patent Application No. 201610342264.4, which corresponds with U.S. Appl. No. 14/866,511, 3 pages. |
| Patent, dated Feb. 7, 2020, received in Chinese Patent Application No. 201610342264.4, which corresponds with U.S. Appl. No. 14/866,511, 7 pages. |
| Notice of Allowance, dated Jan. 12, 2017, received in Chinese Patent Application No. 201620470281.1, which corresponds with U.S. Appl. No. 14/866,511, 1 page. |
| Office Action, dated Mar. 22, 2016, received in Danish Patent Application No. 201500576, which corresponds with U.S. Appl. No. 14/866,511, 10 pages. |
| Intention to Grant, dated Jun. 8, 2016, received in Danish Patent Application No. 201500576, which corresponds with U.S. Appl. No. 14/866,511, 2 pages. |
| Grant, dated Aug. 26, 2016, received in Danish Patent Application No. 201500576, which corresponds with U.S. Appl. No. 14/866,511, 2 pages. |
| Patent, dated Jan. 23, 2017, received in Danish Patent Application No. 201500576, which corresponds with U.S. Appl. No. 14/866,511, 3 pages. |
| Office Action, dated Nov. 24, 2017, received in European Patent Application No. 16727900.9, which corresponds with U.S. Appl. No. 14/866,511, 5 pages. |
| Office Action, dated May 24, 2018, received in European Patent Application No. 16727900.9, which corresponds with U.S. Appl. No. 14/866,511, 7 pages. |
| Office Action, dated Jan. 2, 2019, received in European Patent Application No. 16727900.9, which corresponds with U.S. Appl. No. 14/866,511, 5 pages. |
| Intention to Grant, dated Jul. 5, 2019, received in European Patent Application No. 16727900.9, which corresponds with U.S. Appl. No. 14/866,511, 5 pages. |
| Decision to Grant, dated Dec. 5, 2019, received in European Patent Application No. 16727900.9, which corresponds with U.S. Appl. No. 14/866,511, 2 pages. |
| Patent, dated Jan. 1, 2020, received in European Patent Application No. 16727900.9, which corresponds with U.S. Appl. No. 14/866,511, 3 pages. |
| Office Action, dated Jun. 9, 2017, received in Japanese Patent Application No. 2016558214, which corresponds with U.S. Appl. No. 14/866,511, 6 pages. |
| Notice of Allowance, dated Jul. 14, 2017, received in Japanese Patent Application No. 2016558214, which corresponds with U.S. Appl. No. 14/866,511, 5 pages. |
| Patent, dated Aug. 18, 2017, received in Japanese Patent Application No. 2016558214, which corresponds with U.S. Appl. No. 14/866,511, 3 pages. |
| Office Action, dated Apr. 24, 2020, received in Korean Patent Application No. 2020-7003065, which corresponds with U.S. Appl. No. 14/866,511, 3 pages. |
| Notice of Allowance, dated Jul. 29, 2020, received in Korean Patent Application No. 2020-7003065, which corresponds with U.S. Appl. No. 14/866,511, 5 pages. |
| Patent, dated Oct. 29, 2020, received in Korean Patent Application No. 2020-7003065, which corresponds with U.S. Appl. No. 14/866,511, 5 pages. |
| Office Action, dated May 10, 2016, received in U.S. Appl. No. 14/866,489, 15 pages. |
| Final Office Action, dated Sep. 16, 2016, received in U.S. Appl. No. 14/866,489, 24 pages. |
| Notice of Allowance, dated Apr. 27, 2017, received in U.S. Appl. No. 14/866,489 (7298), 27 pages. |
| Notice of Allowance, dated Jul. 6, 2017, received in U.S. Appl. No. 14/866,489, 12 pages. |
| Office Action, dated Mar. 28, 2016, received in U.S. Appl. No. 14/869,899, 17 pages. |
| Office Action, dated Jun. 28, 2016, received in U.S. Appl. No. 14/869,899, 5 pages. |
| Final Office Action, dated Sep. 2, 2016, received in U.S. Appl. No. 14/869,899, 22 pages. |
| Notice of Allowance, dated Feb. 28, 2017, received in U.S. Appl. No. 14/869,899, 9 pages. |
| Innovation Patent, dated Aug. 25, 2016, received in Australian Patent Application No. 2016101438, which corresponds with U.S. Appl. No. 14/869,899, 1 page. |
| Certificate of Examination, dated Oct. 11, 2016, received in Australian Patent Application No. 2016101438, which corresponds with U.S. Appl. No. 14/869,899, 1 page. |
| Notice of Acceptance, dated Aug. 23, 2018, received in Australian Patent Application No. 2018204611, which corresponds with U.S. Appl. No. 14/869,899, 3 pages. |
| Office Action, dated Nov. 6, 2020, received in Chinese Patent Application No. 201610871595.7, which corresponds with U.S. Appl. No. 14/869,899, 15 pages. |
| Notice of Allowance, dated Mar. 30, 2021, received in Chinese Patent Application No. 201610871595.7, which corresponds with U.S. Appl. No. 14/869,899, 1 page. |
| Patent, dated Jun. 4, 2021, received in Chinese Patent Application No. 201610871595.7, which corresponds with U.S. Appl. No. 14/869,899, 7 pages. |
| Office Action, dated Feb. 3, 2016, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 9 pages. |
| Office Action, dated Oct. 7, 2016, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 6 pages. |
| Office Action, dated Jul. 3, 2017, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 5 pages. |
| Office Action, dated Jan. 29, 2018, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 2 pages. |
| Notice of Allowance, dated Apr. 24, 2018, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 2 pages. |
| Patent, dated May 28, 2018, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 2 pages. |
| Office Action, dated Nov. 22, 2016, received in Danish Patent Application No. 201670594, which corresponds with U.S. Appl. No. 14/869,899, 9 pages. |
| Office Action, dated Dec. 14, 2017, received in Danish Patent Application No. 201670594, which corresponds with U.S. Appl. No. 14/869,899, 3 pages. |
| Office Action, dated May 1, 2018, received in Danish Patent Application No. 201670594, which corresponds with U.S. Appl. No. 14/869,899, 2 pages. |
| Office Action, dated Oct. 9, 2018, received in Danish Patent Application No. 201670594, which corresponds with U.S. Appl. No. 14/869,899, 2 pages. |
| Patent, dated Feb. 26, 2019, received in Danish Patent Application No. 201670594, which corresponds with U.S. Appl. No. 14/869,899, 3 pages. |
| Office Action, dated May 8, 2019, received in European Patent Application No. 18168939.9, which corresponds with U.S. Appl. No. 14/869,899, 10 pages. |
| Intention to Grant, dated Oct. 25, 2019, received in European Patent Application No. 18168939.9, which corresponds with U.S. Appl. No. 14/869,899, 8 pages. |
| Decision to Grant, dated Mar. 26, 2020, received in European Patent Application No. 18168939.9, which corresponds with U.S. Appl. No. 14/869,899, 3 pages. |
| Patent, dated Apr. 22, 2020, received in European Patent Application No. 18168939.9, which corresponds with U.S. Appl. No. 14/869,899, 3 pages. |
| Office Action, dated May 23, 2019, received in European Patent Application No. 18175195.9, which corresponds with U.S. Appl. No. 14/869,899, 10 pages. |
| Oral Summons, dated Dec. 6, 2019, received in European Patent Application No. 18175195.9, which corresponds with U.S. Appl. No. 14/869,899, 9 pages. |
| Office Action, dated Sep. 21, 2018, received in Japanese Patent Application No. 2018-100827, which corresponds with U.S. Appl. No. 14/869,899, 4 pages. |
| Notice of Allowance, dated Mar. 1, 2019, received in Japanese Patent Application No. 2018-100827, which corresponds with U.S. Appl. No. 14/869,899, 5 pages. |
| Patent, dated Apr. 5, 2019, received in Japanese Patent Application No. 2018-100827, which corresponds with U.S. Appl. No. 14/869,899, 5 pages. |
| Office Action, dated Oct. 5, 2018, received in Korean Patent Application No. 2018-7017213, which corresponds with U.S. Appl. No. 14/869,899, 3 pages. |
| Office Action, dated Mar. 22, 2019, received in Korean Patent Application No. 2018-7017213, which corresponds with U.S. Appl. No. 14/869,899, 6 pages. |
| Patent, dated May 10, 2019, received in Korean Patent Application No. 2018-7017213, which corresponds with U.S. Appl. No. 14/869,899, 8 pages. |
| Office Action, dated Mar. 4, 2016, received in U.S. Appl. No. 14/866,992, 30 pages. |
| Final Office Action, dated Jul. 29, 2016, received in U.S. Appl. No. 14/866,992, 35 pages. |
| Office Action, dated Apr. 13, 2017, received in U.S. Appl. No. 14/866,992, 34 pages. |
| Final Office Action, dated Oct. 3, 2017, received in U.S. Appl. No. 14/866,992, 37 pages. |
| Office Action, dated Jan. 29, 2018, received in U.S. Appl. No. 14/866,992, 44 pages. |
| Final Office Action, dated Aug. 28, 2018, received in U.S. Appl. No. 14/866,992, 52 pages. |
| Examiner's Answer, dated May 9, 2019, received in U.S. Appl. No. 14/866,992, 26 pages. |
| Innovation Patent, dated Sep. 22, 2016, received in Australian Patent Application No. 2016101418, which corresponds with U.S. Appl. No. 14/866,992, 1 page. |
| Office Action, dated Nov. 22, 2016, received in Australian Patent Application No. 2016101418, which corresponds with U.S. Appl. No. 14/866,992, 7 pages. |
| Office Action, dated Feb. 7, 2017, received in Australian Patent Application No. 2016101418, which corresponds with U.S. Appl. No. 14/866,992, 5 pages. |
| Office Action, dated Mar. 26, 2018, received in Australian Patent Application No. 2016304890, which corresponds with U.S. Appl. No. 14/866,992, 3 pages. |
| Notice of Acceptance, dated Mar. 12, 2019, received in Australian Patent Application No. 2016304890, which corresponds with U.S. Appl. No. 14/866,992, 5 pages. |
| Certificate of Grant, dated Jul. 4, 2019, received in Australian Patent Application No. 2016304890, which corresponds with U.S. Appl. No. 14/866,992, 1 page. |
| Office Action, dated Jan. 19, 2018, received in Australian Patent Application No. 201761478, which corresponds with U.S. Appl. No. 14/866,992, 6 pages. |
| Certificate of Grant, dated May 9, 2019, received in Australian Patent Application No. 201761478, which corresponds with U.S. Appl. No. 14/866,992, 3 pages. |
| Office Action, dated Sep. 12, 2019, received in Chinese Patent Application No. 201610658351.8, which corresponds with U.S. Appl. No. 14/866,992, 5 pages. |
| Office Action, dated Jan. 13, 2020, received in Chinese Patent Application No. 201610658351.8, which corresponds with U.S. Appl. No. 14/866,992, 3 pages. |
| Office Action, dated Jun. 30, 2020, received in Chinese Patent Application No. 201610658351.8, which corresponds with U.S. Appl. No. 14/866,992, 11 pages. |
| Office Action, dated Nov. 25, 2020, received in Chinese Patent Application No. 201610658351.8, which corresponds with U.S. Appl. No. 14/866,992, 9 pages. |
| Office Action, dated Jul. 24, 2020, received in Chinese Patent Application No. 201680041559.6, which corresponds with U.S. Appl. No. 14/866,992, 13 pages. |
| Notice of Allowance, dated Apr. 26, 2021, received in Chinese Patent Application No. 201680041559.6, which corresponds with U.S. Appl. No. 14/866,992, 1 page. |
| Patent, dated May 28, 2021, received in Chinese Patent Application No. 201680041559.6, which corresponds with U.S. Appl. No. 14/866,992, 7 pages. |
| Office Action, dated Mar. 18, 2016, received in Danish Patent Application No. 201500593, which corresponds with U.S. Appl. No. 14/866,992, 10 pages. |
| Office Action, dated Jun. 27, 2016, received in Danish Patent Application No. 201500593, which corresponds with U.S. Appl. No. 14/866,992, 7 pages. |
| Office Action, dated Feb. 6, 2017, received in Danish Patent Application No. 201500593, which corresponds with U.S. Appl. No. 14/866,992, 4 pages. |
| Office Action, dated Sep. 5, 2017, received in Danish Patent Application No. 201500593, which corresponds with U.S. Appl. No. 14/866,992, 6 pages. |
| Office Action, dated Oct. 12, 2018, received in European Patent Application No. 16758008.3, which corresponds with U.S. Appl. No. 14/866,992, 11 pages. |
| Summons, dated May 8, 2019, received in European Patent Application No. 16758008.3, which corresponds with U.S. Appl. No. 14/866,992, 14 pages. |
| Office Action, dated Jan. 11, 2019, received in Japanese Patent Application No. 2018-506425, which corresponds with U.S. Appl. No. 14/866,992, 6 pages. |
| Notice of Allowance, dated Jun. 18, 2019, received in Japanese Patent Application No. 2018-506425, which corresponds with U.S. Appl. No. 14/866,992, 5 pages. |
| Patent, dated Jul. 26, 2019, received in Japanese Patent Application No. 2018-506425, which corresponds with U.S. Appl. No. 14/866,992, 3 pages. |
| Notice of Allowance, dated Sep. 10, 2019, received in Korean Patent Application No. 2018-7003890, which corresponds with U.S. Appl. No. 14/866,992, 5 pages. |
| Patent, dated Oct. 11, 2019, received in Korean Patent Application No. 2018-7003890, which corresponds with U.S. Appl. No. 14/866,992, 5 pages. |
| Office Action, dated Feb. 12, 2018, received in U.S. Appl. No. 15/009,661, 36 pages. |
| Final Office Action, dated Sep. 19, 2018, received in U.S. Appl. No. 15/009,661, 28 pages. |
| Office Action, dated Jun. 28, 2019, received in U.S. Appl. No. 15/009,661, 33 pages. |
| Final Office Action, dated Dec. 30, 2019, received in U.S. Appl. No. 15/009,661, 33 pages. |
| Office Action, dated Sep. 16, 2020, received in U.S. Appl. No. 15/009,661, 37 pages. |
| Final Office Action, dated Feb. 26, 2021, received in U.S. Appl. No. 15/009,661, 46 pages. |
| Office Action, dated Jul. 1, 2021 received in U.S. Appl. No. 15/009,661, 52 pages. |
| Office Action, dated Jan. 18, 2018, received in U.S. Appl. No. 15/009,676, 21 Pages. |
| Notice of Allowance, dated Aug. 3, 2018, received in U.S. Appl. No. 15/009,676, 6 pages. |
| Notice of Allowance, dated Nov. 15, 2018, received in U.S. Appl. No. 15/009,676, 6 pages. |
| Office Action, dated Jul. 15, 2020, received in Chinese Patent Application No. 201680047125.7, which corresponds with U.S. Appl. No. 15/009,676, 11 pages. |
| Office Action, dated Nov. 30, 2020, received in Chinese Patent Application No. 201680047125.7, which corresponds with U.S. Appl. No. 15/009,676, 11 pages. |
| Notice of Allowance, dated Feb. 24, 2021, received in Chinese Patent Application No. 201680047125.7, which corresponds with U.S. Appl. No. 15/009,676, 1 page. |
| Patent, dated Apr. 27, 2021, received in Chinese Patent Application No. 201680047125.7, which corresponds with U.S. Appl. No. 15/009,676, 8 pages. |
| Intention to Grant, dated Apr. 7, 2020, received in European Patent Application No. 16756866.6, which corresponds with U.S. Appl. No. 15/009,676, 8 pages. |
| Decision to Grant, dated Aug. 27, 2020, received in European Patent Application No. 16756866.6, which corresponds with U.S. Appl. No. 15/009,676, 4 pages. |
| Patent, dated Sep. 23, 2020, received in European Patent Application No. 16756866.6, which corresponds with U.S. Appl. No. 15/009,676, 4 pages. |
| Office Action, dated Mar. 13, 2018, received in U.S. Appl. No. 15/009,688, 10 pages. |
| Notice of Allowance, dated Nov. 6, 2018, received in U.S. Appl. No. 15/009,688, 10 pages. |
| Office Action, dated Jun. 29, 2020, received in Chinese Patent Application No. 201680047164.7, which corresponds with U.S. Appl. No. 15/009,688, 7 pages. |
| Notice of Allowance, dated Oct. 9, 2020, received in Chinese Patent Application No. 201680047164.7, which corresponds with U.S. Appl. No. 15/009,688, 5 pages. |
| Patent, dated Nov. 10, 2020, received in Chinese Patent Application No. 201680047164.7, which corresponds with U.S. Appl. No. 15/009,688, 6 pages. |
| Intention to Grant, dated Mar. 16, 2020, received in European Patent Application No. 16753796.8, which corresponds with U.S. Appl. No. 15/009,688, 6 pages. |
| Decision to Grant, dated Sep. 24, 2020, received in European Patent Application No. 16753796.8, which corresponds with U.S. Appl. No. 15/009,688, 4 pages. |
| Certificate of Grant, dated Oct. 21, 2020, received in European Patent Application No. 16753796.8, which corresponds with U.S. Appl. No. 15/009,688, 4 pages. |
| Office Action, dated Nov. 30, 2015, received in U.S. Appl. No. 14/845,217, 24 pages. |
| Final Office Action, dated Apr. 22, 2016, received in U.S. Appl. No. 14/845,217, 36 pages. |
| Notice of Allowance, dated Aug. 26, 2016, received in U.S. Appl. No. 14/845,217, 5 pages. |
| Notice of Allowance, dated Jan. 4, 2017, received in U.S. Appl. No. 14/845,217, 5 pages. |
| Office Action, dated Feb. 3, 2016, received in U.S. Appl. No. 14/856,517, 36 pages. |
| Final Office Action, dated Jul. 13, 2016, received in U.S. Appl. No. 14/856,517, 30 pages. |
| Office Action, dated May 2, 2017, received in U.S. Appl. No. 14/856,517, 34 pages. |
| Final Office Action, dated Oct. 4, 2017, received in U.S. Appl. No. 14/856,517, 33 pages. |
| Notice of Allowance, dated Jun. 29, 2018, received in U.S. Appl. No. 14/856,517, 11 pages. |
| Office Action, dated Feb. 11, 2016, received in U.S. Appl. No. 14/856,519, 34 pages. |
| Final Office Action, dated Jul. 15, 2016, received in U.S. Appl. No. 14/856,519, 31 pages. |
| Office Action, dated May 18, 2017, received in U.S. Appl. No. 14/856,519, 35 pages. |
| Final Office Action, dated Nov. 15, 2017, received in U.S. Appl. No. 14/856,519, 31 pages. |
| Notice of Allowance, dated Jan. 31, 2018, received in U.S. Appl. No. 14/856,519, 9 pages. |
| Notice of Allowance, dated May 2, 2018, received in U.S. Appl. No. 14/856,519, 10 pages. |
| Office Action, dated Jun. 9, 2017, received in U.S. Appl. No. 14/856,520, 36 pages. |
| Final Office Action, dated Nov. 16, 2017, received in U.S. Appl. No. 14/856,520, 41 pages. |
| Office Action, dated Nov. 20, 2018, received in U.S. Appl. No. 14/856,520, 36 pages. |
| Final Office Action, dated Apr. 17, 2019, received in U.S. Appl. No. 14/856,520, 38 pages. |
| Notice of Allowance, dated Jan. 6, 2020, received in U.S. Appl. No. 14/856,520, 5 pages. |
| Notice of Allowance, dated Mar. 4, 2020, received in U.S. Appl. No. 14/856,520, 6 pages. |
| Notice of Allowance, dated Oct. 1, 2020, received in U.S. Appl. No. 14/856,520, 5 pages. |
| Office Action, dated Jun. 30, 2017, received in U.S. Appl. No. 14/856,522, 22 pages. |
| Notice of Allowance, dated Feb. 9, 2018, received in U.S. Appl. No. 14/856,522, 9 pages. |
| Office Action, dated Feb. 1, 2016, received in U.S. Appl. No. 14/857,645, 15 pages. |
| Final Office Action, dated Jun. 16, 2016, received in U.S. Appl. No. 14/857,645, 12 pages. |
| Notice of Allowance, dated Oct. 24, 2016, received in U.S. Appl. No. 14/857,645, 6 pages. |
| Notice of Allowance, dated Jun. 16, 2017, received in in U.S. Appl. No. 14/857,645, 5 pages. |
| Office Action, dated Nov. 30, 2017, received in U.S. Appl. No. 14/857,636, 19 pages. |
| Notice of Allowance, dated Aug. 16, 2018, received in U.S. Appl. No. 14/857,636, 5 pages. |
| Office Action, dated Jan. 17, 2018, received in Australian Patent Application No. 2017202816, which corresponds with U.S. Appl. No. 14/857,636, 3 pages. |
| Notice of Allowance, dated Jan. 15, 2019, received in Australian Patent Application No. 2017202816, which corresponds with U.S. Appl. No. 14/857,636, 3 pages. |
| Certificate of Grant, dated May 16, 2019, received in Australian Patent Application No. 2017202816, which corresponds with U.S. Appl. No. 14/857,636, 4 pages. |
| Office Action, dated Jul. 1, 2020, received in Chinese Patent Application No. 201711262953.5, which corresponds with U.S. Appl. No. 14/857,636, 13 pages. |
| Patent, dated Nov. 27, 2020, received in Chinese Patent Application No. 201711262953.5, which corresponds with U.S. Appl. No. 14/857,636, 6 pages. |
| Office Action, dated Sep. 22, 2017, received in Japanese Patent Application No. 2017-029201, which corresponds with U.S. Appl. No. 14/857,636, 8 pages. |
| Office Action, dated Jun. 25, 2018, received in Japanese Patent Application No. 2017-029201, which corresponds with U.S. Appl. No. 14/857,636, 4 pages. |
| Office Action, dated Jan. 20, 2020, received in Japanese Patent Application No. 2017-029201, which corresponds with U.S. Appl. No. 14/857,636, 21 pages. |
| Notice of Allowance, dated Oct. 16, 2020, received in Japanese Patent Application No. 2017-029201, which corresponds with U.S. Appl. No. 14/857,636, 4 pages. |
| Patent, dated Nov. 12, 2020, received in Japanese Patent Application No. 2017-029201, which corresponds with U.S. Appl. No. 14/857,636, 3 pages. |
| Office Action, dated Nov. 28, 2018, received in Korean Patent Application No. 20177036645, which corresponds with U.S. Appl. No. 14/857,636, 6 pages. |
| Notice of Allowance, dated May 10, 2019, received in Korean Patent Application No. 20177036645, which corresponds with U.S. Appl. No. 14/857,636, 4 pages. |
| Patent, dated Jul. 11, 2019, received in Korean Patent Application No. 20177036645, which corresponds with U.S. Appl. No. 14/857,636, 8 pages. |
| Office Action, dated Dec. 1, 2017, received in U.S. Appl. No. 14/857,663, 15 pages. |
| Notice of Allowance, dated Aug. 16, 2018, received in U.S. Appl. No. 14/857,663, 5 pages. |
| Office Action, dated Jul. 14, 2020, received in Chinese Patent Application No. 201711261143.8, which corresponds with U.S. Appl. No. 14/857,663, 12 pages. |
| Notice of Allowance, dated Dec. 2, 2020, received in Chinese Patent Application No. 201711261143.8, which corresponds with U.S. Appl. No. 14/857,663, 3 pages. |
| Patent, dated Jan. 22, 2021, received in Chinese Patent Application No. 201711261143.8, which corresponds with U.S. Appl. No. 14/857,663, 6 pages. |
| Office Action, dated Nov. 11, 2019, received in Japanese Patent Application No. 2018-201076, which corresponds with U.S. Appl. No. 14/857,663, 7 pages. |
| Notice of Allowance, dated Sep. 18, 2020, received in Japanese Patent Application No. 2018-201076, which corresponds with U.S. Appl. No. 14/857,663, 5 pages. |
| Patent, dated Oct. 19, 2020, received in Japanese Patent Application No. 2018-201076, which corresponds with U.S. Appl. No. 14/857,663, 4 pages. |
| Office Action, dated Mar. 31, 2017, received in U.S. Appl. No. 14/857,700, 14 pages. |
| Final Office Action, dated Oct. 11, 2017, received in U.S. Appl. No. 14/857,700, 13 pages. |
| Notice of Allowance, dated Feb. 12, 2018, received in U.S. Appl. No. 14/857,700, 13 pages. |
| Notice of Allowance, dated Apr. 9, 2018, received in U.S. Appl. No. 14/857,700, 7 pages. |
| Notice of Allowance, dated Apr. 19, 2018, received in U.S. Appl. No. 14/864,529, 11 pages. |
| Notice of Allowance, dated Oct. 9, 2018, received in U.S. Appl. No. 14/864,529, 11 pages. |
| Office Action, dated Dec. 21, 2020, received in Korean Patent Application No. 2020-7029178, which corresponds with U.S. Appl. No. 14/870,882, 2 pages. |
| Notice of allowance, dated Jun. 28, 2021, received in Korean Patent Application No. 2020-7029178, which corresponds with U.S. Appl. No. 14/870,882, 2 pages. |
| Patent, dated Sep. 28, 2021, received in Korean Patent Application No. 2020-7029178, which corresponds with U.S. Appl. No. 14/870,882, 3 pages. |
| Grant of Patent, dated Apr. 16, 2018, received in Dutch Patent Application No. 2019215, 2 pages. |
| Office Action, dated Jan. 25, 2016, received in U.S. Appl. No. 14/864,580, 29 pages. |
| Notice of Allowance, dated May 23, 2016, received in U.S. Appl. No. 14/864,580, 9 pages. |
| Notice of Allowance, dated Aug. 4, 2016, received in U.S. Appl. No. 14/864,580, 9 pages. |
| Notice of Allowance, dated Dec. 28, 2016, received in U.S. Appl. No. 14/864,580, 8 pages. |
| Office Action, dated Aug. 19, 2016, received in Australian Patent Application No. 2016100648, which corresponds with U.S. Appl. No. 14/864,580, 6 pages. |
| Office Action, dated Jul. 1, 2019, received in Australian Patent Application No. 2019200872, which corresponds with U.S. Appl. No. 14/864,580, 6 pages. |
| Notice of Acceptance, dated Sep. 19, 2019, received in Australian Patent Application No. 2019200872, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Certificate of Grant, dated Jan. 23, 2020, received in Australian Patent Application No. 2019200872, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Office Action, dated Nov. 7, 2018, received in Chinese Patent Application No. 201610342151.4, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Notice of Allowance, dated Jun. 14, 2019, received in Chinese Patent Application No. 201610342151.4, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Patent, dated Jul. 30, 2019, received in Chinese Patent Application No. 201610342151.4, which corresponds with U.S. Appl. No. 14/864,580, 6 pages. |
| Notice of Allowance, dated Nov. 8, 2016, received in Chinese Patent Application No. 201620470247.4, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Certificate of Registration, dated Oct. 14, 2016, received in German Patent Application No. 20201600003234.9, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Office Action, dated Apr. 8, 2016, received in Danish Patent Application No. 201500584, which corresponds with U.S. Appl. No. 14/864,580, 9 pages. |
| Office Action, dated Oct. 7, 2016, received in Danish Patent Application No. 201500584, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Office Action, dated May 5, 2017, received in Danish Patent Application No. 201500584, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Office Action, dated Dec. 15, 2017, received in Danish Patent Application No. 201500584, which corresponds with U.S. Appl. No. 14/864,580, 4 pages. |
| Office Action, dated Jun. 17, 2021, received in European Patent Application No. 19194418.0, which corresponds with U.S. Appl. No. 14/864,580, 7 pages. |
| Notice of Allowance, dated Feb. 4, 2022, received in Japanese Patent Application No. 2020-185336, which corresponds with U.S. Appl. No. 14/864,580, 2 pages. |
| Notice of Allowance, dated Aug. 14, 2019, received in Korean Patent Application No. 2019-7018317, which corresponds with U.S. Appl. No. 14/864,580, 6 pages. |
| Patent, dated Nov. 12, 2019, received in Korean Patent Application No. 2019-7018317, which corresponds with U.S. Appl. No. 14/864,580, 6 pages. |
| Notice of Allowance, dated Nov. 23, 2016, received in U.S. Appl. No. 14/864,601, 12 pages. |
| Notice of Allowance, dated Apr. 20, 2017, received in U.S. Appl. No. 14/864,601, 13 pages. |
| Office Action, dated Aug. 31, 2018, received in Australian Patent Application No. 2016276030, which corresponds with U.S. Appl. No. 14/864,601, 3 pages. |
| Certificate of Grant, dated Feb. 21, 2019, received in Australian Patent Application No. 2016276030, which corresponds with U.S. Appl. No. 14/864,601, 4 pages. |
| Office Action, dated Feb. 4, 2019, received in European Patent Application No. 16730554.9, which corresponds with U.S. Appl. No. 14/864,601, 10 pages. |
| Intention to Grant, dated Jul. 18, 2019, received in European Patent Application No. 16730554.9, which corresponds with U.S. Appl. No. 14/864,601, 5 pages. |
| Decision to Grant, dated Sep. 12, 2019, received in European Patent Application No. 16730554.9, which corresponds with U.S. Appl. No. 14/864,601, 2 pages. |
| Patent, dated Oct. 9, 2019, received in European Patent Application No. 16730554.9, which corresponds with U.S. Appl. No. 14/864,601, 3 pages. |
| Notice of Allowance, dated Dec. 10, 2018, received in Japanese Patent Application No. 2017-561375, which corresponds with U.S. Appl. No. 14/864,601, 5 pages. |
| Patent, dated Jan. 11, 2019, received in Japanese Patent Application No. 2017-561375, which corresponds with U.S. Appl. No. 14/864,601, 3 pages. |
| Office Action, dated Jan. 25, 2019, received in Korean Patent Application No. 2017-7033756, which corresponds with U.S. Appl. No. 14/864,601, 8 pages. |
| Notice of Allowance, dated May 29, 2019, received in Korean Patent Application No. 2017-7033756, which corresponds with U.S. Appl. No. 14/864,601, 6 pages. |
| Patent, dated Jun. 25, 2019, received in Korean Patent Application No. 2017-7033756, which corresponds with U.S. Appl. No. 14/864,601, 6 pages. |
| Office Action, dated Apr. 19, 2016, received in U.S. Appl. No. 14/864,627, 9 pages. |
| Notice of Allowance, dated Jan. 31, 2017, received in U.S. Appl. No. 14/864,627, 7 pages. |
| Office Action, dated Apr. 8, 2016, received in Danish Patent Application No. 201500585, which corresponds with U.S. Appl. No. 14/864,627, 9 pages. |
| Office Action, dated Oct. 7, 2016, received in Danish Patent Application No. 201500585, which corresponds with U.S. Appl. No. 14/864,627, 3 pages. |
| Office Action, dated May 5, 2017, received in Danish Patent Application No. 201500585, which corresponds with U.S. Appl. No. 14/864,627, 4 pages. |
| Office Action, dated Dec. 15, 2017, received in Danish Patent Application No. 201500585, which corresponds with U.S. Appl. No. 14/864,627, 5 pages. |
| Office Action, dated Mar. 29, 2016, received in U.S. Appl. No. 14/866,361, 22 pages. |
| Notice of Allowance, dated Jul. 19, 2016, received in U.S. Appl. No. 14/866,361, 8 pages. |
| Office Action, dated Jun. 10, 2016, received in Australian Patent Application No. 2016100292, which corresponds with U.S. Appl. No. 14/866,361, 4 pages. |
| Certificate of Examination, dated Dec. 8, 2016, received in Australian Patent Application No. 2016100292, which corresponds with U.S. Appl. No. 14/866,361, 1 page. |
| Office Action, dated Oct. 19, 2018, received in Chinese Patent Application No. 201610189298.4, which corresponds with U.S. Appl. No. 14/866,361, 6 pages. |
| Notice of Allowance, dated May 23, 2019, received in Chinese Patent Application No. 201610189298.4, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
| Patent, dated Jul. 23, 2019, received in Chinese Patent Application No. 201610189298.4, which corresponds with U.S. Appl. No. 14/866,361, 7 pages. |
| Notice of Allowance/Grant, dated Jul. 1, 2016, received in Chinese Patent Application No. 201620251706.X, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
| Letters Patent, dated Aug. 3, 2016, received in Chinese Patent Application No. 201620251706.X, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
| Certificate of Registration, dated Jun. 24, 2016, received in German Patent Application No. 202016001819.2, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
| Office Action, dated Apr. 7, 2016, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 10 pages. |
| Office Action, dated Oct. 28, 2016, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
| Office Action, dated Jun. 15, 2017, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 2 pages. |
| Office Action, dated Jan. 4, 2018, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 2 pages. |
| Notice of Allowance, dated Mar. 16, 2018, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 2 pages. |
| Patent, dated May 22, 2018, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 2 pages. |
| Office Action, dated Jun. 11, 2018, received in European Patent Application No. 17188507.2, which corresponds with U.S. Appl. No. 14/866,361, 10 pages. |
| Office Action, dated Jan. 30, 2019, received in European Patent Application No. 17188507.2, which corresponds with U.S. Appl. No. 14/866,361, 13 pages. |
| Office Action, dated Oct. 8, 2019, received in European Patent Application No. 17188507.2, which corresponds with U.S. Appl. No. 14/866,361, 6 pages. |
| Intention to Grant, dated Apr. 14, 2020, received in European Patent Application No. 17188507.2, which corresponds with U.S. Appl. No. 14/866,361, 7 pages. |
| Intention to Grant, dated Feb. 3, 2021, received in European Patent Application No. 17188507.2, which corresponds with U.S. Appl. No. 14/866,361, 7 pages. |
| Patent, dated May 26, 2021, received in European Patent Application No. 17188507.2, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
| Office Action, dated Oct. 12, 2018, received in Japanese Patent Application No. 2017-141962, which corresponds with U.S. Appl. No. 14/866,361, 6 pages. |
| Office Action, dated Jun. 10, 2019, received in Japanese Patent Application No. 2017-141962, which corresponds with U.S. Appl. No. 14/866,361, 6 pages. |
| Notice of Allowance, dated Oct. 7, 2019, received in Japanese Patent Application No. 2017-141962, which corresponds with U.S. Appl. No. 14/866,361, 5 pages. |
| Patent, dated Nov. 8, 2019, received in Japanese Patent Application No. 2017-141962, which corresponds with U.S. Appl. No. 14/866,361, 4 pages. |
| Office Action, dated Sep. 14, 2018, received in Korean Patent Application No. 2018-7013039, which corresponds with U.S. Appl. No. 14/866,361, 2 pages. |
| Notice of Allowance, dated Jan. 30, 2019, received in Korean Patent Application No. 2018-7013039, which corresponds with U.S. Appl. No. 14/866,361, 5 pages. |
| Patent, dated Apr. 3, 2019, received in Korean Patent Application No. 2018-7013039, which corresponds with U.S. Appl. No. 14/866,361, 4 pages. |
| Office Action, dated Jan. 22, 2018, received in U.S. Appl. No. 14/866,987, 22 pages. |
| Final Office Action, dated Oct. 11, 2018, received in U.S. Appl. No. 14/866,987, 20 pages. |
| Notice of Allowance, dated Apr. 4, 2019, received in U.S. Appl. No. 14/866,987, 5 pages. |
| Patent, dated Aug. 8, 2016, received in Australian Patent Application No. 2016100649, which corresponds with U.S. Appl. No. 14/866,987, 1 page. |
| Office Action, dated Dec. 4, 2018, received in Chinese Patent Application No. 201610342336.5, which corresponds with U.S. Appl. No. 14/866,987, 5 pages. |
| Rejection Decision, dated Apr. 28, 2019, received in Chinese Patent Application No. 201610342336.5, which corresponds with U.S. Appl. No. 14/866,987, 4 pages. |
| Office Action, dated Aug. 15, 2019, received in Chinese Patent Application No. 201610342336.5, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Notice of Allowance, dated Dec. 3, 2019, received in Chinese Patent Application No. 201610342336.5, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Patent, dated Jan. 31, 2020, received in Chinese Patent Application No. 201610342336.5, which corresponds with U.S. Appl. No. 14/866,987, 7 pages. |
| Office Action, dated Oct. 19, 2016, received in Chinese Patent Application No. 2016201470246.X, which corresponds with U.S. Appl. No. 14/866,987, 4 pages. |
| Patent, dated May 3, 2017, received in Chinese Patent Application No. 2016201470246.X, which corresponds with U.S. Appl. No. 14/866,987, 2 pages. |
| Patent, dated Sep. 19, 2016, received in German Patent Application No. 202016002908.9, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Office Action, dated Mar. 22, 2016, received in Danish Patent Application No. 201500587, which corresponds with U.S. Appl. No. 14/866,987, 8 pages. |
| Intention to Grant, dated Jun. 10, 2016, received in Danish Patent Application No. 201500587, which corresponds with U.S. Appl. No. 14/866,987, 2 pages. |
| Notice of Allowance, dated Nov. 1, 2016, received in Danish Patent Application No. 201500587, which corresponds with U.S. Appl. No. 14/866,987, 2 pages. |
| Office Action, dated Sep. 9, 2016, received in Danish Patent Application No. 201670463, which corresponds with U.S. Appl. No. 14/866,987, 7 pages. |
| Notice of Allowance, dated Jan. 31, 2017, received in Danish Patent Application No. 201670463, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Office Action, dated Apr. 19, 2017, received in Danish Patent Application No. 201670463, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Notice of Allowance, dated Sep. 29, 2017, received in Danish Patent Application No. 201670463, which corresponds with U.S. Appl. No. 14/866,987, 2 pages. |
| Patent, dated Nov. 6, 2017, received in Danish Patent Application No. 201670463, which corresponds with U.S. Appl. No. 14/866,987, 6 pages. |
| Office Action, dated May 7, 2018, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 5 pages. |
| Office Action, dated Dec. 11, 2018, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 6 pages. |
| Intention to Grant, dated Jun. 14, 2019, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 7 pages. |
| Intention to Grant, dated Oct. 25, 2019, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 7 pages. |
| Decision to Grant, dated Nov. 14, 2019, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 2 pages. |
| Patent, dated Dec. 11, 2019, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Office Action, dated Feb. 3, 2020, received in European Patent Application No. 17163309.2, which corresponds with U.S. Appl. No. 14/866,987, 6 pages. |
| Office Action, dated Dec. 22, 2021, received in European Patent Application No. 17163309.2, which corresponds with U.S. Appl. No. 14/866,987, 4 pages. |
| Patent, dated Feb. 5, 2021, received in Hong Kong Patent Application No. 1235878, which corresponds with U.S. Appl. No. 14/866,987, 6 pages. |
| Patent, dated Jan. 8, 2021, received in Hong Kong Patent Application No. 18100151.5, which corresponds with U.S. Appl. No. 14/866,987, 6 pages. |
| Office Action, dated Aug. 26, 2020, received in Indian Application No. 201617032291, which corresponds with U.S. Appl. No. 14/866,987, 9 pages. |
| Notice of Allowance, dated Sep. 22, 2017, received in Japanese Patent Application No. 2016-233449, which corresponds with U.S. Appl. No. 14/866,987, 5 pages. |
| Patent, dated Oct. 27, 2017, received in Japanese Patent Application No. 2016-233449, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Office Action, dated Jul. 31, 2017, received in Japanese Patent Application No. 2017126445, which corresponds with U.S. Appl. No. 14/866,987, 6 pages. |
| Notice of Allowance, dated Mar. 6, 2018, received in Japanese Patent Application No. 2017-126445, which corresponds with U.S. Appl. No. 14/866,987, 5 pages. |
| Patent, dated Apr. 6, 2018, received in Japanese Patent Application No. 2017-126445, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Office Action, dated Nov. 29, 2017, received in U.S. Appl. No. 14/866,989, 31 pages. |
| Final Office Action, dated Jul. 3, 2018, received in U.S. Appl. No. 14/866,989, 17 pages. |
| Notice of Allowance, dated Jan. 17, 2019, received in U.S. Appl. No. 14/866,989, 8 pages. |
| Certificate of Exam, dated Jul. 21, 2016, received in Australian Patent Application No. 2016100652, which corresponds with U.S. Appl. No. 14/866,989, 1 page. |
| Office Action, dated Feb. 26, 2018, received in Australian Patent Application No. 2017201079, which corresponds with U.S. Appl. No. 14/866,989, 6 pages. |
| Notice of Acceptance, dated Feb. 14, 2019, received in Australian Patent Application No. 2017201079, which corresponds with U.S. Appl. No. 14/866,989, 3 pages. |
| Certificate of Grant, dated Jun. 13, 2019, received in Australian Patent Application No. 2017201079, which corresponds with U.S. Appl. No. 14/866,989, 1 page. |
| Office Action, dated Sep. 19, 2018, received in Chinese Patent Application No. 201610342314.9, which corresponds with U.S. Appl. No. 14/866,989, 6 pages. |
| Office Action, dated Feb. 25, 2019, received in Chinese Patent Application No. 201610342314.9, which corresponds with U.S. Appl. No. 14/866,989, 3 pages. |
| Rejection Decision, dated Apr. 24, 2019, received in Chinese Patent Application No. 201610342314.9, which corresponds with U.S. Appl. No. 14/866,989, 3 pages. |
| Office Action, dated Jun. 16, 2017, received in Japanese Patent Application No. 2016-233450, which corresponds with U.S. Appl. No. 14/866,989, 6 pages. |
| Patent, dated Mar. 9, 2018, received in Japanese Patent Application No. 2016-233450, which corresponds with U.S. Appl. No. 14/866,989, 4 pages. |
| Office Action, dated Apr. 1, 2016, received in Danish Patent Application No. 201500589, which corresponds with U.S. Appl. No. 14/866,989, 8 pages. |
| Intention to Grant, dated Jun. 10, 2016, received in Danish Patent Application No. 201500589, which corresponds with U.S. Appl. No. 14/866,989, 2 pages. |
| Notice of Allowance, dated Nov. 1, 2016, received in Danish Patent Application No. 201500589, which corresponds with U.S. Appl. No. 14/866,989, 2 pages. |
| Office Action, dated Feb. 3, 2020, received in European Patent Application No. 16189425.8, which corresponds with U.S. Appl. No. 14/866,989, 6 pages. |
| Intention to Grant, dated Dec. 3, 2020, received in European Patent Application No. 16189425.8, which corresponds with U.S. Appl. No. 14/866,989, 7 pages. |
| Decision to Grant, dated Feb. 25, 2021, received in European Patent Application No. 16189425.8, which corresponds with U.S. Appl. No. 14/866,989, 1 page. |
| Notice of Allowance, dated Feb. 5, 2018, received in Japanese Patent Application No. 2016-233450, which corresponds with U.S. Appl. No. 14/866,989, 5 pages. |
| Office Action, dated Apr. 11, 2016, received in U.S. Appl. No. 14/871,236, 23 pages. |
| Office Action, dated Jun. 28, 2016, received in U.S. Appl. No. 14/871,236, 21 pages. |
| Final Office Action, dated Nov. 4, 2016, received in U.S. Appl. No. 14/871,236, 24 pages. |
| Notice of Allowance, dated Feb. 28, 2017, received in U.S. Appl. No. 14/871,236, 9 pages. |
| Innovation Patent, dated Aug. 25, 2016, received in Australian Patent Application No. 2016101433, which corresponds with U.S. Appl. No. 14/871,236, 1 page. |
| Office Action, dated Oct. 14, 2016, received in Australian Patent Application No. 2016101433, which corresponds with U.S. Appl. No. 14/871,236, 3 pages. |
| Office Action, dated Jun. 23, 2020, received in Brazilian Patent Application No. 11201701119-9, which corresponds with U.S. Appl. No. 14/871,236, 9 pages. |
| Office Action, dated Sep. 30, 2019, received in Chinese Patent Application No. 201610871466.8, which corresponds with U.S. Appl. No. 14/871,236, 4 pages. |
| Notice of Allowance, dated Mar. 24, 2020, received in Chinese Patent Application No. 201610871466.8, which corresponds with U.S. Appl. No. 14/871,236, 3 pages. |
| Patent, dated May 19, 2020, received in Chinese Patent Application No. 201610871466.8, which corresponds with U.S. Appl. No. 14/871,236, 8 pages. |
| Office Action, dated Apr. 8, 2016, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 12 pages. |
| Office Action, dated May 26, 2016, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 14 pages. |
| Office Action, dated Sep. 30, 2016, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 10 pages. |
| Office Action, dated Jun. 15, 2017, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 4 pages. |
| Office Action, dated Jan. 29, 2018, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 2 pages. |
| Notice of Allowance, dated Apr. 26, 2018, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 2 pages. |
| Patent, dated Jun. 18, 2018, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 3 pages. |
| Intention to Grant, dated Dec. 4, 2019, received in European Patent Application No. 18168941.5, which corresponds with U.S. Appl. No. 14/871,236, 8 pages. |
| Intention to Grant, dated Oct. 5, 2020, received in European Patent Application No. 18168941.5, which corresponds with U.S. Appl. No. 14/871,236, 8 pages. |
| Decision to Grant, dated Mar. 25, 2021, received in European Patent Application No. 18168941.5, which corresponds with U.S. Appl. No. 14/871,236, 2 pages. |
| Patent, dated Apr. 21, 2021, received in European Patent Application No. 18168941.5, which corresponds with U.S. Appl. No. 14/871,236, 3 pages. |
| Office Action, dated Mar. 17, 2020, received in Mx/a/2017/011610, which corresponds with U.S. Appl. No. 14/871,236, 4 pages. |
| Notice of Allowance, dated Sep. 7, 2020, received in Mx/a/201//011610, which corresponds with U.S. Appl. No. 14/871,236, 12 pages. |
| Patent, dated Dec. 2, 2020, received in Mx/a/2017/011610, which corresponds with U.S. Appl. No. 14/871,236, 4 pages. |
| Office Action, dated Jul. 19, 2018, received in Russian Patent Application No. 2017131408, which corresponds with U.S. Appl. No. 14/871,236, 8 pages. |
| Patent, dated Feb. 15, 2019, received in Russian Patent Application No. 2017131408, which corresponds with U.S. Appl. No. 14/871,236, 2 pages. |
| Office Action, dated Sep. 1, 2017, received in U.S. Appl. No. 14/870,754, 22 pages. |
| Final Office Action, dated Mar. 9, 2018, received in U.S. Appl. No. 14/870,754, 19 pages. |
| Notice of Allowance, dated Jul. 2, 2018, received in U.S. Appl. No. 14/870,754, 9 pages. |
| Notice of Allowance, dated Dec. 3, 2018, received in U.S. Appl. No. 14/870,754, 8 pages. |
| Office Action, dated Nov. 14, 2017, received in U.S. Appl. No. 14/870,882, 25 pages. |
| Final Office Action, dated Apr. 20, 2018, received in U.S. Appl. No. 14/870,882, 7 pages. |
| Notice of Allowance, dated Jul. 12, 2018, received in U.S. Appl. No. 14/870,882, 5 pages. |
| Notice of Allowance, dated Dec. 5, 2018, received in U.S. Appl. No. 14/870,882, 8 pages. |
| Innovation Patent, dated Aug. 25, 2016, received in Australian Patent Application No. 2016101436, which corresponds with U.S. Appl. No. 14/871,236, 1 pages. |
| Office Action, dated Oct. 31, 2016, received in Australian Patent Application No. 2016101438, which corresponds with U.S. Appl. No. 14/871,236, 6 pages. |
| Office Action, dated Nov. 28, 2019, received in Chinese Patent Application No. 201610870912.3, which corresponds with U.S. Appl. No. 14/870,882, 10 pages. |
| Office Action, dated Aug. 3, 2020, received in Chinese Patent Application No. 201610870912.3, which corresponds with U.S. Appl. No. 14/870,882, 4 pages. |
| Office Action, dated Dec. 21, 2020, received in Chinese Patent Application No. 201610870912.3, which corresponds with U.S. Appl. No. 14/870,882, 5 pages. |
| Notice of Allowance, dated Mar. 22, 2021, received in Chinese Patent Application No. 201610870912.3, which corresponds with U.S. Appl. No. 14/870,882, 1 pages. |
| Patent, dated May 25, 2021, received in Chinese Patent Application No. 201610870912.3, which corresponds with U.S. Appl. No. 14/870,882, 8 pages. |
| Office Action, dated Apr. 6, 2016, received in Danish Patent Application No. 201500596, which corresponds with U.S. Appl. No. 14/870,882, 7 pages. |
| Office Action, dated Jun. 9, 2016, received in Danish Patent Application No. 201500596, which corresponds with U.S. Appl. No. 14/870,882, 9 pages. |
| Notice of Allowance, dated Oct. 31, 2017, received in Danish Patent Application No. 201500596, which corresponds with U.S. Appl. No. 14/870,882, 2 pages. |
| Patent, dated Jan. 29, 2018, received in Danish Patent Application No. 201500596, which corresponds with U.S. Appl. No. 14/870,882, 4 pages. |
| Office Action, dated Feb. 11, 2019, received in European Patent Application No. 17171972.7, which corresponds with U.S. Appl. No. 14/870,882, 7 pages. |
| Office Action, dated Sep. 1, 2017, received in U.S. Appl. No. 14/870,988, 14 pages. |
| Final Office Action, dated Feb. 16, 2018, received in U.S. Appl. No. 14/870,988, 18 pages. |
| Notice of Allowance, dated Aug. 27, 2018, received in U.S. Appl. No. 14/870,988, 11 pages. |
| Office Action, dated Nov. 22, 2017, received in U.S. Appl. No. 14/871,227, 24 pages. |
| Notice of Allowance, dated Jun. 11, 2018, received in U.S. Appl. No. 14/871,227, 11 pages. |
| Office Action, dated Oct. 17, 2016, received in Australian Patent Application No. 2016203040, which corresponds with U.S. Appl. No. 14/871,227, 7 pages. |
| Office Action, dated Oct. 16, 2017, received in Australian Patent Application No. 2016203040, which corresponds with U.S. Appl. No. 14/871,227, 5 pages. |
| Notice of Acceptance, dated Oct. 30, 2018, received in Australian Patent Application No. 2016203040, which corresponds with U.S. Appl. No. 14/871,227, 4 pages. |
| Certificate of Grant, dated Feb. 28, 2019, received in Australian Patent Application No. 2016203040, which corresponds with U.S. Appl. No. 14/871,227, 1 page. |
| Office Action, dated Oct. 18, 2016, received in Australian Patent Application No. 2016101431, which corresponds with U.S. Appl. No. 14/871,227, 3 pages. |
| Office Action, dated Apr. 13, 2017, received in Australian Patent Application No. 2016101431, which corresponds with U.S. Appl. No. 14/871,227, 4 pages. |
| Office Action, dated Oct. 11, 2018, received in Australian Patent Application No. 2017245442, which corresponds with U.S. Appl. No. 14/871,227, 4 pages. |
| Office Action, dated Nov. 16, 2018, received in Chinese Patent Application No. 201680000466.9, which corresponds with U.S. Appl. No. 14/871,227, 5 pages. |
| Notice of Allowance, dated Jun. 5, 2019, received in Chinese Patent Application No. 201680000466.9, which corresponds with U.S. Appl. No. 14/871,227, 5 pages. |
| Patent, dated Aug. 9, 2019, received in Chinese Patent Application No. 201680000466.9, which corresponds with U.S. Appl. No. 14/871,227, 8 pages. |
| Intention to Grant, dated Apr. 7, 2016, received in Danish Patent Application No. 201500597, which corresponds with U.S. Appl. No. 14/871,227, 7 pages. |
| Grant, dated Jun. 21, 2016, received in Danish Patent Application No. 201500597, which corresponds with U.S. Appl. No. 14/871,227, 2 pages. |
| Patent, dated Sep. 26, 2016, received in Danish Patent Application No. 201500597, which corresponds with U.S. Appl. No. 14/871,227, 7 pages. |
| Intent to Grant, dated Sep. 17, 2018, received in European Patent No. 16711743.1, which corresponds with U.S. Appl. No. 14/871,227, 5 pages. |
| Patent, dated Nov. 28, 2018, received in European Patent No. 16711743.1, which corresponds with U.S. Appl. No. 14/871,227, 1 page. |
| Office Action, dated Jul. 20, 2020, received in Indian Patent Application No. 201617032293, which corresponds with U.S. Appl. No. 14/871,227, 9 pages. |
| Office Action, dated Mar. 24, 2017, received in Japanese Patent Application No. 2016-533201, which corresponds with U.S. Appl. No. 14/871,227, 6 pages. |
| Office Action, dated Aug. 4, 2017, received in Japanese Patent Application No. 2016-533201, which corresponds with U.S. Appl. No. 14/871,227, 6 pages. |
| Notice of Allowance, dated Jan. 4, 2018, received in Japanese Patent Application No. 2016-533201, which corresponds with U.S. Appl. No. 14/871,227, 4 pages. |
| Patent, dated Feb. 9, 2018, received in Japanese Patent Application No. 2016-533201, which corresponds with U.S. Appl. No. 14/871,227, 4 pages. |
| Office Action, dated Feb. 20, 2018, received in Korean Patent Application No. 2016-7019816, which corresponds with U.S. Appl. No. 14/871,227, 8 pages. |
| Notice of Allowance, dated Oct. 1, 2018, received in Korean Patent Application No. 2016-7019816, which corresponds with U.S. Appl. No. 14/871,227, 6 pages. |
| Patent, dated Dec. 28, 2018, received in Korean Patent Application No. 2016-7019816, which corresponds with U.S. Appl. No. 14/871,227, 8 pages. |
| Office Action, dated Oct. 26, 2017, received in U.S. Appl. No. 14/871,336, 22 pages. |
| Final Office Action, dated Mar. 15, 2018, received in U.S. Appl. No. 14/871,336, 23 pages. |
| Office Action, dated Nov. 5, 2018, received in U.S. Appl. No. 14/871,336, 24 pages. |
| Notice of Allowance, dated Feb. 5, 2019, received in U.S. Appl. No. 14/871,336, 10 pages. |
| Office Action, dated Oct. 14, 2016, received in Australian Patent Application No. 2016101437, which corresponds with U.S. Appl. No. 14/871,336, 2 pages. |
| Office Action, dated Apr. 11, 2017, received in Australian Patent Application No. 2016101437, which corresponds with U.S. Appl. No. 14/871,336, 4 pages. |
| Office Action, dated Nov. 4, 2019, received in Chinese Patent Application No. 201610871323.7, which corresponds with U.S. Appl. No. 14/871,336, 12 pages. |
| Office Action, dated Aug. 4, 2020, received in Chinese Patent Application No. 201610871323.7, which corresponds with U.S. Appl. No. 14/871,336, 18 pages. |
| Office Action, dated Feb. 9, 2021, received in Chinese Patent Application No. 201610871323.7, which corresponds with U.S. Appl. No. 14/871,336, 1 page. |
| Office Action, dated Jun. 1, 2021, received in Chinese Patent Application No. 201610871323.7, which corresponds with U.S. Appl. No. 14/871,336, 1 page. |
| Office Action, dated Apr. 18, 2016, received in Danish Patent Application No. 201500601, which corresponds with U.S. Appl. No. 14/871,336, 8 pages. |
| Office Action, dated Oct. 18, 2016, received in Danish Patent Application No. 201500601, which corresponds with U.S. Appl. No. 14/871,336, 3 pages. |
| Notice of Allowance, dated Mar. 23, 2017, received in Danish Patent Application No. 201500601, which corresponds with U.S. Appl. No. 14/871,336, 2 pages. |
| Patent, dated Oct. 30, 2017, Danish Patent Application No. 201500601, which corresponds with U.S. Appl. No. 14/871,336, 5 pages. |
| Office Action, dated Feb. 12, 2019, received in European Patent Application No. 17172266.3, which corresponds with U.S. Appl. No. 14/871,336, 6 pages. |
| Office Action, dated Apr. 2, 2018, received in Japanese Patent Application No. 2018-020324, which corresponds with U.S. Appl. No. 14/871,336, 4 pages. |
| Notice of Allowance, dated Oct. 12, 2018, received in Japanese Patent Application No. 2018-020324, which corresponds with U.S. Appl. No. 14/871,336, 5 pages. |
| Patent, dated Nov. 16, 2018, received in Japanese Patent Application No. 2018-020324, which corresponds with U.S. Appl. No. 14/871,336, 4 pages. |
| Office Action, dated Oct. 16, 2017, received in U.S. Appl. No. 14/871,462, 26 pages. |
| Innovation Patent, dated Aug. 25, 2016, received in Australian Patent Application No. 2016101435, which corresponds with U.S. Appl. No. 14/871,462, 1 page. |
| Office Action, dated Oct. 4, 2016, received in Australian Patent Application No. 2016101435, which corresponds with U.S. Appl. No. 14/871,462, 3 pages. |
| Office Action, dated Oct. 4, 2016, received in Australian Patent Application No. 2016231505, which corresponds with U.S. Appl. No. 14/871,462, 3 pages. |
| Office Action, dated Sep. 29, 2017, received in Australian Patent Application No. 2016231505, which corresponds with U.S. Appl. No. 14/871,462, 5 pages. |
| Innovation Patent, dated Oct. 11, 2017, received in Australian Patent Application No. 2016231505, which corresponds with U.S. Appl. No. 14/871,462, 1 page. |
| Office Action, dated Oct. 9, 2021, received in Chinese Patent Application No. 201610869950.7, which corresponds with U.S. Appl. No. 14/871,462, 5 pages. |
| Notice of Allowance, dated Feb. 9, 2022, received in Chinese Patent Application No. 201610869950.7, which corresponds with U.S. Appl. No. 14/871,462, 1 page. |
| Office Action, dated Apr. 20, 2017, received in Chinese Patent Application No. 201621044346.2, which corresponds with U.S. Appl. No. 14/871,462, 3 pages. |
| Intention to Grant, dated Apr. 18, 2016, received in Danish Patent Application No. 201500600, which corresponds with U.S. Appl. No. 14/871,462, 7 pages. |
| Grant, dated Aug. 30, 2016, received in Danish Patent Application No. 201500600, which corresponds with U.S. Appl. No. 14/871,462, 2 pages. |
| Office Action, dated Mar. 13, 2017, received in Japanese Patent Application No. 2016-183289, which corresponds with U.S. Appl. No. 14/871,462, 5 pages. |
| Office Action, dated Nov. 13, 2017, received in Japanese Patent Application No. 2016-183289, which corresponds with U.S. Appl. No. 14/871,462, 5 pages. |
| Office Action, dated Apr. 29, 2016, received in U.S. Appl. No. 14/867,823, 28 pages. |
| Final Office Action, dated Sep. 28, 2016, received in U.S. Appl. No. 14/867,823, 31 pages. |
| Office Action, dated May 11, 2017, received in U.S. Appl. No. 14/867,823, 42 pages. |
| Final Office Action, dated Nov. 29, 2017, received in U.S. Appl. No. 14/867,823, 47 pages. |
| Notice of Allowance, dated Apr. 18, 2018, received in U.S. Appl. No. 14/867,823, 10 pages. |
| Notice of Allowance, dated Aug. 7, 2018, received in U.S. Appl. No. 14/867,823, 8 pages. |
| Office Action, dated Mar. 18, 2016, received in Danish Patent Application No. 201500594, which corresponds with U.S. Appl. No. 14/867,823, 10 pages. |
| Office Action, dated Sep. 7, 2016, received in Danish Patent Application No. 201500594, which corresponds with U.S. Appl. No. 14/867,823, 4 pages. |
| Office Action, dated May 15, 2017, received in Danish Patent Application No. 201500594, which corresponds with U.S. Appl. No. 14/867,823, 4 pages. |
| Office Action, dated Jan. 23, 2018, received in Danish Patent Application No. 201500594, which corresponds with U.S. Appl. No. 14/867,823, 8 pages. |
| Office Action, dated May 10, 2016, received in U.S. Appl. No. 14/867,892, 28 pages. |
| Final Office Action, dated Nov. 2, 2016, received in U.S. Appl. No. 14/867,892, 48 pages. |
| Office Action, dated Jul. 6, 2017, received in U.S. Appl. No. 14/867,892, 55 pages. |
| Final Office Action, dated Dec. 14, 2017, received in U.S. Appl. No. 14/867,892, 53 pages. |
| Office Action, dated Apr. 24, 2018, received in U.S. Appl. No. 14/867,892, 63 pages. |
| Final Office Action, dated Oct. 17, 2018, received in U.S. Appl. No. 14/867,892, 48 pages. |
| Examiner's Answer, dated Jul. 18, 2019, received in U.S. Appl. No. 14/867,892, 17 pages. |
| Notice of Allowance, dated May 26, 2021, received in U.S. Appl. No. 14/867,892, 7 pages. |
| Notice of Allowance, dated Jul. 13, 2021, received in U.S. Appl. No. 14/867,892, 8 pages. |
| Office Action, dated Mar. 21, 2016, received in Danish Patent Application No. 201500598, which corresponds with U.S. Appl. No. 14/867,892, 9 pages. |
| Office Action, dated Sep. 14, 2016, received in Danish Patent Application No. 201500598, which corresponds with U.S. Appl. No. 14/867,892, 4 pages. |
| Office Action, dated May 4, 2017, received in Danish Patent Application No. 201500598, which corresponds with U.S. Appl. No. 14/867,892, 4 pages. |
| Office Action, dated Oct. 31, 2017, received in Danish Patent Application No. 201500598, which corresponds with U.S. Appl. No. 14/867,892, 2 pages. |
| Notice of Allowance, dated Jan. 26, 2018, received in Danish Patent Application No. 201500598, which corresponds with U.S. Appl. No. 14/867,892, 2 pages. |
| Office Action, dated Feb. 28, 2018, received in U.S. Appl. No. 14/869,361, 26 pages. |
| Final Office Action, dated Oct. 4, 2018, received in U.S. Appl. No. 14/869,361, 28 pages. |
| Office Action, dated Feb. 27. 2019, received in U.S. Appl. No. 14/869,361, 28 pages. |
| Office Action, dated Mar. 1, 2017, received in U.S. Appl. No. 14/869,855, 14 pages. |
| Final Office Action, dated Oct. 10, 2017, received in U.S. Appl. No. 14/869,855, 16 pages. |
| Office Action, dated Jan. 23, 2018, received in U.S. Appl. No. 14/869,855, 24 pages. |
| Notice of Allowance, dated May 31, 2018, received in U.S. Appl. No. 14/869,855, 10 pages. |
| Office Action, dated Feb. 9, 2017, received in U.S. Appl. No. 14/869,873, 17 pages. |
| Final Office Action, dated Aug. 18, 2017, received in U.S. Appl. No. 14/869,873, 20 pages. |
| Office Action, dated Jan. 18, 2018, received in U.S. Appl. No. 14/869,873, 25 pages. |
| Final Office Action, dated May 23, 2018, received in U.S. Appl. No. 14/869,873, 18 pages. |
| Notice of Allowance, dated Jul. 30, 2018, received in U.S. Appl. No. 14/869,873, 8 pages. |
| Office Action, dated Jan. 11, 2018, received in U.S. Appl. No. 14/869,997, 17 pages. |
| Office Action, dated Sep. 7, 2018, received in U.S. Appl. No. 14/869,997, 23 pages. |
| Notice of Allowance, dated Apr. 4, 2019, received in U.S. Appl. No. 14/869,997, 9 pages. |
| Notice of Allowance, dated Jan. 17, 2018, received in U.S. Appl. No. 14/867,990, 12 pages. |
| Notice of Allowance, dated Mar. 30, 3018, received in U.S. Appl. No. 14/867,990, 5 pages. |
| Office Action, dated May 23, 2016, received in Australian Patent Application No. 2016100253, which corresponds with U.S. Appl. No. 14/867,990, 5 pages. |
| Notice of Allowance, dated May 21, 2019, received in Chinese Patent Application No. 201610131507.X, which corresponds with U.S. Appl. No. 14/867,990, 3 pages. |
| Patent, dated Jul. 19, 2019, received in Chinese Patent Application No. 201610131507.X, which corresponds with U.S. Appl. No. 14/867,990, 6 pages. |
| Office Action, dated Jul. 5, 2016, received in Chinese Patent Application No. 201620176221.9, which corresponds with U.S. Appl. No. 14/867,990, 4 pages. |
| Office Action, dated Oct. 25, 2016, received in Chinese Patent Application No. 201620176221.9, which corresponds with U.S. Appl. No. 14/867,990, 7 pages. |
| Certificate of Registration, dated Jun. 16, 2016, received in German Patent No. 202016001489.8, which corresponds with U.S. Appl. No. 14/867,990, 3 pages. |
| Office Action, dated Mar. 18, 2016, received in Danish Patent Application No. 201500581, which corresponds with U.S. Appl. No. 14/867,990, 9 pages. |
| Office Action, dated Sep. 26, 2016, received in Danish Patent Application No. 201500581, which corresponds with U.S. Appl. No. 14/867,990, 5 pages. |
| Office Action, dated May 3, 2017, received in Danish Patent Application No. 201500581, which corresponds with U.S. Appl. No. 14/867,990, 5 pages. |
| Office Action, dated Feb. 19, 2018, received in Danish Patent Application No. 201500581, which corresponds with U.S. Appl. No. 14/867,990, 4 pages. |
| Office Action, dated Feb. 21, 2020, received in European Patent Application No. 16711725.8, which corresponds with U.S. Appl. No. 14/867,990, 13 pages. |
| Office Action, dated May 14, 2021, received in European Patent Application No. 16711725.8, which corresponds with U.S. Appl. No. 14/867,990, 7 pages. |
| Office Action, dated Apr. 19, 2018, received in U.S. Appl. No. 14/869,703, 19 pages. |
| Final Office Action, dated Oct. 26, 2018, received in U.S. Appl. No. 14/869,703, 19 pages. |
| Notice of Allowance, dated Mar. 12, 2019, received in U.S. Appl. No. 14/869,703, 6 pages. |
| Office Action, dated Dec. 12, 2017, received in U.S. Appl. No. 15/009,668, 32 pages. |
| Final Office Action, dated Jul. 3, 2018, received in U.S. Appl. No. 15/009,668, 19 pages. |
| Office Action, dated Jan. 10, 2019, received in U.S. Appl. No. 15/009,668, 17 pages. |
| Notice of Allowance, dated May 1, 2019, received in U.S. Appl. No. 15/009,668, 12 pages. |
| Office Action, dated Aug. 20, 2020, received in Chinese Patent Application No. 201680046985.9, which corresponds with U.S. Appl. No. 15/009,668, 15 pages. |
| Notice of Allowance, dated Apr. 20, 2021, received in Chinese Patent Application No. 201680046985.9, which corresponds with U.S. Appl. No. 15/009,668, 1 page. |
| Office Action, dated Jan. 31, 2020, received in European Patent Application No. 16753795.0, which corresponds with U.S. Appl. No. 15/009,668, 9 pages. |
| Office Action, dated Mar. 19, 2021, received in European Patent Application No. 16753795.0, which corresponds with U.S. Appl. No. 15/009,668, 5 pages. |
| Office Action, dated Nov. 25, 2016, received in U.S. Appl. No. 15/081,771, 17 pages. |
| Final Office Action, dated Jun. 2, 2017, received in U.S. Appl. No. 15/081,771, 17 pages. |
| Notice of Allowance, dated Dec. 4, 2017, received in U.S. Appl. No. 15/081,771, 10 pages. |
| Office Action, dated Feb. 1, 2018, received in Australian Patent Application No. 2017202058, which corresponds with U.S. Appl. No. 15/081,771, 4 pages. |
| Notice of Acceptance, dated Jan. 24, 2019, received in Australian Patent Application No. 2017202058, which corresponds with U.S. Appl. No. 15/081,771, 3 pages. |
| Certificate of Grant, dated May 23, 2019, received in Australian Patent Application No. 2017202058, which corresponds with U.S. Appl. No. 15/081,771, 1 page. |
| Office Action, dated Jan. 24, 2020, received in European Patent Application No. 18205283.7, which corresponds with U.S. Appl. No. 15/081,771, 4 pages. |
| Intention to Grant, dated Apr. 30, 2020, received in European Patent Application No. 18205283.7, which corresponds with U.S. Appl. No. 15/081,771, 7 pages. |
| Decision to Grant, dated Aug. 27, 2020, received in European Patent Application No. 18205283.7, which corresponds with U.S. Appl. No. 15/081,771, 4 pages. |
| Patent, dated Sep. 23, 2020, received in European Patent Application No. 18205283.7, which corresponds with U.S. Appl. No. 15/081,771, 4 pages. |
| Office Action, dated Jan. 26, 2018, received in Japanese Patent Application No. 2017-086460, which corresponds with U.S. Appl. No. 15/081,771, 6 pages. |
| Notice of Allowance, dated Oct. 12, 2018, received in Japanese Patent Application No. 2017-086460, which corresponds with U.S. Appl. No. 15/081,771, 5 pages. |
| Office Action, dated Aug. 29, 2017, received in Korean Patent Application No. 2017-7014536, which corresponds with U.S. Appl. No. 15/081,771, 5 pages. |
| Notice of Allowance, dated Jun. 28, 2018, received in Korean Patent Application No. 2017-7014536, which corresponds with U.S. Appl. No. 15/081,771, 4 pages. |
| Patent, dated Sep. 28, 2018, received in Korean Patent Application No. 2017-7014536, which corresponds with U.S. Appl. No. 15/081,771, 3 pages. |
| Final Office Action, dated May 1, 2017, received in U.S. Appl. No. 15/136,782, 18 pages. |
| Notice of Allowance, dated Oct. 20, 2017, received in U.S. Appl. No. 15/136,782, 9 pages. |
| Office Action, dated May 4, 2018, received in Australian Patent Application No. 2018202855, which corresponds with U.S. Appl. No. 15/136,782, 3 pages. |
| Notice of Acceptance, dated Sep. 10, 2018, received in Australian Patent Application No. 2018202855, which corresponds with U.S. Appl. No. 15/136,782, 3 pages. |
| Certificate of Grant, dated Jan. 17, 2019, received in Australian Patent Application No. 2018202855, which corresponds with U.S. Appl. No. 15/136,782, 4 pages. |
| Office Action, dated Sep. 27, 2019, received in Chinese Patent Application No. 201810119007.3, which corresponds with U.S. Appl. No. 15/136,782, 6 pages. |
| Notice of Allowance, dated Feb. 26, 2020, received in Chinese Patent Application No. 201810119007.3, which corresponds with U.S. Appl. No. 15/136,782, 3 pages. |
| Patent, dated Apr. 7, 2020, received in Chinese Patent Application No. 201810119007.3, which corresponds with U.S. Appl. No. 15/136,782, 7 pages. |
| Office Action, dated May 23, 2017, received in Danish Patent Application No. 201770190, which corresponds with U.S. Appl. No. 15/136,782, 7 pages. |
| Office Action, dated Jan. 8, 2018, received in Danish Patent Application No. 201770190, which corresponds with U.S. Appl. No. 15/136,782, 2 pages. |
| Notice of Allowance, dated Mar. 19, 2018, received in Danish Patent Application No. 201770190, which corresponds with U.S. Appl. No. 15/136,782, 2 pages. |
| Patent, dated May 22, 2018, received in Danish Patent Application No. 201770190, which corresponds with U.S. Appl. No. 15/136,782, 2 pages. |
| Office Action, dated Apr. 17, 2019, received in European Patent Application No. 18171453.6, which corresponds with U.S. Appl. No. 15/136,782, 4 pages. |
| Office Action, dated Oct. 2, 2019, received in European Patent Application No. 18171453.6, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Office Action, dated May 12, 2020, received in European Patent Application No. 18171453.6, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Patent, dated Feb. 5, 2021, received in Hong Kong Patent Application No. 1257553, which corresponds with U.S. Appl. No. 15/136,782, 14 pages. |
| Office Action, dated Jun. 1, 2018, received in Japanese Patent Application No. 2018-062161, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Office Action, dated Nov. 12, 2018, received in Japanese Patent Application No. 2018-062161, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Notice of Allowance, dated Feb. 18, 2019, received in Japanese Patent Application No. 2018-062161, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Patent, dated Mar. 22, 2019, received in Japanese Patent Application No. 2018-062161, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Office Action, dated Oct. 31, 2018, received in Korean Patent Application No. 2018-7020659, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Notice of Allowance, dated Feb. 25, 2019, received in Korean Patent Application No. 2018-7020659, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Patent, dated Apr. 3, 2019, received in Korean Patent Application No. 2018-7020659, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Office Action, dated Jan. 20, 2017, received in U.S. Appl. No. 15/231,745, 21 pages. |
| Notice of Allowance, dated Jul. 6, 2017, received in U.S. Appl. No. 15/231,745, 18 pages. |
| Office Action, dated Oct. 17, 2016, received in Danish Patent Application No. 201670587, which corresponds with U.S. Appl. No. 15/231,745, 9 pages. |
| Office Action, dated Jun. 29, 2017, received in Danish Patent Application No. 201670587, which corresponds with U.S. Appl. No. 15/231,745, 4 pages. |
| Office Action, dated Feb. 22, 2018, received in Danish Patent Application No. 201670587, which corresponds with U.S. Appl. No. 15/231,745, 4 pages. |
| Office Action, dated Dec. 18, 2018, received in Danish Patent Application No. 201670587, which corresponds with U.S. Appl. No. 15/231,745, 4 pages. |
| Office Action, dated Dec. 14, 2016, received in Danish Patent Application No. 201670590, which corresponds with U.S. Appl. No. 15/231,745, 9 pages. |
| Office Action, dated Jul. 6, 2017, received in Danish Patent Application No. 201670590, which corresponds with U.S. Appl. No. 15/231,745, 3 pages. |
| Office Action, dated Jan. 10, 2018, received in Danish Patent Application No. 201670590, which corresponds with U.S. Appl. No. 15/231,745, 2 pages. |
| Patent, dated May 28, 2018, received in Danish Patent Application No. 201670590, which corresponds with U.S. Appl. No. 15/231,745, 2 pages. |
| Office Action, dated Nov. 10, 2016, received in Danish Patent Application No. 201670591, which corresponds with U.S. Appl. No. 15/231,745, 12 pages. |
| Office Action, dated Apr. 11, 2018, received in Danish Patent Application No. 201670591, which corresponds with U.S. Appl. No. 15/231,745, 3 pages. |
| Office Action, dated Nov. 23, 2018, received in Danish Patent Application No. 201670591, which corresponds with U.S. Appl. No. 15/231,745, 7 pages. |
| Office Action, dated Oct. 26, 2016, received in Danish Patent Application No. 201670592, which corresponds with U.S. Appl. No. 15/231,745, 8 pages. |
| Office Action, dated Jan. 5, 2017, received in Danish Patent Application No. 201670592, which corresponds with U.S. Appl. No. 15/231,745, 3 pages. |
| Office Action, dated Jan. 30, 2018, received in Danish Patent Application No. 201670592, which corresponds with U.S. Appl. No. 15/231,745, 2 pages. |
| Notice of Allowance, dated Mar. 27, 2018, received in Danish Patent Application No. 201670592, which corresponds with U.S. Appl. No. 15/231,745, 2 pages. |
| Patent, dated May 28, 2018, received in Danish Patent Application No. 201670592, which corresponds with U.S. Appl. No. 15/231,745, 2 pages. |
| Office Action, dated Oct. 12, 2016, received in Danish Patent Application No. 201670593, which corresponds with U.S. Appl. No. 15/231,745, 7 pages. |
| Patent, dated Oct. 30, 2017, received in Danish Patent Application No. 201670593, which corresponds with U.S. Appl. No. 15/231,745, 3 pages. |
| Notice of Allowance, dated Nov. 1, 2019, received in Japanese Patent Application No. 2018-158502, which corresponds with U.S. Appl. No. 15/231,745, 5 pages. |
| Patent, dated Nov. 29, 2019, received in Japanese Patent Application No. 2018-158502, which corresponds with U.S. Appl. No. 15/231,745, 3 pages. |
| Notice of Allowance, dated Oct. 4, 2018, received in U.S. Appl. No. 15/272,327, 46 pages. |
| Notice of Acceptance, dated Mar. 2, 2018, received in Australian Patent Application No. 2018200705, which corresponds with U.S. Appl. No. 15/272,327, 3 pages. |
| Certificate of Grant, dated Jun. 28, 2018, received in Australian Patent Application No. 2018200705, which corresponds with U.S. Appl. No. 15/272,327, 4 pages. |
| Office Action, dated Mar. 22, 2019, received in Australian Patent Application No. 2018204234, which corresponds with U.S. Appl. No. 15/272,327, 7 pages. |
| Notice of Acceptance, dated Dec. 10, 2019, received in Australian Patent Application No. 2018204234, which corresponds with U.S. Appl. No. 15/272,327, 3 pages. |
| Certificate of Grant, dated Apr. 2, 2020, received in Australian Patent Application No. 2018204234, which corresponds with U.S. Appl. No. 15/272,327, 1 page. |
| Office Action, dated Aug. 31, 2020, received in Chinese Patent Application No. 201810151593.X, which corresponds with U.S. Appl. No. 15/272,327, 10 pages. |
| Notice of Allowance, dated Jan. 27, 2021, received in Chinese Patent Application No. 201810151593.X, which corresponds with U.S. Appl. No. 15/272,327, 3 pages. |
| Patent, dated Mar. 19, 2021, received in Chinese Patent Application No. 201810151593.X, which corresponds with U.S. Appl. No. 15/272,327, 6 pages. |
| Office Action, dated Sep. 14, 2018, received in European Patent Application No. 15155939.4, which corresponds with U.S. Appl. No. 15/272,327, 5 pages. |
| Intention to Grant, dated Mar. 19, 2019, received in European Patent Application No. 15155939.4, which corresponds with U.S. Appl. No. 15/272,327, 6 pages. |
| Decision to Grant, dated Apr. 26, 2019, received in European Patent Application No. 15155939.4, which corresponds with U.S. Appl. No. 15/272,327, 2 pages. |
| Patent, dated May 22, 2019, received in European Patent Application No. 15155939.4, which corresponds with U.S. Appl. No. 15/272,327, 1 page. |
| Notice of Allowance, dated Jul. 30, 2018, received in Japanese Patent Application No. 2018-506989, which corresponds with U.S. Appl. No. 15/272,327, 4 pages. |
| Patent, dated Aug. 31, 2018, received in Japanese Patent Application No. 2018-506989, which corresponds with U.S. Appl. No. 15/272,327, 3 pages. |
| Office Action, dated Oct. 26, 2018, received in U.S. Appl. No. 15/272,341, 22 pages. |
| Final Office Action, dated Mar. 25, 2019, received in U.S. Appl. No. 15/272,341, 25 pages. |
| Notice of Allowance, dated Feb. 20, 2020, received in U.S. Appl. No. 15/272,341, 12 pages. |
| Office Action, dated Jul. 27, 2017, received in Australian Patent Application No. 2017100535, which corresponds with U.S. Appl. No. 15/272,341, 4 pages. |
| Notice of Allowance, dated Sep. 20, 2018, received in U.S. Appl. No. 15/272,343, 44 pages. |
| Office Action, dated Jun. 5, 2019, received in Chinese Patent Application No. 201810071627.4, which corresponds with U.S. Appl. No. 15/272,343, 6 pages. |
| Notice of Allowance, dated Dec. 11, 2019, received in Chinese Patent Application No. 201810071627.4, which corresponds with U.S. Appl. No. 15/272,343, 4 pages. |
| Patent, dated Mar. 3, 2020, received in Chinese Patent Application No. 201810071627.4, which corresponds with U.S. Appl. No. 15/272,343, 7 pages. |
| Office Action, dated Jan. 8, 2019, received in European Patent Application No. 17206374.5, which corresponds with U.S. Appl. No. 15/272,343, 5 pages. |
| Intention to Grant, dated May 13, 2019, received in European Patent Application No. 17206374.5, which corresponds with U.S. Appl. No. 15/272,343, 7 pages. |
| Decision to Grant, dated Sep. 12, 2019, received in European Patent Application No. 17206374.5, which corresponds with U.S. Appl. No. 15/272,343, 3 pages. |
| Patent, Oct. 9, 2019, received in European Patent Application No. 17206374.5, which corresponds with U.S. Appl. No. 15/272,343, 3 pages. |
| Office Action, dated Oct. 15, 2018, received in U.S. Appl. No. 15/272,345. 31 pages. |
| Final Office Action, dated Apr. 2, 2019, received in U.S. Appl. No. 15/272,345, 28 pages. |
| Notice of Allowance, dated Apr. 22, 2020, received in U.S. Appl. No. 15/272,345, 12 pages. |
| Notice of Acceptance, dated Mar. 2, 2018, received in Australian Patent Application No. 2016304832, which corresponds with U.S. Appl. No. 15/272,345, 3 pages. |
| Certificate of Grant, dated Jun. 28, 2018, received in Australian Patent Application No. 2016304832, which corresponds with U.S. Appl. No. 15/272,345, 4 pages. |
| Office Action, dated Oct. 22, 2019, received in Chinese Patent Application No. 201680022696.5, which corresponds with U.S. Appl. No. 15/272,345, 7 pages. |
| Notice of Allowance, dated Jul. 6, 2020, received in Chinese Patent Application No. 201680022696.5, which corresponds with U.S. Appl. No. 15/272,345, 5 pages. |
| Patent, dated Sep. 18, 2020, received in Chinese Patent Application No. 201680022696.5, which corresponds with U.S. Appl. No. 15/272,345, 6 pages. |
| Office Action, dated Apr. 20, 2018, received in European Patent Application No. 16756862.5, which corresponds with U.S. Appl. No. 15/272,345, 15 pages. |
| Office Action, dated Nov. 13, 2018, received in European Patent Application No. 16756862.5, which corresponds with U.S. Appl. No. 15/272,345, 5 pages. |
| Decision to Grant, dated Jan. 31, 2019, received in European Patent Application No. 16756862.5, which corresponds with U.S. Appl. No. 15/272,345, 5 pages. |
| Patent, dated Feb. 27, 2019, received in European Patent Application No. 16756862.5, which corresponds with U.S. Appl. No. 15/272,345, 3 pages. |
| Patent, dated Feb. 7, 2020, received in Hong Kong Patent Application No. 18101477.0, which corresponds with U.S. Appl. No. 15/272,345, 6 pages. |
| Office Action, dated Dec. 4, 2020, received in Japanese Patent Application No. 2019-212493, which corresponds with U.S. Appl. No. 15/272,345, 5 pages. |
| Notice of Allowance, dated Aug. 27, 2021, received in Japanese Patent Application No. 2019-212493, which corresponds with U.S. Appl. No. 15/272,345, 2 pages. |
| Patent, dated Sep. 29, 2021, received in Japanese Patent Application No. 2019-212493, which corresponds with U.S. Appl. No. 15/272,345, 4 pages. |
| Office Action, dated Mar. 7, 2018, received in U.S. Appl. No. 15/482,618, 7 pages. |
| Notice of Allowance, dated Aug. 15, 2018, received in U.S. Appl. No. 15/482,618, 7 pages. |
| Office Action, dated Apr. 23, 2018, received in U.S. Appl. No. 15/499,691, 29 pages. |
| Notice of Allowance, dated Oct. 12, 2018, received in U.S. Appl. No. 15/499,693, 8 pages. |
| Office Action, dated May 11, 2020, received in Australian Patent Application No. 2019203776, which corresponds with U.S. Appl. No. 15/499,693, 4 pages. |
| Notice of Acceptance, dated Jul. 22, 2020, received in Australian Patent Application No. 2019203776, which corresponds with U.S. Appl. No. 15/499,693, 3 pages. |
| Certificate of Grant, dated Nov. 26, 2020, received in Australian Patent Application No. 2019203776, which corresponds with U.S. Appl. No. 15/499,693, 3 pages. |
| Office action, dated Nov. 20, 2020, received in Japanese Patent Application No. 2019-200174, which corresponds with U.S. Appl. No. 15/499,693, 6 pages. |
| Notice of Allowance, dated Jul. 16, 2021, received in Japanese Patent Application No. 2019-200174, which corresponds with U.S. Appl. No. 15/499,693, 2 pages. |
| Patent, dated Aug. 18, 2021, received in Japanese Patent Application No. 2019-200174, which corresponds with U.S. Appl. No. 15/499,693, 3 pages. |
| Office Action, dated Aug. 2, 2019, received in Korean Patent Application No. 2019-7009439, which corresponds with U.S. Appl. No. 15/499,693, 3 pages. |
| Notice of Allowance, dated Dec. 27, 2019, received in Korean Patent Application No. 2019-7009439, which corresponds with U.S. Appl. No. 15/499,693, 5 pages. |
| Patent, dated Mar. 27, 2020, received in Korean Patent Application No. 2019-7009439, which corresponds with U.S. Appl. No. 15/499,693, 4 pages. |
| Office Action, dated Aug. 30, 2017, received in U.S. Appl. No. 15/655,749, 22 pages. |
| Final Office Action, dated May 10, 2018, received in U.S. Appl. No. 15/655,749, 19 pages. |
| Office Action, dated Jan. 24, 2019, received in U.S. Appl. No. 15/655,749, 25 pages. |
| Final Office Action, dated Jul. 1, 2019, received in U.S. Appl. No. 15/655,749, 24 pages. |
| Notice of Allowance, dated Feb. 20, 2020, received in U.S. Appl. No. 15/655,749, 10 pages. |
| Office Action, dated Feb. 3, 2020, received in Chinese Patent Application No. 201710331254.5, which corresponds with U.S. Appl. No. 15/655,749, 8 pages. |
| Office Action, dated Mar. 22, 2021, received in Chinese Patent Application No. 201710331254.5, which corresponds with U.S. Appl. No. 15/655,749, 4 pages. |
| Notice of Allowance, dated May 27, 2021, received in Chinese Patent Application No. 201710331254.5, which corresponds with U.S. Appl. No. 15/655,749, 1 page. |
| Patent, dated Jun. 25, 2021, received in Chinese Patent Application No. 201710331254.5, which corresponds with U.S. Appl. No. 15/655,749, 7 pages. |
| Notice of Allowance, dated Apr. 18, 2019, received in Korean Patent Application No. 2017-7034248, which corresponds with U.S. Appl. No. 15/655,749, 5 pages. |
| Patent, dated Jul. 3, 2019, received in Korean Patent Application No. 2017-7034248, which corresponds with U.S. Appl. No. 15/655,749, 5 pages. |
| Office Action, dated Aug. 1, 2019, received in U.S. Appl. No. 15/785,372, 22 pages. |
| Final Office Action, dated Feb. 5, 2020, received in U.S. Appl. No. 15/785,372, 26 pages. |
| Office Action, dated Jul. 23, 2020, received in U.S. Appl. No. 15/785,372, 23 pages. |
| Final Office Action, dated Nov. 18, 2020, received in U.S. Appl. No. 15/785,372, 27 pages. |
| Notice of Allowance, dated Jul. 14, 2021, received in U.S. Appl. No. 15/785,372, 11 pages. |
| Notice of Allowance, dated Oct. 22, 2021, received in U.S. Appl. No. 15/785,372, 11 pages. |
| Office Action, dated Oct. 31, 2017, received in U.S. Appl. No. 15/723,069, 7 pages. |
| Notice of Allowance, dated Dec. 21, 2017, received in U.S. Appl. No. 15/723,069, 7 pages. |
| Office Action, dated Apr. 11, 2019, received in U.S. Appl. No. 15/889,115, 9 pages. |
| Final Office Action, dated Oct. 28, 2019, received in U.S. Appl. No. 15/889,115, 12 pages. |
| Notice of Allowance, dated May 19, 2020, received in U.S. Appl. No. 15/889,115, 9 pages. |
| Office Action, dated Jul. 25, 2019, received in U.S. Appl. No. 15/979,347, 14 pages. |
| Final Office Action, dated Feb. 27, 2020, received in U.S. Appl. No. 15/979,347, 19 pages. |
| Office Action, dated Jul. 14, 2020, received in U.S. Appl. No. 15/979,347, 10 pages. |
| Final Office Action, dated Jan. 25, 2021, received in U.S. Appl. No. 15/979,347, 12 pages. |
| Office Action, dated Sep. 25, 2020, received in U.S. Appl. No. 15/994,843, 5 pages. |
| Notice of Allowance, dated Jan. 22, 2021, received in U.S. Appl. No. 15/994,843, 8 pages. |
| Office Action, dated Nov. 25, 2019, received in U.S. Appl. No. 16/049,725, 9 pages. |
| Notice of Allowance, dated May 14, 2020, received in U.S. Appl. No. 16/049,725, 9 pages. |
| Office Action, dated May 31, 2019, received in Australian Patent Application No. 2018253539, which corresponds with U.S. Appl. No. 16/049,725, 3 pages. |
| Notice of Acceptance, dated Apr. 2, 2020, received in Australian Patent Application No. 2018253539, which corresponds with U.S. Appl. No. 16/049,725, 3 pages. |
| Certificate of Grant, dated Aug. 13, 2020, received in Australian Patent Application No. 2018253539, which corresponds with U.S. Appl. No. 16/049,725, 3 pages. |
| Notice of Allowance, dated Oct. 10, 2019, received in U.S. Appl. No. 16/102,409, 9 pages. |
| Office Action, dated Nov. 29, 2019, received in U.S. Appl. No. 16/136,163, 9 pages. |
| Final Office Action, dated Jun. 9, 2020, received in U.S. Appl. No. 16/136,163, 10 pages. |
| Office Action, dated Sep. 17, 2020, received in U.S. Appl. No. 16/136,163, 13 pages. |
| Final Office Action, dated May 20, 2021, received in U.S. Appl. No. 16/136,163, 13 pages. |
| Office Action, dated Nov. 23, 2021, received in U.S. Appl. No. 16/136,163, 27 pages. |
| Office Action, dated Mar. 9, 2020, received in U.S. Appl. No. 16/145,954, 15 pages. |
| Office Action, dated Dec. 10, 2020, received in U.S. Appl. No. 16/145,954, 5 pages. |
| Office Action, dated Mar. 6, 2020, received in U.S. Appl. No. 16/154,591, 16 pages. |
| Final Office Action, dated Oct. 1, 2020, received in U.S. Appl. No. 16/154,591, 19 pages. |
| Office Action, dated Mar. 4, 2021, received in U.S. Appl. No. 16/154,591, 20 pages. |
| Office Action, dated May 4, 2020, received in Australian Patent Application No. 2019203175, which corresponds with U.S. Appl. No. 16/154,591, 4 pages. |
| Office Action, dated Oct. 13, 2020, received in Australian Patent Application No. 2019203175, which corresponds with U.S. Appl. No. 16/154,591, 5 pages. |
| Office Action, dated Dec. 2, 2019, received in Japanese Patent Application No. 2018-202048, which corresponds with U.S. Appl. No. 16/154,591, 6 pages. |
| Notice of Allowance, dated Jun. 1, 2020, received in Japanese Patent Application No. 2018-202048, which corresponds with U.S. Appl. No. 16/154,591, 3 pages. |
| Patent, dated Jun. 25, 2020, received in Japanese Patent Application No. 2018-202048, which corresponds with U.S. Appl. No. 16/154,591, 4 pages. |
| Office Action, dated Aug. 20, 2019, received in Korean Patent Application No. 2019-7019946, which corresponds with U.S. Appl. No. 16/154,591, 6 pages. |
| Office Action, dated Feb. 27, 2020, received in Korean Patent Application No. 2019-7019946, which corresponds with U.S. Appl. No. 16/154,591, 5 pages. |
| Office Action, dated Mar. 29, 2021, received in Korean Patent Application No. 2019-7019946, which corresponds with U.S. Appl. No. 16/154,591, 6 pages. |
| Notice of Allowance, dated Aug. 26, 2021, received in Korean Patent Application No. 2019-7019946, which corresponds with U.S. Appl. No. 16/154,591, 2 pages. |
| Patent, dated Sep. 7, 2021, received in Korean Patent Application No. 2019-7019946, which corresponds with U.S. Appl. No. 16/154,591, 4 pages. |
| Office Action, dated Nov. 25, 2019, received in U.S. Appl. No. 16/174,170, 31 pages. |
| Final Office Action, dated Mar. 19, 2020, received in U.S. Appl. No. 16/174,170, 25 pages. |
| Notice of Allowance, dated Jun. 18, 2020, received in U.S. Appl. No. 16/174,170, 19 pages. |
| Notice of Allowance, dated Aug. 26, 2020, received in U.S. Appl. No. 16/240,669, 18 pages. |
| Office Action, dated Oct. 30, 2020, received in U.S. Appl. No. 16/230,707, 20 pages. |
| Notice of Allowance, dated Feb. 18, 2021, received in U.S. Appl. No. 16/230,707, 9 pages. |
| Office Action, dated Aug. 10, 2020, received in U.S. Appl. No. 16/240,672, 13 pages. |
| Final Office Action, dated Nov. 27, 2020, received in U.S. Appl. No. 16/240,672, 12 pages. |
| Office Action, dated May 17, 2021, received in U.S. Appl. No. 16/240,672, 14 pages. |
| Notice of Allowance, dated Sep. 2, 2021, received in U.S. Appl. No. 16/240,672, 13 pages. |
| Office Action, dated Sep. 24, 2020, received in Australian Patent Application No. 2019268116, which corresponds with U.S. Appl. No. 16/240,672, 4 pages. |
| Office Action, dated Jan. 28, 2021, received in Australian Patent Application No. 2019268116, which corresponds with U.S. Appl. No. 16/240,672, 4 pages. |
| Notice of Allowance, dated Sep. 20, 2021, received in Australian Patent Application No. 2019268116, which corresponds with U.S. Appl. No. 16/240,672, 3 pages. |
| Patent, dated Jan. 27, 2022, received in Australian Patent Application No. 2019268116, which corresponds with U.S. Appl. No. 16/240,672, 3 pages. |
| Office Action, dated Apr. 21, 2021, received in European Patent Application No. 19195414.8, which corresponds with U.S. Appl. No. 16/240,672, 7 pages. |
| Notice of Allowance, dated May 22, 2020, received in Japanese Patent Application No. 2019-027634, which corresponds with U.S. Appl. No. 16/240,672, 5 pages. |
| Patent, dated Jun. 23, 2020, received in Japanese Patent Application No. 2019-027634, which corresponds with U.S. Appl. No. 16/240,672, 4 pages. |
| Office Action, dated May 22, 2019, received in U.S. Appl. No. 16/230,743, 7 pages. |
| Notice of Allowance, dated Sep. 11, 2019, received in U.S. Appl. No. 16/230,743, 5 pages. |
| Office Action, dated Mar. 6, 2020, received in U.S. Appl. No. 16/243,834, 19 pages. |
| Notice of Allowance, dated Sep. 24, 2020, received in U.S. Appl. No. 16/243,834, 10 pages. |
| Office Action, dated Dec. 18, 2019, received in Australian Patent Application No. 2018282409, which corresponds with U.S. Appl. No. 16/243,834, 3 pages. |
| Office Action, dated Sep. 18, 2020, received in Australian Patent Application No. 2018282409, which corresponds with U.S. Appl. No. 16/243,834, 3 pages. |
| Notice of Acceptance, dated Oct. 21, 2020, received in Australian Patent Application No. 2018282409, which corresponds with U.S. Appl. No. 16/243,834, 3 pages. |
| Certificate of Grant, dated Feb. 18, 2021, received in Australian Patent Application No. 2018282409, which corresponds with U.S. Appl. No. 16/243,834, 3 pages. |
| Office Action, dated Aug. 7, 2020, received in Japanese Patent Application No. 2019-058800, which corresponds with U.S. Appl. No. 16/243,834, 8 pages. |
| Office Action, dated Feb. 12, 2021, received in Japanese Patent Application No. 2019-058800, which corresponds with U.S. Appl. No. 16/243,834, 2 pages. |
| Office Action, dated Jul. 5, 2019, received in Korean Patent Application No. 2018-7037896, which corresponds with U.S. Appl. No. 16/243,834, 2 pages. |
| Notice of Allowance, dated Dec. 23, 2019, received in Korean Patent Application No. 2018-7037896, which corresponds with U.S. Appl. No. 16/243,834, 6 pages. |
| Patent, dated Mar. 13, 2020, received in Korean Patent Application No. 2018-7037896, which corresponds with U.S. Appl. No. 16/243,834, 7 pages. |
| Office Action, dated Nov. 30, 2021, received in Russian Patent Application No. 2018146112, which corresponds with U.S. Appl. No. 16/243,834, 15 pages. |
| Notice of Allowance, dated Nov. 20, 2020, received in U.S. Appl. No. 16/262,784, 8 pages. |
| Office action, dated Feb. 25, 2021, received in Australian Patent Application No. 2020201648, which corresponds with U.S. Appl. No. 16/262,784, 3 pages. |
| Notice of Allowance, dated Dec. 14, 2021, received in Australian Patent Application No. 2020201648, which corresponds with U.S. Appl. No. 16/262,784, 3 pages. |
| Office Action, dated Feb. 5, 2021, received in U.S. Appl. No. 16/262,800, 53 pages. |
| Final Office Action, dated Jun. 4, 2021, received in U.S. Appl. No. 16/262,800, 65 pages. |
| Notice of Allowance, dated Jan. 24, 2022, received in U.S. Appl. No. 16/262,800, 26 pages. |
| Office Action, dated Sep. 15, 2020, received in European Patent Application No. 19194439.6, which corresponds with U.S. Appl. No. 16/262,800, 6 pages. |
| Office Action, dated Mar. 25, 2021, received in European Patent Application No. 19194439.6, which corresponds with U.S. Appl. No. 16/262,800, 5 pages. |
| Notice of Allowance, dated Apr. 19, 2019, received in U.S. Appl. No. 16/252,478, 11 pages. |
| Office Action, dated Jun. 11, 2020, received in Australian Patent Application No. 2019257437, which corresponds with U.S. Appl. No. 16/252,478, 3 pages. |
| Notice of Allowance, dated Sep. 15, 2020, received in Australian Patent Application No. 2019257437, which corresponds with U.S. Appl. No. 16/252,478, 3 pages. |
| Notice of Allowance, dated Dec. 13, 2019, received in Korean Patent Application No. 2019-7033444, which corresponds with U.S. Appl. No. 16/252,478, 6 pages. |
| Patent, dated Mar. 12, 2020, received in Korean Patent Application No. 2019-7033444, which corresponds with U.S. Appl. No. 16/252,478, 6 pages. |
| Office action, dated Aug. 27, 2020, received in U.S. Appl. No. 16/241,883, 11 pages. |
| Notice of Allowance, dated Sep. 28, 2020, received in U.S. Appl. No. 16/241,883, 10 pages. |
| Office Action, dated Aug. 10, 2021, received in European Patent Application No. 19181042.3, which corresponds with U.S. Appl. No. 16/241,883, 7 pages. |
| Office Action, dated Oct. 1, 2021, received in Japanese Patent Applicat No. 2020-174097, which corresponds with U.S. Appl. No. 16/241,883, 2 pages. |
| Office Action, dated Jul. 15, 2019, received in U.S. Appl. No. 16/258,394, 8 pages. |
| Notice of Allowance, dated Nov. 6, 2019, received in U.S. Appl. No. 16/258,394, 8 pages. |
| Office Action, dated Oct. 21, 2021, received in Australian Patent Application No. 2020267298, which corresponds with U.S. Appl. No. 16/258,394, 2 pages. |
| Notice of Allowance, dated Jan. 14, 2022, received in Australian Patent Application No. 2020267298, which corresponds with U.S. Appl. No. 16/258,394, 3 pages. |
| Office Action, dated May 14, 2020, received in U.S. Appl. No. 16/354,035, 16 pages. |
| Notice of Allowance, dated Aug. 25, 2020, received in U.S. Appl. No. 16/354,035, 14 pages. |
| Office Action, dated Jun. 9, 2021, received in U.S. Appl. No. 16/896,141, 21 pages. |
| Final Office Action, dated Dec. 13, 2021, received in U.S. Appl. No. 16/896,141, 29 pages. |
| Office Action, dated Oct. 11, 2019, received in Australian Patent Application No. 2019202417, which corresponds with U.S. Appl. No. 16/896,141, 4 pages. |
| Notice of Allowance, dated Jul. 6, 2020, received in Australian Patent Application No. 2019202417, which corresponds with U.S. Appl. No. 16/896,141, 3 pages. |
| Certificate of Grant, dated Nov. 5, 2020, received in Australian Patent Application No. 2019202417, which corresponds with U.S. Appl. No. 16/896,141, 4 pages. |
| Office Action, dated Aug. 21, 2020, received in Japanese Patent Application No. 2019-047319, which corresponds with U.S. Appl. No. 16/896,141, 6 pages. |
| Office Action, dated Apr. 9, 2021, received in Japanese Patent Application No. 2019-047319, which corresponds with U.S. Appl. No. 16/896,141, 2 pages. |
| Office Action, dated Aug. 30, 2019, received in Korean Patent Application No. 2019-7019100, 2 pages. |
| Notice of Allowance, dated Nov. 1, 2019, received in Korean Patent Application No. 2019-7019100, 5 pages. |
| Patent, dated Jan. 31, 2020, received in Korean Patent Application No. 2019-7019100, 5 pages. |
| Office Action, dated May 14, 2020, received in U.S. Appl. No. 16/509,438, 16 pages. |
| Notice of Allowance, dated Jan. 6, 2021, received in U.S. Appl. No. 16/509,438, 5 pages. |
| Notice of Allowance, dated Apr. 29, 2021, received in U.S. Appl. No. 16/509,438, 9 pages. |
| Office Action, dated Sep. 6, 2021, received in Chinese Patent Application No. 201910718931.8, 6 pages. |
| Notice of Allowance, dated May 20, 2020, received in U.S. Appl. No. 16/534,214, 16 pages. |
| Office Action, dated Oct. 7, 2020, received in U.S. Appl. No. 16/563,505, 20 pages. |
| Final Office Action, dated May 12, 2021, received in U.S. Appl. No. 16/563,505, 19 pages. |
| Office Action, dated Oct. 5, 2021, received in U.S. Appl. No. 16/563,505, 19 pages. |
| Office Action, dated Oct. 19, 2020, received in U.S. Appl. No. 16/685,773, 15 pages. |
| Final Office Action, dated Feb. 2, 2021, received in U.S. Appl. No. 16/685,773, 20 pages. |
| Office Action, dated Dec. 14, 2021, received in U.S. Appl. No. 16/685,773, 20 pages. |
| Office Action, dated Oct. 30, 2020, received in U.S. Appl. No. 16/824,490, 15 pages. |
| Notice of Allowance, dated Feb. 24, 2021, received in U.S. Appl. No. 16/824,490, 8 pages. |
| Office Action, dated Sep. 21, 2020, received in U.S. Appl. No. 16/803,904, 5 pages. |
| Notice of Allowance, dated Jan. 6, 2021, received in U.S. Appl. No. 16/803,904, 9 pages. |
| Notice of Allowance, dated Oct. 25, 2021, received in U.S. Appl. No. 17/003,869, 21 pages. |
| Office Action, dated Aug. 30, 2021, received in Australian Patent Application No. 2020244406, which corresponds with U.S. Appl. No. 17/003,869, 4 pages. |
| Notice of Allowance, dated Jan. 14, 2022, received in Australian Patent Application No. 2020244406, which corresponds with U.S. Appl. No. 17/003,869, 3 pages. |
| Notice of Allowance, dated May 4, 2020, received in Korean Patent Application No. 2019-7033444, which corresponds with U.S. Appl. No. 17/003,869, 5 pages. |
| Patent, dated Jun. 3, 2020, received in Korean Patent Application No. 2019-7033444, which corresponds with U.S. Appl. No. 17/003,869, 7 pages. |
| Notice of Allowance, dated Dec. 21, 2021, received in U.S. Appl. No. 16/921,083, 25 pages. |
| Office Action, dated Sep. 8, 2021, received in Japanese Patent Application No. 2020-106360, 2 pages. |
| Office Action, dated May 26, 2021, received in U.S. Appl. No. 16/988,509, 25 pages. |
| Final Office Action, dated Sep. 16, 2021, received in U.S. Appl. No. 16/988,509, 38 pages. |
| Office Action, dated Feb. 23, 2021, received in Korean Patent Application No. 2020-7031330, which corresponds with U.S. Appl. No. 15/272,398, 3 pages. |
| Office Action, dated Aug. 27, 2021, received in Korean Patent Application No. 2020-7031330, which corresponds with U.S. Appl. No. 15/272,398, 6 pages. |
| Office Action, dated Dec. 23, 2021, received in Korean Patent Application No. 2020-7031330, which corresponds with U.S. Appl. No. 15/272,398, 8 pages. |
| Office Action, dated Oct. 26, 2021, received in U.S. Appl. No. 17/103,899, 21 pages. |
| Office Action, dated Oct. 29, 2021, received in Korean Patent Application No. 2021-7031223, 2 pages. |
| Patent, dated Jan. 27, 2022, received in Korean Patent Application No. 2021-7031223, 5 pages. |
| Notice of Allowance, dated Feb. 21, 2022, received in Korean Patent Application No. 2022-7003345, 2 pages. |
| International Search Report and Written Opinion dated May 26, 2014, received in International Application No. PCT/US2013/040053, which corresponds to U.S. Appl. No. 14/535,671, 32 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040053, which corresponds to U.S. Appl. No. 14/535,671, 26 pages. |
| International Search Report and Written Opinion dated Apr. 7, 2014, received in International Application No. PCT/US2013/069472, which corresponds to U.S. Appl. No. 14/608,895, 24 pages. |
| International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Patent Application No. PCT/US2013/069472, which corresponds with U.S. Appl. No. 14/608,895, 18 pages. |
| International Search Report and Written Opinion dated Aug. 7, 2013, received in International Application No. PCT/US2013/040054, which corresponds to U.S. Appl. No. 14/536,235, 12 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040054, which corresponds to U.S. Appl. No. 14/536,235, 11 pages. |
| International Search Report and Written Opinion dated Aug. 7, 2013, received in International Application No. PCT/US2013/040056, which corresponds to U.S. Appl. No. 14/536,367, 12 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040056, which corresponds to U.S. Appl. No. 14/536,367, 11 pages. |
| Extended European Search Report, dated Nov. 6, 2015, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 7 pages. |
| Extended European Search Report, dated Jul. 30, 2018, received in European Patent Application No. 18180503.7, which corresponds with U.S. Appl. No. 14/536,426, 7 pages. |
| International Search Report and Written Opinion dated Aug. 6, 2013, received in International Application No. PCT/US2013/040058, which corresponds to U.S. Appl. No. 14/536,426, 12 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040058, which corresponds to U.S. Appl. No. 14/536,426, 11 pages. |
| International Search Report and Written Opinion dated Feb. 5, 2014, received in International Application No. PCT/US2013/040061, which corresponds to U.S. Appl. No. 14/536,464, 30 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040061, which corresponds to U.S. Appl. No. 14/536,464, 26 pages. |
| International Search Report and Written Opinion dated May 8, 2014, received in International Application No. PCT/US2013/040067, which corresponds to U.S. Appl. No. 14/536,644, 45 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040067, which corresponds to U.S. Appl. No. 14/536,644, 36 pages. |
| International Search Report and Written Opinion dated Mar. 12, 2014, received in International Application No. PCT/US2013/069479, which corresponds with U.S. Appl. No. 14/608,926, 14 pages. |
| International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Patent Application No. PCT/US2013/069479, which corresponds with U.S. Appl. No. 14/608,926, 11 pages. |
| International Search Report and Written Opinion dated Aug. 7, 2013, received in International Application No. PCT/US2013/040070, which corresponds to U.S. Appl. No. 14/535,646, 12 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040070, which corresponds to U.S. Appl. No. 14/535,646, 10 pages. |
| International Search Report and Written Opinion dated Apr. 7, 2014, received in International Application No. PCT/US2013/040072, which corresponds to U.S. Appl. No. 14/536,141, 38 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040072, which corresponds to U.S. Appl. No. 14/536,141, 32 pages. |
| Extended European Search Report, dated Dec. 5, 2018, received in European Patent Application No. 18194127.9, which corresponds with U.S. Appl. No. 14/608,942, 8 pages. |
| International Search Report and Written Opinion dated Apr. 7, 2014, received in International Application No. PCT/US2013/069483, which corresponds with U.S. Appl. No. 14/608,942, 18 pages. |
| International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Application No. PCT/2013/069483, which corresponds to U.S. Appl. No. 14/608,942, 13 pages. |
| International Search Report and Written Opinion dated Mar. 3, 2014, received in International Application No. PCT/US2013/040087, which corresponds to U.S. Appl. No. 14/536,166, 35 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013/040087, which corresponds to U.S. Appl. No. 14/536,166, 29 pages. |
| International Search Report and Written Opinion dated Aug. 7, 2013, received in International Application No. PCT/US2013/040093, which corresponds to U.S. Appl. No. 14/536,203, 11 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013040093, which corresponds to U.S. Appl. No. 14,536,203, 9 pages. |
| International Search Report and Written Opinion dated Jul. 9, 2014, received in International Application No. PCT/US2013/069484, which corresponds with U.S. Appl. No. 14/608,965, 17 pages. |
| International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Patent Application No. PCT/US2013/069484, which corresponds with U.S. Appl. No. 14/608,965, 12 pages. |
| International Search Report and Written Opinion dated Feb. 5, 2014, received in International Application No. PCT/US2013/040098, which corresponds to U.S. Appl. No. 14/536,247, 35 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013/040098, which corresponds to U.S. Appl. No. 14/536,247, 27 pages. |
| Extended European Search Report, dated Oct. 7, 2016, received in European Patent Application No. 16177863.4, which corresponds with U.S. Appl. No. 14/536,267, 12 pages. |
| Extended European Search Report, dated Oct. 30, 2018, received in European Patent Application No. 18183789.9, which corresponds with U.S. Appl. No. 14/536,267, 11 pages. |
| International Search Report and Written Opinion dated Jan. 27, 2014, received in International Application No. PCT/US2013/040101, which corresponds to U.S. Appl. No. 14/536,267, 30 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013/040101, which corresponds to U.S. Appl. No. 14/536,267, 24 pages. |
| Extended European Search Report, dated Nov. 24, 2017, received in European Patent Application No. 17186744.3, which corresponds with U.S. Appl. No. 14/536,291, 10 pages. |
| International Search Report and Written Opinion dated Jan. 8, 2014, received in International Application No. PCT/US2013/040108, which corresponds to U.S. Appl. No. 14/536,291, 30 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013/040108, which corresponds to U.S. Appl. No. 14/536,291, 25 pages. |
| International Search Report and Written Opinion dated Jun. 2, 2014, received in International Application No. PCT/US2013/069486, which corresponds with U.S. Appl. No. 14/608,985, 7 pages. |
| International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Patent Application No. PCT/US2013/069486, which corresponds with U.S. Appl. No. 14/608,985, 19 pages. |
| International Search Report and Written Opinion dated Mar. 6, 2014, received in International Application No. PCT/US2013/069489, which corresponds with U.S. Appl. No. 14/609,006, 12 pages. |
| International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Patent Application No. PCT/US2013/069489, which corresponds with U.S. Appl. No. 14/609,006, 10 pages. |
| Extended European Search Report, dated Mar. 15, 2017, received in European Patent Application No. 17153418.3, which corresponds with U.S. Appl. No. 14/536,648, 7 pages. |
| Search Report, dated Apr. 13, 2017, received in Dutch Patent Application No. 2016452, which corresponds with U.S. Appl. No. 14/864,737, 22 pages. |
| Search Report, dated Jun. 22, 2017, received in Dutch Patent Application No. 2016375, which corresponds with U.S. Appl. No. 14/866,981, 17 pages. |
| International Search Report and Written Opinion, dated Oct. 14, 2016, received in International Patent Application No. PCT/US2016/020697, which corresponds with U.S. Appl. No. 14/866,981, 21 pages. |
| Search Report, dated Jun. 19, 2017, received in Dutch Patent Application No. 2016377, which corresponds with U.S. Appl. No. 14/866,159, 13 pages. |
| International Search Report and Written Opinion, dated Apr. 25, 2016, received in International Patent Application No. PCT/US2016/018758, which corresponds with U.S. Appl. No. 14/866,159, 15 pages. |
| Extended European Search Report, dated Oct. 17, 2017, received in European Patent Application No. 17184437.6, Which corresponds with U.S. Appl. No. 14/868,078, 8 pages. |
| Search Report, dated Apr. 13, 2017, received in Dutch Patent Application No. 2016376, which corresponds with U.S. Appl. No. 14/868,078, 15 pages. |
| International Search Report and Written Opinion, dated Jul. 21, 2016, received in International Patent Application No. PCT/US2016/019913, which corresponds with U.S. Appl. No. 14/868,078, 16 pages. |
| Search Report, dated Apr. 18, 2017, received in Dutch Patent Application No. 2016801, which corresponds with U.S. Appl. No. 14/863,432, 34 pages. |
| International Search Report and Written Opinion, dated Oct. 31, 2016, received in International Patent Application No. PCT/US2016/033578, which corresponds with U.S. Appl. No. 14/863,432, 36 pages. |
| International Search Report and Written Opinion, dated Nov. 14, 2016, received in International Patent Application No. PCT/US2016/033541, which corresponds with U.S. Appl. No. 14/866,511, 29 pages. |
| Extended European Search Report, dated Aug. 17, 2018, received in European Patent Application No. 18175195.9, which corresponds with U.S. Appl. No. 14/869,899, 13 pages. |
| International Search Report and Written Opinion, dated Aug. 29, 2016, received in International Patent Application No. PCT/US2016/021400, which corresponds with U.S. Appl. No. 14/869,899, 48 pages. |
| International Preliminary Report on Patentability, dated Sep. 12, 2017, received in International Patent Application No. PCT/US2016/021400, which corresponds with U.S. Appl. No. 14/869,899, 39 pages. |
| International Search Report and Written Opinion, dated Jan. 12, 2017, received in International Patent Application No. PCT/US2016/046419, which corresponds with U.S. Appl. No. 14/866,992, 23 pages. |
| International Search Report and Written Opinion, dated Dec. 15, 2016, received in International Patent Application No. PCT/US2016/046403, which corresponds with U.S. Appl. No. 15/009,661, 17 pages. |
| International Search Report and Written Opinion, dated Feb. 27, 2017, received in International Patent Application No. PCT/US2016/046407, which corresponds with U.S. Appl. No. 15/009,688, 30 pages. |
| International Preliminary Report on Patentability, dated Feb. 13, 2018, received in International Patent Application No. PCT/US2016/046407, which corresponds with U.S. Appl. No. 15/009,688, 20 pages. |
| Search Report, dated Feb. 15, 2018, received in Dutch Patent Application No. 2019215, which corresponds with U.S. Appl. No. 14/864,529, 13 pages. |
| Extended European Search Report, dated Nov. 14, 2019, received in European Patent Application No. 19194418.0, which corresponds with U.S. Appl. No. 14/864,580, 8 pages. |
| Search Report, dated Feb. 15, 2018, received in Dutch Patent Application No. 2019214, which corresponds with U.S. Appl. No. 14/864,601, 12 pages. |
| Extended European Search Report, dated Oct. 10, 2017, received in European Patent Application No. 17188507.2, which corresponds with U.S. Appl. No. 14/866,361, 9 pages. |
| Extended European Search Report, dated Jun. 22, 2017, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 7 pages. |
| Extended European Search Report, dated Sep. 11, 2017, received in European Patent Application No. 17163309.2, which corresponds with U.S. Appl. No. 14/866,987, 8 pages. |
| Extended European Search Report, dated Jun. 8, 2017, received in European Patent Application No. 16189425.8, which corresponds with U.S. Appl. No. 14/866,989, 8 pages. |
| Extended European Search Report, dated Aug. 2, 2018, received in European Patent Application No. 18168941.5, which corresponds with U.S. Appl. No. 14/871,236, 11 pages. |
| Extended European Search Report, dated Jul. 25, 2017, received in European Patent Application No. 17171972.7, which corresponds with U.S. Appl. No. 14/870,882, 12 pages. |
| Extended European Search Report, dated Jul. 25, 2017, received in European Patent Application No. 17172266.3, which corresponds with U.S. Appl. No. 14/871,336, 9 pages. |
| Extended European Search Report, dated Dec. 21, 2016, received in European Patent Application No. 16189790.5, which corresponds with U.S. Appl. No. 14/871,462, 8 pages. |
| Extended European Search Report, dated Mar. 8, 2019, received in European Patent Application No. 18205283.7, which corresponds with U.S. Appl. No. 15/081,771, 15 pages. |
| Extended European Search Report, dated Aug. 24, 2018, received in European Patent Application No. 18171453.6, which corresponds with U.S. Appl. No. 15/136,782, 9 pages. |
| International Search Report and Written Opinion, dated Jan. 3, 2017, received in International Patent Application No. PCT/US2016/046214, which corresponds with U.S. Appl. No. 15/231,745, 25 pages. |
| Extended European Search Report, dated May 30, 2018, received in European Patent Application No. 18155939.4, which corresponds with U.S. Appl. No. 15/272,327, 8 pages. |
| Extended European Search Report, dated Mar. 2, 2018, received in European Patent Application No. 17206374.5, which corresponds with U.S. Appl. No. 15/272,343, 11 pages. |
| Extended European Search Report, dated Oct. 6, 2020, received in European Patent Application No. 20188553.0, which corresponds with U.S. Appl. No. 15/499,693, 11 pages. |
| Extended European Search Report, dated Oct. 28, 2019, received in European Patent Application No. 19195414.8, which corresponds with U.S. Appl. No. 16/240,672, 6 pages. |
| Extended European Search Report, dated Nov. 13, 2019, received in European Patent Application No. 19194439.6, which corresponds with U.S. Appl. No. 16/262,800, 12 pages. |
| Extended European Search Report, dated Oct. 9, 2019, received in European Patent Application No. 19181042.3, which corresponds with U.S. Appl. No. 15/272,343, 10 pages. |
| International Search Report and Written Opinion, dated Jan. 11, 2022, received in International Application No. PCT/US2021/042402, which corresponds with U.S. Appl. No. 17/031,637, 50 pages. |
| Office Action, dated Mar. 2, 2023, received in Chinese Patent Application No. 202010281684.2, which corresponds with U.S. Appl. No. 14/864,601, 4 pages. |
| Office Action, dated Mar. 7, 2023, received in Brazilian Patent Application No. 11201701119-9, which corresponds with U.S. Appl. No. 14/871,236, 4 pages. |
| Office Action, dated Mar. 2, 2023, received in Indian Patent Application No. 202118003907, which corresponds with U.S. Appl. No. 16/243,834, 11 pages. |
| Office Action, dated Mar. 12, 2023, received in Chinese Patent Application No. 202010281127.0, which corresponds with U.S. Appl. No. 16/252,478, 4 pages. |
| Patent, dated Mar. 17, 2023, received in Chinese Patent Application No. 201910718931.8, 7 pages. |
| Office Action, dated Feb. 22, 2023, received in Chinese Patent Application No. 202010290361.X, which corresponds with U.S. Appl. No. 17/003,869, 4 pages. |
| Patent, dated Mar. 16, 2023, received in Australian Patent Application No. 2021200655, which corresponds with U.S. Appl. No. 17/103,899, 3 pages. |
| Final Office Action, dated Apr. 24, 2023, received in U.S. Appl. No. 17/333,810, 12 pages. |
| Office Action, dated Mar. 16, 2023, received in U.S. Appl. No. 17/351,035, 23 pages. |
| Notice of Allowance, dated Mar. 6, 2023, received in U.S. Appl. No. 17/524,692, 14 pages. |
| Office Action, dated Mar. 30, 2023, received in U.S. Appl. No. 17/875,307, 15 pages. |
| Office Action, dated Sep. 20, 2022, received in Australian Patent Application No. 2021254568, which corresponds with U.S. Appl. No. 17/560,013, 4 pages. |
| Intent to Grant, dated Jun. 1, 2023, received in European Patent Application No. 16711725.8, which corresponds with U.S. Appl. No. 14/867,990, 8 pages. |
| Notice of Allowance, dated May 19, 2023, received in Japanese Patent Application No. 2021-099049, which corresponds with U.S. Appl. No. 16/243,834, 2 pages. |
| Final Office Action, dated May 31, 2023, received in U.S. Appl. No. 17/409,573, 22 pages. |
| Notice of Allowance, dated Apr. 27, 2023, received in U.S. Appl. No. 18/089,397, 16 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20220187985 A1 | Jun 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62349096 | Jun 2016 | US | |
| 62215722 | Sep 2015 | US | |
| 62213609 | Sep 2015 | US | |
| 62203387 | Aug 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16262800 | Jan 2019 | US |
| Child | 17666495 | US | |
| Parent | 15272327 | Sep 2016 | US |
| Child | 16262800 | US | |
| Parent | 15231745 | Aug 2016 | US |
| Child | 15272327 | US |
