react-native-reanimated VS async-storage

Supports Animation: Tamagui leverages the popular open-source library — Moti as a reanimated driver for animation libraries such as react-native-reanimated and React Native Animated.

FYI react-native-reanimated (https://github.com/software-mansion/react-native-reanimated) is not the Animated API from React Native. react-native-reanimated allows JS code to run on a UI thread that is able to synchronously modify layout, providing alternative synchronous ways for you to hook into the layouting. For instance, as opposed to the asynchronous `measure()` method provided by React Native to measure layouts, react-native-reanimated allows one to call their version of `measure()` (https://docs.swmansion.com/react-native-reanimated/docs/api/...) to perform the same operation on the UI thread, synchronously.

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.

Currently having issues with reanimated (expo installs 2.14.4). My app will crash randomly – possibly linked to these issues here and here.

Reanimated is probably what you're looking for. https://docs.swmansion.com/react-native-reanimated/

One of is: https://github.com/software-mansion/react-native-reanimated/issues/2327

use third party lib that is a beast, but will require a lot of work and upfront knowledge (https://docs.swmansion.com/react-native-reanimated/)

Catalin Miron is also good. Reanimated 2 animations are still relevant. I also would suggest reading the reanimated docs here. That's how I find my way around.

\[@RNC/AsyncStorage\]: NativeModule: AsyncStorage is null. To fix this issue try these steps: • Rebuild and restart the app. • Run the packager with \`--reset-cache\` flag. • If you are using CocoaPods on iOS, run \`pod install\` in the \`ios\` directory and then rebuild and re-run the app. • If this happens while testing with Jest, check out docs how to integrate AsyncStorage with it: https://react-native-async-storage.github.io/async-storage/docs/advanced/jest If none of these fix the issue, please open an issue on the Github repository: https://github.com/react-native-async-storage/async-storage/issues 5 | import { ReactQueryDevtools } from '@tanstack/react-query-devtools'; 6 | import { Platform } from 'react-native'; > 7 | import AsyncStorage from '@react-native-async-storage/async-storage';

Storage: redux-persist, @react-native-async-storage/async-storage

You want this: react-native-async-storage

What do you mean by local storage? The browser based localStorage API does not exist by default in react-native. There is an analogue though... The most basic package that most people use, AsyncStorage is just a string based key-value store: https://github.com/react-native-async-storage/async-storage . It's very useful for anything simple. It also has a merge function which lets you automatically update stringified JSON objects without unpacking them and doing the modifications yourself.

Android - SQLite

Since the original React Native AsyncStorage was deprecated, you may be using the community solution: react-native-async-storage. I would personally recommend it!

I think that you using a deprecated package to store your state. Verify if you are using https://github.com/react-native-async-storage/async-storage.

State management, orchestrating HTTP requests, synchronizing client and server state: all these things will apply to React Native. The differences will only arise when the device layer comes into play (for example, if you have to store data on the client, window.localStorage doesn’t exist, but AsyncStorage does.)