Techlist.io - Korean Tech Blog Curator

figma2 min readCurated summary

The Power of Play | Figma Blog

Laura Fehre’s experiment creating the Figma-based “Mani Mansion” shows how play can unlock creativity when perfectionism and rigid expectations get in the way. Although she initially rejected structure, she discovered that a flexible design system made experimentation easier and more enjoyable. The project ultimately became less about producing a perfect digital salon and more about creating something delightful and inspiring. ## Finding Inspiration in Everyday Experiences - Fehre drew inspiration from the childhood game *Barbie Nail Designer* and her own nail-salon appointments. - She explored real nail salons to capture their sounds, scents, textures, and ’90s aesthetic. - Sketches of plush seating, neon signs, and glossy counters helped translate the physical experience into an interactive Figma playground. - Her goal shifted from designing for efficiency to creating a space where users could lose track of time. ## When Disorder Needs Structure - Fehre initially made every nail shape unique, hoping to create a wild and unconventional experience. - This approach made layering and combining elements difficult, producing endless duplicates and a frustrating file. - She realized that structure and reusable components were necessary to support creative freedom. - The experience also exposed her insecurity about rusty graphic-design skills and unrealistic expectations. ## Reframing Problems as Play - Collaborating with fellow Designer Advocate Miggi Cardona helped Fehre turn creative frustration into experimentation. - They played with nail shapes and patterns without focusing on whether the results were “useful.” - Fehre recognized that trying to impress others had made failure feel threatening. - Letting go of perfection allowed setbacks to become opportunities for learning, humor, and discovery. ## Designing and Sharing the Final Manicure - Fehre created a mood board combining disco glitter, ’80s Versace influences, bold black clothing, “baddie” energy, and Valentine’s Day hearts. - A systematic set of nail shapes and colors gave her enough consistency to explore combinations freely. - She brought the resulting design to her nail technician as creative inspiration rather than an exact template. - The final manicure demonstrated how digital play can inspire real-world collaboration and expression. The practical lesson is that structure and play are not opposites. Designers can use systems as a foundation, then experiment freely within them—especially when the goal is delight rather than perfection.

Read original(opens in new tab)
discord3 min readCurated summary

Staff Picks, April 2025: All The Adaptations

The April 2025 edition of Discord’s “Staff Picks” highlights video game adaptations across television, film, and anime. Staff members praise adaptations such as *The Last of Us*, *Five Nights at Freddy’s*, and *Cyberpunk: Edgerunners*, while suggesting games like *BioShock*, *Ace Attorney*, and *God of War* for future projects. Their choices emphasize strong storytelling, distinctive worlds, memorable characters, and creative visual adaptation. ## Upcoming Video Game Adaptations - April 2025 features several major releases: - *A Minecraft Movie* on April 4 - Season two of HBO’s *The Last of Us* on April 13 - The *Until Dawn* movie on April 25 - The article uses these releases as a starting point for discussing staff members’ favorite adaptations and dream projects. ## Veronica: *The Last of Us* and *BioShock* - Veronica considers HBO’s *The Last of Us* her favorite adaptation. - The original game’s cinematic presentation made it seem naturally suited to television. - The series exceeded her expectations and expanded the game’s lore. - She specifically praises the emotional impact of the third episode. - She is enthusiastic about the adaptation of the divisive but personally beloved second game. - Her ideal future adaptation is the *BioShock* series. - She wants to see the underwater cities of Rapture from *BioShock* and *BioShock 2*. - She is also interested in seeing Columbia from *BioShock Infinite*. - Although adaptation rumors have circulated, she remains cautiously optimistic. ## Cody: *Five Nights at Freddy’s* and *Ace Attorney* - Cody selects the *Five Nights at Freddy’s* movie despite its relatively mild scares. - He enjoys its predictable jumpscares and accessible PG-13 horror style. - The film’s animatronics are especially effective because they were built as real puppets by Jim Henson’s Creature Shop rather than created entirely with CGI. - He would like the *Apollo Justice: Ace Attorney* trilogy to receive an anime adaptation. - The original *Ace Attorney* trilogy already has an anime series. - The Apollo Justice games feature a more comedic and cartoony cast that could translate well to animation. - After spending more than 100 hours playing the trilogy, Cody also hopes Capcom eventually produces a new mainline entry. ## Emi: *Cyberpunk: Edgerunners* and *God of War* - Emi praises *Cyberpunk: Edgerunners* as a standout adaptation. - The anime quickly builds emotional investment in David, Lucy, and the residents of Night City. - Studio Trigger’s animation and visual effects are so striking that she rewatched individual scenes. - The series’ music, particularly “I Really Want to Stay at Your House,” remains emotionally powerful. - Her dream adaptation is the *God of War* franchise as a television series or film. - The Greek and Norse storylines provide a large narrative scope. - Kratos’s character development, cinematic scenes, and supporting cast give the series strong adaptation potential. - She hopes reported plans for a screen adaptation eventually lead to a release. The staff’s recommendations show that successful game adaptations can preserve a game’s atmosphere while expanding its characters, lore, and visual identity. Viewers looking for game-inspired entertainment can start with *The Last of Us*, *Five Nights at Freddy’s*, or *Cyberpunk: Edgerunners*, while fans can look forward to possible adaptations of *BioShock*, *Ace Attorney*, and *God of War*.

