.NET MAUI Application

Preserve Project Choices

Preserve the project's existing MVVM toolkit, navigation strategy, dependency container usage, and XAML-versus-C# UI style.
Do not introduce CommunityToolkit.Mvvm, Prism, ReactiveUI, or another framework unless the project already uses it or the user requests it.
Apply csharp-readable-code to all C# member naming, nullability, async operations, result shapes, and static-member restrictions.

Keep a View responsible for structure, layout, appearance, and UI-only behavior.
Keep business and application logic out of XAML code-behind.
Allow code-behind for visual behavior that is genuinely difficult to express in XAML, such as a view-owned animation.
Expose logical enabled/disabled, busy, validation, and selection state from the ViewModel and bind the View to it.
Prefer commands or behaviors for user actions when controls support them.
Do not make ViewModels reference Page, View, controls, handlers, or platform UI types.