Forum Discussion
_anomDiebolt_
7 years agoQrew Elite
You can get QuickBase to work offline using Service Workers and Workbox.
I have been ranting and raving about using Service Workers with QuickBase for almost three years now and described them as god mode for QuickBase. Not surprisingly last week at Google IO the State of the Union for the Web presentation led with the topic of Service Workers and used the acronym OMFG to underscore their power:
The Web: State Of The Union (Google I/O '18)
https://www.youtube.com/watch?v=Ay-mdLMDtbs
Workbox
JavaScript Libraries For Adding Offline Support To Web Apps
https://developers.google.com/web/tools/workbox/
In practical terms you can get reports to display when offline and simple forms to queue for submission while offline and silently complete submission when network access is regained. Obviously there are limitations to how these operations work when offline. Reports might not be up to date when viewed offline so they are best used for non-mission critical situations like listing contact or account information. Similarly, offline forms operate best when viewing existing records or creating new records. In the case of creating new records offline, simple forms that don't use lookups fields or relations and don't require unique field value can be made to work offline. The essential situation to avoid are forms that need network access to reach related tables or a round trip to the server to validate a field.
I have been ranting and raving about using Service Workers with QuickBase for almost three years now and described them as god mode for QuickBase. Not surprisingly last week at Google IO the State of the Union for the Web presentation led with the topic of Service Workers and used the acronym OMFG to underscore their power:
The Web: State Of The Union (Google I/O '18)
https://www.youtube.com/watch?v=Ay-mdLMDtbs
Workbox
JavaScript Libraries For Adding Offline Support To Web Apps
https://developers.google.com/web/tools/workbox/
In practical terms you can get reports to display when offline and simple forms to queue for submission while offline and silently complete submission when network access is regained. Obviously there are limitations to how these operations work when offline. Reports might not be up to date when viewed offline so they are best used for non-mission critical situations like listing contact or account information. Similarly, offline forms operate best when viewing existing records or creating new records. In the case of creating new records offline, simple forms that don't use lookups fields or relations and don't require unique field value can be made to work offline. The essential situation to avoid are forms that need network access to reach related tables or a round trip to the server to validate a field.