Thunderbird’s Desktop Calendar Visual Redesign

Thunderbird 桌面日历：视觉重构

Thunderbird Desktop Calendar: A Design Journey Thunderbird 桌面日历：一段设计之旅

August 10, 2026 | Jesse M | 11 responses 2026 年 8 月 10 日 | Jesse M | 11 条评论

Hello, Thunderbird community and followers of the blog! This is Jesse from the design team. Today’s post is about our recent journey in redesigning the calendar portion of Thunderbird, and what you can expect us to deliver in the near future. 大家好，Thunderbird 社区的朋友们以及博客的读者们！我是来自设计团队的 Jesse。今天的文章将分享我们近期重构 Thunderbird 日历模块的历程，以及你们在不久的将来可以期待的成果。

The calendar is a key part of any productivity toolset, from your PC Desktop to your office wall. There has been a calendar in Thunderbird since early in the project, and like all parts of the application, it’s evolved on its own terms, for better or for worse. It has many layers of functionality, but the experience has lost parity with current UI standards — at this point, it feels stylistically dated and functionally convoluted. So, with the help of the design team and the developers and the community, we have taken on the task of modernizing and streamlining the calendar. This is my account of the designers’ part of that journey. 无论是在电脑桌面还是办公室墙上，日历都是任何生产力工具集中的关键部分。Thunderbird 自项目早期就内置了日历功能，正如应用程序的所有部分一样，它经历了各自的发展，无论好坏。它拥有多层功能，但其体验已不再符合当前的 UI 标准——从目前来看，它在风格上显得过时，在功能上显得复杂。因此，在设计团队、开发人员和社区的帮助下，我们承担起了现代化和精简日历的任务。以下是我对设计师在这一旅程中所做工作的记录。

The Big Picture

全局视角

Here are some of our guiding principles for this redesign: First, we are here to serve the entire user base, not just the technical experts, or the productivity enthusiasts, or the brand new adoptees. For this reason, the dialog with the community is critical: we need to understand as many of the use cases and interaction patterns as possible, and we want to support them broadly, and efficiently, and effectively. Our ideal solution is open and flexible, respecting the broad range of users who rely on Thunderbird. 以下是我们此次重构的一些指导原则：首先，我们旨在服务于全体用户群，而不仅仅是技术专家、生产力发烧友或新用户。因此，与社区的对话至关重要：我们需要尽可能多地了解使用场景和交互模式，并希望广泛、高效且有效地支持它们。我们理想的解决方案是开放且灵活的，尊重依赖 Thunderbird 的广大用户群体。

Second, a key point: Thunderbird is aiming higher than being simply “the other email client.” We are all committed to creating an experience that meets and exceeds expectations, and competes directly with the oliphaunts in the room: the Google Calendars, the Apple and Microsoft application suites, and the many targeted productivity apps that jockey for this space. And as always, we will do this transparently, with an open source philosophy, in collaboration with our users and contributors. 其次，一个关键点是：Thunderbird 的目标不仅仅是成为“另一款电子邮件客户端”。我们致力于创造一种能够达到并超越预期的体验，并直接与行业巨头竞争：如 Google 日历、Apple 和 Microsoft 的应用套件，以及许多争夺这一领域的专业生产力应用。一如既往，我们将秉持开源理念，以透明的方式与我们的用户和贡献者共同完成这一目标。

The Journey

旅程

This design journey has been ramping up for several years now, in parallel with other company initiatives (Mobile! Web! Accessibility!). As our design practice has evolved, we have worked on the project from several directions, redesigning dialogs and rethinking patterns and collecting insights. For a while, this meant a lot of partial designs, but without a guiding vision. 这段设计之旅已经进行了几年，与公司的其他计划（移动端！Web 端！无障碍！）并行推进。随着我们设计实践的演进，我们从多个方向开展工作，包括重构对话框、重新思考交互模式以及收集见解。在一段时间内，这意味着许多零散的设计，但缺乏一个统一的愿景。

Among these early designs, one of our success stories was a visual and functional update of the Event Details dialog, to replace the existing, rather archaic event details window (”archaic” both visually and in terms of code). These were one of the first redesigns to reach a point where it could be implemented — prioritized partly because it’s a self-contained element, able to be tested without reworking the whole calendar code base. 在这些早期设计中，我们的成功案例之一是对“事件详情”对话框的视觉和功能更新，旨在取代现有的、相当陈旧的事件详情窗口（在视觉和代码层面都很“陈旧”）。这是首批达到可实施阶段的重构之一——之所以优先考虑它，部分原因是它是一个独立的元素，无需重构整个日历代码库即可进行测试。

