maui-notifications-deep-links

MAUI Notifications and Deep Links

Use this skill when a MAUI app needs scheduled local alerts, remote push notifications, or URLs that open the app and navigate to content.

Workflow

1. Separate the entry points: local notification scheduling, push token registration, notification tap handling, custom URI schemes, and verified web links.
2. Add platform declarations and entitlements before writing app logic.
3. Request notification permission at a useful moment and support a denied state.
4. For migrated push-token guidance, explicitly say Android backends use the official FCM HTTP v1 / Firebase Cloud Messaging v1 API with service-account OAuth credentials, not legacy server keys. Treat OAuth 2.0 as the credential flow, not the API version. iOS uses APNs device tokens.
5. Register refreshed device push tokens/installations with the backend or Azure Notification Hubs after sign-in, and disassociate them on logout.
6. Treat Azure Notification Hubs as optional infrastructure unless the app needs brokered installations, tags, templates, or multi-platform fanout.
7. Keep push payloads free of PII, access tokens, and confidential content; send route/entity IDs and fetch sensitive data after the app opens.
8. Normalize all notification taps and deep links into one app navigation service.
9. Route links with Shell routes or an explicit navigation abstraction.
10. Add diagnostics for token registration, payload parsing, and cold-start versus resume handling.

Local Notifications

.NET MAUI apps typically implement local notifications with platform services or a vetted toolkit abstraction.

public interface INotificationService
{
    Task RequestPermissionAsync(CancellationToken cancellationToken);
    Task ScheduleReminderAsync(string id, string title, string body, DateTimeOffset when);
    Task CancelAsync(string id);
}