Techlist.io - Korean Tech Blog Curator

datadogOriginal article

What product designers can learn from explanatory journalism | Datadog (opens in new tab)

Product designers can significantly improve their impact by adopting the techniques of explanatory journalism, which prioritizes deep context over the constant noise of new information. By shifting the focus from simply presenting features to explaining the "why" and "how" behind them, designers can better navigate the complex needs of various stakeholders. This approach fosters more rigorous decision-making and ensures that product solutions are grounded in a comprehensive understanding of the problem space. ### Prioritizing Impact Over Recency * Designers often face a "newness bias" where the latest support ticket or customer call carries disproportionate weight compared to long-term goals. * To counteract this, designers should aggregate feedback from diverse sources—such as high-value customers and recurring requests—to identify and prioritize what is truly important rather than what is merely recent. * Effective prioritization requires a centralized system to track the frequency and source of feedback, allowing for a more objective weighting of product requirements. ### Mitigating Context Collapse * In a large organization, "context collapse" occurs when information is shared across different teams (Sales, Support, Research, Executives) without accounting for their unique perspectives or goals. * A designer's role involves assembling disparate pieces of data—including interview notes, sales requirements, and executive goals—into a single, cohesive narrative. * Beyond just presenting work, designers must frame their solutions specifically for each audience, explaining how the design addresses their specific context or why certain requests were triaged out. ### Leveraging the Unlimited Design Papertrail * The design process should cycle through "expansion," where research and data are gathered without space constraints, and "contraction," where that information is distilled into actionable insights. * Developing a thorough "papertrail" of documentation helps the designer master the subject matter, making their eventual summaries more concise and authoritative. * This documentation should include organized interview notes—categorized by job role and company size—and competitive research to serve as a permanent "canon" for all design decisions. To produce more effective work, designers should embrace the role of an "explainer" by meticulously documenting their research and expansion phases. Building a robust, updated papertrail not only clarifies the designer's own thinking but also provides the necessary evidence to defend usability and interaction design choices in a fast-moving product environment.

figma3 min readCurated summary

Introducing: Figma’s Platform | Figma Blog

Figma launched its Platform in 2018 to connect design files with external tools, scripts, and web applications. Its central innovation was a web API that made design data accessible across operating systems and workflows, enabling new forms of collaboration. Figma argued that this open, web-based foundation could replace outdated export-based processes with live, integrated design systems. ## A Web API for Design - Figma’s API was presented as a first for professional design tools, which had traditionally been siloed desktop applications. - Because Figma operates online, external software can access the current state of a design without depending on: - A particular operating system - Local file paths - Specific software versions - Companies could build custom tools around their own organizational needs. - Examples included: - Uber creating live displays and feeds of work in progress - GitHub automating parts of its icon-production workflow ## Core API Capabilities The initial Web API provided three main functions: - Reading design files in an open JSON format - Reading and writing comments - Rendering files or file sections as PNG, JPG, SVG, and other standard formats Using a file’s URL-based key, developers could retrieve a live representation of its design tree, including: - Shapes and text - Components - Prototype links and transitions - Constraints - Other structural information defining the design The API was designed for familiar web-development tools and programming frameworks rather than proprietary plugin languages, making integrations easier to create and maintain. ## Open-Source Demos and Integrations Figma announced demo projects illustrating possible uses of the platform, including: - A spell checker for Figma designs - A generative art tool - A way to place designs on the Ethereum blockchain It also highlighted integrations with Avocode, Haiku, Zeplin, and Pagedraw. ## Planned Platform Features Figma outlined several future additions: - **Webhooks:** Notifications for file or team events, including design updates. - **Write API:** Broader programmatic editing of Figma files beyond the existing Comment API. - **Extensions:** An in-app extension system, though Figma intended to prioritize robustness, predictability, and quality rather than release an unstable model quickly. ## Collaboration Problems in Traditional Design Workflows As design becomes relevant to engineers, researchers, marketers, executives, and other departments, desktop design tools create organizational friction: - Files must be exported and uploaded before sharing. - Shared files become outdated when the original changes. - Leaders lack an easy way to view and comment on live work. - Engineers spend time locating the correct assets. - Teams often recreate solutions that already exist elsewhere in the organization. Figma positioned its API as a way for enterprises to share, search, and monitor real-time designs across departments. ## Uber’s Internal Use Case Uber’s distributed design team worked across four cities and multiple products, including Uber Eats and Uber Freight. To improve visibility, the company planned to use Figma’s API to: - Broadcast in-progress designs on office TVs - Create a Dribbble-like internal repository - Make work easier to browse across the organization The example demonstrated how Figma’s API could turn design files into live organizational infrastructure rather than isolated project artifacts. Figma’s recommendation was to treat the Platform as a foundation for custom workflows and integrations. By exposing live design data through standard web technologies, it enabled companies to build collaboration tools suited to their own processes while reducing manual exports and duplicated work.

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

