What do you like best about Figma?
Real-time collaboration — design together, see changes live
Figma’s cloud-based, browser-accessible platform allows designers, product managers, developers and even stakeholders to work simultaneously on the same file. Multiple people can edit, comment or prototype in real time — which dramatically reduces delays caused by back-and-forth hand-offs or file version mismatches.
All-in-one tool: design, prototype, hand-off to developers
With vector editing, layout/design mode, prototyping mode, and a “developer mode” for specs and code-ready assets, Figma covers almost the full design-to-dev workflow.
This reduces context switching and helps keep design fidelity high when handing over to engineering.
Cross-platform & cloud-based accessibility — no OS barriers
Because Figma runs in the browser (with optional desktop apps), it works across operating systems. Teams don’t need to worry about Mac vs Windows licenses or file-format compatibility. That inclusivity enables mixed-environment teams (designers + developers + PMs) to collaborate seamlessly.
Design systems, shared libraries & consistency across projects
The ability to build reusable components, shared style libraries, and maintain a “single source of truth” for UI elements helps ensure consistency across screens, pages or products — a major plus for conversion rate optimisation, branding and UX coherence.
Speeds up prototyping & feedback loops — ideal for agile/product-led teams
Because you can quickly turn designs into clickable prototypes, get feedback, iterate, and share with stakeholders or users — Figma supports the fast experimentation cycles that CRO/UX teams often need. This tight feedback-to-iteration loop helps validate UX decisions before committing development resources.
From a CRO or UX-optimization standpoint: Figma enables alignment between design, product, and development — helping deliver better UX, consistent UI, and faster rollouts of hypotheses/tests. Review collected by and hosted on G2.com.
What do you dislike about Figma?
What I Dislike (or What Could Be Better)
Performance issues with large / complex files, and collaboration lags
As projects grow — complex design systems, long flows or many collaborators — Figma can become sluggish, which can hinder productivity or frustrate team members.
Dependence on internet connection; offline mode is limited
Being cloud-based is a major strength — but it also means you need a stable internet connection. Offline editing or working from low-connectivity environments can be inconvenient or unreliable.
Cost/licensing for full team features can be significant
While there may be free or low-tier plans, unlocking all collaboration, design-system, versioning or team-wide features for larger orgs can get expensive. For smaller teams or side-projects, this may be a limiting factor.
Learning curve & complexity — not always trivial for non-designers or beginners
Because Figma offers extensive capabilities (vector editing, prototyping, components, libraries, versioning, etc.), fully leveraging its power may require some ramp-up time. Beginners may find it overwhelming initially.
Not ideal for highly specialized graphic editing or raster-based work
While Figma excels at UI/UX—vector-based interface design and prototyping—it isn’t always a substitute for full-featured graphic editing (bitmap editing, advanced photo manipulation, advanced illustration, etc.). For those tasks, a dedicated tool may still be preferable.
From a CRO/UX lens: in complex, large-scale projects or teams, performance lags or licensing costs might impede agility; for smaller or early-stage teams, trade-offs between price and features need careful consideration. Review collected by and hosted on G2.com.