Using Figma to go beyond Figma
summary
Shows a concrete Figma-driven infrastructure: library analytics plus an invisible pixel in components, Figma API scans that count real usage across ~3,000 component configs and 100+ styles, a discovery plugin that surfaces popular configs, a 30-day team competition to drive adoption, a review plugin with karaoke scoring built from composable logic blocks, programmatic generation of 256 map‑marker permutations, automated i18n testing, and a Matlab web prototype flow that consumes exported SVGs via the Figma REST API.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:01Myth #1: A design system is just a nice idea
- 5:10Myth #2: Our team is special, exempt from the rules
- 8:02Myth #3: We will come back to apply Design Systems later
- 16:20Myth #4: Design systems are tedious and unmaintainable
- 19:40Myth #5: Figma stops being useful after static UI design
- 23:22Closing
related talks
23mUsing Figma beyond and above in design teams
42mCode, Creativity, and Community at Figma
37mExtend what's possible with Figma Plugins
16mDesign Language on Autopilot: How Figma and Code Can Automate Your Workflow
18mMaking the Things That Help Others Do Their Thing
29mBuilding custom Figma plugins to unlock new capabilities
22mFigma Hacks and Workflow Enhancements with Plugins
17mDesign systems in an AI first ecosystem