Implement frontend search to improve perceived performance when searching
Open
Nobody has claimed this yet.
1. to develop
design: interview 🎤
enhancement
performance 🚀
skill:backend
skill:frontend
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Is your feature request related to a problem? Please describe.
Searching for emails is a sluggish experience and takes time to load. Even if the there are some emails cached locally already.
Describe the solution you'd like
The perceived performance of searching emails could be improved.
- Initially search only in emails that have already been loaded on the frontend until remote results come in.
-
Limit the search to one month back first before searching the rest.-> No real benefit as there is a limit anyway.
Describe alternatives you've considered
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing the frontend email-search flow and how already loaded emails are represented; done should mean locally loaded emails appear in results before remote results arrive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100