@ppk asks: “OK, suggestions for my next bit of research?” — https://twitter.com/ppk/status/587545743625478144
@rem replies: “@ppk storage. What works in browser, what browsers, what phones, how it changes when *added to home screen", limits, etc. How's that?” — https://twitter.com/rem/status/587566978065367040
Here’s what I whipped up, please add more in the comments:
- localStorage: https://developer.mozilla.org/en-US/docs/Web/API/Storage/LocalStorage / http://dev.w3.org/html5/webstorage/#dom-localstorage / http://dev.w3.org/html5/webstorage/#storage-0
- Chrome Storage (Chrome apps): https://developer.chrome.com/apps/storage
- IndexedDB: https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API
- WebSQL (although discontinued, still widely available and occasionaly faster or less buggy than IndexedDB): http://www.w3.org/TR/webdatabase/
- Cordova SQLite Plugin (to overcome storage limits): https://github.com/litehelpers/Cordova-sqlite-storage
- compability across a broad browser matrix (hello Mobile Safari)
- storage limits across browsers and OSs
- eviction policies per browser/OS
- storing objects vs. storing text vs. storing binary data / Blobs
-
all the research that went into PouchDB, including:
-
http://offlinefirst.org / https://github.com/offlinefirst/research
Also the issue of binary data in the browser (blobs, arraybuffers, etc.) is probably worthy of its own blog post, but there's some info here:
Also sorry I'm focusing mostly on the negative, but figured it's best to take a hard look at browser storage in all its gory detail. 😃