Patent ID: 12248657

DETAILED DESCRIPTION

The techniques enhance file management applications by introducing expanded folder previews and supplementary user interface elements to streamline the user experience. In the context of the present disclosure, a file is any computing resource for recording digital data such as text, images, video, program code, and so forth. Accordingly, one or several files can be organized into a folder. Furthermore, a folder can itself contain other folders which can in turn contain individual files. Conversely, a folder can also be left empty.

As mentioned above, files and folders belonging to a user can be distributed across many different contexts. For instance, some files and/or folders can be stored locally on the user's computing device. Other files and/or folders can be stored in a cloud storage service which the user can access through a network connection. Still other files and/or folders can be stored in a collaborative environment in which multiple users have access subject to permissions and data safety protocols. As a result, modern file management applications often provide disjointed and cumbersome user experiences.

In contrast, the expanded folder previews serve to streamline the user experience of file management applications by enabling a user to interact with files within a folder without navigating into the folder itself. Stated another way, the user can visually expand the folder in the user interface to display some or all of the files within without transitioning away from the user interface. In this way, the user can interact with several folders at the same time as well as across different contexts (e.g., local and cloud). Consequently, operations that typically involved several user inputs and different user interfaces are streamlined to a single user interface that can dynamically adapt to the needs of a user.

Various examples, scenarios, and aspects that enable the techniques herein are described below with respect toFIGS.1-7.

FIG.1illustrates a system100in which a computing device102provides a file manager application104with a user interface106for interacting with a file system108. In various examples, the file system108is a process and data structure implemented by an operating system for controlling data storage and retrieval. Accordingly, the file system108can define various file contexts110A—110C. For example, the file context110A can be local context containing folders112A that are stored locally on the computing device102. Conversely, the file context110B can be a cloud context containing folders112B that are stored remotely (e.g., in a datacenter) and accessed by the computing device102over a network connection in association with an account belonging to the computing device102and/or a user of the computing device102. In still another example, the file context110C can be a collaborative context containing folders112C that, like the cloud file context110B, are stored remotely but are accessible by multiple users and/or multiple computing devices. For instance, the folders112C can contain work documents that a team of users work on together. It should be understood that while only three file contexts110A-110C are illustrated, the file system108can include any number of file contexts110.

Since modern file systems often span multiple file contexts, the file manager application104described herein provides the user interface106that offers a smooth and intuitive user experience. That is, the user interface106can be configured to display an expanded folder preview114in response to a user input116A selecting from a list of folders112A in a file context110A. It should be understood that the user input116A does not navigate into the folder112A. Stated another way, the system100adapts the existing user interface106in response to the user input116A. In contrast, navigating into the folder112A involves generating a different user interface to display the contents of the folder112A.

As will be elaborated upon below, expanded folder preview114can be a visual expansion of the selected folder112A that displays various files118stored within the selected folder112A. In addition to the files118, a folder112A can also include additional subfolders120which are also displayed in the expanded folder preview114. In various examples, individual files118and subfolders120can be presented using corresponding user interface elements to form a list within the expanded folder preview114. Furthermore, the expanded folder preview114can include supplementary UI elements122which accompany the files118and subfolders120.

The supplementary UI elements122can be customized, both visually and functionally, based on the file context110A of the associated folder112A. For example, in a collaborative file context110C, a supplementary UI element122for a file118can display user access indicators to identify other users who have access to the file. Moreover, the user access indicators can be configured to display the most recent users who opened the file, new users who have been added to collaborate on the file, a timestamp for the most recent changes, and so forth. In this way, the user experience is clearly differentiated and enhanced for different file contexts110. In addition, the expanded folder preview114enables various contextual actions124that can be triggered with another user input116B. For example, a user can open an expanded folder preview114for a first folder112A and a second folder112B within the user interface106. In this scenario, the user can then perform a contextual action124by transferring a file118from the first folder112A to the second folder112B with a single user input116B. In another example, the user may perform a contextual action124by uploading a file118from a local file context110A to a cloud file context110B. In response to the contextual action124, the supplementary UI element122associated with the file118can change to visually indicate the upload contextual action124.