Read original(opens in new tab)
googleOriginal article

A new hybrid platform for quantum simulation of magnetism (opens in new tab)

Google Quantum AI researchers have developed a hybrid quantum simulation platform that combines the flexibility of digital gates with the high-speed entanglement growth of analog dynamics. Using a 69-qubit Sycamore processor, the team demonstrated high-precision simulations of quantum magnetism that are estimated to be over a million years beyond the reach of the world’s fastest supercomputers. This approach allows for the study of complex physical systems before environmental noise can degrade the quantum state. ## The Hybrid Analog-Digital Approach * Digital simulation provides high flexibility by breaking operations into sequential logical gates, but it is relatively slow because qubits only interact in pairs. * Analog simulation activates all qubit couplers in parallel to mimic continuous, real-world dynamics, enabling much faster growth of quantum entanglement. * The hybrid model uses digital gates for initial state preparation and final characterization, while utilizing analog evolution for the core simulation phase. * This combination minimizes the time the system is exposed to noise while maintaining the ability to target specific, complex problems. ## High-Precision Calibration and Benchmarking * The team overcame the "interference" problem of analog simulation—where simultaneous coupler activation creates unpredictable results—by developing a new calibration scheme and precise hardware modeling. * The system achieved a high level of accuracy, with an error rate of only 0.1% each time a quantum excitation moves between qubits. * Benchmarking via random circuit sampling showed the platform can reach chaotic, highly entangled states significantly faster than purely digital methods. * Researchers estimate that reproducing these results with the same accuracy on the Frontier supercomputer would take more than one million years. ## Discovery in Quantum Magnetism * The researchers used the platform to study the XXZ model, a foundational paradigm in quantum magnetism, across a 69-qubit array. * The experiment investigated how quantum systems reach thermal equilibrium, focusing on the Eigenstate Thermalization Hypothesis (ETH). * The simulation revealed a surprising exception to standard physics theories: a specific parameter regime where the system resisted thermalization and remained in a non-equilibrium state. * This finding challenges the "Generalized Gibbs Ensemble," a widely used theory for predicting the behavior of isolated quantum systems. This hybrid platform establishes a new standard for using current-generation quantum hardware to conduct meaningful scientific research. By integrating analog speed with digital control, the approach provides a viable roadmap for exploring many-body physics and finding practical applications in the NISQ (Noisy Intermediate-Scale Quantum) era.

discord2 min readCurated summary

How to Use Discord’s In-Game Overlay to Talk While Playing on PC

