segmented-control VS react-native-paper

Segmented Control: Instead of a filter at the bottom of the list, you’ll learn how to create a segmented control component that allows you to filter tasks based on their status of All, Active, and Completed.

It's called a Segmented Control. https://github.com/react-native-segmented-control/segmented-control

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