V1 Drives in the file browser

[GabrielaVives]

Here are some use cases for the V1 (simplified version of the previous mockups). In some cases I have designed 2 different solutions that I would like to discuss.

• When no additional drive has been added by the user, the interface would stay the same:

• When 1 or more drives have been added, there are 2 options:

1. The "Local drive" is not explicitly mentioned in the UI. Additional drives are places above folders. The issue here is that the files and folders in the local drive are on the same hierarchical level as the drives, this is not a consistent behaviour and could be confusing.
2. The "local drive" is at the top of the file browser, it also appears in the breadcrumb hierarchy when opened. Here the user would have to click on the "local drive" to access the files and folders that usually appear by default in the file browser.

From a user experience point of view I would say that option 2 is the consistent one.

[DenisaCG]

Thanks for the mockups @GabrielaVives!

As you also mentioned, I think that the second option would make the most sense to the user.

In the first option it can seem as if the local files are somehow part of the last drive or just not belonging. To me it seems that by having the Local Drive specified on the interface there is a smoother integration of the drives with the traditional filebrowser.

As a side note, maybe the Local Drive could be expanded initially, so the user could see the usual files and directories and have a more familiar UI image.

But this is just adding to the user perspective, maybe @HaudinFlorence , @fcollonval or @afshin could add more from the technical side of what is possible on the frontend :)