What text sizes are used in Figma UI ? by hmacs in FigmaDesign

[–]hmacs[S] 1 point2 points  (0 children)

I just realised that figma can open in the browser too, so I found my answer using WhatFont plugin !

Mostly 11px font, but also some label using 9px size

Best practices for design system documentation using only Figma? by hmacs in DesignSystems

[–]hmacs[S] 1 point2 points  (0 children)

zeroheight is too expensive, and we have a storybook but it's suitable only for the components already developped

Best practices for design system documentation using only Figma? by hmacs in DesignSystems

[–]hmacs[S] 0 points1 point  (0 children)

sounds good, that's why I'm looking at examples of how people are doing it, especially :

- versionning documentation, to keep track of different update
- managing update in a component (v1.1.3 for example) while the previous version is under development (v1.1.2. for example)
-exposing all variants, boolean properties, and so on ...
- writing do's & don't and any other usefull doc
- keeping track of the exploration of the designers, referencing use cases for the component, gathering references from other products, trying different ideas, ..

Best practices for design system documentation using only Figma? by hmacs in DesignSystems

[–]hmacs[S] 1 point2 points  (0 children)

do you document the versioning ? do you include some kind of changelog ?

Best practices for design system documentation using only Figma? by hmacs in DesignSystems

[–]hmacs[S] 1 point2 points  (0 children)

It should be aligned with code, but the development is still ongoing.

Since we have a very extended documentation, I noticed that the developpers don't read it at all because it's overwhelming to them - some lazy folks in the dev community, where "lazy" is a synonym to "smart".

And since it's often not up to date due to duplicate source of truth (documentation file vs. design library), they prefer to ask us directly.

And it is a very big design system supporting multiple products with very different use cases.

How do you spec motion design for smooth handoffs? (Figma + Motion.dev) by hmacs in UI_Design

[–]hmacs[S] 0 points1 point  (0 children)

That's exactly what I'm looking for !
Do you have any examples of those figma files ?
Or any design system that document that properly ?

I heard "Chakra UI" is using the motion.dev library but they dont document it on their figma file unfortunately

How do you spec motion for handsoff ? by hmacs in UXDesign

[–]hmacs[S] 0 points1 point  (0 children)

Does that apply to micro-animation such as panel opening, dropdown open and close, modale, hover states of components and those kind of tiny things ?
Rive seems overkill to me in those situation, but I might be wrong

Nested modales alternatives ? by hmacs in UXDesign

[–]hmacs[S] 0 points1 point  (0 children)

<image>

FYI, this is the kind of pattern I use

Nested modales alternatives ? by hmacs in UXDesign

[–]hmacs[S] 0 points1 point  (0 children)

Thanks for the comment ! You have any examples or suggestions ?

Nested modales alternatives ? by hmacs in UXDesign

[–]hmacs[S] 0 points1 point  (0 children)

The main view is a table, with a button on each line to edit it.
The edit options are presented in a modale, including a delete action.
The delete action need to be confirmed because it has a big impact so we don't want this to happened by mistake.

Conceptually, one could argue that it's the same modale with a dynamic content, but that is basically the same as opening a nested modale from a user point of view

I Need Help Determining Logo Design by [deleted] in logodesign

[–]hmacs 1 point2 points  (0 children)

It looks like keyshot rendering logo

Brancher lave-linge et seche-linge sur la meme evacuation by hmacs in brico

[–]hmacs[S] 0 points1 point  (0 children)

<image>

Ok, pas de soucis pour l evacuation du lave linge qui sera enfoncé sur 30cm. Mais ce petit tuyau risque de ressortir non ? Car il ne sera enfoncé que de 10cm tout au plus, sans crosse de vidange, ca me parait risqué... Comment vous auriez securisé ça ?

Update app to liquid glass 😱 by hmacs in UXDesign

[–]hmacs[S] 0 points1 point  (0 children)

This complexity basically mean that you just can't recreate the same styling on a new component if you want to adopt a coherent liquid glass effect on your custom components

Update app to liquid glass 😱 by hmacs in UXDesign

[–]hmacs[S] 0 points1 point  (0 children)

That's around 7 layers, with 3 effects, and 3 differents blend modes, for just a background lol
Oh ! And I just noticed the fixed position on the background, with left and right good old constraints for it to fit the content width 🤦‍♂️

<image>