Android WorkManager Notifications

When To Use

• Use this skill when the request is about: android workmanager job, background reminder notification android, reliable retry workmanager.
• Primary outcome: Schedule reliable background work, reminders, and notification delivery with WorkManager and Android execution limits.
• Read references/patterns.md when you need the API-choice matrix for WorkManager vs foreground service vs alarms.
• Read references/scenarios.md for unique-work, notification-permission, and reminder-delivery review paths.
• Handoff skills when the scope expands:
• android-permissions-activity-results
• android-performance-observability

Workflow

1. Choose the right execution API first: WorkManager for deferrable guaranteed work, foreground services for ongoing user-visible work, and exact alarms only when clock-time precision and policy requirements truly demand them.
2. Make work idempotent and uniquely addressable with explicit names, input data contracts, backoff policy, and cancellation behavior.
3. Apply constraints, expedited work, and retry semantics only where they match user value and platform limits.
4. Build notification delivery as part of the contract: channels, importance, tap action, runtime permission handling, and graceful behavior when notifications are denied.
5. Validate duplicate scheduling, reboot/process death, and degraded states before handing off performance or permission-specific follow-up work.

Guardrails

• Keep background work idempotent and cancellation-aware.