3 ms·
Not. See the NoPSD movement: http://thoughtworks.github.io/p2/issue02/continuous-design/ http://thoughtworks.github.io/p2/issue02/continuous-design/
by mpweiher 13y ago
Not.
See the NoPSD movement: http://thoughtworks.github.io/p2/issue02/continuous-design/ http://thoughtworks.github.io/p2/issue02/continuous-design/
- seivan 13y ago+1. I'm getting up to speed with Cocoa to the point where I might be faster than a designer with Photoshop... as long as we don't venture into wooden textures. :)
- platz 13y agoI think there's a difference between using Photoshop for exploratory purposes, and using Photoshop to produce a deliverable. I know Chris Coyier is a fan of using photoshop to explore a little bit, before you get into the mode of writing code, which he thinks can interfere with your creative process.
- nathanbarry 13y agoFor the vast majority of professional designers Photoshop is critical to creating design elements. Not everyone creates a final, pixel-perfect mockup in Photoshop, but those who don't use Photoshop for smaller parts of the design. It is very common to screenshot your rendered HTML/CSS, take that into Photoshop, design one portion of the interface, then take that back to code.
- mpweiher 13y agoAnd why is this a good thing?
- rfnslyr 13y agoWhy do you ask silly snide questions? Tell me what is fundamentally wrong with screenshotting an interface, playing with it a bit, coming up with something you like then turning it into code?
- cvburgess 13y agoIt's a lot of unnecessary, time-consimung back-and-forth that could be easily done in a program like Sketch. Every approach is unique to its designer, and it's situation. But I have yet to (personally) find Photoshop (or a hybrid approach) more effective and time-saving when you deal with a large project. Artboards are MUCH easier to keep track of and group, and with something like Mirror [1] you will save hours in exporting/slicing/sharing over the course of a project. Photoshop was not made for UI design. It can do it, but it will rarely be the best tool because Adobe is not catering features for that niche. [1] http://bohemiancoding.com/sketch/mirror/ http://bohemiancoding.com/sketch/mirror/
- ryanSrich 13y ago> Artboards are MUCH easier to keep track of and group, and with something like Mirror [1] you will save hours in exporting/slicing/sharing over the course of a project. Adobe actually has a tool for this. http://html.adobe.com/edge/inspect/ http://html.adobe.com/edge/inspect/ I'll go against the grain here and say that 80% of the UI design that I do is based in the browser. Certainly getting a style and architecture down is helpful before hand but the design really doesn't come to life until I get into code. Some might say that this isn't sustainable on a large project but I'd argue that using HTML/CSS and github as a tool is just as, if not more, useful than photoshop/sketch/whatever.
- rfnslyr 13y agoHmm is it worth learning Sketch? I'm a photoshop die hard but wow this program looks enticing. Do you have any good resources to learn more about how to develop with Sketch?
- cvburgess 13y agoYes, actually the Sketch Manual [1] (but who reads the manual?) and (my favorite) community resources [2] that you can download, play with, and re-use over and over. [1] http://bohemiancoding.com/sketch/help/ http://bohemiancoding.com/sketch/help/ [2] http://bohemiancoding.com/sketch/community/ http://bohemiancoding.com/sketch/community/
- rfnslyr 13y agoPersonally I much rather fine tune every pixel of my design so I know exactly what to do when I'm coding, just need to reference my screens.