A few tips: 1. If you select all the components, you can 'create multiple components' from the component dropdown in the top bar. 2. If you created one component for all your icons (or use a font icon) Then create one component for your menu item - then create variants - one hover state, one selected state and one default state. Then use overrides to change the icons and text.
@@JustUXChannel there's an option for multiple components. so instead of choosing 1 by 1, you just have to select them all and theres an option to create multiple components.
Being used to using 'base components' made this hard to watch 😅 Great video otherwise! To add to Patrick's tip around creating multiple components; you can create prototype connections without configuring them then configure them in bulk afterwards in the sidebar - makes it much easier to adjust & test until it feels right. Might be enough for a whole separate video with the new variant property types (e.g. to override the icons & labels).
Simple things like that eats your brain fking out, i been trying it like whole damn evening without watching any tuto, finally gave up & cool down a bit & decided to watch your video for the practice I'm doing, But made me realize the simple things you think you know, sometimes they torture you damn bad, & dont let you rest in peace ( :
Ah hope you managed it in the end, let me know if you have any questions! Stay with it buddy, design takes a while to get a hang of, but you'll make huge improvements before you know it!
@@JustUXChannel I think you should work on Prototyping becuase many poeple are covering general things . Be specific and It will help you stand out from the rest and imrpove your channel growth
i think you can use one component and make an active and passive state for it and use it in your side bar and just rename them lol except you want to always know the page you on
🤩 very amazing i will watched again again while i will create the same think to be famlliar with it, you will be a creat youtuber soon, nice topic, please do more videos like this i am bulding my website these days
I got this error using ExportKit and I really need to use it: Component set for node has existing errors. This happens when you have invalid/duplicate variant(names). I changed every name but that doesn't fix anything. Pls help
@@JustUXChannel thanks. and may ik, do u have any tips on how to make the blue thing disapear after clicking on other ui? for example, i click on the "audio devices" it turns blue, then i click on "locations" it turns blue to. so any tips on how to make the "audio devices" blue disapear after clicking "locations"?
Thank you for this! I have a question though: What happens if you click let's say "Audio Devices button" once, and then click the "Locations button" right after? Is it going make those 2 buttons have an active state at the same time? If so, how are you going to prototype the "Audio Devices button" going back to its default state after you click another button? Much love!
Hey Joshua great question! Currently there isn't conditional formatting in Figma, so you would have the unnatural state of having two active links in the menu. You could overcome this by building screens connected with each section. E.g. Audio device screen (Then set the related menu link active via the component properties) You can then do this for all areas in the menu and then connect them via prototype connections. If you just want to test a few screens and avoid the rest of the nav, I'd de-connect them in the prototype settings so you could essentially restrict the users navigation to the areas you want to test. Hope that makes sense, sometimes hard to describe more detailed stuff here!
Very insightful video but after creating these components and prototyping them, how are you taken to thier individual screens? For instance, when I click on audio, and it becomes active, how do I get to the audio screen ?
Hey you'd have to create the screens and then manually set up prototype connections from each link to the respective screen. Hard to describe in comments but will try and make a quick video on this :)
Thank you so much for this tutorial-very helpful and timely for how I'm trying to learn Figma! Two questions came to mind: 1) What if I wanted the default state to be pre-selected to the top item in the left nav (let's assume it's the home page), then how would I need to do anything differently in the interactive component? Or would I just simply choose the active state in the prototype when I'm starting? 2) What would be your suggestion for how to keep only one left nav item selectable at a time?
Hey so glad you liked it :) Thanks for the feedback! 1) In the main sidebar component you can select the link you want to be active and then switch its state to active in the properties panel. Then every instance of the sidebar itself will have this item active as default. Check the Figma community file, as it'll be easier to understand with the source file. 2) I don't have a great answer for this one as there is still no conditional logic to Figma prototypes unfortunately. However when you build out a prototype, if every navigation link is connected to a unique page in the prototype, it will behave like you described, as each click will jump to the related page and the connected nav link will be active.
Better practice: 1. Create a component for the icons. 2. Create another component for the button/nav item with just the default/Hover/onClick events. 3. Nest the icon component in with the button/nav item.
Everything is fantastic, including your presentation and skill, but your background music is pitiful and irritating. Man Because of your background music, most of the words are difficult to understand. Please work on that, or watch other youtube videos.
Super helpful. Glad you went through the trouble in spite of the headaches. Thank you
Thanks Michael! Really appreciate it :)
A few tips:
1. If you select all the components, you can 'create multiple components' from the component dropdown in the top bar.
2. If you created one component for all your icons (or use a font icon) Then create one component for your menu item - then create variants - one hover state, one selected state and one default state. Then use overrides to change the icons and text.
Not sure what you mean about multiple components? Is this the same as 'variants' I use them here for the nav links to define the interactive states
Very true, I will just need a component set of icons, then 1 menu item component with 2 other variants.
@@JustUXChannel there's an option for multiple components. so instead of choosing 1 by 1, you just have to select them all and theres an option to create multiple components.
@@namuh87 Ah yes I know what you mean, would have saved me some time for sure XD
Being used to using 'base components' made this hard to watch 😅 Great video otherwise! To add to Patrick's tip around creating multiple components; you can create prototype connections without configuring them then configure them in bulk afterwards in the sidebar - makes it much easier to adjust & test until it feels right. Might be enough for a whole separate video with the new variant property types (e.g. to override the icons & labels).
Simple things like that eats your brain fking out, i been trying it like whole damn evening without watching any tuto, finally gave up & cool down a bit & decided to watch your video for the practice I'm doing,
But made me realize the simple things you think you know, sometimes they torture you damn bad, & dont let you rest in peace ( :
Ah hope you managed it in the end, let me know if you have any questions! Stay with it buddy, design takes a while to get a hang of, but you'll make huge improvements before you know it!
Great video!
Wish this didn't have the loud music over it
Clear and Concise! Thank you!
Thank you mate! I'm still surprised this gets views, I wish I could update the audio :D
this video is better than figma official tutorial, wish you upload more figma videos.
Thank you!
Hey man thank you so much for this video. I definitely learned a lot,
Thank you mate!
how to show the toggle effect ?(when one is selected/turns blue the rest should remain in default state) Thanks!
Brilliant - thank you for this
Absolultely love this . Thank you so much for the tutorial, it was really helpful
Thank you! Made my Friday!
@@JustUXChannel You deserve 100K subs
@@QamarAmin Thank you bro! Let me know if there's anything you want to see covered in the future :)
@@JustUXChannel I think you should work on Prototyping becuase many poeple are covering general things . Be specific and It will help you stand out from the rest and imrpove your channel growth
@@JustUXChannel Maybe something like. Different Prototyping hacks , tips and tricks
i think you can use one component and make an active and passive state for it and use it in your side bar and just rename them lol except you want to always know the page you on
🤩 very amazing i will watched again again while i will create the same think to be famlliar with it, you will be a creat youtuber soon, nice topic, please do more videos like this i am bulding my website these days
Thanks so much for the kind words mate! Good luck with your website! I hope I'll have time soon to make more videos
Super helpful thank you
💚 Thanks!
But when one is clicked upon, when we click another option, the previous remains same. Can anyone suggest this?
Insightful ..thanks 💙
Thanks Ajay! I'll try and do a new one soon to factor in the new Figma features that make this kind of work super quick
@@JustUXChannel Appreciate the effort you put to support the Design community bro...
Thank you! This video helps me a lot. But for me, the background music was equaly volumed with your voice.
Thanks for the feedback, and understood re volume
Thank You !
Thanks for watching mate!
I got this error using ExportKit and I really need to use it: Component set for node has existing errors. This happens when you have invalid/duplicate variant(names).
I changed every name but that doesn't fix anything. Pls help
Thank you so much
🙌 Thanks for the positive comment!
may ik how u select one by one ? in 1:28
Just hold shift and click
@@JustUXChannel thanks. and may ik, do u have any tips on how to make the blue thing disapear after clicking on other ui? for example, i click on the "audio devices" it turns blue, then i click on "locations" it turns blue to. so any tips on how to make the "audio devices" blue disapear after clicking "locations"?
Thank you for this! I have a question though:
What happens if you click let's say "Audio Devices button" once, and then click the "Locations button" right after? Is it going make those 2 buttons have an active state at the same time? If so, how are you going to prototype the "Audio Devices button" going back to its default state after you click another button? Much love!
Hey Joshua great question!
Currently there isn't conditional formatting in Figma, so you would have the unnatural state of having two active links in the menu.
You could overcome this by building screens connected with each section. E.g. Audio device screen (Then set the related menu link active via the component properties) You can then do this for all areas in the menu and then connect them via prototype connections.
If you just want to test a few screens and avoid the rest of the nav, I'd de-connect them in the prototype settings so you could essentially restrict the users navigation to the areas you want to test.
Hope that makes sense, sometimes hard to describe more detailed stuff here!
@@JustUXChannel Will try to do that! Thanks so much! Appreciate your reply =)
Very insightful video but after creating these components and prototyping them, how are you taken to thier individual screens? For instance, when I click on audio, and it becomes active, how do I get to the audio screen ?
Hey you'd have to create the screens and then manually set up prototype connections from each link to the respective screen. Hard to describe in comments but will try and make a quick video on this :)
Song too loud bro. but thx for the video ;)
Yeh I wish I could change the audio now :D Thanks for the comment!
Thank you so much for this tutorial-very helpful and timely for how I'm trying to learn Figma! Two questions came to mind:
1) What if I wanted the default state to be pre-selected to the top item in the left nav (let's assume it's the home page), then how would I need to do anything differently in the interactive component? Or would I just simply choose the active state in the prototype when I'm starting?
2) What would be your suggestion for how to keep only one left nav item selectable at a time?
Hey so glad you liked it :) Thanks for the feedback!
1)
In the main sidebar component you can select the link you want to be active and then switch its state to active in the properties panel. Then every instance of the sidebar itself will have this item active as default. Check the Figma community file, as it'll be easier to understand with the source file.
2) I don't have a great answer for this one as there is still no conditional logic to Figma prototypes unfortunately.
However when you build out a prototype, if every navigation link is connected to a unique page in the prototype, it will behave like you described, as each click will jump to the related page and the connected nav link will be active.
Great, but the elevator background music is too much :)
100%, I wish I could edit it down in retrospect
RIP "Combine as Variants" option on the right menu
😭 This haunts me tbh
The background music is a huge distraction.
Better practice:
1. Create a component for the icons.
2. Create another component for the button/nav item with just the default/Hover/onClick events.
3. Nest the icon component in with the button/nav item.
i wish this video was without music...:(
sorry mate, next one I'll sort the levels out better!
Thank u.... will look forward for more tutorials...
Everything is fantastic, including your presentation and skill, but your background music is pitiful and irritating.
Man Because of your background music, most of the words are difficult to understand.
Please work on that, or watch other youtube videos.
Hey Vikram, noted. Will definitely use much quieter music in the future, thanks for the feedback :)
Thumb down for the annoying music. Couldn‘t watch to end.
Hey man, it's true the music is way too loud, I just can't retroactively change it. Hopefully it's better on newer vids.