How Kiwi.com handles project structure, versioning & components in Figma | Figma Blog (opens in new tab)

Kiwi.com’s small mobile design team uses Figma to bring design collaboration, prototyping, versioning, and handoff into one shared environment. Their previous Sketch workflow depended on Sketch, Zeplin, Abstract, Marvel, and Dropbox Paper, creating frequent synchronization problems. Figma became attractive because it could centralize these activities and support contributions from around twenty collaborators.

A Small Team with Many Contributors

• Kiwi.com’s mobile design team consists of only two people.
• Around twenty others contribute through:
  • Commenting on design iterations
  • Correcting copy
  • Designing cross-platform features
• The broader front end and Orbit design system were built in Sketch.
• Because Orbit’s mobile components differ visually, the team decided to explore building the mobile system in Figma.

Problems with a Multi-tool Sketch Workflow

• Sketch was used alongside:
  • Zeplin for developer handoff
  • Abstract for version control
  • Marvel for static prototypes
  • Dropbox Paper for embedded PNGs
• These tools frequently fell out of sync:
  • Prototypes could reflect older tested versions.
  • Designers might forget to commit changes to Abstract.
  • Zeplin might not contain the latest approved visuals.
  • Documentation images could be weeks out of date.
• The workflow required constant manual coordination between separate sources of truth.

Why the Team Chose Figma

• Figma offered a way to consolidate design work, collaboration, prototyping, and version history.
• Its value became clearer in a team where many people needed access to current designs.
• The author initially resisted Figma, preferring a native design application over a browser-based tool.
• As Kiwi.com’s collaborative needs grew, the advantages of a shared, synchronized workspace outweighed that hesitation.