Techlist.io - Korean Tech Blog Curator

figmaAug 1, 20222 min readCurated summary

Little Big Updates: More improvements for design and collaboration | Figma Blog

Figma’s August 2022 “Little Big Updates” release introduced more than 20 incremental improvements across Figma, FigJam, the desktop and mobile apps, and Community. The updates focus on smoother design workflows, faster collaboration, better accessibility, and fewer interruptions. Together, they show Figma’s ongoing effort to address user feedback and refine everyday interactions. ## Figma design improvements - Pencil annotations no longer get clipped or interfere with auto layout. - Gradient stops can be evenly distributed by double-clicking them. - Selecting a top-level frame also selects subsequent registered top-level frames. - Objects can be aligned as a temporary group by holding **Shift** while using alignment controls. - Pasting between text nodes preserves bullets and text styles. - Text-alignment shortcuts work while editing text inside a text box. - Links in comments open directly without an interstitial page. ## FigJam collaboration and diagramming - Auto-create prompts now appear on all four sides of shapes and stickies. - The Connector tool remains active by default, allowing users to continue diagramming without repeatedly reselecting it. - New guidelines help match shapes’ widths and heights. - Hovering over stamps reveals the users who added them. - Right-clicking a sticker provides access to its parent library and more stickers. - Copy and paste can replace image fills quickly. - Connectors automatically straighten when objects appear center-aligned. ## App, browser, and Community updates - The desktop app adds a menu-bar notification bell. - FigJam on iPad gets improved Apple Pencil responsiveness. - iPad users can undo and redo with two- or three-finger taps and swipes. - FigJam’s iPad app now supports Observation mode and Spotlight. - Search previews include recent searches, while list views show file owners. - Keyboard navigation makes it easier to move among collaborators and search by name. - **Tab** and **Shift + Tab** navigation now work within the comments modal. - Figma Community has been redesigned with new categories and search filters. Users can try the improvements directly in Figma and suggest additional changes through the Figma forum.

Figma Figjam Collaborative Design Auto Layout+2

figmaJul 26, 20222 min readCurated summary

What’s new in Figma: July 2022 | Figma Blog

Figma’s July 2022 updates focus on strengthening collaboration, expanding global support, and making community resources easier to discover. The company introduced research on effective teamwork, launched a fully localized Japanese experience, and redesigned Figma Community browsing and search. Together, these changes aim to help teams collaborate more effectively and find useful resources faster. ## Research on Effective Collaboration - Figma studied more than 100 teams composed of designers, product managers, engineers, researchers, and writers. - The resulting report, *What Makes Collaboration Click?*, identifies five behaviors associated with better product outcomes: - Co-creation - Rapport - Role clarity - Feedback - Reflection - Figma also announced a livestream featuring product research leaders Cristen Torrey and Andrew Hogan to discuss the findings. ## Figma Expands in Japan - Figma launched a fully localized Japanese product interface, website, and help center. - The company opened a Tokyo office and hired local leadership to support Japanese users and the regional Figma Community. - The expansion reflects Figma’s international user base, with 80% of users located outside the United States. - Figma also introduced the Japanese-focused social account **@FigmaJapan**. ## Improving Figma Community Discovery - Figma redesigned Community browsing to help users navigate its large collection of shared resources. - Users can now more easily distinguish among: - Figma and FigJam products - Use cases such as design systems - Resource types such as files, templates, widgets, and plugins - Search received expanded filtering and sorting options. - Results can be sorted by trending, most popular, or most recent resources. - The changes are intended to make creators’ contributions more discoverable and help users find relevant assets more quickly. Figma’s July improvements combine better collaboration guidance with practical product changes, particularly stronger international support and more efficient Community search and discovery.

Figma Design Systems Figjam Collaborative Design+2

figmaJul 20, 20223 min readCurated summary

Illuminating dark mode | Figma Blog

