techlist.io
KREN

API

31 posts

cloudflare3 min readCurated summary

See risk, fix risk: introducing Remediation in Cloudflare CASB

Cloudflare CASB now lets customers remediate risky SaaS file-sharing directly from the Cloudflare One dashboard, rather than merely identifying problems. The initial release targets Microsoft 365 and Google Workspace, removing public, organization-wide, or external sharing without deleting files or changing ownership. Cloudflare concludes that durable, workflow-based execution makes remediation scalable, observable, and easier to operate. ## CASB as a Centralized SaaS Risk View - CASB connects to services including Microsoft 365, Google Workspace, Slack, Salesforce, Box, GitHub, Jira, and Confluence through APIs. - It provides: - A consolidated view of misconfigurations, overshared files, and risky access. - Continuous scanning as users collaborate and adopt new tools. - Searchable and exportable findings for triage and reporting. - Previously, fixing findings required using each application’s admin interface or submitting tickets to application owners. ## File-Sharing Remediation - The new **Remove sharing** action can address: - Public links that allow anyone to view or edit files. - Company-wide sharing when only a few users need access. - Sharing with external domains or personal accounts. - Any of these risks involving files that match a DLP profile, such as customer records, credentials, or financial data. - Remediation removes the risky sharing configuration only: - Files are not deleted. - Ownership is not changed. - Progress and outcomes are tracked in CASB, while actions are recorded in Cloudflare One Admin logs and can be exported to a SIEM. ## Microsoft 365 and Google Workspace - The initial integrations focus on business-critical documents stored in: - OneDrive and SharePoint. - Google Drive, including Docs, Sheets, and Slides. - Common examples include temporary public editing links, company-wide documents forgotten after an event, and sensitive spreadsheets shared with contractors’ personal accounts. - Teams can now resolve findings directly in CASB instead of exporting CSVs and relying on application owners to make changes. ## Durable Remediation Architecture - Cloudflare designed the system for speed, resilience, and ease of use using: - Workers - Workflows - Queues - Workers KV - Secrets Store - Hyperdrive - The process is: - An API call sends a remediation job to a Worker. - The Worker places it on a Queue. - A second Worker starts a Workflow. - Credentials are securely provided through Workers KV and Secrets Store. - The Workflow gathers information and calls third-party APIs. - Hyperdrive records the final result. - Workflows’ native retries handle vendor API rate limits such as HTTP 429 responses, while built-in step logging shows retry activity. - Load testing and early customer usage produced a median completion time of 48 seconds and a p90 of 72 seconds. ## Planned Expansion - Cloudflare plans to add: - Quarantine actions that move or isolate high-risk files. - Custom Webhooks for ticketing, chat notifications, and external automation. - Carefully scoped autoremediation policies. - Custom CASB findings based on organization-specific patterns, data types, or access conditions. Organizations using Microsoft 365 or Google Workspace can use CASB Remediation to turn detected sharing risks into tracked, auditable fixes. The planned quarantine, webhook, and automated-policy features could further position CASB as an active security control plane rather than a passive reporting tool.

Read original(opens in new tab)
APIDatabase DesignCloudflareSaas+4
kakao2 min readCurated summary

Introducing the new Kanana-o

Kanana-o is Kakao’s new Korean-focused omni-modal AI model, designed to understand and generate text, images, and audio naturally. Kakao is opening a closed beta for the Kanana-1.5-o-9.8b-2602 model to gather feedback from developers and partners before commercial release. The service emphasizes practical experimentation rather than large-scale traffic handling. ## Model Capabilities - Supports simultaneous processing of multiple modalities, including text, images, and audio. - Specializes in: - Deep understanding of Korean language, culture, and user intent. - Natural Korean speech with expressive intonation, pacing, and emotion. - Flexible applications such as podcast narration, multi-turn conversations, and multi-speaker text-to-speech. - Balances text-generation speed with audio-processing speed to produce more natural spoken responses. ## API Beta Service - **Service:** Kanana-o API Beta - **Model:** Kanana-1.5-o-9.8b-2602 - **Beta period:** February 27–May 27, 2026 - **Access:** Selected testers receive a fixed number of daily API uses during the beta. - The closed beta is intended for meaningful developer testing and feedback, not high-volume production workloads. ## Application and Selection - Applicants should visit [omni.kanana.ai](https://omni.kanana.ai/), sign in with a Kakao account, and submit information about: - Their organization or affiliation - Intended purpose - Expected technical scenarios - Selected applicants will receive invitations and API documentation through KakaoTalk notifications starting February 27. - Kakao is seeking developers, students, startups, and researchers with concrete implementation plans. - Specific proposals—such as building a visual shopping assistant for people with visual impairments—are favored over general interest in trying AI. Developers interested in exploring Korean-language, audio, and vision applications can apply for the beta with a clearly defined use case and prototype plan.

