redux-ecosystem-links VS redux-persist

Yeah, from 2016-2018 I spent a lot of time cataloguing Redux-related libraries in the ecosystem, and I definitely saw several addons that were meant to record Redux actions and send them to a server for devs to use in debugging. Totally feasible! (and tbh that's the kind of thing Redux was meant to enable in the first place.)

FWIW, there are some various other third-party replacements for combineReducers that might be useful (see https://github.com/markerikson/redux-ecosystem-links/blob/master/reducers.md ), but you'd have to specifically choose to use them yourself, and on top of that createSlice wouldn't be expecting a third arg or pass it through to its case reducers.

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.