3 ms·

I'm a designer and frontend developer. I would find it odd for the end result of an HTML build to look any different from the design. I can't think of a reason

I'm a designer and frontend developer. I would find it odd for the end result of an HTML build to look any different from the design. I can't think of a reason why a developer (who's not involved in the UI or UX stages) would need to change anything, even by a pixel. That may also lead to problems down the road. If the mockup uses certain dimensions, paddings, line-heights, etc... why not translate them as indented? Especially in 2018. It wasn't fun making websites cross-browser friendly 20 years ago. Even 10 years ago.

edwintorok 8y ago
Why isn't the developer involved in the design? Might help to point out elements of the design that would take large amount of effort to implement faithfully. In fact why isn't the design done as a CSS to begin with?
mygo 8y ago
> I can't think of a reason why a developer (who's not involved in the UI or UX stages) would need to change anything, even by a pixel. I guess you supply your developers fully documented fluid-resizable, responsive, dynamic mockups with all possible states? That’s one lucky developer. As a designer and developer, most (extremely talented!) designers that I end up working with still send me their designs as static PSD’s, and they also don’t understand enough HTML to know which design-choices are costly and which are not, and which don’t scale well with the screen / text / content, etc. If the designer and developer don’t work together at the UI/UX stage then it’s completely understandable for the coded-up site to not be a pixel perfect carbon copy.
- pwython 8y ago
  I generally supply mockups for different breakpoints from Sketch (via Zeplin). Moving away from making web UI in Photoshop was a game changer for myself, and the other developers. Dimensions/spacing is easy to read, and nearly all styles are translated to CSS. Highly recommend telling your designer friends to try software like Sketch or InVision Studio.

edwintorok 8y ago

Why isn't the developer involved in the design? Might help to point out elements of the design that would take large amount of effort to implement faithfully. In fact why isn't the design done as a CSS to begin with?

mygo 8y ago

> I can't think of a reason why a developer (who's not involved in the UI or UX stages) would need to change anything, even by a pixel. I guess you supply your developers fully documented fluid-resizable, responsive, dynamic mockups with all possible states? That’s one lucky developer. As a designer and developer, most (extremely talented!) designers that I end up working with still send me their designs as static PSD’s, and they also don’t understand enough HTML to know which design-choices are costly and which are not, and which don’t scale well with the screen / text / content, etc. If the designer and developer don’t work together at the UI/UX stage then it’s completely understandable for the coded-up site to not be a pixel perfect carbon copy.

pwython 8y ago
I generally supply mockups for different breakpoints from Sketch (via Zeplin). Moving away from making web UI in Photoshop was a game changer for myself, and the other developers. Dimensions/spacing is easy to read, and nearly all styles are translated to CSS. Highly recommend telling your designer friends to try software like Sketch or InVision Studio.