holy shit just write your web pages in html, not everything needs to be a crazy javascript abomination where the body text fades in slowly
That's just mean. Comments like this ^ sidetrack the whole post from what-could-be an interesting discussion into a group bashing over irrelevant little details.
Re-Designing the classic email client
31–40 of 222 posts
Re: Re-Designing the classic email client
#32Re: Re-Designing the classic email client
#33Is there anything out there right now that handles email attachments like described in this pitch? I would love the ability to see all the attachments ever sent to me, organized by date/sender/filetype. Or clicking on a contact and seeing all attachments I've shared with that person.
Re: Re-Designing the classic email client
#34The only real complaints I have about email with a well-configured text client are: * HTML mail from idiots * Syncing on multiple machines, with offline mode (IMAP is ok, but you want to keep full repositories on laptops for use without network, and ideally to process email more quickly than network access) * Mobile clients -- Android has K9Mail, haven't found anything great on iOS yet. The keyboard-based mail workflow doesn't translate to the tablet/phone form factor, but triggers do even more so, so there should be something there * Handling attachments well * Global directory across organizations (FB/LinkedIn/etc. integration could help a lot) * Multi-user mailboxes; you need some kind of ticketing/tagging/CRM on top of it, and these are all standalone, sometimes web based, and fairly universally suck. There are ways to tie them into plain email though.
Re: Re-Designing the classic email client
#35I like the idea of creating actions from within your email client. Integration with some project management tools like pivotal or trello would really smooth off this part of my workflow.
Re: Re-Designing the classic email client
#36Why, on my iPhone, do I have:
1. An email app (which required a major update to unite mail boxes)
2. A "messages" app (which abstracts out two different message systems)
3. A phone app
4. A contacts app
5. Twitter
6. Facebook
7. Skype
What I want to do is (a) send messages to people (I don't care how), (b) check messages I've received (from anyone, using any method), (c) manage my messages (both incoming and outgoing), and -- as the writer of the article points out -- (d) manage my attachments.
On the iPhone (which is by no means the worst case) I might end up doing something stupid like looking up a contact, phone them, get sent to voicemail. Go back to the contact. Use a slightly different path to send an SMS. Discover it doesn't get sent. Switch to mail, and send a message.
Meanwhile the recipient gets a missed call, an empty voicemail, eventually gets the SMS, and then receives an email -- in three different apps on their iPhone.
Tiny incremental improvements to email will only nibble at the edges of the larger problem. Let me communicate with a unified UI and unified contacts.
Re: Re-Designing the classic email client
#37Also, I tried the social thing with emails, and what it looks great in theory. However, I really don't get a lot of emails from people I'm friends with on Facebook or follow on Twitter.
Re: Re-Designing the classic email client
#38holy shit just write your web pages in html, not everything needs to be a crazy javascript abomination where the body text fades in slowly
That's just mean. Comments like this ^ sidetrack the whole post from what-could-be an interesting discussion into a group bashing over irrelevant little details.
His project seems interesting, but sometimes ad hominem attacks can be relevant.
Re: Re-Designing the classic email client
#39The layout of the page (or lack thereof) makes it hard to know what portion you must focus on. The flow is really messy.
Re: Re-Designing the classic email client
#40Earlier quoted context omitted.
That's just mean. Comments like this ^ sidetrack the whole post from what-could-be an interesting discussion into a group bashing over irrelevant little details.
These kinds of comments aren't necessarily inappropriate here. When someone's writing about "great interaction design", it's reasonable to point out the terrible interaction design of their site. If someone were discussing "great font design" on their blog and using Comic Sans, it'd be pretty surprising if they were not attacked.
Also, questioning someone's font survey by attacking their use of Comic Sans is, bluntly put, retarded. You still need to account for the quality of the content to make a judgement.