Figma Dev Mode changed handoff expectations

Figma Dev Mode moved handoff from screenshot exchange toward inspection.

A ready frame is not only a finished visual. It should give another person enough context to build: states, responsive behavior, component sources, tokens, copy, loading, errors, and the choices that still need product or engineering judgment.

A useful frame can answer:

• what is final
• what is intentionally flexible
• what comes from the design system
• which state lives elsewhere
• what remains undecided

Inspection also raises the cost of messy files. A frame that works at one size may fail in a responsive layout. A manually nudged layer may imply the wrong implementation. A layer named Rectangle 182 may be harmless during exploration and unhelpful during handoff.

I would expect a ready frame to include:

clear frame name
known component source
token-backed values where possible
intentional names for important layers
notes for behavior not visible in pixels
links to ticket, prototype, or implementation notes

Dev Mode snippets are evidence, not instructions. A CSS fragment from one layer does not know the production component architecture. The useful mapping is between design concepts and code concepts: which Figma component maps to which production primitive, which variables belong to the token system, and which exception is intentional.

Compare changes help with quiet drift. The design changes after handoff, product edits the copy, or a new state appears. A short note keeps the team from reconstructing the sequence later:

handoff version: account-settings-ready-2023-07-06
changed after handoff:
  added disabled save state
  changed billing copy
  replaced custom toggle with design-system switch
implementation impact: update component and tests

Annotations should explain behavior that inspection cannot infer: title wrapping, required fields, confirmation, empty states, validation, breakpoints, permission states, and data-dependent layout.

Engineers still need to bring codebase constraints into the conversation. A production primitive may not support the exact variant. A table may need a different responsive strategy. Those divergences are fine when they are intentional and visible.

The better handoff is an inspectable artifact with enough structure, state, and provenance to build the right thing and notice when it changes.