Now you can name and annotate your Figma Version History | Figma Blog

Figma introduced named and annotated Version History to make design changes easier to organize, review, and restore. Because Figma continuously autosaves files in the browser, users can now mark important milestones instead of sorting through a long list of automatic saves. The update aims to reduce export work, improve collaboration, and help teams review designs more efficiently. ## Organizing Design Milestones - Designers can manually flag important versions and give them names and notes. - Autosaves between marked versions are automatically collapsed, making the history easier to scan. - Important milestones can be restored or duplicated into new files. - Version History is available through a file’s name menu and “Show Version History.” ## Page-Specific Version History - Version History can now be viewed for individual pages rather than only for the entire file. - This reduces noise when different pages contain unrelated changes. - To access it, open a page, select the file name, and choose “View Version History.” ## Notes for Faster Design Review - Notes can explain what changed in each revision. - Stakeholders can review design stages and leave feedback directly within Version History. - The feature is intended to reduce meetings and speed up design feedback cycles. ## Keyboard Shortcut - macOS: `⌘ + ⌥ + S` - Windows: `Ctrl + Alt + S` - The shortcut quickly saves and names a selected version. The update builds on Figma’s autosave system by adding deliberate checkpoints and context. Teams can stay in their design workflow while preserving, reviewing, and discussing key stages without exporting files.

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

How to hit the road as a UI/UX digital nomad | Figma Blog

Digital nomadism can offer UI/UX designers freedom and new experiences, but it requires careful preparation and reliable communication. The article’s central advice is to secure clients, establish the basics of a freelance business, and plan for dependable internet before leaving. Once abroad, designers should build local connections and maintain client trust through consistent updates and clear expectations. ## Prepare Before You Leave - Secure clients or an employer before booking a one-way ticket. - Building relationships while still nearby makes hiring easier and reduces financial pressure. - Meet prospective clients in person when possible to understand their communication styles and business needs. - Grow a client network by: - Attending design meetups and tech events. - Posting freelance services on Craigslist. - Completing initial projects before explaining long-term travel plans. - Regularly reminding professional contacts that you are accepting work. ## Set Up the Freelance Business Complete administrative tasks before traveling, since registering and managing a business from abroad can be difficult. - Consider forming an LLC for potential business deductions. - Open a separate business checking account. - Create a portfolio website with contact information. - Prepare business cards and other promotional materials. - Work with an accountant to manage taxes. - Register the business name. ## Plan for Reliable Internet Internet access is essential for conference calls, email, and collaborative design work. - Research WiFi quality at each accommodation and check reviews for complaints. - Ask hosts to provide a connection-speed test if necessary. - Carry a backup SIM card or mobile-data option. - Warn clients in advance if connectivity may be unreliable. - Use cloud-based collaboration tools such as Figma to share files, collect comments, and avoid repeatedly exporting designs. - Open Figma files before losing connectivity if offline work may be necessary. ## Build a Digital Nomad Community Traveling can be isolating, so designers should intentionally connect with other remote workers. - Join Facebook communities such as Digital Nomads Around the World, Female Digital Nomads, or Digital Nomad Girls. - Consider destinations with established remote-work communities, including: - Hanoi - Chiang Mai - Ubud - Look for cities with strong WiFi, coworking spaces, coffee shops, and a reasonable cost of living. - Structured programs such as Roam and Remote Year can provide a more organized experience. ## Maintain Client Trust Across Time Zones Distance makes transparency and regular communication especially important. - Send clients frequent progress updates; one designer mentioned sending daily emails. - Schedule recurring calls, such as every two days, to answer questions and maintain alignment. - Set clear expectations around availability, time zones, and possible connectivity problems. - Balance work with travel so the nomadic lifestyle does not become an exhausting remote office. A successful UI/UX digital nomad lifestyle depends less on spontaneity than on preparation, dependable infrastructure, and disciplined client communication. Secure work and business systems first, then choose destinations and routines that support both productivity and the freedom to travel.

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

