Variants (as known in Figma) or States (as known in Adobe XD)

[jcklpe]

Is your feature request related to a problem? Please describe.
Yes. Managing components without the ability to create variations/states is a mess. Single biggest issue that prevents me from attempting to use Penpot full time

Describe the solution you'd like
Have states. Pretty straightforward. Don't know what else to say. 

Describe alternatives you've considered
It's possible to make every state/variation it's own component but this is messy. Furthermore states are used in things like Adobe XD to manage things like microinteractions which wouldn't be possible with separate components.

[jcklpe]

Here's some videos that demonstrate these features:

https://www.youtube.com/watch?v=c8ov6IzFE0c

https://www.adobe.com/products/xd/learn/prototype/component-states/use-auto-animate-and-component-states.html

[elhombretecla]

Hi @jcklpe! Thanks for your feedback

We already have planned a set of advanced features for components into our road map. As you know, kind of "variants" or "states" functionalities are really complicated and challenging so they deserve the whole team best effort to accomplish them. But we have it in mind!!! Stay tunned :)

[jcklpe]

@elhombretecla : any updates on this? This is the only feature really missing IMO for me to start using this in production work.

[hirunatan]

Sorry, this is one of the important (and big) features but we still haven't prioritized it high enough.

[CasparNuel]

Is there any update about this? Penpot is very close to being my editor-of-choice for wireframing and UX/UI testing. States/variations not being available for components is currently a block for me though.

Expanding, moving or "interacting" components are a nightmare to manage with separate panes. States/Variations being implemented would mean a major leap forward in utility for Penpot.

[sneko]

Hi @hirunatan, any news on this?

[Improov-All]

We would like to transition to using Penpot, but alas, having multiple artboards to simulate component states is a pain that's blocking most projects.

[g-clems]

From what I've seen it's on the 2023 roadmap, so maybe we can expect it before 2024 ? maybe. I hope

https://community.penpot.app/t/faq-what-is-in-penpot-s-roadmap-for-2023

[jcklpe]

Let's hope so!

[sneko]

@elhombretecla it was in the 2023 roadmap, do you know the exact state of this feature?

Just found the following link that may indicate the task is still pending:
https://tree.taiga.io/project/penpot/us/2088?milestone=262806

[elhombretecla]

Hi @sneko :)

We're currently working on a new version of Penpot, Penpot 2.0, which is set to be released soon. This update includes a significant and necessary rework of the component functionality. This overhaul is crucial to address the feature of component variants that you're asking for. You can expect news on this development shortly, and we truly appreciate your interest and comment.

Thank you for staying updated with our progress!

[sneko]

@elhombretecla 2.0 is released 😄 ! Do you know where this issue stands in your roadmap now?

EDIT: it seems I can have common properties like shapes between multiple main components, but it still miss the idea of colors... that would make Penpot really useful for design systems.

[myfunnyandy]

@sneko this is one of our main focuses after the 2.0 release. The new components version that was included in 2.0 was a necessary step towards Penpot component variations, so we feel that we are closer.

We are currently working on the definition (you can read some of the advances here) and hope to start soon the implementation.