UX Priorities.

Unicorn.Consulting unicorn.consulting at gmail.com
Fri Mar 23 23:41:41 UTC 2012

On 24/03/2012 4:54 AM, Blake Winton wrote:
> Hey TB-Planners,
> Now that all the big features are landed, and we have some time to 
> breathe again, I've been thinking a little bit about what we want to 
> do on Thunderbird's front-end over the next couple of releases.
In general I think that the compose in a tab (optional) should be at the 
top.  In saying that, I don't see this as a compose in Tab so much as 
either replace for fix the existing composer. The pain point for users 
is not the absence of the tab, it is the creaking and unwieldy composer 

Bug 250539 <https://bugzilla.mozilla.org/show_bug.cgi?id=250539>   is 
one that appears in support on a regular basis and clearly is a big issue.

Users also complain that they can't edit the HTML directly (I think this 
is an offshoot of the clunky design tools, not a real interest in HTML 
editing. Although it would be nice to be able to switch to HTML ala Blogger)

I would also suggest that introducing Compose in a tab without fixing 
the composer code would be worse than doing nothing at all. Users are 
disgruntled but sort of accepting that the composer is clearly not 
getting any attention.  Introducing the 'compose in a tab'  without due 
fixes to the composer would rightly or wrongly lead users to the view 
that the composer is receiving attention, but it is the fancy stuff, not 
the basic usability of the composer and it more than likely going to 
upset them


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/tb-planning/attachments/20120324/591de712/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4938 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.mozilla.org/pipermail/tb-planning/attachments/20120324/591de712/attachment.p7s>

More information about the tb-planning mailing list