Design Systems | Techlist.io

figmaOct 29, 20173 min readCurated summary

How Inneract Project empowers brown and black designers | Figma Blog

The article highlights ten UI/UX design internships recommended by Figma users, arguing that the best programs offer meaningful design work, mentorship, user research, and opportunities to learn—not merely perks or high compensation. Across companies ranging from Shopify and Facebook to Hotels.ng and Palantir, interns are given varying degrees of responsibility, collaboration, and professional guidance. The strongest internships help students build practical skills and often lead to full-time employment. ## What Makes an Internship Valuable? - Respondents valued opportunities to practice design, conduct real user testing, and learn from experienced professionals. - Mentorship was a recurring theme: - Shopify assigns every intern a staff mentor. - Spotify provides interns with a designated mentor or manager. - Perks such as catered meals, generous stipends, travel credits, and office amenities were appreciated but considered secondary to meaningful work and learning. ## Shopify - Places interns on cross-functional teams to develop communication and collaboration skills. - Design interns work on deployable products, including Timeline. - Approximately 80% of interns reportedly return to Shopify or become full-time employees. - Strong emphasis on individual mentorship. ## Hotels.ng - Offers a remote, paid UI/UX internship for Nigerian residents through a partnership with the Akwa Ibom State government. - Interns must complete assigned tasks successfully to remain in the program. - The program lasts three months. - Many graduates receive full-time offers from Hotels.ng or other local companies. ## Facebook - Provides a reported average stipend of about $5,600 per month. - Interns receive substantial responsibility and are treated similarly to full-time employees. - The work environment is described as resembling an intensive “college campus.” ## Spotify - Runs a ten-week program organized into close-knit squads and two-week sprints. - Interns are treated as “band members,” reinforcing the company’s collaborative culture. - The product design program is highly design-focused, with strong expectations for visual craft. - Mentorship and free food are notable parts of the experience. ## Salesforce - Its Futureforce program gives interns meaningful projects and opportunities to learn design systems. - Interns participate in social events with executives and receive up to seven days of Volunteer Time Off. - The program combines professional development with networking and community activities. ## Uber - Offers health benefits, unlimited vacation, and Uber credits. - Interns work in an intense but rewarding environment. - Product design interns may have direct access to senior leaders, whose willingness to listen can give interns significant influence. ## IBM - Austin’s Maelstrom program guides roughly 15 young designers through four tracks: - Design research - Visual design - UX design - Front-end development - Program leaders attribute its success partly to an emphasis on emotional intelligence. ## Airbnb - Known for a strong design culture, influenced in part by its designer co-founders. - Offers a close-knit, progressive, and innovative work environment. - Interns receive travel credits and access to extensive employee perks. - The company was ranked highly as a workplace in 2016. ## Square - Gives interns flexibility to explore different types of design problems as their interests develop. - Recognized for efforts to address gender inequality in technology. - Interns may work beyond conventional UI design, with opportunities to approach problems creatively and artistically. ## Palantir - Product design interns focus on solving complex problems rather than making minor visual adjustments. - The company’s open-source Blueprint style guide reduces repetitive interface work. - The program emphasizes product thinking and meaningful design challenges. ## Practical Takeaway When evaluating internships, prioritize mentorship, real product responsibility, cross-functional collaboration, and opportunities to learn from feedback. Compensation and perks are useful, but a program that develops practical design skills and provides a path to future employment is likely to have the greatest long-term value.

Read original

Design Systems Figma User Experience User Testing+3

figmaSep 28, 20172 min readCurated summary

This Twitter storm shows design systems are still up for debate | Figma Blog

Design systems were still an evolving, contested idea in 2017, without a universally accepted definition. The article examines a Twitter debate sparked by Airbnb’s Karri Saarinen, whose work framed design systems as essential for maintaining consistency and constraints at scale. The discussion suggests that a design system is broader than a library of UI components: it combines shared principles and patterns that shape a product’s overall design. ## An Evolving Definition - Designers offered varied interpretations of what a design system meant, reflecting the concept’s still-nebulous status. - Saarinen defined one as a “set of shared and integrated principles and patterns that define the overall design of a product.” - The debate demonstrated how the design community was actively refining the concept through public discussion. ## Why Design Systems Matter at Scale - Saarinen argued that larger, long-term projects require design systems to succeed. - Systems provide constraints and consistency across products, platforms, and teams. - Airbnb’s approach included principles such as: - Unified - Universal - Iconic - Conversational - Airbnb documented its process publicly as it developed its Design Language System. ## The Twitter Debate - Saarinen’s definition prompted a lively exchange with other design leaders, including Facebook product designer Sean Blanton. - The conversation explored what belongs within a design system and how broadly the term should be applied. - The article presents the discussion as valuable because experienced designers were clarifying the concept in real time. A practical takeaway is to treat a design system as an integrated foundation of principles, patterns, and constraints—not merely a collection of reusable visual components. Its purpose is to help teams create coherent products consistently as they grow.

Read original

Design Systems Product Design User Interface Design Patterns+4

figmaSep 18, 20172 min readCurated summary

Team Library 1.0 | Figma Blog

Figma’s Team Library 1.0 turns shared components into a centralized foundation for collaborative design systems. Building on feedback from its February beta, the release improves component discovery, documentation, and organization. Figma argues that its centralized, online platform can keep teams synchronized without third-party tools or custom internal systems. ## A Centralized Source of Truth - Teams can share buttons, icons, dialogs, and other components across files and with all team members. - Published components and updates appear immediately in the Team Library. - Users receive notifications when shared components change and can choose whether to apply updates to their local instances. - Centralized storage eliminates manual exporting, syncing, and reliance on tools such as Slack, Google Docs, or custom company software. ## Improved Component Browsing - The beta required repeatedly opening a pop-up that obscured the canvas. - Team components are now available in a dedicated tab in the left sidebar, alongside layers. - Designers can drag components directly from the sidebar into their designs. - A separate local-components tab provides an overview of what will be published. - The sidebar tabs can be switched quickly with `Alt+1`. ## Built-In Component Documentation - The beta provided no place to explain how or when components should be used. - Team Library 1.0 adds documentation fields in the right-hand properties panel. - Teammates can read this guidance while browsing components, keeping usage information attached to the component itself. ## Better Categorization and Organization - The beta organized components only by file, which made larger libraries difficult to navigate. - Components can now also be grouped by frame and group. - For example, button components placed in a group named “Buttons” appear together under that category. - Shared component thumbnails can be visually customized by changing the background color of their containing frame. Figma presents Team Library 1.0 as a practical foundation for building and maintaining living design systems. Teams can adopt shared components with less friction, while documentation and categorization make those systems easier to understand and scale.

Read original

Design Systems Figma Collaborative Design Component Library+1

figmaJun 19, 20172 min readCurated summary

Combine is taking on the design venture capitalist world | Figma Blog

Combine is a new seed-stage venture firm founded by former Facebook and Airbnb design leaders Soleio Cuervo and Adam Michela. Rather than relying on publicity, it plans to build an elite, design-focused portfolio and provide hands-on support through an in-house team of design partners. The firm’s model combines early investment with design-studio services, reflecting the growing importance of user experience in competitive software markets. ## A Quiet Venture Launch - Combine launched with little publicity, sharing only cryptic images of its warehouse office and no formal Medium announcement. - Despite its low profile, Silicon Valley insiders were watching closely. - The founders’ understated approach reflects their belief that reputation should come from past work rather than promotional claims. ## Founders with Deep Design Experience - Soleio Cuervo was Facebook’s second design hire. - He helped shape the company’s early design culture. - He led work on Facebook Messenger, Groups, and the original Like button. - Adam Michela joined Facebook after Cuervo’s departure. - He created Facebook’s first design system. - He later built a design system at Airbnb. - Their contrasting personalities complement each other: - Cuervo is an expressive, relationship-oriented connector. - Michela is a quieter, methodical operator. - Both share a strong interest in design and people, along with a reluctance to self-promote. ## A Venture Firm Built Around Design - Combine had raised more than $12 million for its first fund. - The firm planned to maintain a small, selective portfolio. - It intended to hire a team of highly experienced design partners. - These partners would work directly with portfolio companies on: - Branding and marketing - User research - Product design - Recruiting and team-building - The model resembles Andreessen Horowitz’s service-oriented venture approach, but with an unusually strong focus on design. ## The Growing Importance of Design - Combine was launching as startups increasingly compete through user experience. - Cloud infrastructure has made software cheaper and easier to build, giving consumers more alternatives. - As functional differences narrow, thoughtful design can become a company’s strongest competitive advantage. - Users increasingly blame a product—not themselves—when they cannot understand how to use it, making usability central to business success. Combine’s approach represents a shift from venture capital as primarily financial support toward venture capital as an active operating partnership. Its success would depend on whether elite design expertise can meaningfully improve early-stage companies and establish a repeatable model for design-driven investing.

Read original

Design Systems Figma User Experience Product Design+1

figmaJun 4, 20172 min readCurated summary

How one designer escaped the export-upload abyss | Figma Blog

The post argues that traditional designer-developer handoff creates unnecessary work, outdated files, and communication problems. At Pivotal, designer Colby Sato replaced repeated image exports and uploads with Figma’s browser-based, collaborative workflow. This saved roughly two days per project and made design critiques more focused and efficient. ## The Export-and-Upload Problem - Colby exported design frames as images and uploaded them to Pivotal Tracker engineering cards. - He repeated this process 15–20 times per project as designs evolved. - Searching through hundreds of engineering cards was time-consuming. - Missed updates sometimes caused engineers to implement outdated designs. - The process wasted developer time and made collaboration frustrating. ## Figma as a Shared Source of Truth - Figma files were accessible in the browser, always current, and shareable through links. - Colby could add a Figma link when creating an engineering card instead of updating images repeatedly. - Comments attached directly to design frames provided functional context. - The workflow eliminated uncertainty about which design version engineers should use. - Colby estimated it saved him two days of work per project. ## More Effective Design Reviews - Pivotal’s weekly critiques had previously relied on post-it notes and verbal explanations. - Figma comments stayed attached to the relevant design, making feedback easier to understand. - Colby could observe where engineers were focusing in the file through their cursor activity. - He could redirect reviewers toward areas where feedback was most valuable. - Reviews became faster, more contextual, and more collaborative. Figma ultimately shifted Pivotal’s focus from tracking files and feedback to improving the product itself. The post recommends using a shared, continuously updated design workspace to reduce handoff friction and enable stronger collaboration between designers and engineers.

Read original

Design Systems Figma User Interface Design Collaboration+2

figmaMay 19, 20173 min readCurated summary

Reflecting on Figma’s First Year | Figma Blog

Figma’s first year focused on proving that a browser-based design tool could deliver both powerful graphics performance and trustworthy collaboration. The company moved from being dismissed as a “toy” to becoming a serious platform through rapid feature releases, performance improvements, and better support for existing Sketch workflows. Its central insight was that multiplayer editing creates not only collaboration, but also a shared source of truth for entire product teams. ## Building a Browser-Based Design Platform - Figma faced major technical challenges in rendering complex graphics smoothly in a browser. - It also had to persuade designers that a web-based tool could be reliable enough for professional work. - The team spent its first year speaking with designers, engineers, and product managers to understand the needs of growing organizations. - Figma invested heavily in: - Faster file loading and rendering - Workflow improvements and polish - Continued refinement of Sketch import - Because releases came so quickly, the company collected its major updates in one anniversary retrospective. ## Collaborative Design and Multiplayer Editing - Public multiplayer editing launched on September 28, 2016, making Figma the first design tool to offer simultaneous editing. - Designers initially reacted both enthusiastically and skeptically to the idea of “pair design.” - After a year, teams were using multiplayer editing to: - Ship products under tight deadlines - Mentor designers remotely - Conduct more efficient design critiques - The larger benefit was a single source of truth: - Files could be shared through a persistent URL. - Updates appeared at the same location without requiring teams to synchronize assets manually. - Teams avoided overwritten files and outdated versions. - Different roles could work directly with the design: - Copywriters could test messaging. - Developers could inspect design attributes for implementation. - Product managers could monitor progress without relying on Slack updates. ## Components and Design Systems - As design became more central to product development, companies needed systems for maintaining consistent UI elements across teams and files. - Figma introduced components on December 8, 2016, allowing designers to synchronize reusable elements such as navigation menus and status bars. - Component overrides let designers customize individual instances—for example, changing color or typography—without disconnecting them from the underlying component. - This balanced flexibility with consistency, allowing teams to benefit from a broader design system while still adapting individual designs. Figma’s first-year progress suggests that browser-based design succeeds when performance, compatibility, and collaboration are treated as equally important. Its persistent shared files and emerging design-system features aimed to make the design process more connected across the entire product team.

Read original

Design Systems Figma Collaborative Design Multiplayer Editing+2

figmaApr 26, 20172 min readCurated summary

5 books that shaped the design approach of Airbnb’s Jon Gold | Figma Blog

Jem Gold’s design approach combines systems thinking, human-centered technology, disciplined focus, mindfulness, and functional programming. The five books she recommends show how design can be treated as a generative process—one that connects creative practice with engineering and tools that augment human ability. ## Designing Programmes: Design as a System - Karl Gerstner’s *Designing Programmes* presents design as a process that generates assets rather than relying on humans to create every final output manually. - Though focused on layouts, logos, and typography, its ideas remain relevant to modern UI and design systems. - Gold values the concept of a flexible pipeline that people can shape, with the system producing consistent results. ## 10% Happier: Creating Space for Better Decisions - Dan Harris’s memoir about meditation influenced Gold’s design process and outlook. - Meditation helps her avoid immediate, visceral reactions and take time to investigate the best response. - She especially appreciates Harris’s skepticism toward mystical or “woo-woo” claims, making the book a practical introduction to meditation. ## The Dream Machine: Computers as Creative Partners - *The Dream Machine* explores J. C. R. Licklider’s vision of “man-computer symbiosis,” in which computers enhance human intelligence. - It describes researchers who rejected IBM’s slow, punch-card-based model of computing in favor of interactive systems people could enjoy using. - Gold identifies with their rebellious belief that technology should augment human creativity rather than merely automate routine tasks. ## Deep Work: Protecting Creative Focus - Cal Newport’s *Deep Work* argues that social media fragments attention and prevents sustained, original thinking. - Gold responded by eliminating social media for a month and scheduling dedicated blocks for creative projects. - When she felt the urge to check distractions, she replaced the habit with activities such as running or reading. - The practice helped her preserve focus and create space for ideas to develop. ## Functional Programming: Building from Small Primitives - *Professor Frisby’s Mostly Adequate Guide to Functional Programming* introduces functional programming through a short, approachable, free online book. - The paradigm breaks problems into small, composable units that can be rearranged and combined. - Gold applies this principle to design systems: instead of starting with a large page and breaking it down, designers can begin with basic primitives and build upward. - This approach connects programming concepts directly to scalable, reusable design work. Together, these books recommend a design practice built from composable systems, deliberate attention, skepticism, and technology that expands human creativity.

Read original

Design Systems AI React Typography+2

figmaMar 29, 20172 min readCurated summary

Figma’s new icon | Figma Blog

Figma’s 2017 icon redesign reflects the company’s growth and broader design philosophy. Rather than treating the icon as a standalone mark, Figma built it around three ideas: fundamental design elements, playful experimentation, and modular systems. The result is a bright, flexible icon made from simple shapes that represents both Figma’s product and its approach to design. ## Celebrating the Fundamentals of Design - All designs can be reduced to basic elements such as points, lines, and shapes. - Figma’s own tools follow this principle: a relatively small set of carefully integrated functions can produce complex results. - The icon celebrates these foundational building blocks, echoing traditions associated with Bauhaus and other design movements. - Its simple forms represent Figma’s goal of empowering designers to create sophisticated work from elemental components. ## Encouraging Play - The icon’s bright colors and block-like shapes were inspired by children’s building blocks. - Figma views experimentation and play as important ways to discover new solutions. - An open, playful design process can produce more creative and unexpected outcomes. - The icon is intended to communicate the same openness and enjoyment that Figma hopes to enable in its users’ workflows. ## Design as a System - Digital products must work across many screen sizes, devices, operating systems, and connection conditions. - Modular systems and reusable components are therefore more effective than one-off designs. - Figma favors rules-based, vector design because it can adapt to different environments more reliably than fixed pixels. - The new icon is constructed from three simple shapes arranged on a modular grid, reinforcing the idea of flexible, reusable design components. - This concept connects to Figma features such as team libraries, which help designers build and maintain systems. The new icon extends Figma’s identity while expressing its core beliefs: strong design starts with fundamentals, creativity benefits from play, and digital work is most powerful when built as an adaptable system.

Read original

Design Systems Figma Responsive Design Vector Design+2

figmaFeb 14, 20173 min readCurated summary

Team Libraries in Figma | Figma Blog