Dark mode looked like a simple color swap, but Figma found it required a broad redesign of its UI architecture and engineering processes. The project aimed not only to satisfy user demand and improve accessibility, but also to create a scalable foundation for future themes. Figma ultimately treated dark mode as a systems problem involving product scope, shared components, edge cases, and maintainability. ## Accessibility and User Demand - Dark mode became Figma’s most requested feature after users complained about bright screens during late-night work. - It could improve legibility for people with certain visual impairments and aligned with Figma’s mission of making design accessible. - The team also considered WCAG contrast requirements rather than treating the feature as purely cosmetic. - Figma shipped dark mode in May 2022 after months of product, design, and engineering work. ## The Complexities of Color - The initial idea was to replace light colors with dark ones, but this approach would not scale as the product evolved. - Figma wanted a solution that: - Made new features support dark mode by default. - Simplified onboarding for engineers. - Reduced regressions when experimenting with themes. - Could support additional themes in Figma and FigJam. - Some decisions were straightforward: - Light editor panels would become dark. - Text and icons would become light foreground elements. - Toolbars and menus already dark in light mode would remain dark. - Other questions required product decisions: - Which parts of Figma should support dark mode? - Should user-created canvas content, such as the canvas background, change with the theme? - Should colors rendered by the C++ editor engine, including the transparency grid, also change? ## Auditing the Product Surface - Before coding began, team members audited Figma’s UI to estimate the work required for each surface. - The project involved far more than the main editor: - Modals - Panels - Toolbars - Dropdowns and submodals - Hidden states and complex edge cases - Each surface needed its full range of views and states considered, not just its most commonly seen appearance. ## Building a Systematic Approach - At kickoff, ten product engineering teams owned major parts of Figma’s interface. - Shared UI components had to be refactored so they could support dark mode where appropriate while remaining unchanged on unsupported surfaces. - The team recognized that a small central engineering group could not manually handle every component and state. - This drove the need for a systematic, regression-resistant approach that could scale across teams and continue supporting future product development. Figma’s experience shows that theme support should be designed as an extensible system, not implemented as a one-time recoloring exercise. Teams planning similar work should begin with a full product audit, define theme boundaries clearly, and invest in shared components and automation that make future themes easier to add.

Design Systems User Interface Accessibility Wcag+2

figmaJun 29, 20222 min readCurated summary

Digital Design Is Now A Real Job | Figma | Figma Blog

Digital design has gained formal recognition as a distinct profession, reflecting its growing importance to businesses and everyday life. The U.S. Bureau of Labor Statistics now separately tracks “web and digital interface designers” and projects nearly 40% growth in the broader category through 2030. This change confirms a global surge in demand driven by the increasing importance of digital products, subscriptions, and user engagement. ## Formal Recognition of Digital Design - The BLS previously grouped digital designers with web developers or did not track them separately. - Its new category recognizes web and digital interface design alongside established fields such as graphic, industrial, interior, and architectural design. - The broader web development and digital design category is projected to grow from 2020 to 2030 by almost 40%. - Projections for 2030 increased from 188,000 jobs before the pandemic to 225,000 by February 2022. ## Demand Is Growing Globally - Design recruiter Judy Wert describes demand for designers as unprecedented, with company inquiries reportedly tripling in recent years. - LinkedIn identified design and UX research as fast-growing job categories across countries including the UK, France, Germany, Poland, Spain, Brazil, Saudi Arabia, and India. - Figma’s survey of 280 enterprise companies in four countries found that design teams grew by an average of 31% between 2019 and 2022. ## Why Businesses Need More Designers - People increasingly depend on digital interfaces for essential activities, including banking, work, healthcare, entertainment, education, and personal planning. - Many companies now operate through subscriptions or user engagement, making retention and satisfaction critical. - Frequent product updates and rapidly changing user expectations require organizations to respond quickly to feedback. - Design therefore influences not only how products look, but also how companies compete, retain customers, and operate. - Design thinking and initiatives such as Stanford’s d.school have made design methods more accessible across organizations, reducing resistance to design work. Digital design’s recognition by the BLS is less a symbolic change than evidence of a broader business transformation. Organizations should treat design as a core strategic capability and continue investing in designers who can shape effective, adaptable digital products.

Figma User Experience Web Development Design Thinking+1

figmaJun 27, 20222 min readCurated summary

What’s new in Figma: June 2022 | Figma Blog

