community.latenode.com
My concerns about Figma's current path and decisions
Excerpt
div ... It all began when they limited dev mode to just 40 across every pricing tier. Then they started pushing AI features heavily while ignoring improvements to variables (which plugins can handle anyway). The price hikes made things worse. Solo designers and smaller teams are getting pushed out because we can’t afford enterprise-level costs. What really bugs me is how buggy everything has become. My colleagues and I deal with broken components every single day. Data overrides stop working, everything runs slow, weird glitches pop up, files don’t load completely, and properties just disappear. This stuff makes it really hard to get work done. They keep adding things like AI tools and presentation features that feel disconnected from what we actually want. We need them to fix variables, improve component variants, and make the whole platform run smoothly again. These new flashy features don’t help when the basics are broken. … Ditched Figma six months ago for the same reasons. Final straw was when components started corrupting design systems we’d built over years. Management wanted us to stick with it because of licensing costs, but we were spending more time fixing bugs than actually designing. Switched to other tools and don’t regret it. Yeah, the learning curve sucked at first, but having stuff that actually works made it worth it. ... Your frustrations hit close to home. I’ve watched Figma go from this scrappy, designer-focused tool to something that feels corporate and disconnected from actual design work. The Adobe acquisition definitely accelerated this more than anyone wants to admit. What bothers me most is they prioritize investor-pleasing features over stability. Those AI integrations and presentation modes might look good in board meetings, but they’re useless when your basic workflow crashes constantly. … totally feel u on that! seems like they are more focused on adding stuff than fixing the core issues. it’s like they don’t realize we just want a smooth experience. ... Been there with tools that promise everything but deliver headaches. The pricing games and feature bloat sound way too familiar.
Source URL
https://community.latenode.com/t/my-concerns-about-figmas-current-path-and-decisions/38843Related Pain Points
Core platform stability issues with broken components and data loss
8Figma 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.
Dev Mode limited to 40 seats across all pricing tiers
7Figma 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.
Price increases (20-29% for Organization plans) with forced bundling
6Figma'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.
Platform shifting focus away from core design features toward developer tools
6Figma 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.