Figma prototyping: now with transitions | Figma Blog

Figma’s 2018 update introduced transitions to its prototyping tool, allowing designers to create more realistic, communicative app experiences. Users could connect frames with dissolve, slide, or push animations, customize duration and easing, and preview results directly in the toolbar. The update aimed to reduce ambiguity among designers, engineers, clients, and other stakeholders. ## Why Transitions Matter - Prototypes help teams evaluate high-fidelity app experiences before development. - Animation between frames can significantly affect how an interface feels. - Adding transitions reduces back-and-forth by communicating interaction details more clearly. - The feature was developed in response to extensive community feedback. ## New Transition Features - Apply **dissolve, slide, or push** effects between frames. - Set animation durations down to a few milliseconds. - Adjust easing so animations accelerate or slow down at different points. - Preview frame transitions in the prototyping toolbar. - Use transitions to reproduce platform-specific interactions, such as iOS-style motion. ## Existing Prototyping Advantages - **Live design:** Prototypes remain synchronized with the underlying web-based designs, eliminating the need to re-export after edits. - **Mobile presentations:** Presentations can be controlled from Android or iOS browsers, while stakeholders can follow along from their own computers. - **Components:** Prototype interactions assigned to a component automatically apply to its instances, making repeated navigation—such as a home button—easy to maintain. ## Continued Product Development - Figma positioned transitions as another step toward making prototyping faster and easier. - The company planned to continue expanding prototyping to better support everyone involved in software development. Transitions made Figma prototypes more polished and useful for communicating both static designs and interactive behavior before implementation.

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

With love, from Figma: @mentions and file sorting | Figma Blog

Figma’s February 2018 update introduced two features designed to reduce friction in design workflows: file sorting and @mentions. Users can now organize files by creation date or name, while comments can directly notify specific teammates by email and in-app notification. Together, the features make finding files and coordinating asynchronous feedback more efficient. ## Organizing Files with New Sorting Options - Figma file lists were previously sorted primarily by “Last Modified.” - Users can now sort files by: - Date created - File name alphabetically - Last modified date - These options make it easier to locate older files or maintain a more organized workspace. ## Directing Feedback with @Mentions - Figma introduced @mentions for comments, allowing users to tag a teammate by typing `@` followed by their name. - Mentions are useful for: - Drawing a product manager’s attention to a specific design change - Asking engineers questions about a prototype - Notifying designers that copy edits are complete - Mentioned users receive both an email and an in-app notification. - Users can reply directly to comment notification emails, and their response is added to the Figma comment thread. ## Improving Asynchronous Collaboration - Previously, commenters had to send a document link and tell recipients to search for the relevant comment. - @mentions eliminate that extra step by pointing teammates directly to the discussion requiring their attention. - The features were developed in response to repeated requests from Figma users. Refreshing open Figma tabs enables both updates. These additions provide simple, practical improvements for organizing files and ensuring feedback reaches the right collaborator.

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

Web design without a web designer? Xfive turns to Figma. | Figma Blog

