• Sean LesterSean Lester, 9 years ago (edited 9 years ago )

    We will typically overlay a screenshot of the coded page on top of the mock - perhaps turning it into a GIF to show the difference, then cry, then TRY and bring it up to someone who ultimately doesn't think it matters. This isn't helpful, I know. u.u

    1 point
    • Bowen LiBowen Li, 9 years ago

      "Let go your earthly tether, enter the void, empty and become wind."

      Seriously though, pixel perfect implementation for web applications has massively diminishing returns. Given the range of screen sizes, browser zoom, fonts, and text / color rendering differences between browsers, it quickly becomes impossible on any medium-large complexity site.

      0 points
      • Sean LesterSean Lester, 9 years ago

        I would agree if we were talking about simply "pixel perfect implementation". But in our case, it's more they make up their own grid, sizes for everything, alignment, button sizes - basically enough things are wrong to where every page we mock turns into an embarrassing mess that in no way captures the elegance or intention of the mocks and no one here seems to think it matters.

        We are, however, a small company with limited resources and our only front end coders are actually back end programmers who are doing front end simply because there's no one else.

        2 points
        • Bowen LiBowen Li, 9 years ago

          I see what you are saying. What about defining a style guide, so there's no guesswork whenever you need a new button, form, header, etc.

          1 point
        • Cesar TorresCesar Torres, 9 years ago

          This elusive "talking" concept everyone is describing here should be happening all the time, not just in the implementation phase.

          There's a few steps you always go through in your design process; keep stakeholders in the loop during these. Not for "feedback" ("did you try putting this here?" — that's a whole different conversation, ha), but for buy-in — be that business-wise or tech-wise.

          We always build-in time for roadshowing a design recommendation, end to end, whether it's for the other designers on the team, the operations, marketing or exec teams — and definitely the oft-overlooked community and support teams.

          A product studio should be super collaborative, especially as a handoff and shipping stages near. You're creating design systems not just for the hell of it or because it's trendy — you're doing it because it's the helpful analytical part of designing print, web or mobile. Let the engineering team in on that. The team's workflow will be the better for it.

          1 point