maui-app-lifecycle

# .NET MAUI App Lifecycle Handle application state transitions correctly in .NET MAUI. This skill covers the cross-platform Window lifecycle events, their platform-native mappings, and patterns for preserving state across backgrounding and resume cycles. ## When to Use - Saving or restoring state when the app backgrounds or resumes - Subscribing to Window lifecycle events (Created, Activated, Deactivated, Stopped, Resumed, Destroying) - Hooking into platform-native lifecycle callbacks via `ConfigureLifecycleEvents` - Deciding where to place initialization, teardown, or refresh logic - Understanding the difference between Deactivated and Stopped ## When Not to Use - Page-level navigation events — use Shell navigation guidance instead - Registering services at startup — use dependency injection guidance instead - Calling platform-specific APIs outside lifecycle context — use platform invoke guidance instead ## Inputs - The target lifecycle transition (e.g., "save draft when backgrounded", "refresh data on resume") - Which platforms the developer targets (Android, iOS, Mac Catalyst, Windows) - Whether the app uses multiple windows (iPad, Mac Catalyst, desktop Windows) ## App States A .NET MAUI app moves through four states: | State | Description | |---|---| | **Not Running** | Process does not exist | | **Running** | Foreground, receiving input | | **Deactivated** | Visible but lost focus (dialog, split-screen, notification shade) | | **Stopped** | Fully backgrounded, ...