Investigate Designing a Home Tab
|Thunderbird Home Tab|
|Status note||Developers and sponsor needed. Components posted. Duplicate of Home Tab " https://wiki.mozilla.org/Features/Thunderbird/Home_Tab ." The data from that page will be merged into this one. Updated specs. Better design posted.|
|Directly Responsible Individual||Blake Winton|
|Product marketing lead||`|
|Additional members||Nate Watson|
Stage 1: Definition
1. Feature overview
The idea behind a Thunderbird home tab is to provide a convenient start-point/ dashboard for Thunderbird users. When users start Thunderbird, they usually want to do 1 or more of the following: check what unread E-mails have been received, check the calender for events that day, compose a message, start the chat feature, or use some function from an add-on. Right now, the user has to check through all of their inboxes for new messages, switch to the calendar, check that, etc. The current start process for Thunderbird is inefficient. Thunderbird hometab would provide a streamlined workflow. The goal of this feature is to reduce the workload a user has to deal with when they start Thunderbird, come back to it after a while, wake up their computer, etc. This is important because one of the goals of Thunderbird's development is to provide faster software, and reducing required user interaction time is a way this can be implemented.
2. Users & use cases
The target users are users who use Thunderbird for more than just one inbox, "be it multiple inboxes or multiple features." The planned supported users are users who, when starting Thunderbird in one way or another, want to know what has come up, such as unread E-mail, events which occur that day, or launch a Thunderbird component.
Maybe the inclusion of app tabs in Thunderbird, but this can be bypassed. The Launchers are dependent on their related features.
Thunderbird home tab should provide the following:
A consolidated display of unread E-mails from all inboxes. REQUIRED
A list of all events scheduled for that day. OPTIONAL "Depends on use of Lightning"
A framework for launchers. REQUIRED
A new message launcher. REQUIRED
chat and twitter launchers OPTIONAL based on add-ons and the release of the chat feature.
An Add-On Manager launcher. OPTIONAL "not a frequent use case."
A to-do list. OPTIONAL
A common framework for Thunderbird to tell the user about relevant information, such as updates or crashes. REQUIRED
- Re-doing the core inbox page.
- Adding browsing features to Thunderbird.
- Sharing a home tab with Firefox "but this is a neat idea."
- major changes to the tab infrastructure.
Stage 2: Design
5. Functional specification
This feature will provide a tab which is open by default, and has a convenient internal means of performing all of the common tasks Thunderbird Users usually perform when starting Thunderbird; thus optimizing the workflow.
6. User experience design
The current prototype includes a central unread messages panel, list of upcoming Calendar events, launchers, a tabbed notepad, and an internal notification system which Thunderbird components are able to call. All of the requirements have a counterpart. The finalized version will have better iconography,
and will be less "retina burning colorful."
The Central inbox component will show all unread messages, but that piece hasn't been designed yet.
The notepad is simply some text areas with a tab system.
The calendar component will be greyed out if the user doesn't have lightning. It will be more detailed and much like the calendar notifications presently in Thunderbird.
The launchers include starters for: the address book,, calendar, Add-on manager, chat features "assuming these are implemented before this", new event editors in 2 forms, an about:about launcher, a settings launcher, and a new message editor.
The internal notification system is a list of things various Thunderbird pieces will want to convey, from updates to reminders. Every notification has 3 components: a delete button, the actual text, and a 3rd button with the text and 3rd button being defined by the function caller.
Stage 3: Planning
7. Implementation plan
Quality Assurance review
Stage 4: Development
Stage 5: Release
10. Landing criteria
|Theme / Goal||Experience,|
|Secondary roadmap||User Experience|
Team status notes
Aside from some designs, this feature's development hasn't started yet, nor is there any indication of when or if it will. The target release is not yet defined, but the currently assumed version is Thunderbird 18. Development is blocked, due of the lack of developers.