Smart Watch Notification Manager
US-2016085397-A1 · Mar 24, 2016 · US
US10496273B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10496273-B2 |
| Application number | US-201715841578-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 14, 2017 |
| Priority date | Mar 27, 2017 |
| Publication date | Dec 3, 2019 |
| Grant date | Dec 3, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for dismissing displayed elements. In some implementations, a device with a touchscreen is operated using a first touch input threshold value, which may correspond to a minimum distance of input to the touchscreen to identify a gesture. An automobile mode event is detected that initiates an automobile mode for the device. A user input to the touchscreen of the device is received while the device is in the automobile mode. Using a second touch input threshold value corresponding to the automobile mode, the device determines that the user input to the touchscreen of the device represents a gesture corresponding to a user interface element displayed on the device. The device dismisses the user interface element so that the user interface element is no longer displayed.
Opening claim text (preview).
What is claimed is: 1. A method comprising: operating a device with a touchscreen using a first touch input threshold value, wherein the first touch input threshold values is a first minimum distance of input along the touchscreen prior to the device identifying the input as a gesture; initiating operation of the device in an automobile mode in response to one or more of: determining that a location of the device corresponds to a location of an automobile; determining that movement of the device is consistent with being in a moving automobile; receiving an input to enable an automobile mode of the device; detecting placement of the device in a receiver for the device in the automobile; detecting a wired or wireless data connection between the device and the automobile; or determining that a particular application is executing at the device, wherein, while operating in the automobile mode, the device uses a second touch input threshold value that is a second minimum distance of input along the touchscreen prior to the device identifying the input as the gestures, and wherein the second minimum distance is greater than the first minimum distance; after initiating the automobile mode: receiving a user input at the touchscreen of the device; determining, by the device and based on the second touch input threshold value, whether the user input is a gesture corresponding to a user interface element displayed by the touchscreen of the device; and in response to determining that the user input is the gesture corresponding to the user interface element, dismissing the user interface element so that the touchscreen ceases displaying the user interface element. 2. The method of claim 1 , wherein the user input is a swipe gesture originating on a user interface element displayed by the touchscreen of the device. 3. The method of claim 1 , wherein the device comprises one or both of: a mobile device and an automobile head unit; and wherein the touchscreen on which the user interface element is displayed comprises one or both of: a touchscreen forming part of the mobile device, and a touchscreen forming part of the automobile head unit to which the mobile computing device is connected by a wired or wireless data connection. 4. The method of claim 1 , wherein the user interface element comprises a user notification, and, in response to dismissing the user interface element so that the user interface element is removed from being displayed, displaying a user input element for user feedback regarding the user interface element that was dismissed. 5. The method of claim 1 , further comprising: storing data indicating that the user interface element was dismissed, the data including an identifier for the user interface element that is derived from content or metadata of the user interface element. 6. The method of claim 1 , further comprising: obtaining a user interface element suggestion for a second user interface element for display; generating an identifier for the second user interface element, wherein the identifier is derived using predetermined elements of content or metadata associated with the second user interface element; comparing the identifier to a list of identifiers for user interface elements that were previously dismissed; and determining whether to display the second user interface element based on the comparison. 7. The method of claim 6 , wherein generating the identifier for the second user interface element comprises generating a hash of the predetermined elements of content or metadata associated with the second user interface element. 8. The method of claim 6 , further comprising: determining, based on the comparison, that the identifier for the second user interface element is not included in the list of identifiers; and responsive to determining that the identifier for the second user interface element is not included in the list of identifiers, displaying the second user interface element. 9. The method of claim 6 , further comprising: determining, based on the comparison, that the identifier for the second user interface element is included in the list of identifiers; and responsive to determining that the identifier for the second user interface element matches an identifier in the list of identifiers, determining to not display the second user interface element. 10. The method of claim 9 , further comprising: in response to determining that identifier for the second user interface element is included in the list of identifiers, terminating the user interface element suggestion and obtaining a new user interface element suggestion for a new user interface element to be displayed. 11. The method of claim 6 , wherein identifiers of user interface elements of different types are generated using different sets of predetermined elements, wherein the method further comprises: determining a user interface element type for the second user interface element; and identifying a set of predetermined elements corresponding to the determined user interface element type, and wherein generating the identifier for the second user interface element comprises generating the identifier based on portions of content or metadata of the second user interface element that correspond to the elements in the identified set of predetermined elements corresponding to the determined user interface element type. 12. A computing device comprising: one or more processors; a touchscreen; and one or more storage devices storing instructions that are operable, when executed by the one or more processors, to cause the one or more processors to: operate the device using a first touch input threshold value, wherein the first touch input threshold values is a first minimum distance of input along the touchscreen prior to the device identifying the input as a gesture; initiate an automobile mode for the device in response to one or more of: determining that a location of the device corresponds to a location of an automobile; determining that movement of the device is consistent with being in a moving automobile; receiving an input to enable an automobile mode of the device; detecting placement of the device in a receiver for the device in the automobile; detecting a wired or wireless data connection between the device and the automobile; or determining that a particular application is executing at the device; after initiating the automobile mode, receive an indication of a user input detected by the touchscreen; determine, based on a second touch input threshold value, whether the user input is a gesture corresponding to a user interface element displayed by the touchscreen of the device, wherein the second touch input threshold value is a second minimum distance of input along the touchscreen prior to the device identifying the input as the gestures, and wherein the second minimum distance is greater than the first minimum distance; and in response to determining that the user input is the gesture corresponding to the user interface element, dismiss the user interface element so that the touchscreen ceases displaying the user interface element. 13. The computing device of claim 12 , wherein the user input is a swipe gesture originating on a user interface element displayed by the touchscreen. 14. The computing device of claim 12 , wherein the computing device comprises one or both of: a mobile device and an automobile head unit; and wherein the touchscreen on which the user interface element is displayed comprises one or both of: a touchscreen forming part of the mobile device, and a touchscreen
for inputting data by handwriting, e.g. gesture or text · CPC title
based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance · CPC title
Interaction with lists of selectable items, e.g. menus · CPC title
for image manipulation, e.g. dragging, rotation, expansion or change of colour · CPC title
using a touch-screen or digitiser, e.g. input of commands through traced gestures · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.