Abstract: A shell application feature can include trigger information and logic. During operation, the shell application feature can receive an indicator that a trigger occurred; and, in response to the trigger, initiate its logic. The logic of the shell feature is locally performed to identify whether state, object type, user actions, or a combination thereof, with respect to the application satisfy a success criteria corresponding to behavior that will be a prerequisite for a potential feature that is not yet fully implemented. If the state, object type, user action, or combination thereof satisfies the success criteria, a success notification can be communicated to a feature collection service.

Abstract: A computing device receives a trigger to surface commands. A possible set of commands is identified and broken into categories. A category is surfaced for user interaction.

Abstract: A computing device receives a voice command to perform an action within a document. An interpretation of the voice command is mapped to a set of commands. Disambiguation is automatically performed by conducting a user experience to receive additional information.

Abstract: A computing device receives a trigger to surface commands. A possible set of commands is identified and broken into categories. A category is surfaced for user interaction.

Abstract: A computing device receives voice command inputs from a user. The device obtains a language processing result based on the voice command input. The result includes an intent and a set of arguments. The device also obtains a variety of different types of contextual information. An action is identified based on the intent, the arguments, and the contextual information, and the device then suggests the action by displaying a user selectable input mechanism that can be actuated by the user to perform the action. The device can automatically perform the action as well.

Abstract: A document lens service identifies an end-user targeted to consume a productivity document being authored in a user interface to a productivity application. The service then also identifies a document profile specific to the end-user indicative of a model document for the end-user to consume. While the productivity document is being authored, suggestions may be surfaced in the user interface for aligning the productivity document with the model document.

Abstract: A document lens service identifies a document profile specific to an end-user that is indicative of a model document for the end-user. When a productivity document is opened to be consumed by the end-user in a user interface to a productivity application, the service modifies the productivity document based at least on the document profile to align the productivity document with the model document. The productivity document is then rendered as-modified in the user interface.

Abstract: A computing device receives a trigger to surface commands. A possible set of commands is identified and broken into categories. A category is surfaced for user interaction.

Abstract: A computing device receives voice command inputs from a user. The device obtains a language processing result based on the voice command input. The result includes an intent and a set of arguments. The device also obtains a variety of different types of contextual information. An action is identified based on the intent, the arguments, and the contextual information, and the device then suggests the action by displaying a user selectable input mechanism that can be actuated by the user to perform the action. The device can automatically perform the action as well.

Abstract: A computing device receives a voice command to perform an action within a document. An interpretation of the voice command is mapped to a set of commands. Disambiguation is automatically performed by conducting a user experience to receive additional information.

Abstract: Techniques for an electronic file fetch system are described. A method may comprise sending a request for a roaming file list to a file fetch server from a first client device and receiving the roaming file list from the file fetch server by the first client device. The roaming file list includes a unique identifier associated with an application file stored on a second client device. The unique identifier includes a machine identifier identifying the second client device and a local file path portion identifying the file path of the application file stored on the second client device. Based on the machine state of the second client device as indicated in the roaming file list, the application file stored on the second client device may be downloaded to the first client device. Other embodiments are described and claimed.

Abstract: A rechargeable battery includes an iron electrode comprising carbonyl iron composition dispersed over a fibrous electrically conductive substrate. The carbonyl iron composition includes carbonyl iron and at least one additive. A counter-electrode is spaced from the iron electrode. An electrolyte is in contact with the iron electrode and the counter-electrode such that during discharge. Iron in the iron electrode is oxidized with reduction occurring at the counter-electrode such that an electric potential develops. During charging, iron oxides and hydroxides in the iron electrode are reduced with oxidation occurring at the counter-electrode (i.e., a nickel electrode or an air electrode).

Abstract: Techniques for an electronic file fetch system are described. A method may comprise sending a request for a roaming file list to a file fetch server from a first client device and receiving the roaming file list from the file fetch server by the first client device. The roaming file list includes a unique identifier associated with an application file stored on a second client device. The unique identifier includes a machine identifier identifying the second client device and a local file path portion identifying the file path of the application file stored on the second client device. Based on the machine state of the second client device as indicated in the roaming file list, the application file stored on the second client device may be downloaded to the first client device. Other embodiments are described and claimed.

Abstract: A presentation device selectively renders list data that is synchronized across multiple devices via a centralized or distributed synchronization system. The selective rendering depends on a variety of factors including the identity of the entity (e.g., a user, an organization, a system, a device) accessing the list data and the limitations of the presentation device used to access the list data. The selective rendering may also depend on the service or application through which the resource referenced by each list item can be accessed. Further, when uploading list data to a synchronization system, the list data is pre-filtered according to the storage location of each resource referenced by a list item and/or the service through which each resource referenced by a list item is accessible.

Abstract: Techniques for an electronic file fetch system are described. A method may comprise sending a request for a roaming file list to a file fetch server from a first client device and receiving the roaming file list from the file fetch server by the first client device. The roaming file list includes a unique identifier associated with an application file stored on a second client device. The unique identifier includes a machine identifier identifying the second client device and a local file path portion identifying the file path of the application file stored on the second client device. Based on the machine state of the second client device as indicated in the roaming file list, the application file stored on the second client device may be downloaded to the first client device. Other embodiments are described and claimed.

Abstract: Embodiments of the present disclosure provide a user interface that enables a user to more readily identify and use one or more storage services (e.g., cloud storage services or local storage services) to save, open and/or retrieve documents and other data. Embodiments include receiving user credentials from a user that identify the user and also identify one or more storage services that are available to the user. In response to a request to save a document, a list of available services is provided to the user. In an embodiment, the list of services is provided to the user via a user interface. The user may select a storage service from the list and save the document using the selected service.