Abstract: A file access request is received from an application. One or more file types for the file access request are identified, and one or more file hosts supporting files of the identified one or more file types are also identified. A user interface is displayed, the user interface including a hosted area. Within the hosted area, at least one of the one or more file hosts displays a portion of the user interface identifying one or more files of at least one file host that can be selected for retrieval, or one or more locations that can be selected to which the one or more files are saved.

Abstract: A file access request is received from an application. One or more file types for the file access request are identified, and one or more file hosts supporting files of the identified one or more file types are also identified. A user interface is displayed, the user interface including a hosted area. Within the hosted area, at least one of the one or more file hosts displays a portion of the user interface identifying one or more files of at least one file host that can be selected for retrieval, or one or more locations that can be selected to which the one or more files are saved.

Abstract: A system level search user interface that includes both a data entry portion and a search identification portion is displayed. Data input by a user as a search term is displayed in the data entry portion, and identifiers of each of one or more scopes on the computing device that can be searched using the search term are displayed in the search identification portion. Search results based on a selected scope are displayed in a search results portion of the system level search user interface. A set of keyboard shortcuts allow users to quickly search using any of the scopes, and see previews of a number of results that each of the scopes return. Additionally, the system level search user interface allow users to easily focus on different search result entries, and efficiently change scopes for searching.

Abstract: A file access request is received from an application. One or more file types for the file access request are identified, and one or more file hosts supporting files of the identified one or more file types are also identified. A user interface is displayed, the user interface including a hosted area. Within the hosted area, at least one of the one or more file hosts displays a portion of the user interface identifying one or more files of at least one file host that can be selected for retrieval, or one or more locations that can be selected to which the one or more files are saved.

Abstract: A file access request is received from an application. One or more file types for the file access request are identified, and one or more file hosts supporting files of the identified one or more file types are also identified. A user interface is displayed, the user interface including a hosted area. Within the hosted area, at least one of the one or more file hosts displays a portion of the user interface identifying one or more files of at least one file host that can be selected for retrieval, or one or more locations that can be selected to which the one or more files are saved.

Abstract: This document describes techniques for presenting a resource user interface. These techniques present, in a summary section of a user interface, multiple selectable resource tiles that each include real-time and/or static information corresponding to one of multiple resources of a computing device. Each of the multiple selectable resource tiles are presented simultaneously, which enables a user to compare live, real-time resource usage for different resources of the computing device. Further, these techniques present, in a detailed view section of the user interface, additional real-time resource information and/or a real-time resource graph corresponding to a selected one of the multiple resources.

Abstract: Various embodiments for process relationship management are described. In at least some embodiments, a user interface is presented that provides an integrated view of processes that are running on a computing device and relationships between the processes. For example, the user interface can display a visual indication that a first process is related to a second process and that if a user closes the first process, the second process will also close as a result. Further to one or more embodiments, the user interface can display status messages regarding processes, such as that a process is not responding to a request to close or that a process is waiting on user input.

Abstract: A system level search user interface that includes both a data entry portion and an application identification portion is displayed. User data input as a search term is displayed in the data entry portion, and identifiers of each of one or more applications of multiple applications on the computing device that can be searched using the search term are displayed in the application identification portion. The search term is provided to one application of the multiple applications for that one application to generate and display search results based on the search term while the display of at least the data entry portion of the system level search user interface is maintained.

Abstract: A file access request is received from an application. One or more file types for the file access request are identified, and one or more file hosts supporting files of the identified one or more file types are also identified. A user interface is displayed, the user interface including a hosted area. Within the hosted area, at least one of the one or more file hosts displays a portion of the user interface identifying one or more files of at least one file host that can be selected for retrieval, or one or more locations that can be selected to which the one or more files are saved.

Abstract: Two different process management views can be displayed, and a user can request to switch between the two views. The user can select a process in either view and have the selected process terminated. One view is a simplified view that identifies processes and whether they are non-responsive. The other view is an expanded view that identifies processes and the amount of various system resources used by each of those processes. Various additional information can be displayed in the expanded view, such as identifiers of various windows, tabs, and/or services associated with each of the processes.