Xfive, a web development company without in-house designers, used Figma to redesign its outdated website. Content producer Lubos Kmetko created the redesign and used Figma’s browser-based collaboration, prototyping, commenting, and developer handoff features to involve stakeholders across the company. The experience showed that Figma could make website design accessible to non-designers while reducing communication and implementation friction. ## Website problems and redesign goals - Xfive’s homepage and key sections had fallen behind as the company grew. - The site suffered from: - Outdated Customers and Work sections - Confusing navigation - Too many competing calls to action - Numerous landing pages that were difficult to maintain - Because Xfive typically implements client-provided designs, it did not usually employ dedicated designers. - Lubos Kmetko, a content producer familiar with Figma, took responsibility for the redesign. ## Prototyping and stakeholder collaboration - Lubos redesigned the homepage, Customers section, and Work section. - He streamlined navigation and reduced the number of CTAs and landing pages. - Stakeholders from marketing, sales, production, editorial, development, and operations reviewed the mockups. - Figma’s cloud-based workflow allowed anyone with a browser to: - Open the designs through a shared link - Leave comments - Discuss ideas and interactions - Review changes in real time - Feedback and revisions remained synchronized in one location instead of being scattered across files and messages. ## Improving designer-developer handoff - Approved designs were shared directly through Figma rather than sent as files through email or Box. - Developers could inspect designs in the browser using Code Mode. - Figma provided specifications such as dimensions, colors, and padding, along with export options for CSS, iOS, and Android code. - This reduced version-control problems, guesswork, and dependency on tools such as Avocode or Zeplin. - Developers reported that access to precise design details helped them code faster and more accurately. ## Future use of Figma at Xfive - Xfive viewed the redesign as a starting point for adopting Figma in client projects. - Lubos envisioned replacing emailed PDFs and JPEGs with functional, shareable prototypes. - The company planned to use Figma across the process, from early design discussions and implementation details to developer handoff. Figma enabled Xfive to complete a substantial redesign without a traditional designer and created a more centralized, collaborative workflow. For teams working across disciplines or locations, browser-based prototypes, comments, and inspectable design specifications can significantly simplify both design review and development.

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

FigmaTip Roundup 6.0 | Figma Blog

The sixth FigmaTip Roundup collects practical techniques and community-created resources for speeding up design work in Figma. It highlights a Material Design System, more precise color editing for grouped objects, and Figma’s support for smoother “squircle” corners. ## Material Design System for Figma - R. Kamushken’s user-made Material Design System includes a fast table constructor. - The feature was introduced in version 1.3. - The resource is available for download through Setproduct. ## Editing Strokes and Fills Independently - Figma allows designers to change the stroke color of a group without altering its fills. - Objects in the group that have fills but no strokes remain unaffected. - The roundup presents this as a workflow advantage over tools such as Illustrator and Sketch. ## Smoother Corners with Squircles - The post announces a feature for creating ultra-smooth corners using squircles. - This provides an alternative to standard rounded rectangles for producing more polished interface shapes. The roundup encourages designers to adopt these community-discovered resources and features to make everyday Figma workflows faster and more precise.

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

Figma raises $25MM Series B | Figma Blog

Figma announced a $25 million Series B funding round led by Kleiner Perkins partner Mamoon Hamid. Existing investors from Index, Greylock, and LinkedIn also participated. The funding supports Figma’s broader vision of making design accessible, collaborative, and web-based rather than limited by siloed tools and workflows. ## Series B Funding - The round was led by Kleiner Perkins’ Mamoon Hamid. - Hamid’s previous investments included SaaS companies such as Slack, Box, and Intercom. - Existing investors Danny Rimer of Index, John Lilly of Greylock, and LinkedIn co-founder Jeff Weiner joined the round. - This was Hamid’s first investment at Kleiner Perkins. ## Figma’s Founding Vision - Figma was founded five years earlier by Dylan Field and Evan Wallace. - The founders believed creative tools should empower users rather than constrain them. - Their goal was to make creation: - Accessible to more people - Collaborative instead of siloed - Built for the web - The company emerged from experimentation with browser-based design tools, supported initially by a Thiel Fellowship. ## Adopting a New Way of Working - Figma acknowledged that changing established design workflows is difficult and takes time. - The company credited its users, employees, and early investors for supporting its vision during that transition. - The funding announcement represented both financial growth and continued validation of collaborative, web-based design. Figma intended to use the momentum from its Series B to continue developing tools that make design more open, collaborative, and accessible across teams.

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

