Timeline for How should we hand-off and ticket UI designs to the devs to ensure the developed design matches the provided UI mockups, while still being agile?
Current License: CC BY-SA 4.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 16, 2020 at 13:44 | comment | added | Daniel | sorry chrylis, I don't understand the comment | |
Jul 15, 2020 at 23:20 | comment | added | chrylis -cautiouslyoptimistic- | Please allow me to contribute some materials to help you enlarge your soapbox. | |
Jul 15, 2020 at 20:16 | comment | added | Steve Jessop | Agreed: rather than throwing wrenches you want a collaborative process where you can ask a question at the earliest opportunity, which prevents time being wasted working on bad assumptions. So in the case of viewport and spacing, the minute the designer draws a big rectangle and marks it it "800x600 px", someone can say "OK, about that...", before the designer spends an afternoon figuring out how many pixels to allow for each compontent. | |
Jul 15, 2020 at 20:11 | comment | added | Daniel | I think your comments re-enforce the challenge of design and development being two separate efforts. The developer shouldn't be trying to throw a wrench in for the designer and the designers shouldn't be throwing their art over the wall to development. Together, they can use their knowledge and skills to come up with a great solution. | |
Jul 15, 2020 at 18:04 | comment | added | Steve Jessop | And yes, for viewport size you can say it's just something that anyone designing for the web absolutely needs to know about and decide for themselves as part of the design. But identifying annoying edge cases is a core part of a developer's job: less core for graphic designers. So, if it's not viewport size then your developer will find something. | |
Jul 15, 2020 at 18:01 | comment | added | Steve Jessop | "the platform you are developing in builds a whole additional abstraction on top of the HTML/CSS layer" or even, the HTML/CSS layer builds in a whole additional abstraction beyond what the designer has accounted for. For example, developers are the pedantic sorts of people who ask questions designers hate like, "OK, so you've told me all the spacings in pixels, so what if the viewport isn't the size you think it should be?" This is why CSS pixels aren't really pixels any more: the developers realised they were just being too pedantic! | |
Jul 15, 2020 at 5:29 | history | answered | Daniel | CC BY-SA 4.0 |