-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unified search: how to display on client #21619
Comments
So my general question regarding unified search on mobile is: Are we the ones who need to provide this? Cause operating systems do all have unified search pretty much. On iOS you can swipe down and search to get results from all different apps, be it files, conversations, contacts, calendar etc. cc @rullzer @ChristophWurst @skjnldsv regarding unified search and @marinofaggiana @Ivansss for iOS. |
Not sure if we are talking about the same…
So my idea was more like: get all search results back from NC, and if possible redirect user to certain app, but stay within NC ecosystem. |
You’re right of course @tobiasKaminsky – that’s what I was missing. :) Your proposal sounds good. When you click on a result e.g. from Deck and you don’t have the Deck mobile app installed, we could have a choice between "Download mobile app" or "Show online"? The "Show online" option would then do the same as what you proposed for Calendar and Contacts:
That leaves one group: Things from Nextcloud you have synced to your phone but where we don’t control the apps, namely Calendars and Contacts. Is it possible there to e.g. check:
|
Not sure, but even if, then we cannot redirect user to this location. |
Results are lister grouped by types. We'll load 5 results max per type initially. Then a button is under it to load the next other 5. |
Let us discuss what and how you see the results of unified search (https://github.com/orgs/nextcloud/projects/38) within mobile.
Search on mobile would work, but depending on the search results we can do different things:
@jancborchardt
The text was updated successfully, but these errors were encountered: