I started using Figma by just exploring and without taking any proper courses! and I've been finding ways to properly create components but couldn't really find it. This is very very very helpful!!! Subscribed to your channel and gonna go through the videos that you have! THANK YOU!
Awesome video! Please do more videos on design standards! I am learning Figma well but can’t find any info on standards of practice. This is just what I was looking for
This is amazing i was learning and this one video thought me a lot. I was making these mistake and didn't knew why and how things are working. Much help thanks man.
I love this video so much! I started with Figma a few weeks ago, watched some tutorials a this one really helped me understand the components. Thank you!
Thank you very much, this is very informative and helpful. But, autolayout is terrible to use in parts. Definitely missing options for better use here from my point of view. Especially for nesting objects and more complex layouts
It works like flexbox so if it doesn’t work in auto layout it’ll probably be difficult to impossible to develop. The only thing that is missing is a z-index of some sort but you can get around that with image fills and regular frames
Actually, auto layout make much more sense because that is the way how code works in web( CSS ), iOS( SwiftUI ) or Android (Jetpack Compose). So better think in advance than afterwards.
@@figurich That is all clear to me. Autolayout is great. When I create complex boxes and have to interlace them with others, I often have to edit all the constraints again (in detail) because the responsive behavior doesn't work anymore. Maybe this could be improved overall... Like "keep settings / behavior" ONLY that is the point ;-)
Hello sir, I am happy that I found you on youtube. Such a great and very helpful channel for learning Figma. Sir, I have a very humble request to make a video explaining "The correct usage of Constraints & resizing while applying Autolayout- What happens if we use the Fill container, Hug content, and so forth". This is the crucial topic, I guess, we newbies mostly go wrong with them, so I am hopefully looking forward to you for the great help as usual. Thank you very much, sir.
Stellar tutorial mate. I unfortunately fall into the first boo boo! LOL! It's videos like yours that help make us all better designers. Want to WOW your design team? == add small component interactions like AM did in his menu example (#1) The little things like this make a designers day/week. I can attest to this in real life.
Thank you so much, very well explained, useful tips! I am also curious if I didn't add a base component from the beginning, can I do it afterwards and "attach" it to existing variants or I have to recreate everything from scratch?
Thank you Alina. You can attach a base component afterwards but that will mess up the instances that have been used throughout the product. So if you haven't done that, you can leave them, it's not the end of the world, but try to do that the next time you create a component to save yourself time and effort.
Very helpful video from someone coming from XD. When using the base structure component for a set of components, let's say a button with a right arrow, hover and inactive states, and in the future, a left arrow variant is needed. In this case would you have to add the arrow to the base component and then delete it manually from all the component variants that don't need it?
Well, I'v e made some of these mistakes but I think my biggest mistake was not creating a base structure. That is genius and will be doing that from now on. It makes so much sense, I've never seen that before in an video. I think Figma should be promoting that in their office hours videos too. I see to many people create a lot of extra buttons and having to make multiple changes. THANK YOU!
Hey there! I have a question about the ' Not creating components for reusable elements' part. Are the items (Home, About, Locations etc) in that header just instances of components and the header is a component? I was just listening a tutorial from Mavi Design called 'Components inside components' and he said that you should create only one item component, define structure and states and then use just instances of that item component in header. Do you agree with that method? I just wanna clear some things up in my head! Thank you!
Great video, thanks for sharing. However, creating variants using this base structure I don't appear to be able to change the border radius as a property. So do I need to create a separate button base structure for rounded, straight, pill etc ? Many thanks in advance.
@@AMDesignAndDev Thanks so much for the prompt reply, I've now fixed this. However I have another question - is it possible to add a hover colour to the base structure of a button which - when changed - filters down through all the different button variants? The reason being that I plan to use the same button styles throughout multiple projects but the colours will change all the time depending on the project and I'm trying to avoid changing all the colours for each variant each time. Thank you.
@@rookie1969 You can if you want to, but the purpose of the base structure is to define the sizing etc. If you want a base structure for states separately, you can create 2 levels of base structures, but I would not recommend it. So I'd say, do not do that, and have the state specific styling on the main component itself.
You can check some of my other videos where I show you how to create components. Figma Noob to Pro! 04: Components ua-cam.com/video/tDOGUC6L7Vo/v-deo.html Etc I recently have also started creating a design system playlist, so do check it out
I've used Figma in the past but have to come back to it now as I need to use it for some projects. This is really useful and up to date which when looking for useful tips for Figma amongst the thousands is hard to come by! So many video tutorials are out of date. However, could you slow down a little bit when explaining? I followed it all and it all makes perfect sense but you talk too fast and thank goodness for no background music!
Sure Karen, I've heard a lot of people want me to slow down, and in my recent video, I've tried slowing down. So keep in touch and keep letting me know if I should improve elsewhere.
@@AMDesignAndDev Awesome tutorial indeed! I personally don't mind the fast pace, you can always set playback speed anyway, though I agree a slower pace would be better for most. What I find a bit confusing is your use of keyboard shortcuts. Sure, we can see them flash on the screen, but as this video was intended for noobs, it would be a nice addition to mention them at the very least.
How about doing a component for the whole navigation bar and make variants with each of the elements highlighted? I believe it would be easier and faster
I'm just thinking about how best to handle the "base structure" / master component in case I need a primary / secondary button and also a small / large. Is only one master component enough? Would you like some advice? Thanks
Very useful video, as a person who used to create all designs in Adobe XD, there is one feature I can't seem to figure out how it works in Figma. In Adobe XD there is a feature where you can create a component and use the instance of that component and add elements to that instance while still preserving the style of the master component. However in Figma, it does not see that's possible to add elements to an instance but only change / delete elements that already exist. Is it possible to add new design elements to an instance of a component without touching the master component but the instance itself?
Yup, text inputs, dropdowns, checkboxes, labels, tags, basically a lot of things, anything that's repeated a few more than a few times, I prefer using base components for them.
@@AMDesignAndDev good stuff. With inputs, do you create each atom as individual components (label, placeholder text, input box, error messages etc) and then combine them together into one base component? Or do you just have one single base component that contains it all in one?
Hello Thanks for this.. i converted the "Header Active and Inactive state to Combine Variants, but when i tried changing the Active and inactive states of some text in the Header, they changed the original texts to HOME instead of maybe LOCATION, ABOUT, CONTACT. please how do i solve that?
how to duplicate auto layout object inside components? is it possible? So, this is my step by step, until I ask this question, 1. I create an object, ex. Button > Convert to component 2. Drag the button from local component, > Copy button (5 buttons) > Convert to autolayout > Convert to component, and finally, I got a new component and give the name as "tab". 3. Then, I drag the tab from local component, > I try to jump into the tab component, and try to duplicate the button, but nothing happen, it comes to a new component, not like when we create a basic autolayout, we can easily to duplicate the object inside the frame.
AHAHA, they will learn over time, if you get a chance, create a component for them, and once that's done, they may probably understand its value over time, especially when they have to make changes.
Valuable advises! I'm curious how would you create a calendar with components/variants when it is selected a circle with the number will appear. I've done this and let's say the component is 1 default and 1 click with circle background, or whatever. But when I select, for example, another number 12 or 28...etc, I get the same number as in component - 1 circle (and not the initial number I need to be as selected). Should I make all the numbers default and selected as variants?
I think that’s happening because you have not renamed the text in your component in correctly you only need to create the variance once and then if you apply those variance in different components or different date it should work without the text reverting back to the original variant text
So basically a Large Button should be it's own component with it's own states rather than being a variant within a smaller button? So a mobile width button should again be it's own parent component rather than a selectable variety within a different button?
If you put in all possible atoms within a component and just use component properties, is a base structure necessary? Unless you missed a possible atom wouldn't this cover all your bases?
@@AMDesignAndDev Yea sorry, should have looked through the comments. Thanks for your proto vids, its really opened up my thought process on what's possible on figma. Do you happen to do design critiques or have forum like on discord or patreon?
Although the video is a good reminder for mistakes to avoid, the person here is making some very mig mistakes, maybe unconsciously. To everyone else who is reading this - in the early part of the video around 3 minutes he is talking about menu items where he creates 2 separate components for active and inactive items. That's a mistake in itself as variants could have been created with color property, and a boolean property to turn underscore on or off. The bigger mistake was aroun 3:50 where he is actually using "instance swap" to replace active component with inactive component to which he is referring as "variants". That's a big mistake and new designers will be harmed by that. Instance swap and variants are very powerful features and cannot be used interchangeably. I did not watch the full thing after that but the author should either place onscreen corrections or take down the video.
Wow thanks for your valuable contribution! This is why one should try watching the video instead of making quick assumptions. I intentionally made those mistakes so I can correct them later in the same video. Mistake 3 talks about not creating variants within the same component group (for default/active state) Mistake 4 talks about not naming them correctly and not using the boolean toggle for certain variants.
@@AMDesignAndDev You are welcome! Next time you can keep this feedback in mind. Also it's always a good idea to get content reveiewed before publishing.
Aware this is an old tutorial but Figma on their recent building block webinar advised against using base components. The explain some glitches it causes towards the end.
I started using Figma by just exploring and without taking any proper courses! and I've been finding ways to properly create components but couldn't really find it. This is very very very helpful!!! Subscribed to your channel and gonna go through the videos that you have! THANK YOU!
Brother... I made so many design system without making a base button for variants. O my god. Thank you for that tip!
Awsome!!! This video helps me a lot! Thanks for sharing! Looking forward to more Figma related video!
Awesome video! Please do more videos on design standards! I am learning Figma well but can’t find any info on standards of practice. This is just what I was looking for
Hey, sure, I can have a look at it.
Maybe you will look once at my tutorials
This is amazing i was learning and this one video thought me a lot. I was making these mistake and didn't knew why and how things are working. Much help thanks man.
Broooooooooooo! you taught me so much in such a short space of time. Thank you.
Glad I could be of help!
Great video, thanks for sharing!
Taking time to avoid huge maintenance issues afterwards. Tks a lot.
Thanks a lot! Having a Base Structure is really gold!
Behtareen bhaijaan, I was getting the same issues, keep posting these types of issues
Brilliant video. Thank you for the tips!
Super useful easy and needed video!!!!!
Thanks!
kudos to you bro, lots of love from india 👏
Thank you so much! It is very useful for newbies!
This is one of the best video I’ve seen.
That was amazing. Please make more videos like that.
Will do sir :)
that's a quality content I've been looking for
thank you, sir
Thank you so much for this insightful video, God bless you
Excellent video ...............................Thank You !!!
Assalaamualaikum brother, your videos are very helpful! JazakAllahu khairan
Walaikum As Salam brother! Wa iyyaka
Thank you so much for this video! It helped a lot!
first two words were enough to know i am at a right place, thanks a lot.
This video just made me subscribe! You won me over with your focus on proper fundamentals. Thank you for this!
good knowledge i learn from this video, looking for more mistakes to avoid.
Thank you this was very helpful!
Thanks man , keep the good work up
great tutorial video, so much to learn in a single video. it really helps us where we lack.
Appreciate your point of view, great pointers!
thank you thank you thank you!! exactly wha ti was looking for!
Yeah, definitely worth to remember about those things!
Really helpful!
Great tips, thank you!
Wonderful and informative.
Keep making these, they sure help newbies like me.
Will do Ali :)
I love this video so much! I started with Figma a few weeks ago, watched some tutorials a this one really helped me understand the components. Thank you!
thank you so much Sir.. Specially for 5th one..
Awesome video! Thank you!
Great video and really helpful! I couldn't get a grasp on how the setuper works but it's all clear now.
super clear and helpful. thanks so much !!!
Thank you!
Practical content. Keep it up
Well explained
That's a great video for someone starting to learn Figma. Thanks!
🥺I feel so grateful, thank you!
You’re welcome 😊
Atomic design approach 👌🏾👌🏾
Amazing video! I don't have the resizing option in the right side, why is that?
This is gold, very important content for us newbies with Figma, thanks!
Very insightful.
dude, you're the best!
Means a lot :)
Thank you very much, this is very informative and helpful. But, autolayout is terrible to use in parts. Definitely missing options for better use here from my point of view. Especially for nesting objects and more complex layouts
Thanks for the feedback, it definitely has limitations, but in my opinion, it’s much better than going all without.
It works like flexbox so if it doesn’t work in auto layout it’ll probably be difficult to impossible to develop.
The only thing that is missing is a z-index of some sort but you can get around that with image fills and regular frames
Actually, auto layout make much more sense because that is the way how code works in web( CSS ), iOS( SwiftUI ) or Android (Jetpack Compose). So better think in advance than afterwards.
@@figurich That is all clear to me. Autolayout is great. When I create complex boxes and have to interlace them with others, I often have to edit all the constraints again (in detail) because the responsive behavior doesn't work anymore. Maybe this could be improved overall... Like "keep settings / behavior" ONLY that is the point ;-)
Hello sir, I am happy that I found you on youtube. Such a great and very helpful channel for learning Figma. Sir, I have a very humble request to make a video explaining "The correct usage of Constraints & resizing while applying Autolayout- What happens if we use the Fill container, Hug content, and so forth". This is the crucial topic, I guess, we newbies mostly go wrong with them, so I am hopefully looking forward to you for the great help as usual. Thank you very much, sir.
yes i do agree with you
Thank you for the helpful video. If possible please add the shortcut keys which you have used, that will also help us.
This is such a useful tutorial thank you so much
Glad it was helpful!
Very helpful, wish I saw this earlier
It was great as always. If you can make a practical video on how to use colors in user interface design.
Sure Yusef, I can have a look at that.
Very valuable. Thx!
Top job, sir.
Stellar tutorial mate. I unfortunately fall into the first boo boo! LOL! It's videos like yours that help make us all better designers. Want to WOW your design team? == add small component interactions like AM did in his menu example (#1) The little things like this make a designers day/week. I can attest to this in real life.
Thanks mate :)
Thank you so much, very well explained, useful tips! I am also curious if I didn't add a base component from the beginning, can I do it afterwards and "attach" it to existing variants or I have to recreate everything from scratch?
Thank you Alina. You can attach a base component afterwards but that will mess up the instances that have been used throughout the product.
So if you haven't done that, you can leave them, it's not the end of the world, but try to do that the next time you create a component to save yourself time and effort.
Where do you get all those nice colors you had?
Very helpful video from someone coming from XD. When using the base structure component for a set of components, let's say a button with a right arrow, hover and inactive states, and in the future, a left arrow variant is needed. In this case would you have to add the arrow to the base component and then delete it manually from all the component variants that don't need it?
Yea, In Figma you can’t delete items from an instance like in XD, so you’ll just be hiding the arrow.
What UI kit or template are you using that has all of the color and font styles you're using here? (Great video!)
I think its tailwind Ui Css from some Figma community file.
Well, I'v e made some of these mistakes but I think my biggest mistake was not creating a base structure. That is genius and will be doing that from now on. It makes so much sense, I've never seen that before in an video. I think Figma should be promoting that in their office hours videos too. I see to many people create a lot of extra buttons and having to make multiple changes. THANK YOU!
Great video!! But how did you convert the icon name text into its corresponding icon using a text style?
super helpful!
Hey there! I have a question about the ' Not creating components for reusable elements' part.
Are the items (Home, About, Locations etc) in that header just instances of components and the header is a component?
I was just listening a tutorial from Mavi Design called 'Components inside components' and he said that you should create only one item component, define structure and states and then use just instances of that item component in header. Do you agree with that method?
I just wanna clear some things up in my head! Thank you!
Yes. Those items in the header would be components themselves
helpful tips, thank you so much !!!
You're so welcome!
Great video, thanks for sharing. However, creating variants using this base structure I don't appear to be able to change the border radius as a property. So do I need to create a separate button base structure for rounded, straight, pill etc ? Many thanks in advance.
You can change the border radius, that shouldn't be a problem.
@@AMDesignAndDev Thanks so much for the prompt reply, I've now fixed this. However I have another question - is it possible to add a hover colour to the base structure of a button which - when changed - filters down through all the different button variants? The reason being that I plan to use the same button styles throughout multiple projects but the colours will change all the time depending on the project and I'm trying to avoid changing all the colours for each variant each time. Thank you.
@@rookie1969 You can if you want to, but the purpose of the base structure is to define the sizing etc.
If you want a base structure for states separately, you can create 2 levels of base structures, but I would not recommend it.
So I'd say, do not do that, and have the state specific styling on the main component itself.
@@AMDesignAndDev Thank you, you clearly know best as I'm pretty new to all this, advice taken :-)
Hi! Many thanks 🙏
This is so useful, but complicated! Im a newbie, so is it possible to make a slower version of this video where we can follow along?
You can check some of my other videos where I show you how to create components.
Figma Noob to Pro! 04: Components
ua-cam.com/video/tDOGUC6L7Vo/v-deo.html
Etc
I recently have also started creating a design system playlist, so do check it out
I've used Figma in the past but have to come back to it now as I need to use it for some projects. This is really useful and up to date which when looking for useful tips for Figma amongst the thousands is hard to come by! So many video tutorials are out of date. However, could you slow down a little bit when explaining? I followed it all and it all makes perfect sense but you talk too fast and thank goodness for no background music!
Sure Karen, I've heard a lot of people want me to slow down, and in my recent video, I've tried slowing down.
So keep in touch and keep letting me know if I should improve elsewhere.
@@AMDesignAndDev Awesome tutorial indeed! I personally don't mind the fast pace, you can always set playback speed anyway, though I agree a slower pace would be better for most.
What I find a bit confusing is your use of keyboard shortcuts. Sure, we can see them flash on the screen, but as this video was intended for noobs, it would be a nice addition to mention them at the very least.
@@Zuurkern That's an excellent point. I would consider that for later videos!
How about doing a component for the whole navigation bar and make variants with each of the elements highlighted? I believe it would be easier and faster
Nops, a lot of duplicated design if we’re duplicating the navbar for lets say 13 items or more in the sidebar.
Is there a link to your public training courses, please?
I don’t have any public courses yet.
I have finally launched a full premium course on Figma: asaad-mahmood-s-school.teachable.com/
You can use the voucher "amsubscriber" to get a 50% off.
AMAZING!
Assalamualaikum,
Zarbardastt Video
Walaikum As Salam Jazak Allah :)
I'm just thinking about how best to handle the "base structure" / master component in case I need a primary / secondary button and also a small / large. Is only one master component enough? Would you like some advice? Thanks
You can have a look at my buttons video:
ua-cam.com/video/DOb9CJ9mpYI/v-deo.html
@@AMDesignAndDev Thanks, I write comment there :)
Be sure to subscribe and hit the notification icon! It really helps the channel grow and motivates me to keep on investing on the channel.
Very useful video, as a person who used to create all designs in Adobe XD, there is one feature I can't seem to figure out how it works in Figma.
In Adobe XD there is a feature where you can create a component and use the instance of that component and add elements to that instance while still preserving the style of the master component. However in Figma, it does not see that's possible to add elements to an instance but only change / delete elements that already exist.
Is it possible to add new design elements to an instance of a component without touching the master component but the instance itself?
Couldn't agree more!
Good stuff! Curious to know which components you use base components for aside from buttons. I assume text inputs too. Anything else?
Yup, text inputs, dropdowns, checkboxes, labels, tags, basically a lot of things, anything that's repeated a few more than a few times, I prefer using base components for them.
@@AMDesignAndDev good stuff. With inputs, do you create each atom as individual components (label, placeholder text, input box, error messages etc) and then combine them together into one base component? Or do you just have one single base component that contains it all in one?
@@mrnickb Nops, they can be placed in the same base component, and then only the size can change on the larger versions.
@@mrnickb You can check out these two videos:
Inputs:
ua-cam.com/video/9AYrcB2Yp3A/v-deo.html
Form Group:
ua-cam.com/video/uOLGdkMeAws/v-deo.html
@@AMDesignAndDev you're a legend, thank you so much!!!
How do u put the channel rack in the playlist
Does this same logic apply to bottom NAV bars? Because I've been struggling with prototyping each states
For sure.
Hello Thanks for this.. i converted the "Header Active and Inactive state to Combine Variants, but when i tried changing the Active and inactive states of some text in the Header, they changed the original texts to HOME instead of maybe LOCATION, ABOUT, CONTACT. please how do i solve that?
Make sure the layer names are the same in both variants.
If someone want to have your mentorship..... How can be done? Thanks
Excellent💛💛💛
Thanks 🤗
Thank you very much
how to duplicate auto layout object inside components? is it possible?
So, this is my step by step, until I ask this question,
1. I create an object, ex. Button > Convert to component
2. Drag the button from local component, > Copy button (5 buttons) > Convert to autolayout > Convert to component, and finally, I got a new component and give the name as "tab".
3. Then, I drag the tab from local component, > I try to jump into the tab component, and try to duplicate the button, but nothing happen, it comes to a new component, not like when we create a basic autolayout, we can easily to duplicate the object inside the frame.
Thanks - very important tips here starting off much appreciated (too bad no one told you before recording this a bird crapped on your hat:)
I've been struggling to find an soft soft tutorial. I haven't watched yours yet but if the actual company is telling you nice job, then I'm
This is the approach I’ve been trying to get my team to adopt!
They just look at me like I’m crazy 😂
AHAHA, they will learn over time, if you get a chance, create a component for them, and once that's done, they may probably understand its value over time, especially when they have to make changes.
Q : Why i can't see Variant column as shown on your screen at 13 : 43 ?
Valuable advises!
I'm curious how would you create a calendar with components/variants when it is selected a circle with the number will appear. I've done this and let's say the component is 1 default and 1 click with circle background, or whatever. But when I select, for example, another number 12 or 28...etc, I get the same number as in component - 1 circle (and not the initial number I need to be as selected). Should I make all the numbers default and selected as variants?
I think that’s happening because you have not renamed the text in your component in correctly you only need to create the variance once and then if you apply those variance in different components or different date it should work without the text reverting back to the original variant text
@@AMDesignAndDev Thank you for the explanation. Appreciate.
Thank you for such informative video, but I noticed that the version of your figma is different a bit from mine
You’re right, and as a consequence some tips may be outdated.
So basically a Large Button should be it's own component with it's own states rather than being a variant within a smaller button? So a mobile width button should again be it's own parent component rather than a selectable variety within a different button?
Yes, now all buttons should be variants as with the new component properties update, base components don’t really work as intended.
If you put in all possible atoms within a component and just use component properties, is a base structure necessary? Unless you missed a possible atom wouldn't this cover all your bases?
Bas structures are no longer used with component properties. See the pinned comment on this video that I made 9 months ago.
@@AMDesignAndDev Yea sorry, should have looked through the comments. Thanks for your proto vids, its really opened up my thought process on what's possible on figma. Do you happen to do design critiques or have forum like on discord or patreon?
purchases I made was soft soft. I knew it was my passion but I was just stuck because of trauma I couldn't deal with. Now that I'm at a
Any idea why my gms softs different?
i would like to be one of your students , how do i contact you?
both the GMS and softEX setup is very different from the one ur using.. why is it so.? GMS doesn't even soft like a app one... and the
Although the video is a good reminder for mistakes to avoid, the person here is making some very mig mistakes, maybe unconsciously. To everyone else who is reading this - in the early part of the video around 3 minutes he is talking about menu items where he creates 2 separate components for active and inactive items. That's a mistake in itself as variants could have been created with color property, and a boolean property to turn underscore on or off. The bigger mistake was aroun 3:50 where he is actually using "instance swap" to replace active component with inactive component to which he is referring as "variants". That's a big mistake and new designers will be harmed by that. Instance swap and variants are very powerful features and cannot be used interchangeably.
I did not watch the full thing after that but the author should either place onscreen corrections or take down the video.
Wow thanks for your valuable contribution!
This is why one should try watching the video instead of making quick assumptions.
I intentionally made those mistakes so I can correct them later in the same video.
Mistake 3 talks about not creating variants within the same component group (for default/active state)
Mistake 4 talks about not naming them correctly and not using the boolean toggle for certain variants.
@@AMDesignAndDev You are welcome! Next time you can keep this feedback in mind. Also it's always a good idea to get content reveiewed before publishing.
@@AmanKumar23Hey @aman I was being sarcastic, most of the things you mentioned are already in the video if you missed the point of my comment.
@@AmanKumar23Looks like just like the video, you also did not read my comment fully, and just read the first paragraph and are replying.
Thank you so much for tNice tutorials video. I was so confused and overwheld when I first opened soft soft and now I understand how to finally
Aware this is an old tutorial but Figma on their recent building block webinar advised against using base components. The explain some glitches it causes towards the end.
I agree, the base structure no longer works with the component properties