Read original(opens in new tab)
APIAIKanana OText To Speech+1
figma2 min readCurated summary

How eBay Built a Bridge Between Brand and Product with Figma | Figma Blog

eBay rebuilt its design-system documentation to unite brand, product, accessibility, and engineering guidance in one evolving experience. Its new Evo system is centered on the 300-plus-page Playbook, which replaces scattered, manually maintained files with a centralized source of truth. By making Figma the starting point for content and automating validation and publishing, eBay reduced documentation updates from days to minutes and encouraged teams to treat documentation as part of their normal workflow. ## Rebuilding from the Ground Up - Before Evo, documentation was spread across separate Figma files, developer resources, and accessibility guidelines. - Designers manually updated static files and submitted tickets for changes to be published. - eBay’s OneExperience team chose to rebuild the process internally rather than patch the old system or rely on an external agency. - The goal was a system integrated with everyday design and development work, rather than documentation maintained as a separate task. ## Bringing Brand and Product Together - The new Playbook combines brand guidance, design-system documentation, technology resources, and accessibility information in one destination. - It acts as a centralized source of truth for both internal teams and agency partners. - Component pages include design, development, and accessibility views. - Component availability and implementation status are updated from library metadata instead of manually maintained tables. ## Component Status Across Platforms - eBay created an internal Component Status API to track components across its libraries. - The API records component names, versions, availability, and implementation status across: - Published Figma libraries - Native platform libraries - Open-source web-component libraries - Figma components store relevant metadata in their descriptions. - Developers can verify whether a component exists in their framework, whether it matches the Figma version, and whether the Playbook documentation is current. ## Automating Documentation Updates - eBay built a custom Figma plugin and exporter that powers the documentation workflow. - Components, guidelines, and accessibility notes originate in Figma. - Updates are linted, validated, and published directly from Figma without manual CMS work. - Changes that previously took days can now appear on the Playbook site in under two minutes. - Faster publishing makes documentation easier to iterate on and helps teams view it as a living part of their workflow rather than an administrative burden.

Read original(opens in new tab)
APIFigmaDesign SystemsAccessibility+3
discord2 min readCurated summary

Discord Update: December 19, 2024 Changelog

Discord’s December 19, 2024 changelog recaps the year’s most useful performance and reliability improvements through a festive poem. The updates focused on making mobile apps more stable and responsive, speeding up servers, GIFs, chat, and APIs, and improving image quality and storage usage. Discord concludes by encouraging users to join voice, play games, or Go Live, while promoting Nitro gifting. ## Mobile Stability and Performance - iOS crash fixes reduced the overall crash rate by **84%**. - Android’s chat renderer reduced slow frames by up to **60%** and lowered chat-list memory usage by about **12%**. - The Android Expression Picker—covering emojis, GIFs, and stickers—saw up to **50% fewer dropped frames** and approximately **7.5% lower memory usage**. - Foldable-device support and multitasking were significantly improved. - Mobile server lists were virtualized so only visible servers remain loaded, improving scrolling performance. - Server switching on Android and iOS became more than **30% faster**. - Mobile GIF Picker loading times improved by up to **80%**. ## Backend and Media Improvements - Infrastructure changes, including moving to Google Cloud C3 instances and removing an Nginx layer, reduced p90+ API latency by roughly **25%**. - Discord’s media proxy now preserves ICC color-profile data when resizing images into WebP, improving color accuracy across platforms. - iOS data-storage changes reduced disk usage substantially; the most affected 1% of users went from approximately **5.7 GB to 1.7 GB**, with some users recovering up to **4 GB**. ## Seasonal Extras - The recap is presented as a “Fixmas” poem summarizing fixes from Discord’s 2024 Patch Notes. - Users who gift Nitro during the promotion also receive an Avatar Decoration. Together, these changes show Discord’s emphasis on incremental improvements that make everyday communication faster, more reliable, and less demanding on mobile devices.

Read original(opens in new tab)
APIAndroidiOSPerformance Optimization+4
figma3 min readCurated summary

Double click: Human Takes on Agentic AI | Figma Blog

