figmaAug 30, 2023

How Spotify’s Design System Goes Beyond Platforms | Figma Blog (opens in new tab)

Spotify’s expansion to 45 platforms and more than 2,000 device types exposed inconsistencies between its product experiences. The company evolved Encore from separate mobile and web systems into a cross-platform design system focused on shared foundations and reusable components. Its goal is to make Spotify feel coherent everywhere without erasing the distinctive strengths of each platform. ## The Challenge of Consistency at Scale - Spotify’s 2019 ubiquity strategy aimed to make audio available across TVs, cars, computers, phones, and many other devices. - The design team needed more than broad platform coverage: users should recognize the experience as distinctly Spotify wherever they use it. - Components became central to achieving this consistency, from defining their scope to implementing them across products. ## The Birth and Evolution of Encore - When introduced in 2019, Encore had two main subsystems: - **Encore Consumer Mobile**, a flexible catalog of mobile-focused UI components. - **Encore Web**, supporting a wider range of web products. - Both systems used shared design tokens for foundational decisions such as colors and typography. - Over time, differences in component sizing, typography, and state treatments revealed that the subsystems needed greater commonality. - By 2022, flexibility had created too much divergence, prompting Spotify to rebalance the system toward reusable, consistent components. ## A Shared Layer Between Foundation and Products - Spotify created a specialized team focused on reusable components for Encore Mobile. - This new layer sits between the foundational system and Encore Consumer Mobile. - It acts as a “first line of defense,” reducing the need for product-specific teams to build every component themselves. - Developed in collaboration with Encore Web, the layer establishes platform parity from the beginning rather than retrofitting consistency later. ## Designing Components Across Platforms - The overall workflow remained familiar: research, design, and development. - The major change was coordinating design work across iOS, Android, and Web instead of designing for one platform in isolation. - Components are intended to share a coherent visual and behavioral language while still adapting to platform-specific requirements. - This requires collaboration among specialists, since web and mobile designers bring different domain expertise. - Spotify begins by bringing platform teams together and researching each platform’s unique characteristics before creating the shared component. Spotify’s approach treats a design system as more than a collection of platform-specific libraries. By establishing shared components early and combining them with platform-aware design, teams can create experiences that feel unified without sacrificing the qualities that make each device and interface effective.

webdesign-systemsandroidios+3

figmaFeb 26, 2020

Reflections on Config, our first user conference | Figma Blog (opens in new tab)

Config, Figma’s first user conference, brought more than 1,000 participants together to learn, collaborate, and strengthen the design community. Rather than imposing a rigid agenda, Figma invited users to shape the event through workshops, talks, and roundtables. The conference highlighted open design, deeper community connection, and the importance of using technology to support—not replace—human relationships. ## A Conference Built by the Community - Figma created Config as a physical gathering where users and employees could exchange ideas directly. - Attendees discussed team culture, mentorship, design ethics, and other issues affecting the design industry. - Many sessions came from community submissions, encouraging participants to contribute rather than simply listen. - Sessions were also recorded for people who could not attend in person. ## Open Design and Shared Creativity - A central theme was “open design”: sharing, remixing, and building on one another’s work. - Devon Zuegel explored how open-source principles apply to urban planning and physical infrastructure. - Jason Kunesh described how Chicago students helped create a design system when the city’s design team lacked resources. - Miguel Solorio explained how Microsoft incorporated the broader community into its design process. ## Technology as a Tool for Connection - Craig Mod warned that technology can encourage isolation, even as it makes communication easier. - He argued that digital tools should help people connect more deeply with their surroundings rather than escape them. - May-Li Khoe discussed challenging established norms while supporting the communities she cares about. - Both talks encouraged attendees to consider their responsibility to build stronger, more inclusive communities. ## Continuing the Conversation - Figma presented Config as an ongoing community dialogue rather than a one-time event. - The company thanked attendees, speakers, and employees for making the conference possible. - Figma encouraged everyone to watch the recorded sessions and stay engaged with future discussions. Config’s main lesson was that design becomes more powerful when it is shared openly and grounded in community. Future conferences and design initiatives should prioritize participation, collaboration, and meaningful human connection.

webfigmadesign-systemsopen-source+2

figmaFeb 13, 2019

Figma Raises $40MM Series C Round led by Sequoia | Figma Blog (opens in new tab)

