react-native-mmkv VS react-native-navigation

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

Looks like this feature is not available (check here and here) yet. Good luck mate

another option is react-native-navigation which I haven't used yet but as the document says:

The behavior was reported in their issues 2 years ago: https://github.com/wix/react-native-navigation/issues/6174

At this point don't have a clear preference over which package to use in my next project (react-navigation or react-native-navigation) - they both have strengths and weaknesses, one is easier to actually work with, one is faster in terms of execution, one has better APIs, docs, community, etc.

class Home extends React.PureComponent { constructor(props: Props) { super(props); Navigation.events().bindComponent(this); } closeMenu = () => { this._drawer.close(); }; openMenu = () => { this._drawer.open(); }; static options(passProps) { return { topBar: { rightButtons: [ { component: { name: 'MenuButton', passProps: { onClick: () => this.openMenu(), }, }, }, ], }, }; } render() { return ( ... ); }} Reference I got my passProps code from: https://github.com/wix/react-native-navigation/issues/3648

Thanks! React Native to build the app. React Native Navigation from Wix to build the navigation so the app feels native.

There are two major navigation libraries in React Native world: react-navigation and react-native-navigation. They are both widely used among the community.

You can have a look at React Native Navigation: https://wix.github.io/react-native-navigation/

To navigate between screens, you will probably end up using the very popular React Navigation library. There is a great, purely native alternative, React Native Navigation (the names get confused easily), from Wix. It is super performant but not that flexible. Therefore, again: If your design asks you for something custom, you have no choice but to go with React Navigation; luckily, it is a great, well-documented option.