Agentic AI could fundamentally change UX by handling tasks across apps with minimal supervision, reducing the need for users to navigate complex interfaces. Supporters see agents as a new abstraction layer that lets people focus on goals rather than buttons, menus, and tabs. However, the shift also raises concerns about designing for machines at the expense of human creativity, agency, and meaningful interaction. ## The Promise of Agentic AI - Agents can take routine work off users’ plates, such as paying bills or completing multistep tasks. - Perplexity’s Henry Modisett argues that AI should be “how something works,” not necessarily what users directly interact with. - The ideal experience resembles starting a car: users specify where they want to go without needing to understand the machinery underneath. - Agentic systems may reduce the cognitive load associated with chatbots, personalities, and complicated interfaces. ## Agents as a New Web Abstraction - Agents could operate across platforms, creating a more interoperable web that works more like human workflows. - They may reduce the need to navigate menus, manage open tabs, or repeatedly switch between applications. - Rather than one all-purpose AI, the future may involve specialized agents collaborating like a team. - This could shift users’ attention from browsing and operating software toward creating, connecting, and pursuing goals. ## Designing Websites for Machines - Maintaining and optimizing websites for AI agents could become a distinct industry. - Websites may increasingly prioritize: - Clean APIs - Machine-readable content - Clear structure - Streamlined navigation - Visual polish, animations, and pixel-perfect layouts may matter less to agents than accessibility and functional interoperability. - Designers and developers must consider whether they are primarily building for humans, machines, or both. ## Preserving Human Creativity - Optimizing exclusively for AI could flatten the web and remove creativity, depth, and intentional visual experiences. - The growth of agentic systems arrives alongside renewed interest in: - Creative coding - Handcrafted websites - Experiences that move beyond templates - The industry has an opportunity to decide which tedious work to automate while preserving the aspects of the web that feel expressive and distinctly human. ## The Value of Friction and User Control - Traditional UX often treats friction as something to eliminate, but autonomous agents complicate that principle. - Users need deliberate moments to: - Review an agent’s proposed action - Approve consequential changes - Correct mistakes - Stay aware of what the system is doing - Carefully reintroduced friction can preserve agency and trust, even when the agent performs most of the work. - Good agentic design may therefore prioritize appropriate checkpoints over completely invisible automation. Agentic AI is still in its early stages, but it is likely to reshape both web infrastructure and interface design. The strongest approach is to automate complexity while preserving human oversight, creativity, and opportunities for meaningful participation.

Read original(opens in new tab)
APIAI AgentsUser ExperienceCreative Coding+3
figma2 min readCurated summary

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

Figma’s “Find your framework” newsletter highlights ideas and resources from its virtual Framework design systems event. It emphasizes that successful design systems require more than reusable components: teams must connect design to code, market the system internally, teach its fundamentals, and use it to support growth. The post points readers toward Framework announcements, expert discussions, and practical case studies. ## Framework Event Highlights - Framework brought together design systems practitioners and product builders to discuss current challenges and practices. - Figma announced: - **Code Connect**, which links design-system components in Figma to their code implementations. - **Typography and gradient variables** for more flexible, consistent design foundations. - **Library Analytics API** to help organizations measure and improve design-system adoption. - The event also included roundtables and expert Q&As. ## Treating a Design System Like a Product - Design systems become valuable only when teams actually use them. - Adoption requires product thinking, including: - Understanding internal users and their needs. - Communicating the system’s benefits clearly. - Building an internal marketing and adoption strategy. - The goal is to make the design system an indispensable part of the company’s toolkit, not merely a library maintained by a specialized team. ## Design Systems 101 - Figma’s introductory series is aimed at teams beginning their design-system journey. - The guides explain: - What a design system is. - How design systems work. - How they can change design workflows. - How to build one from the ground up. ## Using Design Systems to Fuel Growth - Carvana’s case study shows how a design system can support rapid business and product expansion. - The company used its design system and variables to: - Maintain consistency while responding to sharply increased customer demand. - Scale design across its e-commerce product. - Keep visual details synchronized throughout periods of change. Figma’s overall recommendation is to combine strong system foundations with adoption efforts, developer integration, education, and measurement so the design system can scale with the organization.

Read original(opens in new tab)
APIFigmaDesign SystemsDesign Tokens+2
figma2 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.

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

Behind the build: a Q&A with developer Gavin McFarland | Figma Blog

