hn.today

Why sending notifications is a nightmare for engineers

notifkit.dev33 points35 comments
Screenshot of Why sending notifications is a nightmare for engineers

Commenters disagreed over whether notification delivery is genuinely an engineering nightmare or a problem being overstated to sell a product. Some called the proposal sales-y or an AI-generated solution in search of a problem, arguing that email works for most cases and an MTA can handle sending in the background. Others said notifications should use platform controls on iOS or Android, or services such as Telegram, Slack, and Discord, rather than email - especially for critical alerts. Several commenters stressed that the right channel depends on users and circumstances: one company relies on email for healthcare customers whose locked-down machines and lack of mobile signal limit alternatives.

A commenter with experience building Facebook Live notifications at millions of sends per second described a different kind of complexity: spikes require throttling, and systems should hand off notifications to a reliable service that schedules, sends, and retries asynchronously. They advised separating urgent, explicitly requested notifications from lower-priority or recommendation-based ones. Their view that quiet hours add opaque complexity drew disagreement from commenters who see notifications arriving during sleep as a real concern; others said users can silence their devices. The broader divide was between treating notification delivery as infrastructure that needs queues, prioritization, and scaling, and treating it as a straightforward application feature whose best channel and controls depend on the audience.

Read on notifkit.dev35 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Programming

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.