joshuasortino

The latter. We have paid out, after expenses, millions to at least ten sellers on Teespring.

I was talking about the 10% of the time designers should be coding in this type of environment. (I.e. pushing polish code or hacking together a quick marketing page.)

Even if you haven't heard them, we still get complaints about the usability of the product! It's what we did with the feedback that matters.

As for the business decisions, those were decided by VPs and the business development team.

Yup.

I know the whole left/right brain thing isn't real science. I was using it as a common metaphor. Designers and engineers typically approach things differently. Learn from someone else's approach.

I should clarify, I wouldn't normally recommend using Git for PSDs or binary file collaboration in general.

My point was that a primarily right-brained designer should teach fellow right-brained designers how Git works. Things just make more sense that way.

I'd like to point out that this is the first Android phone which didn't emphasize the logos and manufacture. Most Androids have a horrible cluttered physical design, partly because manufactures slap their logo right on the front.

I was extremely frustrated that, while I had been "reserved" a ticket, the payment repeatedly timed out and I was kicked back to the "we're looking for tickets" page.

Oh well, I guess that's what happens when hundreds of thousands of people are DDoSing a page.

These trends are not because of HTML5. They are because of poor design decisions.

Interesting read. It's fun to hear the other side of the argument. I don't really agree. Some of these arguments could be applied to all mobile sites, not just responsive sites. If that's the case, we've debated the value of mobile sites for years and mobile sites have clearly won.

1. It Defeats User Expectation — This is not a fault of responsive design, but rather the designer. We need more, skilled responsive designers. A responsive site should act and feel like a regular mobile site.

2. It Costs More and Takes Longer — A mobile site usually requires two separate code bases. With a responsive site, you can maintain both the desktop and mobile experiences from the same place. Also, a good responsive designer is cheaper than a desktop and mobile designer. If it's costing more, you're doing it wrong.

3. Non-Responsive Designs Usually Work — This isn't specifically targeted at responsive design, but rather all mobile websites. By your logic, any mobile site is subpar. While I think you should always include a link to the desktop version (which can be easily achieved by switching out the stylesheet), I don't think desktop sites are superior. A desktop view might be appealing to a small percentage of power users, but the majority of users will appreciate a tailored experience. Just don't hide functionality. You should be able to accomplish the same tasks on mobile that can be achieved on the desktop.

4. There is Often No Load Time Benefit — You're doing it wrong. A good responsive design will have a much lighter weight than a desktop version. There is no reason a responsive site can't function in the same manner and achieve the same performance as a mobile website.

5. It’s a Compromise — Again, this is a power user issue. Always offer the option to view the desktop version.

It is silly to argue against mobile design. Screen real-estate is more valuable on a mobile device and our designs should reflect that. If your argument is responsive design doesn't offer performance benefits, than you probably need to reconsider your workflow and RWD structure.