Figma’s June 2022 updates focus on making the platform more collaborative, extensible, and accessible. The major launch is widgets—interactive canvas objects that teams can use together—alongside easier access to plugins, improved API documentation, and expanded availability for students through Google Chromebooks. Together, these changes position Figma as a broader platform for design, development, education, and teamwork. ## Collaborative Widgets in Figma - Widgets are interactive objects embedded directly on the Figma canvas. - Unlike plugins, which primarily support individual automation, widgets enable real-time team interaction. - Potential uses include: - Voting and polls - Time tracking - Design annotations - Status indicators - Task management - Featured widgets include: - **Asana** for discussing tasks and adding follow-up actions - **Jira** for turning designs into development tasks - **RAG Status** for showing red, yellow, or green project status - **Navigate** for guiding stakeholders through designs ## Easier Access to Extensions - Figma made plugins and widgets more discoverable within the editor. - Users can now search for and install extensions directly from the Figma toolbar. - Updates to the Figma Community also make it easier to try and explore available extensions. ## Redesigned API Documentation - Figma introduced redesigned developer documentation to simplify building on its platform. - Improvements include: - New navigation - Better organization of resources - Copyable code blocks - Additional code samples and practical guides ## Expanding Access Through Chromebooks - Figma partnered with Google for Education to bring Figma and FigJam to Chromebooks. - School districts can deploy and manage Figma Organization licenses through Google Admin Console. - The program is offered free to participating schools, potentially reaching tens of millions of U.S. students. - Schools could apply for the beta beginning in summer 2022. Figma’s update recommends exploring widgets and community extensions for collaborative workflows, while the redesigned developer resources provide a clearer path for building custom tools and integrations.

Figma Figjam API Plugins+4

figmaJun 15, 20223 min readCurated summary

How Figma put the bounce in spring animations | Figma Blog

Figma’s spring animations replace manually tuned Bézier curves with motion based on physical properties. By modeling mass, stiffness, and damping, the system produces more natural movement, including believable weight, overshoot, bounce, and deceleration. The engineering challenge was translating physics-based controls into terms designers could easily understand and adjust. ## Why Figma introduced spring animations - Bézier animations let users control how movement starts and ends, but poorly tuned curves can cause: - Sudden, unnatural changes in speed - Objects to appear to accelerate without cause - Abrupt direction changes or stops - Spring animations define the physical behavior of an object rather than its exact path. - This approach helps create: - Weighted movement - Natural overshoot - Gentle transitions - Playful interactions such as FigJam emotes and high-fives ## The physics behind the motion Spring animations rely on three primary variables: - **Mass (`m`)** - Determines how heavy an object behaves. - More mass requires more force to accelerate. - Based on Newton’s law: `F = m × a`. - **Stiffness (`k`)** - Determines how strongly a spring resists displacement. - A stiffer spring pulls an object back more aggressively. - Based on Hooke’s law: `F = -k × x`. - **Damping (`b`)** - Represents resistance caused by friction or similar forces. - More damping reduces motion and brings the object to rest faster. - Its force is proportional and opposite to velocity: `F = -b × v`. Changing these values produces different animation qualities, such as gentle, quick, bouncy, or slow movement. ## Turning the equations into code - Figma used the WebKit `SpringSolver` to implement the spring timing function. - The solver accepts mass, stiffness, and damping and calculates the object’s position over time. - Although the underlying physics is stable and well understood, directly editing the variables is not intuitive for designers. - Designers typically want controls described as: - Faster or slower - More or less bouncy - More or less overshoot - Each physical parameter can affect multiple perceived qualities, making manual tuning difficult. For example, slowing an animation could involve increasing mass, but stiffness and damping also influence the result. ## Designing usable animation controls Figma needed a specialized interface that combined the three physical variables while presenting them in terms that matched how designers think about motion. The goal was to bridge the gap between precise physics calculations and practical animation adjustments, allowing users to achieve natural results without needing to understand the underlying equations. Figma’s approach demonstrates how physics-based animation can provide more convincing motion, provided the technical parameters are translated into accessible creative controls.

Figma User Interface Animation Spring Animations+2

figmaJun 14, 20223 min readCurated summary

Postmortem: Service disruptions on June 6 & 7 2022 | Figma Blog

