Will Figma become an awkward middle ground?

Original Article ↗ Hacker News Discussion ↗

Role of Figma in Workflow

  • Many see Figma as a “middle ground” between rough sketches and production code; some call it a “cursed midpoint” that causes double work.
  • Others argue that middle ground is exactly its value: fast, visual, shareable artifacts without needing to touch code.
  • Several people say Figma is unnecessary for solo devs or very small teams who can go straight from sketch/paper to HTML/CSS.

Design in Code vs Design Tools

  • A number of “codey designers” and engineers prefer to design directly in the browser (React + Tailwind, plain HTML/CSS, etc.), finding it faster and more realistic than pixel-perfect Figma work.
  • Others strongly caution against designing and coding at the same time for non-trivial products, citing wasted effort, poorer UX, and conflation of user needs with implementation constraints.
  • Some workflows: paper or Excalidraw for ideation → code; others: low-fi Figma/FigJam/Miro → code.

Collaboration, Scale, and Design Systems

  • Figma is praised for multiplayer collaboration, alignment across large teams, and shared design systems; this becomes critical at scale and for enterprise products.
  • It’s seen as especially useful for stakeholder alignment, hi-fi mockups, and consistent component usage when many developers are involved.
  • Several note that Figma is better for UX flows and interaction mapping than as a pixel-perfect graphics tool.

Code Export, AI, and Future of Tools

  • Opinions on Figma’s CSS/HTML/JS export range from “good” to “useless,” especially for complex responsive apps and emails.
  • Some expect AI and codegen to blur or replace the Figma layer (wireframe → code, design system–aware generation); others are skeptical due to missing training data, integration complexity, and platform variability.
  • Alternative or adjacent directions mentioned: tools that design closer to code (Webflow, Framer, Judo, tldraw, new “design–frontend hybrid” tools), or even Figma evolving into an IDE / “export as final app.”

Limitations, Pain Points, and Overdesign

  • Complaints: Figma feels too technical, laggy on some setups, poor at complex interaction prototyping, and creates a “fantasy world” for things like HTML email where constraints are harsh.
  • Some blame modern design culture: over-investment in esoteric Figma features, pixel-perfect fantasies, and design systems that never fully translate to working software.
  • Others defend UX as a distinct, necessary discipline; the problem is not the tool but designers who lack implementation awareness.

Designers, Developers, and Hybrid Roles

  • Strong debate over “designers who code”: some see combining roles as ideal (especially early-stage), others note it’s rare, tiring, and often slower than having separate specialists.
  • There’s interest in “design engineer” roles that sit between UX and frontend, but their exact mandate (how vs implementation) remains somewhat unclear.