Figma announces design system meetups in 6 cities around the world | Figma Blog

Figma announced a series of design system meetups in six cities worldwide to help designers share challenges, lessons, and best practices. The initiative began in Lagos, Nigeria, where more than 300 people attended, and was shaped by strong community interest in design systems. Figma concluded that larger meetups were more inclusive and useful than the dinner-sized events originally planned. ## Meetup Locations and Schedule - Lagos, Nigeria — January 27 - Toronto, Canada — February 23 - Bangalore, India — details forthcoming - Amsterdam, Netherlands — details forthcoming - New York, United States — details forthcoming - Los Angeles, United States — details forthcoming Each event would be adapted to its local design community and include presentations from local designers. Figma representatives would attend where possible. ## Community-Driven Organization - The meetups grew out of thousands of responses to a questionnaire launched with DesignSystems.com. - Designers volunteered to host or partner on events. - Figma abandoned its original dinner format after receiving more interest than small venues could accommodate. - The broader meetup format allowed more designers to participate and share “war stories” about building design systems. ## The Lagos Meetup - Lagos was selected because of its growing design and technology scene and its large concentration of Figma users in Africa. - Figma’s cloud-based platform and free tier were especially valuable in Lagos, allowing designers to work from offices, home, or internet cafés. - Hotels.ng designer Namnso Ukpanah organized the event. - Speakers included designers from hotels.ng, Andela, and Paystack, along with Figma CEO Dylan Field. - More than 300 people attended. ## Expanding DesignSystems.com Figma planned to use information from the questionnaire and meetups to create a more comprehensive version of DesignSystems.com. Designers interested in bringing an event to their city were encouraged to express interest, volunteer as hosts, or contact Figma for details. The initiative demonstrates that design systems benefit from open, local communities where practitioners can exchange practical experience. Designers seeking similar events could support the effort by organizing locally or participating through DesignSystems.com.

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

Bug Bashing Party at Figma During Quality Week | Figma Blog

Figma’s Quality Week is a company-wide pause from new feature development to focus on fixing accumulated bugs and polishing existing functionality. The initiative reflects Figma’s belief that small usability problems compound for designers who spend hours in the product. By making quality work a recurring tradition, Figma aims to deliver a smoother, more reliable professional tool while also giving employees opportunities to explore unfamiliar parts of the codebase. ## A Company-Wide Focus on Quality - Figma launched its first official Quality Week in early 2017. - Engineers and designers temporarily paused their regular projects to address: - Annoying but non-critical bugs - Broken or incomplete features - Improvements to existing workflows - The company found that focused maintenance work could be as valuable as continuously shipping new features. - Quality improvements are especially important because users spend long periods working in Figma, making small imperfections increasingly disruptive. ## Quality Week 2018 Improvements - Two engineering teams collaborated on a broad set of bugs and prioritized issues that affected Figma’s professional quality. - Notable fixes included: - **Figma Mirror:** Improved stability and reduced crashes in the mobile mirroring app. - **Sketch import:** Added drag-and-drop importing into the editor and improved text-import accuracy. - **Chromebook support:** Enabled users to hold the search key and drag to duplicate objects. - **Layer panel behavior:** Made it easier and more intuitive to nest layers into groups and frames. - Figma acknowledged that the product was not bug-free, but planned to continue focused quality efforts throughout the year. ## Benefits for the Team - Quality Week helped developers and designers work in parts of the codebase outside their usual areas. - The event encouraged collaboration across teams and made otherwise routine maintenance work enjoyable. - Figma celebrated achievements with awards, including recognition for fixing the company’s oldest known bug—an issue affecting Windows users since 2015. ## Feedback and Ongoing Support - Many bugs addressed during Quality Week were reported by Figma’s user community. - Figma encouraged users to submit feedback through: - The in-product Help menu - Twitter - The community forum - Email support - The company emphasized an all-hands support model, where users might interact with engineers or even the CEO. Figma’s approach shows that dedicated time for bug fixing and product cleanup can complement innovation rather than compete with it. Regular quality-focused periods, combined with continuous user feedback, help maintain a reliable and polished product as it evolves.

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

