Skip to main content

Channels

Channels are the core routing model in Pushmark. Each notification is sent into a channel, and subscribers to that channel receive the event in the app.

For now, the active product flow is centered on public channels. Private channels can be referenced as coming soon, but they should not be treated as generally available in docs yet.

Why channels matter​

Use channels to separate noise from signal:

  • deployments for release messages
  • infra-alerts for production incidents
  • downloads for long-running local tasks
  • personal-reminders for self-notifications

This keeps alert streams readable and makes channel-level sharing easier.

Naming guidance​

  • Use short, stable identifiers.
  • Prefer lowercase with dashes, such as weekly-report.
  • Avoid names tied to one-off incidents.
  • Create separate channels when urgency or audience differs.

One channel per workflow​

This is the best default for solo developers and small teams. It gives you enough isolation without creating channel sprawl.

One channel per environment​

For infrastructure alerts, a structure like prod-alerts, staging-alerts, and dev-alerts is often easier to reason about than one mixed alert stream.

One channel per audience​

If different people should receive different classes of messages, split by owner or team instead of by service.

Operational note​

Start with a small number of channels. If you create too many too early, the app becomes harder to scan and your notification habits degrade.