What are the key properties used by the Infinite Scroll Plugin in MvvmCross

1. Threshold for Loading More Items: This is a crucial property that determines when to load more items. For example, in Xamarin.Forms CollectionView, the `RemainingItemsThreshold` property is used to specify how many items should remain before loading more. This concept is likely similar in MvvmCross plugins, where a threshold is set to trigger the loading of additional items when the user approaches the end of the list.

2. Command or Event Handling: Infinite scrolling plugins often use a command or event to handle the loading of more items. In MvvmCross, this might involve binding a command to a view model property that triggers when the threshold is reached. The command or event handler is responsible for fetching additional data and appending it to the list.

3. Data Loading Mechanism: The plugin would need a mechanism to load data from a data source, such as a web API. This involves making network requests to fetch additional data when the threshold is reached.

4. Pagination or Data Management: To manage the data efficiently, infinite scrolling plugins might use pagination, where data is fetched in chunks (e.g., pages of items). The plugin would need to keep track of which page is currently being displayed and load the next page when necessary.

5. Loading Indicator: Many infinite scrolling implementations include a loading indicator (e.g., a spinner) to show that more data is being loaded. This is typically handled by a boolean property in the view model that toggles the visibility of the loading indicator.

While the specific properties of the Sequence.Plugins.InfiniteScroll plugin for MvvmCross are not detailed in the search results, these general concepts are commonly used in infinite scrolling implementations across various frameworks. For precise details, consulting the plugin's documentation or source code would be necessary.