Concepts in UI Design & Figma, page 6
Versioning a Design System with Semantic Versioning
Use Semantic Versioning (MAJOR.MINOR.PATCH) to signal the impact of design system changes. This tells teams if an update is a breaking change (MAJOR), a new feature (MINOR), or a bug fix (PATCH).
Drive Design System Adoption, Don't Just Build It
Treat your design system like an internal product, not a one-off project. To drive adoption, show quick, measurable wins and offer tiered onboarding for different roles.
Design System Docs: The Product, Not the Afterthought
Treat your design system documentation as a product, not a cleanup task. It's the instruction manual that prevents your component library from being misused. It's essential for scaling a design system to ensure consistency and speed up onboarding.
Figma Comments: Annotate Designs for Better Handoff
Figma comments are the inline documentation for your designs, bridging the gap between a static screen and its intended behavior. Use them to clarify interactions and edge cases directly on the canvas. The footgun is assuming the design speaks for itself.
Real-time Collaboration: Figma's 'Multiplayer' Model
Real-time collaboration uses a central server as the single source of truth for a file. Instead of passing copies, users connect to the same live document, enabling simultaneous editing in tools like Figma.
Figma Comments: Your Team's Built-in Critique Layer
Think of Figma comments as a critique layer on your design. They tie feedback directly to specific elements for asynchronous review, letting you iterate faster without constant meetings. The footgun: Over-mentioning creates notification fatigue.
Figma Pages: The Folders Inside Your Files
Think of Figma pages as folders within a single file. They let you organize complex projects by giving you separate canvases for different design stages, user flows, or component libraries. The main footgun: free plans limit you to only three pages per file.
Figma Permissions Cascade Downward
Figma permissions flow downward: team access opens every project and file inside it. Use share links for quick reviews, but direct invites gate specific files. Inviting someone to a team exposes every project, while a file invite keeps the rest hidden.
Figma Variables: Grouping Primitives with Collections
Think of Figma variables as raw ingredients. A collection is a recipe book ('Spacing') and modes are variations ('Mobile'). This lets you manage design tokens, themes, and responsive layouts.
Figma: Local vs. Published Library Assets
Local Figma assets are private drafts; published assets are the team's shared toolkit. Use this to manage a central design system, but remember: if you don't publish your changes, your team will be using outdated components and variables.
Figma Widgets: Live Apps on Your Canvas
Figma Widgets are like mini-apps living on your canvas that everyone interacts with at once, unlike single-user plugins. Use them for collaborative tools like live polls or data tables.
Realistic UI Motion with Easing Curves
Easing curves control animation acceleration to make UI motion feel natural, not robotic. Use 'Ease Out' for elements entering the screen and 'Ease In' for those leaving. The footgun is overusing one curve; this makes motion feel unnaturally perfect.
User Flow Diagrams: Mapping the Path to 'Done'
A user flow diagram maps the exact steps a user takes in your app to complete one task. It aligns teams on product goals and gives developers a visual guide, preventing confusion and rework. The footgun: it's not a customer journey, which is far broader.
Font Pairing Is Casting, Not Matchmaking
Font pairing is casting: one lead voice, one supporting role that contrasts without competing. A display headline face plus a neutral body sans guides the eye through a dashboard. Using two fonts with similar weights or x-heights creates noise, not hierarchy.
Alignment: Invisible Lines That Structure Interfaces
Alignment is invisible scaffolding: eyes travel along shared edges instead of hunting anchors. In Figma, left-aligning labels and inputs turns chaos into readable flow. Center-aligning long text is the footgun; ragged invisible edges increase reading friction.
Components: One Master, Many Instances
A component is a master spawning linked copies; edit it and all copies update instantly. Use them for buttons and cards that repeat so one edit flows everywhere. Detach instances or override everything and you kill reusability, forcing manual fixes.
Masking: Hide Pixels Without Deleting Them
A mask is a stencil that hides everything outside its shape without destroying the original image. Use it for circular avatars and rounded photo crops. The hidden portion still exists, so exporting without flattening may bloat the file with invisible pixels.
Component Properties: Levers Without Variants
Component properties are levers that let you swap text, toggle layers, or change icons without detaching. They shine in buttons with optional icons. The footgun is adding so many toggles that the panel becomes harder to use than a tidy variant grid.
Text Resizing in Figma Auto Layout
Text in Auto Layout does not wrap by default. A label set to Auto Width grows forever, while a parent set to Hug follows it. The footgun is leaving text on Auto Width inside a responsive card and expecting it to behave like a paragraph.
Boolean Component Properties in Figma
Boolean properties in Figma are light switches for layers inside a component. They let you toggle an icon or badge on and off without spawning extra variants. The catch is that hiding a layer can break auto-layout if that layer was anchoring spacing.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles