Consider you have a list to show a list of categories:
public readonly CollectionViewModel<Item> Items = new CollectionViewModel<Item>();
public class Item : Zebble.Mvvm.ViewModel
public readonly Bindable<Domain.Category> Source = new Bindable<Domain.Category>();
public void Tap()
The<CategoryPage>().Source.Value = Source.Value;
The CollectionViewModel class enables list related view types to handle displaying of lists and collections with good performance. It is also properly rendered by VM.exe.
A list item view model is, well, a view model itself. And so it can have children of its own. It follows the same pattern as above.