ServiceWorker usage and classic "Instagram style" updates
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
All of the links that are followed are requested every time the user clicks them. That's fine - no funny library nonsense introducing all the bugs you see with SPAs.
If Flux introduced a ServiceWorker that could cache all links, and spider the application to pre-cache links, then every click would be instant - but we could mark particular elements as needing to show the live information using data-flux="refresh" or something similar. This is the classic Instagram-style updates, where the old (good) instagram app used to display the page instantly, but then update the likes/followers behind the scenes while refreshing the latest cache.
This will be the best final feature to add some real polish to Flux.
Contributor guide
No contributing guide indexed for this repository
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
Start by locating Flux’s client-side link-request and navigation handling, then review how a ServiceWorker could cache and pre-cache followed links. Define how elements marked for live refresh should behave and how cached pages are updated; the feature is done when navigation is instant while explicitly refreshed information remains current.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100