Open ORCANLRC opened 3 years ago
Relevant (code related) reading:
More reading:
Can we link to the way the AW APP of 121 work flow re data input and saving for later upload?
Can we link to the way the AW APP of 121 work flow re data input and saving for later upload?
The configuration we use for the service-worker of the AW-app: https://github.com/global-121/121-platform/blob/master/interfaces/AW-App/src/ngsw-config.json
An 'interceptor' we use there to 'catch' requests to the back-end when offline: https://github.com/global-121/121-platform/blob/master/interfaces/AW-App/src/app/http-interceptors/retry-interceptor.ts
The 'syncing' functionality is handled by separate components:
(There must be a demo-video somewhere to make this more visual.... ;) )
Some relevant "Offline First" reading:
(The specific tool RxDB isn't really the point here, as I think it'll be a bit steep learning curve to introduce that tool now into the app.)
CC: @arsforza
Our server-datastore might need to change to easily support an "offline-first" interface.
Possible tools: https://hasura.io/blog/couchdb-style-conflict-resolution-rxdb-hasura/
Alternative approach, "online-first, offline-backup": See https://daanstolp.nl/articles/2021/angular-pwa-2/
three options we have: we will go for number 2 1: offline first : issue: too little time & too new to all 2: cache user actions : posting answers ( one edit user is best otherwise they over ride each other) positng comments (out of sync) 3: no offline scenario
Interesting talks: https://pwasummit.org/
As an AW I want to be able to access the CPDW in times where I have no connectivity to later update the online shared information.
See HCD-Notebook: LOW BANDWIDTH / CONNECTIVITY