↵

Why we skip Photoshop (posted 2008)(signalvnoise.com)

over 8 years ago from Brennan Smith, Designer

  • Rolando MurilloRolando Murillo, over 8 years ago

    Exactly my point, man. I can design high-fidelity screens at the speed of thought in Sketch. And also:

    What about the code quality? Designing in code adds a new level of complexity: writing decent code that can be used for production. This means that aside from the design—which needs a lot of thinking already—you need to think about writing good, reusable code and make sure it matches the front-end architecture, conventions, etc.

    Even if you do that AFTER the "design", you then need to refactor the whole thing (very time consuming in my experience). And…

    What about mobile? If your design is meant to be responsive—and that's most of the cases lately— , how do you design for mobile? You need to start using media queries, move things around and think about all what I mentioned early.

    —

    If you just do your job as a designer and design, the best of your time is used.

    1 point
    • Chris Aalid, over 8 years ago

      I totally agree with this.

      It's easy to whip out a live mockup with some quick coding, but I feel like you're either going quickly enough to iterate on your ideas in a timely manner, OR you're writing neat, maintainable code that will actually make sense weeks from now or when someone else needs to add onto it.

      If you're speeding through messy CSS to iterate a bunch of design changes, wouldn't you just have to go back and do tons of cleanup later?

      1 point