4 ms·

I've often just seen it referred to as "designing in the browser." Simple enough I'd think. Unfortunately any designing that's dealt with clients knows it's mu

I've often just seen it referred to as "designing in the browser." Simple enough I'd think. Unfortunately any designing that's dealt with clients knows it's much easier to convince them of something they weren't previously aware of when it comes off as some new movement/idea/trend/etc. It's why Apple brands everything they introduce to their products, even if it's a technology thats been around for years. Telling client, "I know most designers do PSD mockups first, but I just design in the browser instead," likely wouldn't go over very well as they feel they're getting less than they otherwise would, even if the missing part is wasted time. I personally havn't come across a client that'd go for pure designing in the browser (yet). Instead I've generally just encouraged a hybrid approach where the final PSD's are subject to changes and subtle tweaks once in development so that the PSD's can be seen as a rough draft and not necessarily a pixel perfect execution. My most recent client was skeptical, but I think I managed to sell it with something like: "Does a painter paint a painting of his painting before he paints it?"

gilrain 13y ago
> "Does a painter paint a painting of his painting before he paints it?" Yes, frequently! (http://en.wikipedia.org/wiki/Study_%28art%29 http://en.wikipedia.org/wiki/Study_%28art%29) I'm also trying to push designing in the browser, and it's how I do all my personal projects. Just pointing out you may get a retort from a client if you keep using that example.
blindhippo 13y ago
I suspect most clients will never be comfortable with "designing in the browser" for exactly the reasons you state. It does come across as amateur. There is another reason this wouldn't work for most projects. Many, many projects are not just web based. They are part of an overall campaign that includes assets for all different types of media, especially print. Designers have to create assets for all potential media in the campaign, designing in the browser would be duplicating work. However, if all you're concerned with is a pump and dump web product, then this approach may have merit.
- redblacktree 13y ago
  What do you mean by "pump and dump web project?"

gilrain 13y ago

> "Does a painter paint a painting of his painting before he paints it?" Yes, frequently! (http://en.wikipedia.org/wiki/Study_%28art%29 http://en.wikipedia.org/wiki/Study_%28art%29) I'm also trying to push designing in the browser, and it's how I do all my personal projects. Just pointing out you may get a retort from a client if you keep using that example.

blindhippo 13y ago

I suspect most clients will never be comfortable with "designing in the browser" for exactly the reasons you state. It does come across as amateur. There is another reason this wouldn't work for most projects. Many, many projects are not just web based. They are part of an overall campaign that includes assets for all different types of media, especially print. Designers have to create assets for all potential media in the campaign, designing in the browser would be duplicating work. However, if all you're concerned with is a pump and dump web product, then this approach may have merit.

redblacktree 13y ago
What do you mean by "pump and dump web project?"