react-native-navigation VS NativeBase

Looks like this feature is not available (check here and here) yet. Good luck mate

another option is react-native-navigation which I haven't used yet but as the document says:

The behavior was reported in their issues 2 years ago: https://github.com/wix/react-native-navigation/issues/6174

At this point don't have a clear preference over which package to use in my next project (react-navigation or react-native-navigation) - they both have strengths and weaknesses, one is easier to actually work with, one is faster in terms of execution, one has better APIs, docs, community, etc.

class Home extends React.PureComponent { constructor(props: Props) { super(props); Navigation.events().bindComponent(this); } closeMenu = () => { this._drawer.close(); }; openMenu = () => { this._drawer.open(); }; static options(passProps) { return { topBar: { rightButtons: [ { component: { name: 'MenuButton', passProps: { onClick: () => this.openMenu(), }, }, }, ], }, }; } render() { return ( ... ); }} Reference I got my passProps code from: https://github.com/wix/react-native-navigation/issues/3648

Thanks! React Native to build the app. React Native Navigation from Wix to build the navigation so the app feels native.

There are two major navigation libraries in React Native world: react-navigation and react-native-navigation. They are both widely used among the community.

You can have a look at React Native Navigation: https://wix.github.io/react-native-navigation/

To navigate between screens, you will probably end up using the very popular React Navigation library. There is a great, purely native alternative, React Native Navigation (the names get confused easily), from Wix. It is super performant but not that flexible. Therefore, again: If your design asks you for something custom, you have no choice but to go with React Navigation; luckily, it is a great, well-documented option.

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