localForage VS WatermelonDB

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

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.

Have a look at local forage. It is an almost drop in replacement for local storage, but with doing what you want and using the much nicer indexeddb when available.

This is why we have localForage.

I have been using localforage (https://github.com/localForage/localForage) in non vue applications and haven't looked back since. All the features of indexeddb with the same interface as localstorage.

localForage: A Polyfill providing a simple name-value syntax for client-side data storage, which uses IndexedDB in the background, but falls back to WebSQL and then localStorage in browsers that don't support IndexedDB.

Or even a wrapper like this https://github.com/localForage/localForage which falls back to local storage if indexeddb or Web SQL are not available

LocalForage is a good wrapper for it that had worked well for me in Vue 3. https://github.com/localForage/localForage

Storing the notes: For storing the notes, we will use the amazing WatermelonDB package which is a popular sqlite wrapper for react-native. Instead of using the default package we will use a fork of this that uses sqlcipher instead of the regular sqlite, allowing us to encrypt the database by passing a secret key.

As title says, is it a good option? There'll be like 60 webp images not some high quality. Or should I add some local db instead, something like: 1. https://github.com/ammarahm-ed/react-native-mmkv-storage 2. https://github.com/Nozbe/WatermelonDB

Watermelon DB.

Significantly improved performance (a lot of optimizations were done, and state management is more scalable by relying on an actual database)

Watermelondb it gives you an ORM, reactivity (when a records changes it cause UI re-render), and easy syncing with remote server, go with that if you don't know SQL that well.

Why don't you use something like watermelon db if your main goal is to store data locally? I don't think trying to load massive array of data from a single key using any storage providers will be performant.

I think watermelon is they way to go https://github.com/Nozbe/WatermelonDB

We don't have offline capabilities yet - it's something we will investigate probably in the later half of this year.

In the meantime you can use something like WatermelonDb: https://nozbe.github.io/WatermelonDB/