Nothing matches that. Try a shorter word, or browse the topics.
The things every MAUI app needs and nobody enjoys writing: typed navigation with a real ViewModel lifecycle, a MauiProgram.cs that stays readable, configuration from the platform and the network, and permissions declared once.
Typed Shell navigation with a proper ViewModel lifecycle
Opinionated Shell navigation with source-generated routes, strongly-typed parameters and ViewModel lifecycle management — no magic strings, no manual wiring, and testable.
Break MauiProgram.cs into self-contained modules
Split a massive MauiProgram.cs into IMauiModule classes, each responsible for its own registrations and post-build initialization, with static service access and platform lifecycle dispatch.
IMauiModule classesShinyHost service accessPlatform preferences, JSON bundles and remote configuration
Microsoft.Extensions.Configuration providers for mobile apps: platform preference stores, JSON bundled per platform, and configuration fetched from a server. Works without any other Shiny module.
Declare permissions once; MSBuild writes the manifest and Info.plist
Declare permissions in your project file and let MSBuild generate the Android manifest entries and iOS Info.plist entries. No more editing XML by hand.