Figma

Figma experiences significant frame rate drops (15-20 fps) when screen sharing in Microsoft Teams or Zoom, making the application essentially unusable during client presentations and undermining confidence in the design process.

Figma's platform is effectively closed for programmatic design updates. MCP integration with Claude is read-only, and meaningful mutations require plugins running inside Figma's sandbox. There is no serious external API for automation, CI-style pipelines, or integration with engineering systems.

Figma experiences pervasive bugs affecting daily workflows: component corruption, data overrides failing, slow performance, files not loading completely, and properties disappearing. These stability issues make it difficult to use the platform reliably.

Figma's UI3 interface redesign has made previously simple workflows more cumbersome. Functions that took a couple of clicks now require multiple steps, and frequently-used features are now hidden or repositioned, disrupting muscle memory and slowing down daily work for power users.

Apps starting without a design system face fragmentation as designers create clashing components and developers reuse elements incorrectly. As apps grow, UI becomes harder to maintain without consistency and shared rules.

Figma restricted Dev Mode access to only 40 people per workspace regardless of team size or pricing tier, creating bottlenecks and artificial limitations that force teams to choose between design and development workflows.

Even high-end MacBook Pros experience hitching and lag when working with deeply nested components and large design system files. Performance degrades with UI3 updates, and the issue compounds—more component references worsen performance, which is ironic given that components are meant to keep things organized.

Nearly every capability surface appears designed to maximize monetization rather than support ecosystem health. The platform behaves less like infrastructure for design systems and more like a gated environment teams are forced to work around.

Figma Dev Mode exports static layouts and styles but doesn't handle critical production requirements: state management for interactive elements, component logic for complex behaviors, API integration, or responsive code. The generated code requires extensive manual refactoring by developers.

Without automation, developers spend significant time extracting assets, copying styles, converting layouts, and aligning typography. This manual work slows development cycles and introduces errors, especially in large-scale applications.

Figma is adding dev-oriented features like code blocks to Slides while neglecting core design functionality. Long-time users perceive a strategic shift toward developers and coding rather than design, causing concern about Figma's identity and priorities.

Figma's chaotic and non-intuitive interface can feel actively exclusionary rather than empowering, particularly for neurodivergent users. The complex navigation and buried controls create barriers rather than facilitating design work.

Figma's March 2025 pricing changes included 20-29% increases for Organization plans, with forced bundling of FigJam and Figma Slides. Teams that don't use these products are now required to pay for them, feeling like they're subsidizing unwanted features—likened to cable TV bundling.

Figma's file management remains a significant challenge, with designers spending excessive time organizing files rather than focusing on actual design work. Navigating through projects feels cumbersome, especially when working on multiple simultaneous projects, due to lack of robust folder structures and intuitive grouping options.

Figma lacks native z-axis and 3D transforms that CSS has supported for years. Designers need paid plugins or third-party workarounds just to visualize basic 3D rotations that developers can implement with a single CSS line.

Figma locks the order of variable collection modes at creation time. Adding a new breakpoint mode after initial creation places it at the end permanently. Reordering requires rebuilding the entire set from scratch, with no drag-and-drop interface.

Designers work with pixels and layers while developers think in components and logic. This fundamental disconnect causes challenges when translating intricate layouts into maintainable code, compounded by lack of standardized design systems.

Figma lacks offline functionality, forcing users to have continuous internet connectivity to work with design files. This limits usability in offline or low-connectivity scenarios.

Nested component instances are collapsed by default in Figma, forcing designers to manually open each accordion for every instance they need to customize. This creates repetitive, time-consuming work that wastes productivity.

Figma Sites can generate web pages but lacks CMS functionality (pending for later release), making it unsuitable for content-heavy sites or scalable web architectures that require dynamic content management.

Figma requires designers to edit text style properties (like line height) individually across all styles, even when organized in groups. Updating a property across 60 text styles requires 60 separate edits instead of group-level batch operations, creating tedious, time-consuming, repetitive work.

Figma's aspect ratio lock works correctly in the properties panel but fails inside auto-layout components. When aspect ratios should remain consistent during dragging or component resizing, they break unpredictably.

Figma's Recent Files feature displays inconsistent results, often showing files the user doesn't remember working on and failing to show actual recent work, making it difficult to locate files quickly.

Figma's Dev Mode turns on by itself unexpectedly, interrupting designers' workflows. This creates friction when users are trying to focus on design work rather than development features.

When implementing from design mockups, coding assistants often generate images and icons that don't exist in the original Figma designs. Fixing this requires explicit instructions and direct links to specific Figma nodes.

Figma accounts show different interface layouts and experience random updates that disrupt consistency between work sessions. Users with multi-account setups report layout variations that complicate workflow management.

Figma's built-in illustration features don't match the capabilities of dedicated illustration software, forcing designers to switch tools for complex custom visuals and limiting the ability to create expressive graphics entirely within Figma.

Figma's 'Drafts to move' feature creates unnecessary friction in file management workflows. Users find it confusing and report it adds complexity without clear value.