Over at Betalogue, Pierre Igot, who has an eagle-eye for flaws in Apple’s user interface design, unloads on the behaviour of Mail’s Sent mail folder .

He points out:

Sending mail is a pretty essential process. When it comes to e-mail, it does not get much more basic than this. But for some reason, Mail 2.0’s user interface makes the process unnecessarily complicated and non-intuitive. The interface is OK (although still very inelegant) when things work as expected. But as soon as something fails, it’s a disaster.

What really annoys him is the way that the label of the Sent mail folder changes to “Sending…” when outgoing mail is being processed.

It’s ugly, he says, and it’s stupid. If you click on the “Sending…” folder, it displays all your sent messages except the one that is currently being sent. So where is it?

That’s the heart of the interface design failure:

It’s not in the “Sent” box, as we have just seen. It’s no longer in the “Drafts” box either…. So where is it? Well, that’s the kicker: It is nowhere. It is not in any visible part of the user interface in Mail. While the message is in the process of being sent, it effectively disappears from the user interface altogether and stays in some kind of UI limbo, until it’s finally sent—and then it miraculously reappears in the “Sent” box, as expected.

And don’t get him started on what happens next, especially if a message fails to send.

Read the whole post at Betalogue to find out how silly Mail is when that happens. mail.app, apple mail, Sent mail, sending, interface design, dumb dumb dumb, betalogue, bugs

Pierre Igot at Betalogue has some of the sharpest eyes in the blogging world. He repeatedly sees flaws in interface design that I overlook. Whether it is problems with the way Mail handles the format=flowed feature or threading, he’s got it nailed.

He’s done it again with iCal, pointing out something that I must have looked at a hundred times and never “seen”.

Pierre notes iCal’s inability to modify its language when the the value in question is not plural (as in this screenshot of an iCal alarm). He wonders whether anyone at Apple uses iCal and has noticed that it needs to be fixed.

Of course, it’s not earth-shattering. Still, Apple is a company that takes pride in the polish of its apps, so it rankles as Pierre point out:

Yeah, I know, it’s a detail. It’s not a bug. It doesn’t cause iCal to crash. It doesn’t cause iCal to fail to sound the alarm one hour before the event. So the problem is not high on anyone’s to-do list. But surely it is still somewhere on someone’s to-do list? And one day it will be fixed, right?

Now it will niggle at me too. ical, interface, alarms, apple, betalogue, Apple GUI, attention to detail

It is impossible to go away from a post by Pierre Igot at Betalogue without learning something new. Two recent post are no exception.

He details several shortcomings in the way that Mail presents the user interface for threaded messages and in the method it uses to auto-select a first message to display when any given thread is expanded.

A second post expands on the problems , especially how keyboard shortcuts operate in normal and threaded views.

Several of the issues arise because of the way in which Pierre likes to use Mail:

I use Mail with the so-called “message area” pane closed. In other words, my main mail viewer window in Mail consists of the mailbox list on the left-hand side and the message list on the right-hand side. I don’t have a third pane at the bottom displaying the contents of the currently selected message. I don’t like that, because when that “message area” pane is visible, any message in the message list becomes marked as read as soon as you select it, whether you actually want to read it or not.

People who use Mail in the same way will find the second post especially interesting.betalogue, mail.app, apple mail, keyboard shortcuts, bugs, threading, messages, preview pane

At Betalogue, Pierre Igot offers a demolition job on iCal’s user interface.

He points out a number of problems in design and operation with its text fields, contextual menus and information drawer.

I’ve been using iCal for two years now (since switching) and already I’ve become harden to these problems — I unconsciously work around them, I think it’s normal, I don’t see them at all anymore, if I ever did. But Pierre does.ical, user interface, bugs, alarms, betalogue, text fields, problems

Pierre Igot is a professional translator, writer, and Mac technical support person living in southwest Nova Scotia, Canada. He maintains his own web site of literature, music, and visuals at http://www.latext.com and his own blog at http://www.betalogue.com.

