Abstract: Disclosed methods, systems, and storage media provide state-based time/task management interfaces. A computer device may determine various user states and user intents, and generate an instance of a graphical user interface (GUI) comprising objects and semantic time anchors. Each object may correspond to a user intent and each semantic time anchor may be associated with a user state. The computer device may obtain a first input comprising a selection of an object and obtain a second input comprising a selection of a semantic time anchor. The computer device may generate another instance of the GUI to indicate an association of the selected object with the selected semantic time anchor. The computer device may generate a notification to indicate a user intent of the selected object upon occurrence of a state that corresponds with the selected semantic time anchor. Other embodiments may be described and/or claimed.

Abstract: System and techniques for context enhanced indexing are described herein. A document change event may be obtained. A context of the document change event may be captured. Here, the context pertains to an entity responsible for the document change event. Then, an index to correlate a context element of the context to a document of the document change event may be stored.

Abstract: Systems, apparatuses and technology-based methods may provide for generating a graphic representation of a time sorted list of intents and presenting the graphic representation in a perimeter region of a watch face. In addition, a timeline associated with the graphic representation may align with an hour hand of the watch face. In one example, the graphic representation distinguishes between types of intents, shows a start time and end time of one or more intents and shows a status of one or more intents.

Abstract: Systems, apparatuses and methods may provide for identifying a plurality of user intents and identifying user state data. Additionally, a time sorted list of intents may be generated based on the plurality of user intents and the user state data, wherein the time sorted list of intents defines a user route with respect to a particular day. In one example, the sorted list of intents is dynamically updated in response to a change in the user state data, a change in the plurality of user intents and/or a conflict between two or more of the plurality of user intents.

Abstract: Systems, apparatuses and methods may provide for a mouth proximity detection system to be used with a device, such as a wearable device, to determine when to activate (and/or deactivate) a voice-activated circuit on the device. Embodiments may utilize three layers of analysis to make the determination, including a layer to analyze motion, a layer to detect a mouth of a user, and a layer to fuse the layers in a power saving arrangement to determine proximity of the device to the mouth of the user and to determine whether to activate a voice-activated circuit on the device.

Abstract: When a call or message is received from an unidentified sender on the user's communication device, the caller identifier application launches a text-based messaging application and causes it to send an “invisible” text-based message to the user's contacts. The message includes the metadata (e.g., telephone number) associated with the call or message that the user received. The invisible message is a short message whose headers are programmed in a particular manner so that the receiving mobile phone acknowledges the receipt of the message and the receiving mobile phone displays no behavior perceptible by the user. When the invisible message is received by the corresponding caller identifier application on one of the user's contact's mobile phone, the application searches the contact's contact list maintained in his or hers contact application. If the metadata provided to the contact's mobile phone is located in the contact list, the contact details (e.g.

Abstract: When a call or message is received from an unidentified sender on the user's communication device, the caller identifier application launches a text-based messaging application and causes it to send an “invisible” text-based message to the user's contacts. The message includes the metadata (e.g., telephone number) associated with the call or message that the user received. The invisible message is a short message whose headers are programmed in a particular manner so that the receiving mobile phone acknowledges the receipt of the message and the receiving mobile phone displays no behavior perceptible by the user. When the invisible message is received by the corresponding caller identifier application on one of the user's contact's mobile phone, the application searches the contact's contact list maintained in his or hers contact application. If the metadata provided to the contact's mobile phone is located in the contact list, the contact details (e.g.

Abstract: When a call or message is received from an unidentified sender on the user's communication device, the caller identifier application launches a text-based messaging application and causes it to send an “invisible” text-based message to the user's contacts. The message includes the metadata (e.g., telephone number) associated with the call or message that the user received. The invisible message is a short message whose headers are programmed in a particular manner so that the receiving mobile phone acknowledges the receipt of the message and the receiving mobile phone displays no behavior perceptible by the user. When the invisible message is received by the corresponding caller identifier application on one of the user's contact's mobile phone, the application searches the contact's contact list maintained in his or hers contact application. If the metadata provided to the contact's mobile phone is located in the contact list, the contact details (e.g.

Abstract: When a call or message is received from an unidentified sender on the user's communication device, the caller identifier application launches a text-based messaging application and causes it to send an “invisible” text-based message to the user's contacts. The message includes the metadata (e.g., telephone number) associated with the call or message that the user received. The invisible message is a short message whose headers are programmed in a particular manner so that the receiving mobile phone acknowledges the receipt of the message and the receiving mobile phone displays no behavior perceptible by the user. When the invisible message is received by the corresponding caller identifier application on one of the user's contact's mobile phone, the application searches the contact's contact list maintained in his or hers contact application. If the metadata provided to the contact's mobile phone is located in the contact list, the contact details (e.g.

Abstract: When a call or message is received from an unidentified sender on the user's communication device, the caller identifier application launches a text-based messaging application and causes it to send an “invisible” text-based message to the user's contacts. The message includes the metadata (e.g., telephone number) associated with the call or message that the user received. The invisible message is a short message whose headers are programmed in a particular manner so that the receiving mobile phone acknowledges the receipt of the message and the receiving mobile phone displays no behavior perceptible by the user. When the invisible message is received by the corresponding caller identifier application on one of the user's contact's mobile phone, the application searches the contact's contact list maintained in his or hers contact application. If the metadata provided to the contact's mobile phone is located in the contact list, the contact details (e.g.

Abstract: When a call or message is received from an unidentified sender on the user's communication device, the caller identifier application launches a text-based messaging application and causes it to send an “invisible” text-based message to the user's contacts. The message includes the metadata (e.g., telephone number) associated with the call or message that the user received. The invisible message is a short message whose headers are programmed in a particular manner so that the receiving mobile phone acknowledges the receipt of the message and the receiving mobile phone displays no behavior perceptible by the user. When the invisible message is received by the corresponding caller identifier application on one of the user's contact's mobile phone, the application searches the contact's contact list maintained in his or hers contact application. If the metadata provided to the contact's mobile phone is located in the contact list, the contact details (e.g.