Platform

14 documents

Apps that sync data, process uploads, or maintain state SHOULD use platform background execution APIs rather than relying on foreground presence.

All significant feature points and views MUST be deep linkable using the platform's native URL/deep link mechanism:

Apps available on multiple devices SHOULD support continuity features so users can start work on one device and resume on another.

Apps SHOULD use the platform notification system for timely, actionable alerts that respect user preferences.

Components and flows SHOULD be scriptable where the platform supports it:

App content SHOULD be discoverable through the platform's system search, enabling users to find content without opening the app.

Apps SHOULD participate in the platform's share and inter-app data exchange mechanisms to integrate with other apps and workflows.

Apps with time-sensitive or frequently checked data SHOULD provide widgets and glanceable surfaces on platforms that support them.

Windows

Use MVVM with [CommunityToolkit.Mvvm](https://learn.microsoft.com/en-us/dotnet/communitytoolkit/mvvm/) — source-gener...

- Use `d:DataContext` and `d:DesignInstance` for XAML designer preview data

Use built-in WinUI 3 controls — they implement Fluent 2 natively. Never custom-draw what a standard control can do.

XAML layout uses effective pixels (epx) — scaling is automatic for all XAML-rendered content.

- Use the single-project MSIX packaging model

WinUI 3 supports tri-state theming: Light, Dark, and High Contrast.