#FigmaTip Roundup 5.0 | Figma Blog

This #FigmaTip roundup highlights small Figma interactions that can make design work faster and more intuitive. The tips focus on importing multiple images, navigating deeply nested layers, and creating evenly spaced layouts. Together, they demonstrate how Figma’s built-in behaviors can streamline common design tasks. ## Importing Images in Bulk - Drag a folder directly from your desktop into Figma. - Figma imports the folder’s images as a set, avoiding the need to add each file individually. ## Navigating Nested Layers - Hold **Control** and right-click an object. - Use the resulting context menu to view and navigate through the object’s nested layers. - This is particularly useful when several layers overlap or when selecting a deeply nested element is difficult. ## Creating Equal Spacing and Column Grids - Use Figma’s red alignment and spacing guides to quickly position objects at equal distances. - Once the spacing is correct, use the distribute function to arrange the objects into a column-like grid. These shortcuts are worth incorporating into everyday workflows: they reduce repetitive actions and make Figma’s “it just works” interactions more discoverable.

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

How to convince your team to switch to Figma | Figma Blog

Buffer’s move to Figma was presented as a cultural change, not merely a software upgrade. Figma helped break down design silos by making files accessible, collaborative, and usable across platforms. James Morris’s approach was to build support through experimentation and demonstrations rather than simply arguing for the switch. ## Buffer’s Transparency and Collaboration Challenges - Buffer valued transparency, but its existing design tools isolated designers from other departments. - Designs were difficult to locate in Dropbox and often required paid software or newer versions to open. - Developers and product managers worried about accidentally overwriting files. - Figma’s cloud-based files could be opened through shared URLs, with free view-only access for collaborators. - Linux users could access designs without buying a Mac or specialized desktop software. - Viewers could comment and inspect design data for implementation. ## Step 1: Create an Open Exploration Period - Morris introduced a company-wide period for testing different design and collaboration tools. - Teams were encouraged to experiment and identify which tools best addressed their workflow problems. - He gathered feedback and explained how Figma could solve Buffer’s communication issues. - Rather than relying only on a persuasive presentation, he trusted hands-on use to demonstrate Figma’s value. ## Step 2: Show, Don’t Tell ### Collaborative Whiteboarding with Product Managers - Morris used remote whiteboarding sessions to let product managers experience Figma directly. - He and a Canadian PM brainstormed together in real time, using shapes and diagrams much like a collaborative Google Doc. - This allowed them to develop ideas together without waiting for a formal specification. - Figma’s ease of use became apparent through practical collaboration. ### Winning Over Engineers - Morris gave engineers direct links to Figma files and let them explore independently. - Engineers could inspect CSS, Swift, and Android XML values through the free view-only experience. - Stable URLs created a single source of truth, replacing exported images and confusing Dropbox locations. - Figma’s browser-based architecture and use of WebAssembly also appealed to engineers interested in advanced web technology. ### Addressing Designers’ Concerns - Designers could be more difficult to persuade because some feared open, transparent workflows. - Others doubted that a browser-based application could match the speed and performance of desktop software. - The article begins describing the use of incentives—“candy”—to help designers try Figma, but the provided text ends before that section is completed. The practical recommendation is to make tool adoption an open, low-pressure experiment. Give each team a concrete way to experience the benefits—real-time whiteboarding for product managers, inspectable files for engineers, and performance demonstrations for designers—so the change becomes evident through use.

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

How Figma Transformed This Berkeley Design Class | Figma Blog