Turning now toFIG.2, aspects of a user interface202for enabling simultaneous interaction with multiple folders and contextual actions are shown and described. As mentioned above, the file system108and the file manager application104span multiple file contexts110. For example, as shown inFIG.2, the user interface202can enable a user to access a “local” file context204and a “cloud” file context206. Each of the “local” file context204and the “cloud” file context206can respectively contain folders. For example, the “local” file context204contains a “designs” folder208and a “files” folder210. Similarly, the “cloud” file context206contains a “templates” folder212.

In various examples, a user can utilize a cursor214to interact with the user interface202. For instance, the user can select an expansion icon216at the “designs” folder208with the cursor214to cause a display of an expanded folder preview218A which visually expands the associated “designs” folder208within the user interface202. The expanded folder preview218A displays some or all of the contents of the associated “designs” folder208. For example, the expanded folder preview218A includes an “inspiration.jpg” file220, a “style guide.txt” file222, a “visual.png” file224, and a “photo.jpg” file226. Similarly, the expanded folder preview218B displays a “form” file228, a “grid” file230, and a “temp” subfolder232. In addition, a user can optionally leave some folders unexpanded such as the “files” folder210. It should be understood that while a cursor214is illustrated, any suitable input method can be utilized to interact with the user interface202such as a touch input, a pointing device, a gesture input, and so forth.

Using the expanded folder previews218A and218B, a user can perform various contextual actions. For example, the user can transfer files from multiple folders at the same time. As shown, the user can utilize the cursor214to select a first file, the “style guide.txt” file222in the “designs” folder208and a second file, the “grid” file230in the “templates” folder212as indicated by the shading. Subsequently, the user can transfer the selected “style guide.txt” file222and the “grid” file230from their original file contexts—the “local” file context204and the “cloud” file context206respectively—to a “working folder”234within a “collaborative” file context236. In this way, the expanded folder previews218A and218B enable simultaneous interaction with multiple folders distributed across multiple file contexts within a single user interface202thereby streamlining the user experience and improving efficiency.

Turning now toFIG.3, aspects of a user interface302for streamlining the user experience when utilizing search features in a file manager application are shown and described. Using a search bar304, a user can input a search string306to surface folders and/or files across various file contexts that match a query represented by the search string306. As shown inFIG.3, a user inputs a “design document” search string306. In response, folders and files matching some or all of the search string306are displayed in the user interface302. As shown, a “designs” folder308can be displayed with an expanded folder preview310. Accordingly, files within the “designs” folder308that match the search string306may also be displayed. For instance, a “design document” file312, a “design.txt” file314, and an “alt design”316contained within the “designs” folder308are displayed in the expanded folder preview310. In addition, the expanded folder preview310can also include a “see more” option318to display the full contents of the “designs” folder308. In various examples, the “see more” option318can be displayed due to the number of files contained in the associated “designs” folder308exceeds what can be displayed in the expanded folder preview310.

Furthermore, the files312-318that are displayed in the expanded folder preview310can be selected and ranked based on a relevance to the search string306. For instance, the “design document” file312is displayed first in the expanded folder preview310due to its exact match to the search string306. In addition, an enlarged content preview320displaying a large rendering of the file data of the “design document” file312is also displayed. The enlarged content preview320in combination with the high relative position of the “design document” file312within the expanded folder preview310can serve to increase the visual emphasis of files matching the search string306and direct user attention. Other files such as the “alt design.png” file316can be displayed with a minimized content preview322displaying a rendering of the file data of the “alt design” file316that is reduced in size relative to the enlarged content preview320.

In addition, other files within other folders such as the “design template” file324in the “templates” folder326and the “admin document” file328in the “files” folder330that satisfy some or all of the search string306can be displayed as search results. However, due to a reduced relevance to the search string306in relation to the “design document” file312, the “design template” file324and the “admin document” file328can be displayed in a similar manner to the “alt design.png” file316with a minimized content preview322. Moreover, folders such as the “templates” folder326and the “files” folder330can be placed successively to the right of the “designs” folder308within the user interface302. In this way, results that are the most relevant to the search string306can be displayed first in an ordered list of results such as the one shown inFIG.3to draw attention to relevant results thereby improving efficiency and productivity.

