Patent Grant
10908559
The present disclosure relates generally to user interfaces, and more specifically to techniques for displaying user interfaces with managed display usage.
Electronic devices may include screens for displaying user interfaces. Over time, non-uniform use of screens may lead to discoloration of portions of the screen and decreased quality of displayed images.
Some techniques for displaying user interfaces using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces with managed display usage. Such methods and interfaces optionally complement or replace other methods for managing display usage. Such methods improve image quality (e.g., reduce deterioration of image quality) of displayed user interfaces as an electronic device ages and improve the durability of display devices used to display user interfaces. In addition, such methods and interfaces also reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges. Furthermore, such methods and interfaces also reduce the number of unnecessary, extraneous, or repetitive input required at computing devices, such as smartphones and smartwatches.
In accordance with some embodiments, a method is described. The method comprises: at an electronic device having a display: while the electronic device is in a first mode, displaying on the display, a first user interface including: a first time indicator, displayed at a first brightness level; and a first graphical object, displayed at a second brightness level; detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode; while the electronic device is in the second mode, displaying on the display, a second user interface including: a second time indicator indicating the current time, wherein the second time indicator is displayed at a third brightness level that is lower than the first brightness level, at which the first time indicator was previously displayed, by a first amount; and a second graphical object corresponding to the first graphical object, wherein the second graphical object is displayed at a fourth brightness level that is lower than the second brightness level, at which the first graphical object was previously displayed, by a second amount that is different from the first amount of difference in brightness between the first brightness level and the second brightness level.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: while the electronic device is in a first mode, displaying on the display, a first user interface including: a first time indicator, displayed at a first brightness level; and a first graphical object, displayed at a second brightness level; detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode; while the electronic device is in the second mode, displaying on the display, a second user interface including: a second time indicator indicating the current time, wherein the second time indicator is displayed at a third brightness level that is lower than the first brightness level, at which the first time indicator was previously displayed, by a first amount; and a second graphical object corresponding to the first graphical object, wherein the second graphical object is displayed at a fourth brightness level that is lower than the second brightness level, at which the first graphical object was previously displayed, by a second amount that is different from the first amount of difference in brightness between the first brightness level and the second brightness level.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stories one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: while the electronic device is in a first mode, displaying on the display, a first user interface including: a first time indicator, displayed at a first brightness level; and a first graphical object, displayed at a second brightness level; detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode; while the electronic device is in the second mode, displaying on the display, a second user interface including: a second time indicator indicating the current time, wherein the second time indicator is displayed at a third brightness level that is lower than the first brightness level, at which the first time indicator was previously displayed, by a first amount; and a second graphical object corresponding to the first graphical object, wherein the second graphical object is displayed at a fourth brightness level that is lower than the second brightness level, at which the first graphical object was previously displayed, by a second amount that is different from the first amount of difference in brightness between the first brightness level and the second brightness level.
In accordance with some embodiments, an electronic device is described. The electronic device comprising a display; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while the electronic device is in a first mode, displaying on the display, a first user interface including: a first time indicator, displayed at a first brightness level; and a first graphical object, displayed at a second brightness level; detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode; while the electronic device is in the second mode, displaying on the display, a second user interface including: a second time indicator indicating the current time, wherein the second time indicator is displayed at a third brightness level that is lower than the first brightness level, at which the first time indicator was previously displayed, by a first amount; and a second graphical object corresponding to the first graphical object, wherein the second graphical object is displayed at a fourth brightness level that is lower than the second brightness level, at which the first graphical object was previously displayed, by a second amount that is different from the first amount of difference in brightness between the first brightness level and the second brightness level.
In accordance with some embodiments, an electronic device is described. The electronic device comprising, comprising: a display; means, while the electronic device is in a first mode, for displaying on the display, a first user interface including: a first time indicator, displayed at a first brightness level; and a first graphical object, displayed at a second brightness level; means for detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and means, responsive to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, for transitioning the electronic device from the first mode to the second mode; means, while the electronic device is in the second mode, for displaying on the display, a second user interface including: a second time indicator indicating the current time, wherein the second time indicator is displayed at a third brightness level that is lower than the first brightness level, at which the first time indicator was previously displayed, by a first amount; and a second graphical object corresponding to the first graphical object, wherein the second graphical object is displayed at a fourth brightness level that is lower than the second brightness level, at which the first graphical object was previously displayed, by a second amount that is different from the first amount of difference in brightness between the first brightness level and the second brightness level.
In accordance with some embodiments, a method is described. The method comprises: at an electronic device having a display: while the electronic device is in a first mode, displaying on the display, a first user interface including: a first time indicator indicating a current time and is displayed at a first size; and a first graphical object and is displayed at a second size; and detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode; while the electronic device is in the second mode, displaying on the display, a second user interface including: a second time indicator indicating the current time, wherein the second time indicator is displayed at a third size that is smaller than the first size, at which the first time indicator was previously displayed; and a second graphical object corresponding to the first graphical object, wherein the second graphical object is displayed at a fourth size that is smaller than the second size, at which the first graphical object was previously displayed.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: while the electronic device is in a first mode, displaying on the display, a first user interface including: a first time indicator indicating a current time and is displayed at a first size; and a first graphical object and is displayed at a second size; and detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode, including: while the electronic device is in the second mode, displaying on the display, a second user interface including: a second time indicator indicating the current time, wherein the second time indicator is displayed at a third size that is smaller than the first size, at which the first time indicator was previously displayed; and a second graphical object corresponding to the first graphical object, wherein the second graphical object is displayed at a fourth size that is smaller than the second size, at which the first graphical object was previously displayed.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: while the electronic device is in a first mode, displaying on the display, a first user interface including: a first time indicator indicating a current time and is displayed at a first size; and a first graphical object and is displayed at a second size; and detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode, including: while the electronic device is in the second mode, displaying on the display, a second user interface including: a second time indicator indicating the current time, wherein the second time indicator is displayed at a third size that is smaller than the first size, at which the first time indicator was previously displayed; and a second graphical object corresponding to the first graphical object, wherein the second graphical object is displayed at a fourth size that is smaller than the second size, at which the first graphical object was previously displayed.
In accordance with some embodiments, an electronic device is described. The electronic device comprising: a display; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while the electronic device is in a first mode, displaying on the display, a first user interface including: a first time indicator indicating a current time and is displayed at a first size; and a first graphical object and is displayed at a second size; and detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode, including: while the electronic device is in the second mode, displaying on the display, a second user interface including: a second time indicator indicating the current time, wherein the second time indicator is displayed at a third size that is smaller than the first size, at which the first time indicator was previously displayed; and a second graphical object corresponding to the first graphical object, wherein the second graphical object is displayed at a fourth size that is smaller than the second size, at which the first graphical object was previously displayed.
In accordance with some embodiments, an electronic device is described. The electronic device comprising: a display; means, while the electronic device is in a first mode, for displaying on the display, a first user interface including: a first time indicator indicating a current time and is displayed at a first size; and a first graphical object and is displayed at a second size; and means for detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and means, responsive to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, for transitioning the electronic device from the first mode to the second mode, including: means, while the electronic device is in the second mode, for displaying on the display, a second user interface including: a second time indicator indicating the current time, wherein the second time indicator is displayed at a third size that is smaller than the first size, at which the first time indicator was previously displayed; and a second graphical object corresponding to the first graphical object, wherein the second graphical object is displayed at a fourth size that is smaller than the second size, at which the first graphical object was previously displayed.
In accordance with some embodiments, a method is described. The method comprises: at an electronic device having a display and one or more sensors: while the electronic device is in a first mode, displaying on the display, a first user interface at a first display brightness level, the first user interface including: a first time indicator; and a first graphical object; receiving data from the one or more sensors; detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode; and while the electronic device is in the second mode: in accordance with a determination that the data from the one or more sensors corresponds to a first environmental brightness level, displaying a second user interface at a second display brightness level less than the first display brightness level, the second user interface including: a second time indicator different from the first time indicator in one or more visual characteristics other than brightness; and a second graphical object that corresponds to the first graphical object; in accordance with a determination that the data from the one or more sensors corresponds to a second environmental brightness level lower than the first environmental brightness level, displaying a third user interface user interface at a third display brightness level lower than the second display brightness level, the third user interface including different content than the second user interface.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display and one or more sensors, the one or more programs including instructions for: while the electronic device is in a first mode, displaying on the display, a first user interface at a first display brightness level, the first user interface including: a first time indicator; and a first graphical object; receiving data from the one or more sensors; detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode; and while the electronic device is in the second mode: in accordance with a determination that the data from the one or more sensors corresponds to a first environmental brightness level, displaying a second user interface at a second display brightness level less than the first display brightness level, the second user interface including: a second time indicator different from the first time indicator in one or more visual characteristics other than brightness; and a second graphical object that corresponds to the first graphical object; in accordance with a determination that the data from the one or more sensors corresponds to a second environmental brightness level lower than the first environmental brightness level, displaying a third user interface user interface at a third display brightness level lower than the second display brightness level, the third user interface including different content than the second user interface.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display and one or more sensors, the one or more programs including instructions for: while the electronic device is in a first mode, displaying on the display, a first user interface at a first display brightness level, the first user interface including: a first time indicator; and a first graphical object; receiving data from the one or more sensors; detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode; and while the electronic device is in the second mode: in accordance with a determination that the data from the one or more sensors corresponds to a first environmental brightness level, displaying a second user interface at a second display brightness level less than the first display brightness level, the second user interface including: a second time indicator different from the first time indicator in one or more visual characteristics other than brightness; and a second graphical object that corresponds to the first graphical object; in accordance with a determination that the data from the one or more sensors corresponds to a second environmental brightness level lower than the first environmental brightness level, displaying a third user interface user interface at a third display brightness level lower than the second display brightness level, the third user interface including different content than the second user interface.
In accordance with some embodiments, an electronic device is described. The electronic device, comprising: a display; one or more sensors; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while the electronic device is in a first mode, displaying on the display, a first user interface at a first display brightness level, the first user interface including: a first time indicator; and a first graphical object; receiving data from the one or more sensors; detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode; and while the electronic device is in the second mode: in accordance with a determination that the data from the one or more sensors corresponds to a first environmental brightness level, displaying a second user interface at a second display brightness level less than the first display brightness level, the second user interface including: a second time indicator different from the first time indicator in one or more visual characteristics other than brightness; and a second graphical object that corresponds to the first graphical object; in accordance with a determination that the data from the one or more sensors corresponds to a second environmental brightness level lower than the first environmental brightness level, displaying a third user interface user interface at a third display brightness level lower than the second display brightness level, the third user interface including different content than the second user interface.
In accordance with some embodiments, an electronic device is described. The electronic device, comprising: a display; one or more sensors; means, while the electronic device is in a first mode, for displaying on the display, a first user interface at a first display brightness level, the first user interface including: a first time indicator; and a first graphical object; means for receiving data from the one or more sensors; means for detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and means, responsive to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, for transitioning the electronic device from the first mode to the second mode; and means, while the electronic device is in the second mode, for: in accordance with a determination that the data from the one or more sensors corresponds to a first environmental brightness level, displaying a second user interface at a second display brightness level less than the first display brightness level, the second user interface including: a second time indicator different from the first time indicator in one or more visual characteristics other than brightness; and a second graphical object that corresponds to the first graphical object; in accordance with a determination that the data from the one or more sensors corresponds to a second environmental brightness level lower than the first environmental brightness level, displaying a third user interface user interface at a third display brightness level lower than the second display brightness level, the third user interface including different content than the second user interface.
In accordance with some embodiments, a method is described. The method comprises: at an electronic device having a display: displaying a user interface that includes a plurality of user interface elements including a graphical representation of a first type of information that is associated with a first application; while the electronic device is in a first mode: updating the appearance of the graphical representation of the first type of information over time with a first update interval; and after updating the appearance of the graphical representation of the first type of information over time one or more times at the first update interval, detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode; and while the electronic device is in the second mode, updating the appearance of the graphical representation of the first type of information over time with a second update interval that is different from the first update interval.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: displaying a user interface that includes a plurality of user interface elements including a graphical representation of a first type of information that is associated with a first application; while the electronic device is in a first mode: updating the appearance of the graphical representation of the first type of information over time with a first update interval; and after updating the appearance of the graphical representation of the first type of information over time one or more times at the first update interval, detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode; and while the electronic device is in the second mode, updating the appearance of the graphical representation of the first type of information over time with a second update interval that is different from the first update interval.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: displaying a user interface that includes a plurality of user interface elements including a graphical representation of a first type of information that is associated with a first application; while the electronic device is in a first mode: updating the appearance of the graphical representation of the first type of information over time with a first update interval; and after updating the appearance of the graphical representation of the first type of information over time one or more times at the first update interval, detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode; and while the electronic device is in the second mode, updating the appearance of the graphical representation of the first type of information over time with a second update interval that is different from the first update interval.
In accordance with some embodiments, an electronic device is described. The electronic device comprising: a display; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying a user interface that includes a plurality of user interface elements including a graphical representation of a first type of information that is associated with a first application; while the electronic device is in a first mode: updating the appearance of the graphical representation of the first type of information over time with a first update interval; and after updating the appearance of the graphical representation of the first type of information over time one or more times at the first update interval, detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning the electronic device from the first mode to the second mode; and while the electronic device is in the second mode, updating the appearance of the graphical representation of the first type of information over time with a second update interval that is different from the first update interval.
In accordance with some embodiments, an electronic device is described. The electronic device comprising: a display; means for displaying a user interface that includes a plurality of user interface elements including a graphical representation of a first type of information that is associated with a first application; means, while the electronic device is in a first mode, for: updating the appearance of the graphical representation of the first type of information over time with a first update interval; and after updating the appearance of the graphical representation of the first type of information over time one or more times at the first update interval, detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; means, responsive to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, for transitioning the electronic device from the first mode to the second mode; and means, while the electronic device is in the second mode, for updating the appearance of the graphical representation of the first type of information over time with a second update interval that is different from the first update interval.
In accordance with some embodiments, a method is described. The method comprises: at an electronic device having a display: while the electronic device is operating in a first mode, displaying, on the display, a first user interface of a first application, the first user interface including a first graphical object corresponding to the first application; while displaying the first user interface, detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode: in accordance with a determination that the first application is an application of a first type, replacing display of the first user interface of the first application with a second user interface of the first application different from the first user interface, the second user interface including a second graphical object corresponding to the first application; in accordance with a determination that the first application is an application of a second type, replacing display of the first user interface of the first application with a third user interface different from the first user interface of the first application and the second user interface of the first application, the third user interface that is an operating system user interface including one or more elements that are not part of the first user interface of the first application, including a time indicator.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: while the electronic device is operating in a first mode, displaying, on the display, a first user interface of a first application, the first user interface including a first graphical object corresponding to the first application; while displaying the first user interface, detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode: in accordance with a determination that the first application is an application of a first type, replacing display of the first user interface of the first application with a second user interface of the first application different from the first user interface, the second user interface including a second graphical object corresponding to the first application; in accordance with a determination that the first application is an application of a second type, replacing display of the first user interface of the first application with a third user interface different from the first user interface of the first application and the second user interface of the first application, the third user interface that is an operating system user interface including one or more elements that are not part of the first user interface of the first application, including a time indicator.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: while the electronic device is operating in a first mode, displaying, on the display, a first user interface of a first application, the first user interface including a first graphical object corresponding to the first application; while displaying the first user interface, detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode: in accordance with a determination that the first application is an application of a first type, replacing display of the first user interface of the first application with a second user interface of the first application different from the first user interface, the second user interface including a second graphical object corresponding to the first application; in accordance with a determination that the first application is an application of a second type, replacing display of the first user interface of the first application with a third user interface different from the first user interface of the first application and the second user interface of the first application, the third user interface that is an operating system user interface including one or more elements that are not part of the first user interface of the first application, including a time indicator.
In accordance with some embodiments, an electronic device, comprising: a display; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while the electronic device is operating in a first mode, displaying, on the display, a first user interface of a first application, the first user interface including a first graphical object corresponding to the first application; while displaying the first user interface, detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode: in accordance with a determination that the first application is an application of a first type, replacing display of the first user interface of the first application with a second user interface of the first application different from the first user interface, the second user interface including a second graphical object corresponding to the first application; in accordance with a determination that the first application is an application of a second type, replacing display of the first user interface of the first application with a third user interface different from the first user interface of the first application and the second user interface of the first application, the third user interface that is an operating system user interface including one or more elements that are not part of the first user interface of the first application, including a time indicator.
In accordance with some embodiments, an electronic device, comprising: a display; means, while the electronic device is operating in a first mode, for displaying, on the display, a first user interface of a first application, the first user interface including a first graphical object corresponding to the first application; means, while displaying the first user interface, for detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and means, responsive to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, for: in accordance with a determination that the first application is an application of a first type, replacing display of the first user interface of the first application with a second user interface of the first application different from the first user interface, the second user interface including a second graphical object corresponding to the first application; in accordance with a determination that the first application is an application of a second type, replacing display of the first user interface of the first application with a third user interface different from the first user interface of the first application and the second user interface of the first application, the third user interface that is an operating system user interface including one or more elements that are not part of the first user interface of the first application, including a time indicator.
In accordance with some embodiments, a method is described. The method comprises: at an electronic device having a display: while the electronic device is operating in a first mode: displaying, on the display, a first user interface of a first application with an arrangement of user interface elements determined by the first application; and displaying, on the display, a second user interface of a second application with an arrangement of user interface elements determined by the second application; while the electronic device is operating in the first mode, detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning from the first mode to the second mode, including: in accordance with a determination that the first application was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode, displaying information from the first application in a predefined template; and in accordance with a determination that the second application was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode, displaying information from the second application in the predefined template.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: while the electronic device is operating in a first mode: displaying, on the display, a first user interface of a first application with an arrangement of user interface elements determined by the first application; and displaying, on the display, a second user interface of a second application with an arrangement of user interface elements determined by the second application; while the electronic device is operating in the first mode, detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning from the first mode to the second mode, including: in accordance with a determination that the first application was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode displaying information from the first application in a predefined template; and in accordance with a determination that the second application was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode, displaying information from the second application in the predefined template.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: while the electronic device is operating in a first mode: displaying, on the display, a first user interface of a first application with an arrangement of user interface elements determined by the first application; and displaying, on the display, a second user interface of a second application with an arrangement of user interface elements determined by the second application; while the electronic device is operating in the first mode, detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning from the first mode to the second mode, including: in accordance with a determination that the first application was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode displaying information from the first application in a predefined template; and in accordance with a determination that the second application was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode, displaying information from the second application in the predefined template.
In accordance with some embodiments, an electronic device is described. The electronic device comprising: a display; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while the electronic device is operating in a first mode: displaying, on the display, a first user interface of a first application with an arrangement of user interface elements determined by the first application; and displaying, on the display, a second user interface of a second application with an arrangement of user interface elements determined by the second application; while the electronic device is operating in the first mode, detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, transitioning from the first mode to the second mode, including: in accordance with a determination that the first application was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode displaying information from the first application in a predefined template; and in accordance with a determination that the second application was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode, displaying information from the second application in the predefined template.
In accordance with some embodiments, an electronic device is described. The electronic device comprising: a display; means, while the electronic device is operating in a first mode, for: displaying, on the display, a first user interface of a first application with an arrangement of user interface elements determined by the first application; and displaying, on the display, a second user interface of a second application with an arrangement of user interface elements determined by the second application; means, while the electronic device is operating in the first mode, for detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and means, responsive to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, for transitioning from the first mode to the second mode, including: in accordance with a determination that the first application was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode displaying information from the first application in a predefined template; and in accordance with a determination that the second application was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode, displaying information from the second application in the predefined template.
In accordance with some embodiments, a method is described. The method comprises: at an electronic device having a display: while the electronic device is operating in a first mode, displaying, on the display, a first user interface of an application; detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode: transitioning from the first mode to the second mode; replacing, on the display, the first user interface with a second user interface including an obscured representation of at least a portion of the first user interface of the application; and displaying a time indicator at a position on the display overlapping at least a portion of the obscured representation of the at least a portion of the first user interface of the application.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: while the electronic device is operating in a first mode, displaying, on the display, a first user interface of an application; detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode: transitioning from the first mode to the second mode; replacing, on the display, the first user interface with a second user interface including an obscured representation of at least a portion of the first user interface of the application; and displaying a time indicator at a position on the display overlapping at least a portion of the obscured representation of the at least a portion of the first user interface of the application.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: while the electronic device is operating in a first mode, displaying, on the display, a first user interface of an application; detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode: transitioning from the first mode to the second mode; replacing, on the display, the first user interface with a second user interface including an obscured representation of at least a portion of the first user interface of the application; and displaying a time indicator at a position on the display overlapping at least a portion of the obscured representation of the at least a portion of the first user interface of the application.
In accordance with some embodiments, an electronic device is described. The electronic device comprising a display; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while the electronic device is operating in a first mode, displaying, on the display, a first user interface of an application; detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode: transitioning from the first mode to the second mode; replacing, on the display, the first user interface with a second user interface including an obscured representation of at least a portion of the first user interface of the application; and displaying a time indicator at a position on the display overlapping at least a portion of the obscured representation of the at least a portion of the first user interface of the application.
In accordance with some embodiments, an electronic device is described. The electronic device comprising a display; means, while the electronic device is operating in a first mode, for displaying, on the display, a first user interface of an application; means for detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; and means, responsive to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, for: transitioning from the first mode to the second mode; replacing, on the display, the first user interface with a second user interface including an obscured representation of at least a portion of the first user interface of the application; and displaying a time indicator at a position on the display overlapping at least a portion of the obscured representation of the at least a portion of the first user interface of the application.
Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.
Thus, devices are provided with faster, more efficient methods and interfaces for managing display usage, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for managing display usage
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
There is a need for electronic devices that provide efficient methods and interfaces for managing display usage. For example, prolonged display of user interfaces that include non-moving graphical object (e.g., static images) overtime causes screen burn-in or image ghosting. This is particularly true for portable multifunction devices with reduced-size displays, since elements of a displayed user interface are often displayed repetitively at fixed positions on a display. Techniques that thoughtfully manage what is include on a user interface, how it is displayed, and when it is displayed minimize screen burn-in and image ghosting. Such techniques can reduce the cognitive burden on a user who accesses user interfaces, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs and excessive display brightness, and improve the wear characteristics of display devices used to display user interfaces.
Below,
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.
A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more depth camera sensors 175.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the 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).
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 700, 900, 1100, 1300, 1500, 1700, 1900 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).
In some embodiments, the display of representations 578A-578C includes an animation. For example, representation 578A is initially displayed in proximity of application icon 572B, as shown in
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and/or 500) and is ready to be launched (e.g., become opened) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system.
As used herein, the terms “open application” or “executing application” refer to a software application with retained state information (e.g., as part of device/global internal state 157 and/or application internal state 192). An open or executing application is, optionally, any one of the following types of applications:
As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, device 500, or device 600.
Upon determining that a mode-transition criteria has been met, the device transitions from a first mode to a second mode (e.g., a low power mode). In some embodiments, while operating in the second mode, device 600 conserves energy by operating one or more processors of the device at a reduced load, such as by waking (e.g., enabling or turning on) one or more processors of the device at increased intervals (e.g., a reduce rate; less often) compared to operation in the first mode. In some embodiments, a processor includes hardware (e.g., a microprocessor or the like). In some embodiments, a processor includes one or more software components (e.g., software modules for performing various functions; a module for displaying information from applications on a display device; a module for processing sensor data received by the device, a module for performing calculations necessary to perform or implement various features of the device, etc.).
Among the visual characteristics described below that may be altered upon transitioning device modes is the overall brightness of a displayed user interface (e.g., average pixel luminance (APL), average lumen output, total lumen output, average illuminance, or total illuminance of the pixels comprising the user interface on the display; brightness expressed in nits, lux, or lumens). To illustrate this,
Throughout this disclosure, the concept of brightness levels are also discussed with respect to individual graphical elements or groups of graphical elements included in various clock face user interfaces (e.g., affordances, graphical elements included within affordances, complications, clock face elements, backgrounds, indicators, etc.) displayed by device 600 on display 602. Similar to the brightness level of a clock face user interface, the brightness level of a graphical element as displayed within a clock face user interface on display 602 may also by varied (e.g., using the techniques described below). Please note, however, that as depicted throughout the figures described below, brightness scale 630 reflects an overall brightness level of a respective clock face user interface (e.g., the entire clock face user interface being displayed, not the brightness level of individual graphical elements or groups of graphical elements within the respective clock face user interface), unless otherwise noted. Furthermore, brightness scale 630 is not part of any user interface displayed on device 600.
In addition to brightness scale 630, the relative displayed brightness of a clock face user interface and elements constituting the clock face user interfaces described below (e.g., graphical objects displayed in or on the user interface, backgrounds, etc.) are also represented by the depicted shading intensities in each figure (e.g., white or lighter greys indicating more brightly displayed elements; darker greys indicating less brightly displayed elements).
In some embodiments, brightness levels can be adjusted (increased or decreased) using alpha blending. In some embodiments, decreasing a brightness level includes using alpha blending without altering a backlight of the electronic device to create a simulated or real backlight level. For instance, the device can alpha blend image data representing a clock face user interface (or a portion of a clock face user interface such as an affordance or complication) with an increasingly opaque black masking layer to increasingly dim the clock face user interface as displayed on the screen (e.g., so that the user interface fades to black).
In some embodiments, a brightness level of a graphical object in a clock face user interface is changed by altering the shape or composition of the graphical object itself. For example, the brightness of a white clock hand by may decreased by reducing the thickness of the clock hand (e.g., removing white pixels from the element). In some embodiments, a brightness level of a graphical object is altered (e.g., reduced or dimmed) by replacing solid-colored regions of the object with a similarly colored outlines of the solid-colored regions. In some embodiments, a brightness level of a graphical object is reduced or dimmed by altering its colors, for example, by replacing lighter colors (e.g., white, light greys, yellows, etc.) with darker colors (black, dark greys, blues, etc.). Any combination of the brightness altering techniques described above or similar techniques well-known in the art, may be used for adjusting brightness levels of graphical objects and clock face user interfaces in accordance with the embodiments described below.
Turning now to
At
As illustrated in
Date affordance 614 indicates a current date and a description of an upcoming calendar event (e.g., “8:00 AM YOGA GYM”). World clock affordance 616 indicates a geographic location (e.g., “MAD” for Madrid, Spain), a time associated with the geographic location (e.g., an analog clock dial with hour and minute hands), and an indication of day, night, sunset, or sunrise (e.g., indicating that it is day-time in Madrid based on the light-colored shade of the background (e.g., darker shades indicated later in the day)). In some embodiments, world clock affordance 616 includes an offset to a local time. In some embodiments, the position of the location indicator moves to avoid overlapping or interfering with the clock hands as they progress around the world clock dial.
Compass affordance 618 includes graphical (e.g., a compass needle graphic), textual (e.g., “NW”), and numerical (“330” degrees) indicators of a cardinal or intercardinal direction which update as the orientation of device 600 (or the orientation a second device coupled to device 600) changes.
Timer affordance 620 includes a numerical indicator (e.g., “14:59”) and radial markings, each indicating a remaining time associated with a timer application. The radial markings are sequentially altered (e.g., visually de-emphasized in size and/or color) such that the ratio of altered to unaltered radial markings is proportional to the time remaining on a decrementing counter associated with the timer application.
Heart rate affordance 622, moon affordance 624, stopwatch affordance 626, and workout affordance 628 are displayed at the corners of clock face user interface 608-1. As depicted in
At
As depicted in
Clock face user interface 608-3 includes less content than clock face user interface 608-1. As depicted in
In addition to including less or reduced content, corresponding elements in clock face user interface 608-3 are displayed by device 600 differently than they were previously displayed in clock face user interface 608-1. In
Device 600 displays each affordance in clock face user interface 608-3 at reduced brightness levels (e.g., low power display mode brightness levels) compared to their respectively displayed brightness levels in
As depicted in
As depicted in
At
At
At
At
The sequence of
In some embodiments, the transition from low power display mode to standard display mode described above with respect to
At
At
At
At
At
At
At
At
At
At
At
At
At
Clock face user interface 608-21 includes a representation 664 indicating a position of the Sun (e.g., relative to a location on Earth (e.g., corresponding to the current location of device 600)) at the displayed time. The position of representation 664 with respect to analog dial 660 indicates the same time indicated by inset time indication 1604 (e.g., the current time). As time progresses, representation 664 moves around a circular path 666 that has a common origin with the circular path around which inset time indication 662 moves. As illustrated in
At
As described below, method 700 provides an intuitive way for managing display usage. The method reduces power usage and the likelihood of screen burn-in. The method also reduces the cognitive burden on a user for managing display usage, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a device to automatically manage display usage faster and more efficiently conserves power and increases the time between battery charges.
In general, different brightness levels can be achieved using various techniques, which can be employed separately or concurrently. In some embodiments, the brightness level of a graphical element is changed by changing (e.g., brightening, dimming) the brightness of some (or all) pixels of the graphical element. In some embodiments, the brightness level of the graphical element is changed by modifying the graphical element so that fewer (or more) pixels are lit up, such as by thinning (or thickening) lines of the graphical element, and removing (or adding) a background of the graphical element, reducing (or enlarging) a size of the graphical element.
While the electronic device (e.g., 600) is in a first mode (e.g., a higher power consumption mode), the electronic device (e.g., 600) displays (702) on the display, a first user interface (e.g., a clock face of a smart watch; 608-1) including a first time indicator (704) and a first graphical object (706). The first time indicator (704) (e.g., hands of 610 at
The electronic device, (e.g., 600) detects (708) that the electronic device has met criteria for transitioning from the first mode to a second mode (e.g., one or more criteria that are indicative of reduced user activity or reduced user interaction with the electronic device (e.g., determining reduced user activity (physical movement) for a predetermined period of time, determining a lack of user input for a predetermined period of time, detecting a predefined gesture). In some embodiments, detecting that the electronic device has met the criteria includes one or more of: receiving data from one or more sensors (e.g., accelerometer, gyroscope, proximity sensor) corresponding to a user gesture (e.g., wrist-down, wrist-up, palm over display), receiving data from one or more sensors indicating user activity below a threshold activity level, determining a predetermined period of time has elapse without device receiving user input at one or more input devices (e.g., touch-screen, rotatable input mechanism, depressible input mechanism).
In response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, the electronic device (e.g., 600) transitions (710) the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode). The first mode and the second mode are different modes in which the electronic device can operate. In some embodiments, the overall brightness of the display in the first mode is more than the overall brightness of the display in the second mode when displaying a corresponding user interface. In some embodiments, a rate of display refresh is higher in the first mode as compared to the second mode. In some embodiments, one or more processor of the electronic device are awake for a higher percentage of time when the device is in the first mode as compared to when the device is in the second mode. In some embodiments, the one or more processors of the electronic device wake up more frequently over a duration of time when the device is in the first mode as compared to when the device is in the second mode. In some embodiments, more portions of the one or more processors of the electronic device are running when the device is in the first mode as compared to when the device is in the second mode. In some embodiments, the electronic device employs processor power management techniques (e.g., slowing down or turning off a core clock, slowing down or turning off a bus clock, reducing the main CPU voltage (VCC) in the second mode that are not employed in the first mode.
While the electronic device (e.g., 600) is in the second mode, the electronic device (e.g., 600) displays (712) on the display (e.g., 602), a second user interface (e.g., 608-3) including: a second time indicator (714) and a second graphical object (716).
The second time indicator (714) indicates the current time (hands of 610 at
The second graphical object (716) corresponds to the first graphical object (e.g., center of 610 at
Displaying the time indicator at a reduced brightness reduces power usage and improves the battery life of the device. Displaying the graphical object at a reduced brightness reduces power usage and improves the battery life of the device. Reducing the brightness of the indicator and the graphical object by different amounts enables the device to conserve more power by significantly reducing the brightness of the less relevant visual element (e.g., the graphical object) while still displaying the other visual element (e.g., the time indicator) at a brightness that leaves the element more perceptible.
In some embodiments, a first display brightness of the display (e.g., 602 at
In some embodiments, the second display brightness (e.g., 602 at
In some embodiments, the second display brightness (e.g., 602 at
In some embodiments, the first graphical object is a stationary graphical element (e.g., center of 610 at
In some embodiments, the first graphical object is a complication (e.g., 614, 616, 618, and 620 at
A complication refers to any clock face feature other than those used to indicate the hours, minutes, or seconds of a current time associated with the device. In some embodiments, complications provide data obtained from an application. In some embodiments, a complication includes an affordance that when selected launches a corresponding application. In some embodiments, a complication is displayed at a fixed, predefined location on the display while the device is in a particular power consumption mode. In some embodiments, in response to detecting a sequence of one or more inputs, the device may change or edit an aspect of a complication. For example, this could be used to change application data displayed by an application complication. In some embodiments, the complication may indicate a first set of information obtained by an application (e.g., application data. For example, if the application is a weather application, a set of information could be a forecasted weather condition, a current temperature, etc.), and upon editing, the complication could be updated to indicate a second set of information from the same application (e.g., if the application is a weather application, the display could be edited from showing a current temperature to showing current precipitation). In some embodiments, in response to detecting a sequence of one or more inputs, the device may change or edit a complication to indicate a set of information from a different application (e.g., if the application is a weather application, the display could be edited from showing weather to showing data from a calendar application).
In some embodiments, a first dimming ratio between first brightness level and the third brightness level is different from a second dimming ratio between the second brightness level and the fourth brightness level (e.g., difference between 610 and 616 in
In some embodiments, the first user interface (e.g., a clock face of a smart watch; 608-1) displayed while the electronic device is in the first mode includes a third graphical object (e.g., 616 at
In some embodiments, while displaying the first user interface (e.g., 608-1, 1008-4) while the electronic device is in the first mode, the electronic device (e.g., 600) detects (e.g., using one or more light sensors) a change (e.g., reduction) in environmental brightness level (e.g., change in ambient light, without detecting that the electronic device has met criteria for transitioning from the first mode to the second mode). In some embodiments, while displaying the first user interface (e.g., 608-1, 1008-4) while the electronic device is in the first mode, in response to detecting the change (e.g., reduction) in environmental brightness level (e.g., ambient light) (e.g., without detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode), changing (e.g., reducing) the brightness at which the first user interface is displayed on the display without transitioning the electronic device to the second mode (e.g., 1008-4, 1008-5). In some embodiments, the electronic device determines that the amount of ambient light has been reduced and makes a corresponding change in the brightness at which the first user interface is displayed. In some embodiments, changing (e.g., reducing) the brightness at which the first user interface is displayed does not change the displayed content the first user interface other than brightness (e.g., does not change a size of visual elements, does not change the information displayed). In some embodiments, the amount of dimming increases as the environmental brightness increases and the amount of dimming decreases as the environmental brightness decreases (e.g., based on a magnitude of change in the environmental brightness level). In some embodiments, the amount of dimming decreases as the environmental brightness increases and the amount of dimming increases as the environmental brightness decreases (e.g., based on a magnitude of change in the environmental brightness level). Changing the brightness of the display based on environmental brightness allows the contents of the display to be more easily visible in bright ambient light environments, thereby providing the user with improved visual feedback, while reducing battery usage in reduced ambient light environments. 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). Reducing the display brightness reduces power usage and improves the battery life of the device.
In some embodiments, transitioning the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode) includes removing (e.g., ceasing to display) at least some content (e.g., 622) from the display. In some embodiments, one or more visual elements that were displayed in the first mode cease to be displayed as a result of transitioning to the second mode. Removing content from the displays enables the device to conserve battery power by avoiding energizing the pixels that the content previously used (e.g., turning off the pixels). Avoiding energizing pixels of the display reduces the display brightness. Reducing the display brightness reduces power usage and improves the battery life of the device.
In some embodiments, transitioning the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode) includes removing (e.g., ceasing to display) one or more complications (e.g., 622) from the display. In some embodiments, one or more complications that were displayed in the first mode cease to be displayed as a result of transitioning to the second mode.
In some embodiments, transitioning the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode) includes removing (e.g., ceasing to display) a first set of content of one or more complications from the display (e.g., event description of 614, directional data of 618, and seconds data of 620 at
In some embodiments, transitioning the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode) includes removing (e.g., ceasing to display) at least a portion of a background (e.g., solid background color, a background image; 658) from the display. In some embodiments, one or more backgrounds that were displayed in the first mode cease to be displayed as a result of transitioning to the second mode.
In some embodiments, the background has a first visual characteristic (e.g., a first color) and wherein transitioning the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode) includes displaying, at a location corresponding to the removed portion of background (e.g., 658), a third graphical object (e.g., 659) (e.g., an outline having the same shape as a the background; an unfilled geometric shape) having the first visual characteristic.
In some embodiments, transitioning the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode) includes reducing a precision (e.g., a degree of accuracy or exactness of a value (e.g., a time value, a measurement value)) of displayed information (e.g., of the time indicator; 610 at
In some embodiments, reducing a precision of displayed information includes reducing a precision of a time-based visual element by ceasing to display seconds information (e.g., a seconds counter, a seconds hand; 610 at
In some embodiments, transitioning the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode) includes removing (e.g., ceasing to display) a respective type of information (e.g., potentially sensitive information such as calendar information, physical activity information; information deemed to be personal information (e.g., information that is particular to a user of the electronic device)) from the display while continuing to display information that is not of the respective type of information (e.g., time information, weather information; information is non-personal; information that is the same for different users; event description of 614 at
In some embodiments, subsequent to (e.g., in response to) detecting that the electronic device has met criteria for transitioning from the first mode to a second mode and in accordance with a determination that an information suppression setting is enabled (e.g., 640), the electronic device (e.g., 600) removes (e.g., ceasing to display) information of a respective type of information (e.g., potentially sensitive information such as calendar information, physical activity information; information deemed to be personal information (e.g., information that is particular to a user of the electronic device)) while continuing to display information that is not of the respective type of information (e.g., time information, weather information; 614 at
In some embodiments, transitioning the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode) includes reducing the display size of one or more visual elements (614, 616, 618, 620, 624, 626, and 628 of
In some embodiments, prior to displaying the first user interface (e.g., a clock face of a smart watch), the electronic device (e.g., 600) detects a user input, wherein displaying the first user interface is based on (e.g., is in response to) detecting the user input. In some embodiments, the criteria for transitioning from the first mode to the second mode includes a first criterion, wherein: in accordance with a determination that the user input is of a first type (e.g., tap or other touch gesture on a touch-sensitive surface of the electronic device), the first criterion is met based on a first amount of time having elapsed (e.g., the first amount of time having elapsed after detecting the user input, the first amount of time having elapsed after detecting the last user input while in the first mode); and in accordance with a determination that the user input is of a second type (e.g., wrist raise gesture detected by one or more motion sensors), the first criterion is met based on a second amount of time having elapsed (e.g., the second amount of time having elapsed after detecting the user input, the second amount of time having elapsed after detecting the last user input while in the first mode), the second time being different from the first time. In some embodiments, the electronic device stays in the first mode for different amounts of time (e.g., by transitioning to the second mode after varying amounts of time) based on the time of user input that caused the electronic device to enter the first mode. In some examples, the electronic device stays in the first mode for a longer duration when a touch gesture on the electronic device's touch-sensitive surface causes the electronic device to transition to the first mode because the touch gesture is likely to be intentional input and the electronic device stays in the first mode for a shorter duration when a motion-based gesture (e.g., wrist raise) causes the electronic device to transition to the first mode because the motion-based gesture is less likely to be intentional input.
In some embodiments, the first user interface includes display of an animation that includes a first animation portion and a second animation portion (e.g., 648 at
In some embodiments, while in the second mode, the electronic device (e.g., 600) detects (e.g., a beginning of) a second user input (e.g., 632-2, 632-6, 632-7, 632-8) (e.g., a touch gesture input on a touch-sensitive surface of the electronic device, a rotation of a rotatable input mechanism of the electronic device). In response to detecting the second user input, the electronic device (e.g., 600) transitions from the second mode to the first mode, including replacing display of the second user interface with display of the first user interface (e.g.,
In some embodiments, the electronic device includes a rotatable input mechanism (e.g., 604) (e.g., a physical crown that is rotatable relative to a display and/or housing of the electronic device). The second user input is rotation of the rotatable input mechanism (e.g., 632-2). In some embodiments, replacing display of the second user interface (e.g., 608-3, 608-6) with display of the first user interface (e.g., 608-1, 608-8) occurs in conjunction with detecting rotation (e.g., 632-2, 632-6, 632-7, 632-8) of the rotatable input mechanism (e.g., the transition from the second user interface to the first user interface occurs over time where an incremental rotation of the rotatable input mechanism results in a corresponding incremental transition from the second user interface to the first user interface). In some embodiments, rotating the crown cases the visual elements in the second user interface to transition to the corresponding visual elements of the first user interface (e.g., in size, shape, location, brightness).
In some embodiments, the electronic device includes a rotatable input mechanism (e.g., 606) (e.g., a physical crown that is rotatable relative to a display and/or housing of the electronic device). While in the second mode, the electronic device (e.g., 600) detects (e.g., a beginning of) a third user input (e.g., 632-7 and 632-8) (e.g., rotation of a rotatable input mechanism of the electronic device). In response to detecting the second user input, the electronic device (e.g., 600) transitions from the second mode to the first mode and increasing the brightness of the display (e.g., 602 at
In some embodiments, the first time indicator (e.g., 610 at
In some embodiments, the first time indicator includes a first gradient (e.g., 650 at
In some embodiments, the electronic device includes a touch-sensitive surface (e.g., 602). The electronic device (e.g., 600) detects, using the touch-sensitive surface, a tap input (e.g., 632-5, 632-9) at a location corresponding to a displayed complication (e.g., 628) (e.g., that includes weather information, calendar information, or physical activity information) associated with an application (e.g., the complication displays information received from the application). In response to detecting the tap input: in accordance with a determination that the electronic device is in the first mode, the electronic device (e.g., 600) replaces display of the first indication of time with display of the application (e.g., 608-9) (e.g., without changing modes); and in accordance with a determination that the electronic device is in the second mode, the electronic device (e.g., 600) transitions from the second mode to the first mode without replacing display of the second indication of time with display of the application (e.g.,
In some embodiments, the electronic device (e.g., 600) detects (e.g., using a touch-sensitive surface) a swipe gesture input (e.g., 632-1, 632-11). In response to detecting the swipe gesture input: in accordance with a determination that the electronic device is in the first mode, the electronic device (e.g., 600) performs an operation (e.g., displaying 608-11) (e.g., that corresponds to the swipe gesture input); and in accordance with a determination that the electronic device is in the second mode, the electronic device (e.g., 600) maintains the electronic device in the second mode without performing the operation (e.g., displaying 608-4). In some embodiments, in accordance with a determination that the electronic device is in the first mode, the technique maintains the electronic device in the first mode. In some embodiments, the operation includes one or more of: displaying one or more received notifications, changing a clock face of the electronic device, displaying one or more affordances for configuring the electronic device. In some embodiments, the electronic device ignores, disregards, and/or does not act upon swipe gesture inputs when the electronic device is in the second mode. Avoiding performing operations reducing the processing that the device is required to do, thereby reducing the power usage of the device and improving the battery life of the device.
In some embodiments, the electronic device (e.g., 600) detects (e.g., using a touch-sensitive surface) a swipe gesture input (e.g., 632-1). In response to detecting the swipe gesture input: in accordance with a determination that the electronic device is in the first mode, the electronic device (e.g., 600) performs an operation while maintaining the electronic device in the first mode (e.g., that corresponds to the swipe gesture input); and in accordance with a determination that the electronic device is in the second mode, the electronic device (e.g., 600) performs the operation (e.g., displaying 608-11) (and, optionally, transitioning the electronic device to the first mode). In some embodiments, in accordance with a determination that the electronic device is in the first mode, the technique maintains the electronic device in the first mode. In some embodiments, the operation includes one or more of: displaying one or more received notifications, changing a clock face of the electronic device, displaying one or more affordances for configuring the electronic device.
In some embodiments, while the electronic device is in the first mode and displaying the first user interface (e.g., 608-1) (e.g., prior to detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; after detecting that the electronic device has met criteria for transitioning from the first mode to a second mode) and while the electronic device is connected (e.g., via a wire; wireless) to an external power source (e.g., a charger; 636), the electronic device (e.g., 600) detects that the electronic device has met criteria for transitioning from the first mode to a third mode (e.g., description of
In some embodiments, while the electronic device (e.g., 600) is in the first mode and displaying the first user interface (e.g., prior to detecting that the electronic device has met criteria for transitioning from the first mode to a second mode; after detecting that the electronic device has met criteria for transitioning from the first mode to a second mode), the electronic device (e.g., 600) detects a request (e.g., a set of one or more user inputs that enables a fourth mode) to transition the electronic device from the first mode to a fourth mode (e.g., a theater mode; a mode in which the display is inactive and only reactivates (e.g., re-enters the first mode) based on selected user input (e.g., does not activate based on certain inputs that would activate the display (e.g., re-enters the first mode) while in the second mode; a mode that also involves suppressing notifications)). In response to detecting the request to transition the electronic device from the first mode to the fourth mode, the electronic device (e.g., 600) ceases to display the first time indicator and the first graphical object without displaying the second time indicator and second graphical object (e.g., 602 in
Note that details of the processes described above with respect to method 700 (e.g.,
As depicted in
At
In some embodiments, as depicted in
As described below, method 900 provides an intuitive way for managing display usage. The method reduces power usage and the likelihood of screen burn-in. The method also reduces the cognitive burden on a user for managing display usage, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a device to automatically manage display usage faster and more efficiently conserves power and increases the time between battery charges.
While the electronic (e.g., 600) device is in a first mode (e.g., a higher power consumption mode), the electronic device (e.g., 600) displays (902) on the display (e.g., 602), a first user interface (e.g., a clock face of a smart watch) including a first time indicator (904) and a first graphical object (906).
The first time indicator (904) indicates a current time (e.g., 842 at
The electronic device (e.g., 600) detects (908) that the electronic device has met criteria for transitioning from the first mode to a second mode. In response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, electronic device (e.g., 600) transitions (910) the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode).
While the electronic device is in the second mode, electronic device (e.g., 600) displays (912) on the display, a second user interface (e.g., 808-10) including: a second time indicator (914) and a second graphical object (916).
The second time indicator (914) (e.g., 842 at
The second graphical object (916) (e.g., 816, 818, 820, 828, 846, and 844 at
In some embodiments, the first time indicator (e.g., 842 at
In some embodiments, while the electronic device is in the first mode (e.g., a higher power consumption mode), the electronic device (e.g., 600) displays on the display in the first user interface (e.g., a clock face of a smart watch), a third graphical object (e.g., an affordance; a complication; 828 at
In some embodiments, the first graphical object (e.g., 820 at
In some embodiments, the first time indicator (e.g., 842 at
In some embodiments, a combination (e.g., a group) of the first graphical object (e.g., 816, 818, 828 at
In some embodiments, the first time indicator is displayed at a first location on the display as part of the first user interface while in the first mode. In some embodiments, the first graphical object (e.g., 816, 818, 820, 828, 846, and 844 at
In some embodiments, transitioning the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode includes: a first animation (e.g., 808-1 and 808-2) transitioning the first time indicator (e.g., 842 at
In some embodiments, the first graphical object (e.g., 846 at
In some embodiments, the first graphical object (e.g., 820 at
In some embodiments, the first time indicator (e.g., 810 at
In some embodiments, the fourth size is smaller than the second size by a first percentage (e.g., relative size of 846 in
In some embodiments, the first graphical object (e.g., 820 at
In some embodiments, the fourth size is smaller than the second size by a first percentage and the third size is smaller than the first size by a third percentage that is less than the first percentage (e.g., relative size of 810 and 828 at
In some embodiments, while the electronic device is in the second mode and displaying, on the display, the second user interface including the second time indicator at the third size and the second graphical object at the fourth size, the electronic device (e.g., 600) detects that the electronic device has met criteria for transitioning from the second mode to the first mode (e.g., detecting a user input on the display, detecting motion (e.g., motion indicative of a wrist-raise)). In response to detecting that the electronic device has met the criteria for transitioning from the second mode to the first mode, the electronic device (e.g., 600) transitions from the second mode to the first mode, including: animating, over a first amount of time, a transition of the second time indicator (e.g., 842 in
In some embodiments, transitioning from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode) includes: animating, over a third amount of time, a transition of the first time indicator (e.g., 842 at
In some embodiments, transitioning from the second mode (e.g., a lower power consumption mode) to the first mode (e.g., a higher power consumption mode) includes: in accordance with a determination that the user input (e.g., 832-1) is of a first type (e.g., tap or other touch gesture on a touch-sensitive surface of the electronic device), the first amount of time is a first predetermined period of time; and in accordance with a determination that the user input is of a second type (e.g., wrist raise gesture detected by one or more motion sensors) different from the first type, the first amount of time is a second predetermined period of time that is different from the first predetermined period of time. In some embodiments, in accordance with a determination that the user input is of the first type (e.g., tap or other touch gesture on a touch-sensitive surface of the electronic device), the second amount of time is the first predetermined period of time, and in accordance with a determination that the user input is of a second type (e.g., wrist raise gesture detected by one or more motion sensors), the second amount of time is the second predetermined period of time. In some embodiments, the transition from the second mode to the first mode happens at different rates based on the type of input that causes the transition.
In some embodiments, transitioning from the second mode to the first mode includes displaying an animation (e.g., 808-5) that visually accentuates one or more visual differences between the second user interface displayed in the second mode and the first user interface displayed in the first mode.
In some embodiments, visually accentuating one or more visual differences between the second mode and the first mode includes: reducing the display size of the second time indicator (e.g., 842 at
In some embodiments, while the electronic device is in the first mode (e.g., a higher power consumption mode) and displaying the first user interface (e.g., a clock face of a smart watch), the first time indicator (e.g., an analog clock hand (hour, minute, second hand); a digital clock numeral (hour, minute, second numerals)) is displayed at a first brightness level (e.g., average pixel luminance (APL), average lumen output, total lumen output, average illuminance, or total illuminance of the indicator on the display; brightness expressed in nits, lux, or lumens) and the first graphical object (e.g., an affordance; an affordance representing a first application; an interactive graphical object; an affordance displayed as a complication associated with a clock face; a non-updating graphical element (rotation point of a clock hand; colon separating digital clock numerals)) is displayed at a second brightness level (e.g., a brightness level that is the same as the first brightness level; a brightness level that is different than the first brightness level). Thus, the first time indicator is displayed at a first brightness level and the first graphical object is displayed at a second brightness level. In some embodiments, while the electronic device is in the second mode and displaying the second user interface, the second time indicator is displayed at a third brightness level that is lower than the first brightness level, at which the first time indicator was previously displayed and the second graphical object corresponding to the first graphical object (e.g., a non-interactive version of the first graphical object; a visually distinct graphical object representing to the same application as the first graphical object; a graphical object including a subset of the data included in the first graphical object (only mm remaining rather than mm:ss remaining)) is displayed at a fourth brightness level that is lower than the second brightness level, at which the first graphical object was previously displayed.
In some embodiments, visually accentuating one or more visual differences between the second mode and the first mode includes: reducing the brightness level of the second time indicator (e.g., 842 at
In some embodiments, the third size and fourth size are selected based on one or more resizing criteria (e.g., 844 at
In some embodiments, the resizing criteria (e.g., 844 at
In some embodiments, the electronic device (e.g., 600) selects the third size for the second time indicator (e.g., 842 at
In some embodiments, a first display brightness (e.g., Average Pixel Luminance (APL)) of the display (e.g., 602 displaying 808-1) while displaying the second user interface while the electronic device is in the second mode (e.g., a lower power consumption mode) is less than a second display brightness (e.g., APL) of the display (e.g., 602 displaying 808-4) while displaying the first user interface (e.g., a clock face of a smart watch) while the electronic device is in the first mode (e.g., a higher power consumption mode). Thus, the overall brightness of the display is reduced when displaying the second user interface while the electronic device is in the second mode as compared to displaying the first user interface while the electronic device is in the first mode. Reducing the overall brightness of the display reduces power usage and improves the battery life of the device, while still enabling the user to access the device.
Note that details of the processes described above with respect to method 900 (e.g.,
As depicted in
As depicted in
Additionally, analog indication of time 1010 is displayed in a lower brightness relative to its appearance in standard power mode (e.g., as depicted in
At
In response to detecting the drop in environmental brightness, device 600 displays clock face user interface 1008-5 as depicted in
As depicted in
As depicted in
In some embodiments, device 600 first transitions from displaying clock face user interface 1008-1 (e.g., a higher power consumption user interface for high ambient light conditions) to displaying clock face user interface 1008-3 (e.g. a lower power consumption user interface for high ambient light conditions), as described above with respects 10A-10C, then subsequently transitions to displaying clock face user interface 1008-6 (e.g., a lower power consumption user interface for lower ambient light conditions). In some embodiments, portions of analog indication of time 1010 remain brightly displayed (e.g., dimming of hands is foregone, and hands white), when device 600 transitions directly from displaying clock face user interface 1010-3 (e.g. a lower power consumption user interface for high ambient light conditions) to displaying clock face user interface 1008-6 (a lower power consumption user interface for lower ambient light conditions).
In some embodiments, clock face user interface 1008-6 (e.g., lower power consumption user interface for lower ambient light conditions) includes workout affordance 1028 displayed at the brightness level depicted in
As described below, method 1100 provides an intuitive way for managing display usage. The method reduces power usage and the likelihood of screen burn-in. The method also reduces the cognitive burden on a user for managing display usage, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a device to automatically manage display usage faster and more efficiently conserves power and increases the time between battery charges.
While the electronic device (e.g., 600) is in a first mode (e.g., a higher power consumption mode), the electronic device (e.g., 600) displays (1102) on the display (e.g., 602), a first user interface (e.g., 1008-1, 1008-7) (e.g., a clock face of a smart watch; a higher power user interface) at a first display brightness level (e.g., average pixel luminance (APL), average lumen output, total lumen output, average illuminance, or total illuminance of the display; brightness expressed in nits, lux, or lumens). The first user interface includes: a first time indicator (1104) (e.g., 1010 at
The electronic device (e.g., 600) receives (1108) data from the one or more sensors (e.g., a value (digital, analog voltage) representing ambient light measured at a sensor of the electronic device).
The electronic device (e.g., 600) detects (1110) that the electronic device has met criteria for transitioning from the first mode to a second mode (e.g., one or more criteria that are indicative of reduced user activity or reduced user interaction with the electronic device (e.g., determining reduced user activity (physical movement) for a predetermined period of time, determining a lack of user input for a predetermined period of time, detecting a predefined gesture). In some embodiments, detecting that the electronic device has met the criteria includes one or more of: receiving data from one or more sensors (e.g., accelerometer, gyroscope, proximity sensor) corresponding to a user gesture (e.g., wrist-down, wrist-up, palm over display), receiving data from one or more sensors indicating user activity below a threshold activity level, determining a predetermined period of time has elapse without device receiving user input at one or more input devices (e.g., touch-screen, rotatable input mechanism, depressible input mechanism).
In response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, the electronic device (e.g., 600) transitions (1112) the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode). As discussed above in greater detail, the first mode and the second mode are different modes in which the electronic device can operate.
While (1114) the electronic device is in the second mode: in accordance with a determination that the data from the one or more sensors corresponds to a first environmental brightness level, the electronic device (e.g., 600) displays (1116) a second user interface (e.g., 1008-3; 1008-8) (e.g., lower power consumption interface for high ambient light conditions) at a second display brightness level less than the first display brightness level (e.g., average pixel luminance (APL) of inactive interface is lower than APL of the active interface). The second user interface includes: a second time indicator (1118) (e.g., 1010 at
While (1114) the electronic device is in the second mode: in accordance with a determination that the data from the one or more sensors corresponds to a second environmental brightness level lower than the first environmental brightness level, the electronic device (e.g., 600) displays (1122) a third user interface user interface (e.g., 1008-6) (e.g., a lower power consumption interface for low ambient light conditions) at a third display brightness level lower than the second display brightness level (e.g., average pixel luminance (APL) of the lower power consumption interface for low ambient light conditions is less than the APL of the lower power consumption interface for high ambient light conditions). The third user interface includes different content (e.g., 1008-6) than the second user interface (e.g., the third user interface includes a third time indicator different from the second time indicator (e.g., the third time indicator differs from the second time indicator in one or more visual characteristics (size, color, hue, saturation, opacity, shape)); the second user interface includes one or more graphical objects not included in the third user interface (e.g., the second includes a seconds indicator (analog or digital) and third user interface does not include a seconds indicator); the third user interface includes a subset of the graphical objects included in the second interface (e.g., second user interface includes hour ticks and a seconds scale, and third user interface includes hour ticks but does not include a seconds scale); the second user interface includes a greater quantity of graphical objects than the third user interface (e.g., second user interface includes twelve hour markers (e.g., 1-12) and the third user interface includes four hour markers (e.g., 12, 3, 6, 9)); the second user interface includes one or more affordances (complications) and the third user interface does not include at least one of the one or more affordances).
In some embodiments, the electronic device (e.g., 600) detects that the electronic device has not met criteria for transitioning from the first mode to the second mode (e.g., prior to detecting that the electronic device has met criteria for transitioning from the first mode to a second mode). In response to detecting that the electronic device has not met the criteria for transitioning from the first mode to the second mode: in accordance with a determination that second data from the one or more sensors corresponds to a third environmental brightness level, the electronic device (e.g., 600) displays the first user interface (e.g., 1008-5) at a fourth display brightness level different from (e.g., less than) the first display brightness level without transitioning the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode) (e.g., maintain the electronic device in the first mode and continue to display the same user interface but at a different brightness level). In some embodiments, in accordance with a determination that the data from the one or more sensors corresponds to an environmental brightness level different from the third brightness level, the electronic device continues to display the first user interface at the first display brightness level and does not transition the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode) (e.g., maintain the electronic device in the first mode and continue to display the same user interface at the same brightness level). Changing the brightness of the display based on environmental brightness allows the contents of the display to be more easily visible in bright ambient light, thereby providing the user with improved visual feedback, while reducing battery usage in reduced ambient light environments. 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). Reducing the display brightness reduces power usage and improves the battery life of the device.
In some embodiments, transitioning the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode) includes changing the color of one or more user interface elements (e.g., 1010, 1014, 1016, 1018, 1020, 1024, 1026, 1028) having a first color (e.g., white) to be a color other than the first color (e.g., a darker color). In some embodiments, the electronic device changes the color of one or more white user interface elements of the first user interface to a first color when displaying the second user interface and to a second color (different from the first color) when displaying the third user interface. Changing certain colored elements (e.g., white-colored, lighter colored) to a different color allows the device reduce the brightness of elements that more significantly affect battery consumption and to mitigate the negative effects of displaying bright content at the same location on the display, such as display burn-in, while at the same time reducing the display brightness, which reduces power usage and improves the battery life of the device.
In some embodiments, the first graphical object (e.g., 1014, 1018, 1020, and 1026 at
In some embodiments, displaying the second user interface (e.g., 1008-3, 1008-8) (e.g., lower power consumption interface for high ambient light conditions) at the second display brightness level includes applying a mask (e.g., a black mask, a gray mask; an overlay) to a display area. In some embodiments, the electronic device applies a mask the display to reduce the brightness level of the display. In some embodiments, displaying the third user interface (e.g., lower power consumption interface for low ambient light conditions) at the third display brightness level includes applying a black (or gray, or other color) mask to a display area. Applying a mask, such as a black or gray mask, to a display area reduces the display brightness with which that area is displayed. Reducing the display brightness reduces power usage and improves the battery life of the device.
In some embodiments, displaying the second user interface (e.g., 1008-3, 1008-8) (e.g., lower power consumption interface for high ambient light conditions) at the second display brightness level includes turning off one or more pixels (e.g., 1014, 1018, 1020, and 1026 at
In some embodiments, the first graphical object (e.g., 1014, 1016, 1018, 1020, 1024, 1026, and 1028 at
In some embodiments, the first time indicator (e.g., 1010 at
In some embodiments, the first time indicator (e.g., 1010 at
In some embodiments, the first user interface includes a first set of tick marks (e.g., indicating locations corresponding to respective times) displayed with a fourth thickness. In some embodiments, the second user interface (e.g., 1008-3) includes a second set of tick marks (e.g., 1012 at
In some embodiments, a rate of change (e.g., illustrated by change in shading between 1008-1 and 1008-3 of elements 1010 and 1016) in brightness for transitioning from display of the first time indicator to display of the second time indicator is faster than the rate of change in brightness for transitioning from display of the first graphical object to the second graphical object.
In some embodiments, the second user interface (e.g., 1008-3, 1008-7) includes a first complication corresponding to a first application and the third user interface (e.g., 1008-6, 1008-9) includes a second complication corresponding to the first application and a third time indicator. In some embodiments, a difference in brightness between the second time indicator and the first complication is less than a different in brightness between the third time indicator and the second complication.
In some embodiments, the first user interface (e.g., 1008-1) includes a first graphical element (e.g., 1028 of
In some embodiments, a background of the first user interface (e.g., 1008-1) has a third color that is different from a color of the first time indicator. In some embodiments, the second time indicator is displayed in the third color in the second user interface (e.g., 1008-3).
In some embodiments, the first user interface (e.g., 1008-1) includes a first level of color saturation. In some embodiments, the second user interface (e.g., 1008-3) includes a second level of color saturation that is different from (e.g., less than or greater than) the first level of color saturation. In some embodiments, the technique reduces the color saturation of graphical elements when transitioning from the first mode to the second mode. In some embodiments, the technique reduces the color saturation to zero, thereby displaying the user interfaces in monochrome. In some embodiments, the technique reduces the color saturation to zero for certain colors while not reducing the color saturation to zero (but optionally still reducing) for other colors. Reducing the saturation of colors (or of certain colors or elements) mitigates the negative effects of displaying content at the same location on the display, such as display burn-in, while at the same time reducing the display brightness, which reduces power usage and improves the battery life of the device.
Note that details of the processes described above with respect to method 1100 (e.g.,
In
Cellular affordance 1278 includes four circular indicators (e.g., dots) which change appearance in response to changes to a cellular signal strength detected by device 600 (e.g., circular indicators appearing as either solidly-colored or as outlines, a greater number of solidly-colored circular indicators representing a stronger detected signal strength). As depicted in
Noise affordance 1280 includes graphical (e.g., meter graphic), numerical (e.g., “40 dB”), and symbolic (e.g., check mark) indicators which update in response to changes to one or more environmental noise levels detected by device 600. The graphical indicator includes radially-oriented segments which are sequentially emphasized (e.g., transitioned from a first visual appearance to a second visual appearance) in a clockwise direction as a detected noise level increases, and vice versa. In some embodiments, the radially-oriented segments are emphasized with a color based in part on a threshold noise level (e.g., emphasized segments are green when a detected noise level is below a threshold noise level and yellow when a detected noise level is not below the threshold noise level). In some embodiments, the status indicator is updated based in part on a threshold noise level (e.g., including an “OK” or a first graphical element (e.g., a checkmark) when the noise level is below a threshold and “LOUD” or a second graphical element (e.g., an exclamation point) when the noise level is at or above the threshold). In some embodiments, the graphical, numerical, and symbolic indicators are based on different sampling windows of the same noise data and as a result, update at different rates (e.g., graphical and numerical indicators based on an averaged detected noise level over a 1-second window; symbolic indicator based on an averaged detected noise level over a 1-second window). As depicted in
Music affordance 1282 includes a graphical icon (e.g., musical note) surrounded by a circular progress indicator depicting a playback position associated with a music application on device 600 (e.g., a playback position of a media file currently being played or accessed by the music application). As a playback position advances, a portion of the circular progress indicator is progressively emphasized (e.g., transitioned from a first visual appearance to a second visual appearance) in a clockwise direction, beginning at the top of the affordance (e.g., beginning at the twelve o'clock position). As depicted in
At
At
At
As depicted in
In some embodiments, music affordance 1282 includes a track description (e.g., a song title) in place of or in addition to the circular progress indicator. While operating in standard display and low power display modes, device 600 updates the track description (e.g., to indicate a media file currently being played or accessed) in a manner corresponding to the updates to performed to the progress indicator as described herein. For example, while in standard display mode, device 600 updates the track description every second (e.g., at 10:09:02, 10:10:01, and 10:10:02 as depicted in
At
At
At
As described below, method 1300 provides an intuitive way for managing display usage. The method reduces power usage and the likelihood of screen burn-in. The method also reduces the cognitive burden on a user for managing display usage, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a device to automatically manage display usage faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., device 600) displays (1302) a user interface (e.g., 1208-1) that includes a plurality of user interface elements including a graphical representation (e.g., 1220 at
While (1304) the electronic device is in a first mode (e.g., a higher power consumption mode), the electronic device (e.g., device 600) updates (1306) the appearance of the graphical representation of the first type of information over time with a first update interval (e.g., transition from 1208-1 to 1208-2).
While (1304) the electronic device is in the first mode (e.g., a higher power consumption mode) and after updating the appearance of the graphical representation of the first type of information over time one or more times at the first update interval, the electronic device (e.g., device 600) detects (1308) that the electronic device has met criteria for transitioning from the first mode to a second mode.
In response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, the electronic device (e.g., device 600) transitions (1310) the electronic device from the first mode (e.g., a higher power consumption mode) to the second mode (e.g., a lower power consumption mode). As discussed above in greater detail, the first mode and the second mode are different modes in which the electronic device can operate.
While the electronic device is in the second mode, the electronic device (e.g., device 600) updates (1312) the appearance of the graphical representation of the first type of information (e.g., 1220 at
In some embodiments, the plurality of user interface elements includes a graphical representation (e.g., 1282 at
In some embodiments, displaying the user interface that includes the plurality of user interface elements includes displaying, as part of the user interface and concurrently with the graphical representation of the first type of information, a time indicator (e.g., 1210) (e.g., watch hands that indicate the current time, digital readout that indicates the current time, an analog clock hand (hour, minute, second hand); a digital clock numeral (hour, minute, second numerals).
In some embodiments, while the electronic device is operating in the first mode, the electronic device (e.g., 600) updates the time indicator (e.g., 1210 at
In some embodiments, the graphical representation (e.g., 1220 and 1282 at
In some embodiments, the first mode (e.g., operation of device 600 in
In some embodiments, the first update interval is based on an activity level of the first application. In some embodiments, the second update interval is not based on the activity level of the first application. In some embodiments, both the first update interval and the second update interval are based on the activity level of the first application. Changing the interval at which the appearance of graphical elements are displayed based on the activity level of the corresponding applications enables the device to conserve battery power by, for example, avoiding unnecessarily checking for information from the application that is not available or updating the display when new information would not be available, which reduces power usage and improves the battery life of the device. As a result, more active applications cause the corresponding graphical elements to be updated more frequently while less active applications cause the corresponding graphical element to be updated less frequently.
In some embodiments, updating the appearance of the graphical representation of the first type of information includes displaying an animation (e.g., display 1208-1 to 1208-4). In some embodiments, updating the appearance of the first type of information in the first mode includes displaying the animation and updating the appearance of the first type of information in the second mode does not include displaying the animation.
In some embodiments, a first display brightness (e.g., Average Pixel Luminance (APL)) of the display (e.g., display 602 at
In some embodiments, while the electronic device is in the second mode, the electronic device (e.g., 600) displays an indication (e.g., removal of 1210 in
In some embodiments, in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode, the electronic device (e.g., 600) computes (e.g., prior to transitioning to the second mode) animation frames for the graphical representation of the first type of information to be displayed while the electronic device is in the second mode (e.g., to use to update the appearance of the graphical representation of the first type of information over time with the second update interval). In some embodiments, frames for graphical representations that can be accurately predicted (e.g., upcoming calendar event, song progress) for display in the second mode are computed in the first mode. Computing animation frames for display in the second mode (e.g., before entering the second mode) enables the device to avoid computing the animation frames while in the second mode, thereby allowing those processing components to be put to sleep, which reduces power usage and improves the battery life of the device. Computing animation frames for display in the second mode (e.g., before entering the second mode) enables the device to display the animation frames while in the low power consumption mode, thereby providing the user with visual feedback. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the plurality of user interface elements includes a graphical representation of a third type of information that is associated with a third application (e.g., data received from the application is optionally displayed as part of the graphical representation). In some embodiments, while the electronic device is operating in the first mode, the electronic device (e.g., 600) updates the appearance of the graphical representation of the third type of information over time with a seventh update interval. While the electronic device is operating in the second mode, the electronic device (e.g., 600) forgoes updating (e.g., maintaining) the appearance of the graphical representation of the third type of information over.
Note that details of the processes described above with respect to method 1300 (e.g.,
In particular,
At
At
At
At
The timer application continues to execute throughout the times in
At
At
At
At
At
At
At
At
At
At
At
At
At
At
At
At
At
At
As described below, method 1500 provides an intuitive way for managing display usage. The method reduces power usage and the likelihood of screen burn-in. The method also reduces the cognitive burden on a user for managing display usage, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a device to automatically manage display usage faster and more efficiently conserves power and increases the time between battery charges.
While the electronic device (e.g., 600) is operating in a first mode (e.g., a higher power consumption mode), the electronic device (e.g., 600) displays (1502), on the display, a first user interface (e.g., a higher power consumption interface; 1402 of
While displaying the first user interface, the electronic device (e.g., 600) detects (1504) that the electronic device (e.g., 600) has met criteria for transitioning from the first mode to a second mode (e.g., a lower power consumption mode).
In some embodiments, in response (1506) to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode (e.g., criteria that are indicative of reduced user interaction with the electronic device (e.g., timeout expiration, accelerometer data indicating wrist down, touch data indicating palm over gesture)), the electronic device (e.g., 600) transitions the electronic device from the first mode to the second mode in response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode. As discussed above in greater detail, the first mode and the second mode are different modes in which the electronic device can operate.
In response (1506) to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode and in accordance with a determination that the first application is an application of a first type (e.g., an application that includes a lower power consumption interface), the electronic device (e.g., 600) replaces (1508) display of the first user interface (e.g., 1402, 1420) of the first application with a second user interface (e.g., a lower power consumption interface, 1404 of
In response (1506) to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode and in accordance with a determination that the first application is an application of a second type (e.g., an application that does not include a lower power consumption interface), the electronic device (e.g., 600) replaces (1510) display of the first user interface (e.g., 1408 of
Displaying a lower power consumption interface of an application when available enables the device to continue to show information specific to that application while in the lower power consumption mode, yet still allows the device to achieve the lower power consumption mode when the lower power consumption interface is not available for the application by displaying a lower power consumption watch face. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, while the electronic device (e.g., 600) is in the second mode and is displaying the third user interface (e.g., 1406 of
In some embodiments, while the electronic device (e.g., 600) is in the second mode and is displaying the third user interface (e.g., 1406 of
Displaying a brighter user interface when the device detects that the user is attempting to interact with the device provides the user with feedback that the device has left the lower power consumption mode. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the second set of criteria for transitioning from the second mode to the first mode includes a criterion that is met when the electronic device (e.g., 600) detects a wrist raise gesture (e.g., detected using one or more motion sensors of the electronic device to detect the device changing in orientation to an orientation that is facing upward at an angle). Displaying a brighter user interface when the device detects that the user is performing a wrist raise gesture to interact with the device provides the user with feedback that the device has left the lower power consumption mode. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the second set of criteria for transitioning from the second mode to the first mode includes a criterion that is met when the electronic device detects a tap gesture (e.g., 1450d, detected using a touch-sensitive surface of the electronic device).
Displaying a brighter user interface when the device detects that the user is performing a tap gesture to interact with the device provides the user with feedback that the device has left the lower power consumption mode. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, while the electronic device is in the second mode and is displaying the second user interface, the electronic device (e.g., 600) detects that the electronic device has met a third set of criteria for transitioning from the second mode to the first mode. In some embodiments, the third set of criteria for transitioning from the second mode to the first mode are met with the electronic device detects a user input (e.g., detecting a wrist raise gesture, detecting a touch gesture, such as a tap, on a touch-sensitive surface of the electronic device) (within the threshold period of time). In response to detecting that the electronic device has met the third set of criteria for transitioning from the second mode to the first mode, the electronic device (e.g., 600) replaces (e.g., in accordance with a determination that the first user interface was not a system user interface, in accordance with a determination that the user input was received within the threshold period of time, such as 2 seconds) display of the second user interface with display of the first user interface (e.g., 1402 of
Displaying a brighter user interface when the device detects that the user is attempting to interact with the device provides the user with feedback that the device has left the lower power consumption mode. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, while the electronic device is in the second mode and is displaying the third user interface (e.g., 1406 of
In some embodiments, in response to detecting that the electronic device has met the fourth set of criteria for transitioning from the second mode to the first mode: in accordance with a determination that a set of criteria is met (e.g., the set of criteria including one or more of: a time-from-input criterion that is met when the user input is detected within a threshold period of time (e.g., 2 seconds, 5 seconds) of the electronic device transitioning to the second mode, a touch-gesture criterion that is met when the user input is a touch gesture detected on a touch-sensitive surface of the electronic device, a tap-gesture criterion that is met when the user input is a tap gesture detected on the touch-sensitive surface of the electronic device, and a wrist-raise-gesture that is met when the user input is a wrist-raise gesture detected using one or more sensors (e.g., motion sensors) of the electronic device), the electronic device (e.g., 600) replaces display of the third user interface with display of the first user interface (e.g., 1402 at
In some embodiments, in response to detecting that the electronic device has met the fourth set of criteria for transitioning from the second mode to the first mode: in accordance with a determination that the set of criteria is not met (e.g., input is detected after the threshold period of time, after 5 seconds), replacing display of the third user interface (e.g., 1406 at
In some embodiments, the user input is a wrist raise gesture (e.g., detected using one or more motion sensors of the electronic device). In some embodiments, the input type criterion is satisfied if the user input is a wrist raise gesture. Displaying a brighter user interface when the device detects that the user is performing a wrist raise gesture to interact with the device provides the user with feedback that the device has left the lower power consumption mode. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the user input is a tap gesture (e.g., 1450c, 1450d, detected using a touch-sensitive surface of the electronic device). In some embodiments, the input type criterion is satisfied if the user input is a tap gesture. In some embodiments, the input type criterion is satisfied if the user input is either a tap gesture or a wrist raise gesture. In some embodiments, the threshold period of time varies based on the type of input received. In some examples, the threshold period of time is shorter when the user input is a tap input and longer when the user input is a wrist raise gesture. Displaying a brighter user interface when the device detects that the user is performing a tap gesture to interact with the device provides the user with feedback that the device has left the lower power consumption mode. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first graphical object (e.g., 1402c, 1420c) (or a another graphical object, such as 1402d, 1402e) is displayed with a first visual characteristic (e.g., in a first color) in the first user interface and the first graphical object (or the another graphical object 1402d, 1402e), when selected in the first user interface, activates a first function (e.g., device detecting tap gesture on the first graphical object causes a corresponding function (e.g., a function related to the first application) to be performed). For example, cancel when affordance 1402d is pressed, pause when affordance 1402e is pressed.
In some embodiments, the first graphical object (or the another graphical object 1402d, 1402e) is displayed with a second visual characteristic (e.g., in a second color, such as in a darker color affordance in 1404 of
In some embodiments, the first graphical object (e.g., 1420c) (e.g., a first metric provided by a workout application) is a selected graphical object (e.g., is visually distinguished (e.g., by highlighting, by bolding, by being different in size) from other graphical objects of the first user interface (e.g., indicating that it is selected and/or highlighted for further action)). In some embodiments, only one graphical object can be selected at a time and selection of another graphical object deselects the first graphical object. In some embodiments, the first application is a workout application (e.g., a physical activity tracking application. In some embodiments, the first user interface of the first application includes a third graphical object (e.g., 1420d-1420e in
In some embodiments, replacing display of the first user interface of the first application with a second user interface (e.g., a lower power consumption interface) of the first application different from the first user interface includes: in accordance with a determination that the second graphical object (e.g., 1420g) corresponds to the selected first graphical object (e.g., the second graphical object includes at least a portion of the same information as the first graphical object), the electronic device (e.g., 600) displays the second graphical object (e.g., 1420g) at a first brightness level (e.g., average pixel luminance (APL), average lumen output, total lumen output, average illuminance, or total illuminance of the indicator on the display; brightness expressed in nits, lux, or lumens); and in accordance with a determination that the second graphical object (e.g., 1420d-1420e in
In some embodiments, after displaying the second graphical object (e.g., 1420g at 1418b) at the first brightness level, the electronic device (e.g., 600) displays, on the display, a second instance of the first user interface with the first graphical object as a selected object. the electronic device (e.g., 600) detects a set of one or more inputs corresponding to a request to select the third graphical object. In response to detecting the set of one or more inputs corresponding to a request to select the third graphical object: the electronic device (e.g., 600) selects the third graphical object and de-selecting the first graphical object. In some embodiments, displaying the third graphical object with one or more visual characteristics that indicate that it is selected (e.g., by highlighting, by bolding, by being different in size) from other graphical objects of the first user interface (e.g., indicating that it is selected and/or highlighted for further action)). While the third graphical object is selected, the electronic device (e.g., 600) detects that the electronic device has met criteria for transitioning from the first mode to a second mode. In response to detecting that the electronic device has met criteria for transitioning from the first mode to a second mode while the third graphical object is detected, the electronic device (e.g., 600) replaces display of the second instance of the first user interface with a second instance of the second user interface that includes a fourth graphical object that: in accordance with a determination that the fourth graphical object corresponds to the first graphical object that is not selected, is displayed at a third brightness level; and in accordance with a determination that the fourth graphical object corresponds to the third graphical object that is selected, is displayed at a fourth brightness level that is greater than the third brightness level. In some embodiments, selecting a different graphical object (e.g., while in the first user interface) causes a graphical object of the second user interface that corresponds to the newly selected graphical object to be displayed with a brightness level that is greater than the brightness of a graphical object of the second user interface that corresponds to the previously selected (but no longer selected) graphical object of the first user interface. Differentiating between selected and unselected graphical elements for brightness control enables the device to show selected elements (e.g., that is particularly relevant to the user) at an appropriate brightness level so that the user can more readily access the selected information, yet reduce the overall display brightness, which reduces power usage and improves the battery life of the device.
In some embodiments, the fourth graphical object updates with a shorter update interval than the second graphical object based on the third graphical object having been selected. In some embodiments, graphical objects in the second user interface that correspond to selected graphical object in the first user interface update with shorter update intervals than graphical objects in the second user interface that do not correspond to selected graphical objects in the first user interface. Differentiating between selected and unselected graphical elements for frequency of updates enables the device to update selected elements (e.g., that is particularly relevant to the user) at appropriate intervals so that the user can more readily access the selected information, yet reduce the overall processing required for the user interface, which reduces power usage and improves the battery life of the device.
In some embodiments, the electronic device (e.g., 600) displays, on the display, a fourth user interface (e.g., a higher power consumption interface) of (e.g., generated by) a second application (e.g., an installed application distinct from the operating system; an interface corresponding to an application operating in the foreground) that is different from the first application, the fourth user interface including a fifth graphical object corresponding to (e.g., generated by) the second application (e.g., a graphical object that includes information provided by the second application). While displaying the fourth user interface, the electronic device (e.g., 600) detects that the electronic device has met the criteria for transitioning from the first mode to the second mode. In response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode (e.g., criteria that are indicative of reduced user interaction with the electronic device (e.g., timeout expiration, accelerometer data indicating wrist down, touch data indicating palm over gesture)): in accordance with a determination that the second application is an application of the first type (e.g., an application that includes a lower power consumption interface), the electronic device (e.g., 600) replaces display of the fourth user interface of the second application with a fifth user interface (e.g., a lower power consumption interface) of the second application different from the fourth user interface (e.g., lower power interface differs from the higher power interface in one or more visual characteristics (size of elements, color, hue, saturation, opacity, shape)), the fifth user interface including a sixth graphical object corresponding to the second application (e.g., a graphical object that includes information provided by the second application). In some embodiments, the sixth graphical object is the fifth graphical object. In some embodiments, the sixth graphical object corresponds to the fifth graphical object (e.g., the sixth graphical object includes the same information as the fifth graphical object). In some embodiments, in accordance with a determination that the second application is an application of the second type (e.g., an application that does not include a lower power consumption interface), the electronic device (e.g., 600) replaces display of the fourth user interface of the second application with the third user interface (e.g., a clock face of a smart watch). In some embodiments, the third user interface is not generated by the second application. In some embodiments, the third user interface is different from the fifth user interface of the second application and the sixth user interface of the second application. In some embodiments, the third user interface does not include graphical objects (e.g., any graphical objects) generated by the second application (e.g., does not include graphical objects that include information provided by the second application).
In some embodiments, display of the first user interface (e.g., 1402 of
In some embodiments, in response to detecting that the electronic device (e.g., 600) has met criteria for transitioning from the first mode to the second mode, prior to replacing display of the first user interface (e.g., 1408 at
In some embodiments, the third user interface includes a graphical object (e.g., 1406f associated with a compass application) associated with a third application (e.g., the graphical object is a complication that displays information received from the third application) and a graphical object associated (e.g., 1406g associated with a world time application) with a fourth application (e.g., the graphical object is a complication that displays information received from the fourth application).
In some embodiments, while the electronic device is operating in the first mode, the electronic device (e.g., 600) displays, on the display, a system user interface (e.g., 1818 of
In some embodiments, in response to detecting that the electronic device has met the fifth set of criteria for transitioning from the first mode to the second mode: in accordance with the electronic device displaying the system user interface when the sixth set of criteria for transitioning from the first mode to the second mode are met, replacing display of the system user interface (e.g., 1818 of
Note that details of the processes described above with respect to method 1500 (e.g.,
In particular,
While displaying user interface 1602 of the stopwatch application, device 600 determines that the device has met the mode-transition criteria (e.g., detecting a wrist-down gesture using, for example, motion sensors; no input of certain types for 15 seconds). In response to the determination that device 600 has met the mode-transition criteria, device 600 transitions to a low power display mode and replaces user interface 1602 with user interface 1604. User interface 1604 is a lower power consumption interface (as compared to 1602) and is displayed using the first template (e.g., based on device 600 having determined that the timer application corresponds to the first template).
In some embodiments, the stopwatch application provides the time for stopwatch timer 1604c, but the stopwatch application is not able to specify (e.g., because the operating system of device 600 specifies) the color, size, location, font, and/or precision with which to display the timer, for device 600 to display user interface 1604 in the low power display mode.
While displaying user interface 1606 of the music application, device 600 determines that device 600 has met the mode-transition criteria (e.g., detecting a wrist-down gesture using, for example, motion sensors; no input of certain types for 15 seconds). In response to the determination that device 600 has met the mode-transition criteria, device 600 transitions to a low power display mode and replaces user interface 1606 with user interface 1608. User interface 1608 is a lower power consumption interface (as compared to 1606) and is displayed using the first template (e.g., based on device 600 having determined that the music application corresponds to the first template).
In some embodiments, the music application provides the name for song name 1608c, but the music application is not able to specify the color, size, location, font, and/or precision with which to display the name, for device 600 to display user interface 1608 in the low power display mode.
Because user interface 1604 and 1608 both use the same first template, they have various visual characteristics in common. In some embodiments, the location, size, color, and font of title 1604a is the same as those of 1608a. In some embodiments, the location, size, color, and font of stopwatch timer 1604c is the same as those of song name 1608c. In some embodiments, the background color of user interface 1604 and 1608 is the same color. In some embodiments, user interface 1604 and 1608 each include only two fields (e.g., for title and for stopwatch timer/song name).
While displaying user interface 1610 of the progress tracking application, device 600 determines that device 600 has met the mode-transition criteria (e.g., detecting a wrist-down gesture using, for example, motion sensors; no input of certain types for 15 seconds). In response to the determination that device 600 has met the mode-transition criteria, device 600 transitions to a low power display mode and replaces user interface 1610 with user interface 1612. User interface 1612 is a lower power consumption interface (as compared to 1610) and is displayed using the second template (e.g., based on device 600 having determined that the progress tracking application corresponds to the second template) that is different from the first template.
In some embodiments, the progress tracking application provides the units for measurement units 1612b and provides the progress and goal for time progress information 1612c, but the progress tracking application is not able to specify the color, size, location, font, and/or precision with which to display the information, for device 600 to display user interface 1612 in the low power display mode.
Because user interface 1612 uses a second template that is different from the first template used for user interface 1604 and 1608, use interface 1612 has various visual characteristics that differ from those of user interfaces 1604 and 1608. In some embodiments, the location, size, color, and font of measurement units 1612b and time progress information 1612c are different from graphical elements of user interfaces 1604 and 1608. In some embodiments, the background color of user interface 1604, 1608, and 1612 is the same color. In some embodiments, user interface 1604 and 1608 each include only two fields (e.g., for title and for stopwatch timer/song name), while user interface 1612 includes more than two fields.
As described below, method 1700 provides an intuitive way for managing display usage. The method reduces power usage and the likelihood of screen burn-in. The method also reduces the cognitive burden on a user for managing display usage, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a device to automatically manage display usage faster and more efficiently conserves power and increases the time between battery charges.
While (1702) the electronic device (e.g., 600) is operating in a first mode (e.g., a higher power consumption mode), the electronic device (e.g., 600) displays (1704), on the display, a first user interface (e.g., 1602; a higher power consumption interface) of a first application with an arrangement of user interface elements (e.g., 1602c-1602e) determined by the first application, and displays (1706), on the display, a second user interface (e.g., 1606; a higher power consumption interface) of a second application with an arrangement of user interface elements (e.g., 1606c-1606f) determined by the second application.
While the electronic device (e.g., 600) is operating in the first mode, the electronic device (e.g., 600) detects (1710) that the electronic device has met criteria for transitioning from the first mode to a second mode (e.g., a lower power consumption mode).
In response to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode (e.g., criteria that are indicative of reduced user interaction with the electronic device (e.g., timeout expiration, accelerometer data indicating wrist down, touch data indicating palm over gesture)), the electronic device (e.g., 600) transitions (1712) from the first mode to the second mode.
Transitioning (1712) from the first mode to the second mode includes: in accordance with a determination that the first application (e.g., 1602) was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode, displaying (1714) information (e.g., 1604c) from the first application in a predefined template (e.g., template shown used in 1604 and 1608; a preset format (e.g., comprising preset elements (e.g., graphical elements, watch complications, text elements, and/or time indicator elements), preset sizes for elements, preset color schemes for elements, preset brightness level schemes for elements, and/or present positions for elements); a preset arrangement; a preset layout).
Transitioning (1712) from the first mode to the second mode includes: in accordance with a determination that the second application (e.g., 1606) was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode, displaying (1716) information (e.g., 1608c) from the second application in the predefined template (e.g., template shown used in 1604 and 1608). As discussed above in greater detail, the first mode and the second mode are different modes in which the electronic device can operate.
Displaying information from various applications using the same template enables the device to display information from those various applications using a lower power consumption interface, which reduces power usage and improves the battery life of the device. Displaying information in the same template also provides the user with feedback about the state of the device (e.g., that it is in the second mode). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, while (1702) the electronic device is operating in the first mode (e.g., a higher power consumption mode), the electronic device (e.g., 600) displays (1708) a third user interface (e.g., 1610; a higher power consumption interface) of a third application with an arrangement of user interface elements (e.g., 1610c-1610f) determined by the third application. In some embodiments, transitioning (1712) from the first mode to the second mode includes: in accordance with a determination that the third application (e.g., 1610) was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode, displaying (1718) information (e.g., 1612b-1612c) from the third application in a second predefined template (e.g., template as shown in 1612) that is different (e.g., having a different predefined set or arrangement of elements; having the same elements but arranged in a different predefined spatial pattern) from the predefined template (e.g., template as shown in 1604 and 1608). In some embodiments, different applications use different predefined temples for displaying information while the electronic device is in the second mode. In some embodiments, the first application and the second application are a first type of application and accordingly use the predefined template and the third application is a second type of application (different from the first type) and thus the second predefined template is used. In some embodiments, the predefined template and the second predefined template include placement of user interface elements at different positions.
Displaying information from particular types of applications using templates that correspond to the application enables the device to display information from those different types of applications in formats appropriate for the applications in lower power consumption interface formats, which reduces power usage and improves the battery life of the device.
In some embodiments, the predefined template (e.g., template as shown in 1604 and 1608) is a user interface template configured for use in a low power consumption mode. In some embodiments, the power required to display the first user interface is higher than that required to display information (e.g., of the first and/or the second applications) in the predefined template. In some embodiments, displaying information of the first application in the predefined template requires approximately the same amount of power as displaying the information of the second application in the predefined template.
In some embodiments, the predefined template includes an icon template field for display of an application icon corresponding to the application that was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode.
In some embodiments, the predefined template includes an information template field (e.g., template field for displaying 1604c, 1608c) for display of the information from the application that was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode.
In some embodiments, the predefined template also includes a title template field for display of the name of the application or a title provided by the application. In some embodiments, the icon template field is positioned at the top of the user interface, the title template field is positioned below the icon template field, and the information template field is displayed below the title template field. Displaying an application icon and information from an application provides the user with feedback about which application is providing the information. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first application is of a first category of applications (e.g., applications that require more frequent display updates in the second mode) and the second application is of a second category of applications (e.g., applications that require less frequent updates in the second mode) different from the first category of information. While the electronic device is operating in the second mode, the electronic device (e.g., 600) updates the information (e.g., 1604c, 1608c) from the application that was displayed on the display when the electronic device detected that the electronic device has met criteria for transitioning from the first mode to a second mode, over time with an update interval that is determined based on the category of the application. In some embodiments, when information from the first application is being displayed, the information is updated with a first update interval (e.g., updated every second) and when information from the second application is being displayed, the information is updated with a second update interval (e.g., updated every two seconds) that is different from the first update interval. For example, information from an application that is categorized as a workout (e.g., user exercise tracking) application is updated more frequently than information from an application that is not categorized as a workout application.
Changing the interval at which displayed information from applications are updated based on the category of the application enables the device to conserve battery power by reducing the frequency with which the information to be displayed is calculated and the frequency with which the display should be refreshed when, for example, the application is a lower priority application and/or the application does not provide frequent/constant updated information, which reduces power usage and improves the battery life of the device.
In some embodiments, the information from the first application is of a first category of information (e.g., timer information 1604c, information that requires more frequent display updates in the second mode) and the information from the second application is of a second category of information (e.g., track name information 1608c, information that require less frequent updates in the second mode) different from the first category of information. While the electronic device is operating in the second mode, the electronic device (e.g., 600) updates display of information (e.g., 1604c, 1608c) from the application that was displayed on the display over time with an update interval that is determined based on the category of the information. In some embodiments, displayed information from the first category of information is updated with a first information update interval (e.g., updated every second) and displayed information from the second category of information is updated with a second information update interval (e.g., updated every two seconds, ten seconds, or minute) that is different from the first information update interval. For example, information that is categorized as workout (e.g., user exercise tracking) information is updated more frequently than information that is not categorized as workout information. Changing the interval at which displayed information from applications are updated based on the category of the information enables the device to conserve battery power by reducing the frequency with which the information to be displayed is calculated and the frequency with which the display should be refreshed when, for example, the type of information is lower priority information and/or the type of information is not time-sensitive, which reduces power usage and improves the battery life of the device.
In some embodiments, displaying the first user interface (e.g., a higher power consumption interface) of the first application with an arrangement of user interface elements determined by the first application includes displaying information of a first category of information (e.g., timer information; workout information, steps taken, heart rate). In some embodiments, displaying information from the first application in the predefined template includes displaying information of the first category of information. In some embodiments, the displayed information from the first application in the predefined template being visually different (e.g., not having a hundredths of seconds field as shown in 1604c) from the displayed information in the first user interface by one or more visual characteristics other than color. In some embodiments, the information displayed in the first user interface is a first size and the same category of information displayed using the predefined template is in a second size different from the first size (e.g., smaller than the first size). In some embodiments, the information displayed in the first user interface is displayed at a first brightness level and the same category of information displayed using the predefined template is in at a second brightness level different from the first brightness level (e.g., less bright than the first brightness level).
Displaying the information from the application in visually distinct ways provides the user with feedback about the state of the device. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, displaying the first user interface (e.g., 1602; a higher power consumption interface) of the first application with an arrangement of user interface elements determined by the first application includes displaying a first set of information (e.g., minutes and seconds of 1602c) and a second set of information (e.g., hundredths of seconds of 1602c). In some embodiments, displaying information from the first application in the predefined template includes displaying the first set of information (e.g., minutes and seconds of 1602c) without displaying the second set of information (e.g., hundredths of seconds of 1602c). In some embodiments, the amount of information displayed while in the second mode is less than the amount of information displayed while in the first mode.
In some embodiments, a first display brightness level (e.g., average pixel luminance (APL), average lumen output, total lumen output, average illuminance, or total illuminance of the indicator on the display; brightness expressed in nits, lux, or lumens) of the display while displaying the first user interface (e.g., 1602) while the electronic device is in the first mode (e.g., a higher power consumption mode) is higher than a second display brightness level of the display while displaying information from the first application in the predefined template (e.g., 1604) while the electronic device is in the second mode (e.g., a lower power consumption mode). In some embodiments, a third display brightness level (e.g., Average Pixel Luminance (APL)) of the display while displaying the second user interface while the electronic device is in the first mode (e.g., a higher power consumption mode) is higher than a fourth display brightness level (e.g., APL, same as second display brightness) of the display while displaying information from the second application in the predefined template while the electronic device is in the second mode (e.g., a lower power consumption mode). Thus, the overall brightness of the display is reduced when displaying information while the electronic device is in the second mode as compared to displaying information while the electronic device is in the first mode. Reducing the overall brightness of the display reduces power usage and improves the battery life of the device, while still enabling the user to access the device.
Note that details of the processes described above with respect to method 1700 (e.g.,
In particular,
As part of the transition from user interface 1802 to user interface 1804, device 600 ceases to display (e.g., fades out, blurs out) current time 1802b and changes the brightness of user interface 1802 (e.g., including title 1802a and graphical elements 1802c) such that they are less bright, as shown in user interface 1804 of
The transition continues, with device 600 animating changes from user interface 1804 to user interface 1806. Device 600 displays (e.g., fades in, blurs in) current time 1806b and changes the brightness of user interface 1804 (e.g., including title 1802a and graphical elements 1802c) such that user interface 1806 is less bright as compared to user interface 1804 and 1802, as shown in
Current time 1806b at
At
While displaying user interface 1808 at
As part of the animated transition to display user interface 1812, device 600 ceases to display (e.g., fades out, blurs out) current time 1806b, as illustrated in user interface 1810 of FIG. 18E. At
User interface 1814 is a higher power consumption user interface displayed while device 600 is in the standard display mode. While displaying user interface 1814, device 600 determines that device 600 has met the mode-transition criteria (e.g., detecting a wrist-down gesture using, for example, motion sensors; no input of certain types for 15 seconds). In response to the determination that device 600 has met the mode-transition criteria, device 600 begins to transition to a low power display mode, resulting in replacing user interface 1814 with user interface 1816, a lower power consumption user interface.
As part of the transition from user interface 1814 to user interface 1816, device 600 ceases to display (e.g., fades out, blurs out) current time 1802b instead displays current time 1814f at a larger size and at a different location. Device 600 reduces the brightness of the display when transitioning from user interface 1814 to 1816. Device 600 reduces the brightness at which title 1814a, countdown timer 1814c, cancel affordance 1814d, and pause affordance 1814e are displayed. For example, device 600 changes some (or all) white elements, such as title 1802, to a gray color, thereby reducing the amount of power the elements consume and reducing the risk of burn-in on the display. Concurrently with reducing the brightness of the user interface, device 600 reduces the size of the user interface elements, while optionally maintaining a center of the user interface, as shown in the transition between user interface 1814 and 1816. Device 600 blurs elements of the user interface, as shown in user interface 1816 of
In
While displaying a system user interface (e.g., 1818, 1820), device 600 determines that device 600 has met the mode-transition criteria (e.g., detecting a wrist-down gesture using, for example, motion sensors; no input of certain types for 15 seconds). In response to the determination that device 600 has met the mode-transition criteria, device 600 begins to transition to a low power display mode and replaces the system user interface (e.g., 1818, 1820) with user interface 1822, a clock face user interface that is a lower power consumption user interface. Thus, in accordance with a determination that the currently displayed user interface is a system interface, device 600 replaces the system interface with user interface 1822, which is a lower power user interface. As noted by brightness scale 630, the overall brightness of the display of device 600 is higher while displaying the system user interface (e.g., 1818, 1820) than while displaying user interface 1822. Thus, device 600 consumes less power while displaying user interface 1822. In some embodiments, in accordance with the determination that the currently displayed user interface is a system interface, device 600 does not reduce down in size and blur out the displayed user interface (e.g., 1818, 1820) when the mode-transition criteria is met (and does when the user interface is not a system interface, described above with respect to 18A-18C and 18G-18H).
While displaying user interface 1822 at
As described below, method 1900 provides an intuitive way for managing display usage. The method reduces power usage and the likelihood of screen burn-in. The method also reduces the cognitive burden on a user for managing display usage, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a device to automatically manage display usage faster and more efficiently conserves power and increases the time between battery charges.
While the electronic device (e.g., 600) is operating in a first mode, the electronic device (e.g., 600) displays (1902), on the display, a first user interface (e.g., 1802, 1814) of (e.g., a higher power consumption interface) an application. The electronic device (e.g., 600) detects (1904) (e.g., while displaying the first user interface) that the electronic device has met criteria for transitioning from the first mode to a second mode.
In response (1906) to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode (e.g., criteria that are indicative of reduced user interaction with the electronic device (e.g., timeout expiration, accelerometer data indicating wrist down, touch data indicating palm over gesture)), the electronic device (e.g., 600) transitions (1908) from the first mode to the second mode. As discussed above in greater detail, the first mode and the second mode are different modes in which the electronic device can operate.
In response (1906) to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode (e.g., criteria that are indicative of reduced user interaction with the electronic device (e.g., timeout expiration, accelerometer data indicating wrist down, touch data indicating palm over gesture)), the electronic device (e.g., 600) replaces (1910), on the display, the first user interface with a second user interface (e.g., 1806, 1808, 1816; a lower power consumption interface) including an obscured representation (e.g., 1802a, 802c, 1814a, 1814c, 1814d) of at least a portion of the first user interface (e.g., 1802, 1814) of the application (e.g., a representation of the same graphical object including the same data with reduced sharpness (detail) or contrast (e.g., blurred); a representation resulting from applying a non-linear filter to the representation).
In response (1906) to detecting that the electronic device has met the criteria for transitioning from the first mode to the second mode (e.g., criteria that are indicative of reduced user interaction with the electronic device (e.g., timeout expiration, accelerometer data indicating wrist down, touch data indicating palm over gesture)), the electronic device (e.g., 600) displays (1914) a time indicator (e.g., 1806b, 1814f) at a position on the display overlapping at least a portion of the obscured representation (e.g., 1802c, 1814c) of the at least a portion of the first user interface (e.g., 1802, 1814) of the application (e.g., time overlay).
Displaying an obscured representation of the interface of the application provides the user with visual feedback that the device is operating in a lower power consumption mode while still providing the user with feedback about the application that was displayed when the device entered the lower power consumption mode. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the obscured representation (e.g., 1802a, 802c, 1814a, 1814c, 1814d) of at least a portion of the first user interface (e.g., 1802, 1814) of the application is a blurred (1912) representation of at least the portion of the first user interface (e.g., 1802, 1814). In some embodiments, obscuring the representation of the portion of the first user interface for display includes blurring the representation of the portion of the first user interface. Obscuring the representation of the interface of the application provides the user with visual feedback that the device is operating in a lower power consumption mode while still providing the user with feedback about the application that was displayed when the device entered the lower power consumption mode. Further, obscuring the representation of the interface of the application provides the user with additional security, as other users are less able to view the contents of the application. Providing improved visual feedback to the user and improving security enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, displaying the first user interface (e.g., 1802, 1814) of the application while in the first mode includes displaying the portion of the first user interface (e.g., 1802c, 1814c) of the application at a first size. In some embodiments, replacing the first user interface with the second user interface including the obscured representation of at least the portion of the first user interface of the application includes displaying an obscured representation of the portion of the first user interface of the application at a second size that is smaller than the first size (e.g., as shown in
In some embodiments, displaying the first user interface (e.g., 1802, 1814) of the application while in the first mode includes displaying the portion of the first user interface (e.g., 1802, 1814) of the application at a first brightness level. In some embodiments, replacing the first user interface (e.g., 1802, 1814) with the second user interface (e.g., 1806, 1816) including the obscured representation of at least the portion of the first user interface of the application includes displaying an obscured representation of the portion of the first user interface of the application at a second brightness level that is lower than the first brightness level (e.g., as shown in
In some embodiments, replacing the first user interface (e.g., 1802, 1814) with the second user interface (e.g., 1806, 1816) includes dimming the display by an amount to reduce the brightness of the display, the amount based on the content of the first user interface (e.g., 1802, 1814). In some embodiments, the electronic device dims the displays more when the content of the first user interface is brighter (e.g., includes brighter images) than when the content of the first user interface is less bright (e.g., includes less bright images). In some embodiments, the amount by which the electronic device dims the brightness of the display is based on a requirement to meet a threshold APL when the second user interface is displayed. Dimming the interface of the application by an amount based on the content of the interface enables the device to, for example, dim brighter user interface more and dim less-brighter user interfaces less, thereby achieving a threshold reduced APL, which reduces power usage and improves the battery life of the device.
In some embodiments, replacing the first user interface (e.g., 1802, 1814) with the second user interface (e.g., 1806, 1816) includes dimming the display by an amount to reduce the brightness of the display, the amount based on an environmental brightness level (e.g., ambient light level). In some embodiments, the amount of dimming increases as the environmental brightness increases and the amount of dimming decreases as the environmental brightness decreases (e.g., based on a magnitude of change in the environmental brightness level). In some embodiments, the amount of dimming decreases as the environmental brightness increases and the amount of dimming increases as the environmental brightness decreases (e.g., based on a magnitude of change in the environmental brightness level). Dimming the display based on environmental brightness levels allows the contents of the display to be more easily visible in bright ambient light environments, thereby providing the user with improved visual feedback, while reducing battery usage in reduced ambient light environments. 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). Reducing the display brightness reduces power usage and improves the battery life of the device.
In some embodiments, replacing, on the display, the first user interface (e.g., 1802, 1814) with a second user interface (e.g., 1806, 1816) including the obscured representation of at least a portion of the first user interface (e.g., 1802, 1814) of the application includes displaying a first animation of the at least a portion of the first user interface transitioning from an unobscured state to the obscured state. In some embodiments, displaying the time indicator (e.g., 1806b, 1814f) at the position on the display overlapping at least a portion of the obscured representation (e.g., 1802c, 1814c) of the at least a portion of the first user interface of the application includes displaying a second animation of the time indicator becoming displayed (e.g., an animation of the time indicator appearing (e.g., transitioning from being not displayed to displayed; moving from a previous position to the final position) at the position on the display overlapping at least a portion of the obscured representation of the at least a portion of the first user interface of the application). In some embodiments, at least a portion of the first animation occurs concurrently with at least a portion of the second animation. In some embodiments, the first animation and the second animation are synchronized (e.g., synchronized to start at the same time and/or end at the same time). In some embodiments, time indicator displayed in the first user interface fades out while the time indicator at the position on the display overlapping the at least portion of the obscured representation of the user interface of the application fades in. In some embodiments, the time indicator at the first position fades out and time indicator at the position on the display overlapping the at least portion of the obscured representation of the user interface of the application fades in to cause a visual cross-fade transition over time.
In some embodiments, displaying the first user interface (e.g., 1802, 1814) includes displaying the time indicator (e.g., 1802b, 1814b) at a first display size and at a first position on the display that is different from the position on the display overlapping the at least portion of the obscured representation of the application in the second mode. In some embodiments, displaying the time indicator (e.g., 1806b, 1814f) at the position on the display overlapping at least a portion of the obscured representation of the user interface of the application includes displaying an animation of: the time indicator expanding from the first display size (e.g., as in 1802b, 1814b) to a second display size (e.g., as in 1806b, 1814f) that is different from the first display size, and the time indicator translating from the first position on the display (e.g., as in 1802b, 1814b) to the position on the display (e.g., as in 1806b, 1814f) overlapping the at least portion of the obscured representation of the application. In some embodiments, the first position is adjacent to an edge of the display (e.g., a top edge) and translating to the position on the display overlapping the at least portion of the obscured representation of the application includes translating the time indicator away from the edge of the display.
In some embodiments, while the electronic device (e.g., 600) is in the second mode and the time indicator (e.g., 1806b, 1814f) is displayed at the position on the display overlapping at least portion of the obscured representation of the at least portion of the first user interface of the application (e.g., time overlay), the electronic device (e.g., 600) detects a first user input (e.g., a wrist raise gesture, a tap gesture on a touch-sensitive surface of the displays). In response to detecting the first user input, the electronic device (e.g., 600) ceases to display the time indicator (e.g., 1806b, 1814f) at the position on the display overlapping at least a portion of the obscured representation of the at least a portion of the first user interface of the application (e.g., ceasing to display the time indicator altogether; displaying the time indicator at another position).
In some embodiments, while the electronic device (e.g., 600) is in the second mode and the time indicator (e.g., 1806b, 1814f) is displayed at the position on the display overlapping the at least portion of the obscured representation of the at least portion of the first user interface of the application (e.g., time overlay), the electronic device (e.g., 600) detects a first user input (e.g., a wrist raise gesture, a tap gesture on a touch-sensitive surface of the displays). In response to detecting the first user input, the electronic device (e.g., 600) replaces, on the display, the second user interface (e.g., 1806, 1808,1816, a lower power consumption interface) including the obscured representation of the at least portion of the first user interface of the application with the first user interface (e.g., 1812). In some embodiments, in response to detecting the first user input, the electronic device ceases to obscure the user interface of the application.
In some embodiments, the obscured representation (e.g., 1802a, 1802c in
In some embodiments, one or more processes for the application are being processed by one or more processors of the electronic device (e.g., 600), while the electronic device (e.g., 600) is operating in the second mode. In some embodiments, the application is a timer application and one or more processes for the timer application continue to be processed such that the timer continues to run and can alert the user when a timing condition is met. In some embodiments, the application is an alarm clock application and one or more processes of the alarm clock application continue to be processed such that alarm times continue to be monitored and can alert the user when an alarm condition (e.g., alarm time is reached) is met.
In some embodiments, while displaying the second user interface (e.g., 1806, 1808, 1816, in the second mode), the electronic device (e.g., 600) detects that the electronic device has met a timeout criteria (e.g., a predetermined duration of time has lapsed since the electronic device is displaying the second user interface without receiving a qualifying user input, such as a wrist raise or a tap input on a touch-sensitive surface). In response to detecting that the electronic device has met the timeout criteria, the electronic device (e.g., 600) replaces display of the second user interface with display of a first watch face user interface (e.g., as shown in
In some embodiments, while displaying the first watch face user interface (e.g., as shown in
In some embodiments, the display, while displaying the first user interface of (e.g., 1802, 1814, a higher power consumption interface) the application in the first mode, has a first display brightness (e.g., average pixel luminance (APL), average lumen output, total lumen output, average illuminance, or total illuminance of the indicator on the display; brightness expressed in nits, lux, or lumens) and the display, while displaying the second user interface (e.g., 1806, 1808, 1816, a lower power consumption interface) including an obscured representation of at least a portion of the first user interface of the application (e.g., in the second mode), has a second display brightness that is lower than the first display brightness.
In some embodiments, the electronic device (e.g., 600) receives (e.g., via wireless communication) a notification. Subsequent to (e.g., in response to receiving) receiving the notification, the electronic device (e.g., 600) displays a first notification user interface (e.g., 1820) corresponding to the notification (e.g., including content received in the notification). While displaying the first notification user interface (e.g., 1820) corresponding to the notification, the electronic device (e.g., 600) detects a wrist down gesture (detecting that the user has moved their wrist that is wearing the electronic device from a raised position to a non-raised position). In response to detecting the wrist down gesture: the electronic device (e.g., 600) replaces, on the display, the notification user interface (e.g., 1820) with a second notification user interface (e.g., a lower power consumption interface) including an obscured representation of at least a portion of the first notification user interface (e.g., 1820) corresponding to the notification (e.g., a representation of the same graphical object including the same data with reduced sharpness (detail) or contrast (e.g., blurred); a representation resulting from applying a non-linear filter to the representation), and the electronic device (e.g., 600) displays a time indicator at a position on the display overlapping at least a portion of the obscured representation of the first notification user interface (e.g., time overlay). In some embodiments, obscuring includes blurring, scaling down/reducing in size, and/or dimming. Obscuring a representation of the first notification user interface provides the user with visual feedback that the device is operating in a lower power consumption mode while still providing the user with feedback about the notification user interface that was displayed when the device entered the lower power consumption mode. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
Note that details of the processes described above with respect to method 1900 (e.g.,
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.
The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to automatically display helpful or useful information (e.g., content of interest to a user) that may otherwise be cumbersome to access manually. Accordingly, use of such personal information data enables users to have convenient access to a wider variety of content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user's general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals.
The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.
Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of displaying private data such as calendar data or health-related data on user interfaces, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In another example, users can select not to provide private data such as calendar data of health-related data for automated display (e.g., delivery). In yet another example, users can select to limit the length of time private data such as calendar data or health-related data is maintained or entirely prohibit the development of data models or profiles derived from such data mood profile. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.
Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user's privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.
Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and displayed to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the device, or publicly available information.
This application claims priority to of U.S. Provisional Application No. 62/897,959, filed Sep. 9, 2019, entitled “TECHNIQUES FOR MANAGING DISPLAY USAGE,” the entire contents of which are hereby incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3148500 | Hayes | Sep 1964 | A |
| 4205628 | Null | Jun 1980 | A |
| 5124959 | Yamazaki et al. | Jun 1992 | A |
| 5208790 | Sato | May 1993 | A |
| 5455808 | Grupp et al. | Oct 1995 | A |
| 5500835 | Born | Mar 1996 | A |
| 5508979 | Eisenegger | Apr 1996 | A |
| 5659693 | Hansen et al. | Aug 1997 | A |
| 5825353 | Will | Oct 1998 | A |
| 5845257 | Fu et al. | Dec 1998 | A |
| 5892519 | Hirai | Apr 1999 | A |
| 5986655 | Chiu et al. | Nov 1999 | A |
| 5999195 | Santangeli | Dec 1999 | A |
| 6043818 | Nakano et al. | Mar 2000 | A |
| 6128012 | Seidensticker, Jr. et al. | Oct 2000 | A |
| 6160767 | Ho | Dec 2000 | A |
| 6279018 | Kudrolli et al. | Aug 2001 | B1 |
| 6359839 | Schenk et al. | Mar 2002 | B1 |
| 6441824 | Hertzfeld | Aug 2002 | B2 |
| 6449219 | Hepp et al. | Sep 2002 | B1 |
| 6452597 | Goldberg et al. | Sep 2002 | B1 |
| 6477117 | Narayanaswami et al. | Nov 2002 | B1 |
| 6496780 | Harris et al. | Dec 2002 | B1 |
| 6525997 | Narayanaswami et al. | Feb 2003 | B1 |
| 6539243 | Kimura et al. | Mar 2003 | B1 |
| 6539343 | Zhao et al. | Mar 2003 | B2 |
| 6549218 | Gershony et al. | Apr 2003 | B1 |
| 6556222 | Narayanaswami | Apr 2003 | B1 |
| 6683653 | Miyake et al. | Jan 2004 | B1 |
| 6690623 | Maano | Feb 2004 | B1 |
| 6728533 | Ishii | Apr 2004 | B2 |
| 6809724 | Shiraishi et al. | Oct 2004 | B1 |
| 6871076 | Samn | Mar 2005 | B2 |
| 7203380 | Chiu et al. | Apr 2007 | B2 |
| 7257254 | Tunney | Aug 2007 | B2 |
| 7302650 | Allyn et al. | Nov 2007 | B1 |
| 7378954 | Wendt | May 2008 | B2 |
| 7479949 | Jobs et al. | Jan 2009 | B2 |
| 7515509 | Klein | Apr 2009 | B2 |
| 7515903 | Cast | Apr 2009 | B1 |
| 7619615 | Donoghue | Nov 2009 | B1 |
| 7751285 | Cain | Jul 2010 | B1 |
| 7773460 | Holt | Aug 2010 | B2 |
| 7843769 | Ishida et al. | Nov 2010 | B2 |
| 7898542 | Yu et al. | Mar 2011 | B1 |
| 7907476 | Lee | Mar 2011 | B2 |
| 8238876 | Teng et al. | Aug 2012 | B2 |
| 8245143 | Yach et al. | Aug 2012 | B2 |
| 8462997 | Pettit et al. | Jun 2013 | B2 |
| 8595649 | Sherrard et al. | Nov 2013 | B2 |
| 8725842 | Al-nasser | May 2014 | B1 |
| 8847903 | Stokes et al. | Sep 2014 | B2 |
| 8854925 | Lee et al. | Oct 2014 | B1 |
| 8938394 | Faaborg et al. | Jan 2015 | B1 |
| 8948819 | Yun et al. | Feb 2015 | B2 |
| 8963894 | Klassen et al. | Feb 2015 | B2 |
| 9070092 | Chou et al. | Jun 2015 | B2 |
| 9082314 | Tsai | Jul 2015 | B2 |
| 9141270 | Stuart et al. | Sep 2015 | B1 |
| 9152211 | Gunn et al. | Oct 2015 | B2 |
| 9152212 | Gunn | Oct 2015 | B2 |
| 9173052 | Hauser et al. | Oct 2015 | B2 |
| 9197738 | Peev et al. | Nov 2015 | B2 |
| 9239605 | Nanda et al. | Jan 2016 | B1 |
| 9459781 | Wilson et al. | Oct 2016 | B2 |
| 9547425 | Wilson et al. | Jan 2017 | B2 |
| 9568891 | Adams et al. | Feb 2017 | B2 |
| 9582165 | Wilson et al. | Feb 2017 | B2 |
| 9600178 | Yun et al. | Mar 2017 | B2 |
| 9609230 | Bakshi et al. | Mar 2017 | B1 |
| 9635255 | Baldwin | Apr 2017 | B1 |
| 9753436 | Ely et al. | Sep 2017 | B2 |
| 9794397 | Min et al. | Oct 2017 | B2 |
| 10304347 | Wilson et al. | May 2019 | B2 |
| 10620590 | Guzman et al. | Apr 2020 | B1 |
| 10684592 | Chang et al. | Jun 2020 | B2 |
| 20020054066 | Kikinis et al. | May 2002 | A1 |
| 20020054541 | Hall | May 2002 | A1 |
| 20020059623 | Rodriguez et al. | May 2002 | A1 |
| 20020131331 | Molander | Sep 2002 | A1 |
| 20030002391 | Biggs | Jan 2003 | A1 |
| 20030027621 | Libby et al. | Feb 2003 | A1 |
| 20030067497 | Pichon | Apr 2003 | A1 |
| 20030164847 | Zaima et al. | Sep 2003 | A1 |
| 20030214885 | Powell et al. | Nov 2003 | A1 |
| 20030229900 | Reisman | Dec 2003 | A1 |
| 20040001105 | Chew et al. | Jan 2004 | A1 |
| 20040017733 | Sullivan | Jan 2004 | A1 |
| 20040021699 | Fildebrandt | Feb 2004 | A1 |
| 20040047244 | Iino et al. | Mar 2004 | A1 |
| 20040066710 | Yuen et al. | Apr 2004 | A1 |
| 20040075700 | Liu et al. | Apr 2004 | A1 |
| 20040168107 | Sharp et al. | Aug 2004 | A1 |
| 20040192332 | Samn | Sep 2004 | A1 |
| 20040218472 | Narayanaswami et al. | Nov 2004 | A1 |
| 20040225966 | Besharat et al. | Nov 2004 | A1 |
| 20040243547 | Chhatrapati et al. | Dec 2004 | A1 |
| 20040266491 | Howard et al. | Dec 2004 | A1 |
| 20050041667 | Miller et al. | Feb 2005 | A1 |
| 20050052446 | Plut | Mar 2005 | A1 |
| 20050094492 | Rosevear | May 2005 | A1 |
| 20050139852 | Chen et al. | Jun 2005 | A1 |
| 20050156873 | Walter et al. | Jul 2005 | A1 |
| 20050200611 | Goto et al. | Sep 2005 | A1 |
| 20050272462 | Okamoto | Dec 2005 | A1 |
| 20050278757 | Grossman et al. | Dec 2005 | A1 |
| 20060007785 | Fernandez et al. | Jan 2006 | A1 |
| 20060035628 | Miller et al. | Feb 2006 | A1 |
| 20060085765 | Peterson et al. | Apr 2006 | A1 |
| 20060092770 | Demas | May 2006 | A1 |
| 20060128419 | Shimizu et al. | Jun 2006 | A1 |
| 20060214935 | Boyd et al. | Sep 2006 | A1 |
| 20070004451 | Anderson | Jan 2007 | A1 |
| 20070006096 | Kim et al. | Jan 2007 | A1 |
| 20070055947 | Ostojic et al. | Mar 2007 | A1 |
| 20070057775 | O'reilly et al. | Mar 2007 | A1 |
| 20070094330 | Russell | Apr 2007 | A1 |
| 20070101279 | Chaudhri et al. | May 2007 | A1 |
| 20070146344 | Martin | Jun 2007 | A1 |
| 20070211042 | Kim et al. | Sep 2007 | A1 |
| 20070236475 | Wherry | Oct 2007 | A1 |
| 20070239754 | Schnitman | Oct 2007 | A1 |
| 20070261537 | Eronen et al. | Nov 2007 | A1 |
| 20070279190 | Lugt et al. | Dec 2007 | A1 |
| 20070287140 | Liebowitz | Dec 2007 | A1 |
| 20080082930 | Omernick et al. | Apr 2008 | A1 |
| 20080127268 | Bergeron et al. | May 2008 | A1 |
| 20080130421 | Akaiwa et al. | Jun 2008 | A1 |
| 20080150959 | Marui | Jun 2008 | A1 |
| 20080151700 | Inoue et al. | Jun 2008 | A1 |
| 20080167834 | Herz | Jul 2008 | A1 |
| 20080168396 | Matas et al. | Jul 2008 | A1 |
| 20080186808 | Lee | Aug 2008 | A1 |
| 20080192021 | Lim et al. | Aug 2008 | A1 |
| 20080201647 | Lagerstedt et al. | Aug 2008 | A1 |
| 20080215240 | Howard et al. | Sep 2008 | A1 |
| 20080224988 | Whang | Sep 2008 | A1 |
| 20080246778 | Ham et al. | Oct 2008 | A1 |
| 20080270934 | Firebaugh et al. | Oct 2008 | A1 |
| 20090012988 | Brown | Jan 2009 | A1 |
| 20090051327 | Bohne | Feb 2009 | A1 |
| 20090058821 | Chaudhri et al. | Mar 2009 | A1 |
| 20090059730 | Lyons et al. | Mar 2009 | A1 |
| 20090066533 | Park et al. | Mar 2009 | A1 |
| 20090143114 | Vargas et al. | Jun 2009 | A1 |
| 20090146962 | Ahonen et al. | Jun 2009 | A1 |
| 20090158173 | Palahnuk et al. | Jun 2009 | A1 |
| 20090164923 | Ovi | Jun 2009 | A1 |
| 20090178007 | Matas et al. | Jul 2009 | A1 |
| 20090178008 | Herz et al. | Jul 2009 | A1 |
| 20090199130 | Tsern et al. | Aug 2009 | A1 |
| 20090249247 | Tseng et al. | Oct 2009 | A1 |
| 20090259958 | Ban | Oct 2009 | A1 |
| 20090264116 | Thompson | Oct 2009 | A1 |
| 20090279392 | Scott et al. | Nov 2009 | A1 |
| 20090284389 | Klassen | Nov 2009 | A1 |
| 20090287470 | Farnsworth et al. | Nov 2009 | A1 |
| 20090300146 | Park et al. | Dec 2009 | A1 |
| 20090305732 | Marcellino et al. | Dec 2009 | A1 |
| 20090312059 | Pratt et al. | Dec 2009 | A1 |
| 20090319467 | Berg et al. | Dec 2009 | A1 |
| 20090327886 | Whytock et al. | Dec 2009 | A1 |
| 20100026640 | Kim et al. | Feb 2010 | A1 |
| 20100060586 | Pisula et al. | Mar 2010 | A1 |
| 20100064255 | Rottler et al. | Mar 2010 | A1 |
| 20100069035 | Johnson | Mar 2010 | A1 |
| 20100081473 | Chatterjee et al. | Apr 2010 | A1 |
| 20100085203 | Kahn et al. | Apr 2010 | A1 |
| 20100110082 | Myrick et al. | May 2010 | A1 |
| 20100124152 | Lee | May 2010 | A1 |
| 20100146437 | Woodcock et al. | Jun 2010 | A1 |
| 20100156833 | Kim et al. | Jun 2010 | A1 |
| 20100157742 | Relyea et al. | Jun 2010 | A1 |
| 20100167712 | Stallings et al. | Jul 2010 | A1 |
| 20100205563 | Haapsaari et al. | Aug 2010 | A1 |
| 20100217657 | Gazdzinski | Aug 2010 | A1 |
| 20100223563 | Green | Sep 2010 | A1 |
| 20100225495 | Marui | Sep 2010 | A1 |
| 20100226213 | Drugge | Sep 2010 | A1 |
| 20100235726 | Ording et al. | Sep 2010 | A1 |
| 20100243516 | Martin et al. | Sep 2010 | A1 |
| 20100281374 | Schulz et al. | Nov 2010 | A1 |
| 20110003616 | Gorsica et al. | Jan 2011 | A1 |
| 20110003621 | Atsumi | Jan 2011 | A1 |
| 20110003665 | Burton et al. | Jan 2011 | A1 |
| 20110004835 | Yanchar et al. | Jan 2011 | A1 |
| 20110025719 | Yanase | Feb 2011 | A1 |
| 20110029870 | May et al. | Feb 2011 | A1 |
| 20110061010 | Wasko et al. | Mar 2011 | A1 |
| 20110070924 | Kim | Mar 2011 | A1 |
| 20110076992 | Chou et al. | Mar 2011 | A1 |
| 20110078624 | Missig et al. | Mar 2011 | A1 |
| 20110083111 | Forutanpour et al. | Apr 2011 | A1 |
| 20110098928 | Hoffman et al. | Apr 2011 | A1 |
| 20110109540 | Milne et al. | May 2011 | A1 |
| 20110117902 | Chang et al. | May 2011 | A1 |
| 20110128311 | Wakatsuki et al. | Jun 2011 | A1 |
| 20110138329 | Wells et al. | Jun 2011 | A1 |
| 20110151415 | Darling | Jun 2011 | A1 |
| 20110157046 | Lee et al. | Jun 2011 | A1 |
| 20110166777 | Chavakula | Jul 2011 | A1 |
| 20110173221 | Ahiakpor et al. | Jul 2011 | A1 |
| 20110179372 | Moore et al. | Jul 2011 | A1 |
| 20110182151 | Geyer et al. | Jul 2011 | A1 |
| 20110191661 | Phillips et al. | Aug 2011 | A1 |
| 20110193878 | Seo et al. | Aug 2011 | A1 |
| 20110197165 | Filippov et al. | Aug 2011 | A1 |
| 20110202883 | Oh et al. | Aug 2011 | A1 |
| 20110205851 | Harris | Aug 2011 | A1 |
| 20110218765 | Rogers | Sep 2011 | A1 |
| 20110230986 | Lafortune et al. | Sep 2011 | A1 |
| 20110234152 | Frossen et al. | Sep 2011 | A1 |
| 20110261079 | Ingrassia et al. | Oct 2011 | A1 |
| 20110281342 | Porsch et al. | Nov 2011 | A1 |
| 20110296324 | Goossens et al. | Dec 2011 | A1 |
| 20110306421 | Nishimoto et al. | Dec 2011 | A1 |
| 20110316858 | Shen et al. | Dec 2011 | A1 |
| 20110320938 | Schorsch | Dec 2011 | A1 |
| 20120001922 | Escher et al. | Jan 2012 | A1 |
| 20120028707 | Raitt et al. | Feb 2012 | A1 |
| 20120059787 | Brown et al. | Mar 2012 | A1 |
| 20120062470 | Chang | Mar 2012 | A1 |
| 20120079375 | Ogino et al. | Mar 2012 | A1 |
| 20120084729 | Lin | Apr 2012 | A1 |
| 20120092383 | Hysek et al. | Apr 2012 | A1 |
| 20120098639 | Ijas | Apr 2012 | A1 |
| 20120110438 | Peraza et al. | May 2012 | A1 |
| 20120116550 | Hoffman et al. | May 2012 | A1 |
| 20120117507 | Tseng et al. | May 2012 | A1 |
| 20120124499 | Tsai | May 2012 | A1 |
| 20120154156 | Kuntzel | Jun 2012 | A1 |
| 20120182226 | Tuli | Jul 2012 | A1 |
| 20120197523 | Kirsch | Aug 2012 | A1 |
| 20120231849 | Yamashita | Sep 2012 | A1 |
| 20120243735 | Wu | Sep 2012 | A1 |
| 20120254804 | Sheha et al. | Oct 2012 | A1 |
| 20120254810 | Heck et al. | Oct 2012 | A1 |
| 20120288139 | Singhar | Nov 2012 | A1 |
| 20120297346 | Hoffknecht et al. | Nov 2012 | A1 |
| 20120304084 | Kim et al. | Nov 2012 | A1 |
| 20120319984 | Borovsky et al. | Dec 2012 | A1 |
| 20120324390 | Tao | Dec 2012 | A1 |
| 20130007665 | Chaudhri et al. | Jan 2013 | A1 |
| 20130021236 | Bender | Jan 2013 | A1 |
| 20130030892 | Liu et al. | Jan 2013 | A1 |
| 20130044072 | Kobayashi et al. | Feb 2013 | A1 |
| 20130050263 | Khoe et al. | Feb 2013 | A1 |
| 20130055147 | Vasudev et al. | Feb 2013 | A1 |
| 20130057566 | Kriese et al. | Mar 2013 | A1 |
| 20130063084 | Tilvis et al. | Mar 2013 | A1 |
| 20130063383 | Anderssonreimer et al. | Mar 2013 | A1 |
| 20130069893 | Brinda et al. | Mar 2013 | A1 |
| 20130076757 | Pritting | Mar 2013 | A1 |
| 20130082965 | Wada et al. | Apr 2013 | A1 |
| 20130107674 | Gossweiler et al. | May 2013 | A1 |
| 20130111579 | Newman et al. | May 2013 | A1 |
| 20130116967 | Akcasu et al. | May 2013 | A1 |
| 20130132888 | Tijssen | May 2013 | A1 |
| 20130141371 | Hallford et al. | Jun 2013 | A1 |
| 20130147825 | Martin et al. | Jun 2013 | A1 |
| 20130162611 | Lim et al. | Jun 2013 | A1 |
| 20130176293 | Pantfoerder | Jul 2013 | A1 |
| 20130185813 | Shim et al. | Jul 2013 | A1 |
| 20130191785 | Rampson et al. | Jul 2013 | A1 |
| 20130205194 | Decker et al. | Aug 2013 | A1 |
| 20130215044 | Ahn et al. | Aug 2013 | A1 |
| 20130222271 | Alberth et al. | Aug 2013 | A1 |
| 20130232443 | Ryu et al. | Sep 2013 | A1 |
| 20130239060 | Kang et al. | Sep 2013 | A1 |
| 20130254705 | Mooring et al. | Sep 2013 | A1 |
| 20130316763 | Kader | Nov 2013 | A1 |
| 20130318437 | Jung et al. | Nov 2013 | A1 |
| 20130318466 | Estrada et al. | Nov 2013 | A1 |
| 20130326418 | Utsuki et al. | Dec 2013 | A1 |
| 20130345980 | Van Os et al. | Dec 2013 | A1 |
| 20140013414 | Bruck | Jan 2014 | A1 |
| 20140022183 | Ayoub et al. | Jan 2014 | A1 |
| 20140037109 | Ban | Feb 2014 | A1 |
| 20140047525 | Bonhoff | Feb 2014 | A1 |
| 20140055495 | Kim et al. | Feb 2014 | A1 |
| 20140059493 | Kim | Feb 2014 | A1 |
| 20140074570 | Hope et al. | Mar 2014 | A1 |
| 20140082533 | Kelley | Mar 2014 | A1 |
| 20140094224 | Lozovoy | Apr 2014 | A1 |
| 20140101169 | Kurata et al. | Apr 2014 | A1 |
| 20140126336 | Goeller et al. | May 2014 | A1 |
| 20140129959 | Battles et al. | May 2014 | A1 |
| 20140139454 | Mistry et al. | May 2014 | A1 |
| 20140139637 | Mistry et al. | May 2014 | A1 |
| 20140143678 | Mistry et al. | May 2014 | A1 |
| 20140143737 | Mistry et al. | May 2014 | A1 |
| 20140155031 | Lee et al. | Jun 2014 | A1 |
| 20140157189 | Morita | Jun 2014 | A1 |
| 20140157321 | Kurita | Jun 2014 | A1 |
| 20140173439 | Gutierrez et al. | Jun 2014 | A1 |
| 20140189578 | Shuttleworth et al. | Jul 2014 | A1 |
| 20140189584 | Weng et al. | Jul 2014 | A1 |
| 20140192244 | Ishihara et al. | Jul 2014 | A1 |
| 20140200691 | Lee et al. | Jul 2014 | A1 |
| 20140201655 | Mahaffey et al. | Jul 2014 | A1 |
| 20140229752 | Lee | Aug 2014 | A1 |
| 20140244165 | Bells | Aug 2014 | A1 |
| 20140245161 | Yuen et al. | Aug 2014 | A1 |
| 20140245177 | Maklouf | Aug 2014 | A1 |
| 20140250374 | Ohki et al. | Sep 2014 | A1 |
| 20140250391 | Jong et al. | Sep 2014 | A1 |
| 20140253487 | Bezinge et al. | Sep 2014 | A1 |
| 20140256298 | Moss et al. | Sep 2014 | A1 |
| 20140258935 | Nishida et al. | Sep 2014 | A1 |
| 20140267303 | Larkin et al. | Sep 2014 | A1 |
| 20140276244 | Kamyar | Sep 2014 | A1 |
| 20140282103 | Crandall | Sep 2014 | A1 |
| 20140282153 | Christiansen et al. | Sep 2014 | A1 |
| 20140282254 | Feiereisen et al. | Sep 2014 | A1 |
| 20140285699 | Kato | Sep 2014 | A1 |
| 20140289660 | Min | Sep 2014 | A1 |
| 20140293755 | Geiser et al. | Oct 2014 | A1 |
| 20140304664 | Lee et al. | Oct 2014 | A1 |
| 20140310618 | Venkatesh | Oct 2014 | A1 |
| 20140317543 | Kim | Oct 2014 | A1 |
| 20140320434 | Pantel | Oct 2014 | A1 |
| 20140325384 | Kobayashi | Oct 2014 | A1 |
| 20140325408 | Leppanen et al. | Oct 2014 | A1 |
| 20140328151 | Serber | Nov 2014 | A1 |
| 20140344723 | Malik et al. | Nov 2014 | A1 |
| 20140347275 | Kim et al. | Nov 2014 | A1 |
| 20140359477 | Chen | Dec 2014 | A1 |
| 20140362105 | Kocienda et al. | Dec 2014 | A1 |
| 20140380229 | Volodin et al. | Dec 2014 | A1 |
| 20150002735 | Moskovchenko | Jan 2015 | A1 |
| 20150022438 | Hong | Jan 2015 | A1 |
| 20150055197 | Romanoff et al. | Feb 2015 | A1 |
| 20150058651 | Choi et al. | Feb 2015 | A1 |
| 20150062130 | Ho | Mar 2015 | A1 |
| 20150071043 | Kubota | Mar 2015 | A1 |
| 20150083970 | Koh et al. | Mar 2015 | A1 |
| 20150100621 | Pan | Apr 2015 | A1 |
| 20150105125 | Min et al. | Apr 2015 | A1 |
| 20150106752 | Yang | Apr 2015 | A1 |
| 20150111558 | Yang | Apr 2015 | A1 |
| 20150113468 | Clark | Apr 2015 | A1 |
| 20150117162 | Tsai | Apr 2015 | A1 |
| 20150143234 | Norris, III | May 2015 | A1 |
| 20150160806 | Fey et al. | Jun 2015 | A1 |
| 20150160812 | Yuan et al. | Jun 2015 | A1 |
| 20150160856 | Jang et al. | Jun 2015 | A1 |
| 20150172438 | Yang | Jun 2015 | A1 |
| 20150185703 | Tanaka | Jul 2015 | A1 |
| 20150185995 | Shoemaker et al. | Jul 2015 | A1 |
| 20150194137 | Wyatt | Jul 2015 | A1 |
| 20150205509 | Scriven et al. | Jul 2015 | A1 |
| 20150207922 | Kobayashi et al. | Jul 2015 | A1 |
| 20150217163 | Amis et al. | Aug 2015 | A1 |
| 20150248235 | Offenberg et al. | Sep 2015 | A1 |
| 20150254875 | Zhang | Sep 2015 | A1 |
| 20150262548 | Lin | Sep 2015 | A1 |
| 20150277545 | Flowers et al. | Oct 2015 | A1 |
| 20150286372 | Swindell et al. | Oct 2015 | A1 |
| 20150286391 | Jacobs et al. | Oct 2015 | A1 |
| 20150301506 | Koumaiha | Oct 2015 | A1 |
| 20150301608 | Nagaraju et al. | Oct 2015 | A1 |
| 20150346694 | Hoobler et al. | Dec 2015 | A1 |
| 20150355830 | Chaudhri et al. | Dec 2015 | A1 |
| 20150365892 | Ma et al. | Dec 2015 | A1 |
| 20150379476 | Chaudhri et al. | Dec 2015 | A1 |
| 20160004345 | Imana | Jan 2016 | A1 |
| 20160004393 | Faaborg et al. | Jan 2016 | A1 |
| 20160018872 | Tu et al. | Jan 2016 | A1 |
| 20160022202 | Peterson et al. | Jan 2016 | A1 |
| 20160027420 | Eronen | Jan 2016 | A1 |
| 20160034133 | Wilson et al. | Feb 2016 | A1 |
| 20160034148 | Wilson et al. | Feb 2016 | A1 |
| 20160034152 | Wilson et al. | Feb 2016 | A1 |
| 20160034166 | Wilson et al. | Feb 2016 | A1 |
| 20160034167 | Wilson et al. | Feb 2016 | A1 |
| 20160044091 | Doumet | Feb 2016 | A1 |
| 20160048283 | Yang et al. | Feb 2016 | A1 |
| 20160054710 | Jo et al. | Feb 2016 | A1 |
| 20160054892 | Kim et al. | Feb 2016 | A1 |
| 20160058375 | Rothkopf | Mar 2016 | A1 |
| 20160062450 | Han | Mar 2016 | A1 |
| 20160062540 | Yang et al. | Mar 2016 | A1 |
| 20160062570 | Dascola et al. | Mar 2016 | A1 |
| 20160062589 | Wan et al. | Mar 2016 | A1 |
| 20160077718 | Kwon et al. | Mar 2016 | A1 |
| 20160085397 | Jain | Mar 2016 | A1 |
| 20160091867 | Mansour et al. | Mar 2016 | A1 |
| 20160098137 | Kim et al. | Apr 2016 | A1 |
| 20160134737 | Pulletikurty | May 2016 | A1 |
| 20160162112 | Lee et al. | Jun 2016 | A1 |
| 20160188179 | Roh | Jun 2016 | A1 |
| 20160188181 | Smith | Jun 2016 | A1 |
| 20160205241 | Atsumi | Jul 2016 | A1 |
| 20160205244 | Dvortsov | Jul 2016 | A1 |
| 20160205267 | Vaughn et al. | Jul 2016 | A1 |
| 20160261675 | Block et al. | Sep 2016 | A1 |
| 20160266548 | Akiyama | Sep 2016 | A1 |
| 20160283094 | Choi | Sep 2016 | A1 |
| 20160320756 | Lee et al. | Nov 2016 | A1 |
| 20160327911 | Eim et al. | Nov 2016 | A1 |
| 20160327915 | Katzer et al. | Nov 2016 | A1 |
| 20160342327 | Chi et al. | Nov 2016 | A1 |
| 20160357354 | Chen et al. | Dec 2016 | A1 |
| 20160358311 | Chen et al. | Dec 2016 | A1 |
| 20170046024 | Dascola et al. | Feb 2017 | A1 |
| 20170053542 | Wilson et al. | Feb 2017 | A1 |
| 20170061934 | Shin | Mar 2017 | A1 |
| 20170068407 | Wilson et al. | Mar 2017 | A1 |
| 20170070716 | Park et al. | Mar 2017 | A1 |
| 20170075305 | Ryu et al. | Mar 2017 | A1 |
| 20170075563 | Bauer et al. | Mar 2017 | A1 |
| 20170109011 | Jiang | Apr 2017 | A1 |
| 20170123571 | Huang et al. | May 2017 | A1 |
| 20170123603 | Chang | May 2017 | A1 |
| 20170123640 | Wilson et al. | May 2017 | A1 |
| 20170134321 | Ushio et al. | May 2017 | A1 |
| 20170160898 | Lee et al. | Jun 2017 | A1 |
| 20170269715 | Kim et al. | Sep 2017 | A1 |
| 20170269792 | Xu et al. | Sep 2017 | A1 |
| 20170277136 | Minami et al. | Sep 2017 | A1 |
| 20170287312 | Schofield et al. | Oct 2017 | A1 |
| 20170300013 | Satou et al. | Oct 2017 | A1 |
| 20170322658 | Lee et al. | Nov 2017 | A1 |
| 20170325196 | Cho et al. | Nov 2017 | A1 |
| 20170357329 | Park et al. | Dec 2017 | A1 |
| 20170357358 | Teutschler et al. | Dec 2017 | A1 |
| 20170357426 | Wilson et al. | Dec 2017 | A1 |
| 20170357427 | Wilson | Dec 2017 | A1 |
| 20170358276 | Mese et al. | Dec 2017 | A1 |
| 20180011450 | Stackowski | Jan 2018 | A1 |
| 20180024619 | Kasuo et al. | Jan 2018 | A1 |
| 20180033311 | Berggren | Feb 2018 | A1 |
| 20180052428 | Abramov | Feb 2018 | A1 |
| 20180067633 | Wilson et al. | Mar 2018 | A1 |
| 20180081515 | Block et al. | Mar 2018 | A1 |
| 20180088797 | Mcatee | Mar 2018 | A1 |
| 20180136810 | Martin et al. | May 2018 | A1 |
| 20180150212 | Chen et al. | May 2018 | A1 |
| 20180275739 | Minami et al. | Sep 2018 | A1 |
| 20180329587 | Ko et al. | Nov 2018 | A1 |
| 20180336866 | Triverio et al. | Nov 2018 | A1 |
| 20180343023 | Park et al. | Nov 2018 | A1 |
| 20180374429 | Nakamura | Dec 2018 | A1 |
| 20190069244 | Jeon et al. | Feb 2019 | A1 |
| 20190121300 | Peterson et al. | Apr 2019 | A1 |
| 20190212707 | Minami et al. | Jul 2019 | A1 |
| 20190213037 | Kim et al. | Jul 2019 | A1 |
| 20190250813 | Block et al. | Aug 2019 | A1 |
| 20190279520 | Wilson et al. | Sep 2019 | A1 |
| 20190281154 | Choi et al. | Sep 2019 | A1 |
| 20190339860 | Chen et al. | Nov 2019 | A1 |
| 20200050332 | Yang et al. | Feb 2020 | A1 |
| 20200125037 | Jo et al. | Apr 2020 | A1 |
| 20200133206 | Jo et al. | Apr 2020 | A1 |
| 20200249632 | Olwal et al. | Aug 2020 | A1 |
| 20200279539 | Triverio et al. | Sep 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 2010249319 | Jun 2012 | AU |
| 2015101019 | Sep 2015 | AU |
| 2781636 | Jul 2010 | CA |
| 2986980 | May 2019 | CA |
| 707412 | Jun 2014 | CH |
| 1337638 | Feb 2002 | CN |
| 1397904 | Feb 2003 | CN |
| 1536511 | Oct 2004 | CN |
| 1870796 | Nov 2006 | CN |
| 1932590 | Mar 2007 | CN |
| 1997957 | Jul 2007 | CN |
| 101273324 | Sep 2008 | CN |
| 101382438 | Mar 2009 | CN |
| 101432722 | May 2009 | CN |
| 101505320 | Aug 2009 | CN |
| 101627349 | Jan 2010 | CN |
| 101702112 | May 2010 | CN |
| 101819486 | Sep 2010 | CN |
| 101981987 | Feb 2011 | CN |
| 102687176 | Sep 2012 | CN |
| 103019567 | Apr 2013 | CN |
| 103281419 | Sep 2013 | CN |
| 103399480 | Nov 2013 | CN |
| 103562832 | Feb 2014 | CN |
| 103607660 | Feb 2014 | CN |
| 103853328 | Jun 2014 | CN |
| 103902165 | Jul 2014 | CN |
| 104501043 | Apr 2015 | CN |
| 104978904 | Oct 2015 | CN |
| 105260049 | Jan 2016 | CN |
| 105388966 | Mar 2016 | CN |
| 105389107 | Mar 2016 | CN |
| 105430154 | Mar 2016 | CN |
| 105677179 | Jun 2016 | CN |
| 205608658 | Sep 2016 | CN |
| 106056848 | Oct 2016 | CN |
| 0831629 | Mar 1998 | EP |
| 1659504 | May 2006 | EP |
| 1674889 | Jun 2006 | EP |
| 1674977 | Jun 2006 | EP |
| 1750242 | Feb 2007 | EP |
| 1832969 | Sep 2007 | EP |
| 1855170 | Nov 2007 | EP |
| 2120115 | Nov 2009 | EP |
| 2194508 | Jun 2010 | EP |
| 2204702 | Jul 2010 | EP |
| 2290922 | Mar 2011 | EP |
| 2312512 | Apr 2011 | EP |
| 2413577 | Feb 2012 | EP |
| 2423810 | Feb 2012 | EP |
| 2426902 | Mar 2012 | EP |
| 2565602 | Mar 2013 | EP |
| 2600215 | Jun 2013 | EP |
| 2738640 | Jun 2014 | EP |
| 2942932 | Nov 2015 | EP |
| 3056949 | Aug 2016 | EP |
| 3376342 | Sep 2018 | EP |
| 3401770 | Nov 2018 | EP |
| 2475669 | Jun 2011 | GB |
| 8-110955 | Apr 1996 | JP |
| 9-251084 | Sep 1997 | JP |
| 11-160470 | Jun 1999 | JP |
| 11-232013 | Aug 1999 | JP |
| 2001-318852 | Nov 2001 | JP |
| 2002-507718 | Mar 2002 | JP |
| 2002-271451 | Sep 2002 | JP |
| 2003-196593 | Jul 2003 | JP |
| 2003-296246 | Oct 2003 | JP |
| 2005-339017 | Dec 2005 | JP |
| 2006-287949 | Oct 2006 | JP |
| 2009-147889 | Jul 2009 | JP |
| 2010-124181 | Jun 2010 | JP |
| 2010-257051 | Nov 2010 | JP |
| 3168099 | Jun 2011 | JP |
| 2012-53642 | Mar 2012 | JP |
| 2012-505478 | Mar 2012 | JP |
| 2012-147432 | Aug 2012 | JP |
| 2012-517630 | Aug 2012 | JP |
| 2012-203832 | Oct 2012 | JP |
| 2012-531607 | Dec 2012 | JP |
| 2014-123197 | Jul 2014 | JP |
| 2014-519126 | Aug 2014 | JP |
| 2014-216868 | Nov 2014 | JP |
| 2015-210587 | Nov 2015 | JP |
| 20-0425314 | Sep 2006 | KR |
| 10-2008-0058246 | Jun 2008 | KR |
| 10-2013-0109466 | Oct 2013 | KR |
| 10-2014-0025552 | Mar 2014 | KR |
| 10-2014-0064687 | May 2014 | KR |
| 10-2015-0038711 | Apr 2015 | KR |
| 10-2015-0081140 | Jul 2015 | KR |
| 10-2017-0076452 | Jul 2017 | KR |
| 10-2017-0082698 | Jul 2017 | KR |
| 498240 | Aug 2002 | TW |
| 546942 | Aug 2003 | TW |
| 200512616 | Apr 2005 | TW |
| 200850058 | Dec 2008 | TW |
| 200915698 | Apr 2009 | TW |
| I348803 | Sep 2011 | TW |
| 201232486 | Aug 2012 | TW |
| 201419115 | May 2014 | TW |
| 200171433 | Sep 2001 | WO |
| 2002054157 | Jul 2002 | WO |
| 2006012343 | Feb 2006 | WO |
| 2006112641 | Oct 2006 | WO |
| 2007018881 | Feb 2007 | WO |
| 2007043222 | Apr 2007 | WO |
| 2007124364 | Nov 2007 | WO |
| 2009146857 | Dec 2009 | WO |
| 2010017627 | Feb 2010 | WO |
| 2011000893 | Jan 2011 | WO |
| 2012021507 | Feb 2012 | WO |
| 2012161434 | Nov 2012 | WO |
| 2012170446 | Dec 2012 | WO |
| 2013051048 | Apr 2013 | WO |
| 2013093558 | Jun 2013 | WO |
| 2013136548 | Sep 2013 | WO |
| 2013169842 | Nov 2013 | WO |
| 2013169849 | Nov 2013 | WO |
| 2013169875 | Nov 2013 | WO |
| 2013169882 | Nov 2013 | WO |
| 2014024366 | Feb 2014 | WO |
| 2014078114 | May 2014 | WO |
| 2014105278 | Jul 2014 | WO |
| 2014189197 | Nov 2014 | WO |
| 2015034965 | Mar 2015 | WO |
| 2015163536 | Oct 2015 | WO |
| 2016022203 | Feb 2016 | WO |
| 2016022205 | Feb 2016 | WO |
| 2016022496 | Feb 2016 | WO |
| 2016036427 | Mar 2016 | WO |
| 2016036472 | Mar 2016 | WO |
| 2016039587 | Mar 2016 | WO |
| 2016099097 | Jun 2016 | WO |
| 2016144563 | Sep 2016 | WO |
| 2017000522 | Jan 2017 | WO |
| 2017027526 | Feb 2017 | WO |
| Entry |
|---|
| Advisory Action received for U.S. Appl. No. 14/815,898, dated Aug. 30, 2016, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/841,606, dated Feb. 28, 2019, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/846,511, dated Sep. 19, 2018, 8 pages. |
| “AdyClock—Night Alarm Clock”, App for android, Google play store page: https://web.archive.org/web/20130924223153/https://play.google.com/store/apps/details?id=com.adyclock&hl=en, Sep. 24, 2013, 2 pages. |
| Airshow, “Airshow App for Mobile Devices”, 2012, 4 pages. |
| Android Central, “BeWeather weather app for Android”, Available online at: https://www.youtube.com/watch?v=G2EY2K-XkSl, Sep. 1, 2011, 1 page. |
| Android Central, “Changing the Watchface on your Android Wear device”, Retrieved from: https://www.youtube.com/watch?v=YYwFe2K_qil, Jul. 2, 2014, 4 pages. |
| APK Root, “Butterfly 3D Live Wallpaper 1.0 APK”, Available at: http://net-suckga-ilauncher2.apk-dl.com/butterfly-3d-live-wallpaper, Feb. 26, 2013, 7 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/554,204, dated Oct. 11, 2019, 5 pages. |
| Avdonin, Nikita, “Astroviewer 3D”, Available at: https://www.youtube.comjwatch?v=zY0tslx3JHY/, Nov. 5, 2013, 2 pages. |
| Bogdanov, Alexei, “SKMEI 1016”, XP054977588, Available online at URL: https://www.youtube.com/watch?v=E4q4Fug05Fw>, Jun. 21, 2014, 2 pages {See Communication under 37 CFR § 1.98(a) (3)}. |
| Bond, John-Michael, “The 4 Best Free Flashlight Apps for Android and iOS”, Online Available at: https://www.dailydot.com/debug/best-free-flashlight-apps/, Apr. 2, 2017, 8 pages. |
| Castellini, Rick, “Google Earth”, Retrieved from: https://www.youtube.com/watch?v=bgjMSBXsFZQ>, Feb. 12, 2013, 3 pages. |
| Certificate of Examination received for Australian Patent Application No. 2018101947, dated Feb. 18, 2019, 2 pages. |
| Clark, Josh, “Designing Great iPhone Apps”, O'Reilly Japan Co., O'Reilly Tim, vol. 1, May 24, 2012, 5 pages {See Communication under 37 CFR § 1.98(a) (3)}. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/815,879, dated Jul. 13, 2017, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/815,879, dated Jul. 28, 2017, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/815,879, dated Sep. 21, 2017, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/183,663, dated Feb. 25, 2019, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/183,663, dated Mar. 27, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/798,257, dated Aug. 26, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/798,257, dated Jul. 9, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/798,257, dated Jun. 12, 2019, 2 pages. |
| Cyr, Jim, “Apple Watch—Customize Modular Watch Face”, Available online at: https://www.youtube.com/watch?v=02W93HbKlK8, May 13, 2015, 2 pages. |
| Decision on Acceptance received for Australian Patent Application No. 2015298710, dated Jul. 19, 2019, 18 pages. |
| Decision on Opposition received for Australian Patent Application No. 2015298710, dated Aug. 9, 2019, 4 pages. |
| Decision on Opposition received for Australian Patent Application No. 2015298710, dated Aug. 20, 2018, 20 pages. |
| Decision to Grant received for Danish Patent Application No. PA201770387, dated Aug. 30, 2018, 2 pages. |
| Decision to Grant Received for Danish Patent Application No. PA201770397, dated Feb. 6, 2018, 2 pages. |
| Decision to Refuse received for European Patent Application No. 15730924.6, dated Mar. 15, 2019, 12 pages. |
| “Deluxe Moon-Guide”, available online at: https://web.archive.org/web/20130520161057/http://www.lifewaresolutions.com/deluxe_moon_guide_ip.html, May 20, 2013, 5 pages. |
| “Digital alarm clock app for Android”, Goggle play store digital alarm clock description page, Mar. 25, 2015, 3 pages. |
| Disrapptive, “Flashlight for Android Wear”, Online Available at: https://www.youtube.corn/watch?v=HVNxxUl57BM, Jul. 10, 2014, 5 pages. |
| EBPMAN Tech Reviews, “LG G3 Tips: How to customize the clock face”, Available online at: https://www.youtube.com/watch?v=evraMWFb1fY, Jul. 25, 2014, 1 page. |
| European Search Report received for European Patent Application No. 17206177.2, dated Apr. 30, 2018, 4 pages. |
| Evgenyevich, Sergey, “Earth & Moon in HD Gyro 3D”, Available at https://www.youtube.com/watch?v=IRwNcaSYrls/, Dec. 1, 2013, 2 pages. |
| Extended European Search Report received for European Patent Application No. 16762356.0, dated Nov. 9, 2018, 10 pages. |
| Extended European Search Report received for European Patent Application No. 16837432.0, dated Mar. 11, 2019, 10 pages. |
| Extended European Search Report received for European Patent Application No. 17853656.1, dated Jul. 3, 2019, 9 pages. |
| Extended European Search Report received for European Patent Application No. 18172554.0, dated Aug. 3, 2018, 10 pages. |
| Feist, Jonathan, “Android customization—how to create a custom clock widget using Zooper Widget”, Available Online at: https://www.androidauthority.com/zooper-widget-clock-366476/, May 15, 2014, 10 pages. |
| Feldman, Ari, “Excerpts from: Designing Arcade Computer Game Graphics”, Available online at: http://www.phatcode.net/res/269/files/dacgg.pdf, Jan. 1, 2001, 35 pages. |
| Final Office Action received for U.S. Appl. No. 14/815,890, dated Feb. 26, 2018, 20 pages. |
| Final Office Action received for U.S. Appl. No. 14/815,890, dated May 14, 2019, 22 pages. |
| Final Office Action received for U.S. Appl. No. 14/815,890, dated Nov. 21, 2016, 18 pages. |
| Final Office Action received for U.S. Appl. No. 14/815,898, dated Jun. 9, 2016, 19 pages. |
| Final Office Action received for U.S. Appl. No. 14/821,667, dated Apr. 26, 2018, 13 pages. |
| Final Office Action received for U.S. Appl. No. 14/841,606, dated Sep. 7, 2018, 34 pages. |
| Final Office Action received for U.S. Appl. No. 14/846,511 dated May 10, 2018, 21 pages. |
| Final Office Action received for U.S. Appl. No. 14/846,511, dated Jun. 5, 2019, 24 pages. |
| Final Office Action received for U.S. Appl. No. 15/713,544, dated Jul. 19, 2019, 20 pages. |
| Final Office Action received for U.S. Appl. No. 15/791,829, dated Mar. 7, 2019, 23 pages. |
| Final Office Action received for U.S. Appl. No. 15/798,235, dated Oct. 9, 2018, 45 pages. |
| Final Office Action received for U.S. Appl. No. 15/881,544, dated Jan. 29, 2019, 14 pages. |
| Final Office Action received for U.S. Appl. No. 14/815,879, dated Mar. 24, 2016, 46 pages. |
| First Action Interview received for U.S. Appl. No. 14/815,890, dated Aug. 12, 2016, 3 pages. |
| “Fitbit surge Fitness Watch”, Manual version 1.0, May 7, 2015, 48 pages. |
| Fuchphone Extras, “LG G Watch—Designs | Watch Faces”, Available online at: https://www.youtube.com/watch?v=yqxzqdi_MSE, Jul. 27, 2014, 1 page. |
| Fuchphone Extras, “Samsung Gear Live—Designs | Watch Faces”, Available online at: https://www.youtube.com/watch?v=fFjtVAxyimE, Jul. 26, 2014, 1 page. |
| Fukuda, Kazuhiro, “Xperia Z1 Perfect Manual”, Sotec Co., Ltd., No. 1, Nov. 15, 2013, pp. 217-218. |
| Gazer, “iPhone 4S Super Manual”, Shuwa System Co., Saito Kazukuni, vol. 1, Jun. 6, 2013, 7 pages {See Communication under 37 CFR § 1.98(a) (3)}. |
| Geary, David, “Programming HTML5 Canvas”, O'Reilly Japan, Inc., No. 1, Jul. 23, 2014, pp. 327-330. |
| Geek, “How to Put the Day of the Week into the Windows Taskbar Clock”, Available online at: https://www.howtogeek.com/194103/how-to-put-the-day-of-the-week-into-the-windows-taskbar-clock/, 2014, 3 pages. |
| “Google Earth 7.0.1.8244”, retrieved from the Internet: http://dl.google.com/dl/earth/client/ge7/release_7_0_1/googleearth-win-bundle-7.0.1.8244.exe, Oct. 29, 2012, 1 page. |
| “Google Earth on Android—AndroidCentral.com”, Available online at :—https://www.youtube.com/watch?v=1WxN1RunrE4, Feb. 22, 2010, 1 page. |
| GottaBeMobile, “How to Change Watch Faces on Android Wear”, Available online at URL: https://www.youtube.com/watch?v=B8iRGkGq6a8, Jul. 9, 2014, 4 pages. |
| Haidar, Rawand, “How to Use Android Wear Smartwatch as a Flashlight!”, Available online at :—https://howto.highonandroid.com/android-wear-tutorials/how-to-use-android-wear-smartwatch-as-a-flashlight-flashlight-app/, Sep. 13, 2015, 6 pages. |
| HollywoodFrodo, “Free Flashlight Android App by Asus Best Flashlight App on Google Play”, Online Available at: https://www.youtube.corn/watch?v=K_kFa7PoVsc>, Sep. 9, 2016, 3 pages. |
| “Huawei Watch FAQs-en_us-V2.8”, Online available at: https://maplindownloads.s3-eu-west-1.amazonaws.com/A27WH-9512.pdf, Apr. 11, 2016, 135 pages. |
| Intention to Grant received for Danish Patent Application No. PA201570496, dated Feb. 17, 2016, 6 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770387, dated Apr. 4, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770387, dated May 24, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770397, dated Aug. 18, 2017, 7 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/034604, dated Feb. 16, 2017, 21 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/034606, dated Feb. 16, 2017, 11 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/034607, dated Feb. 16, 2017, 18 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/044473, dated Mar. 2, 2017, 20 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/044485, dated Mar. 2, 2017, 20 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/053353, dated Sep. 21, 2017, 15 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/054223, dated Dec. 14, 2017, 18 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/021403, dated Sep. 21, 2017, 21 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/035090, dated Dec. 14, 2017, 14 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/037686, dated Mar. 1, 2018, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/034834, dated Dec. 20, 2018, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/049793, dated Apr. 4, 2019, 15 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/034604, dated Nov. 9, 2015, 30 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/034606, dated Dec. 2, 2015, 17 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/034607, dated Dec. 1, 2015, 23 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/044473, dated Feb. 12, 2016, 24 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/044485, dated Feb. 9, 2016, 27 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/053353, dated May 9, 2016, 21 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/054223, dated Jul. 6, 2016, 25 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/021403, dated May 12, 2016, 23 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/035090, dated Oct. 4, 2016, 17 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/037686, dated Sep. 9, 2016, 19 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2017/034834, dated Aug. 23, 2017, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2017/049793, dated Dec. 27, 2017, 19 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2018/032164, dated Oct. 18, 2018, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2018/032385, dated Aug. 3, 2018, 14 pages. |
| Invitation to Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2015/034604, dated Sep. 4, 2015, 6 pages. |
| Invitation to Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2015/034606, dated Sep. 9, 2015, 6 pages. |
| Invitation to Pay Additional Fee received for European Patent Application No. 15747595.5, dated Feb. 9, 2018, 6 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/034607, dated Sep. 30, 2015, 4 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/044473, dated Nov. 3, 2015, 5 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/044485, dated Nov. 3, 2015, 7 pages. |
| Invitation to Pay Additional fees received for PCT Patent Application No. PCT/US2015/053353, dated Jan. 21, 2016, 7 pages. |
| Invitation to Pay Additional fees received for PCT Patent Application No. PCT/US2015/054223, dated Mar. 9, 2016, 9 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2016/035090, dated Jul. 15, 2016, 2 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2017/049793, dated Nov. 3, 2017, 2 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2018/032164, dated Aug. 21, 2018, 10 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/030770, dated Jul. 26, 2019, 12 pages. |
| ISO 9241-13:1998, “Ergonomic requirements for office work with visual display terminals (VDTs)”, Part 13: User guidance, International Standard ISO, Zuerich, CH, vol. 9241-13, Jul. 15, 1998, 40 pages. |
| Kenney, Briley, “How to Customize a Smartwatch and other Personalization Questions”, Available online at: https://smartwatches.org/learn/customize-smartwatch/, Jan. 23, 2014, 3 pages. |
| “Kidizoom Smartwatch”, Available online at URL: https://www.vtechnl.com/media/downloads/Kidizoom-Smart-Watch.pdf, Jun. 24, 2014, 23 pages. |
| “Link to Wayback Machine with link to Google Play showing different layouts of complications associated with a clock face”, Available online at: https://play.google.com/store/apps/details?id=com.levelup.beautifulwidgets.free&hl=da , Sep. 9, 2013, 6 pages. |
| “Living Earth”, Available at: http://www.livingcarthapp.com/, 2014, 6 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 15730924.6, mailed on Mar. 13, 2019, 4 pages. |
| “MS Excel 2013”, Jan. 29, 2013, 2 pages. |
| NerdTalk, “The Best Android Clock Widgets”, Available at: https://www.youtube.com/watch?v=E1bAprWByfU, Apr. 25, 2011, 1 page. |
| “New, but unsigned—Easy StopWatch for Symbian”, XP55393563, Available online at: http://www.allaboutsymbian.com/flow/item/19490_New_but_unsigned-Easy_StopWatc.php, Mar. 15, 2014, 15 pages. |
| “Night Display (Alarm Clock) App”, Google Play Store Night Display (Alarm Clock) Description page, Available at: https://web.archive.org/web/20141007124222/https://play.google.com/store/apps/details?id=com.srk.nighttimedisplay&hl=en, Oct. 7, 2014, pp. 1-3. |
| Non-Final Office Action received for U.S. Appl. No. 15/554,204, dated Apr. 17, 2019, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,879, dated Dec. 15, 2016, 33 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,879, dated Nov. 6, 2015, 35 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,890, dated Dec. 18, 2018, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,890, dated Jun. 6, 2017, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,890, dated Oct. 19, 2015, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,898, dated Dec. 1, 2015, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,907, dated Jan. 12, 2016, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/815,909, dated Nov. 27, 2015, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/821,667, dated Feb. 4, 2019, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/821,667, dated Jul. 14, 2017, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,889, dated Mar. 7, 2017, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,606, dated Dec. 7, 2017, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,606, dated May 8, 2019, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/846,511 dated Oct. 27, 2017, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/846,511, dated Nov. 30, 2018, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/183,663, dated Jul. 9, 2018, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/355,956, dated May 31, 2019, 32 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/405,122, dated May 31, 2019, 43 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/421,865, dated Mar. 21, 2019, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/713,544, dated Jan. 24, 2019, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/791,829, dated Nov. 8, 2018, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/798,235, dated Apr. 24, 2019, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/798,235, dated Mar. 14, 2018, 58 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/881,544, dated Jun. 7, 2018, 15 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2016229847, dated Sep. 12, 2018, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201510481525.6, dated May 27, 2019, 2 pages (1 page of English Translation). |
| Notice of Allowance received for Chinese Patent Application No. 201510483305.7, dated Jan. 8, 2019, 3 pages (1 page of English Translation). |
| Notice of Allowance received for Chinese Patent Application No. 201510484514.3, dated Jun. 6, 2019, 2 pages (1 page of English Translation). |
| Notice of Allowance received for Chinese Patent Application No. 201520594249.X, dated Jul. 12, 2016, 4 pages (2 pages of English Translation). |
| Notice of Allowance received for Chinese Patent Application No. 201810037665.8, dated Jul. 9, 2019, 4 pages (1 page of English Translation). |
| Notice of Allowance received for Danish Patent Application No. PA201570495, dated Feb. 22, 2017, 1 page. |
| Notice of Allowance received for Danish Patent Application No. PA201570496, dated Apr. 18, 2016, 2 pages |
| Notice of Allowance received for Japanese Patent Application No. 2017-505450, dated Mar. 9, 2018, 10 pages (7 pages of English Translation). |
| Notice of Allowance received for Japanese Patent Application No. 2017-505847, dated May 20, 2019, 4 pages (1 page of English Translation). |
| Notice of Allowance received for Japanese Patent Application No. 2017-545918, dated Jul. 22, 2019, 4 pages (1 page of English Translation). |
| Notice of Allowance received for Japanese Patent Application No. 2018-074971, dated Apr. 23, 2019, 4 pages (1 page of English Translation). |
| Notice of Allowance received for Korean Patent Application No. 10-2017-7005939, dated Mar. 30, 2018, 5 pages (2 pages of English Translation). |
| Notice of Allowance received for Taiwanese Patent Application No. 104124962, dated Jul. 27, 2017, 3 pages {See Communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Taiwanese Patent Application No. 104124963, dated Sep. 28, 2017, 5 pages (1 page of English Translation of Search report). |
| Notice of Allowance received for Taiwanese Patent Application No. 104124995, dated Jul. 27, 2017, 3 pages {See Communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Taiwanese Patent Application No. 104124997, dated Jun. 16, 2017, 5 pages (1 page of English Translation of Search report). |
| Notice of Allowance received for Taiwanese Patent Application No. 104124998, dated Mar. 31, 2017, 3 pages {See Communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Taiwanese Patent Application No. 104134740, dated Dec. 8, 2016, 5 pages (1 page of English Translation of Search Report). |
| Notice of Allowance received for U.S. Appl. No. 14/815,879, dated Jun. 26, 2017, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,898, dated Dec. 5, 2016, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,898, dated Oct. 24, 2016, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,907, dated Jul. 28, 2016, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,907, dated Nov. 30, 2016, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,909, dated Jun. 9, 2016, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,909, dated May 3, 2016, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,909, dated May 20, 2016, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/815,909, dated Sep. 6, 2016, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/821,667, dated Jun. 12, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,889, dated Oct. 30, 2017, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/183,663, dated Jan. 17, 2019, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/791,829, dated Oct. 4, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/798,257, dated May 22, 2019, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/881,544, dated Jun. 26, 2019, 6 pages. |
| Nova, “Tour of the Solar System”, Retrieved from: http://www.pbs.org/wgbh/nova/space/tour-solar-system.html, May 24, 2013, 14 pages. |
| Obara, Yuuta, “iPhone Application Selection for University Students”, Shuwa System Co., Saito Kazukuni, vol. 1, May 16, 2013, 4 pages {See Communication under 37 CFR § 1.98(a) (3)}. |
| Octoba, “Just Install It—Utilizing Method for Android Application Business”, ASCII Media Works Co. Takano Kiyoshi, vol. 1, Apr. 25, 2013, 6 pages {See Communication under 37 CFR § 1.98(a) (3)}. |
| Office Action received for Danish Patent Application No. PA201570499, dated Nov. 1, 2017, 6 pages. |
| Office Action received for European Patent Application No. 15730924.6, dated Dec. 12, 2017, 8 pages. |
| Office Action received for Australian Patent Application No. 2015101019, dated Oct. 14, 2015, 3 pages. |
| Office Action received for Australian Patent Application No. 2015101019, dated Apr. 7, 2016, 4 pages. |
| Office Action received for Australian Patent Application No. 2015101019, dated Feb. 12, 2016, 4 pages. |
| Office Action received for Australian Patent Application No. 2015101020, dated Oct. 26, 2015, 8 pages. |
| Office Action received for Australian Patent Application No. 2015101021, dated Apr. 26, 2016, 4 pages. |
| Office Action received for Australian Patent Application No. 2015101021, dated Oct. 28, 2015, 10 pages. |
| Office Action received for Australian Patent Application No. 2015298710, dated Apr. 13, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2015298710, dated Feb. 15, 2017, 2 pages. |
| Office Action received for Australian Patent Application No. 2015298710, dated Nov. 6, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2015298710, dated Sep. 24, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2016100411, dated Jun. 10, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2016100476, dated Jun. 9, 2016, 4 pages. |
| Office Action received for Australian Patent Application No. 2016100765, dated Aug. 5, 2016, 2 pages. |
| Office Action received for Australian Patent Application No. 2016100765, dated Dec. 16, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2016229847, dated Jul. 3, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2017277813, dated Jun. 11, 2019, 3 pages. |
| Office Action received for Australian Patent Application No. 2018100179, dated Jun. 4, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2018100179, dated Nov. 20, 2018, 7 pages. |
| Office Action received for Australian Patent Application No. 2018100179, dated Sep. 14, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2018206770, dated Apr. 30, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2018206770, dated Jul. 16, 2019, 5 pages. |
| Office Action received for Australian Patent Application No. 2018206770, dated Jul. 25, 2018, 5 pages. |
| Office Action received for Australian Patent Application No. 2018206770, dated Mar. 5, 2019, 3 pages. |
| Office Action received for Australian Patent Application No. 2018279037, dated Jun. 18, 2019, 5 pages. |
| Office Action received for Chinese Patent Application No. 201520595384.6, dated Mar. 25, 2016, 3 pages (1 page of English Translation). |
| Office Action received for Chinese Patent Application No. 201510479088.4, dated Mar. 12, 2018, 20 pages (6 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201510479088.4, dated May 7, 2019, 6 pages (3 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201510481525.6, dated Aug. 29, 2018, 10 pages (5 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201510481525.6, dated Nov. 29, 2017, 9 pages (3 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201510483268.X, dated Apr. 16, 2019, 6 pages (3 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201510483268.X, dated Dec. 1, 2017, 11 pages (5 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201510483268.X, dated Oct. 19, 2018, 10 pages (5 pages of English Translation). |
| Office action received for Chinese Patent Application No. 201510483305.7, dated Aug. 31, 2018, 10 pages (5 pages of English Translation). |
| Office action received for Chinese Patent Application No. 201510483305.7, dated Dec. 1, 2017, 13 pages (5 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201510484514.3, dated Apr. 4, 2018, 12 pages (5 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201510484514.3, dated Dec. 24, 2018, 13 pages (6 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201520594249.X, dated Mar. 25, 2016, 3 pages (1 page of English Translation). |
| Office Action received for Chinese Patent Application No. 201520595384.6, dated Dec. 30, 2016, 2 pages {See Communication under 37 CFR § 1.98(a) (3)}. |
| Office Action received for Chinese Patent Application No. 201520595384.6, dated Jul. 22, 2016, 3 pages (1 page of English Translation). |
| Office Action received for Chinese Patent Application No. 201520595385.0, dated Dec. 30, 2016, 2 pages {See Communication under 37 CFR § 1.98(a) (3)}. |
| Office Action received for Chinese Patent Application No. 201520595385.0, dated Jul. 22, 2016, 3 pages (1 page of English Translation). |
| Office Action received for Chinese Patent Application No. 201520595385.0, dated Mar. 25, 2016, 3 pages (1 page of English Translation). |
| Office Action received for Chinese Patent Application No. 201520595408.8, dated Dec. 9, 2015, 4 pages (2 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201520595408.8, dated Dec. 30, 2016, 2 pages {See Communication under 37 CFR § 1.98(a) (3)}. |
| Office Action received for Chinese Patent Application No. 201520595408.8, dated Jul. 25, 2016, 3 pages (1 page of English Translation). |
| Office Action received for Chinese Patent Application No. 201520595408.8, dated Mar. 25, 2016, 3 pages (1 page of English Translation). |
| Office Action received for Chinese Patent Application No. 201520595538.1, dated Dec. 30, 2016, 2 pages {See Communication under 37 CFR § 1.98(a) (3)}. |
| Office Action received for Chinese Patent Application No. 201520595538.1, dated Jul. 22, 2016, 3 pages (1 page of English Translation). |
| Office Action received for Chinese Patent Application No. 201520595538.1, dated Mar. 25, 2016, 3 pages (1 page of English Translation). |
| Office Action received for Chinese Patent Application No. 201680047983.1, dated Mar. 18, 2019, 18 pages (6 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201810037665.8, dated Dec. 7, 2018, 10 pages (5 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201810467061.7, dated Aug. 15, 2019, 13 pages (7 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201810467061.7, dated Feb. 22, 2019, 19 pages (10 pages of English Translation). |
| Office Action Received for Chinese Patent Application No. 201520594249.X, dated Dec. 9, 2015, 4 pages (2 pages of English Translation). |
| Office Action Received for Chinese Patent Application No. 201520595384.6, dated Dec. 9, 2015, 4 pages (2 pages of English Translation). |
| Office Action Received for Chinese Patent Application No. 201520595385.0, dated Dec. 9, 2015, 4 pages (2 pages of English Translation). |
| Office Action Received for Chinese Patent Application No. 201520595538.1, dated Dec. 9, 2015, 4 pages (2 pages of English Translation). |
| Office Action received for Danish Patent Application No. PA201570495, dated Dec. 9, 2016, 2 pages. |
| Office action received for Danish Patent Application No. PA201570495, dated May 4, 2016, 8 pages. |
| Office Action received for Danish Patent Application No. PA201570495, dated Oct. 29, 2015, 7 pages. |
| Office Action received for Danish Patent Application No. PA201570497, dated Feb. 21, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201570497, dated May 17, 2016, 6 pages. |
| Office Action received for Danish Patent Application No. PA201570497, dated Nov. 15, 2016, 2 pages. |
| Office Action received for Danish Patent Application No. PA201570497, dated Oct. 24, 2017, 2 pages. |
| Office Action received for Danish Patent Application No. PA201570498, dated Feb. 6, 2017, 2 pages. |
| Office Action received for Danish Patent Application No. PA201570498, dated Jun. 2, 2016, 8 pages. |
| Office Action received for Danish Patent Application No. PA201570498, dated Oct. 26, 2017, 5 pages. |
| Office Action received for Danish Patent Application No. PA201570498, dated Oct. 30, 2015, 7 pages. |
| Office Action received for Danish Patent Application No. PA201570499, dated Feb. 14, 2017, 2 pages. |
| Office Action received for Danish Patent Application No. PA201570499, dated Jun. 16, 2016, 8 pages. |
| Office Action received for Danish Patent Application No. PA201570499, dated Jun. 19, 2018, 4 pages. |
| Office Action received for Danish Patent Application No. PA201570499, dated Nov. 3, 2015, 7 pages. |
| Office Action Received for Danish Patent Application No. PA201570768, dated Sep. 13, 2016, 8 pages. |
| Office Action received for Danish Patent Application No. PA201570770, dated Apr. 7, 2017, 7 pages. |
| Office Action received for Danish Patent Application No. PA201570770, dated Mar. 17, 2016, 9 pages. |
| Office Action received for Danish Patent Application No. PA201570770, dated Sep. 12, 2016, 6 pages. |
| Office Action received for Danish Patent Application No. PA201770387, dated Feb. 1, 2018, 3 Pages. |
| Office Action received for Danish Patent Application No. PA201770791, dated Jan. 31, 2018, 8 pages. |
| Office Action received for Danish Patent Application No. PA201770791, dated Jul. 13, 2018, 2 pages. |
| Office Action received for Danish Patent Application No. PA201770791, dated Jun. 11, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201570496, dated Oct. 29, 2015, 6 pages. |
| Office Action received for Danish Patent Application No. PA201570497, dated Oct. 30, 2015, 6 pages. |
| Office Action received for European Patent Application No. 15730925.3, dated Apr. 12, 2018, 8 pages. |
| Office Action received for European Patent Application No. 15747595.5, dated Apr. 15, 2019, 4 pages. |
| Office Action received for European Patent Application No. 15747595.5, dated Jun. 27, 2018, 8 pages. |
| Office Action received for European Patent Application No. 17206177.2, dated May 15, 2018, 6 pages. |
| Office Action received for European Patent Application No. 18172554.0, dated Jul. 12, 2019, 10 Pages. |
| Office Action received for European Patent Application No. 15730925.3, dated Feb. 27, 2019, 5 pages. |
| Office Action received for German Patent Application No. 112015003083.2, dated Mar. 9, 2018, 12 pages (5 pages of English Translation). |
| Office Action received for Japanese Patent Application No. 2017-505450, dated Jun. 20, 2017, 8 pages (4 pages of English Translation). |
| Office Action received for Japanese Patent Application No. 2017-505842, dated Feb. 22, 2019, 11 pages (6 pages of English Translation). |
| Office Action received for Japanese Patent Application No. 2017-505842, dated Sep. 9, 2019, 7 pages (3 pages of English Translation). |
| Office Action received for Japanese Patent Application No. 2017-505847, dated Feb. 12, 2019, 13 pages (6 pages of English Translation). |
| Office Action received for Japanese Patent Application No. 2017-545918, dated Sep. 14, 2018, 12 pages (7 pages of English Translation). |
| Office Action received for Japanese Patent Application No. 2018-074971, dated Jan. 28, 2019, 6 pages (3 pages of English Translation). |
| Office Action received for Japanese Patent Application No. 2018-537840, dated Jul. 8, 2019, 15 pages (8 pages of English Translation). |
| Office Action received for Korean Patent Application No. 10-2017-7005939, dated Jun. 30, 2017, 6 pages (2 pages of English Translation). |
| Office Action received for Korean Patent Application No. 10-2017-7024570, dated Jul. 10, 2019, 6 pages (3 pages of English Translation). |
| Office Action received for Korean Patent Application No. 10-2017-7024570, dated Sep. 28, 2018, 14 pages (6 pages of English Translation). |
| Office Action received for Korean Patent Application No. 10-2018-7018904, dated Aug. 20, 2019, 8 pages (3 pages of English Translation). |
| Office Action received for Korean Patent Application No. 10-2018-7022101, dated Feb. 14, 2019, 15 pages (6 pages of English Translation). |
| Office Action received for Korean Patent Application No. 10-2018-7022101, dated Jul. 9, 2019, 10 pages (5 pages of English Translation). |
| Office Action received for Netherland Patent Application No. 2015239, dated Oct. 28, 2016, 13 pages (5 pages of English Translation). |
| Office Action received for Netherland Patent Application No. 2015245, dated Jan. 24, 2017, 11 pages (1 page of English Translation). |
| Office Action Received for Taiwanese Patent Application No. 104124962, dated Nov. 29, 2016, 6 pages (3 pages of English Translation). |
| Office Action received for Taiwanese Patent Application No. 104124998, dated Nov. 29, 2016, 6 pages (3 pages of English Translation). |
| Office Action received for Taiwanese Patent Application No. 104124963, dated Jan. 5, 2017, 11 pages (5 pages of English Translation). |
| Office Action received for Taiwanese Patent Application No. 104124995, dated Dec. 1, 2016, 6 pages (3 pages of English Translation). |
| Office Action received for Taiwanese Patent Application No. 104124997, dated Dec. 8, 2016, 12 pages (5 pages of English Translation). |
| Office Action received for Taiwanese Patent Application No. 104126627, dated Nov. 29, 2016, 9 pages (4 pages of English Translation). |
| Office Action received for Taiwanese Patent Application No. 104126627, dated Aug. 30, 2018, 22 pages (9 pages of English Translation). |
| Office Action received for Taiwanese Patent Application No. 104126627, dated Dec. 20, 2018, 4 pages (2 pages of English Translation). |
| Office Action received for Taiwanese Patent Application No. 104126627, dated Oct. 16, 2017, 7 pages (3 pages of English Translation). |
| Office Action received for Taiwanese Patent Application No. 104132636, dated Dec. 13, 2018, 26 pages (9 pages of English Translation). |
| Office Action received for Taiwanese Patent Application No. 104132636, dated Mar. 23, 2017, 25 pages (10 pages of English Translation). |
| Office Action received for Taiwanese Patent Application No. 104132636, dated Oct. 31, 2017, 10 pages (4 pages of English Translation). |
| Omar Romero, “Sony Smartwatch 2 Custom Watchfaces Tutorial”, Retrieved From: https://www.youtube.com/watch?v=8odbxqwSQR8, May 1, 2014, 2 pages. |
| “Online Alarm Clock”, https://web.archive.org/web/20150505081746/http://www.online-stopwatch.com/online-alarm-clock, May 5, 2015, 2 pages. |
| “Pentax K20D Operating Manual”, http://www.ricoh-imaging.eu/en/operating-manuals-download.html, 2008, pp. 173-174. |
| Pre-Interview First Office Action received for U.S. Appl. No. 14/815,890, dated May 26, 2016, 4 pages. |
| Rehman, A, “Install Android 4.2 Gesture-Based Keyboard & Clock App on Jelly Bean 4.1 or Higher”, Excerpts from, Available online at: http://www.addictivetips.com/android/install-android-4-2-keyboard-clock-app-apk-on-jelly-bean-4-1-x/, Nov. 3, 2012, 4 pages. |
| Restriction Requirement received for U.S. Appl. No. 14/815,890, dated Feb. 22, 2016, 5 pages, 5 pages. |
| “Reuse Animations-Synfig Animation Studio”, Available online at: https://wiki.synfig.org/index.php?title=Doc:Reuse_Animations&oldid=18173, May 20, 2013, 5 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201770387, dated Oct. 12, 2017, 8 pages. |
| Search Report and Opinion Received for Netherland Patent Application No. 2015232, dated Jan. 25, 2017, 9 pages (1 page of English Translation). |
| Search Report and Opinion received for Netherlands Patent Application No. 2015242, dated Jul. 4, 2017, 20 pages (10 pages of English Translation). |
| Search Report and Opinion received for Netherlands Patent Application No. 2018531, dated Jul. 27, 2017, 14 pages (6 pages of English Translation). |
| Search Report received for Danish Patent Application No. 201570768, dated Mar. 17, 2016, 11 pages. |
| Shiota, Shinji, “Windows 7 Dojo”, Weekly ASCII, Ascii Mediaworks Inc., vol. 798, Aug. 31, 2010, 3 pages. |
| Smartwatch, “App Earth Space HD Live Wallpaper APK for Smart Watch”, Version 1.7, Android version 2.2, Aug. 27, 2013, 1 page. |
| “Solar Walk Free”, Vito Technology, Jun. 19, 2014, 9 pages. |
| Sony, “Live View™ micro display”, Extended User Guide, Aug. 2010, 27 pages. |
| Sony, “Sony SmartWatch”, User Guide, Dec. 2011, 18 pages. |
| StateofTech, “Samsung Galaxy Gear Tips—Change the Clock Face”, Retrieved from: https://www.youtube.com/watch?v=GOom7AZUAjY, Dec. 11, 2013, 2 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15730924.6, mailed on Jun. 13, 2018, 10 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15730925.3, mailed on Oct. 2, 2019, 8 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17206177.2, mailed on Jun. 3, 2019, 8 pages. |
| Sun Set, “Sun Set solar image clock”, Available at: https://web.archive.orgjweb/20140719005410/http://www.sunsetclock.com/, 2013, 5 pages. |
| TalkAndroid, “Android Wear walkthrough”, Available online at: https://www.youtube.com/watch?v=4xntpZac4sw, Jun. 30, 2014, 1 page. |
| “The Simply Alarm app for Pebble”, Available online at: https://web.archive.org/web/20150517070400/http://www.rebootsramblings.ca/n/sahhelp/https://www.youtube.com/watch?v=IVp1scQPw08, May 17, 2015, 1 page. |
| “Tropical Fish 14”, Available online at: https://www.turbosquid.com/3d-models/tropical-fish-3d-model/388510, Feb. 4, 2008, 2 pages. |
| Tweedie, Steven, “Create and Customize Your Own Emojis with ‘Makemoji’ for iPhone”, Available online at: http://www.businessinsider.com/create-custom-emojis-with-makemoji-app-2014-8, Aug. 19, 2014, 6 pages. |
| “UlKit User Interface Catalog: Page Controls”, Available online at: https://web.archive.org/web/20140703123442/https://developer.apple.com/library/ios/documentation/userexperience/conceptual/UlKitUlCatalog/UlPageControl.html, Dec. 16, 2013, 4 pages. |
| “Ultitorch for”, Online Available at: https://apkgk.com/com.qasq.torchpro, Jan. 8, 2016, 4 pages. |
| Viticci, Frederico, “Checking Time Zones with Living Earth—MacStories”, Available at: https://www.macstories.net/reviews/checking-time-zones-with-living-earth/, Dec. 11, 2013, pp. 1-5. |
| Watchophilia, “Mickey Mouse Watches”, Online Available at: https://web.archive.org/web/20130929065422/https://www.watchophilia.com/photogallery/mickey-mouse/, Sep. 29, 2013, 16 pages. |
| Watchuseek, “The Watch every Father needs: M-I-C-K-E-Y, M-O-U-S-E. Mickey Mouse . . . ?”, Online Available at: https://forums.watchuseek.com/f2/watch-every-father-needs-m-i-c-k-e-y-m-o-u-s-e-mickey-mouse-855069.html, 2013, 3 pages. |
| Whitwam, Ryan, “Facer is Fast Becoming the De Facto Custom Watch Face Maker for Android Wear”, Available online at: http://www.androidpolice.com/2014/09/19/facer-is-fast-becoming-the-de-facto-custom-watch-face-maker-for-android-wear, Sep. 19, 2014, 11 pages. |
| Xperia ZL2 SOL25, “Instruction Manual”, Detailed version, KDDI Corporation, No. 1, vol. 1, Jun. 2014, 4 pages. |
| Zukerman, Erez, “6 Beautiful, Interesting & Versatile Timer Apps [Android]”, available at: http://www.makeuseof.com/tag/beautiful-interesting-versatile-timer-apps-android/, May 18, 2012, 5 pages. |
| Advisory Action received for U.S. Appl. No. 14/846,511, dated Oct. 22, 2019, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/713,544, dated Oct. 24, 2019, 4 pages. |
| Final Office Action received for U.S. Appl. No. 15/554,204, dated Oct. 31, 2019, 22 pages. |
| Final Office Action received for U.S. Appl. No. 15/798,235, dated Oct. 18, 2019, 25 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015298710, dated Oct. 8, 2019, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7022101, dated Oct. 14, 2019, 4 pages (1 page of English Translation). |
| Office Action received for Australian Patent Application No. 2018201089, dated Oct. 11, 2019, 4 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201970598, dated Oct. 31, 2019, 9 pages. |
| Brief Communication regarding Oral Proceedings received for European Patent Application No. 17206177.2, mailed on Nov. 21, 2019, 5 pages. |
| Extended European Search Report received for European Patent Application No. 17810723.1, dated Nov. 12, 2019, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2018/032164, dated Nov. 21, 2019, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/030770, dated Oct. 31, 2019, 23 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201510483268.X, dated Nov. 6, 2019, 2 pages (1 page of English translation). |
| Notice of Allowance received for U.S. Appl. No. 15/355,956, dated Nov. 22, 2019, 29 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/881,544, dated Nov. 7, 2019, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7029673, dated Nov. 5, 2019, 10 pages (4 pages of English Translation). |
| Search Report and Opinion received for Danish Patent Application No. PA201970599, dated Nov. 8, 2019, 12 pages. |
| Andro Dollar, “Huawei Watch GT Always on Mode Update is finally here!”, Online Available at: https://www.youtube.com/watch?v=AJw_FlAf7v4, Jun. 6, 2019, 4 pages. |
| Internet Blog Post, “[PC] Pre-Customization of Black Desert's Characters”, Online Available at: https://blog.naver.com/hsh6051/220209813968, Dec. 14, 2014, 41 pages (21 pages of English translation). |
| Zephyrnix, “Steam's In-Game Home menu”, Online Available at: https://www.youtube.com/watch?v=jLoRFiPkcUw, see 0;00-1;06, Feb. 15, 2011, 3 pages. |
| Cancellation of Oral Proceedings received for European Patent Application No. 17206177.2, mailed on Dec. 4, 2019, 2 pages. |
| Final Office Action received for U.S. Appl. No. 15/421,865, dated Dec. 2, 2019, 19 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2018/032385, dated Nov. 28, 2019, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/713,544, dated Dec. 11, 2019, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,281, dated Dec. 10, 2019, 23 pages. |
| Office Action received for Australian Patent Application No. 2017330211, dated Dec. 5, 2019, 3 pages. |
| Office Action received for Chinese Patent Application No. 201680047983.1, dated Nov. 28, 2019, 9 pages (4 pages of English Translation). |
| Search Report and Opinion received for Danish Patent Application No. PA201970597, dated Dec. 18, 2019, 10 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201970596, dated Dec. 4, 2019, 11 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/584,281, dated Mar. 9, 2020, 5 pages. |
| Brief Communication regarding Oral Proceedings received for European Patent Application No. 15730925.3, mailed on Feb. 18, 2020, 7 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770791, dated Feb. 19, 2020, 2 pages. |
| Intention to Grant received for European Patent Application No. 15747595.5, dated Feb. 17, 2020, 8 pages. |
| Intention to Grant received for European Patent Application No. 17206177.2, dated Feb. 24, 2020, 8 pages. |
| Intention to Grant received for European Patent Application No. 18172554.0, dated Feb. 17, 2020, 8 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7005734, dated Feb. 24, 2020, 13 pages (7 pages of English Translation). |
| Big Phil TV, “Gear S3 Watch faces with great always on display(A O D)”, Available online at: https://www.youtube.com/watch?v=2cxMnrMiGU8, Apr. 5, 2017, 3 pages. |
| Cengic, Suad, “Samsung Gear S3—Display Always On! Cool!”, Available online at: https://www.youtube.com/watch?v=ceeDinbPwOY, Mar. 10, 2017, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/355,956, dated Jan. 3, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/791,829, dated Jan. 16, 2020, 2 pages. |
| Droid Life, “How to: Use Always-on Apps with Android Wear”, Available online at: https://www.youtube.com/watch?v=_-xYB9EBTaA, Jun. 26, 2015, 3 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,445, dated Dec. 26, 2019, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/846,511 dated Jan. 7, 2020, 25 pages. |
| Office Action received for European Patent Application No. 16837432.0, dated Jan. 10, 2020, 7 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/421,865, dated Feb. 3, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/554,204, dated Jan. 31, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/798,235, dated Feb. 3, 2020, 3 pages. |
| Final Office Action received for U.S. Appl. No. 15/405,122, dated Jan. 21, 2020, 36 pages. |
| Office Action and Search Report received for Danish Patent Application No. PA201970598, dated Jan. 28, 2020, 6 pages. |
| Office Action received for Australian Patent Application No. 2018279037, dated Jan. 17, 2020,4 pages. |
| Office Action received for Danish Patent Application No. PA201970599, dated Jan. 23, 2020, 6 pages. |
| Phandroid, “New Android Wear Wrist Gestures in Marshmallow”, Available online at: https://www.youtube.com/watch?v=0WhKuklpQ9A, Feb. 11, 2016, 3 pages. |
| Wikipedia, “Emoji”, Available online at: https://en.wikipedia.org/w/index.php?title=Emoji&oldid=648831795, Feb. 25, 2015, 12 pages. |
| Wikipedia, “Emoticon”, Available online at: https://en.wikipedia.org/w/index.php?title=Emoticon&oldid=648776142, Feb. 25, 2015, 9 pages. |
| Advisory Action received for U.S. Appl. No. 15/554,204, dated Mar. 12, 2020, 3 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/584,445, dated Mar. 17, 2020, 5 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/815,890, mailed on Mar. 20, 2020, 16 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-505842, dated Mar. 16, 2020, 4 pages (1 page of English Translation). |
| Office Action received for Chinese Patent Application No. 2018104670617, dated Feb. 18, 2020, 12 pages (6 pages of English Translation). |
| Office Action received for Danish Patent Application No. PA201970599, dated May 27, 2020, 4 pages. |
| Office Action received for Danish Patent Application No. PA201970596, dated May 6, 2020, 4 pages. |
| Advisory Action received for U.S. Appl. No. 15/421,865, dated Apr. 16, 2020, 7 pages. |
| Advisory Action received for U.S. Appl. No. 16/582,020, dated Aug. 3, 2020, 4 pages. |
| “AOD too Dim. I've Answered My Own Question to Help Others”, Online Available: <https://forums.androidcentral.com/samsung-galaxy-s9-s9-plus/874444-aod-too-dim-ive-answered-my-own-question-help-others.html>, Mar. 11, 2018, 3 pages. |
| Android Tips, “Create a Minimal Lock Screen with WidgetLocker”, Online Available at: http://appstap192.blogspot.com/2012/01/create-minimal-lock-screen-with.html, Jan. 18, 2012, 6 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 14/846,511, dated Apr. 20, 2020, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/713,544, dated Apr. 6, 2020, 7 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/389,722, dated Jul. 7, 2020, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/582,020, dated Jul. 14, 2020, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/582,020, dated Mar. 25, 2020, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/585,399, dated Mar. 25, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/405,122, dated May 21, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/584,281, dated Sep. 14, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/585,714, dated Jul. 20, 2020, 5 pages. |
| Barbosa Jonathan, “Weather Clock 2.1 for Android”, APKPure, Online Available at: <https://apkpure.com/weather-clock/com.urbandroid.wclock>, Oct. 15, 2015, 3 pages. |
| “Brightness on Lock Screen”, Online Available at: https://www.reddit.com/r/galaxys10/comments/b4d5fb/brightness_on_lock_screen/, 2019, 1 page. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/554,204, dated Aug. 19, 2020, 3 pages. |
| Dan, “Get This Look: ‘Minimal’ Zooper Widget”, Online Available at: <https://www.androidguys.com/featured/customize/get-look-minimal-zooper-widget/>, Mar. 7, 2014, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201770791, dated Jul. 7, 2020, 2 pages. |
| Decision to Grant received for European Patent Application No. 15747595.5, dated Jul. 16, 2020, 2 pages. |
| Decision to Grant received for European Patent Application No. 17206177.2, dated Aug. 6, 2020, 2 pages. |
| Decision to Grant received for European Patent Application No. 18172554.0, dated Jul. 30, 2020, 2 pages. |
| Elecont, “Weather clock—hourly forecast description”, Accurate 10-day weather forecast, NOAA radar and satellite, buoy, Elecont LLC Forums, Online Available at: <https://www.tapatalk.com/groups/elecontfr/weather-clock-hourly-forecast-description-t427.html>, Dec. 1, 2011, 5 pages. |
| European Search Report received for European Patent Application No. 20172197.4, dated Jul. 28, 2020, 4 pages. |
| Extended European Search Report received for European Patent Application No. 20180900.1, dated Sep. 18, 2020, 7 pages. |
| Final Office Action received for U.S. Appl. No. 14/846,511, dated Aug. 11, 2020, 25 pages. |
| Final Office Action received for U.S. Appl. No. 15/713,544, dated May 20, 2020, 14 pages. |
| Final Office Action received for U.S. Appl. No. 16/582,020, dated Apr. 28, 2020, 31 pages. |
| Final Office Action received for U.S. Appl. No. 16/584,281, dated Apr. 15, 2020, 26 pages. |
| Intention to Grant received for European Patent Application No. 15730925.3, dated May 28, 2020, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/030079, dated Sep. 4, 2020, 18 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/030079, dated Jul. 14, 2020, 12 pages. |
| “Looking for a Launcher That Changes the Default Homescreen or Widgets Based on wifi, Location, or Other Context”, Online Available at: https://www.reddit.com/r/androidapps/comments/35lu90/looking_for_a_launcher_that_changes_the_default/, 2015, 2 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 15730925.3, mailed on May 26, 2020, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/405,122, dated Sep. 24, 2020, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/421,865, dated Oct. 7, 2020, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/389,722, dated Apr. 3, 2020, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/418,786, dated Apr. 24, 2020, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/582,020, dated Jan. 13, 2020, 39 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/585,399, dated Jan. 23, 2020, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/585,714, dated Apr. 16, 2020, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/659,507, dated Oct. 7, 2020, 16 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017277813, dated Jun. 16, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017330211, dated May 11, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018279037, dated May 13, 2020, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-537840, dated Mar. 19, 2020, 4 pages (1 page of English Translation). |
| Notice of Allowance received for Japanese Patent Application No. 2019-096219, dated Jun. 26, 2020, 4 pages (1 page of English Translation). |
| Notice of Allowance received for Japanese Patent Application No. 2019-511611, dated Jul. 20, 2020, 4 pages (1 page of English Translation). |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7018904, dated Jun. 26, 2020, 4 pages (1 page of English Translation). |
| Notice of Allowance received for U.S. Appl. No. 15/554,204, dated Jul. 13, 2020, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/798,235, dated Apr. 1, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/798,235, dated Sep. 22, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,281, dated Sep. 29, 2020, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,445, dated Apr. 17, 2020, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,445, dated Jul. 23, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,445, dated Jun. 24, 2020, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,445, dated May 29, 2020, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/585,366, dated Jan. 2, 2020, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/585,399, dated Jul. 21, 2020, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/585,714, dated Sep. 25, 2020, 15 pages. |
| “Nova Launcher—Lock Screen Edit”, Online Available at: <https://forums.androidcentral.com/ask-question/835057-nova-launcher-lock-screen-edit.html>, Sep. 2017, 2 pages. |
| Office Action received for Australian Patent Application No. 2017277813, dated Mar. 20, 2020, 4 pages. |
| Office Action received for Australian Patent Application No. 2018201089, dated Jul. 23, 2020, 4 pages. |
| Office Action received for Australian Patent Application No. 2019208225, dated Mar. 20, 2020, 3 pages. |
| Office Action received for Chinese Patent Application No. 201510479088.4, dated Apr. 22, 2020, 7 pages (3 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201680013193.1, dated Mar. 25, 2020, 21 pages (8 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201680047983.1, dated Jul. 1, 2020, 6 pages (3 pages of English Translation). |
| Office Action received for Chinese Patent Application No. 201780002643.1, dated Jun. 17, 2020, 30 pages (10 pages of English Translation). |
| Office Action received for European Patent Application No. 20172197.4, dated Aug. 5, 2020, 6 pages. |
| Office Action received for Japanese Patent Application No. 2019-511611, dated Feb. 28, 2020, 4 pages (2 pages of English Translation). |
| Office Action received for Korean Patent Application No. 10-2019-7005734, dated Jul. 14, 2020, 8 pages (4 pages of English Translation). |
| Office Action received for Korean Patent Application No. 10-2019-7029673, dated Sep. 3, 2020, 9 pages (4 pages of English Translation). |
| Office Action received for Korean Patent Application No. 10-2020-7001340, dated Sep. 24, 2020, 19 pages (8 pages of English Translation). |
| Phlam Dev, “Clockwork Tomato Presentation”, Retrieved from the Internet: <https://www.youtube.com/watch?v=2lQDx9REn0E>, Apr. 29, 2016, 6 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/585,399, dated Aug. 26, 2020, 2 pages. |
| Wade Cliff, “Get the most out of Nova Launcher: Changing Icon Sizes”, Online Available at: <https://www.androidguys.com/tips-tools/get-nova-launcher-changing-icon-sizes/>, Nov. 16, 2015, 3 pages. |
| Wade, Cliff, “Get the most out of Nova Launcher: Customizing the Dock (Contest Including)”, Online Available at: <https://www.androidguys.com/tips-tools/get-nova-launcher-customizing-dockcontest-included/>, Dec. 1, 2015, 5 pages. |
| Office Action received for Danish Patent Application No. PA201970597, dated Oct. 29, 2020, 4 pages. |
| Office Action received for Danish Patent Application No. PA201970598, dated Oct. 9, 2020, 4 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/045814, dated Nov. 18, 2020, 11 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 62897959 | Sep 2019 | US |