Gavin McFarland, a freelance design consultant and developer, discusses building a FigJam table widget after first creating a popular Figma table plugin. The widget lets users manage tabular data without leaving FigJam, supporting columns, rows, data import, and sorting. His experimentation with the widget API evolved into broader questions about multiplayer collaboration, performance, and productivity. ## Gavin’s Path to Plugin Development - McFarland began by designing and building websites for friends and family. - As a freelance consultant focused on user-centered digital transformation, he regularly pushes himself to learn new tools. - After seeing someone ask for an easier way to create tables in Figma, he modified the Rectangle Creator example into his first plugin, **Table Creator**. - The plugin eventually gained tens of thousands of users. ## Building a Table Widget for FigJam - McFarland created a FigJam table widget for users who need to display and manage structured data during collaborative work. - The widget supports: - Adding rows and columns - Importing data - Sorting by columns - The goal is to keep users inside FigJam rather than requiring a separate tabular-data application. ## Learning the Widget API - He began with the FigJam notepad example and made incremental modifications to understand the API. - The project required learning JSX, which he had not previously used extensively. - After understanding the basics, he experimented with rendering rows, columns, and different visual designs. ## Collaboration and Multiplayer Challenges - What started as an API exercise became an exploration of how teams could work more effectively together. - McFarland considered: - How simultaneous editing should work when multiple people modify one table - How the interface could show that another collaborator is active - How to keep large datasets responsive during multiplayer interactions - These challenges appealed to him because they combine visual design with technical problem-solving. ## Finding Ideas Through the Community - McFarland looks for problems designers encounter in their everyday workflows. - He draws inspiration from the Friends of Figma Slack community and the broader developer community. - Conversations with other plugin creators help him exchange ideas and improve his own work. ## Focus on Practical Productivity - He hopes the widget helps people work more productively and collaborate more closely. - His broader motivation is creating tools that address real, everyday problems. - The article ends as he begins discussing another plugin, **Node Decoder**, so the remainder of that project description is not included.

Read original(opens in new tab)
APIFigmaFigjamReal Time Collaboration+3
figma2 min readCurated summary

Behind the build: a Q&A with developer Tru Narla | Figma Blog

The post profiles Tru Narla, a software engineer and creator of FigJam’s Soundboard widget. Her project adds playful audio interactions to FigJam boards and demonstrates how accessible the widget platform can be for developers. Despite API limitations, documentation, experimentation, community support, and livestreaming helped her turn a side-project idea into a published product. ## Soundboard for FigJam - Soundboard lets users add fun sounds to FigJam boards. - Tru initially wanted to support user-recorded audio and preset sounds, but widget limitations prevented audio recording. - The idea came from wanting to create an interactive experience focused specifically on sound. ## Building the Widget - Tru began by reading the documentation and studying demo projects. - Much of the development involved trial and error and reducing the project’s scope to fit the available APIs. - A private Slack community for widget developers helped her share code, troubleshoot bugs, and stay motivated. - She found widget development easier and more enjoyable than expected. ## Inspiration and Motivation - Tru draws ideas from Twitter and everyday experiences. - She records potential project ideas and prefers building tools she would personally use. - Publishing a finished project was a major motivation after repeatedly starting—but not completing—side projects. - Streaming the development process on Twitch provided additional accountability and encouragement. ## Future Projects and Platform Potential - Her next project is an interactive piano with clickable keys and keyboard shortcuts mapped to different notes. - She is also considering multiplayer games, though they require more planning and development time. - Tru is excited by FigJam’s growing ecosystem of plugins and widgets and the possibilities still open to developers. - She particularly likes the new code embed feature and imagines using it for tutorials, system design, and code explanations. - She would also like to see running code displayed in a sandbox within FigJam. Tru’s experience suggests that developers can begin with a small, playful idea, use the available documentation and community resources, and gradually expand their ambitions as the FigJam platform evolves.

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

Bringing the power of our open platform to FigJam | Figma Blog