Turning now toFIG.4A, aspects of an example user interface402illustrating customized folder previews are shown and described. As mentioned above with respect toFIG.1, various supplementary UI elements122can be customized based on the file context110A to differentiate the user experience of expanded folder previews114across different file contexts110. For example, as shown inFIG.4A, a local folder preview404can include a local supplementary UI element406. The local supplementary UI element406provides a preview rendering of the file data for an associated file such as the “inspiration.jpg” file408. In various examples, the local supplementary UI element406can be configured to match a file type within the local folder preview404. For instance, the “inspiration.jpg” file408can be an image file type. In response to detecting the image file type, the local supplementary UI element406can be configured as an image rendering of the file data for the “inspiration.jpg” file408. In another example, a “style guide.txt” file410can be a text file type. Accordingly, a local supplementary UI element for the “style guide.txt” file410can display a preview of the text data within the “style guide.txt” file410. Alternatively, the local supplementary UI element for the “style guide.txt” file410can be an icon visually indicating the text file type.

In another example of customizable folder previews, a collaborative folder preview412can include a collaborative supplementary UI element414. The collaborative supplementary UI element414can be a user access indicator (e.g., a profile picture icon) indicating various users who have access to an associated file in a collaborative file context. For example, the collaborative supplementary UI element414can indicate that greater than twenty users have access to a “form” file416. In addition, files presented in the collaborative folder preview412can be sorted using various criteria. In one example, the collaborative folder preview412can be sorted based on a number of users that have access to a file. Accordingly, the “form” file416is displayed above the “grid” file418due to the greater number of users that have access. Alternatively, files in the collaborative folder412can be sorted based on a priority associated with the file and/or users who have access to the file. For example, a new batch of users may have been recently added to the “form” file416. In response, the “form” file416can be displayed first to make a user aware of new collaborators. Conversely, a user may have been newly added by a file owner to an existing file such as the “form” file416. Accordingly, the “form” file416can be displayed first in the collaborative folder preview412to inform the user of their new file access.

In still another example of the customizable folder previews, a cloud folder preview420can include a cloud supplementary UI element422. In various examples, the cloud supplementary UI element422can indicate a timestamp of the most recent changes to an associated file. For instance, the cloud supplementary UI element422shows that the “budget” file424was last edited two hours ago while the “admin document” file426was last edited four hours ago. Files within the cloud folder preview420can be sorted based on a time of the most recent modification and/or addition. For instance, the “budget” file424can be displayed ahead of the “admin document” file426due to the more recent time of last modification.

Moreover, regardless of file context, a folder that does not contain any files such as the “miscellaneous” folder428can include an empty folder indicator430. In this way, a user can save time by seeing a folder is empty without navigating into the folder itself thereby streamlining the user experience. It should be understood that all of the local folder preview404, the collaborative folder preview412, and the cloud folder preview420can be displayed concurrently in the same user interface402. Consequently, a user can access file distributed across a plurality of file contexts and simultaneously interact with different folder previews404,412,420and associated supplementary UI elements406,414, and422.

Proceeding toFIG.4Badditional aspects of customizable supplementary UI elements are shown and described. As mentioned above, various supplementary UI elements can dynamically adapt over time (T) in response to contextual actions initiated by a user. For example, a use can initiate a file upload contextual action432within a “collaborative” file context434. For example, a user can upload an “inspiration.jpg” file436to a “designs” folder438. In response to the file upload contextual action432, an upload progress supplementary UI element440can be displayed alongside the “inspiration.jpg” file436. The upload progress supplementary UI element440can include a progress bar and uploaded file size to visually indicate progress as well as an estimated time remaining to complete the file upload contextual action432.

However, due to the multi-user nature of the “collaborative” file context434, the designs folder438may be a public folder which can be accessible by any number of users (e.g., within a team, within a company). Accordingly, in response to the file upload contextual action432, an upload location warning442can be displayed to inform the user that the “insipiration.jpg” file436is being uploaded to a public folder. Upon receiving a user confirmation444, the file upload can continue. Conversely, the user confirmation444be denied by the user. In response, the file upload can be terminated.

