guettli/sharedinbox
1
0
Fork 0
Code Issues 21 Pull Requests 6 Actions Packages Projects Releases Wiki Activity

Native notifications: default vs important #86

New Issue
Open
opened 2026-05-15 07:15:43 +00:00 by guettli · 2 comments
guettli commented 2026-05-15 07:15:43 +00:00 (Migrated from codeberg.org)
Copy Link
Copy Source

I want some mails to pop up immediately.

By default mails should not popup.

Create a plan how this could be configured by the user.

Focus on user convenience. Implementation is not important now.

Labels:

  • State/InProgress — Set this when you start working on an issue
  • State/Question — Set this when you hit a blocker or need clarification
I want some mails to pop up immediately. By default mails should not popup. Create a plan how this could be configured by the user. Focus on user convenience. Implementation is not important now. --- Labels: - **State/InProgress** — Set this when you start working on an issue - **State/Question** — Set this when you hit a blocker or need clarification
guettlibot commented 2026-05-15 08:52:13 +00:00 (Migrated from codeberg.org)
Copy Link
Copy Source

Plan comment test

Plan comment test
guettlibot commented 2026-05-15 08:52:27 +00:00 (Migrated from codeberg.org)
Copy Link
Copy Source

Plan: Configurable notification level per account

User-facing design

Each account gets a Notifications setting in the Edit Account screen with three choices:

Level Behaviour
Off No notification (for noise/monitored mailboxes)
Silent (default) Notification in shade, no pop-up, no sound
Important Heads-up pop-up with sound

The setting is per-account, so one account can be silent while another pops up immediately.

Data model

Add an AccountNotificationLevel enum (off, silent, important) to the Account class. Default = silent.

No DB migration needed: the field lives in the existing secure-storage JSON blob; a missing key defaults to silent.

Android notification channels

Two channels created once at app startup:

  • new_mail_silent — Importance.defaultImportance, no forced sound
  • new_mail_important — Importance.high, Priority.high, default sound

showNewMailNotification receives the account-level setting, picks the right channel, or returns early for off.

UI

EditAccountScreen gets a Notifications section (a SegmentedButton with Off / Silent / Important). No extra screen or navigation needed.

Future scope (out of this issue)

  • iOS/macOS: same enum, different DarwinNotificationDetails wiring
  • Per-mailbox granularity (INBOX important, Promotions silent)
  • Auto-upgrade based on email Importance:/X-Priority: headers
## Plan: Configurable notification level per account ### User-facing design Each account gets a **Notifications** setting in the Edit Account screen with three choices: | Level | Behaviour | |---|---| | **Off** | No notification (for noise/monitored mailboxes) | | **Silent** *(default)* | Notification in shade, no pop-up, no sound | | **Important** | Heads-up pop-up with sound | The setting is per-account, so one account can be silent while another pops up immediately. ### Data model Add an `AccountNotificationLevel` enum (`off`, `silent`, `important`) to the `Account` class. Default = `silent`. No DB migration needed: the field lives in the existing secure-storage JSON blob; a missing key defaults to `silent`. ### Android notification channels Two channels created once at app startup: - `new_mail_silent` — `Importance.defaultImportance`, no forced sound - `new_mail_important` — `Importance.high`, `Priority.high`, default sound `showNewMailNotification` receives the account-level setting, picks the right channel, or returns early for `off`. ### UI `EditAccountScreen` gets a **Notifications** section (a `SegmentedButton` with Off / Silent / Important). No extra screen or navigation needed. ### Future scope (out of this issue) - iOS/macOS: same enum, different `DarwinNotificationDetails` wiring - Per-mailbox granularity (INBOX important, Promotions silent) - Auto-upgrade based on email `Importance:`/`X-Priority:` headers
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
NeedSupervisor
Issue escalated to a human supervisor; agentloop will skip it until cleared.
 State/InProgress
State/Later
State/Planned
automerge
Eligible for automatic merge by CI
 ci-failure
Issue opened by agentloop to track a failing CI workflow; used for deduplication.
 do-not-merge
Plan PR — review only, do not merge.
 loop/code
Add to run the built-in "code" prompt; override at prompts/code.md.
 loop/code-ci-pending
Prompt "code" finished; waiting for the PR's CI to pass before advancing.
 loop/code-done
Prompt "code" finished successfully.
 loop/code-in-process
Agent for the "code" prompt is currently running on this issue.
 loop/merge
Managed by agentloop
 loop/merge-done
Managed by agentloop
 loop/merge-in-process
Managed by agentloop
 loop/plan
Add to run the built-in "plan" prompt; override at prompts/plan.md.
 loop/plan-done
Prompt "plan" finished successfully.
 loop/plan-in-process
Agent for the "plan" prompt is currently running on this issue.
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
guettlibot guettli
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: guettli/sharedinbox#86