A Xamarin.Forms layout that adds pull-to-refresh functionality to ScrollView, ListView, and CollectionView.
PullToRefreshLayout is a Xamarin.Forms library that adds pull-to-refresh functionality to scrollable views like ScrollView, ListView, and CollectionView. It solves the need for a cross-platform refresh gesture in mobile apps before Xamarin.Forms 4.3 introduced an official RefreshView. The library allows developers to trigger data refreshes with a simple pull-down gesture.
Xamarin.Forms developers building iOS and Android apps who need pull-to-refresh capabilities, especially those using versions before Xamarin.Forms 4.3.
It provides a straightforward, customizable implementation of pull-to-refresh that integrates with Xamarin.Forms' layout system and data binding, saving developers from implementing platform-specific refresh logic.
Pull To Refresh a ScrollView or ListView in Xamarin.Forms
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides pull-to-refresh functionality on both iOS and Android within Xamarin.Forms, ensuring a uniform user experience without platform-specific code, as highlighted in its cross-platform support.
Can wrap various views like ScrollView, ListView, and CollectionView, making it adaptable to different UI structures without restricting content types, per the README's supported views list.
Allows setting refresh colors and binding to refresh commands and states via XAML or code, giving developers control over the refresh UI and behavior, as shown in the API examples.
Filled a critical gap by offering pull-to-refresh capabilities before Xamarin.Forms 4.3 introduced the official RefreshView, saving development time for legacy projects.
The library is no longer maintained, with all issues closed and no further updates, making it risky for production use as stated in the README's deprecation notice.
Requires calling PullToRefreshLayoutRenderer.Init() in both MainActivity and AppDelegate, adding setup complexity and potential for errors compared to built-in components.
For Android, it must be built against SDK 8.1 or 9.0, which is outdated for modern app development and may limit compatibility with newer APIs and features.
Views like UICollectionView and RecyclerView are only unofficially supported and may behave oddly, as admitted in the README, leading to unpredictable UI behavior.