Discord’s Windows In-Game Overlay lets players stay connected without alt-tabbing out of their games. It provides access to voice calls, video, chat, screen sharing, streams, notifications, and Activities while playing. The article explains how to use and customize it, plus troubleshooting steps when it does not appear. ## Overlay Features - **Chat Bar:** Provides access to voice and video settings, the soundboard, screen sharing, Activities, and other Discord controls. - **Voice Channel widget:** Shows current call participants and highlights whoever is speaking. - **Video Tiles:** Displays friends’ camera feeds, including Vtuber or PNGtuber models. - **Activity widget:** Shows the game currently associated with your Discord activity status. - **Streams widget:** Displays friends’ live broadcasts so they can be viewed directly in-game. - **Notifications widget:** Shows messages, mentions, and game invites. ## Opening and Customizing the Overlay - Press **Ctrl + `** by default to open the overlay. - Widgets can be repositioned by dragging their dotted borders. - Layouts can be customized to suit different game types, such as FPS or RTS games. ## Streaming Your Game - Click the **screen share** button in the Chat Bar to instantly stream to the current voice channel. - Discord automatically selects suitable streaming quality. - The drop-down menu beside the button allows users to adjust quality and bandwidth usage. ## Watching Friends’ Streams - Streams started in the current voice channel appear in the Overlay’s Streams widget. - Users can click a stream to watch it without leaving the game. - Multiple streams can be viewed directly through the Overlay. - Repositioning the Streams widget changes where broadcasts appear on screen. ## Troubleshooting the Overlay - Confirm that the Overlay is enabled under **User Settings > Overlay**. - Check the per-game settings, since the feature can be disabled for individual games. - Use **windowed** or **borderless windowed** mode; fullscreen games are not supported. - Some games may not be compatible, so test the Overlay with another title if necessary. - The Overlay is available only on **Windows** and does not support macOS or Linux. For Windows players, enabling and customizing the Overlay can make Discord voice chat, streaming, and social interaction available without interrupting gameplay.

Read original(opens in new tab)
discordOriginal article

Make More Closet Space! Nitro Members Can Now Keep Avatar Decoration Quest Rewards for Longer (opens in new tab)

Discord is updating its Quest reward system to provide Nitro members with extended access to earned avatar decorations, which previously expired after a standard two-month window. While all users will continue to receive a minimum of two months of use for any claimed decoration, active Nitro subscribers can now keep many of these rewards for longer, with some even returning from previous Quests. This shift transforms temporary participation rewards into a more permanent benefit for the platform's premium subscriber base. ### Extended Availability for Nitro Subscribers * Most avatar decorations earned through Discord Quests will no longer strictly expire after 60 days for Nitro members. * The specific amount of extra time granted varies between different decorations, with many remaining available as long as a subscription is active. * All Quest participants, including non-subscribers, are still guaranteed the initial two-month period to use their rewards. ### Subscription Requirements and Eligibility * The extension perk is exclusive to full Nitro members; those on Nitro Basic or Nitro Classic plans do not qualify for the extended time. * Users who are not currently Nitro members can subscribe or upgrade their existing plan to immediately regain access to previously collected Quest decorations that have "expired." * Not every decoration is eligible for an extension, as Discord determines availability on an item-by-item basis. ### Management and Returning Content * Discord is retroactively returning several previously available Quest decorations to the collections of eligible users who earned them in the past. * Users can verify the status and expiration date of their items by navigating to Profile Settings > Change Decoration and reviewing the individual item descriptions. * The update is currently live, allowing eligible users to re-equip old rewards or view new expiration timelines immediately. To maximize your collection, check your Profile Settings to see which legacy decorations have returned to your inventory and ensure your Nitro subscription is active to prevent future rewards from expiring.

googleOriginal article

InstructPipe: Generating Visual Blocks pipelines with human instructions and LLMs (opens in new tab)

InstructPipe is a research prototype designed to simplify machine learning prototyping by generating visual programming pipelines directly from natural language instructions. By leveraging a multi-stage large language model (LLM) framework, the system automates the selection and connection of nodes to lower the barrier for novice users. The result is a streamlined workflow that transforms abstract text commands into functional, editable node-graph diagrams within the Visual Blocks for ML environment. ### Pipeline Representation and Efficiency - Visual Blocks pipelines are structured as Directed Acyclic Graphs (DAGs) and are typically stored in a verbose JSON format. - To improve LLM performance, InstructPipe utilizes a "pseudocode" intermediate representation that is highly token-efficient, compressing pipeline data from 2.8k tokens down to approximately 123 tokens. - This pseudocode defines output variables, unique node IDs, and node types while specifying arguments such as input images or text prompts (e.g., `pali_1_out:pali(image=input_image_1, prompt=input_text_1)`). ### Two-Stage LLM Refinement - The **Node Selector** module acts as a high-level filter, using brief node descriptions to identify a relevant subset of tools from the library based on the user's intent. - The **Code Writer** module receives the filtered list and uses detailed node configurations—including specific input/output data types and usage examples—to draft the actual pipeline logic. - This dual-prompting strategy mimics human developer behavior by first scanning documentation categories and then focusing on specific function requirements to ensure accurate node connections. ### Interpretation and Execution - A dedicated **Code Interpreter** parses the generated pseudocode to reconstruct the final JSON-formatted pipeline required by the visual editor. - The system renders the resulting graph in an interactive workspace, allowing users to immediately execute, modify, or extend the machine learning workflow. - Technical evaluations indicate that this approach effectively supports multimodal pipelines, such as those involving the PaLI model for vision-language tasks, while significantly reducing the learning curve for new users. InstructPipe demonstrates how LLMs can bridge the gap between high-level human intent and low-code visual programming environments. For developers and researchers, this approach mitigates the "blank canvas" problem, allowing for faster experimentation and the rapid prototyping of complex machine learning architectures through simple text-based collaboration.

