User Interface

71 posts

figmaApr 30, 20252 min readCurated summary

How Figma Helps You Learn Figma | Figma Blog

Figma’s Product Education team has built a learning ecosystem to help users move from beginner concepts to practical design skills. It combines written guides, videos, interactive files, community support, and a refreshed beginner course based on feedback from millions of learners. The central message is that consistent, hands-on practice—and not fear of mistakes—is the best way to become comfortable with Figma. ## An Evolving Educational Ecosystem - The Help Center provides feature documentation, tutorials, and troubleshooting guidance. - YouTube tutorials demonstrate concepts through practical examples. - Interactive playground files let learners experiment safely. - The new **Figma Design for beginners** course teaches users by helping them create a portfolio website. - Students and teachers may qualify for Figma’s Education plan, which provides Professional plan features for free. ## Improving the Beginner Course Through Feedback - Nearly three million people have watched Figma’s original beginner course since its launch in 2020. - Learner feedback highlighted the need for: - More hands-on practice - Clearer explanations of complex features - Real-world examples - Greater emphasis on free features - The updated course includes feature deep dives, guided creative exercises, professional tips, and a usable portfolio website template. ## Turning Knowledge into Skill Figma recommends continuing to learn through practical projects and community interaction after completing the course. - **Start small:** Recreate manageable elements such as interactive buttons or loading animations before attempting a full website. - **Practice often:** Set weekly learning goals and use tutorials to build consistency, confidence, and familiarity with shortcuts. - **Get inspired:** Browse and duplicate projects in the Figma Community to study how other designers work. - **Make mistakes:** Experiment freely, iterate, and use undo shortcuts such as `Cmd/Ctrl + Z`. - **Be kind to yourself:** Skill development takes time, so learners should celebrate incremental progress and accept trial and error. Figma’s recommendation is to begin with the updated **Figma Design for beginners** course, then reinforce the lessons through small, regular projects and community exploration.

User Interface Figma Prototyping Interaction Design+1

figmaApr 15, 20253 min readCurated summary

Version Control: Three Ways Figma Explored Horizontal Scrolling | Figma Blog

Figma’s request for horizontal scrolling in the Layers panel exposed significant design and engineering complexity. The panel contains interactive, virtualized layers whose names and nesting change dynamically, so scrolling could easily obscure hierarchy or disrupt users’ mental models. Through three unshipped prototypes, the team learned that preserving context and preventing accidental actions mattered more than applying seemingly simple scrolling behaviors. ## Why Horizontal Scrolling Was Difficult - Nested layers can extend beyond the panel, requiring users to move horizontally to see their full hierarchy. - Layers are interactive: users can hide, lock, collapse, and expand them while scrolling. - Virtualization renders only visible layers for performance, meaning newly visible rows may have different text lengths. - The design needed to communicate that more content existed without making the hierarchy harder to understand. - Code-based prototyping with JavaScript, HTML, CSS, and React helped the team test behavior across thousands of layers and complex interactions. ## Version One: Indicators at the Panel Edges - The team explored showing icons at the top-left and bottom-right edges when layers moved out of view. - This symmetrical treatment was intended to help users understand their position in the hierarchy. - Engineering challenges arose because edge icons needed opaque backgrounds that covered layer text while scrolling. - Layer rows did not have enough positional knowledge to determine which areas should be covered or revealed. - The design also created a ragged edge where partially visible layer names ended, introducing visual clutter. - The experiment demonstrated that a symmetrical solution could create new problems, particularly around unused white space. ## Version Two: Automatically Scrolling to Selected Layers - Another prototype automatically scrolled the Layers panel to center a layer selected on the canvas. - Although this made the selected layer easy to find, it often moved the panel both vertically and horizontally. - Testers found the behavior disorienting because parent layers and surrounding context disappeared. - Figma compared the experience to a map suddenly jumping to another location while driving. - The team concluded that users need to retain their mental model of a layer’s name, location, and relationship to parent components. ## Version Three: Renaming Layers While Scrolling - Horizontal scrolling created ambiguity when a user began editing a layer name and then scrolled to another layer. - One possible behavior was to save the edited text automatically when scrolling away. - The team rejected this because scrolling was not a strong enough signal that the user intended to confirm the rename. - The issue highlighted the need to avoid turning navigation actions into irreversible edits. Figma’s experiments show that horizontal scrolling in a dynamic hierarchy is not merely a visual or mechanical feature. The best solution must preserve orientation, context, and user control while handling virtualization and interactive layer states.

User Interface Figma React JavaScript+4

figmaMar 24, 20252 min readCurated summary

Making the Move to UI3: A Guide to Figma’s Next Chapter | Figma Blog

Figma will retire UI2 on April 30, 2025, making UI3 the standard interface. The redesign prioritizes canvas space, streamlines workflows, and enables features that will only be available in UI3, ahead of Config. Although users may need time to rebuild muscle memory, Figma argues that the changes ultimately make the product more intuitive and efficient. ## UI3 Becomes the New Standard - Figma is ending support for UI2 on April 30. - New features and experiences planned around Config will be available only in UI3. - Figma says it has incorporated user feedback before the full transition. - Recent refinements include: - Replacing the redundant “Reset others” icon - Simplifying boolean-operation labels - Removing duplicate actions from the overflow menu - Updating the mask icon for clarity - Restoring a tidy-up experience closer to UI2 - After the transition, the Properties panel will become a major focus for further improvements. ## Adjusting to the Redesigned Interface - The author initially hesitated because established workflows and muscle memory make interface changes difficult. - After using UI3, they found the redesign more effective rather than merely different. - Reported adjustment times vary: - Some users adapted within a few hours. - Others needed about a week to rebuild muscle memory. - The overall response presented in the article is that UI3 quickly becomes familiar and comfortable. ## Smart Eyedropper Selection - The eyedropper shortcut remains **I**, but the tool now understands more than raw color values. - It stays active while inspecting the canvas and supports switching between color models such as: - Hex - HSB - RGB - When hovering over a color, style, or variable, Figma can identify and display the underlying style or variable instead of only showing a hexadecimal value. - UI3 also allows users to create variables directly where they are working, reducing interruptions to the design workflow. UI3 is positioned as a necessary transition rather than an optional visual refresh. Users should begin adapting before April 30, while taking advantage of its improved variable handling, streamlined controls, and more canvas-focused layout.

User Interface Figma Design Systems Prototyping+1

figmaDec 4, 20242 min readCurated summary

The Long and Short of It: Issue no.8 | Figma Blog

Figma’s Issue No. 8 reflects on how its community shaped the company’s 2024 releases and culture. The year included 180 product updates, a major Config conference, expanded tools for developers and product teams, and a refreshed brand identity. The central message is that Figma builds products through continuous dialogue with the people who use them. ## A Year Shaped by the Community - Figma published 180 new releases in 2024. - More than 10,000 people attended Config. - Over 220 Friends of Figma groups operated worldwide. - The company emphasizes that users do more than receive new features: they influence how those features evolve in practice. ## Expanding Figma’s Products - Figma refined its UI3 interface to give users more control. - AI tools were reworked with a more deliberate approach. - Dev Mode was enhanced to improve connections between design and code. - Figma Slides was launched to support presentations and give design work a broader stage. - The company highlights that the design process continues after launch, when users apply new tools to real workflows. ## Config and the Future of Product Building - Config 2024 was Figma’s largest conference yet, held in San Francisco with more than 10,000 attendees. - Figma points readers toward talks and advice from Config speakers. - Featured guidance focuses on creating memorable presentations and sessions that genuinely inspire audiences. - Early-bird tickets for Config 2025 were already available. ## A New Brand and Web System - As Figma expanded toward developers, marketers, and broader product teams, it updated its visual identity. - The redesign introduced a new typeface and a refreshed brand system. - Figma used its own tools to audit and rebuild its web system. - The process included streamlining components, improving workflows, refining variables and styles, and preparing the system for future growth. ## Design Inspiration and Cross-Functional Collaboration - Community templates for Figma Slides offer ways to create more engaging presentations. - Ableton Note designer Pablo Sánchez shares seven principles for designing surprising and memorable digital experiences. - One North’s Nick Villapiano argues that developers should participate actively in design rather than treating design as a handoff. - These examples reinforce Figma’s broader view that design is collaborative and extends across disciplines. Figma’s year-end message is ultimately a recommendation to keep building in conversation with users. Product launches, brand systems, developer workflows, and community events become more valuable when people actively shape how they are used.

User Interface Figma Design Systems Dev Mode+2

figmaSep 30, 20243 min readCurated summary

Figma on Figma: Our Approach to Designing UI3 | Figma Blog

UI3 is Figma’s two-year effort to make the interface less distracting and keep designers focused on their work. The redesign explored bold changes, including floating panels and a new way to minimize interface elements, but user feedback and performance data led Figma to reverse some decisions. The result balances a long-term vision for a cleaner canvas with practical adjustments based on how people actually work. ## Designing Around Focus and Flow - Figma’s central goal was to put users’ creative work “center stage” and minimize distractions. - The team relied on craft, intuition, feature-adoption data, performance metrics, and extensive user feedback. - Figma emphasizes that redesigning for designers requires establishing a clear destination while bringing users along through iteration. - UI3 was scheduled for general availability on October 10, 2024. ## Docked Panels: Experimentation and Reversal - The team explored unconventional navigation and properties-panel designs: - Panels appearing only on hover - Panels floating above the canvas - A simplified floating-panel system shared across Figma products - Floating panels initially seemed promising but created practical problems for frequent users: - Reduced available canvas space, especially on smaller screens - Made designs appear to sit behind the panels - Increased distraction - Made rulers less useful by moving them farther from the design - Slowed users down, conflicting with Figma’s goal that “speed is a feature” - For the full UI3 rollout, Figma reattached the navigation and properties panels in Figma Design. - The panels remain resizable for flexibility. - Floating UI continues in specific contexts, including: - Minimize UI mode in Figma Design - Grid view in Figma Slides - Default views in FigJam - Bottom toolbars across Figma products ## Minimize UI: Making the Canvas the Center - Figma’s redesign was guided by the belief that work should remain the primary focus of the canvas, even as interface conventions evolve. - The existing Hide UI feature was considered too rigid and “blunt.” - Minimize UI offers a more flexible alternative: - Collapses side panels for distraction-free work - Keeps tools readily accessible - Works better in small windows and split-screen setups - The interface hierarchy was reorganized to accommodate future features more cleanly. - The navigation panel now follows a linear structure: - File name - Branch name - Project name - Pages - Layers - This structure gives future navigation capabilities a logical place without requiring disruptive layout compromises. ## Updating Familiar Interface Conventions - UI3 also examines established interaction patterns, such as keyboard shortcuts, scrollbars, and blend modes. - Figma describes these as “training wheels” or conventions that may no longer match how modern interfaces are used. - The redesign aimed to balance newer interaction trends with users’ existing habits and expectations. UI3 demonstrates that successful redesign is not simply about pursuing a cleaner or more ambitious vision. Figma’s experience suggests that bold experiments should be tested in real workflows, with usability and performance data ultimately determining which ideas remain.

User Interface Figma Design Systems User Experience+2

figmaAug 28, 20242 min readCurated summary

Breaking In: A Guide To Landing Your First Product Design Role | Figma Blog

Figma’s guide explains how aspiring product designers can land their first role by presenting strong work, communicating their thinking, and showing how they learn from challenges. It emphasizes that a portfolio should be personal but focused on clear storytelling, accessible navigation, and evidence of design impact. The strongest projects are those where candidates can explain their decisions, trade-offs, constraints, and outcomes. ## Crafting a Portfolio - Portfolios do not need to follow one prescribed format or use a specific website builder. - The priority is to: - Showcase your best work. - Tell compelling project stories. - Make the portfolio easy to navigate. - Represent your individual perspective and skills. ### Lead with Your Best Work - Your first project creates the initial impression, so lead with work that best demonstrates your: - Design skills - Creativity - Process - Product impact - If choosing between projects, feature the one you can discuss most naturally and explain most compellingly. - Strong case studies should include: - A clear problem statement - Important project milestones - An insightful conclusion - Relevant metrics and learnings - What you would change in retrospect - A project does not need to have been an overwhelming success. Honest reflection and lessons learned can create a stronger narrative. - Explain the reasoning behind design decisions, not just the final visuals. - Discuss the trade-offs, advantages, disadvantages, constraints, and implications of choices involving colors, components, styles, and copy. - Figma designer Tammy Taabassum argues that explaining “why” demonstrates product thinking more effectively than simply showing “what” was designed. ## Figma’s Early-Career Opportunities - Figma welcomes interns and new graduates onto its product design team. - Early-career designers are encouraged to contribute actively and bring new ideas rather than merely observe. - The guide is intended to explain what Figma looks for and how aspiring designers can prepare for its interview process. A practical approach is to build a portfolio around a few well-developed case studies, prioritize the work you can explain most clearly, and make your decision-making and learning as visible as the final design.

User Interface Figma User Experience Generative AI+3

figmaAug 14, 20242 min readCurated summary

The Three Cs of Figma: A Beginner’s Guide to Success | Figma Blog

Figma beginners should focus less on memorizing individual features and more on building practical skills through three stages: creation, customization, and collaboration. The author argues that this framework makes learning more structured and helps users progress from making simple designs to creating reusable resources for their teams. Learning by doing, seeking help, and setting realistic milestones are central to that progression. ## Establishing Goals, Timelines, and Mindset - Define what you want to learn and how Figma fits into your role, whether in design, development, product management, or education. - Suggested milestones: - **30 days:** Learn basic tools, collaboration practices, and file organization. - **60 days:** Pilot projects and identify knowledge gaps. - **90 days:** Add more advanced features to your workflow. - Adopt a hands-on learning approach by experimenting, making mistakes, and rebuilding. - Share work and ask questions through coworkers, Slack, social media, or the Figma Community Forum. - Take breaks and allow time for unfamiliar tools and processes to become natural. ## The Three Cs of Figma - **Creation:** Learn to make a basic design element. - **Customization:** Use advanced features to make the element flexible and reusable. - **Collaboration:** Share the work with teammates and provide components or documentation they can use. - The three stages function like rungs on a ladder: users first create something, then improve its adaptability, and finally make it useful to others. - Figma’s Help Center, YouTube channel, virtual events, and community resources support this learning process. ## Applying the Framework to a Button - A button provides a practical example of the three Cs: - Create a basic button. - Turn it into a reusable component. - Publish it so teammates can use it in their own files. - This approach connects individual feature knowledge to real design workflows and team collaboration. - Figma provides a playground file for practicing the progression. The practical recommendation is to learn Figma through small, complete projects rather than isolated feature tutorials. Build something, make it reusable, and share it with others while progressing at a sustainable pace.

User Interface Figma Design Systems Prototyping+2

figmaJul 16, 20242 min readCurated summary

An Update on our Make Designs Feature | Figma Blog

Figma temporarily disabled its Make Designs AI feature after discovering that some generated mockups closely resembled real applications, including Apple’s weather app. The issue came not from model training, but from insufficiently reviewed components and example screens in Figma’s custom design systems. Figma removed the problematic assets and planned stronger quality assurance before relaunching the feature, later bringing it back under the name First Draft with updates. ## How Make Designs Works - Combines an AI model, contextual design-system data, and a user prompt. - Uses generally available models such as OpenAI’s GPT-4o and Amazon Titan, without additional fine-tuning. - Relies on separate mobile and desktop design systems containing hundreds of components and example compositions. - The language model selects, arranges, parameterizes, and themes components based on the prompt. - Amazon Titan generates the images used in the resulting designs. ## What Went Wrong - Figma reviewed the design systems during development and private beta testing. - Shortly before Config 2024, new components and example screens were added without sufficient vetting. - Some assets resembled patterns from real-world applications. - A prompt for a weather app produced results that appeared notably similar to Apple’s first-party design. - The incident was identified after designer Andy Allen raised the concern, prompting an immediate investigation. ## Figma’s Response - The team traced the similarities to assets in the underlying design systems. - Problematic components and examples were removed. - Make Designs was rolled back and disabled. - Figma postponed relaunching the feature while developing a more robust QA process. ## Future Direction - Make Designs was originally called “First Draft” to emphasize that AI output is only a starting point. - Figma wants users eventually to connect the feature to their own company design systems. - This could reduce the time spent locating, assembling, and configuring components. - Figma maintains that designers remain essential for refining drafts into meaningful user experiences. - The feature was later re-enabled with updates and renamed First Draft. Figma’s experience highlights the need to carefully audit not only AI models but also the data, components, and examples supplied to them. AI-generated designs should be treated as starting points that require professional review and creative refinement.

User Interface AI Design Systems Generative AI+3

figmaJun 25, 20242 min readCurated summary

What is Good Design in the Age of AI? | Figma Blog

AI is making product creation faster and more accessible, increasing the importance of design as a differentiator. Figma argues that designers should not chase automation or trends, but apply enduring principles such as empathy, creativity, and solving real user needs. The future of good design will depend on experimentation, stronger design-to-code connections, pragmatism, and new forms of human–AI collaboration. ## AI Creates a New Design Inflection Point - Like the iPhone’s launch in 2007, AI is introducing a new medium that requires experimentation and the development of new interaction patterns. - Early mobile products often forced desktop experiences onto smaller screens; today, many AI products similarly rely on basic chatbots and templates. - Designers can unlock AI’s potential through: - Richer interactions - Intuitive gestures - Patterns designed specifically for AI - AI can generate code, designs, and complete applications from prompts, allowing teams to move rapidly from concept to creation. - As more people participate in product development, thoughtful design becomes increasingly important for products to stand out. ## Codifying the Fundamentals of Good Design - Figma’s AI feature for generating initial UI drafts needed to understand the mechanics of good design. - Because large language models are text-oriented, generating high-quality visual interfaces is more difficult than generating text or code. - A complete rulebook for design is impractical: - Good design contains too many contextual details to define exhaustively. - Extremely large prompts exceed technical token limits. - Figma instead focused on reducing design expertise to a small set of broadly applicable principles. - Teaching AI requires designers to make their intuitive knowledge explicit by creating rules that are: - Clear - Concrete - Practical - General enough to apply across many interfaces - The process resembles teaching design: instructors must break complex judgment into principles that others can understand and use. ## Design’s Continuing Role - AI should elevate design rather than simply automate it. - The most valuable design foundations remain relatively constant despite technological change. - Designers’ roles may evolve, but their understanding of users, creativity, and ability to solve meaningful problems remain essential. ## Practical Direction Teams should treat AI as a new design medium, not merely an automation tool. They should experiment with AI-native interaction patterns while grounding products in concise, teachable design principles and genuine user needs.

User Interface Figma AI Design Systems+2

figmaJun 25, 20242 min readCurated summary

Inside the Redesigned Figma, Where Your Work Takes Center Stage | Figma Blog

UI3 is Figma’s third major redesign, created to manage the complexity accumulated over nearly a decade of new features. Its central goal is to put users’ work—not the interface—at the center while preserving professional workflows and making Figma more approachable. The redesign also establishes a flexible foundation for products such as Dev Mode, Figma AI, and Figma Slides. ## Why Figma redesigned the interface - **Center users’ ideas:** New capabilities such as interactive components and AI risked making the interface feel crowded or distracting. - **Serve both beginners and experts:** Figma aimed to become more intuitive for newcomers without removing the power and familiar ergonomics professional designers rely on. - **Adapt to modern design practices:** Reusable components, generative AI, and higher-level abstractions require tools that provide building blocks rather than focusing only on individual pixels. - **Prepare for the future:** UI3 supports Figma’s broader ecosystem, including closer connections between design and code, Dev Mode, Figma AI, and the newly introduced Figma Slides. ## Clearing the stage for the canvas - The redesign began by maximizing canvas space and reducing visual distractions. - Figma experimented with extreme concepts, including interfaces that appeared only on hover and layouts where panels constantly appeared and disappeared. - These approaches made the workspace feel unstable, so the team moved toward a more consistent solution: - Resizable and collapsible panels - A slim toolbar positioned at the bottom of the canvas - The ability to hide the interface completely and reveal panels when needed - The new structure creates a roomier workspace and provides a consistent framework for switching between Figma products. ## Iterative design process - Figma explored hundreds of interface variations. - Designers built and used many prototypes internally to evaluate how each approach affected real workflows. - Features and controls were deliberately removed until the team identified what users genuinely missed, then selectively restored them. UI3’s practical recommendation is to give designers more control over the interface: keep tools accessible, but allow the canvas and the work itself to take priority.

User Interface Figma Design Systems User Experience+2

figmaJun 25, 20242 min readCurated summary

Config 2024 In Review | Figma Blog

Figma’s Config 2024 announcements focus on making design more exploratory, efficient, and connected to development. The company introduced Figma AI, a redesigned UI3 interface, Figma Slides, major Dev Mode improvements, and quality-of-life updates. Figma argues that as AI makes software creation easier, thoughtful design will become an even stronger differentiator. ## Figma AI: Faster exploration and production - **Visual Search** lets users find similar designs across accessible team files using a screenshot, selected frame, image, or sketch. - Improved **Asset Search** understands the context of queries, even when search terms do not match asset names. - New AI-powered efficiency features can: - Generate realistic images and copy - Rewrite, translate, or vary text - Automatically create prototype connections - Rename layers - **Make Designs**, available through the Actions panel, generates initial UI layouts and component options from text prompts. - Figma says these tools are built around practical user needs rather than AI hype, using large language models to reduce tedious work and help designers explore more possibilities. ## Other major Config announcements - **UI3** redesigns the Figma interface. - **Figma Slides** introduces a dedicated environment for building, collaborating on, and presenting presentations. - **Dev Mode updates** aim to move teams from designs being merely “design ready” to being fully “dev complete.” - Additional improvements target **Auto Layout, UI kits, and the prototype viewer**. ## Availability - Figma AI and UI3 were announced as limited betas with gradual rollout. - Users can join the waitlist through Figma’s help menu by selecting **“Join UI3 + AI waitlist.”** Figma’s overall direction is to support the full path from idea generation through design, presentation, and development, while using AI to automate routine tasks and expand creative exploration.

User Interface AI Design Systems Large Language Models+3

figmaApr 7, 20242 min readCurated summary

How to Build a Design System | Design Systems 102 | Figma Blog

