I've read through all the available documentation (and I'm honestly just not sure if I'm understanding the process correctly) but is it possible to currently create a component, say a button, and generate different states such as rest/hover/click? I see you can nest components within components so I was questioning if that was my solution, but as it stands I'm not able to get anything workable save having a different button state on a separate artboard and performing state changes on the component between them. Is this functionality currently available and if not is it forthcoming? Thanks!
Also I apologize if this is the wrong place to ask, please feel free to redirect me to the correct location if so!
comments
Sort by
official comment
Hi Andy,
I would be happy to open a ticket on your behalf for this feature request as well! Please look for a message from our Support team soon.
Have a wonderful day,
Shaina
We’re currently tracking interest for this. If anybody else would like to add their vote for this feature, please contact Support here and voice your opinion!
Hi Michael!
You are in the right place to ask! Yes you can create such components, here's how I created a simple button inside a page, using a Button component.
I created a simple button component.
I reused the button component in every "Page 1" art board, and changed the color of the buttons to show the different states. So my Primary state art board has an interaction of hover and it'll show the pink art board. You can see the Interaction panel on the lower right panel.
And made my click interaction on the hover state to turn blue.
So...
if I have 3 buttons and each button has 'default', 'hover' and 'clicked' states in 3 different views, should I create 9 artboards to show that situation? it's like in hell...
I think component has multiple states is a good solution, but...
Thanks Lala, I managed to get your solution to work but I'm not sure you can actually call it a "component" since they all have to live in their own separate artboards and right now Studio won't handle the roll-on/off behavior correctly (far as I can tell), plus click can only act as a toggle and not a real down/press and release state.
I think some logic added into the components such as allowing them to have up/over/down/disabled/etc states would solve this issue, plus make it much cleaner at this point (like Wayne pointed out).
I'm coming from using Axure primarily for prototyping and there are concepts there I'd love to see come over to Studio to really make it shine as a prototyping tool, hopefully it evolves to incorporate some of those things moving forward.
Hi Wayne and Michael,
Thanks for bringing this to our attention, and for working with our Ambassador! I would like our Support team to receive your feedback regarding this functionality as they are interested in collecting as much feedback as possible while in the early stages of Studio.
I will open tickets on each of your behalf with our Support team. Please look for a message from them soon.
Have a wonderful day,
Shaina
I'd like to add an upvote for states within a component itself as well. I need to build prototypes with components that can reuse both visual styles as well as interactions. Copying a single component (like a button) around artboards is drastically easier and faster than replicating the interactions as they are played out above.
This feature, if executed well, would make InVision Studio the ideal protyping environment.
Yes Shaina +1 for me as well!
Hi Clint,
I would be happy to open a ticket for you as well! Please look for a message from our Support team.
Have a great day,
Shaina
+1 Component states are a must.
Hi,
I am also really missing this feature. This was actually the one feature I was missing from Invision and I was hoping that Invision Studio could provide. Also, this is the reason I still use tools like Axure and proto.io when prototyping.
Good Afternoon,
I believe this would currently be a feature a request.
Same here. Actually I was not even able to create a simple button with 2 different states, receiving for any try: "multiple states are not supported".
Thanks for any support.
Hi Ashley, John, and Tiago,
Thank you very much for adding your input to this thread in regards to this feature request. As mentioned in my post above, please be sure to add your vote for this feature by contacting Support here and voicing your opinion!
Have a wonderful day,
Shaina
+1 Component states are a must.
I don't want to create 5+ artboards to show how combobox works
Hi Peter,
Please be sure to add your vote for this feature by contacting Support here and voicing your opinion!
Have a great day,
Shaina