Skip to main content

LAUNCHED: Support Auto Layout in Interactive Components


Show first post
This topic has been closed for replies.

78 replies

Kenneth_Lindbeck-Dahlstrom

+1 on this, would be great to see if there has been any progress on this 6 months in 🙂


Ollie_Barker

Yeah it’d be great to get an update on this, at a minimum proper AL support. I’m in the beta but I can’t really do anything with it until this works 😭


Wesley2
  • 1 reply
  • August 10, 2021

Interactive component has an expand function, an extra description that slides out under the title when clicked on.

The interactive component is placed in a list component with multiple instances. When I click the title in the prototype, the text expands, but the other items don’t slide down. But if I change the state of the interactive component within the list component outside of the prototype, on the artboard, then it does work.

Both the list and the interactive components are set to ‘hug contents’ for their vertical height.



Yulia
  • 39 replies
  • August 13, 2021

we’re waiting, and waiting, and waiting… 🤷‍♀️


craigmurdo_fs

Come on Figma! Give us an update please 😅


Grahammertime

This will be a game changer


andreyveda


When I change the component, Auto Layout does not work in the prototype


Slava_Bronevitskiy

Any sight on the release date?


Doug_Wickham

@anon21722796
Any idea when this will get updated? It would cut down on some much prototyping and make Design System elements so much more powerful.


Jeff_Olson

This would be such a HUGE benefit to prototypes. And YES DS components behaving this way would be much easier to illustrate to stakeholders!


Leo_Sarmento

I´m using interactive elements, as it reminds me another prototyping tool that had a similar feature.
But I´m missing a feature. Pushing objects and components when changing the variant on the go.
It works when editing perfectly, pushing everything around. But when presenting the prototype the new variant overlaps the other elements.

If you could fix this it would improve immensely the possibilities.


Kevin_Chiang

nikolasklein just want to say that this is so crucial for my team as well, glad to see it’s being worked on! We have a lot of form fields and accordions that need to expand and collapse in our prototypes.


Sam13
  • 1 reply
  • August 30, 2021

Hi guys,
Same problem here and we need to have a solution as soon as possible. I think - this is a very crucial problem and would make figma more attractive for developers.

Could someone provide an update of the status of this feature??

Best Regards from Germany


Eric
  • Author
  • 20 replies
  • September 1, 2021

Bumping because I am OP… 😛


seazona
  • 1 reply
  • September 2, 2021

Diving into Figma and very intuitively expected auto-layout behavior in preview mode and was surprised to learn here that it’s not yet an active function! The great thing is that I set up my components and auto-layout rules correctly without needing any documentation, so thank you Figma for a great UX here. Now it’s just about getting that feature unlocked in preview mode at some point.


Steven_Hines

Any update on a release date? IC has been in beta for 6 months now 🥺


Ariel_Cavalcante

@figma @anon21722796 You got me interested then disappeared. Stop ghosting me.


Myron_McMillin

+1 I have been pulling my hair out with this one. Finally gave up to report the issue and see this thread.

It seems like building interactive component accordions in a prototype is what brought many of us here.


Eric
  • Author
  • 20 replies
  • September 14, 2021

As a random thought. Most of the time, “everything is a list” and usually I want to modify a state of a component IE) card/list/animation grow. This could also be considered a “transition” to another state of the component.

Usually I don’t want to proceed to the next “page/artboard/screen” until I’ve finished X number of tasks on that “page/artboard/screen”. The nice thing in Figma is I can have multiple on one page and multiple on one target.

The missing piece is that it doesn’t change the page appropriately as we’ve all commented now, the natural flow is that I want to complete X actions/transitions per page, before establishing the move to the next major artboard/screen.

This could indeed be a tab on top of a screen, on top of a already transitioned menu, so you’re basically 3-4 “actions/transitions” deep, before the demo task is setup/completed and I want to trigger onto the next screen.

The upside here is that, if you had a user flow with like say 15-20 screens, you could easily bring that down to 5-10 no problem. The only thing to watch, is that it doesn’t get difficult for others to understand what animations/transitions are happening, IE) things are set to 0% opacity and aren’t showing, things have a radius set, and all the other tricks that are used to create the desired effect. it needs to very easily understandable and easily visible to someone who didn’t make it.


Eric
  • Author
  • 20 replies
  • September 14, 2021

I didn’t even start any personal projects because I’m lazy, and state changes of components like this, will save a solid 30-40% of screens in a user flow.


Cody_Gagnon

+1 Support for auto layout with interactive components is essential. Hope to see this soon (or at least get an update).


Adam17
  • 1 reply
  • September 17, 2021

+1 I’d love to see this feature in the prototype view.


Axel1
  • 15 replies
  • September 21, 2021

I also need this feature so desperately! This is so essential and would save so much prototyping time and effort.

Figma, pleeeeeeeeeeeeeeeeeeeeeeeease! 🙏 🥺


Romia_Aksan

Kind of expected auto layout to work…
Any news on a (expected) release date?


Bendik
  • 2 replies
  • September 23, 2021

Hi! Just want to say that this feature is urgent for many of our designers. We are over 70 designers working with prototyping for user testing every week.

I hope you will get this working as soon as possible.


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