A simple bottom drawer control for Xamarin.Forms projects, inspired by Google Maps.
Xam.Plugin.SimpleBottomDrawer is a Xamarin.Forms plugin that provides a bottom drawer control for mobile applications. It solves the need for a sliding panel interface to display additional content or controls, similar to the one used in Google Maps. The control is designed to be simple and customizable through XAML.
Xamarin.Forms developers building cross-platform mobile apps who need a bottom drawer UI component. It's ideal for those looking to implement Google Maps-like sliding panels in their applications.
Developers choose this plugin because it offers a straightforward, easy-to-integrate solution specifically for Xamarin.Forms, with no complex setup. Its focus on simplicity and XAML customization makes it a practical choice over building a drawer from scratch.
Just a nice and simple BottomDrawer for your Xamarin Forms project
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Implements the intuitive sliding panel behavior identical to Google Maps, as demonstrated in the side-by-side GIF comparison in the README.
The drawer's content is completely defined via XAML, allowing flexible UI design, as shown in the usage example with StackLayout and ScrollView.
Supports properties like ExpandedPercentage and IsExpanded that can be bound to ViewModel data for dynamic state management, enabling responsive interactions.
Designed to work seamlessly with Xamarin.Forms' RelativeLayout for responsive positioning, as illustrated in the provided XAML code snippet with constraints.
Lacks support for advanced functionalities such as custom animations, nested drawers, or complex gestures, which might be needed for more sophisticated UIs beyond basic sliding.
Built for Xamarin.Forms, which is being phased out in favor of .NET MAUI, potentially limiting future updates, bug fixes, and compatibility with newer platforms.
The README provides basic examples, but detailed documentation is minimal and linked to a separate doc.md file, which may not cover edge cases or advanced usage scenarios.