redux-undo VS redux-persist

worth noting that they're using redux-undo instead of redux-undoable

Here is an example implementation in Redux: https://github.com/omnidan/redux-undo

As for undoing, my personal opinion is that it is never required. After all, undoing an action is really just dispatching a new action with the information to repopulate which you can compute on the fly. An added benefit of this method is your action history is always moving forward, never backwards. That being said, this redux-undo library might help. Note, I have never used it, but it does come back to my point that middleware are usually the solution.

If you wanna get fancy, you could do something like redux undo.

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.