A super light, convention-based MVVM framework designed specifically for Xamarin.Forms mobile development.
FreshMvvm is a lightweight MVVM framework specifically designed for Xamarin.Forms. It provides essential MVVM patterns like navigation, dependency injection, and data binding with minimal complexity, solving the problem of over-engineered frameworks for Xamarin.Forms projects.
Xamarin.Forms developers who need a simple, convention-based MVVM framework without the steep learning curve or overhead of larger alternatives like MvvmCross or Prism.
Developers choose FreshMvvm for its simplicity, flexibility, and Xamarin.Forms-specific design, offering a streamlined alternative to heavier MVVM frameworks while maintaining powerful features like IOC and custom navigation.
FreshMvvm is a super light Mvvm Framework designed specifically for Xamarin.Forms. It's designed to be Easy, Simple and Flexible.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Described as 'super light' and easy to learn, it reduces overhead compared to heavier frameworks like MvvmCross, making it ideal for straightforward Xamarin.Forms apps.
Tailored specifically for Xamarin.Forms with features like PageModel navigation and automatic BindingContext wiring, ensuring seamless integration without extra setup.
Uses naming conventions (e.g., QuotePage pairs with QuotePageModel) to automatically link views and ViewModels, minimizing boilerplate configuration code.
Includes a built-in dependency injection container based on TinyIOC, supporting constructor injection and lifetime management without requiring external libraries.
Supports multiple independent navigation services, enabling complex scenarios like separate authentication and main app flows, as detailed in the README with code examples.
Exclusively tied to Xamarin.Forms, which is deprecated in favor of .NET MAUI, and the MAUI version is a separate project, raising concerns about long-term maintenance.
Focuses on core MVVM patterns but lacks advanced features such as reactive extensions or pre-built UI controls, requiring more custom development work.
Heavy reliance on naming conventions can be restrictive for teams with non-standard architectures or those preferring explicit configuration over implicit rules.
Has a smaller ecosystem compared to frameworks like Prism, resulting in fewer third-party integrations, tutorials, and community-driven resources.