Figma is extending its open plugin platform to FigJam, allowing builders to create plugins and interactive widgets. Plugins automate individual workflows, while widgets support collaborative experiences such as polls, voting, and games. The APIs are designed to be approachable for developers familiar with JavaScript, HTML, or React. ## An Open Platform for FigJam - Figma’s original plugin API aimed to make customization accessible: anyone who can build a website should be able to build a plugin. - FigJam extends this philosophy while emphasizing collaboration and shared interaction. - Plugins can connect workflows, import real data, and automate repetitive design or brainstorming tasks. ## Interactive Widgets for Collaboration - Widgets can be dragged directly onto FigJam boards and used by multiple participants. - Potential uses include: - Voting and polls - Games - Interactive team activities - The widget API is declarative and functional. - Developers define interfaces with components such as `Frame`, `Rectangle`, `Text`, and `SVG`. - Event listeners can execute code in response to actions such as clicks. - Widgets can include inline property menus similar to native FigJam objects. - Synced state allows interactions, such as a counter, to remain consistent for everyone in the file. - The API is modeled after React, with components whose properties resemble CSS, reducing the learning curve for React developers. ## Plugins for Workflow Automation - Plugins are intended to reduce repetitive work and help teams focus on collaboration. - Examples include converting CSV data into sticky-note grids or creating sticky notes from text. ### Organization and Synthesis - Sort sticky notes by color. - Add tags for categorization. - Extract themes with tools such as word clouds. - Count votes using stamp counters. ### Task Automation - Add features such as spell checking and find-and-replace. - Generate large groups of objects automatically, such as 100 colored sticky notes. - Existing Figma plugins, including SPELLL, can be republished for FigJam. ### Content Libraries - Import icons, emojis, logos, and other reusable assets. - Planned integrations include Icons8, Material Design icons, Iconify, and Brandfetch. ### Customization - Plugins can help users apply custom colors, fonts, and text styles, addressing requests for more personalization in FigJam. FigJam’s open platform combines workflow automation with collaborative interactivity, giving developers a straightforward way to build tools that make brainstorming more efficient and engaging.

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

How to get closer with your developer | Figma Blog

Bringing engineers into product design early helps teams uncover technical constraints, explore better solutions, and move faster. Rather than waiting until designs are polished, designers should use early, exploratory collaboration to expose assumptions and edge cases. The post recommends partnering closely with one engineer through ideation using straw man mocks, brainstorming, and clearly defined questions. ## Technical Knowledge Improves Ideation - Engineers can identify technical constraints and unexpected edge cases early. - This input helps designers avoid solutions that seem promising but are difficult or costly to build. - Early collaboration does not eliminate creativity; it makes ideas more thoughtful and grounded. - Sharing unfinished work can be more productive than protecting designs until they appear complete. ## Establish a Close Engineering Partnership - For Coda’s Packs Tables feature, Helena Jaramillo worked closely with one engineering partner, Gil. - Packs Tables connected services such as Spotify, Google Calendar, and Gmail to Coda documents. - Because the feature had to work across multiple APIs, close engineering collaboration was essential. - The broader team was involved, but having a consistent partner enabled faster brainstorming and continuous feedback. ## Start with Straw Man Mocks - Straw man mocks are quick, rough visual proposals intended to generate discussion rather than finalize a design. - They should: - Be fast to create, since early assumptions are often incorrect. - Ask more questions than they answer. - Present multiple directions instead of prematurely narrowing to one solution. - Designers should first imagine how the feature might work if it were easy, then test those assumptions with an engineer. - Useful questions include: - What assumptions or misconceptions are we making? - What are we overlooking? - Which directions are interesting? - Which directions are technically difficult, and what trade-offs would they involve? ## Brainstorm Through Visualization - Early brainstorming should involve both designers and engineers, not just a finished design review. - Teams can use wireframing kits, high-fidelity components, paper sketches, iPads, or screen sharing. - During Packs Tables, Helena and Gil used whiteboarding to explore UI ideas and clarify potential problems. - The goal at this stage is alignment and exploration—not polished interface design. ## Define Key Questions - Key questions act as principles for making later decisions. - They help teams address foundational issues before debating individual solutions. - Answering questions about constraints, resources, priorities, and desired outcomes makes detailed decisions easier. - Helena and Gil recorded their key questions in a Coda document and reviewed them with the engineers involved in the project. Designers should treat engineers as creative partners from the beginning of a project. Rough mocks, shared brainstorming, and agreed-upon guiding questions create a faster path to feasible, thoughtful solutions.

Read original(opens in new tab)
APIProduct DesignCollaborationWireframing+2
figma2 min readCurated summary

Looking to improve your Figma workflow? Check out our updated user forum | Figma Blog

