Nathan Curtis
where else to find them
linkedin:nathancurtis
what they talk about
all 4 in the filters
where they keep going back
- Schema by Figma New York City2 editions2022–2025
all 6 in the filters
on a stage with
who talks about the same things
- Hiroshi Mendoza4 talks
- Patrycja Rozmus4 talks
- Lauren LoPrete5 talks
- Luis Ouriach3 talks
- Jacob Miller7 talks
- Noah Levin8 talks
| title | conference | date |
|---|---|---|
| Introducing Slots (new feature) | Schema by Figma 2025 | 2025-10-28 |
Slots replace pseudo-slot utilities with real editable areas so designers can duplicate, reorder, and add items directly — checkbox groups shed hidden layers… | ||
| Managing Design Systems, from Features to Roadmaps | SmashingConf Antwerp 2024 | 2024-10-29 |
Shows a repeatable workflow: plan → design → spec → code → publish, with tasks tracked per-component and slotted into releases (examples use a monthly release… | ||
| Managing Design Systems with | SmashingConf New York 2024 | 2024-10-07 |
Practical workflow for running a design system: organize work as columns of tasks and rows of features, define a directly responsible individual, and use… | ||
| Speaker Panel Q&A | Schema by Figma London 2022 | 2022-11-09 |
Panelists name concrete practices and tradeoffs: Uber shows a push toward coverage percentage and parity between Figma and code with base tracking, the… | ||
| Speaker Panel Q&A | Schema by Figma Tokyo 2022 | 2022-11-02 |
Specifics about what works and what still needs work emerge: teams track coverage percentage of screens and use theming to onboard acquisitions, napkin ROI… | ||
| Architecting Subcomponents | Schema by Figma 2022 New York City | 2022-10-26 |
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 | Schema by Figma 2022 New York City | 2022-10-26 |
Panelists report concrete practices and outcomes: tracking parity between Figma and code and component coverage percentages to prove impact, theming Postmates… | ||
| Components: Big, Small, or Do 'em All? | SmashingConf Freiburg 2022 | 2022-09-05 |
Design systems need rules: build only what a majority uses, or enable teams to compose. Large systems vary — Carbon has 39 components, Salesforce 85; Atlassian… | ||
| nothing matches | ||