Ac Notification Systems

Sending notifications to your users' own channels: the notification as a routed artefact rather than an email, channel selection and the fan-out across email, push, in-app and SMS, delivery receipts and the retry paths that differ per channel, quiet hours and user preference as routing inputs, templates with per-channel context, digest and batch policies that respect attention, and the written notification record. It explains how a notification platform behaves; it never recommends a vendor and never decides how often to interrupt a user. Use when asking "notification system", "push notification", "in-app notification", "fan out", "notification preferences", "quiet hours", "digest", "read receipts", "cross-channel notification", "why did users turn off notifications". Not for mobile push implementation on one platform (ac-mobile-client-engineering), not for webhook delivery to endpoints you do not own (ac-webhook-and-async-delivery), not for email deliverability mechanics (ac-email-deliverability).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit 52289a69fb

Frequently asked questions

npx get-skill add jiayaoqijia/ac-notification-systems