❔ Choosing an MVVM Framework - Prism vs MvvmCross
Hello! I'm researching MVVM frameworks for a new large project with a complex UI. I'd like it to be UI framework agnostic, in case WPF (which will probably be the target UI framework of the project) is buried by Microsoft.
Additionally, I'd like to be free to choose whichever IoC I want, e.g., DryIoC
To this day I was not using any frameworks for MVVM.
I've noted the following potential frameworks:
- Prism
- MvvmCross
- ReactiveUI
Could you please share your experience with said frameworks, and, if possible, why you chose one over the other?
-- Here are my quick notes:
Prism is one of the most popular MVVM frameworks, that offers many features necessary for large-scale applications. This means reading the documentation is necessary, but less overall boilerplate code is written. Moreover, Prism has native support for DryIoc and Unity. The framework had been out for quite a while.
MvvmCross is easy to start working with. Everything works out of the box but allows developers to override features to their needs. The documentation might not be up to date. It is very similar to Prism.
ReactiveUI is a powerful library focused on simplifying updates to the view by making it “reactive” to changes made in the view model. This means that it is much easier to use for e.g. displaying stock exchange prices, which change constantly, or logging. The project is very popular and actively developed.
Additionally, I'd like to be free to choose whichever IoC I want, e.g., DryIoC
To this day I was not using any frameworks for MVVM.
I've noted the following potential frameworks:
- Prism
- MvvmCross
- ReactiveUI
Could you please share your experience with said frameworks, and, if possible, why you chose one over the other?
-- Here are my quick notes:
Prism is one of the most popular MVVM frameworks, that offers many features necessary for large-scale applications. This means reading the documentation is necessary, but less overall boilerplate code is written. Moreover, Prism has native support for DryIoc and Unity. The framework had been out for quite a while.
MvvmCross is easy to start working with. Everything works out of the box but allows developers to override features to their needs. The documentation might not be up to date. It is very similar to Prism.
ReactiveUI is a powerful library focused on simplifying updates to the view by making it “reactive” to changes made in the view model. This means that it is much easier to use for e.g. displaying stock exchange prices, which change constantly, or logging. The project is very popular and actively developed.
