Technology · Design

Figma

Where every Innoveev product starts — multiplayer design, living prototypes, and tokens that flow straight into code.

Made by
Figma, Inc.
First release
2016
Runs in
Browser · desktop app
In our stack since
2018
In plain English

What it is, and why we use it.

Figma is the collaborative interface-design tool that moved design from files on someone's laptop to a shared canvas in the browser. Designers, engineers, and clients look at the same screens at the same time; prototypes are clickable without exporting anything; and Dev Mode exposes spacing, tokens and component props directly to the engineer implementing them.

Every product we build — mobile and web — is designed in Figma first: flows in FigJam, hi-fi screens with real content in both LTR and RTL, design tokens named to match the codebase, and component libraries that mirror our Storybook one-to-one. Clients get a live file link from week one, not a PDF at the end.

Key differences

Figma vs Sketch vs Penpot.

Figma against the classic Mac-native tool it displaced and the open-source challenger — why the industry consolidated, and where the others still make sense.

DimensionFigmaSketchPenpot
PlatformBrowser + desktop, any OSmacOS onlyBrowser, self-hostable
Real-time collaborationNative — multiplayer is the core modelVia separate workspace toolingNative multiplayer
PrototypingBuilt-in, with variables and conditional logicBasic; relies on companion appsBasic interactions
Developer handoffDev Mode — inspect, tokens, code snippetsThird-party toolsInspect built in; tokens are open-format
Design systems at scaleComponent libraries, variables, team-wide publishingStrong symbols, weaker multi-team storyImproving fast, smaller ecosystem
Cost & opennessCommercial SaaS; your files live on its cloudOne-time-ish licence, local filesOpen source — free, your servers, your data

Figma wins when

  • Designers, engineers and stakeholders need one live source of truth
  • Design systems must map one-to-one to coded component libraries
  • Prototypes have to be tested with users before code exists

Sketch wins when

  • A Mac-native, offline-first workflow matters more than collaboration
  • You prefer local files and one-time licensing
  • Long-established Sketch libraries aren't worth migrating

Penpot wins when

  • Data sovereignty requires self-hosting your design files
  • Budget rules out SaaS seats for a large team
  • You want open standards (SVG-native) under your design work
Our take

Figma is where our design practice lives — not out of fashion, but because multiplayer files and Dev Mode demonstrably kill the handoff gap that used to eat 20% of every project. We keep an eye on Penpot for sovereignty-sensitive clients.

Thinking about Figma?

Tell us what you're building — we'll tell you honestly whether Figma is the right tool for it.