Change research behaviour

[Kilian-Perisset]

Hi,
Here is the wanted behaviour of the research :

• When user clicks on "search" icon button (magnifying glass), the files list is cleared and a "search" instruction (like on iOS app) is shown, with something like "Type something to search (2 characters min.)"
• When user types something, 300ms after end of typing (debounce), the term is searched (or early if user press enter on keyboard)
• If user clicks on "X" (cross) on right of field, we return to the original RESEARCH state ("Type something to search [...]")
• If user clicks on arrow/back, it cancels the research and return to the original FILES LIST state.

It has been discussed here : #5000
The "bug part" has been fixed, but the wanted behaviour has to be developed.

So I create this issue to keep the "enhancement" part.

[tobiasKaminsky]

* When user clicks on "search" icon button (magnifying glass), the files list is cleared and a "search" instruction (like on iOS app) is shown, with something like "Type something to search (2 characters min.)"

Jan and me had (way long ago) the idea, to do first a quick filtering on current folder and then show below the result of a search, like it is done web:

(first part with checkboxes are items within the same folder, and below is the real search.)

This way we also provide a good functionality to quickly navigate in large folders.

What do you think? :-)

[JorisBodin]

@tobiasKaminsky
Is the current behavior on the iOS application.
Personally, I don't find it intuitive. The user can easily get lost.
An action must produce only one result. Not two.
Either it's a local search only. Or a global search.

Because it will start to show us the local search result, then a second (following the connection) after the global search result.

So if you want to keep the local search first, the user has to click on another button afterwards to push the global search.
For example at the bottom of the result list: "search my entire cloud".

But I've looked at the others app, it's always a global search and not a local search :)

[Kilian-Perisset]

@tobiasKaminsky
Good evening,

I agree with Joris' comment, the research must be global.
If you use the finder, the windows explorer, and any "Cloud/Drive" app, the research is always global. I've discussed it with a few people, and the behavior I've described is really ideal according to users, UX designers and developers.

However, I'm looking for some kind of approval before starting to work on this behaviour (the urgent thing was to fix the bugs related to the search, and it's done)

[jancborchardt]

I never said the search should not be global. It is – in Files, in our Talk app, we always want global search.

When user clicks on "search" icon button (magnifying glass), the files list is cleared and a "search" instruction (like on iOS app) is shown, with something like "Type something to search (2 characters min.)"

Sorry, this is confusing and an unnecessary blocker, as said in the other issue too. See what we do now in the Talk app – it’s instant search which feels snappy.

The initial search filters the folder to be fast and show the most likely results instantly. But the search is global.

Another thing we can do is how Google Drive does it: Expand the search field and show pre-filter suggestions like:

• PDFs
• Images
• Documents
• Spreadsheets
• And of course recent search terms as well

But even with this: The initial quick filter should always be on the current folder, to have instant quick results while we need to wait for the more detailed search results.