Skip to main content

JobJitsu Notifications

Notifications are polite taps on the shoulder, not sirens. They protect attention the way the product protects privacy.


Principles​

  1. Timely, not constant. Batch when possible; never gamify open rates.
  2. Actionable or clearly informational. If nothing to do, keep it quiet and dismissible.
  3. Calm urgency. Follow-ups use Amber caution — not error red — unless something broke.
  4. Respect focus. No sound by default; optional user toggle.
  5. Privacy-safe content. Notification text should not leak résumé contents to OS previews when avoidable; prefer “Follow-up ready” over pasted email bodies.

Channels​

ChannelUse forAvoid
In-app toastImmediate result of a user actionLong policy text
In-app inbox / bellFollow-ups, agent needs reviewMarketing tips
OS notificationTime-sensitive follow-up while app backgroundedEvery queue tick
Status bar badgeAgent · On-device readinessVanity counts

Severity → Presentation​

LevelColorWhen
InfoTeal / neutralStatus, tips, loading complete
SuccessJadeSend confirmed, save confirmed
CautionAmberFollow-up due, approval needed
ErrorClear error treatmentFailures — see ERROR_MESSAGES.md

Copy Patterns​

Needs review (agent)​

Title: Application ready for review
Body: Tailored draft is queued. Approve to send — you’re still in control.
Action: Review

Follow-up due​

Title: Follow-up ready
Body: Time to gently nudge — a polite reminder is ready.
Action: Open reminder

Agent ready​

Title: On-device model ready
Body: Warming complete. No data leaves this dojo.
Action: none / Dismiss

Preferences saved​

Title: Preferences saved
Body: The agent will use these on your next run.
Action: none

Approval required before send​

Title: Approval needed
Body: Send is blocked until you approve. Your rules, your signal.
Action: Review


Frequency & Batching​

  • Collapse repeated agent progress into one line: “3 applications queued” — not three toasts.
  • Follow-up OS notifications: at most one per role per reminder window.
  • Never notify for marketing, “streaks”, or inactivity shaming.

Behavior​

  • Toasts: auto-dismiss success/info (~4–6s); keep errors until dismissed or recovered.
  • Live regions: polite for info/success; assertive for errors.
  • Motion: toast rise per DESIGN_SYSTEM.md § Motion; honor reduced motion.

Don’ts​

  • Red badges for benign counts
  • “You’re falling behind!” inactivity pushes
  • Exclamation-stack titles (“Urgent!!!”)
  • Sound + banner + badge all at once for one event