discord3 min readCurated summary

The Game Developer Playbook, Part One: Getting Started on Discord

Discord’s playtest community should be created early in development to build relationships with players, gather feedback, and develop trusted advocates. The article recommends keeping the server focused on testing and feedback, with a clear structure separating information, discussion, staff communication, and playtest voice channels. A simple server template can evolve as the game and community grow. ## Getting Started - New server owners should understand Discord basics, including: - Creating and setting up a server - Managing permissions and roles - Sharing screens - Starting early gives developers more time to nurture a small but valuable group of engaged players. ## Playtest Community Basics - The primary goals should be to: - Make it easy for players to test the game - Give testers clear ways to provide feedback - Keep the community’s scope focused - Developers can begin with Discord’s recommended server template and expand it over time. ## Categories and Server Organization - Organize channels into clear groups: - Read-only information - Two-way discussions - Staff-only communication - Individual voice channels for voice chat, video, and screen sharing - Keep important information—such as rules, announcements, and updates—at the top. - Games with many classes, heroes, kits, or complex mechanics may benefit from dedicated forum or discussion channels. ## Roles and Permissions - Use two primary roles: - `@admin`, later renamed for the studio - `@playtest`, assigned to testers - Studio members should access every channel, while testers should see everything except the admin-only category. - Remove permissions from `@everyone` so unassigned users see an empty server, even if they enter through an unauthorized invite. - Use Discord’s **View Server As** feature to verify what each role can access. ## Community Features - Enabling Discord’s **Community** features can help larger servers manage growth. - Useful options include: - **Announcement Channels** for publishing updates that other servers can follow - **Server Insights** for engagement and retention data once the server reaches 500 members - **Community Onboarding** for self-assigned roles and rule acceptance - These features do not need to be enabled immediately; developers can adopt them as the community expands. ## Channel Design - Every channel should have a clearly defined purpose and a descriptive name. - Read-only channels should use consistent formatting, emojis, and Markdown to make important information easy to scan. - Suggested channels include: - `#rules-and-info` for server rules and guidelines - `#announcements` for game and playtest news - `#patch-notes` for updates and release details - `#game-discussion` for broader conversation A successful game playtest server should start small, organized, and purpose-driven. Establish clear permissions, separate information from discussion, and add features or channels only when they support the testing process and the community’s growth.

Read original(opens in new tab)
figma3 min readCurated summary

Version Control: How a UX Writer Weighs One Word Against Another | Figma Blog

A UX writer explains how a seemingly simple menu label for Figma’s offline prototyping feature revealed deeper questions about user expectations and product behavior. The team tested technically accurate, goal-oriented, and action-focused wording, but each option created confusion about what would happen after clicking. The central lesson is that UX copy must connect users’ intentions with the system’s actual behavior. ## The Challenge: Explaining Offline Prototyping - Users wanted a way to present prototypes reliably without an internet connection. - Engineers built an initial version that loaded prototype content in advance. - The remaining challenge was finding a few words that accurately explained the feature without requiring technical knowledge. - The writer argues that language exposes underlying product assumptions: choosing a verb forces the team to clarify what the system is really doing. ## Version One: “Preload Prototype” - “Preload prototype” accurately described the technical behavior: - Prototypes normally load screen by screen. - The feature gathers the necessary content upfront and retains it for later presentation. - However, “preload” implies that loading happens before the prototype appears, like “preheating” an oven. - Users had already loaded the prototype, so the prefix “pre-” did not match their experience. - Alternatives such as: - “Load full prototype” - “Load all screens” - “Load all assets” - These labels created a trust problem: users might reasonably assume that a prototype shown on screen was already fully loaded. - The wording needed to communicate that the initial load was incomplete without making the product seem unreliable. ## Version Two: Focusing on the User’s Goal - The team shifted from describing the technical process to describing the intended outcome: - “Present prototype offline” - “Prepare to present offline” - These phrases connected more directly to the user’s motivation: presenting without an internet connection. - However, “Present prototype offline” suggested that clicking the option would immediately begin presenting, even though it only prepared the prototype. - “Prepare to present offline” was more accurate but ambiguous: - Users would not know what preparation involved. - They would not know how far in advance to select it. - Both options might have worked within a larger workflow with explicit preparation steps, but they felt too imposing and unclear for a simple toggle menu. ## Language as an Interface to Computing - UX writing treats menu labels as actions or intentions: - Imperatives tell the program what to do. - Phrases can also express what the user wants to accomplish. - Terry Winograd’s principle that “people act through language” captures the problem: words connect a user’s mental model to a computer’s behavior. - When the wording, user intention, and system result are out of alignment, the interaction becomes confusing. - The article’s third iteration begins by examining what users can actually control, but the provided text ends before that approach is explained.

