I’m new to IndexedDB myself but I too have been thinking a lot about how I would use IndexedDB for purposes like this. The first thing I would suggest, if you haven’t done it already, is to look at how other key-value / document databases (CouchDB, MongoDB, etc.) work, since that’s essentially the type of … Read more
Web SQL is deprecated per https://www.w3.org/TR/webdatabase/. You can use IndexedDB if you need to store structured client specific data that you do not store in the server side or you do not want to request from the server every time. Also as opposed to localStorage, IndexedDB is async so it is more performant. It supports … Read more
Well, as with all things computing, the game is “abstraction”. If you can come up with an adequate layer that works on both a SQL store and a key/value store, then, ideally you’re isolated from the problem and can support the appropriate implementation on the particular browser. If your data model and access patterns don’t … Read more
Using PersistenceJS there is a persistence.reset API which will wipe the database clean. PersistenceJS Site For developing / testing purposes, you can view content and delete webSQL, IndexedDB, cookies, etc by searching for your domain name at this URL in Chrome: chrome://settings/cookies There, you can delete all the storage for a domain or just certain … Read more
I would recommend checking out the JayData library, that actually has the exact purpose of creating a storage agnostic data access layer for mobile devices. JayData provides an abstraction layer with JavaScript Language Query (JSLQ) and JavaScript CRUD support and let’s you work on the exact same way with different offline and online data store … Read more
Let me answer step by step if the app stores data with localStorage or web SQL, and the user switches to a different standard browser on their Android, will the app be opened with the new browser and does that mean that the stored data is unavailable? The data is saved in the ‘cache'(its not … Read more