Skip to content
View in the app

A better way to browse. Learn more.

Web Designer Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Still using Photoshop?

Featured Replies

Am I the only one who does not design websites from the ground up in graphic software?

 

 

These days, I use Photoshop as a tool purely to create the graphical elements that I cannot create using CSS.

 

I don't think I've ever actually designed a website in Photoshop.

That's all very well and I do my best to use as few graphics as possible, however it really dependson the client.

Many many clients want something visual to base their decisions on future plans on. It's never a viable or efficient way to CSS it including bug fixes.

 

In short it depends on the job at hand.

Some start as plain PSD mockups and some start as in browser mockups.

  • Author

Fair enough. I suppose because I'm employed I don't get those clients in the first place.

 

God help me if I do, cos my PS skills suck!

I need to show stakeholders at work what something will look like before we send it to development (and they aren't able to 'get' it from balsamiq mockups or sketches), so that's why we use Photoshop.

 

On my side projects I've tried designing in the browser before but I just feel that it takes longer to do things. I'm so proficient in photoshop that changing a mockup around isn't that difficult, where as changing a layout in code would be a little too difficult.

 

I think this is definitely a "different folks, different strokes" kind of thing though.

Blimey! I feel a bit old school. I usually start by sketching out a rough design on paper, then make a Photoshop wireframe or mock-up.

Edited by Spitfire

I've never done image based mockups, I've never owned Photoshop (tried it once, hated it).

 

Ever since I started web building last century I've always started with content and HTML wireframes, that way I can show clients a site actually working so they can click on it, interact with it, feel it - you can't do that with images :)

 

So brightonmike you're not the only one :)

  • Author

I've never done image based mockups, I've never owned Photoshop (tried it once, hated it).

 

Ever since I started web building last century I've always started with content and HTML wireframes, that way I can show clients a site actually working so they can click on it, interact with it, feel it - you can't do that with images :)

 

So brightonmike you're not the only one :)

 

 

Huzzah!

 

Also, it's not like you even have to start from scratch. You can use HTML5 Boilerplate as your foundation which saves you having to worry about resets and coding all those annoying bits that you have on every website anyway.

 

I've added various bits onto the boilerplate so it's my own sort of base.

 

I usually start by writing out some structure in the HTML - which in truth takes all of ten minutes.

 

E.g. wrapper, topnav, slider, section, footer.

 

Then I use my dev tools in Chrome to fiddle the styling, which I then copy over to Notepad++ when I want the change to be permanent.

 

And if you think CSS3 is too slow to code, try http://css3generator.com/

 

Plus, Paul Irish's very useful http://css3please.com/

 

The benefit of all this is that your draft designs reflect how the website will actually look and function, whereas a website coded from a Photoshop design never quite looks how it did in Photoshop.

Edited by brightonmike

Showing a mock-up in photoshop gives that "wow factor" that make client want to continue working with you so i am on the photoshop side.

  • Author

Why can't you do the same with a browser mock-up? Surely having a draft they can visit in their browser and actually interact with is going to be more of a "wow factor".

Personally I'm sort of with you a lot of the way Mike, I kind of do rough stuff in Photoshop up to the point where it's demonstrating the idea clearly, get that signed off then do the actual working mockup live in html. I think the clients sort of like to "visit" it and interact with it like its a proper web page.

 

I don't do photoshop to the point where it's exactly like the page, it may be for example just the framework with placeholders etc. but I don't try and reproduce the content in it too much, as it invariably looks slightly different (especially the text) when done in html.

I use PS because I used That before I started Coding.

 

 

I also stick to PS because I quite often give up on a design half way through for a number of Reasons and start again

Why can't you do the same with a browser mock-up? Surely having a draft they can visit in their browser and actually interact with is going to be more of a "wow factor".

 

 

Because of time constraints. I feel I'm quicker knocking up a design in photoshop then actually coding up a website for them to look at. Also, it's quicker to move elements around, change the layout, alter images etc etc in photoshop.

 

In your first post you said something like "you build all the elements in CSS and only use photoshop for bits that you cant do". I think thats how everyone works, and because I've used photoshop doesn't mean it's going to be a graphics intense website, I can just visualise the way the website is going to look; the font, the styles, the elements, the placements, the gradients. I find it much easier then constantly changing code around

  • Author

Each to their own then, I guess. For me, changing styles/layout is quicker to do in the code itself then Photoshop.

Another two benefits of HTML wireframes for me:

 

