Skip to content

Leveraging Alternative Native Drawer Behaviors #3

@smooJitter

Description

@smooJitter

First, I'm a newbie to react-native and I know very little about native IOS and Android. I've bee searching for an approach to handle navigation and routing for reach-native apps. I tried react-native-router-flux and I was satisfied. So far, I like my experience with react-native-navigation. For the most part, it's easy to reason about. I started with react-native-controller but a few days ago, my demo project broke giving me react-native, react, and react-native-controller package conflicts. Nevertheless, its easy to find my way around this package.

I have a few questions,

  1. Are all the features available to react-native-controller available to this package.
  2. What do you think it would take to leverage native drawer behaviors such as,
  • jondanao/TheSidebarController:  https://github.com/jondanao/TheSidebarController
    
  • romaonthego/RESideMenu: https://github.com/romaonthego/RESideMenu/
    

I ask because, similar to this package, these implementations seem ( correct me if I'm wrong) based on native view controllers.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions