"In June 2024, we introduced a redesigned Figma-called UI3. With UI3, some parts of this video might not match what you see in the product today. We appreciate your patience while we update our content. - Find where features moved to in our guide: help.figma.com/hc/en-us/articles/23954856027159-Navigating-UI3-Figma-s-new-UI - Learn more about component properties in Figma: help.figma.com/hc/en-us/articles/5579474826519-Explore-component-properties"
Sketch actually has had component/symbol properties for years (and has killed it). I made icons with changeable and toggleable icons many years ago in Sketch. They just never really nailed down the auto layout part, which is the huuuuuge win for Figma here.
This is great! Will it be possible to add a Fill property? Not sure if that makes sense but I'd love to have one component and easily swap the brand style (fill color, text color).
Do you create the icons as variants or different components with same name and slash before?? Because with the first way, i'm not able to swap between icons when i set them as a swap instance... To change the icon i must select it, it won't let me change it just selecting the button...
This video is amazing, but the music is so bad I have to mute it and try to interpret the captions... Please do not have such ear piercing music next time. This is a informative tutorial, much better to make it easy to watch without music, than to try to add music only to make it unwatchable.
I wonder there are different paddings based on icons and text. When turning the icon on and off for a button including text and icon, how can the padding change too? For example, (text+icon) padding will be (24 | 16), (text only) padding will be (24 | 24)? Thank you guys
I don't know what I'm doing wrong. When I select my text layer, it only gives me an option to create a Boolean property. Why don't I have the option to create a text property?
The only downer of this feature is that you can't change paddings accordingly. Usually (if we take the button example) you don't have the same paddings with an icons, as you have without them. Just removing an icon doesn't really help for that example. Good feature, but sometimes it makes things look much simpler than they actually are. Any solution?
Yup, this is my gripe as well. Looks good on paper, but if your design system is not this cut-and-paste simple system, this new method will enjoy very limited use.
I am still confused by properties, when and where to use them... it doesn't map easily to my thinking of CSS or even variables (in any programming language)...
text was easy i didnt have any of the options to do this with the icon. i think the simple button you started was too complicated for me 😅 i did a rectangle and text and tried my own icon
Any chance you can make an official video on how to make a notification component with variants, been searching for weeks but none are definitive. Basically how to go about it the right way like, your websites's notification system for instance
It only took Figma four years to finally steal normal component control from Sketch. And it still works worse and creates problems in most cases. And Variants still big and useless piece of sh*. Can someone explain to me why use them at all?) A lot of time was spent on the video to show how to change the properties of a variant "Message". But why? Just make changes on the same component, copy that and change the text and color and that's it! You use this once to show the developer how "Typing..." state looks like, so why not fix it by hand. Variants are useless! I hope one day the Figma company will finally hire some UX designers who actually use Figma, to understand how to improve it)))
17:20 this is a bad example of properties. The original component set was bloated but clear. After the cleanup it has become possible to create a button with left & right icons, and no text. This should not be allowed
I like the last update, but there is no fucking sense if I use principles of atomic design! Why should I fall through to a nested component? This flow is not convenient, very uncomfortable and fucking annoying! And also Instance Swap doesn’t work with variants. PLEASE FIX IT!
This is very convenient for the designer. But when we hide everything, how will the developers see that there are other variations with either properties? Personally, I clone instances and show all of them anyway. How do you solve this issue?
please, don't add music to videos, it's really confusing and annoying, especially when speed it 1.5x or 2x .. and hey, music tastes differs, so it doesn't make sense to make all of us taste this genre .. bad genre, ewww.
2:52 - can't see that option.(Apply instant swap property). 5:34 - Can't see any controls. seriously, what am I doing wrong here? am I using an older version?
Hi Jay, - You should be able to see the apply instant swap property when you're using icon from the component library. - The controls will show up when you're clicking on an instance of a component that has component properties defined.
@@Figma and I am using the Component Properties Playground file, in the batch editing screen, how do you select both CTA's at once. they both wrapped up in two different groups?
Amazing and well explained video! The thing that's troubling me now is how to swap efficiently to all the new properties components in alllll the design files which use currently the regular components variants...it wasn't really explained in the video
I don't understand. I keep getting an error message "not used within component". Is there something specific I should be doing when creating the object, because I've been trying to do this for an hour and I'm stuck on the first step.
This is actually very intuitive but you need to understand the process, like photoshop with masks and illustrator with forms. Need practice, this is not a simple sofware. It s for pro designer ..
I agree that it gets easier by practising. Also it helps to follow with the video and after watching it trying to replicate the workflow in a different use case e.g. on a different component.
What happens to designers' components and instances properties when a design system is published with a reduced number of components set due to utilizing Boolean feature?
Great explanation! One question though.. at the beginning of the process you created a copy of the variants in our design system so we don't mess it up but, how do we replace the existing one with the copy once we have finished implementing the changes? Would deleting the original one be enough (as they have the same names?)?
I'm following a guide from a few months ago with I can't use because the UI updated, so I find this newer guide which also has a different UI. Very frustrating when UIs are inconsistent or rapidly change.
This is by far the best video. This is how tutorials should be done! I love the intro which summarizes what we’ll be learning/requirements we’ll cover, easy to find sections, displaying which buttons you’re using on the screen (instead of the ones that disappear instantly).
Год назад+1
Exactly! All that ego filled mumbo jumbo 45 minutes long videos are disaster!
I'm a bit unclear on how the component properties retained/inherited the prototype settings since those variants were removed and deleted from the component set.
This feature is wonderful, though it's missing one crucial thing to make it useful for design systems. The properties (and variants) of children should be controllable by parents. As it is now, you have to dig deep into the tree of nested components to control variants - it would be way better to have all the controls surfaced to the parent component instead. This was suggested on Figma forums around a year ago, it would be great to finally have it supported natively.
You might like an upcoming feature for Component Properties called "Bubbled Props", as it does exactly that! Jacob Miller talks more about it in a recent Office Hours: ruclips.net/video/hobK6JqADio/видео.html
What would be useful is actually using the same example of the button to demonstrate how component properties differ from variant properties - less context switching and users can actually see how one thing (in this case, a button) can have both component and variant properties.
I'm struggling with the instance swap property. I have all the icons I'm using for this project as variants of an icon component so when I apply the instance swap property, It just selects the icon component without giving me an option of selecting a default icon. Could it just be a problem with the way I organized the icons?
I really loved component properties, but there wasn't many tutorials when it first released, there was only a figma file explaining. I had to figure out by myself and after that, I FCKING LOVE IT! I couldn't believe how we were creating sooooo many variations. It was a must all alone. Figma is literally the leader of design industry, other apps still needs many years to catch up. Only thing I wish are regional pricing and improvements of photo editing (and maybe more options for prototype). Like small addon or something like that would save us opening photoshop for editing pictures. You can't always find the perfect picture for your design, sometimes you have to make it.
Is there an efficient way to reduce the current variants within a design system? A lot of variants are used in different design files, if I were to remove them or modify, I'd have to go through each and every design and manually update...
Thanks for the video. What I haven't seen: if I want to do an instance swap, but the proportion of the image is different - wide vs tall. Let's say the default is wide. But then the tall image is forced to be wide. How to remedy this problem? Thanks.
I have a query. I have 200 frames, each depicting an animal and its name. Now, I aim to utilize them and trigger an action where hovering changes the frame's border color, or clicking on the frame navigates to the respective animal's page. How can I achieve this with swap properties or variables to minimize excessive components and avoid multiple computations for 200 animals each time? Thanks
The file structure in this video is extremely confusing. There are 4-5 folders named icons, some with only one icon in them. There is a reason why @2:31 is the most replayed. I've tried for 4 hours and cannot make sense of this.
It's good but yes it was confusing. The only thing, in the file shown with the previous variants...a user can see the number of variants :) One thing, if I have a variant of size (default and large), how will I manage that.
And yes, I certainly understand that most Figma users are so dumb that they can't even learn how to use Figma's tools. These guys won’t even get to the point of thinking why these features are needed at all and maybe it’s just worth not using these tools
👋 why are variants better than components? I'm new to design and figma and I was having a difficult time understanding when to use one over the other or if one is just better to use.
@@hcf797 Use properties when you want to have control over some element's visibility, the text content, or what component instance should be embedded. So if you have a button with an icon, you'd use properties to control the text, the icon's visibility, and what icon should be used on that button. Use variants for everything else: colors, sizes, styles, paddings, borders, etc. So you'd use variants to have a primary, secondary, and tertiary button styles, each with different colors and borders. Or you'd create a variant with a lighter background, call it "hovered", and add a prototype connection to animate to this variant on hover. Properties and variants have different uses. You can still use variants alone for everything described above, but properties make it way easier for common tasks. Once bubbling props go live, this will be a very powerful set of tools for design systems.
i think the team at figma did an excellent job properties are more powerful than variants and build on top of them so you dont have to use them if you dont want or need to
Ah I finally understand how to use these! Thank you so much. I cannot wait until you have styling properties too, being able to set variable colours in particular would be incredible useful.
Hey figma, thanks for keep creating helpful video. Can you please help us to show how much way we can share the component library and how to remove it? And how can i create a basic style guide/DS and use it for all of my internal work. It should be for unpaind version. Coz as you know very wll there are a lost's of unpaid figma user who needs your support.
It is actually very comfortable. But, I stick with my many variants (like 96 buttons), because I have variants that need 3 icon sizes. The buttons has different colors and shapes and states. All this does not work here so far. And by the way, have a look to the comments on the playground file ;-)
This is a great tutorial with real use cases and a very foolproof explanation. Just the right amount of detail.. well done! --> The pace of the background music did get me into a trance sometimes, so i had to scroll back a few times when I got distracted. But this could be all on me :) Keep 'm coming!
Thank God the narrator has been changed! No offense to the other person doing the tutorials back then but his voice is just so robotic, monotonous and listening to him makes me sad and low on energy 😅
13:58 This is confusing. If you set a new Property for Icon Right, why would the corresponding Boolean Property titled Has RIGHT Icon need to be set to FALSE? I understand setting it to FALSE if the Property name were still Icon Left, but the icon IS on the right in the Icon Right property, so why set it to FALSE?
Nice video....@14:30 you opted to create the text properties (boolean and text change) from the component set rather than from the Text layer (i.e., your explanation was....."this method is useful if you want to apply existing properties to a new layer or object"). Can you expound on that a bit more? What existing properties are we trying to apply here? Maybe some more discussion of the downsides of doing it the other way or the advantages of taking the approach you took would help clarify....especially given that you're chosing to do something different then what you had done for other properties...Why is the text stuff special and different enough to warrant a completely different approach. This part of the video REALLY begs for a more detailed explanation. Thoughts?
In the Example: Message List: "Message" component, is it important to create a separate text style for "Typing..." in blue as in the case of "Subline" in color gray? Does it matter since we will not write anything there? Thanks :)
Only there is a small problem here, maybe not a problem but I don’t like this situation. Whenever I click on a boolean property, another property related to it disappears from the right sidebar, which causes me a lot of inconvenience.
![Tee Grizzley - Blow for Blow (feat. J. Cole) [Official Video]](http://i.ytimg.com/vi/wNLN5xsx5dc/mqdefault.jpg)
"In June 2024, we introduced a redesigned Figma-called UI3.
With UI3, some parts of this video might not match what you see in the product today. We appreciate your patience while we update our content.
- Find where features moved to in our guide: help.figma.com/hc/en-us/articles/23954856027159-Navigating-UI3-Figma-s-new-UI
- Learn more about component properties in Figma: help.figma.com/hc/en-us/articles/5579474826519-Explore-component-properties"
I wonder if Sketch developers take long breaks to self reflect after each one of these incredible Figma updates
Is Sketch still alive?
hahah, Sketch is like an ancient dinosaur now
Sketch actually has had component/symbol properties for years (and has killed it). I made icons with changeable and toggleable icons many years ago in Sketch. They just never really nailed down the auto layout part, which is the huuuuuge win for Figma here.
I had not known about a position called sketch developer. The internet is creating a variety of positions I have not heard of.
@@WealthyThomas😂😂
These tutorials are perfect. Thank you for producing them.
A very good tutorial. But PLEASE get rid of that awful background music.
And narrator. Her voice is very annoying. This needs a more straightforward and focused tone.
What a great video, Clarified each and every doubt on component properties.
You guys are awsome❤❤❤❤
THAT IS A REALLY AWESOME VIDEO!
This is great!
Will it be possible to add a Fill property? Not sure if that makes sense but I'd love to have one component and easily swap the brand style (fill color, text color).
It doesn't say in the tutorial but your icon must be a component instance to do this.
Thank you figma... awesomeness is the greatness of figma😊
Do you create the icons as variants or different components with same name and slash before?? Because with the first way, i'm not able to swap between icons when i set them as a swap instance... To change the icon i must select it, it won't let me change it just selecting the button...
This video is amazing, but the music is so bad I have to mute it and try to interpret the captions... Please do not have such ear piercing music next time. This is a informative tutorial, much better to make it easy to watch without music, than to try to add music only to make it unwatchable.
I wonder there are different paddings based on icons and text. When turning the icon on and off for a button including text and icon, how can the padding change too? For example, (text+icon) padding will be (24 | 16), (text only) padding will be (24 | 24)? Thank you guys
I don't know what I'm doing wrong. When I select my text layer, it only gives me an option to create a Boolean property. Why don't I have the option to create a text property?
so, now that the design system has two identical buttons, how do you complete the process? Simply delete the original button?
The only downer of this feature is that you can't change paddings accordingly. Usually (if we take the button example) you don't have the same paddings with an icons, as you have without them. Just removing an icon doesn't really help for that example. Good feature, but sometimes it makes things look much simpler than they actually are. Any solution?
Yup, this is my gripe as well. Looks good on paper, but if your design system is not this cut-and-paste simple system, this new method will enjoy very limited use.
@@GregK8625 well I must say I use it on a daily. It limits the designer for sure, but now I‘m not even sure if that‘s bad tbh.
I've followed the instructions here and I do not have the true/false toggles. I get a setting icon and have to go to a menu to change that value.
Awesome figma, love you
I am still confused by properties, when and where to use them... it doesn't map easily to my thinking of CSS or even variables (in any programming language)...
Love it.
I love Figma!
Rally weird, i created a component, how to define an instance swap property and use it? In your video the element is there.
text was easy i didnt have any of the options to do this with the icon. i think the simple button you started was too complicated for me 😅 i did a rectangle and text and tried my own icon
Any chance you can make an official video on how to make a notification component with variants, been searching for weeks but none are definitive. Basically how to go about it the right way like, your websites's notification system for instance
So complicated...
I couldn't can make button auto resize on text change or when is icon hided ... How to component wrap auto resize?
You need to put text in a frame with auto layout. In this case, button will be behaving as like you wish.
when i select icon there is no checkmark pls explain from the beginning!
I think it needs to be made into a component first
11:18 Instance Swap POPERTY
WTF it is genius!
great video but the music is unbearable
I wish the violinist would practise her pitch a bit to make her playing less distractive.
All still relevant here? Thanks
What liminal space music is this? Makes distractingly sad
really great and useful film, thanks! But I couldn't stand this voice, sorry. I had to stop every 3 minutes :)
It only took Figma four years to finally steal normal component control from Sketch. And it still works worse and creates problems in most cases. And Variants still big and useless piece of sh*. Can someone explain to me why use them at all?) A lot of time was spent on the video to show how to change the properties of a variant "Message". But why? Just make changes on the same component, copy that and change the text and color and that's it! You use this once to show the developer how "Typing..." state looks like, so why not fix it by hand. Variants are useless! I hope one day the Figma company will finally hire some UX designers who actually use Figma, to understand how to improve it)))
Please change the voice of the videos, this is difficult to follow.
Why the voice and its modulations of the video is like a child animated video? Very strange... Cant you make something more adult?
17:20 this is a bad example of properties. The original component set was bloated but clear. After the cleanup it has become possible to create a button with left & right icons, and no text. This should not be allowed
Finally an official videos on Component properties. It was bit confusing at first. But now I am feeling much comfortable.
Thanks 😊
im still at confusing :'(
@@elmotareal What's wrong Ayyash?
I like the last update, but there is no fucking sense if I use principles of atomic design! Why should I fall through to a nested component? This flow is not convenient, very uncomfortable and fucking annoying! And also Instance Swap doesn’t work with variants. PLEASE FIX IT!
This is very convenient for the designer. But when we hide everything, how will the developers see that there are other variations with either properties?
Personally, I clone instances and show all of them anyway. How do you solve this issue?
I think the component playground in Dev Mode addresses this concern.
please, don't add music to videos, it's really confusing and annoying, especially when speed it 1.5x or 2x ..
and hey, music tastes differs, so it doesn't make sense to make all of us taste this genre .. bad genre, ewww.
Background music is very distracting 😅
Very easy to understand. Exactly what I needed, great job :)
2:52 - can't see that option.(Apply instant swap property).
5:34 - Can't see any controls. seriously, what am I doing wrong here? am I using an older version?
Hi Jay,
- You should be able to see the apply instant swap property when you're using icon from the component library.
- The controls will show up when you're clicking on an instance of a component that has component properties defined.
@@Figma and I am using the Component Properties Playground file, in the batch editing screen, how do you select both CTA's at once. they both wrapped up in two different groups?
Very Easy to understand but background music is so sad hear.
Amazing and well explained video! The thing that's troubling me now is how to swap efficiently to all the new properties components in alllll the design files which use currently the regular components variants...it wasn't really explained in the video
I don't understand. I keep getting an error message "not used within component". Is there something specific I should be doing when creating the object, because I've been trying to do this for an hour and I'm stuck on the first step.
same here
Hi Figma community, any suggestion??
Figma have so confusing and unintuitive interface… I'm watched this video a few time, but still cant understand how properties work. :\
This is actually very intuitive but you need to understand the process, like photoshop with masks and illustrator with forms.
Need practice, this is not a simple sofware. It s for pro designer ..
I agree that it gets easier by practising. Also it helps to follow with the video and after watching it trying to replicate the workflow in a different use case e.g. on a different component.
Same problem 😢
What happens to designers' components and instances properties when a design system is published with a reduced number of components set due to utilizing Boolean feature?
Great explanation!
One question though.. at the beginning of the process you created a copy of the variants in our design system so we don't mess it up but, how do we replace the existing one with the copy once we have finished implementing the changes? Would deleting the original one be enough (as they have the same names?)?
I'm following a guide from a few months ago with I can't use because the UI updated, so I find this newer guide which also has a different UI. Very frustrating when UIs are inconsistent or rapidly change.
This is by far the best video. This is how tutorials should be done! I love the intro which summarizes what we’ll be learning/requirements we’ll cover, easy to find sections, displaying which buttons you’re using on the screen (instead of the ones that disappear instantly).
Exactly! All that ego filled mumbo jumbo 45 minutes long videos are disaster!
Oh cool! New features. OH NO!! California vocal fry
Still pretty confusing to me
I'm a bit unclear on how the component properties retained/inherited the prototype settings since those variants were removed and deleted from the component set.
This feature is wonderful, though it's missing one crucial thing to make it useful for design systems. The properties (and variants) of children should be controllable by parents.
As it is now, you have to dig deep into the tree of nested components to control variants - it would be way better to have all the controls surfaced to the parent component instead. This was suggested on Figma forums around a year ago, it would be great to finally have it supported natively.
This! I wish you could wire up and access some child component properties from the parent.
You might like an upcoming feature for Component Properties called "Bubbled Props", as it does exactly that! Jacob Miller talks more about it in a recent Office Hours: ruclips.net/video/hobK6JqADio/видео.html
@@Figma You guys are beyond awesome! Figma is shaping up to be my favorite tool. Thanks for listening to your community!
@@Figma This is great news, thank you! For anyone interested, the timestamp in that video is 46:08.
@@browsing4307 I concur, Figma just keeps getting better and better. What an amazing team! What an amazing tool!
What would be useful is actually using the same example of the button to demonstrate how component properties differ from variant properties - less context switching and users can actually see how one thing (in this case, a button) can have both component and variant properties.
I'm struggling with the instance swap property.
I have all the icons I'm using for this project as variants of an icon component so when I apply the instance swap property, It just selects the icon component without giving me an option of selecting a default icon.
Could it just be a problem with the way I organized the icons?
I really loved component properties, but there wasn't many tutorials when it first released, there was only a figma file explaining. I had to figure out by myself and after that, I FCKING LOVE IT! I couldn't believe how we were creating sooooo many variations. It was a must all alone. Figma is literally the leader of design industry, other apps still needs many years to catch up. Only thing I wish are regional pricing and improvements of photo editing (and maybe more options for prototype). Like small addon or something like that would save us opening photoshop for editing pictures. You can't always find the perfect picture for your design, sometimes you have to make it.
Is there an efficient way to reduce the current variants within a design system? A lot of variants are used in different design files, if I were to remove them or modify, I'd have to go through each and every design and manually update...
Great question, waiting for an answer too
Thanks for the video. What I haven't seen: if I want to do an instance swap, but the proportion of the image is different - wide vs tall. Let's say the default is wide. But then the tall image is forced to be wide. How to remedy this problem? Thanks.
I have a query. I have 200 frames, each depicting an animal and its name. Now, I aim to utilize them and trigger an action where hovering changes the frame's border color, or clicking on the frame navigates to the respective animal's page. How can I achieve this with swap properties or variables to minimize excessive components and avoid multiple computations for 200 animals each time? Thanks
What is the "option" key for Windows? I tried ALT, but CTRL+ALT+K opens an app on my computer.
I really need help... The boolean function is not visible in my figma.
How to enable it, i've searched for it everywhere...
Very well explained in a simple way. Thanks alot.
nice narration and video, annoying music. RUclips should introduce a toggle bg-music feature.
The file structure in this video is extremely confusing. There are 4-5 folders named icons, some with only one icon in them. There is a reason why @2:31 is the most replayed. I've tried for 4 hours and cannot make sense of this.
Great video, shitty background music!
So distracting..
It's good but yes it was confusing. The only thing, in the file shown with the previous variants...a user can see the number of variants :)
One thing, if I have a variant of size (default and large), how will I manage that.
OMG THANK YOU for explaining how to use this on an already created component set... I was worried I would have to figure this out on my own...
And yes, I certainly understand that most Figma users are so dumb that they can't even learn how to use Figma's tools. These guys won’t even get to the point of thinking why these features are needed at all and maybe it’s just worth not using these tools
It might save space but it's not better than variants, it's confusing
It's like going back to Sketch times, the dark times lol
👋 why are variants better than components? I'm new to design and figma and I was having a difficult time understanding when to use one over the other or if one is just better to use.
@@hcf797 Use properties when you want to have control over some element's visibility, the text content, or what component instance should be embedded. So if you have a button with an icon, you'd use properties to control the text, the icon's visibility, and what icon should be used on that button.
Use variants for everything else: colors, sizes, styles, paddings, borders, etc. So you'd use variants to have a primary, secondary, and tertiary button styles, each with different colors and borders. Or you'd create a variant with a lighter background, call it "hovered", and add a prototype connection to animate to this variant on hover.
Properties and variants have different uses. You can still use variants alone for everything described above, but properties make it way easier for common tasks. Once bubbling props go live, this will be a very powerful set of tools for design systems.
i think the team at figma did an excellent job
properties are more powerful than variants and build on top of them so you dont have to use them if you dont want or need to
This is awesome! Are there any plans to add a color/text style property?
great tutorial! why does the background music sound kinda sad though :333
The background “music” is pretty annoying/distracting unfortunately 😢
Super helpful information, but please re-visit your choice of backing track 🙉
Simply epic.
Thank you for the video. Please remove the music background.
I cant stand this robotic read-from-a-script audio. Not for 18 minutes. atrocious.
nice video, but it was very difficult to listen with such high-pitch voice, had to use subtitles
Ah I finally understand how to use these! Thank you so much. I cannot wait until you have styling properties too, being able to set variable colours in particular would be incredible useful.
FAX
Please don't use that awful annoying background music again.
Top stuff fig team, its been a little difficult getting my head around it but you have answered many questions...cheers
This bg music is distracting. Hard to follow by all the missed tones
Hey figma, thanks for keep creating helpful video. Can you please help us to show how much way we can share the component library and how to remove it? And how can i create a basic style guide/DS and use it for all of my internal work. It should be for unpaind version. Coz as you know very wll there are a lost's of unpaid figma user who needs your support.
You can't share library between files with free account. But you can copy/paste them between files if you want
This has been so delightful to watch. Thanks a lot Figma, you're awesome✨
It is actually very comfortable. But, I stick with my many variants (like 96 buttons), because
I have variants that need 3 icon sizes. The buttons has different colors and shapes and states. All this does not work here so far. And by the way, have a look to the comments on the playground file ;-)
the same situation :(
Did you find a solution?
Your tutorial doesn't provide related example, so bad
I did not spend the time to discover the new Components properties and now I understand everything. Thanks!
This is a great tutorial with real use cases and a very foolproof explanation. Just the right amount of detail.. well done!
--> The pace of the background music did get me into a trance sometimes, so i had to scroll back a few times when I got distracted. But this could be all on me :)
Keep 'm coming!
You are right! That music is not a good choice.
Thank God the narrator has been changed! No offense to the other person doing the tutorials back then but his voice is just so robotic, monotonous and listening to him makes me sad and low on energy 😅
3:45 - The Content section is now contained in the Text property panel
13:58 This is confusing. If you set a new Property for Icon Right, why would the corresponding Boolean Property titled Has RIGHT Icon need to be set to FALSE? I understand setting it to FALSE if the Property name were still Icon Left, but the icon IS on the right in the Icon Right property, so why set it to FALSE?
Nice video....@14:30 you opted to create the text properties (boolean and text change) from the component set rather than from the Text layer (i.e., your explanation was....."this method is useful if you want to apply existing properties to a new layer or object"). Can you expound on that a bit more? What existing properties are we trying to apply here? Maybe some more discussion of the downsides of doing it the other way or the advantages of taking the approach you took would help clarify....especially given that you're chosing to do something different then what you had done for other properties...Why is the text stuff special and different enough to warrant a completely different approach. This part of the video REALLY begs for a more detailed explanation. Thoughts?
In the Example: Message List: "Message" component, is it important to create a separate text style for "Typing..." in blue as in the case of "Subline" in color gray? Does it matter since we will not write anything there? Thanks :)
Instance Swap is so difficult to get correct.
Whenever I turn my icon boolean property off my text disappears! 🤕 I already checked and the text is using its own property. How can I fix it? 😞
This is exactly , how should be a tutorial , I loved it ❤
anybody has a link to download the Whyte font?
Only there is a small problem here, maybe not a problem but I don’t like this situation. Whenever I click on a boolean property, another property related to it disappears from the right sidebar, which causes me a lot of inconvenience.