I have been over-viewing indexedDB recently, and I cannot seem to find a suitable use case that would not be better done using a server side database. Since the little hackathon competition I'm doing with my friends is creating an agenda web-app, I'll put my examples in that contest.
Just to make sure, I read that indexedDB is stored per site per browser. If this is so, the following ideas make no sense:
- Storing user preferences. Since a user will most likely want his preferences saved across devices, it would seem better to save this on the server side.
- Storing items / date that were recently viewed. Since this data is not structured and not data that will need to persist for a long time, wouldn't be easier to use localStorage.
I could go on with ideas that would fit better with a server side DB, localStorage or sessionStorage, so to cut to the chase, what are some example use cases that would fix indexedDB well?