forum.figma.com
DX for Plugin Development is terrible. - Figma Forum
Excerpt
I genuinely don’t understand how Figma continues to dominate given how hostile the experience has become — for both users and developers. The UX is chaotic and non-intuitive: layers buried under layers, controls hidden behind inconsistent interaction models, and navigation that feels designed to fight the user instead of helping them. For many people — especially neurodivergent users — the interface can feel actively exclusionary rather than empowering. It’s hard to shake the feeling that usability is no longer the priority. From a developer perspective, the situation is even worse. The platform is effectively closed. The MCP integration with Claude is read-only, and meaningful mutation requires plugins running inside Figma’s sandbox. There is no serious external API for programmatic design updates. That makes modern workflows — automation, CI-style pipelines, integration with engineering systems — far more difficult than they should be. Meanwhile nearly every capability surface seems designed to maximize monetization rather than ecosystem health. The result is a platform that behaves less like infrastructure for design systems and more like a gated environment teams are forced to work around. History is full of companies that confused market position with permission to squeeze their users and developers. It usually ends the same way: the ecosystem eventually moves on.
Source URL
https://forum.figma.com/share-your-feedback-26/dx-for-plugin-development-is-terrible-51914Related Pain Points
Closed platform with limited external API for design automation
8Figma'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.
UI redesign (UI3) makes common tasks slower and harder
7Figma'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.
Platform monetization prioritized over ecosystem health
7Nearly 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.
Interface accessibility exclusionary for neurodivergent users
6Figma'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.