Closed thombruce closed 1 year ago
Name | Link |
---|---|
Latest commit | 6a8def322c471381dca5f549decbc59533c96ed1 |
Latest deploy log | https://app.netlify.com/sites/toodles/deploys/649e331030cbc50008aa9f56 |
Deploy Preview | https://deploy-preview-91--toodles.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Status | Category | Percentage | Covered / Total |
---|---|---|---|
🟢 | Lines | 67.07% / 60% | 379 / 565 |
🟢 | Statements | 67.07% / 60% | 379 / 565 |
🟢 | Functions | 65.9% / 60% | 29 / 44 |
🟢 | Branches | 71.42% / 60% | 45 / 63 |
General PWA issues reported by Lighthouse for the Netlify preview build:
Vite PWA Plugin has this page describing some of the minimal requirements and how to meet them: https://vite-pwa-org.netlify.app/guide/pwa-minimal-requirements.html
PWA support is now all green in Lighthouse:
What does this achieve?
In theory, it means the web app is installable from the browser wherever that is supported.
This should enable the app to run offline. It will store data in its own browser instance (not sure if this is shared with the version still on a webpage... probably?).
What else?
It opens up the capability to introduce a service worker in the future that would sync offline activity with a cloud server... even if only in the sense that it yields offline capability at this point. This is still a complex matter, requiring different solutions in different environments.
Added robots.txt at recommendation of https://vite-pwa-org.netlify.app/guide/pwa-minimal-requirements.html#search-engines
Otherwise... we don't need a service worker to be fully implemented at this time, so we can skip that and revisit it in the future.
This is ready to merge.
closes #89