Notifications & Communication

Every notification spends user trust. Phones already deliver on the order of dozens of notifications a day (Pielot et al., MobileHCI 2014, logged an average of ~63/day back when that was novel), and each one competes for attention the product hasn't necessarily earned. Design the whole lifecycle — permission, channels, timing, and exit — not just the message.

Permission & priming

• Never ask on first launch. Ask in context, after an action that makes the value obvious ("Get notified when your order ships?"). Apple's own guidance: request authorization where the user understands why.
• Pre-permission prompts (soft ask): on iOS the system prompt can only be shown once, so the widespread convention is an in-app explainer first; only trigger the OS dialog after the user says yes to yours. A "not now" on your prompt costs nothing; a "Don't Allow" on the system prompt is nearly permanent (recovery requires a trip to Settings).
• iOS specifics: provisional authorization (iOS 12+) delivers quietly to Notification Center without any prompt — a legitimate trial channel; users can later upgrade to full alerts. Scheduled Summary and Focus (iOS 15+) mean your notification may be deferred regardless of intent.
• Android specifics: since Android 13 (API 33), notifications are opt-in via the POST_NOTIFICATIONS runtime permission — new installs are OFF by default and you must request like any dangerous permission (apps present before an upgrade to 13 are pre-granted). The pre-13 "on by default" assumption is dead; the priming playbook now applies to both platforms.

Categories, channels & user control

• Offer per-category controls (orders, messages, promotions, tips) in YOUR settings, not just the OS switch — the alternative to granular opt-out is total opt-out. Android formalizes this as notification channels (8.0+): users can silence or block each channel individually and you cannot programmatically re-enable one they've blocked, so name channels in user language and don't lump marketing into a "General" channel users need.
• Deep-link "Manage notifications" from the notification itself (Android exposes this natively; replicate on iOS in-app). When a user mutes a category, confirm and honor it everywhere — including email.

Timing, batching & quiet hours

• Interruptions have a real cost: Mark, Gudith & Klocke (CHI 2008) found interrupted workers finish tasks by working faster at the price of significantly more stress and frustration; Iqbal & Horvitz's field studies (CHI 2007) documented long resumption lags after alert-driven task switches. The oft-quoted "~23 minutes to refocus" figure comes from Gloria Mark's broader research program (popularized in her 2023 book Attention Span), not a single controlled study — cite it as such.
• Batch and digest by default for anything non-urgent: "5 new comments" beats five pings; offer daily/weekly digest as a user-selectable cadence. Reserve real-time interruption for messages from humans and time-critical events (security, delivery at the door).
• Respect quiet hours: honor OS Do Not Disturb/Focus, don't send marketing pushes late night in the RECIPIENT'S timezone, and offer in-product quiet hours where the OS doesn't (web, email cadence).

Badges & division of labor

• Badge etiquette: a badge is a promise of something actionable inside. Badges that never clear, count promos, or reappear after being checked train users to ignore them (and to delete apps). Clear on view, count only what the user considers unread, never badge marketing.
• Right channel for the job (convention, strongly held): push = timely, personally relevant, action-needed; in-app messages = contextual tips, feature announcements, upsells (they wait until the user is present — default here when unsure); email = records, summaries, anything to be re-found later; SMS = highest urgency only, strictest consent.

Email: transactional vs. marketing, and the legal floor

• Keep transactional email (receipts, resets, shipping) rigorously free of marketing — mixing endangers deliverability and, in consent regimes, its legal basis. Separate sending domains/subdomains are standard practice.
• Legal floor (verify current law for your market; this is a floor, not the goal): US CAN-SPAM — no deceptive headers/subject lines, a working opt-out honored within 10 business days, physical postal address; it permits opt-out marketing. EU GDPR + ePrivacy — prior opt-in consent for marketing email, with a narrow "soft opt-in" for your own similar products to existing customers; consent must be specific, unbundled, and as easy to withdraw as to give. Canada (CASL) is stricter still.
• Gmail/Yahoo bulk-sender rules (effective Feb 2024; verified): senders of ~5,000+ msgs/day to those providers must authenticate (SPF, DKIM, DMARC), keep spam-complaint rates under 0.3%, and support one-click unsubscribe via RFC 8058 List-Unsubscribe-Post headers, honored within two days. Non-compliance now means rejection, not just spam-foldering.

Lifecycle emails (label the evidence honestly)

Welcome (immediately post-signup, one job: deliver the promised value), onboarding sequence (behavior-triggered beats time-triggered — convention backed by vendor A/B data, not independent research), digest (user-chosen cadence), re-engagement ("here's what you missed" tied to real activity), win-back (a genuine offer or a goodbye). Most published "welcome emails get 4× open rates"-style numbers are vendor marketing statistics — treat as directional, A/B test in your own context, and sunset sequences that don't move retention. Send a "we'll stop emailing you" sunset notice to long-inactive addresses; it protects sender reputation and is honest.

Unsubscribe UX & the opt-out spiral

• One click means one click: no login wall, no "why are you leaving" gauntlet before the action, no 10-day silent limbo without confirmation. Offer down-shifting (fewer emails, digest only, pause 30 days) AFTER the unsubscribe is secured, not as an obstacle to it.
• Making opt-out hard is a dark pattern (see Persuasion, Ethics & Dark Patterns) and now also a deliverability liability: the hard-to-find unsubscribe converts into a spam complaint, which counts against the 0.3% ceiling.
• Notification fatigue is an opt-out spiral: each low-value ping raises the chance the user disables the whole channel, after which your critical messages die too. Track opt-out and complaint rates per category as first-class health metrics; the correct response to declining engagement is fewer, better messages — never more.

Sources

• Android Developers — "Notification runtime permission" (Android 13+ POST_NOTIFICATIONS); notification channels docs (developer.android.com).
• Apple Developer — "Asking permission to use notifications"; UserNotifications provisional authorization docs (developer.apple.com).
• Mark, G., Gudith, D. & Klocke, U. (2008). "The cost of interrupted work: more speed and stress." CHI '08; Mark, G. (2023). Attention Span.
• Iqbal, S. & Horvitz, E. (2007). "Disruption and recovery of computing tasks." CHI '07; (2010) alerting field study, CSCW '10.
• Pielot, M., Church, K. & de Oliveira, R. (2014). "An in-situ study of mobile phone notifications." MobileHCI '14.
• Google — "Email sender guidelines" (support.google.com/a/answer/81126); Yahoo Sender Hub (senders.yahooinc.com); IETF RFC 8058.
• US FTC — CAN-SPAM Act compliance guide; EU GDPR Art. 7 & ePrivacy Directive Art. 13 (soft opt-in).