Project 1d: Designer-developer relations

Following advice I heard from Chris, CEO of The Futur, when requesting feedback from designers I asked them to annotate a screenshot of the page, rather than let them make edits to the stylesheet. It’s easy to see why a designer proficient in CSS would want to simply make the correct changes to the code rather than go down the tough road of talking to a dev, however, this is clearly not a sustainable model. This is one thing I really appreciate John Fass, course leader and lecturer, pressuring students to do. Making us articulate clearly what we really mean. This removes the deadly ambiguity in our communication and the nonsense corporate marketing speak.

Pinhole camera project webpage deign iteration • Ran Cheng

Jared Spoole riled up many designers when he tweeted that anyone who influences what the design becomes is the designer”. Many designers saw this as a threat to their job. As a result of the delta between the design in the mind of the designer, and the technical perspective from the developer, code tends to not fully reflect the intent of design decisions made. Developers will be filling in pieces, as did I in this design, when the answers to technical questions are not provided by the designer upfront. For instance, super simple responsive layout question. When viewed on an 11″ laptop this layout simply fits into the width of the viewport, however, I was not told how to treat the layout when viewed on a 27″ display for instance. For this reason, the first revision of the markup did not account for additional padding to the right and left of the centered content on larger displays. In this case, thought role playing a developer and only making superficial changes, I was 100% making design decisions.

Project currently live here.

‹ Part c

Next project ›