Read original(opens in new tab)
discord3 min readCurated summary

The Game Developer Playbook, Part Two: Early Access and Pre-Launch

The post explains how game developers should evolve a Discord server from a private playtest space into a public pre-launch or Early Access community. Its central advice is to define what members should do, create focused spaces for conversation and feedback, and measure meaningful engagement rather than member count alone. The server should remain flexible as the game and community develop. ## Defining the Community’s Purpose - Decide what you want members to do when they visit the server. - Successful communities typically: - Encourage open discussions about trailers, updates, and development decisions. - Build a network of ambassadors and super fans. - Host activities for both small and large groups. - Gather feedback through announcement threads rather than one-way posts. - Help players find others for multiplayer sessions, strategy discussions, and team play. - Members may join for news, feedback opportunities, social connections, or organized events, so the server should support these different needs. ## Designing the Server Structure - Starting early helps developers understand how the community evolves. - A server focused on one game is usually easier to navigate than one covering multiple games or franchises. - Developers moving from a private playtest to a public community may benefit from creating a new server and rewarding playtesters with VIP roles. - The layout should remain experimental and adaptable. ### Categories and Channels - Categories can organize discussions as the community grows, including dedicated support areas. - Every channel should have a clear purpose. - Start with a small number of channels and expand only when necessary. - Use categories and emojis to make channels easier to recognize. ### Roles and Permissions - Administrators should handle major server-wide changes. - Staff roles can provide lighter permissions and access to private operational areas. - Moderators need only the permissions required to enforce rules and manage conversations. - It is easier to add roles and channels later than to remove permissions or undo an overly complex setup. ## Measuring Engagement - A large membership count does not necessarily indicate a successful community. - Discord should function as an ongoing conversation, not merely a broadcast channel. - More useful metrics include: - **Activation and engagement:** Whether new members explore channels or send a message on their first day. - **Communication:** How many members participate in text or voice conversations, measured daily, weekly, or monthly. - **Retention:** Whether new members return and participate again the following week. - Community servers can use Discord’s Server Insights to monitor these measures and other activity data. The practical recommendation is to keep the server focused, lean, and community-oriented. Developers should prioritize meaningful participation, feedback, and member retention while adjusting the server structure as the game and audience grow.

Read original(opens in new tab)
googleOriginal article

Teaching machines the language of biology: Scaling large language models for next-generation single-cell analysis (opens in new tab)

Cell2Sentence-Scale (C2S-Scale) is a new family of open-source large language models designed to transform complex single-cell transcriptomic data into a text-based format accessible to natural language processing. By representing gene expression profiles as "cell sentences," the framework allows researchers to use general-purpose LLM architectures to "read" and "write" biological information. This approach simplifies single-cell analysis, enabling conversational queries and automated data interpretation that were previously limited to specialized tools and expert users. ### The Cell2Sentence Mapping Method * Translates single-cell RNA sequencing (scRNA-seq) measurements into sequences of text by ordering gene names according to their expression levels. * Enables the integration of cellular data with text-based biological context, such as cell types, experimental metadata, and scientific literature. * Leverages the existing vocabulary of biology—gene names and functions—to make high-dimensional data interpretable by standard language model tokenizers. ### C2S-Scale Model Architecture and Training * Built upon Google’s Gemma open model family, maintaining the original architecture to benefit from existing scalability and infrastructure. * Trained on a dataset exceeding 1 billion tokens derived from real-world transcriptomic data and biological metadata. * Features a range of model sizes from 410 million to 27 billion parameters, allowing researchers to choose between computational efficiency for exploratory work and high performance for complex tasks. ### Functional Applications in Biology * **Conversational Querying:** Researchers can interact with data through natural language to ask specific questions, such as predicting how a T cell might respond to a particular cancer therapy. * **Automated Interpretation:** The models can generate biological summaries of experiments, describing everything from individual cell types to the characteristics of entire tissues. * **Predictive Tasks:** The framework handles diverse tasks including cell type annotation and the generation of synthetic cells or tissues for research simulations. ### Performance and Biological Scaling Laws * Research demonstrates that biological language models follow predictable scaling laws, where performance in tasks like cell type annotation improves as model size increases. * Larger models show superior gene overlap and semantic similarity scores when interpreting datasets compared to smaller versions. * Smaller models remain highly effective for parameter-efficient fine-tuning in resource-constrained environments. C2S-Scale is available as an open-source resource on GitHub and HuggingFace, offering a flexible toolkit for the research community to apply large language models to next-generation genomic discovery.

