penpot / penpot

Penpot: The open-source design tool for design and code collaboration
https://penpot.app
Mozilla Public License 2.0
33.52k stars 1.7k forks source link

Microinteractions #769

Open jcklpe opened 3 years ago

jcklpe commented 3 years ago

Is your feature request related to a problem? Please describe.
Sometimes you have an interaction that does not lead to a change in the entire page, such as click on a hamburger menu button, so exiting a modal. Currently in penpot if you want to simulate that interaction you have to create an entirely new artboard. This requires a lot of duplicative screens. 

Describe the solution you'd like
micro interactions, similar to Adobe XD. 

Describe alternatives you've considered
a lot of drudgery I'd rather not maintain. 

Additional context
A good video explaining how this works in XD: 
https://www.adobe.com/products/xd/learn/prototype/component-states/use-auto-animate-and-component-states.html

jcklpe commented 3 years ago

related issue: https://github.com/penpot/penpot/issues/768

elhombretecla commented 3 years ago

Thanks for the info!!! We will review this and check the functionality we already have designed for this.

It will be part of our devs sprint in a close future :)

jdittrich commented 3 years ago

In figma, this seems to be called "overlays"

jcklpe commented 3 years ago

@jdittrich overlays in figma do allow for interacting with an interaction that changes a screen (such as a modal) but microinteractions are somewhat distinct in that they refer to changes at a component level such as a button hover or a toggle switch

jdittrich commented 3 years ago

@jcklpe so micointeractions is changing the look of a component, e.g. between a button’s normal/hovered/pressed/deactivated state, correct? (I think these are "Component Variants" in figma)

jdittrich commented 3 years ago

Maybe it would make sense to rename the issue as "microinteractions" does also refer to detail-focussed design of small-scale interaction, typically with animations. ("Component states", maybe?)

jcklpe commented 3 years ago

@jdittrich  : yes this is correct.