Earlier quoted context omitted.
Looks really bad on my retina Macbook pro, all pixelated. If he's to do that JPG stuff, he ought to include x2 images :)
The retina Macbook is going to be in a small minority for a while yet- don't expect people to be leaping out of their seats to accomodate you!
Re-Designing the classic email client
201–210 of 222 posts
Re: Re-Designing the classic email client
#202I love this concept. I'm curious how well this would work for multiple projects, a blend of personal and work email, and high-volume inboxes. Seems like it'd really need some type of labeling in addition to the actionsteps. Hopefully I get some free time this week, I might look into building some of this. Looks like fun.
I've been working on something similar in the past year and I'm considering bringing it back.
Re: Re-Designing the classic email client
#203Earlier quoted context omitted.
Messages will send as an SMS if the iMessage isn't delivered in a reasonably short amount of time.
Interesting, but does that mean delivered all the way to the recipient, or just to the iMessage server? Is there good feedback? If I'm in a low-signal area, I need to know how long to leave my phone in that one spot that gets signal.
Re: Re-Designing the classic email client
#204Earlier quoted context omitted.
Any other areas of your life where you throw the baby out with the bath water? Someone over salt some food so you assume that everything they say or do with food is wrong? Refuse to ever get a lift with a friend because they forgot to indicate once so obviously they can't be trusted to drive? I'm not wild about the way he's presented his website but I'm still willing to look at his ideas about e-mail workflow with an…
Someone's Photoshop mock-ups could have new ideas to introduce, yes. This doesn't. It's just triage of messages as they come in and an all-attachments view, coupled with hand-waving about typography and design by someone who hopes a developer will contact him.
Re: Re-Designing the classic email client
#205Immediate thoughts: From a business perspective, 3 steps like that isn't enough. What I really want is email completely integrated with a CRM/Project management tool & a calendar - I have tried Googl Apps and the whole Email / Tasks / Calendar separation just doesn't work. From what I've seen Exchange comes close, and I believe one of the others (Zimbra?) does too. The problem with email is everyone uses it different…
Re: Re-Designing the classic email client
#206Don't fix email. Fix communication. Why, 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…
In my kitchen I have: 1. A fridge 2. A coffee machine 3. A stove 4. A microwave 5. A blender 6. Mixing bowls 7. Measuring cups All I want to do is feed myself. Why on earth do I need to have so many different things to do it? To...most people, having a separate "app" for things that do wildly different things is a good . Skype and email fill completely different roles to me, and I suspect they fill completely differe…
Re: Re-Designing the classic email client
#207Re: Re-Designing the classic email client
#208The layout of the page (or lack thereof) makes it hard to know what portion you must focus on. The flow is really messy.
This was my hangup. My eye was going towards all of the heavy red and black shapes and not the screenshots themselves.
Re: Re-Designing the classic email client
#209Earlier quoted context omitted.
I'm not sure how this really addresses anything in the parent post. Sure, interoperability sucks, but surely you're not suggesting that the solution is to glom everything together into a single monolithic app that does everything? By all means, fix the fact that tools are painful when you want them to work together. Maybe unify a few of those communications tools.
> Let me communicate with a unified UI and unified contacts. This was from the top comment. It is suggesting the solution is to glom everything together. I think the comment you are responding to is concurring with their parent comment by providing an illustration of the concerns raised.
Basically, it shouldn't matter what service someone is using. What really matters to people is people. If someone is at their computer, they might want to use Facebook messenger. If they're away, they'll want to use text. Barring that, they might rather use email. The point is, someone shouldn't have to open the Facebook app, find they're not online, send a text only to wait for a response and assume they do or do not have their phone on them, then send an email. If they can do it with one app, the app telling them the best way to contact someone, it makes communication much easier.
No one has gotten it right yet, but I feel WebOS and Windows Phone are closer than the traditional discrete applications.