they keep showing the branding functionality as something common but it is only for organizations. So freelancers and small companies are not cared for as usual. Most of the times this presentations are out of touch with the reality of half of figma users. This is only geared to cash grab money from big company clients
It seems like the more layered, interactive, and complex the design becomes, the more the prototype struggles. Interactions start to lag bad with hover states getting stuck all over the place and everything moving slowly. This has become a serious issue for me.
@@STalvacchia I don't currently need to use anything heavy as there is enough established in code that Figma is more of an initial sketch space, but I used to use Protopie for more intricate prototypes. At the end of the day, code is the best place to test serious ideas. Figma prototypes should be answering a question, not trying to provide the solution
An open source generic accessible component library would be nice, as an addition to the native Material and HI. Then we could all just relate to three global component libraries and build our brand and patterns around them. A United Nations DS 🌎
feels like feature creep, Figma trying to make designers dependent on their systems (imho). Would love Figma to help me conduct better usability tests and capture ongoing user feedback
Figma. You adding too much complexity to the design. It's becoming more & more difficult and overwhelming. I find myself doing more technical stuff than design itself.
Hey thanks for the shoutout on the deprecation article :) Definitely going to check out the Verizon talk and see what we can adopt there. Our approach was very much hacking around the shortcomings of Figma 3+ years ago, lots of room for continuous improvement.
Does anyone else think that Figma desperately needs to address how complicated Variables are? As a designer I’ve been trying on and off to understand it over the last year and I’m still completely lost.
@@ViruX93 Agree, the basic variables are still fine but conditions etc are borderline closer to programming than designing lol. It is no longer a "design" tool at that point.
It's a Unicode character named "Arrow pointing downwards then curving rightwards" ⤷. You can access and copy it from the system symbol or emoji panel (at least on macOS).
@@ismawatinurjannah1249 I was trying to figure this out for a while too. When I added the symbol you mentioned to mine and tried it out, I realized that it wasn't really necessary. The component already hides and shows properties based on toggle states. I just wish we could organize properties underneath specific variants. The variants are stuck at the top. But sometimes I have a property that only applies to a specific variant so it would be more intutitve to place it right under that variant.
@@robertboyhan2884 It's nice to have for visual cues, like when you have multiple variant properties for a single toggle action you'd be able to instantly recognize which ones belong under that group.
Ironically, the new UI is the worst update ever. It adds so much complexity, without much value except for looks. Also, it ruins the whole easy-to-use experience. Focus your resources on something else Figma team.
the number 1 metric for a design system is adoption.. always remember that.
The second woman speaks so quickly.
they keep showing the branding functionality as something common but it is only for organizations. So freelancers and small companies are not cared for as usual. Most of the times this presentations are out of touch with the reality of half of figma users. This is only geared to cash grab money from big company clients
It seems like the more layered, interactive, and complex the design becomes, the more the prototype struggles. Interactions start to lag bad with hover states getting stuck all over the place and everything moving slowly. This has become a serious issue for me.
Yeah hover states quickly stop working when you’ve got more than a few components using them.
I love Figma but it's not a serious heavy prototype tool.
@@platinumdynamite what do you use for prototyping? Do you use another tool in conjunction with Figma or completely separate?
@@STalvacchia I don't currently need to use anything heavy as there is enough established in code that Figma is more of an initial sketch space, but I used to use Protopie for more intricate prototypes. At the end of the day, code is the best place to test serious ideas. Figma prototypes should be answering a question, not trying to provide the solution
An open source generic accessible component library would be nice, as an addition to the native Material and HI. Then we could all just relate to three global component libraries and build our brand and patterns around them. A United Nations DS 🌎
Lady slow down... 😅
I changed the playback speed to 0.9 when Alexia was presenting.
feels like feature creep, Figma trying to make designers dependent on their systems (imho). Would love Figma to help me conduct better usability tests and capture ongoing user feedback
Figma. You adding too much complexity to the design. It's becoming more & more difficult and overwhelming. I find myself doing more technical stuff than design itself.
Great talk, loved all that was said. Great tips thank you!
Can you provide to us Spanish subtitles? Ana Speaks so fast! 😅😅
I changed the playback speed to 0.9.
Hey thanks for the shoutout on the deprecation article :) Definitely going to check out the Verizon talk and see what we can adopt there. Our approach was very much hacking around the shortcomings of Figma 3+ years ago, lots of room for continuous improvement.
Where is talk with TE “a look inside teenage engineering”?Just yesterday it was on the channel
the second speaker needs to slow down! She speaks too fast!
You don’t have the right to train your ai off of our designs. Penpot is looking pretty good nowadays.
It is opt out, is it not?
@@fanovaohsmuts Penpot is a tool.
I thought it would be opt in
Great stuff thanks for the great tips!
When will the update be available?
Does anyone else think that Figma desperately needs to address how complicated Variables are? As a designer I’ve been trying on and off to understand it over the last year and I’m still completely lost.
yes. Variables and styles. The UX is so bad for this feature.
I have trouble with understanding advanced prototypes like using conditions but variables are fine.
@@ViruX93 Agree, the basic variables are still fine but conditions etc are borderline closer to programming than designing lol. It is no longer a "design" tool at that point.
Speak so fast and is so difficult understand the meaning, really I hate this presentation. So sad.
I changed the playback speed to 0.9 when Alexia was presenting.
wow great knowledge its amazinng
Thank you :)
Hi guys, how i input like arrow down under sub properties like on 13:46?
updated: after i look at the video in very slow mode.. i think they just copy/paste this symbol ahahha -> ↪
It's a Unicode character named "Arrow pointing downwards then curving rightwards" ⤷. You can access and copy it from the system symbol or emoji panel (at least on macOS).
@@ismawatinurjannah1249 ↳
@@ismawatinurjannah1249 I was trying to figure this out for a while too. When I added the symbol you mentioned to mine and tried it out, I realized that it wasn't really necessary. The component already hides and shows properties based on toggle states. I just wish we could organize properties underneath specific variants. The variants are stuck at the top. But sometimes I have a property that only applies to a specific variant so it would be more intutitve to place it right under that variant.
@@robertboyhan2884 It's nice to have for visual cues, like when you have multiple variant properties for a single toggle action you'd be able to instantly recognize which ones belong under that group.
great talk, quite helpful
speaking so fast😨
I changed the playback speed to 0.9 when Alexia was presenting.
Ironically, the new UI is the worst update ever. It adds so much complexity, without much value except for looks. Also, it ruins the whole easy-to-use experience. Focus your resources on something else Figma team.
Give a couple of specific examples of how it increases the complexity please
LOL - I've heard this story before.
Just say change scares you
I agree with you on this