Figma experienced four service disruptions between June 6–7, 2022, lasting from seven minutes to 1 hour 20 minutes. Existing files remained usable, but users could not open new files or collaborate; no data was lost. The root cause was a rare AWS ElastiCache/Redis bug that saturated the Engine CPU of a Cluster-Mode Enabled node under heavy Publish/Subscribe load. ## Impact and Timeline - Incidents occurred between 11:34 PM PDT on June 6 and 10:43 AM PDT on June 7. - The web application became fully functional at approximately 10:41 AM; some API features were restored later. - Users could continue working in already-open files. - Opening files and real-time collaboration were unavailable during disruptions. - Local changes were preserved and synchronized when service connectivity returned. ## Redis and ElastiCache Architecture - Figma uses AWS ElastiCache, a managed Redis service, for: - Caching frequently accessed data - Routing messages between services - Its setup included: - A Cluster-Mode Disabled instance - A Cluster-Mode Enabled instance, which supports horizontal scaling by adding Redis nodes - Several weeks before the outage, Figma moved its Redis Publish/Subscribe traffic from the CMD instance to the CME instance. - The workload had operated normally for weeks, with no obvious traffic or usage changes immediately before the incidents. ## Root Cause: Engine CPU Saturation - Monitoring alerted Figma within seconds that one CME ElastiCache node had reached 100% Engine CPU. - AWS later identified a rare Redis bug triggered by high Publish/Subscribe traffic on CME clusters. - Figma could not obtain CPU profiles from the underlying ElastiCache machines, making it difficult to identify the exact operation consuming CPU. - Increasing cluster capacity did not solve the problem and ultimately made the behavior worse. ## Mitigation and Investigation - Figma initially suspected insufficient capacity or faulty hardware. - Engineers: - Initiated a failover of the affected node - Created a larger ElastiCache cluster with more nodes - Redirected traffic to the replacement clusters when failover took too long - The first traffic redirection restored service, but the new cluster later experienced the same CPU saturation. - A subsequent failover completed successfully and restored service more quickly. - Engineers investigated and ruled out: - Routine backups or unexpected snapshots - Sudden increases in Redis command volume - Slow commands, large keys, or other obvious misuse - Scheduled background jobs - Blocking requests that appeared to be waiting longest for Redis commands did not resolve the issue. Figma’s outage was ultimately caused by an AWS Redis/ElastiCache defect rather than a data-loss event or an observable change in application traffic. The incident underscores the need to validate Redis Publish/Subscribe workloads on Cluster-Mode Enabled deployments and maintain mitigation strategies that do not rely solely on adding capacity.

Redis Incident Response Aws Elasticache Publish Subscribe+1

figmaJun 6, 20223 min readCurated summary

Figma and Chromebook: Empowering the next generation of designers | Figma Blog

Figma’s partnership with Google for Education brings Figma and FigJam to Chromebooks, making professional design and collaboration tools available to millions of students at no cost to participating schools. The initiative aims to remove financial, hardware, and geographic barriers to design education while preparing students for a digital-first workforce. Figma argues that design skills—especially visual communication, collaboration, problem-solving, and creativity—should be accessible to everyone, not only students with specialized degrees or expensive equipment. ## Bringing Design Tools to Chromebooks - School districts can deploy and manage free Figma Organization licenses through the Google Admin Console. - Figma and FigJam will be available on Chromebooks, the most common personal computing devices for students. - Students can design, brainstorm, and collaborate from their own school devices rather than relying on limited computer-lab sessions. - Schools can apply for the beta program beginning in summer 2022. ## Removing Barriers to Design Education - Specialized degrees, costly hardware, and expensive creative software can prevent students from gaining design experience. - Cloud-based Chromebooks make design tools more affordable and accessible. - Figma’s founders designed the product to be free because they had seen how expensive creative tools could be for college students. - The broader goal is to give students access to opportunities in design and software regardless of their financial background. ## Why Design Skills Matter - The shift from physical to digital work, accelerated by the pandemic, has increased the importance of digital design and visual communication. - Design education develops: - Complex problem-solving - Collaboration - Creative expression - Communication and critical thinking - These skills are valuable across disciplines, not only in traditional design careers. - Figma cites research suggesting that design-focused companies outperform their peers by a factor of two. ## Teachers’ and Students’ Experiences - Teachers report higher student engagement and enthusiasm in class. - Students with no previous exposure to design have become interested in pursuing it after graduation. - Some students use Figma at home for personal projects simply because they enjoy creating. - Teachers use FigJam for icebreakers, collaborative exercises, and classroom activities. ## Learning Through Play and Projects - Dylan Field emphasizes play, hands-on work, and project-based learning as important ways to develop design skills. - He describes his own project-based high school, where science concepts were reinforced through engineering projects. - That curriculum reflected a design process: - Explore broadly and generate possibilities - Narrow the options and choose a direction - Execute the selected idea - This approach helps students learn by making, experimenting, and solving concrete problems rather than relying solely on instruction. Figma’s Chromebook initiative is intended to make design education a normal part of students’ everyday learning. Providing free, accessible tools—combined with hands-on, collaborative projects—can help more students build the creative and technical skills needed for the future.

