If you need the code for the design, what format do you require? and how

Working closely with designers is one of the most rewarding parts of software engineering, but it can also be a source of constant friction. Have you ever received a design file and wondered: Is this meant to be a static spec, a tokenized design system, or production-ready component code?

When we talk about bridging the gap between design and development, the question always comes down to handover formats. If you need the code for a design, what format do you actually require, and how do you get the best results?

Top comments (0)

Subscribe

Code of Conduct • Report abuse

For further actions, you may consider blocking this person and/or reporting abuse