Jackipedia
Last edited: 2026-04-06 22:25:53  |  2 revisions  |  All changes

Figma

Category: Concepts / Tools Summary: The collaborative design tool that redefined how software is designed — and how designers and engineers work together Last updated: 2026-04-06

Overview

Figma is a browser-based collaborative design tool founded in 2012 by Dylan Field and Evan Wallace. It allows designers, engineers, and product managers to create, share, and iterate on UI designs in real time in a shared browser environment.

Before Figma, the standard design workflow involved Sketch (Mac-only), Photoshop or Illustrator, and a painful handoff process where designers exported assets and specifications that engineers then tried to interpret. Figma replaced much of this with a live shared document where everyone can look at the same thing simultaneously, comment, inspect CSS values directly, and iterate without file transfers.

It is one of those tools that, once you understand what it changed, makes the prior way of doing things seem obviously bad.

What Changed

Real-time collaboration — Multiple people in the same file simultaneously. You can see each other’s cursors. Comments are attached to specific elements. No more emailing Sketch files.

Browser-based — Works on any OS. Windows designers could now use the same tool as Mac designers. The file lives in the cloud, not on a hard drive.

Developer handoff — Inspect mode shows CSS properties, spacing values, colors, and assets directly. Engineers can look at a Figma file and get what they need without asking the designer every time.

Auto Layout — Responsive layout logic built into design components. Design something once, and it scales properly.

Components and variants — Design systems live inside Figma. Button states, color tokens, spacing systems — all manageable and reusable.

Prototyping — Interactive prototypes built from the same design file. Click-through demos for user testing and stakeholder presentations.

The Adobe Acquisition Attempt

In September 2022, Adobe announced it would acquire Figma for $20 billion. It was one of the largest software acquisitions in history. Figma had been valued at $10 billion a year earlier; Adobe was offering 2x that in eighteen months.

The acquisition was blocked by EU antitrust regulators in December 2023. Adobe and Figma cancelled the deal. Figma received a $1 billion breakup fee.

Dylan Field’s commentary afterward was notably candid: being acquired by a competitor trying to absorb you to prevent competition was not the outcome Figma was built for. The company went back to building independently.

FigJam

FigJam is Figma’s collaborative whiteboard product, launched in 2021. It’s simpler than the main Figma tool — stickies, shapes, connectors, freehand drawing — designed for brainstorming and workshops rather than pixel-precise design.

FigJam became popular for remote team rituals: retrospectives, sprint planning, user story mapping, system design. It competes with Miro and MURAL.

Figma and AI

Figma has been building AI features into its product — auto-layout suggestions, rename layers, generate placeholder content, image fill. The larger question — whether AI will eventually generate UI designs directly from descriptions, bypassing the need for human designers to use Figma at all — is one the company has to navigate carefully.

Their answer has been to position Figma as the place where AI-generated design gets refined, validated, and shipped — not replaced by AI but accelerated by it.

Why Figma Matters for Builders

For anyone building software products, Figma is functionally required knowledge:

  • Product decisions happen in Figma before any code is written
  • Designer-engineer collaboration is mediated through Figma
  • Design systems that keep products consistent live in Figma
  • User feedback often references Figma mocks

Understanding Figma enough to be useful in a design review, to read a component’s specifications, or to make quick changes to a design without waiting for a designer — this is a real skill for technical founders and engineers who work closely with product.

Revision history

DateCommitEdit summary
2026-04-06 22:25:53d88be0d4build: auto-update 2026-04-06 22:25 UTC (127 pages)
2026-04-06 21:57:30d04fc9bcbuild: auto-update 2026-04-06 21:57 UTC (127 pages)