Notifications Improvements — Refactor

🎯 The objective

Notifications and sync remain our top complaints from users. While we can address smaller bugs without a large-scale refactor, the truth is we may have to consider how we do syncing and how we show notifications. This will include giving users new options, more frequent syncing, improvements to sync reliability, and bug fixes that could not be repaired without a large refactor. It may also entail increasing the minimum Android version to make use of features we can’t currently use, however, that is negotiable and may not be a requirement for improvement.

🎒 Resources

• [github.com/thunderbird/thunderbird-support-reports/blob/main/lisa/2026/april.md#top-3-friction-points](http://github.com/thunderbird/thunderbird-support-reports/blob/main/lisa/2026/april.md#top-3-friction-points)
• https://github.com/thunderbird/thunderbird-android/tree/main/feature/notification
• https://github.com/thunderbird/thunderbird-android/blob/main/feature/notification/docs/notification-architecture.md
• https://developer.android.com/develop/ui/compose/notifications

🦮 Rules of the Road

🟢 In Scope

• Notification improvements to match user demands
• Syncing improvements to deliver notifications in a more timely fashion
• Large-scale changes to sync and notifications to facilitate faster delivery

🔴 Out of Scope

• Small bugs and regression bugs that we can fix before beginning a large rewrite of multiple features

🚧 Technical and/or Business Requirements

🏃 Milestones