It’s my first day of using Figma and I have found my way to this thread… Disappointing

Still very much needed feature!

This is definitely the first thing I think when comparing in my head Figma to Axure. This feature would change a lot in my daily workflow, where I am forced to duplicate screens to be able to simulate this effect. Would ❤️ love to have this thing in Figma 🙏

And on that occasion thank you Figma designers and devs for great, amazing, and stunning work!

I got very excited when I saw this thread started way back in March 2021, and very sad when I saw the last ask for this was 9 days ago 😦

Not sure if it’s helpful, but I’d certainly like to add my +1 for this functionality.

Also adding my +1! I don’t want to have to fake the interaction by making a whole new canvas 🫣

It would be very helpful if Figma release such feature 🙏

Agreed. I’m running into the same issue mentioned previously where I need a combobox menu selection to add or remove fields from a form. Being able to change the state of another component would really help simulate more complex interactions like that.

Here I was hoping this type of interaction was possible without making a whole new page. I’m new to Figma, but adding my voice here to say this feature would be a huge time saver.

Voting this feature up as it is a ginormous must-have! Let’s get it in the air ASAP Figma! 🤓

It can be replicated by adding more frames/canvas, but darn… that is such a workaround!

+1 for this, sometimes we need to protype interactions in which multiple parts of the UI have to be coordinated and it doesn’t make sense to have everything as a component variant

This became possible from June 21, 2023. I also answered you here: Change variant of a component from a different component - #2 by tank666.

The container components is great in some situation, however, when the first component set control a video play, that triggered by a play icon, and the video rectangle also hold a role of these variants. The other component set is the animation of timeline, which process after the play icon is clicked. I have no idea when they are in different components,

Fortunately we have variables now, and the patter I suggested is no longer needed.

That you actually can do right now.

You can create a boolean variable (true/false) and connect that buttons visability to that variable. Then you add a click event to the checkboxes that change the value of that same variable.

True, there are tons of prototype things that Figma can learn from Axure, Our team has been using Axure for a long time, and we recently want to change to Figma, so our docs, prototypes, and UI can be All-in-one. but sadly, Figma can’t prototype a lot of things! One of the very important reasons is it can’t interact between components!!!

So, I don’t know if this will help anyone out, but something I figured out last night is that you can makeshift some component-to-other-component control by using the “Mouse enter” option on interactions. So the way that looks is that, on the frame where I have the page built out, I go to Prototype, add an Interaction, and select “Mouse enter”, which then gives me the ability to set a Conditional action.

So for example, for me, I was trying to build a dropdown field (as the only field on a multi-step form page) that had multiple options that could be checked on. Below the field was a Next Button. I wanted that button to be gray until they checked at least one option on that field. Once they selected one or more options, I wanted the button to become colored. I couldn’t find a way to conditionally change the variant without a “Click” action on the button itself. I wanted the variant on the BUTTON to change when the CHECKBOX was clicked on the field component. But that’s not really baked into the new functionality yet, it seems. So by having a “Mouse enter” interaction on the page, the conditional logic starts working immediately as soon as the page loads pretty much.

Hope that helps someone else out! And feel free to tell me if there’s an easier way to do what I’m saying.

Changing states of components from any other component would give us so much prototyping flexibility and give us more legit coding like behavior. This is how OOP programing works, components can communicate with each other and change each others states.

Let’s say you are designing a simple game, you might have a score component, and a ship component, and an enemy component, then when the ship destroys an enemy, the score component gets updated. You wouldn’t have a giant game component that has every possible variation of destroyed enemies and scores.

Hey Brady 👋

I’ve the same exact problem than you and I found your comment really interesting! Is there a way for you to share a copy of your doc? I’m having a hard time reproduce what you’ve done… Thank you 🙏

For the time being, I’ll send you a direct message with a link to view it. I’ll create a modified version to publish to the Figma community at some point so that everyone can view it. But this was being done for a client, so I need to make it a bit more generic before I post the example to the public.

Thank you so much for your quick answer Brady 🙏

I think this may be helpful. You can achieve it with variables.