Sarah Parmenter: "I can’t design in the browser"

.net designer of the year on hybrid methods and issues with existing apps

.net designer of the year: "I can’t design in the browser"
Sarah Parmenter says that while many blogs advocate designing in the browser, doing so, for her, leads to dull results

In a post on her blog, award-winning designer Sarah Parmenter has said that she can't design in the browser. "It's a guilty secret I've been harbouring for about a year, I can't design directly into the browser," she revealed, stating that her creative brain switches at the point she opens her HTML/CSS editor, and "starts thinking in terms of structure and how to achieve the look of my design using as much native CSS as possible". Without the design to follow, her process breaks down, and designs end up suffering, "looking boxy, bland and uninspiring".

We asked Parmenter why she considered her post a guilty secret, and she told us: "There are so many blogs and tweets about how backwards designing in Photoshop/graphics editors is nowadays, in relation to responsive design. The only feasible alternative is to design directly in the browser, side-swiping static comps that won't show every breakpoint. There's always been talk about how clients signing off static imagery of a website is a bad thing, and I can completely see why." She added that only a hybrid method between the two will truly work, and finding that holy grail is proving difficult – ground we've covered before in .net, such as in The perfect web design app… and why it doesn't exist.

On current software and where it fails, Parmenter said that much of it clearly isn't built solely for user interface designers or for a quick iterative process, but she'd defend Photoshop: "It's a great tool, but it needs serious tweaks to make it less of a hack for a UI designer and more integrated into our process." However, Parmenter doesn't want software that would output code – "Some things should never be automated, and that's one of them" – and is instead hoping Photoshop will borrow some tricks from publishing software: "I'd love a global Photoshop stylesheet type of panel that would allow for quick global changes across multiple layers, the same as InDesign currently has. Photoshop's halfway there with Smart Objects but that still seems a clumsy way of doing minute tasks."

3 comments

Comment: 1

I really want to agree with Sarah on this because I'm tired of dull designs being hailed as the "next big thing" (e.g. Windows Metro). On the other hand, this discussion is ill-founded as the key issue here is "what is design". If design is the way things look than I agree with Sarah. But I believe design is more about how things work than how they look… Of course, if the two are disconnected it's just as bad. But designing in the browser allows for more thorough experimental design. You can design the flows, the interactions, the "feel" of the interface. You're then free to go back to your canvas of choice and add the artistic elements that create the uniqueness of the experience. But if you think you can design the totality of the experience in the canvas, you'll put yourself in a sore spot, focusing on the uniqueness way too soon…

TL;DR: canvas is for uniqueness; browser is for experience. Don't confuse the two.

Comment: 2

I agree with Sarah when it comes to visually designing elements, but as stated by levifig this is not to be confused with user experience design. This should be done and an interface prototyped before we hit Photoshop to do the high fidelity work.

Working in Photoshop becomes problematic for me when considering responsive web design and typography. I try to reconcile the former by starting with a layer that is divided up into my grid but I find typography a bit trickier. I'm looking forward to Adobe bridging the gap between Typekit and Photoshop.

I tried doing a purely browser based design for a personal experiment when initially embracing the whole responsive methodology, but it came out minimalistic and boxey... Photoshop helps you break out of that grid sometimes.

Comment: 3

I think it's common these days to do a little bit of both. I'm used to getting fully designed psd's to convert into a website. When it comes to responsive it's common to create design guidelines, patterns and almost a playbook of design rules. Then let the developer have at it.

However if you're as talented a designer as Sarah you have a great understanding of design and web. You'll also be two or three steps ahead in the design process. I don't think Sarah needs to feel guilty or behind on web design techniques.

Don't mess with success :)

Jesse
June issue on sale now!

The Week in Web Design

Sign up to our 'Week in Web Design' newsletter!

Hosting Directory
.net digital edition
Treat yourself to our geeky merchandise!
site stat collection