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

Decide how to implement PWA features #25

Closed
ZooeyMiller opened this issue Jun 7, 2017 · 1 comment
Closed

Decide how to implement PWA features #25

ZooeyMiller opened this issue Jun 7, 2017 · 1 comment
Labels

Comments

@ZooeyMiller
Copy link
Owner

We need to decide how and what PWA features we want to implement.
I'm inclined towards using sw-precache as both @oliverjam and I have experience with it and find the config pretty straightforward.

If nothing else with sw-precache we can at least serve some content when the user is offline, even if the user cannot meaningfully interact with the app whilst offline.
For meaningful interaction we would need to work out how to use localstorage with Elm so we can store our Model offline.

Relates #8

@ZooeyMiller
Copy link
Owner Author

We've talked (irl, gasp) about what to do in regards to PWA features, we've decided local storage is a priority.
Considering most people will be using the app on a single device then local storage is pretty important. If we sort local storage then get the communication with the api working to store the model remotely.
We're going to use sw-precache and ports in Elm for local storage.

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

No branches or pull requests

1 participant