Team Libraries bring shared, synchronized components to Figma, addressing the difficulty of maintaining design systems across separate files. The feature builds on Figma’s components, constraints, and web-based collaboration to create a single source of truth that teams can reuse and update efficiently. Its workflow—Publish, Insert, and Update—combines engineering-style structure with an accessible design workflow. ## The Problems with Traditional Design Tools - Many design tools were modeled on print and illustration software rather than interactive applications. - They lack meaningful support for application behavior, platform constraints, and reusable interface structures. - Copying symbols between files creates disconnected versions that must be updated manually. - Large organizations such as Facebook, Google, and Airbnb have had to build custom tools and dedicate staff to maintaining design systems. - Designers need synchronized, compounding component structures to create scalable systems. ## Bridging Design and Dynamic Interfaces - Figma’s earlier features established the foundation for reusable design systems: - Reliable vector editing - Constraints that reflect system behavior - Dynamic, reusable components - Team Libraries extend these capabilities across files and team members. - Because Figma operates online, shared components have effectively no synchronization delay. - Teams can reuse structured components across devices, platforms, layouts, and user flows. ## An Engineering-Inspired Design Workflow - Figma draws on software concepts such as modular composition and frameworks like React. - Structuring interfaces from discrete, clearly defined parts makes products easier to maintain. - The feature adapts engineering principles for designers rather than copying programming workflows directly. ## Publishing Components - Designers select components and choose **Add to Library** in the inspector sidebar. - Multiple components can be collected and reviewed before being published. - Permissions separate the source of truth from its consumers: - Editors of the source file can modify the original components. - Anyone with view access can use the published components. - This lets specialized teams control assets such as icons, colors, or brand guidelines while others reuse them without changing the rules. ## Inserting and Nesting Components - Published components are available in any file for users who can view the source file. - Users insert them through Figma’s components tool. - Components can be nested inside larger components or modules. - Nested structures allow teams to build complex views from reusable source elements while preserving a predictable single source of truth. ## Updating Shared Components - Changes are made to the original component and published again. - Figma provides a confirmation step and a visual diff showing what changed. - Deleting a component from the source file and publishing removes it from the team library. - The update process includes an additional safeguard because changes may affect multiple design explorations and could otherwise cause users to lose work.

Read original

Design Systems Figma User Interface React+3

figmaDec 7, 20163 min readCurated summary

Components in Figma | Figma Blog

Figma’s 2016 Components release applies software-engineering ideas such as composition, inheritance, and overrides to interface design. Components let designers reuse shared elements as linked instances, so updates remain consistent while local customizations are preserved. The result is a design workflow that supports both systematic reuse and creative flexibility. ## Designing with Components - Components help designers break complex interfaces into smaller, understandable parts. - Reusable elements can appear in multiple locations, at different sizes and with local modifications. - Unlike duplicated copies, component instances remain connected to their source. - Updates to the original component are automatically reflected across all instances, improving consistency and reducing repetitive work. - Examples include repeated address-book rows containing shared typography, spacing, icons, and graphics. ## Figma’s Design Goals Figma aimed to make Components: - Easy for new users to learn. - Powerful enough for advanced design systems. - Flexible throughout the design process. - Low-overhead, so systematic design improves speed without limiting experimentation. ## Creating and Using Instances - Any frame or selected object can be converted into a component through the toolbar. - Duplicating, copying, pasting, or Alt-dragging a component creates instances rather than independent copies. - Instances can move independently on the canvas while retaining their connection to the source component. - Changes made to the main component propagate immediately to its instances. - Certain internal properties, such as the position and size of nested objects, are restricted to make components easier to maintain. ## Style and Property Overrides - Instance changes are treated as overrides of the original component’s properties. - Designers can override fills, strokes, colors, widths, and properties of nested layers. - Overrides remain intact when the source component changes. - Properties that were not overridden continue to update from the source component. - Overrides can be removed with the “Reset Instance” action. ## Complex and Nested Components - Components can contain instances of other components. - Combining nested components makes it possible to build larger systems from smaller, reusable parts. - Designers can add instances to an existing component or create a new component from selected instances. - Nested components are intended to work like other Figma objects, keeping complex systems manageable. ## Constraints - Components can be combined with Figma’s Constraints feature. - Constraints allow elements to respond to changes in size and position. - Together, components and constraints support reusable designs that adapt more intelligently across layouts. Components provide a practical bridge between design and software development: create shared building blocks once, reuse them widely, and preserve controlled customization through overrides. Teams building consistent, evolving interfaces can use them to reduce duplication while keeping designs adaptable.

Read original

Design Systems Figma React Android+4