A design system creates a shared language and reusable components that improve product consistency, team efficiency, and collaboration. Figma recommends building one around the organization’s specific goals and challenges rather than following a universal formula. The process begins with understanding the problem, auditing existing work, involving cross-functional partners, and choosing an approach that can evolve over time. ## Lay the Groundwork - Define why the design system is needed: - What problems should it solve? - What goals should it support? - How will success be measured? - Recognize that systems vary in scope: - Small teams may need a simple component library. - Enterprise organizations may require a comprehensive system. - Design the system to grow as product and team needs change. ## Take Stock of Existing Design and Code - Collect screenshots and examples of the product across: - Platforms and devices - Interactive states - Alternate versions - Look for recurring patterns and consistent UI elements that can become system foundations. - Audit the codebase for existing reusable components, shared CSS variables, and repeated UI patterns. - Build on existing engineering work instead of creating disconnected design and development systems. ## Organize and Evaluate the Product Landscape - Categorize the collected examples to understand the current design language. - Identify: - Inconsistencies across products or platforms - Redundant solutions - Disconnected user experiences - Problems being solved differently by designers and developers - Use these findings to prioritize where a unified system can provide the greatest value. ## Find Cross-Functional Champions - Involve designers, developers, product managers, and other stakeholders. - Seek people who care about consistency and can advocate for the system internally. - Include developers early because they can assess: - Technical feasibility - Implementation requirements - Long-term maintenance - A design system can begin with a single dedicated contributor, but broader collaboration helps it serve the whole product team. ## Choose an Approach - Decide whether to: - Build a custom system from scratch - Adopt an existing framework and adapt it to the organization’s needs - The best choice depends on the team’s goals, existing assets, technical context, and available resources. A practical starting point is to define measurable goals, audit both design files and production code, and form a cross-functional group before creating components. This ensures the design system addresses real product problems and remains useful as the organization evolves.

User Interface Figma Design Systems User Experience+3

figmaDec 6, 20232 min readCurated summary

From Slack-lash to Toggle Tax: The New Vernacular of Work | Figma Blog

The article presents a playful glossary for the changing realities of digital and hybrid work. These terms capture common frustrations, habits, and moments in modern workplaces—from endless notifications and multitasking to awkward meetings and collaborative design. Together, they suggest that humor and shared language help people navigate an increasingly virtual work environment. ## Balancing Effort and Iteration - **Fidelity Fluency:** Knowing how polished a project needs to be, and avoiding unnecessary pixel-perfect work when a rough concept is sufficient. - **WIP Waltz:** The continual cycle of revising, tweaking, and rethinking work as it develops. - **Style Guide Safari:** Exploring a design system’s typography, colors, and other visual elements to find the right creative direction. - **UI Lock Ness Monster:** A frequently discussed interface feature that is always expected in a future update but never appears. ## Digital Overload and Distraction - **Keyboard Cardio:** The frantic effort of sending emails and Slack messages, likened to an intense keyboard workout. - **Slack-lash:** The shock of being hit by a sudden flood of Slack notifications and messages. - **Tab Tsunami:** Having so many browser tabs open that the screen—and one’s attention—feels overwhelmed. - **Toggle Tax:** The mental cost of constantly switching between tasks and contexts. - **Workplace Whack-a-Mole:** Repeatedly responding to incoming tasks, alerts, and emails as soon as they appear. ## Virtual Meeting Experiences - **Icebroken:** Oversharing during an icebreaker and turning a friendly introduction into an uncomfortable moment. - **Screenshare Scramble:** Quickly hiding embarrassing or irrelevant browser tabs before sharing a screen. - **Zoombie:** Someone who appears present on a video call but is mentally disengaged. - **Zoom Zen:** The rare, highly effective meeting where the agenda is clear, participation runs smoothly, and the call ends on time. ## Collaboration and Social Validation - **Sudden Heavy Stamping:** Receiving an unexpected rush of positive reactions—such as hearts or “+1” votes—on a collaborative idea. - **Fidelity Fluency** also reflects collaborative judgment: teams must match the level of detail to the project’s actual needs rather than overinvesting in polish. The glossary turns the habits and tensions of modern work into memorable expressions. Recognizing these patterns can make digital collaboration more manageable—and encourage teams to protect focus, communicate intentionally, and find humor in workplace chaos.

