Thank you so much for the video! It's very helpfully the way that you show every step! 😄 If you don't mind, I have another couple of questions... 1. There is a way that I could hide the connections between buttons and screens? As the connections between variants when you change to hover and active. This is because I'm designing a web, and thinking in the header, it will be A LOT OF connections on the design page (I have a lot of screens) 2. The connections that you showed up on your video are with components that are on the same page that screens, but, can I add a connection between components and screen if I have the variants in the page of Assets and screens on the page of Design? I don't know if I making myself clear. Thank you sooooooo much! I really appreciate your comments! there are really helpfully!😁
I've got one for you. How would you prototype something where hovering over one component affects another component? Example: When in prototype mode in Figma, hovering over the layer list also highlights the layer on the canvas. (This can be done bluntly but I'd like to know if there is an elegant way to do this with interactive components)
I would do this by creating my individual components and variants first, then combining those with the other things to be affected in a new component with variants. I think that’s about as elegant as you can get currently with native functionality.
Interesting workaround. I would still call this a workaround as the model on web allows you to do thisd. Figma has constraints on how its built and wont allow you to do that. You can do the same thing in a tool that is closer to web, e.g. Framer Or UXPin Or Axure... Not here...
This changes everything. I no longer have to make 6000 screens 😂
oh, thank you, wonderful man!
So, just started… am I the only one thinking there’s no hover on a phone?
Ha, good call. Pretend this is on a computer. 😜
Nope :)
Thank you so much for the video! It's very helpfully the way that you show every step! 😄 If you don't mind, I have another couple of questions...
1. There is a way that I could hide the connections between buttons and screens? As the connections between variants when you change to hover and active. This is because I'm designing a web, and thinking in the header, it will be A LOT OF connections on the design page (I have a lot of screens)
2. The connections that you showed up on your video are with components that are on the same page that screens, but, can I add a connection between components and screen if I have the variants in the page of Assets and screens on the page of Design? I don't know if I making myself clear.
Thank you sooooooo much! I really appreciate your comments! there are really helpfully!😁
This has been my interactive component issue! Thank you to the person who asked the question and to you for making the solution 👏
Thanks bro, you're the best!!
I like how spontaneous the video is. Just wondering, is the "Mouse Leave" trigger really necessary when hovering? I personally almost never used it.
It’s probably not necessary
Nice Matt! but what if you're working with a library?
I’d probably nest the library component in a new native file component, then link those nested native instances to the appropriate screens.
Great work! thanks for the walk-thru!
I've got one for you. How would you prototype something where hovering over one component affects another component? Example: When in prototype mode in Figma, hovering over the layer list also highlights the layer on the canvas.
(This can be done bluntly but I'd like to know if there is an elegant way to do this with interactive components)
I would do this by creating my individual components and variants first, then combining those with the other things to be affected in a new component with variants. I think that’s about as elegant as you can get currently with native functionality.
hover on mobile xd
🔥🔥🔥
Interesting workaround. I would still call this a workaround as the model on web allows you to do thisd. Figma has constraints on how its built and wont allow you to do that. You can do the same thing in a tool that is closer to web, e.g. Framer Or UXPin Or Axure... Not here...
You could call all design tools workarounds compared to how the web works.
@@mdsnotavailable Agree. all are workarounds in a spectrum. Figma is at an end of the spectrum where even the most trivial have high effort.
No hover on mobile
You don’t hook up a mouse to your iPhone like I do? 😅
@@mdsnotavailable Never thought about that idea... yet :)
Using this way you should keep your master component on the same page. Not good
This is only a quick example. You can still have components elsewhere and make it happen with smart nesting and prototype only component controls.