react-native-biometrics VS redux-persist

react-native-biometrics helps us to access functionalities like FaceID, TouchID, or any other biometric features that are available in the device. react-native-biometrics uses the device Keystore for biometric authentication. it's helpful when you develop an application that is security intensive.

In React Native, this solution is readily available with the react-native-biometrics library, which is, unfortunately, not actively maintained (last commit 2/2020) and its biometrics part does not support the latest standards, such as fallback to passcode when Face ID fails.

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.