Component States
Alexander Vinogradov
Now it takes an enormous amount of time to create a simple tabs menu with buttons having active and normal states. Please do an ability to make a "snapshot" of the component and save it as a "state". Then allow to tween between them (or simply switch). Now it takes 2 hours to just set up showing/hiding and recoloring the text/shapes of the simple button (up/down/active/disabled)
Mete Polat
This is a must-add and would halve the prototyping time in many instances. Disappointed to see this not even "In Review" yet.
Garrett Anderson
This feature + autolayout is the game changing set of features that are required to make Protopie a worthy companion to Figma.
Rachel DeNoble
+1 the lack of component states is a massive headache
Jonathan Vinson
Rachel DeNoble: I concur. I just found out about ProtoPie yesterday and was blown away at how powerful and simple it was...until I tried to do something that I thought was simple, like button states and toggles. Over 400 people want this to happen, and all the less capable prototyping and design tools have it already, but on the agenda are apple watch players and barcode scanners? What? Buttons, toggles, sliders, etc. are the building blocks of so many things. Why not make it easier to implement?
Aakreit Sachdeva
This missing feature is what has moved my entire team to prefer uxpin
辰 黄
Aakreit Sachdeva: Thank you for helping me find a better software...
Patricia (ProtoPie Team)
Merged in a post:
Import Figma component states
Fynn MLlyr
When importing components with states, translate those states into equivalent triggers, conditions, and actions. Currently, when I import a component with states from Figma, it's not interactive at all. Recreating that in Protopie is a huge time suck.
Matthew Mercer
Agreed, having "states" within each component, a feature available in proto.io, would make components more capable and make the workflow for tasks as described above much simpler. +1
e
eden huh
open
S
Saulo Vallory
There's a cheap way to get 80% of this. You guys could simply show unmediatable interaction previews. That would already be a huge help.
The idea is that, for each trigger, we would have in the editor a preview of what the component would look like after all responses have been executed. And it can be a simple preview! Editing can be done as we do today as long as the trigger preview is automatically updated
L
Lucas Malaquias
Hopefully we can get this feature soon
D
DavidT Kim
under review
Load More
→