figma3 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.

Read original(opens in new tab)
figma2 min readCurated summary

Figma has confidentially submitted a draft S-1 with the SEC | Figma Blog

Figma announced on April 15, 2025, that it had confidentially submitted a draft S-1 registration statement to the U.S. Securities and Exchange Commission. The filing gives the company the option to pursue an initial public offering, but the IPO remains conditional on SEC review and further decisions by Figma. ## Confidential S-1 Submission - Figma submitted a draft Registration Statement on Form S-1 to the SEC. - The filing concerns a potential offering of Figma’s Class A common stock. - Because the submission is confidential, Figma has not yet committed to completing an IPO. - The announcement was made under Rule 135 of the Securities Act of 1933. ## No Offering Details Yet - Figma has not determined: - The number of shares that might be offered - The potential price range - The timing of a public offering - Any future sale or solicitation of securities would occur only after the SEC completes its review and applicable registration requirements are satisfied. - The announcement itself is not an offer to sell securities or a solicitation to buy them. Figma’s announcement signals that it is preparing for a possible transition to public ownership while emphasizing that the process is preliminary. Investors will need to wait for later filings and SEC review before receiving financial details or confirmation of an IPO.

Read original(opens in new tab)
figma2 min readCurated summary

Figma Localizes Product and Support for Korean Market | Figma Blog

Figma is launching an open beta of its fully localized Korean product and support experience on April 16. The rollout responds to strong adoption in South Korea and aims to remove language barriers across design, development, and collaboration. It is Figma’s third product localization, following Japanese and Spanish, with more languages expected this year. ## Korean Market Expansion - The localization includes: - A complete Korean product translation - Culturally adapted user interfaces - Dedicated Korean-language customer support - South Korea already has a significant Figma user base: - Nearly one-third of KOSPI 200 companies use Figma. - More than four million files were created in the country over the past year. - More than 75,000 files are edited daily. - The Seoul Friends of Figma community has over 1,000 active members. - Customers include Gangnam Unni, Daangn, KakaoBank, and Woowa Brothers. ## Benefits for Customers - KakaoBank reports a 30% increase in employee productivity attributed to Figma. - Its design team expects full Korean support to speed up critical projects by eliminating the need to work across two languages. - Woowa Brothers says Korean-language access will lower barriers and bring more people into the product development process. - Figma emphasizes that localization benefits both designers and non-designers, including developers. ## Supporting the Full Product Development Process Figma’s localization arrives alongside an expanding product ecosystem: - **FigJam**, launched in 2021, supports brainstorming, meetings, and collaborative work. - **Dev Mode**, launched in 2023, helps teams turn designs into coded products. - **Figma Slides**, launched in 2024, brings Figma’s design and collaboration features to presentations. - New AI-powered features help users develop and refine ideas. ## Global Context and Rollout - About 85% of Figma’s monthly active users are outside the United States. - Non-U.S. markets generated approximately 50% of revenue at the end of 2024. - Nearly two-thirds of users work outside traditional design roles, and about 30% identify as developers. - The Korean version will roll out gradually in open beta beginning April 16. - Figma will also showcase new products and features at Config in San Francisco on May 6–8 and London on May 14. Figma’s Korean localization is intended to make collaborative product development faster and more inclusive by allowing teams to work entirely in their native language.

Read original(opens in new tab)
figma2 min readCurated summary

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

