3 ms·
(note I'm generally a pro-web anti-app guy) That is easier said than done. Never worked with the thing, but I've read everywhere that HTML appcache is not exact
by jakub_g 11y ago
(note I'm generally a pro-web anti-app guy) That is easier said than done. Never worked with the thing, but I've read everywhere that HTML appcache is not exactly the best thing ever invented and a pain to work with. Service workers which are proposed to supersede it are now being pushed by Chrome and others, but it sounded a bit complex (though powerful) when I read about it. Then come all the other issues about cache invalidation including involuntary automatic cache clean (hey, I'm low on memory, let's clear the cache!). Your apps generally don't automatically uninstall themselves (though they may clean their cached data, at least on iOS).
Regarding the standard browser caching and "offline mode", it used to work well long time ago for simple static HTML pages (in Firefox and IE), but from my experience it doesn't work well for rich clientside apps (and Chrome doesn't even have "work offline" button)
- maxerickson 11y agoThe article is speculative. So I meant in principle, I have zero clue how practical it is right now.
- jaffathecake 11y agoThere's a spec in development to make an origin's storage persistent https://storage.spec.whatwg.org/#dom-storagemanager-requestpersistent https://storage.spec.whatwg.org/#dom-storagemanager-requestp... - at the moment Chrome only drops data from indexeddb and the cache api if the device starts running out of space.