Industries / Finance and business services / Advertising and marketing / Graphic and web design
Handover to developers and printers
Handover is the step where a finished design leaves the designer as files, measurements, named values and packed folders that a developer can build from, or a printer can print from, without guessing.
7
Milestones achieved, from 1993 to 2025.
2
To watch for: announced, not yet confirmed outside.
2
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
1993
One folder for the printer
A Quark press release of September 1992 said QuarkXPress 3.2, a page-layout program, would add "Save for Service Bureau," a command that copies a document and all its pictures into one folder, with a data file describing it, for the service bureau, the shop that turned files into film for printing. The Centre for Computing History dates version 3.2 to 1993. QuarkXPress now does the same job with Collect for Output and Adobe InDesign with Package, and print shops such as Ohio University's Printing Services ask designers to send packaged files.
LessonOhio's printers warn that InDesign "may not collect every font used in placed graphics" made in Illustrator or FreeHand, so a package is only as complete as the software's view into files placed inside other files.
discmaster.textfiles.comcomputinghistory.org.ukquark.comohio.edu
Credit
Quark, Inc
2014
Design decisions become data
Salesforce's design team stored its colors, font sizes, spacing and corner shapes as named values in JSON files (a plain-text data format) and called them design tokens. It built Theo, an open-source tool that turns those files into style variables for websites, XML for Android apps and JSON for iOS apps, so a design change made once reaches every platform's code. Martin Fowler's site, an outside source on software design, says "Salesforce originally introduced design tokens."
Credit
Salesforce UX; the September 2014 post is by Sönke Rohde, and a later history credits Jina Anne with the idea
2015
Specs generated, not drawn
Developers used to get exported images and a spec sheet marked up by hand with measurements, called redlines; Zeplin's co-founder Pelin Kenez described it as "some PNGs and... this PDF file with all these annotations." Zeplin, begun in Istanbul in June 2014, launched version 1.0 in July 2015; it reads the design and gives developers its sizes, distances, fonts, color codes and icons. TechCrunch reported in November 2015 that Zeplin said it had 85,000 users, 1,800 of them paying, including Slack and Pinterest.
Credit
Pelin Kenez, Berk Çebi, Ismail Ceylan and Merih Akar (Zeplin)
2017
Animations handed over as files
Airbnb released Lottie, a library for iOS, Android and React Native apps that plays animations made in Adobe After Effects, an animation program, from JSON files exported by the open-source Bodymovin plug-in. Engineers no longer had to rebuild a designer's motion by hand from a GIF; Airbnb wrote that they "can use exactly what the designer intended." GitHub showed about 35,800 stars, its bookmark count, on the Android library in November 2026.
Credit
Brandon Withrow, Gabriel Peal, Leland Richardson and Salih Abdul-Karim (Airbnb), building on Hernan Torrisi's Bodymovin
2023
A developer view inside Figma
On 21 June 2023 Figma, a design tool that runs in the web browser, launched Dev Mode in beta: a view of the design file for developers that shows measurements, specs, code and assets. Designers can mark a section "ready for development," developers can compare versions of a frame, and an extension brings it into the VS Code editor. The trade site DevClass reported that from 2024 it would need a paid license.
Credit
Figma (its chief technology officer, Kris Rasmussen)
2024
Adobe stops building XD
Adobe XD, Adobe's tool for designing and prototyping app and web screens, went into maintenance mode, with bug and security fixes only, in May 2023, The Register reported. Adobe and Figma ended their planned merger on 18 December 2023, citing "no clear path" to approval from the European Commission and the UK's competition regulator, and in January 2024 Adobe said XD was no longer sold on its own to new customers and that it had "no plans to further invest" in it.
LessonIt was Adobe's second freeze of a screen-design tool in about ten years, after it stopped new features for Fireworks in May 2013; designs and specs kept only in one company's file format depend on that company's plans.
Credit
Adobe
2025
A shared format for tokens
On 28 October 2025 the Design Tokens Community Group, a volunteer group hosted by the W3C, published the first stable version (2025.10) of its Design Tokens Specification, a JSON file format for passing tokens between design tools and code. Figma said the same day that it would ship import and export of its variables following the format in November, and its user forum showed the rollout still under way in December 2025. The specification says it "is not a W3C Standard."
Credit
Design Tokens Community Group, with more than 20 editors and authors
Watch for
Code Connect trims agent work
Figma's MCP server, launched in beta in June 2025, is a connector that lets AI coding agents read a Figma file, and Code Connect maps each Figma component to the team's real code component. Figma ran 27 design-to-code tasks on two React design systems that Figma itself built, with and without Code Connect, using Claude Sonnet 4.5 and Claude Opus 4.7. With it, the median task took 19.6% less time, the AI model processed 29.5% less text, and code quality rose from 2 to 3 on a 1 to 4 scale, as judged by AI models.
Achieved whena team outside Figma repeats the comparison on a design system Figma did not build, publishes the tasks, and has people score the code without knowing which setup made it.
Claimed by
Figma (Tom Weightman), August 2026
Agents draw in design files
Figma says work can now flow from code back into the design file. Since February 2026 Claude Code can capture a working web page and turn it into editable Figma frames, and since March 2026 agents such as Claude Code and Codex can create and change designs through the MCP server's use_figma tool, making "design assets that are linked to your design system." Writing to files is in beta, free for now and due to become a paid feature charged by use.
Achieved whenthe feature leaves beta and an outside test reports what share of agent-made layers use the file's own library components and variables rather than loose copies.
Claimed by
Figma (Gui Seiz and Alex Kern; Matt Colyer), February and March 2026
Open
01
Design-to-code that keeps tokens
An open benchmark of screens drawn with open design systems that publish both a Figma library and a code library, such as Figma's Simple Design System (MIT license), IBM's Carbon (Apache 2.0) and GitHub's Primer React (MIT). Each screen gets reference code written by hand with the library. Each design-to-code tool is scored on the share of color, spacing and type values written as the system's token names rather than raw numbers; the share of components built with the matching library component rather than rebuilt from scratch; and how closely the result matches the design at three screen widths.
The briefCredit · unclaimed02
Scorecard for token file exchange
One reference token file in the 2025.10 format covering every token type, aliases (tokens that point to other tokens), and light and dark modes. Import it into each tool that claims support, export it again, check each export against the official 2025.10 schemas and compare it with the original. Publish a table of which token types survive, change or drop, per tool and version.
The briefCredit · unclaimed
Open 01 · the brief
Design-to-code that keeps tokens
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
An open benchmark of screens drawn with open design systems that publish both a Figma library and a code library, such as Figma's Simple Design System (MIT license), IBM's Carbon (Apache 2.0) and GitHub's Primer React (MIT). Each screen gets reference code written by hand with the library. Each design-to-code tool is scored on the share of color, spacing and type values written as the system's token names rather than raw numbers; the share of components built with the matching library component rather than rebuilt from scratch; and how closely the result matches the design at three screen widths.
Why it is still open
Benchmarks built from Figma files score looks, layout and resizing, not use of the file's own tokens. FigmaBench, with 1,234 Figma Community samples, scores visual, layout, text-and-style and responsive quality. Figma2Code (ICLR 2026) checks only a stand-in for token use: how often the code writes raw values instead of named classes. TaoD2C-Bench (October 2026) checks components against a target library but has no token check, uses company-owned designs released for non-commercial research only, and its authors note that visual scoring cannot verify "whether the code uses the intended components." Figma's 27-task Code Connect test is internal.
Built with what exists
the three open libraries and their Figma Community files; Figma's MCP server tools for design context and variables (Figma's REST API reads variables only on its Enterprise plan); Playwright to render each result at fixed widths; DINOv2 image embeddings to measure visual match, as TaoD2C does; a CSS and JSX parser to count token references; entrants such as Claude Fable 5.2 (see the Note "Three working devices") and an open-weights model such as Mistral Large 4 (see the Note "A trillion open parameters").
First step
Duplicate the Simple Design System Community file, pick 10 screens, write their reference code against its MIT-licensed React repository, and write the token counter.
Done looks like
At least 60 screens across 3 systems, with every reference solution scoring 100% on the token and component checks; a public leaderboard of at least 5 tools or models; a second person rerunning the tests gets scores within 2 percentage points.
Open 02 · the brief
Scorecard for token file exchange
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
One reference token file in the 2025.10 format covering every token type, aliases (tokens that point to other tokens), and light and dark modes. Import it into each tool that claims support, export it again, check each export against the official 2025.10 schemas and compare it with the original. Publish a table of which token types survive, change or drop, per tool and version.
Why it is still open
The group's official test suite, added in September 2026 with 93 valid and 127 invalid files, checks whether a file is valid, not whether a tool keeps tokens intact, and its list of supporting tools is filled in by the tools' makers. A Penpot user found in May 2026 that Penpot exports the older Tokens Studio format, not 2025.10, and built "a shim library requiring 9 distinct transforms" to convert one export. The documentation of Style Dictionary, a widely used token converter, says 2025.10 "does not have full support yet."
Built with what exists
the group's JSON schemas and test suite; Ajv, the validator the suite itself uses; Figma's variable import and export; Penpot; Tokens Studio; the Style Dictionary and Terrazzo command-line tools; a script that compares two JSON files.
First step
Write the reference file and run it through Style Dictionary, Terrazzo and Penpot, which are all free.
Done looks like
At least 6 tools tested on the 13 token types the suite lists, each cell marked kept, changed or dropped and linked to the exported file, with tool versions and dates recorded and one script that rebuilds the whole table.