react-native-paper VS NativeBase

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

Gluestack, like any other customizable UI library, is built to make styling less cumbersome. It comprises a set of themed and unstyled components easily integrated across different platforms and devices. Originally, Gluestack was a part of NativeBase, a component library for both React and React Native. With performance and maintainability in mind, NativeBase was split into two parts, focusing on a universal CSS-in-JS library and an independent set of unstyled components. Gluestack has several advantages, some of which are:

Native-base

Just like the other libraries mentioned in this article, Gluestack is another unstyled component library. Originally a part of NativeBase, the developer team created this library to prevent bloat and enhance maintainability of the project.

KumaUI : Another relatively new contender, Kuma uses zero runtime CSS-in-JS to create headless UI components which allows a lot of flexibility. It was heavily inspired by other zero runtime CSS-in-JS solutions such as PandaCSS, Vanilla Extract, and Linaria, as well as by Styled System, ChakraUI, and Native Base. ### Vue

You can see timeline of that here: https://github.com/GeekyAnts/NativeBase/issues/4302

NativeBase is being abandoned unfortunately , I wouldn’t start a new project with it https://github.com/GeekyAnts/NativeBase/issues/4302