maui-device-capabilities

MAUI Device Capabilities

Use this skill when a MAUI app needs device services such as files, media, camera, location, or maps. Always pair runtime API calls with platform declarations and a user-friendly denied/cancelled path.

Workflow

1. Inspect target platforms and existing files under Platforms/Android, Platforms/iOS, Platforms/MacCatalyst, and Platforms/Windows.
2. Identify the exact capability and minimum permission needed.
3. Add platform declarations before requesting runtime permissions.
4. Request permissions close to the feature that needs them, after explaining why the app needs access.
5. Treat cancellation as normal user choice.
6. Keep device APIs behind services if ViewModels or tests should not depend on MAUI static APIs directly.
7. Validate on every target platform because permission names and UX differ.

Permission Pattern

var status = await Permissions.CheckStatusAsync<Permissions.LocationWhenInUse>();

if (status != PermissionStatus.Granted)
{
    status = await Permissions.RequestAsync<Permissions.LocationWhenInUse>();
}

if (status != PermissionStatus.Granted)
{
    PermissionDeniedMessage = "Location is off. Enable it in Settings to show nearby stores.";
    CanOpenSettings = true;
    SemanticScreenReader.Announce(PermissionDeniedMessage);
    return;
}

Do not repeatedly prompt after a user denies access. Show a feature-specific empty/blocked state that screen readers can observe, and when appropriate guide the user to app settings with an explicit button that calls AppInfo.ShowSettingsUI().

Platform Declaration Map