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

Add an option to use the cached dataset for longer #108

Open
bopjesvla opened this issue Jan 8, 2025 · 1 comment
Open

Add an option to use the cached dataset for longer #108

bopjesvla opened this issue Jan 8, 2025 · 1 comment

Comments

@bopjesvla
Copy link
Owner

Leon writes in #103:

On the road, the mobile data will get drained and waste a lot of bandwidth. Every ten minutes, the cache gets invalidated as long as there changes (right?). It will reload if there is an internet connection, requiring you to download all the data again.

This is indeed the case, but syncing the dataset seems too complex a solution for this. It's easier to let the user choose how long the cached version is valid, probably in the main menu. This requires some communication between the app and the service worker.

@leon-wbr
Copy link
Contributor

leon-wbr commented Jan 9, 2025

I support this. It's a question of UX/UI, also.

Perhaps we could implement an endpoint that returns a datetime of last update and do a notification on initial page load that prompts the user to update manually, if they haven't updated since x amount of time and there are changes?

Bit simpler than implementing a control. Perhaps we could also put the control into that notification to do the initial setting; such as: "There is a new dataset available. Do you want to update now? Yes / No / Automatically update if older than 10 mins, 1 hr, 1 day, 1 week, 1 month."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants