NativeBase VS react-native-gesture-handler

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

See this for my source code: https://github.com/software-mansion/react-native-gesture-handler/discussions/2501

We are excited to release a stable version of React Native ECharts 1.1. In the new version, we have added support for the react-native-gesture-handler gesture solution, among other enhancements. Read on to learn more!

GitHub Stars: 5.2k

the solution is react-native-reanimated. reanimated helps us to create smooth and performant animations with minimal setup, with a lot of helpers, and is relatively easy to use. another useful library for handling gesture animations is react-native-gesture-handler which is defined as:

One of my first impressions was the vast difference in ease of usage of the React Native Gesture Handler in comparison to React Native’s Gesture Responder System. One less obvious impression was how React Native Gesture Handler’s seamless integration with React Native Reanimated transformed fluidity and complexity of animations. Hence, I concluded on leveraging on the power boost from the duo. Armed to the teeth with weapons of mass destruction, I proceeded on the journey to build NestedLists. 😂

To draw stuff? Maybe https://docs.swmansion.com/react-native-gesture-handler/

For swiping in mode screens I use Reanimated with React Native Gesture Handler. In sound shop swipe is implemented through a simple ScrollView which is built into RecyclerListView. I didn't quite understand the second part of the question tho

1.React Native Gesture Handler 2.React Native Material UI 3.Native Base; (Cross-platform UI components for React Native) 4.React-Native-UI-Kitten 5.Axious; (HTTP client for the browser and Node.js) 6.React Native Maps

Your PanGestureHandler is handling all the clicks. Please check this library from Software Mansion: https://github.com/software-mansion/react-native-gesture-handler You can replace PanGestureHandler with other handlers. Last part is to import TouchableOpacity from RNGH and it will work out of the box.

Thanks :) react-native-gesture-handler and the base Animated API