Figma Figjam Cloud Computing Digital Design+3

datadogJun 6, 20223 min readCurated summary

Engineering Spotlight: Tay Nishimura

Tay Nishimura’s career shows that succeeding in tech is often less about fitting a standard engineering mold and more about finding work that matches one’s strengths. Although she initially struggled with the speed and coding demands of software development, her rigor, visual thinking, and careful approach became valuable in site reliability engineering. Her transition was enabled by self-directed learning, community education, and ToyNet, an open source networking simulator that demonstrated her practical abilities. ## Entering Tech from Mathematics - Tay began as a mathematics major focused on real analysis, then added computer science after advice from a professor. - Internships at Amazon and Google introduced her to the technology industry. - She found a sharp contrast between academia and industry: - School rewarded theoretical rigor. - Industry emphasized practical, fast, and agile solutions. - Tay also felt like an outsider because she had little exposure to computers growing up. ## Struggling with Traditional Software Engineering - Coding did not come naturally to Tay’s visual way of thinking. - She translated code into drawings to understand and modify it, then converted those ideas back into code. - This process produced high-quality, careful work but made her slower than colleagues expected. - A manager suggested product management and site reliability engineering as possible alternatives. - Tay discovered that her deliberate pace was useful for SRE work, particularly when evaluating failure modes and making critical changes. - Because her company offered no path into those roles, she eventually left rather than continue facing increasing stress. ## Discovering Networking and Technical Program Work - Tay’s next role had a software engineer title but involved work closer to product or technical program management. - She learned that job titles and responsibilities vary significantly between companies. - With better work-life balance, she began studying computer networking in her free time. - She created visual diagrams and learning modules to explain switches, routers, and packet flows. - These efforts became Project Reclass, a nonprofit teaching technical skills to incarcerated people and military veterans. - The program used improvised equipment, such as fake routers and switches, to teach concepts in environments where real networking hardware was unavailable. ## Building ToyNet During the Pandemic - After her company laid off its entire office during COVID-19, Tay decided to pursue SRE directly. - When prisons suspended in-person education, Project Reclass adapted by creating a digital networking simulator. - Tay architected ToyNet, an open source platform built with: - React - A Flask backend - Containerized Mininet instances for network emulation - Users can connect simulated routers, switches, and hosts, configure IP addresses, and run commands such as `ping` and `arp`. - ToyNet was designed to work for incarcerated learners with restricted internet access. - Deploying it in the cloud also gave Tay practical experience that helped compensate for limited professional cloud experience. - Companies interested in the project were more likely to advance her through the interview process, eventually leading to Datadog. ## Finding the Right Environment at Datadog - At Datadog, Tay learned Kubernetes, chaos engineering, network traffic control, and Go. - She found that her rigor and visual thinking were assets rather than liabilities. - While learning Datadog’s Chaos Controller codebase, she mapped files and dependencies by drawing boxes and arrows. - Her experience suggests that engineers do not need to learn or reason in a single conventional way; the right environment can turn an apparent weakness into a strength. Tay’s path recommends experimenting broadly, studying independently, and building concrete projects that reveal how you think and solve problems. The most suitable tech role may emerge only after moving between companies and disciplines rather than forcing yourself to succeed in an ill-fitting position.