His primary home office machine is a Power Macintosh G5 Quad with 4.5 GB of RAM and two 500 MB Seagate hard drives, used with a dual-monitor setup consisting of an Apple Cinema HD 30″ display and an older Apple Cinema HD 23″ display. He uses all kinds of software in his daily computing activities, including Mac OS X 10.4, Mail, Safari, NetNewsWire, iTunes, iPhoto, GarageBand, Pages, Microsoft Office, Adobe Creative Suite 2, BBEdit, FileMaker Pro, etc.

HW: How long have you been using Mail.app? What other clients have you used (and why did you stop)?

PI: I switched from Eudora to Mail via Mailsmith in August 2002. I even wrote an article about the adventure at the time.

Basically, I was a long-time Eudora user, but had become disappointed with the lack of progress of the Mac OS X version. The program was in endless beta mode, there were lots of glitches, many core Mac OS X features were not supported, etc. Since I was also a long-time user and fan of Bare Bones Software’s BBEdit (mostly for web site authoring), I figured I would give Mailsmith , their e-mail client, a try.

I was thoroughly disappointed by Mailsmith. There was no integration with Mac OS X’s Address Book (at the time), and its own address book was really poor. (It didn’t even distinguish between first name and last name, forcing you type the names in reverse order to make sure they would be properly alphabetized!) But it had rather impressive filtering capabilities. I was willing to live with the flaws, but the deal breaker was the program’s performance, which was simply unacceptable.

I was also very wary of using a program where my entire e-mail archive was stored in a single (huge) database file. That was one of the primary reasons why I never even considered switching to Microsoft’s Entourage, even though I owned a copy of it as part of Microsoft Office. (As a long-time Microsoft Word user, I am also all too aware of the poor quality of Microsoft’s software for the Mac in general. I know that Entourage is supposed to be better, but on the handful of occasions where I actually tried using the program, I wasn’t particularly impressed. Things haven’t changed significantly since 2002 as far as I can tell.)

When I decided to switch to Mail, I was fully aware of its limitations. But there were too many benefits that outweighed the limitations: full Mac OS X integration with Address Book support, support for core Mac OS X features such as Quartz text smoothing, use of the “.mbox” file format for storing e-mail mailboxes, etc. And the price was nice too, of course.

I have been using Mail for nearly four years now, and, in spite of all the trials and tribulations, I haven’t regretted my choice. One thing I should emphasize for prospective switchers, however: If you want to switch from Eudora, make sure to use Eudora Mailbox Cleaner. I wasn’t aware of this application at the time, and ended up using the built-in import features in Mailsmith and then Mail to import my extensive archive of old e-mail. I am still living with the consequences of this process (badly encoded accented characters, HTML rendered as plain text, etc.) in some of my old e-mail.

HW: What plugins and extensions do you use to make your email experience better?

(more…)

At Betalogue, Pierre Igot reports two more annoyances in Apple Mail:

1. Mail 2.0: ?¢‚ǨÀú0 messages, 3 unread?¢‚Ǩ‚Ñ¢ — By doing several complicated things at once, he brings Mail.app‘s multi-threading ability to its knees.

   It shouldn’t happen, it shouldn’t be so hard to discover that the app has stalled and it shouldn’t be so difficult to unstick it.

   This leads to some reflections on how Mail.app might be better designed so that things like this are more transparent for average users.

2. Mail 2.0: ?¢‚ǨÀúUndo Mark as Junk?¢‚Ǩ‚Ñ¢ doesn?¢‚Ǩ‚Ñ¢t undo anything — Pierre has an email incorrectly-marked as Junk. If the Junk filter is on automatic, it will move the message to the Junk folder.

   But going to the Junk folder and selecting the message to “un-junk it”, he notes that clicking the “Undo Mark as Junk” option in the Edit menu or selecting “Mark as Not Junk” from the Message menu doesn’t do anything.

   I can’t reproduce this behaviour. When I do this, the message does get “un-junked”. And I guess that Apple Mail’s Spam database is updated in the background, but I agree it would be useful if Mail.app automatically restored the message to the mailbox from whence it came. (like Entourage does…Grrrr!!)

As always, excellent holiday reading!