Problem:

Currently, Proton Mail on Android provides a binary notification experience. Mail notifications either produce an alert sound or are disabled entirely. Because the vast majority of incoming emails are routine or non-urgent, every notification chime creates unnecessary cognitive friction and urgency to check the phone, while completely disabling notifications for less urgent tasks risks missing still time-sensitive messages from contacts or academic and work senders.

Proposed Solution:

Implement dynamic Android Notification Channels tied to Proton Mail folders or labels:

1. When a user creates or configures a folder or label, expose an option to register a dedicated Android Notification Channel for that tag.

2. Allow incoming messages routed to that label to dispatch through its specific notification channel.

3. This allows users to leverage native Android system settings to set custom ringtones, distinct vibration patterns, or completely silent background delivery for lower-priority folders while keeping loud, distinct chimes reserved exclusively for urgent mail.

Technical Feasibility:

Because Proton Mail decrypts the notification payload locally on the Android device before constructing the notification, the application already has client-side access to folder, sender, and label metadata prior to calling the Android NotificationManager. Android has supported creating dynamic Notification Channels and Channel Groups at runtime since API 26 (Android 8.0), meaning there is no cryptographic limitation preventing this routing from occurring entirely on-device.