Kubernetes Open Source React Cloud Computing+4

datadogJun 6, 20222 min readCurated summary

Engineering Spotlight: Tay Nishimura | Datadog

Datadog announces that it has been named a Leader in the 2026 Gartner® Magic Quadrant™ for Observability Platforms. The provided content primarily consists of Datadog’s navigation and product listings, so it does not include Gartner’s evaluation details or the announcement’s supporting arguments. ## Recognition as an Observability Leader - Datadog highlights its placement as a Leader in Gartner’s 2026 Magic Quadrant for Observability Platforms. - The announcement links to a Gartner-related resource hosted by Datadog. - No specific Gartner strengths, cautions, scoring, or comparison with other vendors are included in the provided text. ## Datadog’s Broad Platform Coverage The navigation presents Datadog as a unified platform spanning: - **Infrastructure:** infrastructure, container, network, serverless, GPU, storage, and cloud-cost monitoring. - **Applications and data:** APM, universal service monitoring, continuous profiling, database monitoring, data-stream monitoring, and jobs monitoring. - **Logs and security:** log management, observability pipelines, sensitive-data scanning, cloud security, SIEM, workload protection, and application/API protection. - **Digital experience:** browser and mobile RUM, session replay, synthetic monitoring, product analytics, experiments, and error tracking. - **Software delivery and service management:** CI visibility, test optimization, feature flags, code coverage, incident response, SLOs, workflow automation, and case management. - **AI:** agent observability, GPU monitoring, AI integrations, AI agents, investigation tools, and an MCP server. Overall, the announcement positions Datadog’s broad, integrated observability and security platform as the basis for its Leader designation, but the supplied excerpt does not provide enough detail to assess Gartner’s underlying evaluation.

Kubernetes Datadog Observability Application Performance Monitoring+3

figmaMay 26, 20222 min readCurated summary

Full-scale expression with Grilli Type | Figma Blog

Variable fonts let designers adjust weight, optical size, slant, and other typographic properties from a single file, making type more adaptable across screens and contexts. Thierry Blancpain of Grilli Type argues that they improve efficiency, designer–developer collaboration, accessibility, and expressive web design. Their adoption in tools such as Figma helps turn precise typographic intentions into practical code. ## Scaling Typography Across Contexts - Fonts can become less readable when scaled from mobile or business-card sizes to desktop or billboard sizes. - Designers often need careful kerning and tracking adjustments to preserve legibility and visual balance. - Supporting multiple weights and styles traditionally requires separate font files, increasing assets, code complexity, download size, and opportunities for error. ## The Efficiency of Variable Fonts - A variable font contains an entire type family in one file. - Designers can adjust several axes—such as weight, optical size, and slant—rather than selecting from fixed styles. - Variable fonts are increasingly a standard format, so support across tools is important for avoiding workarounds and inconsistent workflows. - Figma’s support allows designers to use the same capabilities during design that developers can later implement in code. ## Improving Designer–Developer Collaboration - Developers benefit from managing one font file instead of many individual assets. - A single file simplifies updates, keeps code cleaner, and reduces implementation friction. - Designers gain finer control over typography, including custom weights and optical sizing. - Blancpain notes that variable fonts are especially valuable when designers and developers work in separate roles, since the format creates a shared, more transferable design language. ## More Expressive and Dynamic Web Design - Variable fonts support animated and interactive typography, such as changing from regular to bold on hover. - Grilli Type’s GT Maru Mega demonstrates how expressive type can remain usable at small sizes through variable adjustments. - Blancpain expects the web to become increasingly dynamic, with motion and responsive typography replacing purely static experiences. - Typography can communicate mood and interaction—not merely deliver information. Variable fonts are recommended as both a practical production format and a creative medium. Their combination of smaller asset overhead, precise control, and animation potential makes them useful for modern responsive interfaces and richer web experiences.

Figma User Experience Accessibility Typography+3

figmaMay 23, 20222 min readCurated summary

A look back at Config 2022 | Figma Blog

