The Sorry State of States: Today’s Figma assets show design could align better with code medium.com/p/89dd4668737e - ThreadSky

About ThreadSky

nathanacurtis.bsky.social • 84 days ago

The Sorry State of States:
Today’s Figma assets show design could align better with code

https://medium.com/p/89dd4668737e

Comments

iknowdavehouse.bsky.social•84 days ago

For what it’s worth - I think I mentioned on Slack but we do have combinations like focus + error etc but none of our consumers actually use them. They are there for component definition rather than use (we found any form of interactive component apart from hover creates conflicts with prototypes)

iknowdavehouse.bsky.social•84 days ago

So I do often ponder to myself. Should we create a component for definition / specification AND a simplified one for Figma prototypes? Not that I want to do that!

wolfbruening.de•84 days ago

We usually build all states (except those that are automatically a given, like :focus) in Figma together with the devs in the creation of the component. But this is only a static design and not made for reuse.
Then we build the Figma component only with the states we need for design & prototyping.

iknowdavehouse.bsky.social•84 days ago

Yes! Do a bit of this also for the ones we don’t cover.

I just wish there was a “hide from
publishing” for almost everything. Hiding modes, hiding props, hiding values of props etc.

wolfbruening.de•84 days ago

Yeah that would be nice!

wolfbruening.de•84 days ago

The coded components in storybook are our single point of truth so we don’t need to have *all* states in Figma.

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply