Schema by Figma 2022 New York City
who it's for
design system engineers, product designers, frontend engineers, design managers, design operations, mobile engineers, developer advocates
topics
component properties metadata; subcomponent layout patterns; headless design systems; visual regression testing; Figma branching workflows; Figma REST API usage; plugin analytics and auto-linting; Style Dictionary token codegen; native mobile component libraries; roadmapping with spreadsheets; HAFNA workshops (hopes fears not working); theming via presentation-structure separation
| title | author | length |
|---|---|---|
| NYC Opening Keynote - Conference Kickoff | Jacob Miller | 15m |
Design complexity grows along three concrete axes: layout, theming, and process. The talk claims variant explosion is solved by component properties and a… | ||
| Designing a community-driven design systems roadmap | Jules Forrest | 22m |
A design systems roadmap gets co-created with the internal community using Google Sheets spreadsheets built with data validation, conditional formatting… | ||
| Establishing early evangelists: from sentiment gathering to strategic roadmapping | Taylor Cashdan | 21m |
Starts from a concrete claim: run discipline-specific HAFNA: hopes fears working not working sessions (about 45-minute sessions, ~15 people each) using FigJam… | ||
| Creating DoorDash’s native mobile design system | Camden Asay, Matthew Burg, Will Hou, Ayanna Kosoko | 21m |
DoorDash’s Prism system claims a single native library powers three product surfaces and now contains 38 native mobile components after a multi‑year build that… | ||
| Evolving systems with data and heart | Bernadette Faller, Vincent van der Meulen, Hiroshi Mendoza | 19m |
A design system team describes concrete outcomes: they use the Figma REST API and plugin analytics to track component usage, ship an auto‑lint that is later… | ||
| Expanding your Design System's sphere of influence and other lessons | Lauren LoPrete | 21m |
Design systems sell culture change through measurable moves: a checklist + Figma playground for onboarding, regular office hours, a satisfaction survey, and… | ||
| Inside: Behind the scenes of component properties | Su Yang, Naomi Jung | 22m |
Component properties are actually implemented as metadata on instances that store component properties values so files avoid the variant explosion problem… | ||
| Architecting Subcomponents | Nathan Curtis | 22m |
Argues that instead of inflating a card component with endless props or forcing users to rebuild from scratch, break it into smaller parts so adopters can… | ||
| Speaker Panel Q&A | Patrycja Rozmus, Hiroshi Mendoza, Nathan Curtis, Lauren LoPrete | 35m |
Panelists report concrete practices and outcomes: tracking parity between Figma and code and component coverage percentages to prove impact, theming Postmates… | ||
| nothing matches | ||