User Interface Figma Design Systems Slack+3

figmaOct 17, 20233 min readCurated summary

Figma's commitment to FedRAMP | Figma Blog

Figma is pursuing FedRAMP Moderate certification to make its collaborative design platform available to US government agencies and public-sector organizations. The certification process demonstrates that Figma meets rigorous security and privacy requirements and would allow government teams to safely design, prototype, and test digital services. Figma argues that its browser-based, collaborative workflow could help agencies iterate faster and improve citizen-facing software. ## FedRAMP Status and Purpose - Figma’s FedRAMP Moderate authorization is currently “in process.” - Listing on the FedRAMP Marketplace indicates that Figma has completed an audit and is moving through the final certification steps. - FedRAMP evaluates cloud applications against government security controls and categorizes them as low, moderate, or high impact. - Certification is necessary before Figma can fully host government data. ## Benefits for Public-Sector Users - Certification would allow government agencies, contractors, and civic-technology teams to: - Create software designs in Figma - Build and test interactive prototypes - Validate ideas through rapid iteration - Improve the usability of government applications - Figma says the certification will give customers confidence that their data and content meet demanding security and privacy standards. - Its browser-based and platform-agnostic design supports collaboration among distributed teams, including agencies and contingent workers. ## Public-Sector Collaboration and Modernization - The shift toward hybrid and remote work has increased demand for accessible, collaborative digital tools in government. - Figma connects this trend with broader efforts to improve customer experience and rebuild trust in government services. - The company believes public-sector organizations often work similarly to private companies despite having different missions and business models. - Collaborative design could help agencies ship services more quickly and achieve better outcomes for citizens. ## Building a Federal Government Team - Figma is expanding its federal-government organization, beginning with federal sales leader James Kohler. - The company is seeking people who understand government procurement and security requirements while also being able to build new programs from the ground up. - Kohler’s role is to adapt lessons from Figma’s private-sector work to the needs of government users. - Figma plans to encourage knowledge sharing between its commercial and government teams. ## Next Steps - Figma’s immediate goal is to complete FedRAMP certification and become authorized for federal use. - The company intends to continue engaging public-sector customers and sharing updates about its government efforts. Figma’s certification effort is a prerequisite for broader government adoption. If completed, the platform could give public-sector teams a secure way to collaborate on and rapidly improve digital services.

User Interface Figma Prototyping Security+4

figmaJun 18, 20232 min readCurated summary

What’s Happening at Config 2023? | Figma Blog

Config 2023 was covered as a live, informal scene report by Figma editors Herbert Lui and Jenny Xie. The post captures the excitement, humor, attendee reactions, and social-media energy surrounding the event rather than presenting a detailed recap of individual talks. Readers are directed to watch the full talks online and revisit the community conversation under #Config2023 and #confits2023. ## Live Coverage from Config 2023 - Figma’s Editorial Team reported from the event in real time. - The coverage aimed to give people who missed Config a sense of the atmosphere and ongoing activity. - The post included embedded posts from attendees and Figma community members, including jokes about different types of designers attending the conference. ## Community Reactions and Social Media - Attendees shared photos, commentary, and humorous observations on X/Twitter. - The hashtag **#confits2023** highlighted fashion and outfit-related posts from the event. - The social conversation reflected both the professional content and the playful culture surrounding Config. ## Talks and Follow-Up Content - Figma provided a YouTube playlist containing all talks from Config 2023. - Readers were encouraged to catch up on presentations after the event. - The editors closed by celebrating the event’s success, acknowledging “Config withdrawals,” and looking ahead to the following year. The practical takeaway is to use the recorded talk playlist for substantive content, while the blog and accompanying social posts provide a more casual view of Config’s community and atmosphere.

User Interface Figma Collaborative Design Design Tools+1