Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

I'm working on a UX/UI process for my project, however I'm confused to understand the approach between UX/UI and front-end.

After a .psd is developed, who would be responsible to transform it into html/css?

share|improve this question
    
UI/front end developer should be working on the HTML/CSS. what is the current process in your company? –  Awesh Sep 5 '13 at 9:31
    
I think it varies depending on the size and priorities of the company. In my company, a graphic designer creates the PSD for web layout along with other print-based communication. The web designer slices and dices those graphics and writes the HTML/CSS to make it all work. Unfortunately, the print-media bias of our graphic designers means there is a lot of back and forth when their ideas do not translate well. Other UI elements are typically a collaboration of the web designer and the programmer. –  ph33nyx Sep 5 '13 at 17:50
    
I would have thought that some basic mockup/prototype will have already been developed before you take it to the detailed design stage in the UX/UI process. I wouldn't leave the coding right at the end because there might be design issues that need to be considered, and you need some guidance in terms of technical requirements/constraints before finalizing the design. The UX designer should be working closely with the graphic designer and developers as part of an iterative process rather than a straight hand-off/over. –  Michael Lai Sep 5 '13 at 23:47
add comment

2 Answers

up vote 3 down vote accepted

It entirely depend on your organizational structure as to who would be responsible to transform the psd designs to html/css.

But in a typical scenario, a designer is expected to take up their PSD files and prepare a set of image assets to be used in HTML/CSS and also create a specification document defining all styles used alongwith sizes. This specifications document should also capture any transitions/effects desired in the designed files.

Thereafter this document is typically passed onto either a front-end developer or to the core developer team who is responsible for writing html/css for the same.

In some cases however, it is the designer's responsibility to deliver the css file with all styles defined and then the dev team will build html around the defined css.

share|improve this answer
    
Got it. However, how the designer will prepare the assets if many components are jquery/plugins? Does it influence in something? –  Paul Martin Sep 7 '13 at 0:51
    
When I say assets, I meant images used in HTML which are commonly called image assets. So even if there are jquery/plugins required for creating final working pages, the structure is still defined in CSS and all specs and images are used. –  djagatram Sep 10 '13 at 17:32
add comment

In my company this is how it goes:

Interaction Designers are tasked with conceptualizing, and implementing high fidelity wireframes to give to the visual designer. Wireframes are annotated (this means we specify what certain elements do what, like if a modal pops up, we want it to bounce three times for instance).

Once we have all the wireframes annotated and sent to the visual designer for visual treatment, we then send it to the front-end back-end developers to implement what is needed to be done. They then follow the visual design and get the assets from the designer, while also paying attention to the annotations for exactly what certain things do.

This is a little more complex than what I said, because there is also site maps, user flows, user testing, user research, and so on and so forth, but for your question I think this works.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.