A React Native library providing native bottom action sheets for Android and iOS with Material Design compliance.
react-native-bottom-action-sheet is a React Native library that provides native bottom action sheet components for Android and iOS applications. It solves the need for platform-authentic bottom sheets that follow Material Design guidelines on Android and native iOS patterns, offering multiple view types (sheet, grid, alert) with full customization.
React Native developers building cross-platform mobile apps who need native-feeling bottom sheets with Material Design compliance on Android and iOS-native styling.
Developers choose this library for its true native performance (wrapping native libraries), adherence to Material Design specs, and flexible API that supports both imperative and declarative usage patterns across both major mobile platforms.
React Native: Native Bottom Action Sheet
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Wraps proven native libraries like BottomSheetBuilder for Android and SGActionView for iOS, ensuring smooth animations and platform-consistent behavior as demonstrated in the README's GIF examples.
Adheres to Google's Material Design specifications on Android, providing visual and interactive consistency with native Android apps, which is a core feature highlighted in the description.
Supports both imperative (API) and declarative (React component) usage, offering integration flexibility for different coding styles, as shown in the example code snippets.
Includes Sheet View, Grid View, and Alert View to accommodate various interaction patterns, with clear examples and platform-specific tuning options in the API documentation.
Requires installing multiple dependencies (react-native-image-helper, react-native-vector-icons), modifying Podfile for iOS, and adding jitpack repository for Android, with version-specific instructions that can be confusing.
Custom icons necessitate manual copying of assets to platform-specific folders (Android drawable, iOS resources), as the README admits this limitation due to native rendering constraints.
Some features like subTitle for items are iOS-only, leading to inconsistencies that developers must handle manually in cross-platform code, as noted in the API documentation.