I am a UI team lead.
I detected that the topic of "how do you want the graphics?" is a very hot topic in my company. And I find myself always giving the same explanation.
I would like to give like a "checklist" for the PMs and the designers we work with to make the work more efficient and fun.
Currently there's this constant ping-pong in emails between us and PMs. I would like to get rid of that..
Thought about the following list (several of the items I gathered so far..):
- The design should be web and mobile friendly. (yes - sometimes we get some crazy design that require us to use mostly images even with all the power of CSS today..)
- Flat design is good. - obviously a recommendation.
- Images should have transparent background.
- The original PSD file
- Each layer in PNG with transparent background.
- Icons and flat images should be in SVG, and if possible - as a font. (we usually convert to font ourselves).
- General guideline of the design should be attached.
- color palette and the purpose for each color: Title, subtitle, text, disabled items, actions items.. etc..
- important alignments guidelines - sometimes we miss the need for things to align whereas the designer feels they based the entire design on that. This usually affects the HTML structure as well - so it is very important to have common grounds on this ASAP.
- Error messages display (ALWAYS MISSING! no one designs the errors..)
And then a whole different section for emails :P
We usually develop web design, but non-web might be required too in the future.
Seems to me like someone probably already made such a list and I am reinventing the wheel.
What is the standard for passing the grail from the designer to the dev team?
This question is technical.
What is the standard way of getting deliveries from the designer?
or if you'd like - as a designer - what is my checklist for delivery?
I assume almost every HiTech company with GUI has this process, so it must have grown into a written standard I can simply send to my designers, and make sure they follow it.
Like a checklist the designers will check, and my team will validate to avoid back and forth correspondence like "we need this in png" , "can you also get jpg?" etc.. which consumes a lot of time, and is just not right as I want to allow the designers to move forward and forget this project.
Especially since the design step happens way before the implementation, and by the time we reach that phase, we start to discover we are missing some artifacts from the designer.
I expect people to publish their checklist, or reference me to a checklist they are using.
The first answer that hits the spot will be accepted. Opinions like "whether this checklist or that checklist is better" has no room here.
If there is no such standard checklist, I think there should be, and I also think this question has a great potential to start one right here.
The workflow is known, the motivation is very high, the communication between us and the designer is great. This part of the process is understood, but the content is always questioned, and I can't understand why.