Preparing design assets ensures smooth handover of design for development.
Duration
Complexity
Contributors
UX designer, UI designer, Design manager, Product manager
At the end of the design process, the design team needs to hand over the design to the development team. If done right, this enables development work to start on the right note. This is an important step in order for the design to get developed as expected.
Preparation for design assets handover should:
ensure all the required material is available
be easy to find
be organized
be present in required formats
The following items are required for starting with Development, hence need to be prepared for the handoff
Detailed Key UIs: Important unique UIs in the design are illustrated in detail and annotated if required
Navigation Schema: Definition of primary and secondary navigation
Prototype: An interactive prototype of the functionality in scope
Styleguide: Including the definition of colors as
HEX codes
Fonts variations as used for each UI element
Icons in required formats such as SVGs, PNGs, GIFs, JPGs, etc
Earlier designers used to create specifications for the design once finalized. Now automated handover tools are available. This has simplified the handover process. Specifications are not required to be created manually anymore. Designers can grab all the specifics from the source design file itself and share it for development.
Organize your files: Make sure all your design assets are properly labeled and organized in folders. Use clear naming conventions that are easy for developers to understand.
Determine the file formats: Consult with your development team to determine the file formats they need. Common formats include PSD, AI, Sketch, and XD.
Export assets: Export all necessary assets in the required file formats. This includes images, icons, logos, and any other design elements needed for the development process.
Provide documentation: Provide detailed documentation that explains how the assets should be used. This includes guidelines for typography, colors, and spacing.
Share: Share the design assets and documentation with the development team. Make sure they have access to all the files they need to start the development.
Collaborate: Work closely with the development team to ensure that the design assets are being implemented correctly. Provide feedback and make any necessary revisions as the development process progresses.
Handing over a design for development has 2 parts to it.
Preparing the material for handover that includes the final design, specifications, style guide, etc. depending on the project requirement.
Knowledge transfer regarding design, which is usually done through a live interaction between designers and developers like a Handover workshop
Apart from a well-done handover, good rapport between designers and developers is essential for building good products. A lot of communication and collaboration is required between designers and developers in order to develop the product as per the design and refine it to further fit it to the users’ needs.
Here are a few guidelines to help have a good rapport between designers and developers:
Encourage communication
Understand and appreciate respective roles
Set clear expectations
Raise a flag as soon as any issue is identified
Share constructive feedback
Focus on making things happen together rather than pointing out mistakes
Don't take feedback personally
Build design systems together rather than creating individual UIs
Use tools in the design & development process as much as possible
Respect a different point of view
Do’s |
Don’ts |
|
|
Zeppelin
MarvelApp
Avocode
Sympli
Mockplus
Figma
GoogleDocs
A Guide to Successful Design Handoff Document from MarvelApp Blog
Developer Handoff from DesignCode
How to Ensure a Smooth Design Handoff from IxDF
How to Handoff UI Designs to Developers (Figma vs Zeplin) from Mizko
Design Handoff from Checklist
2022 Guide to Smooth Design Handoffs – Checklist and Tools from UserGuiding
The Relationship Between Designers and Developers from UX Magazine