redux-persist VS redux-saga-thunk

Storage: redux-persist, @react-native-async-storage/async-storage

Next, following their official document, I added some changes to my store.

redux-persist : For persisting data locally

One thing to keep in mind with persisting data to a device is that you maybe have to run migrations on that data if your app starts to use that data differently. https://github.com/rt2zz/redux-persist/blob/master/docs/migrations.md

for most applications, AsyncStorage works fine. also, you can use it with redux-persist or persist middleware of zustand. in this way, you won't even need to touch the AsyncStorage. my first choice as a database (or just a persistor tool) is zustand and AsyncStorage. this combination can solve storage issues most of the time.

That is also admittedly not very smart. Maybe you only want to persist certain slices, maybe you need to do other things with it. That's why https://github.com/rt2zz/redux-persist and other similar addons exist.

There are some hacky workarounds, such as putting a callback in the action object itself, and having the saga run that callback. That should be avoided, though. There are at least a couple packages that implement something that may work a bit better, like https://www.npmjs.com/package/@adobe/redux-saga-promise and https://github.com/diegohaz/redux-saga-thunk , but I haven't tried them.