Abstract: A file access request is received from an application. One or more file types for the file access request are identified, and one or more file hosts supporting files of the identified one or more file types are also identified. A user interface is displayed, the user interface including a hosted area. Within the hosted area, at least one of the one or more file hosts displays a portion of the user interface identifying one or more files of at least one file host that can be selected for retrieval, or one or more locations that can be selected to which the one or more files are saved.

Abstract: File management user interface techniques are described. In one or more implementations, properties of a file are displayed in a user interface by a computing device. In response to selection of a particular one of the properties in the user interface, one or more representations of one or more other files that include a corresponding value of the particular property are displayed, respectively, of the file.

Abstract: This document describes techniques and apparatuses for managing an immersive environment. These techniques and/or apparatuses enable a user to select when, where, or under what conditions to present applications in this immersive environment.

Abstract: Collection user interface techniques are described. In one or more implementations, a plurality of inputs are recognized as gestures received via interaction with a user interface to navigate through a file system of a computing device and select representations of objects managed by file system of the computing device, at least two of which are accessible via different devices. In response, copies of the representations are displayed by the computing device in a collection portion of the user interface. An option is output in conjunction with the collection portion by the computing device that is selectable to initiate a command to be performed using the objects that have corresponding representations included in the collection portion.

Abstract: Collection user interface techniques are described. In one or more implementations, a plurality of inputs are recognized as gestures received via interaction with a user interface to navigate through a file system of a computing device and select representations of objects managed by file system of the computing device, at least two of which are accessible via different devices. In response, copies of the representations are displayed by the computing device in a collection portion of the user interface. An option is output in conjunction with the collection portion by the computing device that is selectable to initiate a command to be performed using the objects that have corresponding representations included in the collection portion.

Abstract: This document describes techniques for presenting a resource user interface. These techniques present, in a summary section of a user interface, multiple selectable resource tiles that each include real-time and/or static information corresponding to one of multiple resources of a computing device. Each of the multiple selectable resource tiles are presented simultaneously, which enables a user to compare live, real-time resource usage for different resources of the computing device. Further, these techniques present, in a detailed view section of the user interface, additional real-time resource information and/or a real-time resource graph corresponding to a selected one of the multiple resources.

Abstract: Semantic zoom techniques are described. In one or more implementations, techniques are described that may be utilized by a user to navigate to content of interest. These techniques may also include a variety of different features, such as to support semantic swaps and zooming “in” and “out.” These techniques may also include a variety of different input features, such as to support gestures, cursor-control device, and keyboard inputs. A variety of other features are also supported as further described in the detailed description and figures.

Abstract: Various embodiments for process relationship management are described. In at least some embodiments, a user interface is presented that provides an integrated view of processes that are running on a computing device and relationships between the processes. For example, the user interface can display a visual indication that a first process is related to a second process and that if a user closes the first process, the second process will also close as a result. Further to one or more embodiments, the user interface can display status messages regarding processes, such as that a process is not responding to a request to close or that a process is waiting on user input.

Abstract: Two different process management views can be displayed, and a user can request to switch between the two views. The user can select a process in either view and have the selected process terminated. One view is a simplified view that identifies processes and whether they are non-responsive. The other view is an expanded view that identifies processes and the amount of various system resources used by each of those processes. Various additional information can be displayed in the expanded view, such as identifiers of various windows, tabs, and/or services associated with each of the processes.

Abstract: A file access request is received from an application. One or more file types for the file access request are identified, and one or more file hosts supporting files of the identified one or more file types are also identified. A user interface is displayed, the user interface including a hosted area. Within the hosted area, at least one of the one or more file hosts displays a portion of the user interface identifying one or more files of at least one file host that can be selected for retrieval, or one or more locations that can be selected to which the one or more files are saved.