If you use Thunderbird Daily, you may recognize this: We’ve followed this pattern for several other bits and bobs, including the dialog for editing an event, and the notification for unanswered invitations. In all cases，these changes will create better contrast and visual hierarchy, and improve the visibility and organization of controls. 如果你使用 Thunderbird Daily 版本，你可能已经见过它：我们对其他几个部分也遵循了这种模式，包括编辑事件的对话框以及未回复邀请的通知。在所有情况下，这些更改都将创造更好的对比度和视觉层级，并提高控件的可见性和组织性。

This alone could provide enough work for several release cycles. But designing isolated elements creates inconsistency and debt, both for design and development. As the design process on Calendar increased in velocity, it became clear that we needed to articulate a unifying vision. 仅此一项工作就足以填满几个发布周期。但设计孤立的元素会造成设计和开发层面的不一致和技术债务。随着日历设计进程的加快，我们清楚地意识到，我们需要阐明一个统一的愿景。

Bringing it together

整合

With these designs setting a direction, we had to step back and decide how all the pieces would fit together. In order to do that, we still had to answer three more questions: How does the actual calendar grid look, set to view a day, a week, a month, or a year? How does the user change their view and navigate forward and backward? How does the user connect to their calendars, and manage them all in one place? 随着这些设计确定了方向，我们必须退后一步，决定如何将所有部分整合在一起。为此，我们还需要回答三个问题：当设置为日、周、月或年视图时，实际的日历网格看起来如何？用户如何更改视图并进行前后导航？用户如何连接到他们的日历，并在一个地方管理它们？

These considerations led us to a lean design, with screen space broken up into three main sections. First is the grid, which provides the main element at the center of the layout — the user’s primary workspace. Second is the navigation bar, directly above the grid. Third is a sidebar for managing calendars — the nerve center for your calendars and data sources. 这些考量引导我们走向一种精简的设计，将屏幕空间划分为三个主要部分。第一部分是网格，它是布局中心的主要元素，也是用户的主要工作区。第二部分是导航栏，位于网格的正上方。第三部分是用于管理日历的侧边栏——这是你日历和数据源的神经中枢。

This design, focused on the most important functional areas, provided a great foundation for all the necessary functionality, with low friction and strong fundamentals. The blueprint for our design (called a “wireframe” in the UX design world) ended up looking like this: 这种专注于最重要功能区域的设计，为所有必要的功能提供了坚实的基础，具有低摩擦力和强大的基本功。我们设计的蓝图（在 UX 设计领域称为“线框图”）最终看起来是这样的：

(Image placeholder: The grid acts as the user’s main workspace, and the header and navigation provide their basic controls.) （图片占位符：网格作为用户的主要工作区，页眉和导航提供基本控制。）

Given the wide range of our users’ scheduling needs, we decided the calendar sidebar should be collapsible, and useful at both large and small sizes, so that users could decide how much of a footprint they needed to manage their calendar list. 考虑到用户日程安排需求的多样性，我们决定日历侧边栏应该是可折叠的，并且在大尺寸和小尺寸下都应实用，以便用户可以决定他们需要多少空间来管理日历列表。

Where we go from here

未来展望

As these elements came together, we also turned outward and looked to our community for more feedback. Through the various stages of design, we published two TopicBox posts, and we ran a short but informative survey, looking for initial reactions to the direction we were taking. This feedback has been very encouraging, and also enlightening: we have seen a positive response to our designs, and we’ve also gathered lots of insights on what you cite as most important (task integration, platform interoperability, and a re-assessment of agenda, mini-month, and multi-week views, to name a few). These discussions gave us some additional confidence, but more so, they reminded us that we are still at the beginning of a longer arc. 随着这些元素的整合，我们也向外寻求社区的更多反馈。在设计的各个阶段，我们发布了两篇 TopicBox 文章，并进行了一项简短但信息量丰富的调查，以了解大家对我们所采取方向的初步反应。这些反馈非常令人鼓舞，也很有启发性：我们看到了对我们设计的积极响应，同时也收集到了许多关于你们认为最重要功能的见解（例如任务集成、平台互操作性，以及对议程、迷你月视图和多周视图的重新评估等）。这些讨论给了我们额外的信心，但更重要的是，它们提醒我们，我们仍处于一段更长旅程的起点。