figmaJan 20, 20162 min readCurated summary

From Furniture to Screens | Figma Blog

Furniture design taught Figma designer Sayer Pease that tools should support people’s activities without becoming the focus themselves. Figma applies this principle through simple, versatile tools, tactile controls, and a restrained visual system that helps designers concentrate on their work. The broader lesson is that useful design principles can come from disciplines far beyond digital product design. ## Tools - A small, well-designed toolset can support both simple and complex work, much like a hammer can build anything from a cabinet to a house. - Figma’s pen tool was designed to feel more like a physical pen. - Its vector objects use networks of connected points rather than traditional paths, enabling more flexible and natural drawing. - The editor is intended to resemble an organized workbench, with essential tools easy to find and use. ## Control - Familiar, tactile interactions help users feel in control of digital tools. - Keyboard shortcuts provide both physical familiarity and greater efficiency. - Figma’s Command-drag selection heuristic distinguishes containers from their contents. - Users can select nested elements—such as icons inside a toolbar—without selecting the toolbar itself, reducing the need to think about layer hierarchy. ## Color as Semantic Guidance - Figma initially used an almost entirely monochromatic, “unskinned” interface so the product would fade behind users’ designs. - As functionality increased, the lack of visual differentiation made UI components harder to distinguish. - The revised approach uses color without making the interface visually dominant. - Colors add semantic meaning: green indicates actions, while blue indicates selection. - This helps users understand what they are doing at a glance rather than focusing on how the interface works. ## Learning Across Disciplines - Product designers should challenge the assumptions and conventions of their immediate field. - Valuable solutions can come from both historical design practices and unrelated disciplines. - Furniture design provides Figma with principles centered on utility, organization, control, and unobtrusive support. Ultimately, digital tools should enable users’ creativity rather than compete with it. Designers can improve products by studying how other disciplines create tools and environments that quietly support meaningful work.

Read original

Design Systems Figma User Experience User Interface+2

figmaDec 14, 20153 min readCurated summary

Grid Systems for Screen Design | Figma Blog

Swiss grid design remains relevant to digital products, but traditional fixed-page tools do not handle fluid screen sizes well. The post argues that flexible grids can preserve visual coherence while adapting to different devices. Figma’s solution combines constraints, layout grids, and nested frames to create responsive design systems with precise alignment. ## From Fixed Pages to Fluid Screens - Swiss designers such as Joseph Müller-Brockmann and Karl Gerstner systematized printed-page layouts using rational grid structures. - Traditional grids assumed fixed page dimensions and precise control over typography, margins, and spacing. - Digital interfaces must accommodate changing screen sizes, shapes, and pixel densities. - Designers often compensate with multiple artboards, repetitive adjustments, or guesswork when tools are built around static layouts. ## The Core Building Blocks Figma proposes three complementary features: - **Constraints:** Define how an object responds when its containing frame changes size. - **Layout grids:** Provide detailed alignment and sizing rules across a design. - **Nested frames:** Allow different parts of a design to use their own layout systems. The greatest flexibility comes from combining all three rather than using them independently. ## Constraints for Responsive Behavior - Objects can be anchored to the left, right, or center of a frame. - Objects can also stretch to fill available space. - Constraints provide a basic way to preserve relationships as a frame expands or contracts. ## Stretchable Layout Grids - Grids provide more granular control than simple edge or center constraints. - A box spanning two grid columns can grow or shrink while remaining aligned to those columns. - Column grids can organize text, toolbar icons, and other interface elements—not just web-page content. - Stretching grids allow layouts to respond naturally to changing screen dimensions. ## Frames Within Frames - Nested frames let different sections of a design use separate grids and alignment rules. - This makes it possible, for example, to keep toolbar icons aligned to one grid while allowing the main content to follow another layout. - Frames provide more functionality than static artboards because they support responsive relationships and hierarchical layout systems. - The structure resembles nested HTML `<div>` elements, making it closer to how designs are implemented in code. ## Toward Better Design Tools - Responsive layout systems are only a starting point for improving digital design tools. - The post encourages designers to reassess inherited conventions and look to historical design practices for useful ideas. - Modern tools should combine the coherence of traditional grids with the flexibility required by variable screens. Figma’s recommended approach is to build designs from nested frames, stretchable grids, and well-defined constraints, creating systems that remain organized without being tied to a single screen size.

Read original

Design Systems Figma HTML Responsive Design+3