Notifications and delivery
Define typed notifications, resolve recipient preferences, deliver across explicit channels, and retain one provider-independent history of every send.
Experimental
An FCM delivery seam with explicit provider transport and target lifecycle.
Define typed notifications, resolve recipient preferences, deliver across explicit channels, and retain one provider-independent history of every send.
Compose @playstack/delivery/fcm with an application-owned sender and encrypted device targets. Supply credentials and response normalization; retain product scheduling, recipient revalidation and invalid-token handling.
Delivery acceptance does not prove background execution or message receipt. Data-only hints and visible notifications have different platform policies; keep documents and secrets out of both.