Hi Philippe,
Can you provide some examples of rules you might have for filtering
email directly into Chandler?
Another issue that hasn't been mentioned:
If we postulate that the emails users will want to put into Chandler
are the emails that represent tasks, invitations, and emails need to
be reviewed in more detail and/or replied to...when users file emails
into the special 'Chandler' IMAP folder, will they want to keep those
emails in the Inbox as flagged items?
Over and over again in our interviews, people lamented that their
Inboxes got out of control because they felt the need to keep 'emails
that need follow-up' in their Inbox, because it was basically the
only view they knew they would always be looking at / aware of.
It seems like the optimal workflow would be to set up a rule to
'Copy' flagged items to the Chandler IMAP folder, while
This gives users a familiar / easy affordance with which to 'add'
individual emails to Chandler without having to remove them from the
Inbox.
Mimi
See more in-line...
On Jul 19, 2006, at 10:52 PM, Philippe Bossut wrote:
Mimi Yin wrote:
On Jul 13, 2006, at 7:43 PM, Katie Capps Parlante wrote:
+ Drag and drop emails and attachments from other email clients.
Observation:
- one advantage of the IMAP solution is that you can create a
rule to copy items as they come in, vs moving them by hand.
For some scenarios this will work. But rules and filters are still
IMAP client features that are beyond a lot of people. It's also
extremely difficult, if not impossible to set up a rule or filter
for: Emails that will require follow-up.
True but having a rule to populate an IMAP "To Chandler" folder
does not prevent individual emails to be dragged and dropped
manually in it. I do that all the time because my simple rules
cannot capture every categorization subtleties.
I personally like the IMAP solution better because drag and drop
from an app to another is error prone and cumbersome on my screen
real estate challenged iBook... I currently never DnD between apps
because of this.
Yes this is true. Although the ability to drag an invitation directly
onto the calendar canvas to specify start time is pretty desirable.
In fact, a couple of interview subjects described this feature
verbatim, which indicates that it would discoverable. Many people
aren't even aware of the difference between IMAP and POP accounts
because they don't access their IMAP email account from multiple
clients.
I wonder how many users with similar machines do DnD between apps.
Mostly, this solution has the highest chance of discoverability.
It requires no setup on the part of the user, other than to
download and install Chandler. Everything else requires some
minimal amount of understanding of accounts and servers.
True again but the IMAP solution will bring Chandler much closer to
a real email solution with an embryonic IMAP workflow. We shouldn't
fool ourselves: if indeed rules and filters are beyond the
cognitive abilities of our target user, we'll have to implement a
full blown email client in Chandler sooner rather than later. For
the "bridge" solution, we should choose something which is a
stepping stone toward that full solution.
I'm not sure I understand the reasoning behind this. Can you elaborate?
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
