Skip to main content
Question

Prototyping in Figma is Fraught with Bugs and Problems

  • October 14, 2024
  • 3 replies
  • 96 views

JimL
  • New Member
  • 8 replies

Every time I go to do some prototyping in Figma, I encounter a new bug or problem that causes me to spend hours trying to understand why it is happening and figuring out a workaround.

The latest is I have a button component nested in another component combined with other components into a form layout. The button has variants and nested components for icons, style, and state. I am trying to attach a variable to the state so that when clicked it will switch from default to disabled (So that people will perceive that it can no longer be clicked). As soon as I set the State to use a variable it breaks the button variant Style so that the hover and disabled states do not retain the overrides.

This is amongst several other issues including having the theme mode flash in the default theme (Dark instead of Light mode) for interactive components, and the infamous color change for instance swaps on nested components. And then to still not have proper drop-downs and actual text inputs or a table component just makes Figma a tedious tool.

I am at the point where I cannot trust Figma for prototyping. All the new features and functionality have made things very unstable for prototyping and I am having to revert to detaching instances and breaking things back to the basics to get them to work. Which defeats the purpose of things like variables, and instance swaps.

3 replies

Fred_Tinsel
  • Active Member
  • 110 replies
  • November 5, 2024

Yeap I can confirm…
Each time you want to make advanced prototyping using variables, you are getting in trouble, in particular with variants.
A simple example : A card with a button changing its size via variable depending on the breakpoint. On large screens, I want a large button → Text and icon overrides are lost.
Here is a demo :

@figmates


SomethingFishy

My general experience with Figma has been the same. I’ve been using it for about a year now and it never fails while I’m prototyping, things always go buggy. It seems the more complexity or nuance you try to accomplish, the worse it becomes, even for extremely common UI interactions. (How we still cannot pair smart animation with expanding accordions without some hacky workarounds blows my mind.)


Matty_Vazquez

Yep- been my experience too. It very much feels like the Figma folks rushed some stuff like variables out the door to make their Adobe acquisition that much more enticing. Yes, the community needed variables, but it’s just way too buggy.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings