6:55 @DesignCourse At the autolayout options you can just set from "Packed" to "Space between". That way you can resize the container however you want, because there will be no margin value between the two elements inside the container. I don't remember seeing you using space between autolayout option in the course as well as in RU-vid videos. Hope I was able to tell you something helpful.
Cool tutorial! I haven't used Figma in a while, but the prototyping process feels.. smoother? I've never been sold on the idea that we need a label above the search input (and really any element outside of forms when you usually would want to have them). It feels very unnecessary, especially in a navbar, and it's a really easy way to clutter your UI and create spacing issues, just like it happened to you at around 21:00.
Thank you for this video. I have made it like this but I want to know. I want to know if is it possible if I click one component that will open and the other component will be off.
@@vac1e I am transitioning back to Figma from XD (XD was corporate decision) and was curious on what's new, because with opacity the space taken by components is still there, and so if you have states on 'opacitated' children these may sometimes create unexpected results in parent in XD even when 'opacitated'. So barring animations, I'd rather turn visibility off on layers. But in Figma it seems clicking the eye icon opacity is the same as setting 0%, no? So why this way and is this a personal pref?
@@scrooge-mcduck No, it's not the same. You know Web development? I mean like the DOM structure. If you do know I can explain you hopefully. So Opacity is a thing you can animate, because you change the % value of the given item. But the show/hide is like visibility, it's a boolean value which means it's either true (visible) or false (hidden) or like display. If you set display to none it will take the given element out of the DOM.