What Figma Is: Cloud-Native, Collaborative UI/UX Design

Figma

Chapter 1 · What Figma Is: Cloud-Native, Collaborative UI/UX Design

Vector Graphics covered Illustrator and Inkscape — two file-based applications built around drawing and editing paths. Figma shares that same underlying vector foundation, but it's built on a genuinely different architecture from the ground up: no installed application, no file to save, and multiple people editing the exact same design at the exact same moment.

What Figma Is: A Browser-Based Design Tool

Figma runs primarily in a web browser (a desktop app exists too, but it's essentially a dedicated browser window rather than a fundamentally different application). It's purpose-built for UI/UX and product design — screens, components, interactive prototypes — rather than the print/illustration focus Vector Graphics' own tools lean toward.

Cloud-Native by Default: No File to Save

A Figma design lives on Figma's own servers from the moment it's created. There's no "Save" command in the traditional sense, because there's no local file being written to — every change is continuously synced to the cloud as it happens. This is the same underlying model Google Workspace's own Chapter 1 described for Docs, Sheets, and Slides, applied here to design work instead of documents.

Real-Time Multiplayer: Multiple People, One Design

Multiple people can open the exact same Figma file at the exact same time, each seeing the others' cursors move and edits appear live, the same way Google Workspace's own real-time collaboration works in a shared document. A designer, a teammate reviewing a component, and a stakeholder leaving feedback can all be looking at — and editing — the identical canvas simultaneously, with no separate copies to merge afterward.

Contrasted with Vector Graphics' Own File-Based Model

Illustrator and Inkscape both work with a local file that's opened, edited, and explicitly saved back to disk — one person's own copy at a time, even when a file is later shared with someone else. Figma has no equivalent "the file" at all in that sense; the design simply exists in Figma's own cloud workspace, openable by anyone with permission at any moment, with everyone looking at the same live canvas rather than their own separate copy.

What This Course Actually Teaches

This course covers Figma's own core UI/UX design workflow — frames, auto layout, components, prototyping, collaboration, and developer handoff — alongside Penpot, a free and open-source alternative. Chapter 2 introduces that pairing directly, including an honest note about how lopsided the comparison actually is compared to Illustrator and Inkscape.

AspectIllustrator/Inkscape (Vector Graphics)Figma
Where it runsInstalled desktop applicationWeb browser (desktop app is a dedicated browser window)
Where the design livesA local file, opened and savedFigma's own cloud servers, always synced
Editing togetherOne person's own copy at a timeReal-time multiplayer, same live canvas
Primary focusIllustration, print, general vector workUI/UX and product design
Coming up in Chapter 2
Figma's real-world dominance in UI/UX design is genuinely more lopsided than Illustrator's own dominance over Inkscape — Chapter 2 says so directly rather than presenting Figma and its open-source alternative, Penpot, as two evenly-matched options.
"No file to save" doesn't mean "no version history"
It's tempting to assume that since there's no explicit Save command, there's no safety net if something goes wrong or an edit needs undoing after the fact. Figma keeps its own continuous version history automatically in the background — the same underlying safety net Google Workspace's own Version History chapter described for documents, just applied here to design files. Nothing about the lack of a manual Save step means changes are unprotected or unrecoverable.

Hands-On Exercises

Exercise 1

A designer used to Illustrator opens Figma for the first time and looks for a "Save" button, growing anxious when they can't find one. Using this chapter's own material, explain why there's no Save command and why this isn't actually a problem.

📄 View solution
Exercise 2

A team wants a designer, a developer, and a stakeholder to all review and comment on the exact same design at the same time, without emailing separate file copies back and forth. Using this chapter's own material, explain how Figma's own model solves this directly.

📄 View solution
Exercise 3

Explain, using this chapter's own material, why Figma's cloud-native, real-time-multiplayer model is described as a genuinely different architecture from Illustrator and Inkscape's own file-based model, rather than just a different-looking version of the same thing.

📄 View solution

Chapter 1 Quick Reference

  • Figma is browser-based, purpose-built for UI/UX and product design
  • Designs live on Figma's own cloud servers, continuously synced — there's no local file to manually save
  • Real-time multiplayer lets multiple people edit the same live canvas simultaneously
  • This is a genuinely different architecture from Illustrator/Inkscape's own file-based model, not just a different interface
  • Version history runs automatically in the background — no Save button doesn't mean no safety net