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

Missing Technologies: Keeping Application State #7

Open
janl opened this issue Nov 28, 2013 · 2 comments
Open

Missing Technologies: Keeping Application State #7

janl opened this issue Nov 28, 2013 · 2 comments

Comments

@janl
Copy link
Contributor

janl commented Nov 28, 2013

Native apps, at least on iOS, are trained to restore a specific application state that reflects what the user saw the last time they were in the app. Because mobile apps can be retired for memory or battery reasons at any time, they need to be able to restore their state. iOS comes with system APIs that help with that.

On the web app front, this isn’t an established pattern and existing tools don’t have this built in, or make it easy. Please comment with counter examples!

@michielbdejong
Copy link

good point! shouldn't be so hard to build this into router frameworks - just always store the current route in localStorage or IndexedDB, right?

@ghost
Copy link

ghost commented Dec 18, 2013

store the current route in localStorage or IndexedDB

Or the whole DOM, then you also capture page state.

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

No branches or pull requests

2 participants