“Skill share,” Figma’s April 2025 issue, gathers practical lessons for designers, developers, and product builders ahead of Config 2025. Its central argument is that strong products depend not only on speed or technical execution, but also on craft, communication, storytelling, experimentation, and long-term thinking. The issue encourages readers to keep learning across disciplines and apply these skills collaboratively. ## Craft as a Competitive Advantage - Linear CEO Karri Saarinen shares ten principles for creating products that stand out. - The advice reflects a shift away from “move fast and break things” toward deliberate quality and attention to detail. - Craft is presented as an organizational value that should influence every level of product development. ## Better Designer–Developer Handoff - Successful handoff depends on collaboration rather than simply transferring designs to engineering. - Figma’s guide focuses on three principles: - Encourage curiosity between designers and developers. - Keep communication open throughout the build process. - Establish a shared understanding of what “good” means. - The goal is to reduce friction, clarify expectations, and preserve design intent during implementation. ## Writing and Storytelling for Product Builders - Clear writing helps teams explain technical architecture, new features, product roadmaps, and broader visions. - Storytelling is not limited to writers or marketers; people in every product role benefit from articulating ideas effectively. - Strong communication can make complex concepts easier to understand and build support for new directions. ## Building for the Long Term - In a period of rapidly advancing AI tools, product teams must focus on making things work well—not merely making them work. - Dylan Field and Garry Tan discuss experimentation, play, and exploring an “idea maze” as essential parts of product development. - They also address vibe coding, AI-assisted creation, and the importance of preserving human craft even as AI models become more capable. - Founders are encouraged to remain deeply focused on quality and to develop products with lasting value. ## Broader Exploration - The issue also includes a “Rabbit hole” section featuring additional visual and editorial explorations. - Together, the featured topics present skill development as an ongoing process spanning design, engineering, communication, and strategy. The practical takeaway is to treat craft and collaboration as core product skills. Teams can improve their work by communicating clearly, aligning early, experimenting freely, and maintaining high standards even when new tools make development faster.

Read original(opens in new tab)
slack3 min readCurated summary

Optimizing Our E2E Pipeline

Slack optimized its monorepo E2E pipeline by avoiding frontend rebuilds when a pull request contains no frontend changes. Using `git diff` to detect relevant changes and serving recent frontend artifacts from S3 through an internal CDN, the team reduced build frequency by 60% and cut end-to-end pipeline time from roughly 10 minutes to 2 minutes. The changes also lowered storage and compute costs and improved test reliability. ## The Cost of Unnecessary Frontend Builds - Slack’s E2E pipeline validates frontend, backend, database, and service changes before merging into `main`. - Previously, every run rebuilt the frontend, even when a pull request changed only backend or unrelated files. - A typical pipeline included: - About 5 minutes for the frontend build - Deployment to QA - More than 200 E2E tests taking another 5 minutes - With hundreds of pull requests merged daily, redundant builds caused: - Thousands of unnecessary builds each week - Nearly a gigabyte of S3 data per build - Terabytes of duplicate stored artifacts - Significant developer and cloud-compute costs ## Conditional Frontend Builds - Slack used `git diff` with three-dot notation to compare the checked-out branch against `main`. - If frontend files had changed, the pipeline ran a new frontend build. - If no frontend changes were detected, the build step was skipped. - Git analyzed the repository’s more than 100,000 tracked files in only a few seconds. ## Reusing Prebuilt Assets - When a new build was unnecessary, the pipeline located a recent frontend build already stored in AWS S3. - The selected artifact was still in production, ensuring the E2E tests used sufficiently current frontend assets. - An internal CDN served those assets to the QA environment. - S3 naming and asset-management conventions made it possible to find an appropriate artifact in under three seconds on average. ## Results and Additional Benefits - Frontend build frequency fell by 60%. - Average E2E pipeline time dropped from about 10 minutes to 2 minutes. - Monthly savings included hundreds of hours of compute and developer waiting time. - S3 usage decreased by several terabytes per month. - Test flakiness reached its lowest measured level, partly because asset delivery became more consistent. - The work also exposed legacy systems and generated a backlog of future maintenance improvements. Slack’s experience demonstrates that pipelines should not automatically repeat expensive steps when their inputs have not changed. Detecting affected files and reusing trustworthy build artifacts can substantially improve speed, reliability, and cost without requiring a wholesale rewrite of the CI/CD system.

Read original(opens in new tab)