Skip to main content

There are a couple of prototyping tools offering conditions in their prototyping process, such as UXPin, Protopie, etc.

This condition feature is just dope. I’m a big Figma fan though lover, so I’d imagine if Figma adds this condition feature, the whole prototyping would just blow. It would be a super feature.


Thank you guys at @figma

Hi there, I have been trying to create a questionnaire that has some logical conditions. I have yes or no questions and based on the answers I’d like to show a different set of questions on the next page. I linked the ‘Next’ buttons to separate pages whether the answer is yes or no (I created 3 different variants of the question component). But that does not work. How can we have different links in different variants? Isn’t it possible to do that? Many thanks for your help!



I think you can create all the possible answers and question and then combine them as variants within a component set then you should prototype each variant to its relevant possibilities.


@Figma_Support I’ve got lots of use cases with a very complicated web application. I need to present concepts to stakeholders and do users testing and am managing way too many screens to show things that toggle on and off on a “single screen” (X that by all of the screens across said web app). My BAs need to take these prototypes to FE/BE as well leadership needs them for a variety of stakeholder meetings. Please please add this feature. Loosing my mind over here managing agile work + complex prototypes.


Another Vote! I couldn’t believe this wasn’t a thing. I try to make a form with conditional rendering based off radio input and I went down a rabbit hole trying to figure it out.


Condition logic will be a real game changer in designing digital artifacts. Also real input box could help, but condition logic has to come first.


A use case for conditional logic and a context aware local components:


I have a local component that is shared across several screens. This component contain ‘Delete’ button that opens a modal with simple info: ‘Are you sure you want to delete…’. Modal has button ‘Confirm’ and ‘Cancel’ that have interactions that ‘Navigate to’ a specific screen.

Here is where conditional would be very helpful. And, also that a shared local component IS aware of its context. E.g. my shared component with ‘Delete’ button knows that it was clicked on screen A, so I can further redirect my interaction from the modal, to come back to screen A in a dynamic way.


Reply