Config 2022 brought together more than 100 speakers for 24 hours of talks on ambitious, urgent design work. The event covered topics ranging from Web3 and research strategy to design systems and emerging technologies. A central message was that designers can create meaningful local or global change by designing more inclusively and acting with urgency. ## Designing for Different Digital Experiences - Yuan Qing Lim discussed designing for Chinese users who moved directly from limited PC use to widespread mobile internet. - Three themes shaped the discussion: - **“More is More”**: Chinese digital products often embrace rich, maximalist experiences. - **Super apps**: Users expect broad functionality within unified platforms. - **Community**: Digital experiences should reflect strong social and communal behaviors. - The goal is to better serve China’s roughly 1 billion internet users by accounting for local expectations rather than applying Western design assumptions. ## Designing for New Internet Users - Rahul Goradia focused on people who are new to the internet, a group often overlooked by mainstream UX practices. - This population is especially significant in India, where internet access is expected to grow rapidly. - Designers should use usability testing to make e-commerce approachable for newcomers. - Products must account for changing behaviors, particularly as users adapt to a post-pandemic digital environment. ## A Broad Program of Design Topics - Other Config 2022 sessions explored: - Decentralizing design through Web3 - Turning research findings into strategy and product development - Design systems and their limitations - UX writing and product copy - Design tokens and collaboration - Dark-mode implementation - Multi-platform design systems - Designing super apps for Southeast Asia’s cultural diversity The event’s practical takeaway is to design for a wider range of users, challenge assumptions about “standard” digital behavior, and use research and collaboration to make products more accessible and effective.

Figma Design Systems User Experience Design Tokens+4

figmaMay 18, 20222 min readCurated summary

A step forward in our accessibility efforts | Figma Blog

Figma argues that making design accessible requires enabling people of all abilities to participate throughout the design process. Its new prototype screen reader beta addresses a major gap for blind and low-vision users by making prototype content readable and navigable with assistive technology. The company presents this as an important step, while acknowledging that substantial accessibility work remains. ## Prototype Screen Reader Beta - Previously, screen readers encountered Figma prototypes as an essentially empty canvas, making text, images, and interactive content inaccessible. - The beta supports: - Text notes - Image alt text - Navigation through prototypes - Buttons and keyboard actions such as tabbing - Because Figma designs are not built as HTML, the company created an HTML representation of prototypes specifically for screen readers. - The beta was launched to gather feedback and improve the experience; it later became an open beta for everyone. ## Accessibility Work Underway - Figma has also introduced: - Dark mode and improved color-contrast compliance - Live captions for audio chat - A platform-wide accessibility assessment by Deque - Greater support for accessibility plugins, widgets, and community files - The company is developing reusable UI components and internal tools that encourage keyboard and screen reader compatibility. - Accessibility is being incorporated into team expectations, product development, and early user testing through alpha and beta programs. ## Remaining Challenges - Figma recognizes that more screen reader and general accessibility support is needed. - Planned capabilities include allowing users to: - Add alt text - Assign ARIA roles to components - Define prototype tab order - The company emphasizes that accessibility improvements should be developed collaboratively with the community. Figma’s recommendation in practice is to continue testing accessibility features with users who rely on assistive technology and to treat accessibility as an ongoing part of product design and engineering rather than a one-time update.

Accessibility HTML Wcag Keyboard Navigation+3

datadogMay 17, 20222 min readCurated summary

Introducing Husky, Datadog's third-generation event store | Datadog

Datadog’s page announces that Gartner named it a Leader in the 2026 Magic Quadrant for Observability Platforms. The provided content does not include the report’s evaluation criteria, Gartner’s analysis, or Datadog’s supporting evidence; it primarily contains website navigation and links to Datadog products. ## Gartner Recognition - Datadog highlights its placement as a **Leader** in Gartner’s Magic Quadrant for Observability Platforms. - The announcement links to a downloadable Gartner resource. - No details are provided about Datadog’s position, strengths, weaknesses, or comparison with other vendors. ## Datadog’s Product Portfolio The page navigation presents Datadog as a broad observability and operations platform covering: - **Infrastructure:** infrastructure, container, network, serverless, GPU, storage, and cloud-cost monitoring. - **Applications:** APM, universal service monitoring, continuous profiling, dynamic instrumentation, and agent observability. - **Data and logs:** database, data-streams, quality, jobs, log management, sensitive-data scanning, and observability pipelines. - **Security:** code, cloud, workload, vulnerability, compliance, SIEM, and application/API protection. - **Digital experience:** browser and mobile RUM, session replay, synthetic monitoring, product analytics, experiments, and error tracking. - **Software delivery and service management:** CI visibility, test optimization, internal developer portals, incident response, SLOs, workflow automation, and case management. - **AI capabilities:** AI integrations, GPU monitoring, Bits AI agents, investigation tools, MCP support, and agent observability. ## What the Provided Content Does Not Cover - Gartner’s methodology or assessment criteria - Specific reasons Datadog was named a Leader - Customer feedback, market vision, or execution scores - Technical architecture, pricing, implementation guidance, or product comparisons The material supports the conclusion that Datadog is promoting broad platform coverage and third-party recognition, but the linked Gartner report would be needed for a substantive evaluation.

Kubernetes Datadog Observability Application Performance Monitoring+3

datadogMay 17, 20223 min readCurated summary

Introducing Husky, Datadog's third-generation event store

Datadog built Husky, a new event-storage system, after its original log architecture struggled with multi-tenant reliability, rapid platform growth, and evolving product requirements. The post explains how Datadog moved from metrics-oriented storage to event storage, introduced custom sharding and routing, and eventually recognized the need for a more flexible system. Husky emerged from these lessons about isolation, scalability, and retaining high-cardinality event data. ## From Metrics to Logs - Metrics systems store pre-aggregated tuples such as `<timeseries_id, timestamp, float64>`. - Aggregation makes metrics extremely efficient: millions of events in a second can become one compact datapoint, often requiring less than two bytes with delta-of-delta encoding. - This model is poorly suited to logs because logs must preserve individual events and their full context. - Metrics typically favor long-lived, low-cardinality dimensions such as: - Datacenter - Service - Pod name - Short-lived, high-cardinality fields such as transaction IDs and packet IDs are usually pre-aggregated or omitted. - Logs instead need to support: - Multi-kilobyte events - High-cardinality values such as UUIDs and stack traces - Arbitrary aggregations performed at query time ## Limitations of the Initial Logs System - Datadog’s first Logs architecture initially worked well but became vulnerable in a multi-tenant environment. - A single unhealthy or overloaded node could degrade service for every tenant in the cluster. - Scaling overloaded clusters could worsen the situation because nodes began streaming data to one another while already handling excessive read and write workloads. - Diagnosing and mitigating these cascading failures was difficult. ## Separating Storage from Clustering Datadog’s second architecture retained the same single-node storage engine but moved clustering responsibilities into dedicated services. - Storage nodes no longer knew about one another and behaved like independent one-node clusters. - Failures were isolated to the tenants assigned to a particular shard instead of spreading across the entire cluster. - A Shard Router: - Read events from Kafka - Reorganized them into shard-based Kafka partitions - Dynamically assigned tenants to an appropriate number of shards based on their recent five-minute data volume - Each shard was consumed by two storage-node replicas for redundancy. - A custom query engine tracked tenant-to-shard assignments, queried the relevant replicas, merged partial aggregates, and produced final results. ## Growth of the Event Platform - The new architecture substantially improved reliability and reduced operational burden. - Datadog expanded the platform beyond Logs to support products including: - Network Performance Monitoring - Real User Monitoring - Continuous Profiler - These products generated structured, multi-kilobyte events with storage and indexing requirements similar to logs. - As usage grew, new problems appeared: - A tenant producing a sudden burst of events could degrade query performance for other tenants sharing its shard. - Product teams requested longer retention for important but infrequently queried data, while still requiring it to remain immediately queryable. - The existing architecture was increasingly difficult to adapt to these isolation, scalability, and retention requirements, motivating the development of Husky. Datadog’s progression shows that event storage cannot simply reuse metrics-oriented designs. Systems must preserve event-level context, isolate tenants from one another, and support changing retention and query requirements as products and workloads evolve.

Database Design Datadog Apache Kafka Metrics+4