-
Notifications
You must be signed in to change notification settings - Fork 0
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
App should work offline #5
Labels
Comments
rcmenno
added a commit
that referenced
this issue
May 1, 2023
rcmenno
added a commit
that referenced
this issue
May 8, 2023
rcmenno
added a commit
that referenced
this issue
May 8, 2023
rcmenno
added a commit
that referenced
this issue
May 8, 2023
rcmenno
added a commit
that referenced
this issue
May 15, 2023
rcmenno
added a commit
that referenced
this issue
Nov 17, 2023
rcmenno
added a commit
that referenced
this issue
Nov 27, 2023
rcmenno
added a commit
that referenced
this issue
Nov 27, 2023
rcmenno
added a commit
that referenced
this issue
Nov 27, 2023
rcmenno
added a commit
that referenced
this issue
Nov 27, 2023
rcmenno
added a commit
that referenced
this issue
Nov 27, 2023
rcmenno
added a commit
that referenced
this issue
Nov 27, 2023
rcmenno
added a commit
that referenced
this issue
Dec 22, 2023
Is there any progress regarding this issue? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User Story
As a user
I want to be able to do the relief process offline
So that I don't have to fall back to primitive methods nor be blocked during my work
What needs to be done
Implementation
ReliefBox will be ported on a screen by screen basis to a progressive web app in which service workers make sure the app can work fully offline once installed.
Since at first, all data will live offline, the login flow will not be implemented as long as it's not needed yet.
Screens to port (might change depending on what's encountered):
loginsignuptest_loginThe text was updated successfully, but these errors were encountered: