async-storage VS react-native-paper

\[@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.)

In most cases they are wrappers around pure RN components (as I have been burnt by styling lib in the past - exactly NativeBase and its performance issues) and in the end, created components look like very light-weight version of RN paper components*:* https://github.com/callstack/react-native-paper/blob/main/src/components/Typography/Text.tsx.

react paper modal - Modal

Some that also come up are: * https://github.com/akveo/react-native-ui-kitten * https://github.com/draftbit/react-native-jigsaw/tree/master/packages/ui * https://github.com/callstack/react-native-paper * https://github.com/GeekyAnts/NativeBase * https://github.com/react-native-elements/react-native-elements

I'd say a good start would be to check the demos for NativeBase and Paper to compare the look/feel and see if they have all the components you need.

React Native Paper

CSS-based UI libs don't make sense on mobile; your new options include NativeBase, React Native Elements and others). Some web-based UI libs do have RN siblings though - such as React Native Material and React Native Paper (for Material-UI), and tailwind-rn (for Tailwind). This just means new decisions to make, some learning, and new paradigms for how to use the new libs.

I'll suggest going with native base and react native paper . As these are only 2 libraries up there which are efficient and give some good results.

Every time when I start to learn something new I usually have a look at popular open source project. So I can understand some good patterns etc. E.g. https://github.com/callstack/react-native-paper