Designers read this and developers will love you
photoshopetiquette.com
Designers read this and developers will love you
1–10 of 67 posts
Re: Designers read this and developers will love you
#2Thank you so much for this, I'll forward the link to a couple of developers I work with and I always have to explain how things should be done.
The last design I got was in pdf! :S
Re: Designers read this and developers will love you
#3I'm a frontend developer and I think some of these expectations make little sense. Giving a name to every layer is a lot of work and I don't care about it that much. I'll do my work with layers like "Layer 0 copy copy" as long as they're grouped. Having designer rename all the layers is a lot of work that would be better spent creatively. (Does your boss want to pay the designer for it?)
Another example: "#34 Be familiar with browser compatibility" - this is just your, developer's job. I cannot imagine expecting a designer to know about IE6 limitations (and tons of hacks and techniques to overcome them).
That said, I agree with many points, like naming files properly (which costs almost nothing) or careful use of blending modes (which are a lot of pain for the developer). Or careful use of gradients, especially over repeating patterns (#22).
Re: Designers read this and developers will love you
#4FYI its impossible to read on an iPhone, since the sidebar blocks the view. I tried to click the buttons on top, since they like close/hide buttons, but no reaction.
Re: Designers read this and developers will love you
#5I'm a frontend developer and I think some of these expectations make little sense. Giving a name to every layer is a lot of work and I don't care about it that much. I'll do my work with layers like "Layer 0 copy copy" as long as they're grouped. Having designer rename all the layers is a lot of work that would be better spent creatively. (Does your boss want to pay the designer for it?) Another example: "#34 Be fami…
"this is just your, developer's job"
Shockingly, it's not. Most places I know of are moving away from a the designer and frontend developer positions. It's a big cost savings, not just in salary but in cycle time as well. Our designer sends us his designs in HTML. There is no bickering over fonts, no pixel perfection, no stupid photoshop-isms -filters, drop shadows, embossing, etc. I'm pretty sure he doesn't even have photoshop.
If you're a web designer and you can't do this, it's time to learn. You're a theoretical web designer drawing pictures of websites.
Re: Designers read this and developers will love you
#6I'm a frontend developer and I think some of these expectations make little sense. Giving a name to every layer is a lot of work and I don't care about it that much. I'll do my work with layers like "Layer 0 copy copy" as long as they're grouped. Having designer rename all the layers is a lot of work that would be better spent creatively. (Does your boss want to pay the designer for it?) Another example: "#34 Be fami…
No, the designer has to know the medium he or she designs for.
If you don't understand the medium, you basically create pretty pictures. That's about it.
It's no different from designing newspapers, brochures, fashion.
Re: Designers read this and developers will love you
#7I'm a frontend developer and I think some of these expectations make little sense. Giving a name to every layer is a lot of work and I don't care about it that much. I'll do my work with layers like "Layer 0 copy copy" as long as they're grouped. Having designer rename all the layers is a lot of work that would be better spent creatively. (Does your boss want to pay the designer for it?) Another example: "#34 Be fami…
"this is just your, developer's job" Shockingly, it's not. Most places I know of are moving away from a the designer and frontend developer positions. It's a big cost savings, not just in salary but in cycle time as well. Our designer sends us his designs in HTML. There is no bickering over fonts, no pixel perfection, no stupid photoshop-isms -filters, drop shadows, embossing, etc. I'm pretty sure he doesn't even hav…
But then such designer is not a target for this "Manifesto".
BTW, I see value in having one person create designs as HTML files, but I also know a lot of designers who create beautiful, graphics-rich designs and don't know much about code. I suppose it's much harder to find people who can do both as good as separate people.
Re: Designers read this and developers will love you
#8[deleted]
Re: Designers read this and developers will love you
#9I'm a frontend developer and I think some of these expectations make little sense. Giving a name to every layer is a lot of work and I don't care about it that much. I'll do my work with layers like "Layer 0 copy copy" as long as they're grouped. Having designer rename all the layers is a lot of work that would be better spent creatively. (Does your boss want to pay the designer for it?) Another example: "#34 Be fami…
No, the designer has to know the medium he or she designs for. If you don't understand the medium, you basically create pretty pictures. That's about it. It's no different from designing newspapers, brochures, fashion.
[deleted]
Re: Designers read this and developers will love you
#10I'm a frontend developer and I think some of these expectations make little sense. Giving a name to every layer is a lot of work and I don't care about it that much. I'll do my work with layers like "Layer 0 copy copy" as long as they're grouped. Having designer rename all the layers is a lot of work that would be better spent creatively. (Does your boss want to pay the designer for it?) Another example: "#34 Be fami…
"this is just your, developer's job" Shockingly, it's not. Most places I know of are moving away from a the designer and frontend developer positions. It's a big cost savings, not just in salary but in cycle time as well. Our designer sends us his designs in HTML. There is no bickering over fonts, no pixel perfection, no stupid photoshop-isms -filters, drop shadows, embossing, etc. I'm pretty sure he doesn't even hav…
Most places I know of are moving away from a the designer and frontend developer positions.
Is just in regards to bare HTML/CSS or JavaScript interaction as well? I’d think most companies would be hard-pressed to find a designer that could write in the full HTML/CSS/JS stack needed for webapps these days and be equally competent in interaction or visual design – as ironic as that sounds – in which case FEDs are still very important in the process.