Skip to content
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

Smooth Search Experience #12233

Open
alperozturk96 opened this issue Dec 5, 2023 · 0 comments
Open

Smooth Search Experience #12233

alperozturk96 opened this issue Dec 5, 2023 · 0 comments
Labels
enhancement feature: search performance: boosters 🚀 Performance improvement opportunities (non-crash related)

Comments

@alperozturk96
Copy link
Collaborator

alperozturk96 commented Dec 5, 2023

Problem

Every time a user wants to search, the app navigates to another fragment, leading to an actual network call for each keyboard tap.

actual_search.mov

Solution

To optimize the search functionality, there's no need to navigate to a different fragment. Instead, we can utilize OCFileListFragment for searching.

As the user starts typing, we can locally filter all files. When the user taps the search button, we can then perform the actual search or we can still make actual network call for each keyboard tap.

We can choose one of these option for provide more better experience for users.

@tobiasKaminsky @AndyScherzinger

@joshtrichards joshtrichards added the performance: boosters 🚀 Performance improvement opportunities (non-crash related) label Dec 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement feature: search performance: boosters 🚀 Performance improvement opportunities (non-crash related)
Projects
None yet
Development

No branches or pull requests

2 participants