Should all site design details be enclosed in autolayouts?

Question

Design

Should all site design details be enclosed in autolayouts? And in general, the main purpose of their creation?
Well, auto-layout buttons are understandable. Some in the lessons generally wrap everything with them - what is this for?

Answer 1

Ideally - yes, in fact - it is most often not worth it, below I will explain why.
* In general, if you have such a question, then you most likely do not need it.
There are two main goals:

1. Automatic layout rebuilding in case of using components
   Here you have a traditional, favorite design entity "card".
   It is moved to a component and used on N pages approximately N * 50 times.
   A client comes and says: I want to add a big red button to the bottom of the card.
   You add a button to a component.
   If both the component itself and all the parents where it is used are made using autolayouts, then your work ends, all pages look as they should.
   If there are no auto-layouts, welcome either to "move all instances on all pages by hand" (which is tedious, boring, and if the client changes his mind tomorrow, then in general lol), or to "well, here on the "Card v2" page I showed how must be" which after a while leads to a mess on the project, in which it is impossible to find ends.
   
2. More confidence that everything is
   even. This results in the fact that it is more pleasant for the layout designer to work on the layout - he sees the autolayout and he is immediately sure that the indentation between all elements is the same.
   Most likely, it will be possible to make `pixel-perfect`, if it is important for the customer. And without autolayouts, you may have a situation where there is a different indent between identical elements.
   * It will not be necessary - you can be careful, but the extra confidence is good for everyone. Technology insures against mistakes.
   

Now about why not.

• In order for autolayouts to help the process, and not interfere, you should have a complete idea of ​​​​what you want to get in the end even before starting work.
  If you are in the process of creative search - draw as you draw. Once everything seems to look good, think about layouts.
  
• When you need to design a complex, composite component with different options - you really need to design it , according to subjective feelings, this is much closer to layout than to design - and this is a completely different profession, and you need to think differently there.
  For me, when I get to draw, the components are structurally almost the same as they will be on the layout later - and this is great in the long run - there is less mess.
  But I am primarily a technical specialist, and a designer does not think (and should not think) like a layout designer, and will do a little wrong and a little wrong. From the outside, it will most often look like "I created problems for myself out of the blue."
  In addition, this has disadvantages: the component becomes more complicated (sometimes it is directly noticeable) than if you simply arrange elements inside the frame with the mouse. This affects how easy it is for another person to figure out what's going on and make their own changes.
  
• Figma does not (yet) have absolute positioning. While there is a 0/0 width/height frame hack in progress - but this is exactly what a hack is, it increases the complexity of both development and support. Complex components without this are not wrapped in autolayouts in any way.
  
• Not very experienced designers are seriously limited by autolayouts in their creativity - the design turns out ... Well, square, or something.
  
• Not all things can be implemented on autolayouts
  

Everything needs a measure. It should be convenient, fast, reliable and understandable to the team.
And where is this measure - well, everyone decides for himself, right? :)