A benefit often mentioned (e.g., here, here) about HTML5 LocalStorage is support for offline apps. However, the same-origin policy makes me think that an app at foo.com won't see the same LocalStorage as it would if the user downloaded the HTML files of the app and pointed their browser to those files on their local drive. (The same-origin policy is also restrictive with apps loaded from file:// URLs).
My questions:
- My web app must read/write LocalStorage and be usable offline, still reading/writing the same LocalStorage. Is the correct way to support that an app manifest? I.e., if I use an app manifest, when the user tries to visit foo.com when offline, I think he/she will get the cached version, and yet the domain will still count as if the user were online. Is that right?
- I assume that this does not work the same if I create a local app using a wrapper like Atom shell. I.e., the same-origin policy will mean that the user will not be able to access the same LocalStorage inside the wrapped version of my app as they would from their browser. Is that right?