mercredi 3 décembre 2014

How to transfer information to the development team?


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.

  • Formats:

    • 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 none 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?





Aucun commentaire:

Enregistrer un commentaire