UC Berkeley’s CS 160 course used Figma to make digital product design more accessible to computer science students. The cloud-based tool solved problems involving incompatible devices, steep software learning curves, and limited collaboration. As a result, students spent more time applying usability principles and less time learning complicated design software. ## Challenges in Teaching Digital Design - CS 160 teaches human-computer interaction through 3–4-person teams building Android apps around themes such as healthcare and elections. - The course struggled with: - Students using Linux, Windows, Macs, or no personal computer. - Limited computer-lab solutions for incompatible software. - Adobe tools requiring substantial training. - Students with prior design experience often handled wireframing and prototyping, while others focused on coding or user testing. - Enrollment demand was high enough that the course’s original 100-student limit had to be doubled. ## Figma Made Design More Accessible - Figma was free for students and worked across different operating systems. - Its simple interface allowed students without design backgrounds to learn the basics quickly—one student reported becoming productive in about an hour. - Built-in features supported teaching: - In-context comments for instructor feedback. - Version history for reviewing progress. - Simultaneous editing by multiple students. - Integrated prototyping for presentations. - Students could focus on concepts such as Nielsen’s usability heuristics instead of spending most of their time learning Photoshop. ## More Effective Project-Based Learning - Students applied classroom lessons directly to their projects, reinforcing the concepts through practice. - One healthcare-themed team designed an app helping people with alcoholism locate nearby Alcoholics Anonymous meetings. - Figma’s quick prototyping was especially useful because teams had only about an hour of face-to-face collaboration each week. - Teachers and TAs could comment directly on relevant parts of a design rather than sending unclear, broad feedback by email. ## Collaboration Across Disciplines - Real-time editing enabled students to brainstorm, observe one another’s work, and contribute regardless of their design background. - Teams could work outside class without worrying about conflicting file versions or accidentally overwriting one another’s work. - The course used Figma to bring coding and design together, giving computer science students a more collaborative introduction to product design. Figma’s main contribution was reducing technical and logistical barriers so students could concentrate on design thinking, usability, and teamwork. For similar project-based courses, accessible cross-platform tools with real-time collaboration and contextual feedback can make design education more inclusive and effective.

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

18 designers predict UI/UX trends for 2018 | Figma Blog

The article gathers predictions from 18 designers about UI/UX in 2018, emphasizing that the field should improve users’ experiences rather than prioritize novelty or designer ego. Common themes include accessibility, ethical responsibility, collaboration, and closer integration between design and development. It also warns that efficiency and standardized systems can become harmful when adopted without critical thought. ## Accessibility and Inclusive Design - Designers argue that accessibility should become a central responsibility rather than an afterthought. - Common problems include: - Using ultra-light gray text for essential content - Adding unnecessary animation - Making interfaces harder to understand for visual flair - Inclusive design is described as an important trend that the industry needs, even if it is unlikely to attract attention or headlines. - The article suggests that many teams avoid accessibility work because it requires sustained effort rather than producing immediately visible results. ## Design Collaboration Inspired by Engineering - Design teams may begin working more like engineering teams. - Possible developments include: - Formal design reviews similar to code reviews - Design tools that identify inconsistencies like code linters - Open-source design patterns and shared UX standards - This approach could make collaboration more systematic and help establish common practices for user experience and information design. ## Ethics and Designer Responsibility - Designers are encouraged to recognize the influence their work has on people’s behavior and decisions. - UX choices should be evaluated for their ethical consequences, not only their usability or business value. - The broader prediction is that designers will become more accountable for how products affect users and society. ## Risks of Overreliance on Design Systems - Standardized systems such as Material Design and Microsoft’s Fluent Design may become increasingly dominant. - One concern is that designers will adopt these systems automatically without questioning whether they fit a product’s users or context. - Design systems can improve consistency, but they should not replace independent judgment or thoughtful problem-solving. ## Convergence of Design and Development Tools - Design and development tools are expected to become more integrated and centralized. - Technologies such as CSS Grid, custom variables, Vue, and React could make implementation more efficient and flexible. - Greater efficiency should create more time for designers to focus on responsible design and more inclusive experiences. - The article frames technical progress as valuable only when it supports better outcomes for users. Overall, the predictions recommend treating accessibility, ethics, and inclusion as core design requirements—not optional trends—while using collaboration frameworks, design systems, and new development technologies thoughtfully.

Read original(opens in new tab)