In some examples, the “inspiration.jpg” file436may already exist in the “designs” folder438. For instance, a different user may have previously uploaded a “inspiration.jpg” file. Upon detecting a file name that matches “inspiration.jpg” file436within the “designs” folder a replacement notification446can be displayed to query whether a user wishes to skip and terminate the file upload contextual action432or replace the existing file with the “inspiration.jpg” file436and continue the upload. Accordingly, the user can provide a user selection448responsive to the replacement notification446. As shown, the user interface402, by utilizing various supplementary UI elements such as the upload progress supplementary UI element440, the upload location warning442, and the replacement notification446can dynamically adapt over time (T) in response to a contextual action. It should be understood that while the example shown and discussed with respect toFIG.4Bpertain to a specific file upload contextual action432, the user interface402can adapt to response to any type of action within a file context.

Proceeding toFIG.5, aspects of a routine500for enabling expanded folder previews are shown and described. With reference toFIG.5, the routine500begins at operation502where a system displays a plurality of user elements representing a corresponding plurality of folders distributed across a plurality of file contexts in a file manager user interface.

Next, at operation504, the system receives a user input at the file manager user interface selecting a folder from the plurality of folders. The user input does not navigate into the selected folder. That is, the file manager user interface that displays the plurality of folders does not transition, or switch, to a different file manager user interface that displays the content of a single folder.

Then, at operation506, in response to the user input, the system displays a visual expansion of the selected folder comprising a user interface element representing a content item of the folder (e.g., files, subfolders).

Next, at operation508, the system determines a file context of the folder that was selected by the user input.

Finally, at operation510, the system generates a supplementary user interface element based on the file context that is displayed concurrently with the user interface element representing a content of the folder (e.g., files, subfolders).

For ease of understanding, the processes discussed in this disclosure are delineated as separate operations represented as independent blocks. However, these separately delineated operations should not be construed as necessarily order dependent in their performance. The order in which the process is described is not intended to be construed as a limitation, and any number of the described process blocks may be combined in any order to implement the process or an alternate process. Moreover, it is also possible that one or more of the provided operations is modified or omitted.

The particular implementation of the technologies disclosed herein is a matter of choice dependent on the performance and other requirements of a computing device. Accordingly, the logical operations described herein are referred to variously as states, operations, structural devices, acts, or modules. These states, operations, structural devices, acts, and modules can be implemented in hardware, software, firmware, in special-purpose digital logic, and any combination thereof. It should be appreciated that more or fewer operations can be performed than shown in the figures and described herein. These operations can also be performed in a different order than those described herein.

It also should be understood that the illustrated methods can end at any time and need not be performed in their entireties. Some or all operations of the methods, and/or substantially equivalent operations, can be performed by execution of computer-readable instructions included on a computer-storage media, as defined below. The term “computer-readable instructions,” and variants thereof, as used in the description and claims, is used expansively herein to include routines, applications, application modules, program modules, programs, components, data structures, algorithms, and the like. Computer-readable instructions can be implemented on various system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, combinations thereof, and the like.

Thus, it should be appreciated that the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as states, operations, structural devices, acts, or modules. These operations, structural devices, acts, and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof.

For example, the operations of the routine500can be implemented, at least in part, by modules running the features disclosed herein can be a dynamically linked library (DLL), a statically linked library, functionality produced by an application programing interface (API), a compiled program, an interpreted program, a script, or any other executable set of instructions. Data can be stored in a data structure in one or more memory components. Data can be retrieved from the data structure by addressing links or references to the data structure.

Although the illustration may refer to the components of the figures, it should be appreciated that the operations of the routine500may be also implemented in other ways. In addition, one or more of the operations of the routine500may alternatively or additionally be implemented, at least in part, by a chipset working alone or in conjunction with other software modules. In the example described below, one or more modules of a computing system can receive and/or process the data disclosed herein. Any service, circuit, or application suitable for providing the techniques disclosed herein can be used in operations described herein.

FIG.6shows additional details of an example computer architecture600for a device, such as a computer or a server configured as part of the cloud-based platform or system100, capable of executing computer instructions (e.g., a module or a program component described herein). The computer architecture600illustrated inFIG.6includes processing system602, a system memory604, including a random-access memory606(RAM) and a read-only memory (ROM)608, and a system bus610that couples the memory604to the processing system602. The processing system602comprises processing unit(s). In various examples, the processing unit(s) of the processing system602are distributed. Stated another way, one processing unit of the processing system602may be located in a first location (e.g., a rack within a datacenter) while another processing unit of the processing system602is located in a second location separate from the first location.

Processing unit(s), such as processing unit(s) of processing system602, can represent, for example, a CPU-type processing unit, a GPU-type processing unit, a field-programmable gate array (FPGA), another class of digital signal processor (DSP), or other hardware logic components that may, in some instances, be driven by a CPU. For example, illustrative types of hardware logic components that can be used include Application-Specific Integrated Circuits (ASICs), Application-Specific Standard Products (ASSPs), System-on-a-Chip Systems (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.

A basic input/output system containing the basic routines that help to transfer information between elements within the computer architecture600, such as during startup, is stored in the ROM608. The computer architecture600further includes a mass storage device612for storing an operating system614, application(s)616, modules618, and other data described herein.

The mass storage device612is connected to processing system602through a mass storage controller connected to the bus610. The mass storage device612and its associated computer-readable media provide non-volatile storage for the computer architecture600. Although the description of computer-readable media contained herein refers to a mass storage device, the computer-readable media can be any available computer-readable storage media or communication media that can be accessed by the computer architecture600.

Computer-readable media includes computer-readable storage media and/or communication media. Computer-readable storage media includes one or more of volatile memory, nonvolatile memory, and/or other persistent and/or auxiliary computer storage media, removable and non-removable computer storage media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Thus, computer storage media includes tangible and/or physical forms of media included in a device and/or hardware component that is part of a device or external to a device, including RAM, static RAM (SRAM), dynamic RAM (DRAM), phase change memory (PCM), ROM, erasable programmable ROM (EPROM), electrically EPROM (EEPROM), flash memory, compact disc read-only memory (CD-ROM), digital versatile disks (DVDs), optical cards or other optical storage media, magnetic cassettes, magnetic tape, magnetic disk storage, magnetic cards or other magnetic storage devices or media, solid-state memory devices, storage arrays, network attached storage, storage area networks, hosted computer storage or any other storage memory, storage device, and/or storage medium that can be used to store and maintain information for access by a computing device.

In contrast to computer-readable storage media, communication media can embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism. As defined herein, computer storage media does not include communication media. That is, computer-readable storage media does not include communications media consisting solely of a modulated data signal, a carrier wave, or a propagated signal, per se.

According to various configurations, the computer architecture600may operate in a networked environment using logical connections to remote computers through the network620. The computer architecture600may connect to the network620through a network interface unit622connected to the bus610. The computer architecture600also may include an input/output controller624for receiving and processing input from a number of other devices, including a keyboard, mouse, touch, or electronic stylus or pen. Similarly, the input/output controller624may provide output to a display screen, a printer, or other type of output device.

The software components described herein may, when loaded into the processing system602and executed, transform the processing system602and the overall computer architecture600from a general-purpose computing system into a special-purpose computing system customized to facilitate the functionality presented herein. The processing system602may be constructed from any number of transistors or other discrete circuit elements, which may individually or collectively assume any number of states. More specifically, the processing system602may operate as a finite-state machine, in response to executable instructions contained within the software modules disclosed herein. These computer-executable instructions may transform the processing system602by specifying how the processing system602transition between states, thereby transforming the transistors or other discrete hardware elements constituting the processing system602.

FIG.7depicts an illustrative distributed computing environment700capable of executing the software components described herein. Thus, the distributed computing environment700illustrated inFIG.7can be utilized to execute any aspects of the software components presented herein. For example, the distributed computing environment700can be utilized to execute aspects of the software components described herein.

Accordingly, the distributed computing environment700can include a computing environment702operating on, in communication with, or as part of the network704. The network704can include various access networks. One or more client devices706A-706N (hereinafter referred to collectively and/or generically as “computing devices706”) can communicate with the computing environment702via the network704. In one illustrated configuration, the computing devices706include a computing device706A such as a laptop computer, a desktop computer, or other computing device; a slate or tablet computing device (“tablet computing device”)706B; a mobile computing device706C such as a mobile telephone, a smart phone, or other mobile computing device; a server computer706D; and/or other devices706N. It should be understood that any number of computing devices706can communicate with the computing environment702.

In various examples, the computing environment702includes servers708, data storage710, and one or more network interfaces712. The servers708can host various services, virtual machines, portals, and/or other resources. In the illustrated configuration, the servers708host virtual machines714, Web portals716, mailbox services718, storage services720, and/or social networking services722. As shown inFIG.7the servers708also can host other services, applications, portals, and/or other resources (“other resources”)724.

As mentioned above, the computing environment702can include the data storage710. According to various implementations, the functionality of the data storage710is provided by one or more databases operating on, or in communication with, the network704. The functionality of the data storage710also can be provided by one or more servers configured to host data for the computing environment700. The data storage710can include, host, or provide one or more real or virtual datastores726A-726N (hereinafter referred to collectively and/or generically as “datastores726”). The datastores726are configured to host data used or created by the servers808and/or other data. That is, the datastores726also can host or store web page documents, word documents, presentation documents, data structures, algorithms for execution by a recommendation engine, and/or other data utilized by any application program. Aspects of the datastores726may be associated with a service for storing files.

The computing environment702can communicate with, or be accessed by, the network interfaces712. The network interfaces712can include various types of network hardware and software for supporting communications between two or more computing devices including the computing devices and the servers. It should be appreciated that the network interfaces712also may be utilized to connect to other types of networks and/or computer systems.

It should be understood that the distributed computing environment700described herein can provide any aspects of the software elements described herein with any number of virtual computing resources and/or other distributed computing functionality that can be configured to execute any aspects of the software components disclosed herein. According to various implementations of the concepts and technologies disclosed herein, the distributed computing environment700provides the software functionality described herein as a service to the computing devices. It should be understood that the computing devices can include real or virtual machines including server computers, web servers, personal computers, mobile computing devices, smart phones, and/or other devices. As such, various configurations of the concepts and technologies disclosed herein enable any device configured to access the distributed computing environment700to utilize the functionality described herein for providing the techniques disclosed herein, among other aspects.

The disclosure presented herein also encompasses the subject matter set forth in the following clauses.

Example Clause A, a method comprising: displaying a plurality of user interface elements representing an associated plurality of folders distributed across a plurality of file contexts in a file manager user interface; receiving a user input indicating a selection of a folder from the plurality of folders; in response to the user input, displaying a visual expansion of the folder comprising a user interface element representing a content item within the folder; determining a file context of the folder selected by the user input; and generating a supplementary user interface element based on the file context of the folder that is displayed concurrently with the user interface element representing the content within the folder.

Example Clause B, the method of Example Clause A, wherein the user input does not navigate into the folder such that the file manager user interface does not transition to a different file manager user interface that displays content items of a single folder.

Example Clause C, the method of Example Clause A or Example Clause B, wherein the user input comprises a hover gesture that satisfies a threshold hover time.

Example Clause D, the method of Example Clause A or Example Clause B, wherein the user input comprises a click input to expand the folder.

Example Clause E, the method of any one of Example Clause A through D, wherein: the file context of the folder is a cloud storage file context; and the supplementary user interface element is a change time indicator.

Example Clause F, the method of any one of Example Clause A through D, wherein: the file context of the folder is a collaborative file context; and the supplementary user interface element is a user access indicator.

Example Clause G, the method of any one of Example Clause A through F, further comprising: receiving a second user input selecting a second folder from the plurality of folders; and receiving a third user input indicating a movement of a first file from the folder and a second file from the second folder to a third folder from the plurality of folders.

Example Clause H, the method of any one of Example Clause A through G, wherein: the folder does not contain content; and the user interface element indicates an empty status of the folder.

Example Clause I, a system comprising: a processing unit; a computer-readable medium having encoded thereon computer-readable instructions that, when executed by the processing unit, cause the system to: display a plurality of user interface elements representing an associated plurality of folders distributed across a plurality of file contexts in a file manager user interface; receive a user input indicating a selection of a folder from the plurality of folders; in response to the user input, display a visual expansion of the folder comprising a user interface element representing a content item within the folder; determine a file context of the folder selected by the user input; and generate a supplementary user interface element based on the file context of the folder that is displayed concurrently with the user interface element representing the content item within the folder.

Example Clause J, the system of Example Clause I, wherein the user input does not navigate into the folder such that the file manager user interface does not transition to a different file manager user interface that displays content items of a single folder.

Example Clause K, the system of Example Clause I or Example Clause J, wherein the user input comprises a hover gesture that satisfies a threshold hover time.

Example Clause L, the system of Example Clause I or Example Clause J, wherein the user input comprises a click input to expand the folder.

Example Clause M, the system of any one of Example Clause I through L, wherein: the file context of the folder is a cloud storage file context; and the supplementary user interface element is a change time indicator.

Example Clause N, the system of any one of Example Clause I through L, wherein: the file context of the folder is a collaborative file context; and the supplementary user interface element is a user access indicator.

Example Clause O, the system of any one of Example Clause I through N, wherein the computer-readable instructions further cause the system to: receive a second user input selecting a second folder from the plurality of folders; and receive a third user input indicating a movement of a first file from the folder and a second file from the second folder to a third folder from the plurality of folders.

Example Clause P, the system of any one of Example Clause I through O, wherein: the folder does not contain content; and the user interface element indicates an empty status of the folder.

Example Clause Q, a computer-readable storage medium having encoded thereon computer-readable instructions that, when executed by a processing unit, causes a system to: display a plurality of user interface elements representing an associated plurality of folders distributed across a plurality of file contexts in a file manager user interface; receive a user input indicating a selection of a folder from the plurality of folders; in response to the user input, display a visual expansion of the folder comprising a user interface element representing a content item within the folder; determine a file context of the folder selected by the user input; and generate a supplementary user interface element based on the file context of the folder that is displayed concurrently with the user interface element representing the content item within the folder.

Example Clause R, the computer-readable storage medium of Example Clause Q, wherein the user input does not navigate into the folder such that the file manager user interface does not transition to a different file manager user interface that displays content items of a single folder.

Example Clause S, the computer-readable storage medium of Example Clause Q or Example Clause R, wherein: the file context of the folder is a cloud storage file context; and the supplementary user interface element is a change time indicator.

Example Clause T, the computer-readable storage medium of Example Clause Q or Example Clause R, wherein: the file context of the folder is a collaboration file context; and the supplementary user interface element is a user access indicator.

Conditional language such as, among others, “can,” “could,” “might” or “may,” unless specifically stated otherwise, are understood within the context to present that certain examples include, while other examples do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that certain features, elements and/or steps are in any way required for one or more examples or that one or more examples necessarily include logic for deciding, with or without user input or prompting, whether certain features, elements and/or steps are included or are to be performed in any particular example. Conjunctive language such as the phrase “at least one of X, Y or Z,” unless specifically stated otherwise, is to be understood to present that an item, term, etc. may be either X, Y, or Z, or a combination thereof.

The terms “a,” “an,” “the” and similar referents used in the context of describing the invention (especially in the context of the following claims) are to be construed to cover both the singular and the plural unless otherwise indicated herein or clearly contradicted by context. The terms “based on,” “based upon,” and similar referents are to be construed as meaning “based at least in part” which includes being “based in part” and “based in whole” unless otherwise indicated or clearly contradicted by context.

In addition, any reference to “first,” “second,” etc. elements within the Summary and/or Detailed Description is not intended to and should not be construed to necessarily correspond to any reference of “first,” “second,” etc. elements of the claims. Rather, any use of “first” and “second” within the Summary, Detailed Description, and/or claims may be used to distinguish between two different instances of the same element (e.g., two different file contexts).

In closing, although the various configurations have been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended representations is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed subject matter.