Figma announced a $40 million Series C funding round led by Sequoia Capital, with participation from new and existing investors. The funding supports Figma’s mission to make visual design accessible, collaborative, and web-based. The company plans to expand its enterprise offering, improve performance and design-system tools, develop extensibility, and strengthen its global community. ## Funding and Strategic Investors - Sequoia Capital led the round, joined by Coatue, Founders Fund, Jeff Weiner, Mike Krieger, Andrew Wilson, Dan Rose, and existing investors Index, Greylock, and KPCB. - Figma selected investors with experience building enduring companies and communities. - The company highlighted Sequoia’s investments in GitHub and PlanGrid as evidence of relevant expertise. ## Expanding Collaborative Design - Figma argues that productivity software is increasingly becoming collaborative and shared. - Major design teams at Square, Uber, Twitter, and GitHub had adopted Figma. - The new funding will support: - Expansion of Figma Organization, its enterprise offering - Improvements for individual designers and small teams - Continued development of collaborative workflows ## Performance and Design Systems - Despite being viewed as faster than native competitors, Figma sees significant opportunities to improve loading and rendering performance. - With more than one million signups, the company emphasizes delivering a high-quality experience at scale. - A major focus is making Figma the best platform for building and managing design systems. ## Platform Extensibility - Figma is developing platform and extension capabilities to support varied design workflows. - The company is deliberately avoiding a fixed release timeline because extensions must be stable and secure. - Extensibility is presented as essential to making the design process genuinely open. ## Building a Global Community - Around 80% of Figma’s weekly active users were located outside the United States. - The company had 26 user groups in cities ranging from Lagos to Toronto. - Figma planned to improve connections among users worldwide through meetups, local groups, and other community initiatives. - Community is described as a foundation for Figma’s future and a key reason Sequoia was an appealing partner. Figma intended to use the Series C investment not simply to grow the business, but to deepen its collaborative product, improve its technical foundations, and build a global community around accessible design.

webfigmadesign-systemscollaboration+2

figmaOct 2, 2018

We made a mistake with our API Challenge, and we’re sorry | Figma Blog (opens in new tab)

Figma apologized for launching an API challenge that the design community viewed as unpaid “spec work.” The challenge aimed to encourage a Figma-to-Sketch export and support a more open design ecosystem, but Figma acknowledged that its enthusiasm overshadowed the risk of exploiting creative labor. The company paused the challenge and later decided not to pursue any version of it. ## The API Challenge and Its Goal - Figma launched a challenge focused on building a Figma-to-Sketch export. - Its stated purpose was to promote an open ecosystem and help fund tools for exporting data from Figma. - The initiative was intended to expand interoperability within the design toolchain. ## Community Criticism - Designers quickly criticized the challenge as “spec work”—unpaid creative work submitted with no guaranteed compensation. - The backlash reflected broader concerns about skilled workers being asked to produce valuable work without fair payment. - Figma recognized that the challenge conflicted with its stated belief that creatives should be paid. ## Figma’s Response - CEO Dylan Field acknowledged that the company had made a mistake. - Figma said it had been “swept away” by its enthusiasm for making the platform more open. - The company paused the challenge and considered alternative structures that would not require participants to work without guaranteed compensation. - In a later update dated November 19, 2018, Figma said it would not move forward with any version of the challenge at that time. Figma’s experience illustrates the importance of designing developer and creative programs around clear compensation and consent, especially when participants’ work could directly benefit a commercial product.

webfigmaapidesign-tools+2

figmaDec 14, 2015

Slack From the Start | Figma Blog (opens in new tab)

Figma chose to build its collaboration experience around Slack rather than recreate messaging and notification features. User research showed that Slack was already central to designers’ daily workflows and correlated with more transparent collaboration. By making a Figma team a Slack team and routing notifications through Slack, Figma aimed to reduce tool fragmentation and strengthen its core product. ## Why Slack Mattered to Figma’s Users - Figma interviewed many designers about file storage, specifications, and product decisions. - More than half of the designers surveyed reported using Slack throughout the day. - Slack adoption was associated with more open and transparent design processes. ## Building on Slack Instead of Duplicating It - Figma considered recreating communication features inside its own product. - The team rejected that approach because it would create another inbox and require users to manage teams in two places. - Instead, Figma built its collaboration model on top of Slack: - A Figma team corresponded to a Slack team. - Figma file notifications were delivered through Slack. - Communication about design remained connected to users’ existing workflows. ## A Strategic Platform Bet - Figma viewed Slack as a platform well before Slack formally celebrated its platform launch. - Deep integration was considered a significant product and business bet. - Early results suggested the strategy was working, and Figma expected other companies to adopt similar integrations. The practical lesson is to integrate with tools users already rely on rather than reproducing their functionality. For Figma, treating Slack as foundational reduced friction and made collaboration feel like part of an existing workflow.

webfigmaslackcollaboration+2