zustand VS react-native-mmkv

For our case, points 1 and 2 can help us provide a better way of handling updates in our rapidly updating application. I have used zustand for the application.

Daishi Kato, creator of Zustand and Jotai, says there are a few things we need to support RSC serialization:

Zustand

Link: https://zustand-demo.pmnd.rs/

For more code examples visit the documentation here

Have you ever wanted to learn state-management but it felt so overwhelming to get started with Redux? Or maybe you're already using Redux but don't want to take the burden anymore? If so, you might want to take a shot at Zustand! Its an amazing state management library that's easy to get started and maintain in a long run. In this post, we'll dive into creating & sharing stores with this tiny Redux alternative.

You add the current user state to a React Context or state management library, read from it on the top bar, and write to it after a user signs in. Done. No big deal, right?

Zustand

I tried using skipHydration inside my zustand store based on their docs, then rehydrating it inside my modal. So far im getting the same errors. https://github.com/pmndrs/zustand/blob/main/docs/integrations/persisting-store-data.md

react-native-mmkv is a wrapper around MMKV that allows you to easily implement secure storage in your app. It is arguably the fastest key-value storage for React Native apps

Why do you need to access the db from the file system? Can you just use something like https://github.com/mrousavy/react-native-mmkv ?

By using libraries like Reanimated, React Native MMKV, and React Native Skia, you leverage the native thread. However, I know there are developers building amazing things who think outside the box. I'm always thrilled when I read engineering blogs from companies like Netflix, Meta, and Shopify. They create solutions beyond the limits.

mmkv is not really designed to be used for “heavy” writes, or often changing values. But more as e.g. NSUserDefaults. The storage keeps growing over time which may cause memory issues if used wrongly. Here’s a related github issue: https://github.com/mrousavy/react-native-mmkv/issues/440

Persistence - React Native MMKV (supports encryption natively and easily integrates with TanStack Query via persistQueryClient)

if you need to store something small and simple use whatever. if is complex and speed is important use something performant. realmDB, https://github.com/mrousavy/react-native-mmkv and others are good fit for the job.

Screw you all, I'll use MMKV as my Local DB: please do not, as explained here.

Try react native mmkv https://github.com/mrousavy/react-native-mmkv