What Figma users actually want
Mimir analyzed 14 public sources — app reviews, Reddit threads, forum posts — and surfaced 10 patterns with 7 actionable recommendations.
Top recommendation
AI-generated, ranked by impact and evidence strength
Launch bidirectional design token sync with automatic code generation for CSS, React, Swift, and Compose
Rationale
16 sources show that design-developer alignment is a critical friction point, with teams losing design intentions during handoff and struggling to maintain sync between Figma and code. One engineering manager noted that before Dev Mode, "maintaining up-to-date design system documentation felt" impossible. The solution already exists in fragments: Dev Mode's Code Connect, Variables Converter plugins, and the REST API enable bi-directional syncing. But these require manual integration and custom plugins.
Consolidating this into a native feature would eliminate the translation gap. Users report that Code Connect "significantly improved design-to-development workflow by linking Figma components directly to actual component code," but this only works one direction. An engineering manager built a custom Variables Converter plugin to translate Figma variables into multiple code formats—proving demand for automated, multi-platform code generation that stays in sync as designs evolve.
Without this, teams continue to spend engineering time on manual translation, design systems drift from implementation, and the promise of Figma as a single source of truth remains incomplete. This directly impacts retention for engineering leads who evaluate Figma based on workflow efficiency, not just design quality.
More recommendations
6 additional recommendations generated from the same analysis
7 sources report that the inability to nest interactive elements inside other interactive elements is a fundamental design constraint forcing workarounds. Users encounter this limitation repeatedly across different projects, and while a debug toggle exists to suppress warnings, it doesn't solve the underlying problem—designers cannot model real-world component hierarchies where buttons live inside cards, tabs contain forms, or navigation menus include interactive dropdowns.
24 sources show AI-powered design-to-code automation is central to Figma's platform expansion, with Figma Make enabling users to build "complex applications (e.g., farmer marketplace) in weeks." Users describe building real estate sites with lead capture forms connected to backends, and product managers using Make prototypes "as alternatives to traditional PRDs." The value is proven: no-code creation eliminates weeks of development time.
25 sources document a vibrant template ecosystem (Design System Generator 17.8k users, Nuxt UI 13.1k users), but staleness is undermining value. The Online book store landing page template was "last updated 1 year ago—relatively stale compared to active template ecosystem," yet it still has 1.2k users. Users rely on these templates as starting points, and outdated templates teach bad patterns, use deprecated features, or fail to leverage new Figma capabilities like variables and auto-layout improvements.
8 sources show users are building real products with Figma Make: dashboards, marketplaces, real estate sites, internal tools. They're using Figma Sites and Make to ship without code. But each use case requires the same foundational integrations—Stripe for payments, Auth0 for authentication, Segment for analytics, Salesforce or HubSpot for CRM. Users are currently configuring these from scratch, which reintroduces technical complexity.
5 sources report that critical features like screen reader support and hardware acceleration are disabled by default, requiring users to navigate through "multiple steps (Ctrl+K → Accessibility Settings)" to enable. This creates unnecessary friction for accessibility adoption and performance optimization—two areas where default settings should prioritize best practices, not user configuration.
2 sources indicate that sign-up walls prevent unauthenticated users from commenting, editing, and inspecting files, while view-only mode requires account creation. This creates friction for open collaboration and feedback collection workflows, particularly when teams want to gather input from external stakeholders, clients, or users who don't have Figma accounts and may never need one.
The full product behind this analysis
Mimir doesn't just analyze — it's a complete product management workflow from feedback to shipped feature.
Themes emerge from the noise.
Ranked by severity and frequency, with the original quotes inline so you can judge for yourself.
Talk to your research.
Ask questions, get answers grounded in what your users actually said.
What's the top churn signal?
Onboarding confusion appears in 12 of 16 sources. Users describe “not knowing where to start” [Interview #3, NPS]
A prioritized backlog, not a wall of sticky notes.
Ranked by impact and effort, with the reasoning you can actually defend in a roadmap review.
PRDs, briefs, emails — on demand.
Generate documents that reference your actual research, not generic templates.
Paste, upload, or connect.
Transcripts, CSVs, PDFs, screenshots, Slack, URLs.
This analysis used public data only. Imagine what Mimir finds with your customer interviews and product analytics.
Try with your data