1. You can design for scenarios when users have images turned off in their browsers

2. I some part doesn't work and needs to change, eg moving a vertical navigation to a horizontal one, it's a few minutes to do with CSS, whereas several hours with an image editor

Why can't you do the same with a browser mock-up? Surely having a draft they can visit in their browser and actually interact with is going to be more of a "wow factor".

 

Because then you will actually need to make a ps file and slice it which is more work?

Changing a psd file is usually way easier then changing both images in psd and something in css / html as well.

 

I believe changing css/html might be faster only in 1 case which is:

1. Simple website without much images or programming.

 

Its not easier in 2 cases:

1. Graphic intensive website. Even if its not actually tons of graphics it might be some barely visible details on white but you need to draw them as well. Seeing how bandwidth is hardly a problem any more graphics is nice edition.

2. Programming intensive website with lots of forms php code java applets etc. You cant just write "search form will go here" and "products from DB will be loaded here" etc. Easier to draw them then to program them and re-program if client doesnt like smth.

Edited by Lieto

Each to their own then, I guess. For me, changing styles/layout is quicker to do in the code itself then Photoshop.

 

Exactly.

The thought of coding up a two column layout complete with CSS3 gradients and buttons (that may not work on the browser they're looking at it on, so having to then code bug fixes and image fall backs using Photoshop) but then also having to fall back into Photoshop to create image elements and optimise what i've been given, just to show a client what it may look like, strikes me as a horribly inefficient waste of my day.

 

For me the alternative is a quick bash out of a PSD mocking the basic layout and colours (including alternate colour schemes) with added wire-framing and descriptive tags. This file then gets saved out as a watermarked jpeg and sent on to the client safe in the knowledge that (a) it's exactly the same as it is on my screen (B) any additions can be added in seconds © Security is paramount, no code grabbing and only a sample watermarked image.

 

As has already been said, each to their own. Whichever way you find fastest is the way you find fastest. So the best method is to continue to do it like that!

  • Author

Because then you will actually need to make a ps file and slice it which is more work?

Changing a psd file is usually way easier then changing both images in psd and something in css / html as well.

 

 

You haven't read my posts, have you? I'm not using PS, at all. So there is no slicing involved.

 

Exactly.

The thought of coding up a two column layout complete with CSS3 gradients and buttons (that may not work on the browser they're looking at it on, so having to then code bug fixes and image fall backs using Photoshop) but then also having to fall back into Photoshop to create image elements and optimise what i've been given, just to show a client what it may look like, strikes me as a horribly inefficient waste of my day.

 

You have some fair points, but I think you're wording the process to make it sound longer and more drawn out then it really is. It takes mere moments to change colour schemes via CSS.

 

You mention browser discrepancies, but frankly as a client I think I'd be more annoyed that my website, in any browser, doesn't look how it did in the PSD which I suspect is a common problem. Fixing differences between browsers is not really that difficult, and if you use a Boilerplate with a CSS, the vast, vast majority of common browser discrepancies are ironed out for you already. Every time I've coded a static site based on Paul Irish's boilerplate, I've almost never had to then go back and fix issues with different browsers. It's that good.

 

Also, to stop code thieves, you can encrypt your code. Obviously you wouldn't encrypt the actual site when finished, but you can encrypt drafts to protect your code.

Edited by brightonmike

You haven't read my posts, have you? I'm not using PS, at all. So there is no slicing involved.

I did. First of all you didnt mention you are "not using PS, at all". Opening 10 psd files (i hope you have psd for every tiny image you have on the site, since i cant imagine editing jpegs, it will ruin them) to change color scheme or anything really is even less convenient. Thats like brain explosion to me — managing 10-30 psd files for single project when visual wasnt even confirmed yet. Every site have some sort of bullets, outliners, underliners, backgrounds, small icons, buttons, on mouse over behavior images etc, right?

 

And then client is like "hmm, can we try a bit lighter and greener color scheme"? And you are like "Sure let me edit my 20 images". While in ps you can just merge all color parts, cmd+u them and change hue / lightness / saturation to create roughly 10 options to choose from in less then 5 minutes.

Edited by Lieto

  • Author

I did. First of all you didnt mention you are "not using PS, at all". Opening 10 psd files (i hope you have psd for every tiny image you have on the site, since i cant imagine editing jpegs, it will ruin them) to change color scheme or anything really is even less convenient. Thats like brain explosion to me — managing 10-30 psd files for single project when visual wasnt even confirmed yet. Every site have some sort of bullets, outliners, underliners, backgrounds, small icons, buttons, on mouse over behavior images etc, right?

 

And then client is like "hmm, can we try a bit lighter and greener color scheme"? And you are like "Sure let me edit my 20 images". While in ps you can just merge all color parts, cmd+u them and change hue / lightness / saturation to create roughly 10 options to choose from in less then 5 minutes.

 

You're speculating a scenario that nobody in their right mind would play out. Why would anybody, however they design their websites, have 10-30 PSD files? Nonsense.

 

If I've ever had multiple images to support my design, for various elements, then they would be in ONE PSD and then sprited. Therefore changing them for me would be just as quick as you changing your elements in your single PSD also.

 

I don't generally use images for things like bullet points - even in IE8 you can make elements attractive without using images.

even in IE8 you can make elements attractive without using images.

Only problem is that they will be just as cute as on other 1 million web-sites -)

I am "speculating" possible scenario, nothing wrong with it imo. Just cant imagine functional web-site with less then 10-20 graphical elements.

Edited by Lieto

  • Author

Only problem is that they will be just as cute as on other 1 million web-sites -)

 

 

That's just a ridiculous comment, really.

You're speculating a scenario that nobody in their right mind would play out. Why would anybody, however they design their websites, have 10-30 PSD files? Nonsense.

 

To be fair you don't work as a freelancer and a lot of your arguments against designing in Photoshop are based on your experiences not the broader view.

You'd be surprised what i have received from clients in the ten years i've been doing this.

 

Remember that every client is different as is every professional.

 

I don't generally use images for things like bullet points - even in IE8 you can make elements attractive without using images.

 

Larger clients dictate what they want to see.

I worked for a publishing firm before and they dictated that bullet points must have a book icon. Try doing that in just CSS.

 

As i've said it's up to the professional what they use to reach the final goal and even though i agree with your method in some instances, it's not a 100~% viable method to use through the whole industry.

  • Author

I worked for a publishing firm before and they dictated that bullet points must have a book icon. Try doing that in just CSS.

 

I'm not sure what you mean in relation to my comment about 10-30PSDs. I honestly can't see why anyone would need that amount of PSDs, any good designer would at least confine all their UI elements to a single PSD - that's if they're doing them in PS.

 

And just to rile you...

 

http://nicolasgallagher.com/pure-css-gui-icons/demo/

 

Most even work in IE8. There's no book but I'm pretty sure you could make one.

 

:p

I'm not sure what you mean in relation to my comment about 10-30PSDs.

If you are doing it in one psd file you can just as well add text there and voila — you dont need to do ANYTHING in html or css.

 

bookmarked this one +1

 

Most even work in IE8. There's no book but I'm pretty sure you could make one.

Nothing in IE7, severely corrupted in ie8, slightly corrupted in ie9.

Edited by Lieto

I'm not sure what you mean in relation to my comment about 10-30PSDs. I honestly can't see why anyone would need that amount of PSDs, any good designer would at least confine all their UI elements to a single PSD - that's if they're doing them in PS.

 

You've hit the nail on the head there. "any good designer" which is a lovely dream of the utopian ideal but reality it is not.

 

And just to rile you...

 

http://nicolasgallagher.com/pure-css-gui-icons/demo/

 

Most even work in IE8. There's no book but I'm pretty sure you could make one.

 

:p

 

As nice as they may be, they're not anything like what the client wanted.

In truth i probably could have created the icons in CSS3 (had it been available then) but talk about code bloat! There are times when images still win out.

 

Rile me? Nah, i like these sort of discussions, it's why i joined the forum in the first place. It's always good to hear how other professionals are going about their work and seeing if it could help to become more efficient at yours. In this case, i don't think so but you never know ;)

  • Author

If you are doing it in one psd file you can just as well add text there and voila — you dont need to do ANYTHING in html or css.

 

But it's quicker for me to do it in HTML and CSS. I'm pig slow at designing websites in PS.

But it's quicker for me to do it in HTML and CSS. I'm pig slow at designing websites in PS.

 

Going by your sites, this obviously works for you and as a professional you should keep doing it which ever way you find more efficient.

But it's quicker for me to do it in HTML and CSS. I'm pig slow at designing websites in PS.

There are few ways it may go from there:

1. You ll stick to what works for you.

2. You ll try to get more familiar with PS and may as well increase your productivity.

 

Overall there is nothing wrong with going with css/html right away it just looks like you are doing more work then you otherwise could.

In best case scenario your way might be faster since you have everything done right away, in worst case scenario (lots of changes) PS way will be faster and since there are changes most of the times most of us prefer "PS way".

  • Author

I've no problem using PS to create elements. I designed a GUI for one of the most popular security surveillance systems produced in the UK last year in PS. My problem is I find it not well suited to designing web designs in full.

 

I honestly don't believe that for me personally designing websites from scratch using PS would increase my productivity.

I've no problem using PS to create elements. I designed a GUI for one of the most popular security surveillance systems produced in the UK last year in PS. My problem is I find it not well suited to designing web designs in full.

 

I honestly don't believe that for me personally designing websites from scratch using PS would increase my productivity.

 

You're absolutely right; PS isn't well suited to web design. It's also not even that great for UI work since icons don't snap to pixel grid yet (CS6...). I think the only reason I feel so comfortable there is that I've forced myself to learn the ins and outs to the point where the time it would take me to mockup a photoshop file is far less than that of in-browser work, so that's why I use it for me.

 

I doubt there is a right or wrong way to work. My personal philosophy is that you should use the tools that get the job done most efficiently for you, so I think your workflow is probably best for you.

 

Do you do sketching or anything before diving into code? Wireframes maybe? Or do you change the layout frequently while designing in-browser?

  • Author

To throw a spanner in the works:

 

http://designshack.net/articles/layouts/practical-design-considerations-for-responsive-sites/

 

I'd be interested to know how you people design responsive websites in Photoshop?

 

 

What I'd be interested also to see, is how far they will take the dev tools on Chrome. I'm surprised nobody has created a simple extension that gives you the ability to really easily edit colours, layouts etc directly in the browser.

--snip--

 

Haven't read the article you posted yet (short on time) but i will when i get a break as it looks interesting.

However I'll answer your question above.

 

A few clients sites have been responsive up to a point and i currently am re-designing my portfolio (whether i ever get there is a different story!) with the intention of it being responsive.

 

What i've been doing is starting with a grid system i developed of 990px (consisting of gutters of 10px) and designing around that. Width different sections in boxes it's easy to drag them and reposition the whole section depending on what screen size you want to look at and what size the client wants to see. I can then export various sizes for review just by turning off and on the various groups.

If I were going to build a responsive site I'd probably start by sketching out the various layout changes that needed to occur (starting with mobile first and working up). Then I'd pick some of the more important states (the first mobile view, maybe ~800px mark and a 960 grid point) and comp them up in Photoshop, at least roughly enough to see how or if the visual design elements needed to change. Obviously some of the work would be done on the fly, but I don't think that it would be necessary to remove Photoshop from the workflow of a responsive site.

If i have a client who wants a website I'll use photoshop and do 2/3 mock ups and take it from there.

 

If I know exactly what they need or its a personal site or a freebie I'll head straight to notepad

 

it all depends on what you want.

If i have a client who wants a website I'll use photoshop and do 2/3 mock ups and take it from there.

 

If I know exactly what they need or its a personal site or a freebie I'll head straight to notepad

 

it all depends on what you want.

 

 

I work the same way as ste, for personal stuff, I dont waste my time much with photoshop. But from my experience, the best way to work for a client is from psd to html.

  • 3 years later...

I think every tool has its reason to be acknowledged and needed. Each of them has a irreplaceable features.

Still using Photoshop?

so this kind of questions is hard to make a good answer.

This is an old topic, But we still use photoshop because it gives the client something visual to look at. If we were to build something in-house though we'd probably let the designers mockup modules on a whiteboard and I'd test their viability. Once all those are done I'd sit with the designer and we'd look at adding a skin to the whole thing.

 

As it stands with most projects I receive a PS file of the desktop version of the website from one of our designers, then the smaller screen versions I mock up in the browser. I am free to alter bits of the design to improve the experience, we do not believe in pixel perfect, as following pixel perfect will likely run into bloated code that is not re-useable nor scaleable.

I create simple working prototypes for clients rather than static visualisations. As a one man band, my workflow is simpler - I do the full lifecycle myself. For my requirements I can't justify the cost of Photoshop, so I use Paintshop Pro for graphics.

I do my design mockups in Photoshop because I like my clients to "see" how their final website will look. Otherwise I work straight from a framework such as Foundation.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.