Figma relaunched its online forum to help designers learn from one another on subjective, workflow-specific topics that traditional support articles cannot fully address. The updated community introduces clearer channels, new programming such as AMAs and livestreams, and revised guidelines. Bug reports and feature requests are being moved to Figma’s support platform for more focused, private follow-up. ## A More Focused Community Structure - New and renamed channels organize discussions around specific areas of design practice. - The **Design Systems** channel supports conversations about libraries, best practices, and team processes. - Additional channels cover **Prototyping**, **API and Extensions**, and **Workflow and Process**. - **Open Design** lets users share work, request feedback, and find collaborators. - A **Start Here** channel explains the forum structure, guidelines, and code of conduct. ## Moving Support Issues to the Support Platform - Bug reports and feature requests will no longer be handled in the forum. - Figma’s support platform allows one-to-one troubleshooting and the sharing of files or account information that should not be posted publicly. - Support staff can tag and route issues internally. - The support team meets weekly with product and engineering teams to discuss bugs and feature priorities. Figma encourages users to use the relaunched forum to connect, exchange workflow advice, share projects, and learn collaboratively, while directing technical issues and product requests through official support channels.

Read original(opens in new tab)
APIFigmaDesign SystemsPrototyping+1
figma2 min readCurated summary

We made a mistake with our API Challenge, and we’re sorry | Figma Blog

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

Read original(opens in new tab)
APIFigmaDesign ToolsSketch+2
figma2 min readCurated summary

Figma 3.0 (!) | Styles, prototyping++ and design at scale | Figma Blog

Figma 3.0 aims to replace fragmented, desktop-based design workflows with a unified web platform. Its major additions—more capable prototyping, shared styles and libraries, and an Organization tier—help teams keep designs, feedback, prototypes, and systems connected. The overall goal is to reduce tool switching, synchronization work, and redundant subscriptions. ## More Capable Prototyping Figma 3.0 expands prototyping so teams can create realistic interactive experiences directly from their designs: - **Device frames** provide context for designs across iPhones, Android devices, and Apple Watch. - **Fixed objects** keep headers, footers, status bars, and buttons attached to frame edges during scrolling. - **Scrollable areas** support nested frames, vertical lists, horizontal carousels, and scrolling in any direction. - **Transitions** such as dissolve, slide, and push make prototypes resemble native mobile applications. - Prototypes remain synchronized with the underlying design, eliminating screen exports and manual updating. - Comments stay linked to the design, while prototypes can be presented from a mobile browser. - Figma is also investing in an API for integrations with other prototyping tools and web applications. ## Styles and Team Libraries Figma Styles is now generally available, following extensive user research and a private beta. - Styles and Team Libraries allow companies to create and maintain shared design systems. - Teams can centralize reusable visual attributes and apply them consistently across projects. - The feature is intended to reduce inconsistencies and help organizations manage company-wide design standards. ## Organization Tier Figma is previewing a new Organization tier designed for larger companies. - It focuses on scaling design management across large organizations. - Together with shared components, commenting, developer handoff, and web-based collaboration, it is intended to support moving most of a team’s workflow into Figma. Figma 3.0’s practical recommendation is to consolidate design, prototyping, feedback, and design-system management in one web-based environment, while using Figma’s API when specialized integrations are still necessary.

Read original(opens in new tab)
APIFigmaDesign SystemsPrototyping+3
figma2 min readCurated summary

Introducing Figma’s Live Embed Kit | Figma Blog

Figma’s Live Embed Kit lets anyone place continuously updated Figma designs and prototypes on websites or inside third-party tools. Embeds use a simple iframe and remain synchronized with the original file, eliminating repeated exports and uploads. Figma presents the kit as a way to improve team communication and signals future platform tools, including a planned API. ## Simple Embedding for Websites and Tools - Users can select **Share → Public embed** in a Figma file and copy the generated iframe code. - Developers can integrate Live Embeds into their own products using Figma’s embed documentation. - Third-party platforms such as Trello, JIRA, and Dropbox Paper can enable Figma embeds for their users. ## Always-Up-to-Date Designs - Because Figma runs on the web, embedded files stay synchronized with the source document. - Small changes—such as adjusting padding or replacing an icon—appear automatically in every embed. - Teams no longer need to re-export designs or upload updated files manually. ## Collaboration Use Cases - Internal wikis can display live designs alongside project and feature documentation. - Team messaging apps can let users share the latest design versions in conversations. - Blogs and project pages can show designs that remain current for readers. ## Broader Platform Direction - Figma aims to reduce the confusion caused by outdated files scattered across email, Slack, and file-sharing services. - The Live Embed Kit is described as an early step in expanding Figma’s platform. - Figma planned to release an API for retrieving additional information from files and incorporating it into new workflows. The kit is recommended for teams and developers that want design updates to flow automatically into the places where people communicate, document, and build products.

Read original(opens in new tab)
APIFigmaReal Time CollaborationWeb Development+3