You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need to know how to implement a functionality like, navigating pages inside the bottom sheet.
Ex- Bottom sheet is opened and when a button is clicked where it is in the bottom sheet, it should navigate to another page inside the same bottom sheet.
Why it is needed
In many React Native apps, bottom sheets are used for complex workflows that require multiple screens or pages. For example:
A settings bottom sheet with multiple configuration screens.
A checkout flow within a bottom sheet.
A multi-step form inside a bottom sheet.
Currently, developers need to implement custom solutions (e.g., managing a stack of components or using conditional rendering) to achieve multi-page navigation within a bottom sheet. This can lead to repetitive boilerplate code and less-than-ideal performance. Built-in support for multi-page navigation would simplify the implementation, improve developer productivity, and enhance the user experience.
The text was updated successfully, but these errors were encountered:
Feature Request
I need to know how to implement a functionality like, navigating pages inside the bottom sheet.
Ex- Bottom sheet is opened and when a button is clicked where it is in the bottom sheet, it should navigate to another page inside the same bottom sheet.
Why it is needed
In many React Native apps, bottom sheets are used for complex workflows that require multiple screens or pages. For example:
Currently, developers need to implement custom solutions (e.g., managing a stack of components or using conditional rendering) to achieve multi-page navigation within a bottom sheet. This can lead to repetitive boilerplate code and less-than-ideal performance. Built-in support for multi-page navigation would simplify the implementation, improve developer productivity, and enhance the user experience.
The text was updated successfully, but these errors were encountered: