Hey,

 

I am not sure and I personally wanted to know the difference between this two job title?

 

1. What's a designer job scope?
   
2. What's a designer limited to do?
   
3. What's a developer main job?
   
4. Does converting the PSD to HTML have to be done in the design part or the development part?
   
5. No programming codes involves for web designer?
   
6. Should they work together?
   

1. Web design
2. Web design
3. Web design
4. That's deal of html maker-up, coder
5. No
6. Definitely yes.

But...

Hey,

 

I am not sure and I personally wanted to know the difference between this two job title?

 

1. What's a designer job scope?
   
2. What's a designer limited to do?
   
3. What's a developer main job?
   
4. Does converting the PSD to HTML have to be done in the design part or the development part?
   
5. No programming codes involves for web designer?
   
6. Should they work together?
   

 

I think you are forgetting Front-End Developers.

 

Most of the companies I've worked for/with or talked to people who work for are structured as such:

 

Web Designer works with the client/requirements, sketches, wireframes and puts together a visual design in Photoshop or Fireworks.

 

Front-End Developer takes the PSD/PNG file, slices it up as needed and codes any and all HTML/CSS/JavaScript (because back end developers suck at good javascript).

 

Back-End Developer takes the working front end and ties it to the Ruby/PHP/ASP.NET backend.

 

 

I've also seen places that have the Web Designer handle the Visual Design and coding HTML/CSS/JS. The developer then ties in the back end. I think this is less common in good agencies or tech firms.

 

 

I work at a place where all I have to do is turn requirements into PSDs. I have enough experience in Front-End development to know what is possible and what is not, which makes Front-End devs much happier when they get a practical design. Only working with Photoshop provides me more time to focus on design and less time worrying about coding.

 

Oh... and OF COURSE they should work together. A good team requires communication and cooperation between all parties.

Edited April 13, 201115 yr by porkchops

So,

 

Web Designer (Front End) > PSD and HTML

Web Developer (Back End) > MySQL,.NET,PHP,Ruby, etc...

 

This is something that I am afraid of. I am not a good in slicing up the PSD!

Anyway... thanks for the information. Now I am clear on something which has been bothering me in the past few days!

 

Thank guys!

It helps to have a solid understanding of how site layout and structure are achieved through CSS and divs. Once you get a strong grasp on CSS it becomes a lot easier to design and slice comps in Photoshop. A lot of it is really document setup and layer management. So as you design your wireframes you shoud have CSS in mind. Then as you move into your design comps you should make sure to organize the different parts of your site into folders that allow for you to easily turn off parts of the site for you to slice out the necessary images.

web designer or UI designer - everything all about layout,PSD

Web Developer - converting the PSD to HTML code,programing language

Right?

I would question any web designer who doesn't know how to convert PSD to HTML. It's fundamental stuff and html/css are the easiest languages you will ever need to learn. Takes a while to master but you should be able to pick it up within a few weeks.

 

On a personal note, i consider myself a front-end developer and i do most of the design and backend stuff and i have developed intermediate PHP skills. Why? Because i can build better websites that way and my job prospects will always be good. Go and try and find a web designer position without the recruiter asking for HTML/CSS, PHP, jQuery/Javascript skills? Not on your nelly!

Edited April 13, 201115 yr by neilp

I would question any web designer who doesn't know how to convert PSD to HTML. It's fundamental stuff and html/css are the easiest languages you will ever need to learn. Takes a while to master but you should be able to pick it up within a few weeks.

 

Exactly. PSD to XHTML/CSS is Front-End. Backend is SSLs and databases. You have to remember that CSS is presentational, thus falling into the design side of things. And since CSS requires HTML to work, so does the semantic coding of the document structure. I'm sure this will vary slightly from firm to firm. As I know of several that have people who just design comps and then from there a production team takes over. But in general, every web designer should know the process quite well.

(because back end developers suck at good javascript).

bit of a generalisation isn't it?

Web Designer designs the layout of the website. Web Developer develops the coding for the website.

bit of a generalisation isn't it?

 

Not only that, completely the wrong way round in my experience