> We found that what we liked best in a Müller-Brockmann book or on the screen in photoshop was not what we liked best on real data. Photoshop type rendering is

> We found that what we liked best in a Müller-Brockmann book or on the screen in photoshop was not what we liked best on real data. Photoshop type rendering is pretty poor, which is another reason going straight from print to code worked well for us. Really good call to omit Photoshop altogether from design endeavors like this. It's a waste of time copy/pasting actual data into your comp, whenever you want to change part of your design, you have to repeat it manually with all the other elements on the page, the fonts render poorly... We lately try to go from sketch to simple HTML mockups. Having actual data readily available while designing is such an eye-opener. Thanks to web inspector, we can tweak the styles and see the changes get reflected in the entire page. Sometimes when we want to play with the layout, we take a screen grab, cut and move things around in Fireworks. Nicholas Felton, about the Facebook timeline design: "You can come into a meeting with a very beautiful comp and it’s like, ‘Oh yes, we should do it that way,’. But you’re never going to know if you can do it that way until you pump in the real data and live with it for days or weeks". I don't understand how Photoshop is still considered a web design tool. Unless designing a marketing site with no content, it hinders good design more than it facilitates.