Design-to-development handover
A complete handover with specs, tokens and assets lets developers build the design without guesswork.
Background
Without a proper handover, details slip between design file and finished page, especially when design and code sit with different teams. Spacing is off, states go missing or images come in the wrong size.
What the handover includes
Measurements: spacing, sizes and type, readable in Figma's Dev Mode.
Design tokens: colours, fonts and spacing as variables for the code.
States: hover, focus, error, loading and empty states for each component.
Assets: icons as SVG and images in the formats and sizes required.
Accessibility: notes on reading order, labels and roles.
Approach
Our developers check designs for feasibility before they are signed off. We hand over one component at a time, and decisions go straight into Figma. Components keep their Figma names in code.
Designs from external teams
We also build designs from other agencies or your in-house team. We first review the files and flag any gaps.
Outcome
You get fewer corrections, reliable schedules and a build that matches the approved design.