hoodie VS localForage

I'm not looking for the overthrow of CRUD-through-MVC. Rather, Hobo and Hoodie seemed like advances---Hobo was sort of Rails for Rails, and Hoodie was an offline-first framework for something like what we now call Progressive Web Apps---when I tried them early in their life-cycle, but both seem to have withered away. And nobody else (that I can find) seems interested in improving graphical design (as in, "just use Material Design, or Carbon, or whatever"), cleaner parent/child relationships, automatically updating views and controllers to match changes to the models, and probably features that I don't know that I need.

Not really an answer but have you looked into https://github.com/localForage/localForage

I may not be pointing you in the right direction but, please read about [IndexDB storage](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB\_API) method and packages like [localForage](https://localforage.github.io/localForage/) that use it under the hood.

LocalForage: this is a wrapper around IndexedDB, WebSQL, LocalStorage, and SessionStorage with a way to define more interfaces (called drivers) *for additional storage solutions. It does a great job handling all your serialization needs, it is **asynchronous **and handles a large set of data types. Its **API resembles Web Storage API* and it is ridiculously simple to learn.

Depending on what kind of storage requirements you have, LocalForage might be a good fit. It provides a unified API to access WebSQL, indexedDB or localStorage.

I find localForage is pretty helpful for this stuff https://github.com/localForage/localForage

localForage (https://localforage.github.io/localForage/) mirrors localStorage syntax, but uses IndexedDB in the background. If that's not supported, it uses WebSQL and then LocalStorage

This is why we have localForage.