clipboard VS react-native-mmkv-storage

Clipboard API doesn't exist on React Native. We use this clipboard instead.

Above you can see that if the platform is "web" we'll copy the message to their clipboard (via expo-clipboard or react-native-clipboard).

It can now be found in a separate repo: https://github.com/react-native-clipboard/clipboard

As title says, is it a good option? There'll be like 60 webp images not some high quality. Or should I add some local db instead, something like: 1. https://github.com/ammarahm-ed/react-native-mmkv-storage 2. https://github.com/Nozbe/WatermelonDB

Use mmkv storage to make it faster

watermelondb https://github.com/Nozbe/WatermelonDB mmkv giving another issue when you release on playstore in here https://github.com/ammarahm-ed/react-native-mmkv-storage/issues/194

roll your own with asyncstorage (or RN mmkv https://github.com/ammarahm-ed/react-native-mmkv-storage ) and react query

Async Storage is slow/limited though, the new black is MMKV - https://github.com/mrousavy/react-native-mmkv or https://github.com/ammarahm-ed/react-native-mmkv-storage

If you use Async Storage in your React Native App, you should give react-native-mmkv-storage a try. The fastest storage library for react native built with JSI.

It's been a year now and with the extensive support from community, react-native-mmkv-storage has gotten even faster than it was using JSI. I have rewritten the whole library in C++. There are no `@ReactMethods` or the old bridge anymore. Everything happens in C++ which makes this library the fastest solution available for your apps.

In my experience cookies does not play well with RN. In my apps I usually receive the token on the authorization header of the sign in/sign up response. I store it (I use react-native-mmkv since it provides encryption and compatibility with redux-persist out of the box) and append it to every request (using Axios). When the user logs out and for 401 responses I clean the storage