Presented below is the list of features which MugenMvvm provides to Xamarin.Android:
- Work with
Activityis supported. There are exists MugenMvvm implementation for each of standard Android
Activity(name convention is 'Mvvm'+<activity's name>). In order to successfully work with MugenMvvm you must inherit appropriate
Activity. For instance, if you would match a
Activitywith a ViewModel, so after you call
Activityof this type will be made.
- Work with
Fragmentis supported. There are exists MugenMvvm implementation for each of standard Android
Fragment(name convention is 'Mvvm'+<fragment's name>). In order to successfully work with MugenMvvm you must inherit appropriate
Fragment. For instance, if you would match a
MvvmDialogFragmentwith a ViewModel, so after you call
ShowAsyncmethod instance will be shown.
- State control for
Fragmentis supported. States of any
Fragmentare tracked "behind the scene", therefore you haven't manually invoke methods for save/restore the state of ViewModel.
- Back stack navigation is supported.
- Markup binding is supported. In order to use binding on Android one must add the next namepace in
Bind attribute is available to use in xml layout.
- Bindings for
- There is implemented a conception of
DataTemplateSelector, so one can select view template dynamically in runtime. This
DataTemplateSelectoris analogue of conception of
DataTemplateSelectorfor Xaml platform (WPF, WinRT, etc).
- Validation with usage of standard
TextView.Errorproperty is supported.
Updated less than a minute ago